SLUG Mailing List Archives
Re: [SLUG] Re. Kernel panic: 2.6.5.-1-686 boot probs.
- To: slug@xxxxxxxxxxx, Alexander Samad <alex@xxxxxxxxxxxx>, Greg Cockburn <greg@xxxxxxxxxxxxxxxxxxxx>, cfree@xxxxxxxxxxxx
- Subject: Re: [SLUG] Re. Kernel panic: 2.6.5.-1-686 boot probs.
- From: Adam Felix Bogacki <afb@xxxxxxxxxxxxxxx>
- Date: Fri, 14 May 2004 00:39:59 +1200
- User-agent: Mozilla Thunderbird 0.5 (Windows/20040207)
Thanks guys. I've googled by
'mkinitrd examples', 'dave jones 2.6 upgrade' & 'wonderful world of
- which explains (i.a.) that parsing of the 'root= ' command has been
altered in 2.6.5 -
but in trying to get past 'Kernel panic' with a newly installed
2.6.5-1-686 kernel by booting
off a 2.4.18-bf2.4 rescue disk I get the following error message:
Tux:~# /usr/sbin/mkinitrd -m /boot/initrd-2.6.5-1-686custom.img -o
/usr/sbin/mkinitrd: /lib/modules/2.4.18-bf2.4: Not a directory
/usr/sbin/mkinitrd: MODULES needs to be set to none ?
Tux:~# cd /lib modules
Tux:~# /lib/modules ls
0.0.0 2.4.25-1-686 2.6.5-1-686 modprobe.conf modprobe.conf.old
My initial system was 2.4.18-bf2.4, I upgraded to 2.4.25*, and later to
The disk is almost certainly 2.4.18-bf2.4 ...
What do I have to do to successfully boot the 2.6.5* kernel ?