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.
I just got lilo installed to the MBR and now I get a Kernel Panic, cannot
open root device at "0" or unknown block (0,0)
Please append a correct root= boot device
Does this mean I need to change LILO to read something like Root= /dev/hda1?
I will post as much as I can, another thing is every time I reboot I have to reinstall LILO by running liloconfig because it is not there when i first boot from the cd.
I will post as much as I can, another thing is every time I reboot I have to reinstall LILO by running liloconfig because it is not there when i first boot from the cd.
I think that you closed your earlier thread a little too soon;-)
When you boot from the CD, a virtual filesystem is created with all the expected directories such as "/etc". This is _not_ the same as the filesystem on your hard drive, unless you use the "root=/dev/hda1" parameter when booting, but my guess is you didn't. You should mount your hard drive (the installer will do this for you if you want, or you can just do "mount /dev/hda1 /mnt"). Then if you ls /mnt you will see another root-looking filesystem. This is the actual one on your disk. At this point you can issue "chroot /mnt" to temporarily make the filesystem under /mnt the root filesystem. You need to do this before doing liloconfig because otherwise it will install lilo.conf to /etc/lilo.conf (ie. to the virtual filesystem) rather than to /mnt/etc/lilo.conf (your real filesystem). That's why it "disappears" after you reboot.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Quote:
Does this mean I need to change LILO to read something like Root= /dev/hda1?
Yes - that should point to your root filesystem device. The entry root=/proc is not right. Follow the instructions on the install cd/dvd - something like "hugesmp.s root=/dev/hda1 rdinit= ro" at the lilo prompt to boot then fix lilo.conf and rerun lilo.
I mounted the filesystem on the HD, did chroot /mnt and typed liloconfig, but...... I am getting the same error I got originally when i installed slack:
Fatal: open /dev/sda : no such device or address
Sorry but the attempt to install lilo has failed.... Etc.
I dont know what /dev/sda is, on this computer thats what I use to mount my camera.
Can I manually edit lilo.conf and enter the parameters from a working lilo.conf, such as the one on the computer I am using now?
/dev/sd* is for SCSI, SATA, USB, ect. devices. The older IDE PATA devices will be on /dev/hd*. You can look in /proc/partitions to see what's available, or at least recognized by the kernel.
"An error occurred during the root filesystem check,
you will be allowed to log into single user mode to fix the probelem.
This problem has nothing to do with lilo. It means that your filesystem has problems. You need to run fsck in order to find and fix whatever errors you have in your filesystem. Here is an explanation of fsck:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.