Slackware 10.2 Kernel problem
Hello guys. I have just installed Slackware 10.2 on my system. The installation went fine with no errors but when I booted into it, after
Starting PCMCIA, I got modprobe errors saying it could not find the folder /lib/modules/2.4.26 So I looked in /lib/modules and found no 2.4.26 I did however find 2.4.31 which i think is the kernel it should be using. so I checked in /boot for the image I was booting to and it was vmlinuz. but I also saw a vmlinuz-2.4.31 so I went into lilo.conf and changed image = /boot/vmlinuz to image = /boot/vmlinuz-2.4.31 then ran /sbin/lilo and then rebooted but that didn't seem to work either. :/ So now I am lost I don't understand why this is happening. Can anyone help me? Thanks. |
ok, so I figured out what was wrong in the end. Me, being the idiot I am, installed lilo to the MBR last time when I installed slack 10.0 and when I installed 10.2 I installed it to the superblock So all I had to do was reinstall lilo to the mbr. So I did that and had kernel 2.4.31 running with slack 10.2.
Then after that I decided to upgrade to linux 2.6.13 by going on to the linux install cd and accessing linux-2.6.13 on the cd and doing installpkg kernel-generic-2.6.13-1.tgz and the same with alsa drivers and kernel-modules and kernel-headers then I did mkinitrd -c -k 2.6.13 -m reiserfs and then I edited lilo.conf from image = /boot/vmlinuz to image = /boot/vmlinuz-generic-2.6.13 and then I did /sbin/lilo and then rebooted and got kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(3,3) _ So now I am stuck again :/ |
First of all, make sure you compiled in support for your filesystem into the kernel. If you've already done that, then do you have a SATA hard disk?
I have a SATA hard disk which is recognised as /dev/hda in 2.4, and as /dev/sda in 2.6. Here's what I do to get a 2.6 kernel working in Slackware:
|
All times are GMT -5. The time now is 05:51 PM. |