SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
kernel compile 2.6.20 - kernel panic - SATA drive
I am compiling a 2.6.20.4 kernel for a new box with a SATA drive. I am getting the following at boot:
Code:
md: autorun
md:..autorun DONE
VFS: Cannot open root device "805" or unknown-block (8,5)
Please append a correct "root=" boot option
kernel panic - not syncing VFS: Unable to mount root fs on unknown-block(8,5)
I think this has something to do with my drive being SATA but I have selected SATA settings in my config - perhaps not correctly. Any ideas ?? Sorry about the length of my post but I can't get a pastebin working right now !! I know this is probably something stupid ( I have compiled lots of kernels on my old PATA box with no problems).. Thanks in advance.
i believe you get a message like this if you dont have support for your root disk's controller, ie the SATA controller on your motherboard. my hard drives are IDE/PATA, so i have my intel ide controller built in.
did you add built-in support ('Y') for Device Drivers->Serial ATA...->Intel PIIX/ICH Sata Support
try starting with test26.s instead of huge26.s. Also if you jump up to 2.6.20.3 it fixes a huge number of SATA issues so download the source and go from there.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Original Poster
Rep:
I think I've got pastebin to work so here's a link to my .config that I compiled my kernel against.http://pastebin.ca/427828 and heres my lilo.conf:
Code:
# 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
# Windows bootable partition config begins
other = /dev/sda3
label = windows
table = /dev/sda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda5
label = linux
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# EH new 2.6.20 kernel
image = /boot/vmlinuz-2.6.20
root = /dev/sda5
label = linux-2.6.20
read-only
#
My kernel version was 2.6.20.4 to be exact - I probably should have made this clear. Anyway, I use make xconfig to generate a .config file so reading the settings in .config is not something I'm used to. I'm sure I selected
Quote:
built-in support ('Y') for Device Drivers->Serial ATA...->Intel PIIX/ICH Sata Suppo
when I ran through my kernel configuration but looking at my .config (again this is very much guesswork for me) it would appear that CONFIG_SATA_INTEL_COMBINED=y is relevant. (Incidentally - is there a reference guide anywhere to all these flags in the .config file ?
Quote:
You could make a initrd to provide the module for the new kernel. That is if you created the module. Read the /boot/README.initrd to see how.
I didn't really want to have an intial ram disk image loading if possible.
My intention in this, common with most kernel tinkering, is to get a kernel that (1) has a low latency for my music apps, (2) is fast to boot (3) takes advantage (even to a slight extent) of my SMP hardware and (4) addresses my hardware natively rather than through loading a module. In other words, tailored to my box - a Dell Dimension E520 with SATA disk. BTW - the documentation says something about accessing the singel hard disk through some kind of RAID driver - can't remember exactly what as I'm writing this under Slack. Vista (I've set it up to dual boot the dell fitted OS with Slackware 11) runs an application "Intel matrix" or something which I think has something to do with this. Sorry for being a bit vague with my information but I don't want to boot to Vista right now, (although I must admit it looks rather nice), probably shouldn't have said that here !!
My kernel version was 2.6.20.4 to be exact - I probably should have made this clear. Anyway, I use make xconfig to generate a .config file so reading the settings in .config is not something I'm used to. I'm sure I selected when I ran through my kernel configuration but looking at my .config (again this is very much guesswork for me) it would appear that CONFIG_SATA_INTEL_COMBINED=y is relevant. (Incidentally - is there a reference guide anywhere to all these flags in the .config file ?
I didn't really want to have an intial ram disk image loading if possible.
My intention in this, common with most kernel tinkering, is to get a kernel that (1) has a low latency for my music apps, (2) is fast to boot (3) takes advantage (even to a slight extent) of my SMP hardware and (4) addresses my hardware natively rather than through loading a module. In other words, tailored to my box - a Dell Dimension E520 with SATA disk. BTW - the documentation says something about accessing the singel hard disk through some kind of RAID driver - can't remember exactly what as I'm writing this under Slack. Vista (I've set it up to dual boot the dell fitted OS with Slackware 11) runs an application "Intel matrix" or something which I think has something to do with this. Sorry for being a bit vague with my information but I don't want to boot to Vista right now, (although I must admit it looks rather nice), probably shouldn't have said that here !!
So - thanks a lot for all the valuable input.
Hi,
You should make sure that the RAID is enabled in the BIOS. Even if you don't plan on using RAID, the controller will be enabled with this option.
I would use the huge26 or test26 to boot. Once you have the Slackware install cd1 boot then do a 'lspci -vv' to get all your recognized hardware. You can use this information to configure the kernel.
The loading of a module for the kernel will act the same as if the option was compiled in once the module is loaded. No difference! The advantage of compiling in is the 'latency' value of the not having to load a module. Not operational.
As for the SMP, you have it or you don't! If the hardware is there and the kernel support included then the action or use of the processors will be available.
You will need to set CONFIG_X86_BIGSMP, CONFIG_SMP in the '.config'. Don't forget HIMEM and ACPI in the '.config'. Compile and install the kernel with modules but make certain that you use a separate stanza in the 'lilo.conf' file for the new kernel image. Then run 'lilo' as root to update the disk record. This way you can always use the previous working kernel to reboot if a problem occurs.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
