Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
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.
I installed Salix 13.37. I installed it on an external hard drive and my laptop is a dell inspiron 1540 with an intel pentium. I installed the default kernel hugesmp.s. I ran the autoinstall option dedicating my entire external to salix. When it restarted, LILO loaded and I chose linux (trying to dual boot with windows) and then it put up BIOS data check successful followed by:
[7.148184]kernel panic-not syncing: VFS: unable to mount root fs on unknown-block
[7.148184]Pid:1, comm: swapper Not tainted 2.6.3.7.6-smp#2
[7.148296] Call Trace:
[7.148349][<c19daa01>] ?printk+0x1d/0x1f
[7.148401][<c19da8f3>] panic+0x5d/0x14d
[7.148453][<c1cfac39>] mount_block_root+0x1c0/0x259
And it continues in that fashion for a few more lines. BTW, I did try installing the other kernel option of huge.s but I got the same result. Any help that you can give me will be greatly appreciated. Thank you in advance.
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296
Rep:
Hi linuxlover2, Welcome to LQ. One of two things come to mind. Either Lilo isn't configured correctly or you don't have file system support built into your kernel. Options to correct this would be booting to a live disc and reconfiguring Lilo, rebuilding the kernel with support for your file system or creating an initrd to load the module at boot. I would start here.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.