[SOLVED] Missing kernel-modules package

mlangdn · 02-11-2011, 06:43 PM

I upgraded to the latest -current just like always. I do the kernel packages last. This time, the machine failed to boot, telling me that it could not find the kernel modules. Well, rats.

I booted with a slackware dvd, passed the huge.s kernel, and booted into /dev/sda7, which is my main partition. I mounted /dev/sda7, and installed the kernel-modules-2.6.35.11 pkg. Rebooted, and got the same error. ?????

I booted again with the dvd, mounted the partition, and navigated to /lib/modules - no 2.6.35.11 in there!!!

How do I get that package to install?

dive · 02-11-2011, 07:09 PM

ls -l /lib/modules
please

mlangdn · 02-11-2011, 07:36 PM

I got it sorted. I have no idea what happened on the original upgrade. Maybe when I was de-selecting kdexxx stuff from Alien that I didn't want upgraded, I went one too far!

When booting from the slackware dvd, I used:

Code:

huge.s root=/dev/sda7 noinitrd ro

It should have been:

Code:

huge.s root=/dev/sda7 noinitrd rdinit ro

All is well in Slackware Land - I just went brain-dead for a bit. I don't often have to boot to a rescue mode, and I simply didn't get it right.
False Alarm! Go back to your regular surfin'!

I have s**t for brains at times.

Intel_ · 02-12-2011, 04:06 AM

I upgraded (withoud install-new, but there aren't very important packages), recreated mkinitrd fot the new kernel, edited lilo, reran lilo, but after restarted - kernel panic:
not syncin: VFS....
PID:1,comm: Swapper not tainted 2.6.32.11 #1

I was forgot to add the line initrd=/boot/initrd.gz, so I booted linux mint, chrooted to /dev/sda3 (my / part) and added the line as reran lilo, but no effect. Tryed with the boot option /boot/vmlinux-huge.2.6.35.11, but again kernel panic. Is there any way to repair it withoud reinstall? May be the problem is that when i chrooted to / i didn't mounted and the /boot partition or?

mlangdn · 02-12-2011, 10:53 AM

I got into my system using the method in post #3. It should work for you as well.

Intel_ · 02-13-2011, 02:04 AM

So, I should download and record the latest iso current and boot the huge kernel? Btw I have kernel-modules installed - maybe my problem is different.

mlangdn · 02-13-2011, 08:57 AM

You don't need the latest iso, I used the first disk I found, and it was over a year old. We do not have the same problem, but we do have the same need of getting into the system to make a change. This will allow you to make that change, then run lilo to make it stick.