You are not logged in.
Pages: 1
Using powertop I found out that the kernel was preventing my laptop from going idle and reading this page found out about a patch for it.
http://www.lesswatts.org/projects/powertop/known.php
However, that patch is out of date as I just got 2.6.24.3 today. Is there a recent patch for this as it is very annoying to only get three hours where I get five in vista.
Offline
See powertop patch in dark kernel patchset.
Offline
Thanks for that. It got me to four hours and fifteen minutes estimated. I'm sure I could nudge it a bit more.
Offline
Offline
You will have to patch the source code and then compile.
Offline
Should i download the kernel26(with all archlinux patchs) from abs and after patch it with this patch ?
Offline
It's a start, yes .
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
It seems to me that a new version has been released.. http://forums.gentoo.org/viewtopic-t-671192.html
Anyway... what's the difference between patch and broken-out ?
Offline
As suggested, I've sync'd abs, then copied kernel26/ in /var/abs/local/, and finally edited PKGBUILD by adding this rows related to the patch:
#dark5 patch
patch-2.6.24-dark5.patch.bz2
# dark5 patch
patch -Np1 -i ../patch-2.6.24-dark5.patch || return 1
After running makepkg I get an error like this:
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file sound/usb/usx2y/usX2Yhwdep.c.rej
patching file sound/usb/usx2y/usx2yhwdeppcm.c
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file sound/usb/usx2y/usx2yhwdeppcm.c.rej
==> ERRORE: Compilazione interrotta.
L'operazione sta per essere interrotta...
There's something wrong or missing, I don't know how to go on.. any suggestion on how to fix my PKGBUILD?
Offline
It seems to me that a new version has been released.. http://forums.gentoo.org/viewtopic-t-671192.html
Anyway... what's the difference between patch and broken-out ?
These are patch sets, which means a lot of patches thrown together. Either in one big combined patch, or in a tarball which is actually a directory with all the patches in, separately. That's a 'broken out'.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
#dark5 patch patch-2.6.24-dark5.patch.bz2 # dark5 patch patch -Np1 -i ../patch-2.6.24-dark5.patch || return 1
After running makepkg I get an error like this:
Reversed (or previously applied) patch detected! Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file sound/usb/usx2y/usX2Yhwdep.c.rej patching file sound/usb/usx2y/usx2yhwdeppcm.c Reversed (or previously applied) patch detected! Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file sound/usb/usx2y/usx2yhwdeppcm.c.rej ==> ERRORE: Compilazione interrotta. L'operazione sta per essere interrotta...
Simple - the patching failed. Apparently you have patches that are conflicting here, and one file in concern is $startdir/src/linux-2.6.24*/sound/usb/usx2y/usx2yhwdeppcm.c but I can't tell what other files are involved since you didn't paste the relevant lines before this.
Last edited by schivmeister (2008-03-09 03:19:10)
I need real, proper pen and paper for this.
Offline
Just use the broken out ones, what you are doing now is applying the whole lot, I don't think that's what you're after.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
uastasi wrote:#dark5 patch patch-2.6.24-dark5.patch.bz2 # dark5 patch patch -Np1 -i ../patch-2.6.24-dark5.patch || return 1
After running makepkg I get an error like this:
Reversed (or previously applied) patch detected! Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file sound/usb/usx2y/usX2Yhwdep.c.rej patching file sound/usb/usx2y/usx2yhwdeppcm.c Reversed (or previously applied) patch detected! Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file sound/usb/usx2y/usx2yhwdeppcm.c.rej ==> ERRORE: Compilazione interrotta. L'operazione sta per essere interrotta...
Simple - the patching failed. Apparently you have patches that are conflicting here, and one file in concern is $startdir/src/linux-2.6.24*/sound/usb/usx2y/usx2yhwdeppcm.c but I can't tell what other files are involved since you didn't paste the relevant lines before this.
This is the PKGBUILD: http://pastebin.com/m6426d31a
These are the relevant lines before the error: http://pastebin.com/m10c1e6ff
Just use the broken out ones, what you are doing now is applying the whole lot, I don't think that's what you're after.
Now that I know what broken-out means I notice that I could only choose to apply something in particular and not the whole patch, but I'm totally a newbie in kernel patching...
Offline
That's a lot of files.
patching file net/ipv4/xfrm4_tunnel.c
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file net/ipv4/xfrm4_tunnel.c.rej
Self-explanatory; these are those that have already been patched, by the same patch or a different one modifying, removing and/or adding the same lines.
Hunk #7 succeeded at 8656 with fuzz 1.
Hunk #8 succeeded at 8668 (offset 1 line).
Fuzz denotes a guessing game, and offset denotes factual adjustment where it's merely moving lines up or down to match. In the end, the patch succeeds uncleanly.
Before you try to take down each and every failed file, get the broken-out ones.
I need real, proper pen and paper for this.
Offline
That's a lot of files.
patching file net/ipv4/xfrm4_tunnel.c Reversed (or previously applied) patch detected! Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file net/ipv4/xfrm4_tunnel.c.rej
Self-explanatory; these are those that have already been patched, by the same patch or a different one modifying, removing and/or adding the same lines.
Hunk #7 succeeded at 8656 with fuzz 1. Hunk #8 succeeded at 8668 (offset 1 line).
Fuzz denotes a guessing game, and offset denotes factual adjustment where it's merely moving lines up or down to match. In the end, the patch succeeds uncleanly.
Before you try to take down each and every failed file, get the broken-out ones.
Ok, I start with the broken-out way. I guess I have to extract ../patch/dark from broken-out-2.6.24-dark5.tar.bz2 and copy it into $startdir/src/linux-2.6.24*/ at first, but how to edit the PKGBUILD to include this patches, since they are stored into this subfolder?
Offline
That will already be in $srcdir if you have it as a source, as a folder named "patches":
source=(http://www.dcaf-security.org/dark-sources/broken-out-2.6.24-dark4.tar.bz2)
...
...
...
patch -Np1 -i ../patches/dark/powertop-2.6.24.patch
That will apply the powertop patch.
I need real, proper pen and paper for this.
Offline
Even better yet is pulling out the patch and adding it by itself to the source array and patch section of the PKGBUILD - at least, that's what I prefer.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
I just want to know if this is still up to date?
Powertop shows me the rescheduling interrupts and I want to get rid of this.
So, is there a newer patch available or what patch file do I need? (dark/powertop-2.6.24.patch ??)
Maybe someone can specify what B has said in the post above?
Thanks
Offline
Pages: 1