[SOLVED] Installed LILO (from Slackware) in MBR, Debian no longer takes input
DebianThis forum is for the discussion of Debian Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Probably Debian included another configurations in the grub-config, such as kernel flags and modules.
I would suggest you to use grub instead of LILO for this case because of Debian. Slackware will
work fine with whatever you use.
Upon closer inspection of the scrolling boot text, it seems to complain about a "uinput" module or something similar not being loaded. There might be something else, I'm not totally sure.
You've given me an idea, though, knivel - Unfortunatley it seems like it'll be more than a little bit difficult to restore GRUB from within Slackware, but given that all of GRUB's configuration data is still on Debian's partition, is there something I could tweak slightly to allow chainloading GRUB from LILO?
The problem is that debian can't find /dev because it's only running in a chrooted environment. Have a look at this. I haven't tried it, so I'm not sure how it will work, but to make it a bit clearer, this is what I'd do (from Slackware):
mount /dev/your_debian_partition your_debian_mount_point
mount -t proc your_debian_mount_point/proc
mount -B /dev your_debian_mount_point/dev
chroot your_debian_mount_point /bin/bash
In case Debian didn't add an entry for Slackware to the grub menu, then boot into debian, install os-prober (with apt-get/aptitude/synaptic), and run:
It should detect all other OS's in your system and make entries for them in /boot/grub/grub.cfg, so you can boot them.
EDIT: Didn't see your edit when I posted. Good you got it working.
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Os-prober is provided with the current grub which runs it as long as /etc/grub.d/30_os-prober is enabled.
I would be checking in your Debian installs /boot/grub/device.map. Sounds like it may have a problem. If that is there and correct you should not get that error.
I run many installs per drive and am all the time switching from one to the other for my grub on the MBR. This is usually done in a chroot environment as I don't visit those installs except to experiment with whatever I have each of them designated for.
Grub I play with a lot, and like to know that each installs grub works in case I really "improve" one to the point it no longer works.
I have and I'm experiencing the fact that Slackware recognizes my disk with multiple Linux partitions as /dev/sda while the same disk in Debian or Arch will be /dev/sdb ...
I too experienced the problem where Debian would start + hang without a working mouse / keyboard / anything...
I was just stranded on the login screen.
After a while I figured out how Debian somehow booted while using the Slackware kernel. (things were getting mixed up because of the sda / sdb difference)
Maybe you're experiencing the same problem. If I remember correctly I solved this by using root = "UUID ........" instead of referring to the /dev/sda in lilo.conf
You can find the UUID by running this command :