Kernel Panic at boot from Promise ATA100 w/ Kernel 2.6
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
Kernel Panic at boot from Promise ATA100 w/ Kernel 2.6
I'v googled and searched these forums, and found many similar issues, but none quite as mine:
I have been running Slackware 10 with Kernel 2.4, and it booted like a charm. My Master HDD on the primary ATA100 controller was recognized as /dev/hde and booted from correctly.
Now, I compiled Kernel 2.6 and, I supposed, included all the neccessary support for my hardware. However, at boot, I receive a Kernel Panic telling me the Kernel couldn't find the "root" device which is being described as "unknown{xx:xx}" (dont know the exact numbers now, just say if theyre significant anI'll post them).
Choosing Kernel 2.4 again, it boots like always.
So, I suppose I forgot some support or something, but where do I activate that? I looked through the xconfig kernel-config (also with "Show All Options") and can't seem to find it.
HI,
This numbers (xx:xx) are important because tell you which disk and partition the kernel is looking for the root partition. You can find the complete table in "<your-kernel-source-directory>/Documentation/devices.txt".The first number is called Major and the second, the Minor number. You have to look for block devices as, the same major number are used for char and block devices, with different meanings.
After the last compile and install modules and kernel, did you run lilo?
@320mb: Booting is not my problem, I have two images for the same Linux installation in my LILO-config, so I can choose if I want to boot 2.4 or 2.6 - just that, with 2.6, it won't boot.
@osvaldomarques: The comlpete error message is: VFS: Cannot open root device "2106" or unknown-block(33,6). Then, it halts with a Kernel Panic.
Hi MikTheUser,
This 33:06 is /dev/hde6. It would be the third ide controller. Are you sure your root partition is /dev/hde6? Try "df -v" to see where is "/".
Are you sure you got everything needed compiled into the kernel? Sounds like you forgot IDE or filesystem support......neither can be modules if you make no use of intrd.
i'm having the exact same problem. i've got most everything working in 2.6.7 (framebuffer console, sound card, nic, filesystem, etc.) but i always get a kernel panic. my root partition is hdg3 (secondary master on promise ata 100 controller) and even when i pass the kernel the option root=/dev/hdg3 (which i know for sure to be the root partition) it panics. i think what would solve both of our problems is if we knew what drivers we should compile into the kernel (since modularizing them won't help).
if it helps, my controller is an onboard promise pdc 20265r ide raid chip. where is this driver located in gconfig?
mik: is your promise card onboard or offboard? if it is offboard, i was looking through the gconfig menu and it said something about ide reversal for offboard cards. compile that in, and if it doesn't work off the bat, try passing the kernel the option:
ide=reverse
and see where that gets you. if your promise card is onboard, try going to the motherboard manufacturer's website and find out exactly what kind of promise controller you're dealing with. i'm sure that will help get a solution from the gurus around here.
Note that, if you get an error saying "IRQ xx - Nobody cared!", you will have to put the corresponding IRQ number as an additional comma value after the PCI adresses, so your lilo.conf-line will look like this:
I don't actually run Kernel 2.6 now though, because it wouldn't support my Ethernet card, so I decided to wait until Slack officially supports it, with Slackware 10.1 or something
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.