Hello. I'm not too familiar with slack. The way I compile kernel in gentoo or arch is rather simple, just make and modules_install does it. And then copying over bzImage and System.map to /boot. I also copied the config file just in case. However I'm getting:

All I did was modify the default kernel and recompiled it. Didn't change anything except put my name instead of smp just to test how things are done in slack. And I did configure lilo, as it is showing in the menu.

make sure you have got an initrd.img. if no run inside your /boot directory
or ..

edit:i had the same issue earlier and i got it solved..visit thread
http://www.linuxquestions.org/questi...-error-753732/

Hi,

When you make changes to the '/etc/lilo.conf' then write your bootloader via the 'lilo' command.

>>mobinskariya

Thnx for replying, but is initrd really needed? By default I don't see any initrd image of the default kernel either. Hence I didn't create any.

>> oneBuck

yes I ran lilo after configuring /etc/lilo.conf and it gave one warning: LBA32 assuming...I can't remember the exact error. :P
Then it added Windows and the two linux kernels.

EDIT: Hi oneBuck, I saw your kernel compile guide, but they are outdated now. Would you please guide me from start how to do it in slack? Or is there already a new guide for 13? I'm going to try the new kernel 2.6.31
TIA

initrd isnt needed for the huge kernel..but for the generic kernel you need one..
editlease dont ask the difference between the two kernel.me too a newbie

ok will try that after oneBuck gives me some hint to compile 2.6.31 ; hopefully :P Thnx again

All you should have to do is make *config, make, make modules, make modules_install, copy bzImage to /boot/vmlinuz-whatever, ditto System.map, edit lilo.conf, run lilo. An initrd isn't necessary if you compile in the root filesystem drivers.

Hi,

Which guide are you referencing in post #4?

The compilation methodology is basically the same. There might be some minor semantics/syntax but generally the same for the newer kernels. Of course if you don't provide the filesystem in your kernel then you would need to create a 'initrd' and that method has been covered many times. Most distributions have the means to indicate how to create a 'initrd'. Slackware has the '/boot/README.initrd' which should be read to understand how to create the 'initrd'.

BTW, add 'lba32' to the global section of the '/etc/lilo.conf' file then run 'lilo' to update the bootloader to get rid of the warning.

What filesystem to you have, and is the support for it built into the kernel? A mistake I did was to take the regular configuration and optimize it, but somehow oversee that ext4 support was not built into the kernel itself, but rather only as a module, conveniently stored on the ext4 partition

Kind of like locking yourself out of your car, really..

-A

Yes but all I did was just took the default kernel's .config file and removed the -smp from append line and added -shy. Nothing else. How can that be so troublesome?

Hi,

Where did you do this? Please post example as there seems to be some confusion.

Yes I definiely did screw something up by doing that. I just went to /usr/src/linux and make menuconfig and then did the above. So I'm guessing /usr/src/linux was symlinking to 2.6.29.6 the default kernel. Anyway, I will not be even thinkin about compiling my own kernel for a while until I get things sorted,being a newbie to slack it's not going to be easy. I'm already having problem with nvidia driver. Thanks for all your help though.

A kernel's modules are stored in a directory on the root partition, namely /lib/modules. To use those modules, the kernel must first mount the root partition. If the root partition's filesystem driver is a module that it must mount the root partition to access, well, that won't work, will it? When you configure the kernel, you have two options. One is to specifically make sure that your filesystem's driver is compiled into the kernel, and not as a kernel module. (Don't assume it. Check it in the kernel configuration program!) The other is to compile the filesystem driver as a module, then put it in an initrd. There's a README file about this in /boot.

The huge kernel's configuration file actually does build support for most filesystems into the kernel. The generic kernel's configuration file has them built as modules.

Well I was using huge:
EDIT: Solved by mkinitrd, should have done hat earlier. Thnx for all the help.

One thing I noticed though while system bootup, that rc.d modules where still loading 2.6.29.6 modules.
How do I change that to my kernel's modules?
I don't have any such 2.6.31 rc modules there.
Re-EDIT: just copied the rc.modules of older kernel and created a new symlink. :P