LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Kernel Panic - VFS unable to open root device (https://www.linuxquestions.org/questions/slackware-14/kernel-panic-vfs-unable-to-open-root-device-247602/)

JcB 10-30-2004 11:05 AM

Hello!

Thanks for all your suggestions!

rotvogel: I recompiled, making sure that I selected all the options that you had, and I still get the same error message:(

Wintceas: I edited lilo.conf as you suggested, and it didn't work either:(

Lastly, Nichole_knc, I tried using mkinitrd, but I keep getting the following message:

WARNING: Could not find module for "ext2"

I had typed in: mkinitrd -c -m ext2

I also tried some other variations on this theme, like adding in -k 2.6.9 etc, but I got the same message. I think I'm doing something stupid...

Any suggestions?

Thanks

JcB

egag 10-30-2004 11:23 AM

hi there,

---
WARNING: Could not find module for "ext2"
---

that's normal, it's compiled in the kernel.
but if i were you i would try beginning from scratch,
eg. download a complete new kernel-source, and just try again.

egag

Wintceas 10-30-2004 11:27 AM

Mkinitrd
 
Quote:

(...) Lastly, Nichole_knc, I tried using mkinitrd, but I keep getting the following message:

WARNING: Could not find module for "ext2"

I had typed in: mkinitrd -c -m ext2 (...)
I had the same problem with mkinitrd when trying to pass the "ext2" value to parameter "-m". I solved this simply by omitting it. As mkinitrd writes the image with a default name (/boot/initrd.gz), I also used the parameter "-o" as a precaution, to make sure that the old initrd image would not be overwritten. I noticed that you didn't specify the kernel to use with the "-k" parameter. Why? mkinitrc will assume that you are building an image of the current kernel?


All times are GMT -5. The time now is 12:07 AM.