Hi,

A newbie question... hope someone can help.

I'm attempting to upgrade to the 2.4 kernel on my PIII notebook. The kernel currently in use is: kernel-image-2.2.20-idepci.

I've taken the following steps so far:

1) apt-get install kernel-image-2.4.16-686
2) added initrd=/initrd to /etc/lilo.conf as specified in the install instructions
3) ran lilo
4) rebooted

When I reboot, I have no network access. It seems that all of the necessary modules are not being loaded.

Why is it necessary to use initrd with this kernel image when it was not necessary with the previous kernel image?

Also, after booting up with the new kernel, uname -r still shows the old kernel version.... why is that?

Thanks in advance!

-Brad

try my guide that has explanations during each step, and if you still have problems
then post the errors, but many many people have been successful and happy with
this guide i put together, so i don't see why you won't be either ...

go here

hi DrOzz,
don't know if you would be able to help me out or not, but seeing your writeup decided to ask you.
just upgraded my laptop from kernel 2.6.0-test11 to 2.6.7 (Debian). there's no initrd-2.6.7.img file in /boot. however the m/c boots up in kernel 2.6.7 but i don't have network access. the laptop has a realtek card. i've selected 8139cp and 8139too in the kernel configuration as modules.
added this to /etc/modprobe.conf
alias eth0 8139too
and this to /etc/modules
8139too
but the module is not loaded. when i try to manually load the module from (/lib/modules/2.6.7/kernel/drivers/net/8139too) using modprobe i get these error messages:
8139too: Unknown symbol crc32_le
8139too: Unknown symbol bitreverse
FATAL: Error inserting 8139too (/lib/modules/2.6.7/kernel/drivers/net/8139too.ko): Unknown symbol in module, or unknown parameter (see dmesg).
also i can't see my interface (eth0) when i run dhclient.
here is what my /etc/network/interfaces looks like

auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp

any help will be greatly appreciated.
thanks a ton.

1. as for initrd, if you need it (but since you boot, you probably don't) use command mkinitrd
2. as for the message, there is an option in kernel config about crc32 capabilities, maybe it's needed. I dont remember if it's in general options or in crypto. If it works, please notify the 8139 packed developer to include a check at compile-time.

thanks. will give this a try today. don't have the laptop with me now. will post the progress.