
That one slipped under my nose. I'll definitely include it in the next release. Thanks for the heads up.michaelarch wrote:Hello,
Is the nforece2 apic patch included in this patchset? If not, could it be included in the future? Thanks for the great kernels!
Michael
Likewise!bAnTAi wrote:Haha... just switched to love2 today... oh well... two kernel upgrades in one day cant be bad... can it...
I'll have it up on a Dell Latitude Csx500 soon.ledskof wrote:Heh, I was right in the middle of compiling love2 when this thread popped up.
I'm using 2.6.1-love3 on a Dell Latitude c800, if anyone cares.
Code: Select all
killkenny love-sources # emerge love-sources
Calculating dependencies ...done!
>>> emerge (1 of 1) sys-kernel/love-sources-2.6.1-r3 to /
>>> md5 src_uri ;-) linux-2.6.1.tar.bz2
>>> md5 src_uri ;-) 2.6.1-love3.patch.bz2
>>> Unpacking source...
>>> Unpacking linux-2.6.1.tar.bz2 to /var/tmp/portage/love-sources-2.6.1-r3/work
patching file CREDITS
Hunk #2 succeeded at 2677 with fuzz 2 (offset 7 lines).
Hunk #3 FAILED at 3584.
1 out of 3 hunks FAILED -- saving rejects to file CREDITS.rej
patching file Documentation/Changes
Reversed (or previously applied) patch detected! Assume -R? [n] my bad, a fixed ebuild should be up in 5 seconds from nowbAnTAi wrote:Hmm... having some trouble... what does the following mean?
and most importantly... how do i fix it?Code: Select all
killkenny love-sources # emerge love-sources Calculating dependencies ...done! >>> emerge (1 of 1) sys-kernel/love-sources-2.6.1-r3 to / >>> md5 src_uri ;-) linux-2.6.1.tar.bz2 >>> md5 src_uri ;-) 2.6.1-love3.patch.bz2 >>> Unpacking source... >>> Unpacking linux-2.6.1.tar.bz2 to /var/tmp/portage/love-sources-2.6.1-r3/work patching file CREDITS Hunk #2 succeeded at 2677 with fuzz 2 (offset 7 lines). Hunk #3 FAILED at 3584. 1 out of 3 hunks FAILED -- saving rejects to file CREDITS.rej patching file Documentation/Changes Reversed (or previously applied) patch detected! Assume -R? [n]

Code: Select all
killkenny love-sources # emerge love-sources
Calculating dependencies ...done!
>>> emerge (1 of 1) sys-kernel/love-sources-2.6.1-r3 to /
>>> md5 src_uri ;-) linux-2.6.1.tar.bz2
>>> md5 src_uri ;-) 2.6.1-love3.patch.bz2
>>> Unpacking source...
>>> Unpacking linux-2.6.1.tar.bz2 to /var/tmp/portage/love-sources-2.6.1-r3/workpatching file CREDITS
Hunk #2 succeeded at 2677 with fuzz 2 (offset 7 lines).
Hunk #3 FAILED at 3584.
1 out of 3 hunks FAILED -- saving rejects to file CREDITS.rej
patching file Documentation/Changes
Reversed (or previously applied) patch detected! Assume -R? [n] Code: Select all
ebuild love-sources digestI believe the change to kexec-syscall.c should actually beWedge_ wrote:For anyone who wants to try kexec:
Once you've compiled the kernel with kexec support, you need to get kexec-tools. Extract them somewhere (I didn't make an ebuild, if anyone wants to go ahead), and cd into the directory created. Open kexec/kexec-syscall.c in an editor and look for the line that saysChange it toCode: Select all
#define __NR_kexec_load 259then run "make" to compile the tools. This creates two files under objdir/build, sbin/kexec and bin/kexec_test. I'm not exactly sure what kexec_test is supposed to do (you need to run it with "kexec kexec_test") but all it seemed to do was cause a normal reboot. To load a new kernel using kexec, useCode: Select all
#define __NR_kexec_load 274You should see a line saying "Starting new kernel", then the usual boot messages should start scrolling past as if you'd just left the bootloader. It doesn't seem to like the framebuffer - it prints the "Starting new kernel" message, then doesn't display anything else, but the system does actually load the new kernel. If you want to try it but have framebuffer enabled, you can just remove the vga=/video= options from your bootloader temporarily, that seems to work for me.Code: Select all
objdir/build/sbin/kexec --command-line="`cat /proc/cmdline`" -l -f /boot/bzImage
I'm also not sure of the best way to use it. When you run the kexec command, it loads the new kernel immediately, which can screw things up as filesystems don't get unmounted properly, and hardware isn't reset etc. The 3Com NIC on my nForce2 in particular didn't like this, and gave all sorts of errors once the new kernel had loaded. If anyone has suggestions on the best way to go through the usual pre-reboot procedure but to run kexec instead of reboot, please post them.
Code: Select all
#define __NR_kexec_load 275