thanks. really i can live without bootsplash, but i can't live without lirc, and my usbstickvrln wrote:2: vesafb-tng doesn't work/is unstable on SMP systems (in other words a hyperthreaded p4)
Code: Select all
>>> Unpacking linux-2.6.9.tar.bz2 to /var/tmp/portage/nitro-sources-2.6.9-r1/work
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Success
Input file = /usr/portage/distfiles/linux-2.6.9.tar.bz2, output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
tar: Read 7600 bytes from -
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
!!! ERROR: sys-kernel/nitro-sources-2.6.9-r1 failed.
!!! Function unpack, Line 380, Exitcode 2
!!! failure unpacking linux-2.6.9.tar.bz2
!!! If you need support, post the topmost build error, NOT this status message.Say Y to "Prompt for development and/or incomplete code/drivers" in "Code maturity level option" and it will appearTheHermit wrote:Works great but how do I enable reiser4 support? I don't see anything when I do 'make menuconfig'.
Yes I have that checked as Yes and tried No to "Select only drivers expected to compile cleanly". I don't think it's the issue but could the fact then I used the ebuild made a difference? I'll see what happens by manually applying the patch.seppe wrote:Say Y to "Prompt for development and/or incomplete code/drivers" in "Code maturity level option" and it will appearTheHermit wrote:Works great but how do I enable reiser4 support? I don't see anything when I do 'make menuconfig'.
Nope, I emerged this kernel as well and reiser4 worked, it has nothing to do with the ebuild. Normally, you should see Reiser4 inbut could the fact then I used the ebuild made a difference? I'll see what happens by manually applying the patch.
That was it! Thanks for the help.seppe wrote:Nope, I emerged this kernel as well and reiser4 worked, it has nothing to do with the ebuild. Normally, you should see Reiser4 inbut could the fact then I used the ebuild made a difference? I'll see what happens by manually applying the patch.
File System
--> <*> Reiser4 (EXPERIMENTAL very fast general purpose filesystem)
Did you enabled "Use 4Kb for kernel stacks instead of 8Kb" in "Kernel Hacking"? If so, turn it off, reiser4 won't work with 4Kb kernel stacks.

FYI:
Did you enabled "Use 4Kb for kernel stacks instead of 8Kb" in "Kernel Hacking"? If so, turn it off, reiser4 won't work with 4Kb kernel stacks.
Code: Select all
INSTALL sound/pci/emu10k1/snd-emu10k1.ko
INSTALL sound/synth/emux/snd-emux-synth.ko
INSTALL sound/synth/snd-util-mem.ko
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.6.9-nitro1; fi
WARNING: /lib/modules/2.6.9-nitro1/kernel/sound/core/seq/snd-seq-device.ko needs unknown symbol snd_seq_autoload_lock
WARNING: /lib/modules/2.6.9-nitro1/kernel/sound/core/seq/snd-seq-device.ko needs unknown symbol snd_seq_autoload_unlock
Ah, that -p is totally new thing. That makes things much easierfimbulvetr wrote:Oktane,
Not sure if you knew this, but instead of doing:You can just doCode: Select all
mkdir /usr/local/portage && mkdir /usr/local/portage/sys-kernel && mkdir /usr/local/portage/sys-kernel/nitro-sourceswhere -p means "make the parent directories".Code: Select all
mkdir -p /usr/local/portage/sys-kernel/nitro-sources
-fim
Code: Select all
CC arch/i386/power/suspend2.o
arch/i386/power/suspend2.c: In function `__smp_suspend_lowlevel':
arch/i386/power/suspend2.c:541: error: `c_loops_per_jiffy_ref' undeclared (first
use in this function)
arch/i386/power/suspend2.c:541: error: (Each undeclared identifier is reported o
nly once
arch/i386/power/suspend2.c:541: error: for each function it appears in.)
make[1]: *** [arch/i386/power/suspend2.o] Error 1
make: *** [arch/i386/power] Error 2
Darckness wrote:Gentree-you need CONFIG_KMOD=y to stop that error
Code: Select all
Automatic kernel module loading It will be back when netraverse releases patches for 2.6.9, the one's for 2.6.8.1 are hard to get working on a 2.6.9 kernel. PickledOnion can help me with this as well (he is the win4lin patch masterkohno wrote:I'm using it now, but it seems win4lin is missing.
Yeah, it works for me, what is the problem?gmichels wrote:Anyone with swsusp2 working with this one? It's hard to leave swsusp2 once you get used to it