As some of you know, I've been trying to get a good kernel compile for a few weeks now. This is my latest problem, and I have no idea what to do =(

VFS: kmod: failed to exec /sbin/modprobe -s -k block-major-8, errno = 2
failed to exec /sbin/modprobe -s -k block-major-8, errno = 2
VFS: Cannot open root device "806" or 08: 06
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 08:06

This was made using the exact same configuration as the original kernel, but used to compile 2.4.24 (from 2.4.22).

Can somebody please give me some insight as to what's going on?

sounds like a boot loader problem, at least in part. are you using lilo or grub? it might help if you could post the relevant file, e.g., /etc/lilo.conf.

I am using LILO. I will post my original config below:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# 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
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda6
label = Linux
read-only

image = /boot/vmlinuz.old
root = /dev/sda6
label = Linux.old
read-only

# Linux bootable partition config ends

dumb question, but you remembered to run /sbin/lilo after compiling the kernel and moving the kernel to /boot, right? (sometimes i forget... )

i've never used scsi with linux, so this is a shot in the dark, but do you have scsi support for your devices and everything you need for that built into your kernel? just guessing, but with that modprobe error, it almost looks like it can't load the right stuff for scsi, and then the boot fails b/c it can't find your disk.

synapitcal,
I finally got it working. Somehow the make oldconfig put my SCSI as a module, and not built-in. I got that working now.

However... I have enabled SMP for 2 processors, yet it is still only using one processor! This is half the reason I was recompiling to begin with (plus High Mem support, which is now working right). Any ideas??