Slackpkg upgrade-all: kernel panic
Hi,
I've upgraded SW with the latest security packages yesterday and now I get a kernel panic (installed the kernel sources too, otherwise couldn't reinstall the nvidia driver). I guess it has to do with the initrd.gz, right? I'm using jfs on / (sda3) and /home (sda5). So I thought I would have to create an initrd.gz, chrooted into /boot, but now what? Code:
mkinitrd -c -k 2.6.27.31-smp -F And then change /etc/lilo.conf and add the line Code:
initrd = /boot/initrd.gz Code:
image = /boot/vmlinuz Am I missing something? Never done this before, so I wanna be sure. ;) |
Quote:
samac |
OK, thanks, will try that.
The stuff in /etc/lilo.conf is correct do you think? |
I usually give parameters for the kernel modules to load, root filesystem, root partition and clear the existing file tree. So the command would be :
Quote:
I also note that you have Quote:
|
Alien Bob put a nice script (/usr/share/mkinitrd/mkinitrd_command_generator.sh)
in Slackware to help facilitate the making of an initrd image. While it doesn't guarantee to remove all possible errors from the process, it does a good job. Just issue "sh /usr/share/mkinitrd/mkinitrd_command_generator.sh" and the script will output a suggested command. If it looks good to you, run that and then afterwards, run "lilo" to write the new bootloader. |
OK, thanks, I downloaded the script and put it on a USB stick, mounted it and ran the script. Followed the advice and then ran lilo. Rebooted and get this error:
Code:
no kernel modules found for Linux 2.6.27.31 The script adviced 2.6.27.7, shouldn't that be 2.6.27.31? But I tried that too and it didn't work either. |
Quote:
You mean there has to be a new set of lines in lilo.conf, instead of using the old ones? |
Quote:
Code:
# Linux bootable partition config begins As to your problem now. Boot back to the system and make sure you're running kernel 2.6.27.31 with "uname -r". It looks like something has gone strangely wrong with your initrd creation. Did you supply the "-k" and "-m" parameters correctly to mkinitrd ? |
You don't need to download the script, it's on your system:
Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh Code:
sh /usr/share/mkinitrd/mkinitrd_command_generator.sh -i If you're not fixed up, perhaps post the output of "ls -l /boot/". As for the "no kernel modules found for Linux 2.6.27.31" message, it sounds as if the CD/DVD/USB whatever you installed with was not using the latest kernel. Maybe you had a media that you made from a local mirror or something before the last updates to -current? |
Uname isn't going to help be because I boot from the SW DVD.
I'm pretty sure it was 2.6.27.7-smp. But upgrading with these security patches, that should be 2.6.27.31, right? I've booted Knoppix now (also got erors on /proc) and now I see that /proc is empty! That's not normal, is it. |
Please post the output of "ls -l /boot/".
|
Quote:
I'l start over from scratch. boot SW 12.2 DVD mkdir /mnt/slack fsck.jfs /dev/sda3 (filesystem is clean) mount /dev/sda3 /mnt/slack chroot /mnt/slack cd /boot ls -l (ehmmm, that's an awful lot to type, but i'll give it a try) Code:
README.initrd -> /usr/doc/mkinitrd-?.3.3/README.initrd |
Quote:
Quote:
|
Quote:
|
To add a few things, I'm in /boot now as you could see and run the script:
sh mkinitrd_command_generator.sh Code:
?ind: /sys/block: no such file or directory |
All times are GMT -5. The time now is 09:41 PM. |