arghhh I'd like to listen to Miles Davis melodic bass on a 2.6 kernel right now... Anyway, I decided to compile the kernel myself instead of apt-getting an image since I'm not seeing all the modules. I'm hoping that downloading the kernel source and compile it myself, I can have all the necessary modules (at least the sis900 network card module!!). Alas, which is the suggested 2.6 version to download?

2.6.0 is the most recent. I suggest compiling in as much as possible INTO the kernel directly. So far, with 2.6 that's worked out the best for me. However, after apt-getting module-init-tools I CAN see modules in modconf, so I'm uncertain why you can not.

but remember - I have apt-got a kernel image till now - i haven't compiled any kernels (yet). Secondly, you're using Sid, whilst i'm using Woody, and i've read that sid should not give any problems with apt-get 2.6's kernel-image.

Alright, after downloading the linux-2.6.0 source from kernel.org (use a mirror) you untar it in /usr/src. you descend into the /usr/src/linux-2.6.0 directory and type

make menuconfig (or gconfig, xconfig--I prefer menuconfig). Here is where you set options. What I did was look at my 2.4.23 kernel .config file (which was in /usr/src/linux-2.4.23/.config in one xterm and compiled 2.6.0 in another. As you posted part of the .config above, you'll get my drift. This way I make sure that options I want are recompiled into 2.6.0. What I mean by compile it IN instead of modular, is choose Y for YES instead of M for module. This builds a fatter kernel and less modules. after this is done, exit out and save. Now you are ready for the Debian way. Personally, I just use make, make modules modules_install.

Regardless of HOW you compile, you'll want to follow the kerneltrap how-to posted earlier in this thread.

Then, the modules will live in /lib/modules/kernel-version

[ken:modules](08:52 AM)$ ls
2.4.18-bf2.4 2.4.23 2.6.0 modprobe.conf.old
2.4.22 2.4.23-backup modprobe.conf

And inside of 2.6.0/kernel/drivers/* are your modules (if you built any). I don't know how well 2.6.0 works with Woody. Unless this is a server box, I'd upgrade to Unstable. It is rarely "unstable" and will give you more up-to-date packages and features. However, if it IS a server I would wait for any kinks not worked out in the 2.6.test kernels to wash out.

Go ahead and try compiling your kernel. Provided you always leave a backup boot option (other kernel) in grub/lilo, you'll learn alot in the process.

HTH some.

yes i agree. that has been always a stage where i wanted to find myself in (compiling a kernel) and i think the moment has come *fingers crossed*

I have compiled and built the 2.6.1 Kernel and gave me no errors. I then placed the BzImage and System.map files in the /boot directory, and added the following entry in the lilo.conf file:

image=/vmlinuz.2.6.1
label=Linux-2.6.1
read-only

I booted with the new kernel, and I got this error (a freakin kernel panic):

VFS: Cannot open root device "307" or unknown-block (3,7)

so I tried to add this line in the 2.6.1 section: root=/dev/hda7 (it was already there in the main part of the lilo file), but I still got the same error...

anybody knows what have i missed? I've read all the kernel-how to's!!!

Did you compile support for your / file system into the kernel? If not you need to make an initrd and use an initrd line in your lilo.conf under the image= for the kernel or recompile with support for the file system included.

I have compiled my / filesystem (ext 3) INTO the kernel (i.e. not as a module), as desribed by some forums. In addition to that, I have also cramfs loaded into the kernel, and finally made an initrd image by using:

mkinitrd -o /boot/nitrd.img-2.6.1-686 /lib/modules/2.6.1/

I then placed the initrd image in / , made the necessary changes in the lilo.conf file, and finally ran lilo.

I rebooted and another error says:
RAMDISK: Couldn't find a valid RAM disk image starting at 0.

After that comes the previous error that the kernel cannot open the root device. I have also pasted my kernel's .config file here:

http://www.pastebin.org/index.php?pa...key=7ghd6vsogi

Any help is greatly appreciated (since I have played all my cards by now)

ganninu.

You do either one or the other you do not need an initrd when you compile the support into the kernel. Remove the initrd line and run lilo and you should be able to boot with the kernel. BTW have you installed the module-init-tools that are needed to boot a 2.6.X kernel?

yes I have already tried that move... And yes again, I installed (apt-get install) the module-init-tools

I have tried everything guys to compile the 2.6.1 kernel on my Debian woody but invain. i still get the same error!!

I want to know whether someone can send me his config file so I can try it out... I have an Asus Terminator...

Cheers,
ganninu

You can get mine here it has support for the ext2. ext3 and reiserfs compiled in it is setup for ide-scsi emulation of the CD/DVD-R/W's with a onboard via686 sound and SB live for alsa with the OSS emulation plus support for the via chipset on the MB, if you have a netcard that uses either the tulip, 8139too or ne2k-pci module it has them and if you have a MS Sidwinder joystick you good to go with it as well used through the sb live game port.