Hi,
I have a SATA disk. Recently I've installed slackware 10.2 without having a problem. Later i compiled a 2.6 kernel. When it comes to boot from the partition it gets this error:

VFS: Cannot open root device "806" or unknown-block(8,6)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,6)

I've compiled the sata driver in the kernel (not as a module). Here is my lilo.conf:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda
#compact # faster, but won't work on all systems.
prompt
timeout = 300
# VESA framebuffer console @ 1024x768x64k
vga = 791
# 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
# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.16
root = /dev/sda6
label = Linux
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/sda1
label = Windows
table = /dev/sda
# Windows bootable partition config ends


Can anyone help me?
Thanks in advance ...

It looks like your new kernel doesn't have support for SATA disks. Notice how it calls it "unknown-block".

Yeah, I agree with ataraxia.

Boot from your original kernel and recompile your kernel. Make sure you select the correct "block device" and SATA controller in the kernel config.

From the looks of the lilo.conf it doesnt look like you left an entry for the original kernel. Get in the habit of always leaving a backdoor for yourself after you compile a new kernel and reboot. Then, if it fails, you don't have to boot from the slack inst cd.

Scott