kernel recompile

Prism · 08-29-2004, 07:01 PM

I'm having some trouble trying to compile the 2.6.8.1 kernel on my slackware box, it seems to compile ok etc. then i copy the image to the /boot ,then appropriate changes to my lilo.conf...
anyway when I try to boot with the new kernel i get the following error:

Quote:

Cannot open root device "342" or unknown -block (3,66)
please append a correct "root=" boot option
Kernel panic :VFS: Unable to mount root fs on unknown -block (3,66)

I thought it might be a problem with my bootloader (lilo) and I added the line append = "root=/dev/hdb" to my lilo.conf, my lilo.conf currently looks like this:

Code:

# Start LILO global section

boot = /dev/hda

#compact        # faster, but won't work on all systems.
prompt
timeout = 300

# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0     # paranoia setting
# End LILO global section

# Windows bootable partition config begins
other = /dev/hda1
  label = Windows
  table = /dev/hda
# Windows bootable partition config ends

# Linux bootable partition config begins
  image = /boot/vmlinuz.old
  root = /dev/hdb2
  label = Slackware
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends

#linux bootable partition config begins
  image = /boot/vmlinuz
  append = "root=/dev/hdb"
  root = /dev/hdb2
  label = Slack-2.6.8.1
  read-only 
#end config

I was told that it could be a problem with line 468 of my Makefile, which is commented by default, that doesn't seem to be the problem though.

Code:

export INSTALL_PATH=/boot

Does anybody know how to fix this problem, thanks

edit: I forgot to mention, i'm upgrading from the 2.4.26 kernel

moonloader · 08-29-2004, 07:45 PM

hi!did you command once you are in /usr/src/linux-2.6.8.1?
cp /usr/src/linux-2.6.8.1/arch/i386/boot/bzImage /boot/vmlinuz-2.6.8.1
cp /usr/src/linux-2.6.8.1/System.map /boot/System.map-2.6.8.1
ln -s /boot/System.map-2.6.8.1 /boot/System.map

if you didn't then go to the /usr/src directory
su
password:
cd /usr/src/linux-2.6.8.1
then command the above and go to /boot then make sure vmlinuz-2.6.8.1 and System.map-2.6.8.1 are in /boot directory finally fix your lilo.conf

linux bootable partition config begins
image = /boot/vmlinuz-2.6.8.1
root=/dev/hdb
root = /dev/hdb2
label = Slack-2.6.8.1
read-only

#end config

run as root /sbin/lilo

Prism · 08-29-2004, 08:19 PM

I did do that, i just neglected to mention.. thanks anyway

moonloader · 08-30-2004, 07:31 AM

but your lilo configuration was wrong in your first post!

Prism · 08-30-2004, 09:06 AM

What's wrong with my lilo.conf, i don't think

Code:

root=/dev/hdb
root = /dev/hdb2

is the answer, i can't use the same option twice

Nikon01 · 08-30-2004, 09:31 AM

Well first of all root= is supposed to point to the partition that your root directory is on. I think your problem is that in your 2.6.8.1 kernel entry you are pointing at the device and then you root directory. I'd take out that Append= stuff and just leave root=/dev/hdb2. Another thing is if you compiled your kernel w/o the export boot thing commented you're more than likely gonna run into problems after you take out the double root=. So if you run into problems after the double root= thing I would recompile the kernel w/ the export thing uncommented.

cragwolf · 08-30-2004, 09:39 AM

Do you have a SATA hard drive? If so, then this might be the problem. I've heard that the later kernels detect sata differently then they did before. So instead of detecting your drives as hda or hdb, they might be detected as hde or hdf (if you have two standard ide channels), or maybe even as sda or sdb. I have a sata hard drive, but I haven't compiled a newer kernel yet, so I haven't been able to check this yet. If true, this would mean you'd have to edit your lilo.conf file and your fstab file (at the very least) appropriately. Another possibility is that you've left out something crucial in your .config file. Oh, and remember, the boot disk is your friend.

Prism · 08-30-2004, 12:51 PM

I've given up trying the new kernel, i'm going to stick with the 2.4.26 for a while.. thanks for the help

Tuttle · 08-30-2004, 12:53 PM

Are you using the reiser filesystem? If so, did you include it in the kernel (a "yes" not just a module)?