Review your favorite Linux distribution.
Go Back > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Debian This forum is for the discussion of Debian Linux.


Search this Thread
Old 09-19-2011, 02:03 PM   #1
Chemical Rascal
LQ Newbie
Registered: Sep 2011
Posts: 5

Rep: Reputation: Disabled
Installed LILO (from Slackware) in MBR, Debian no longer takes input

Short because nobody likes a life story:

I'm attempting to dual-boot Debian (Squeeze) and Slackware (13.37), so installed Slackware today, overwriting GRUB with LILO.

Long story short, booting into Debian now leaves me stranded at the (Gnome?) login GUI, without a responsive mouse or keyboard. Both devices work fine on Slackware (with XFCE).

I am able to mount the Debian partition in Slack, so that's that.

Obviously that's not going to be enough information, but I don't really know exactly what to provide - I'm well and truly up the creek here.

Thanks for any assistance,

Old 09-19-2011, 02:59 PM   #2
LQ Newbie
Registered: Mar 2008
Distribution: Slackware, Ubuntu
Posts: 5

Rep: Reputation: 0
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.
Old 09-19-2011, 03:58 PM   #3
Chemical Rascal
LQ Newbie
Registered: Sep 2011
Posts: 5

Original Poster
Rep: Reputation: Disabled
Boot arguments. Of course.

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?
Old 09-19-2011, 04:17 PM   #4
Senior Member
Registered: Oct 2008
Location: S.E. Montana
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,338

Rep: Reputation: 395Reputation: 395Reputation: 395Reputation: 395
I would chroot into Debian from Slackware and install Debians grub on the MBR with;
grub-install /dev/sdx
where x is your drive.
Old 09-19-2011, 04:36 PM   #5
Chemical Rascal
LQ Newbie
Registered: Sep 2011
Posts: 5

Original Poster
Rep: Reputation: Disabled
And that'd be the end of it, but I'm getting an error:

root@pvtjoker:/# grub-install /dev/sda
/usr/sbin/grub-probe: error: cannot find a device for /boot/grub (is /dev mounted?).
I've little understanding of what is going on at this point.

EDIT: After a little more coffee and a little more Google, I stumbled upon this:

user@tacos# mount --bind /dev /mnt/new/dev
Which, when done before the chroot, helped fix things nicely.

Thanks for the help guys, at the very least it's been a rather educating experience.

Last edited by Chemical Rascal; 09-19-2011 at 06:13 PM.
Old 09-19-2011, 06:20 PM   #6
Senior Member
Registered: Dec 2004
Location: Caracas, Venezuela
Distribution: Debian Sid, OpenSUSE 13.1
Posts: 1,018

Rep: Reputation: 315Reputation: 315Reputation: 315Reputation: 315
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
grub-install /dev/sda
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.

Last edited by odiseo77; 09-19-2011 at 06:41 PM.
Old 09-19-2011, 07:33 PM   #7
Senior Member
Registered: Oct 2008
Location: S.E. Montana
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,338

Rep: Reputation: 395Reputation: 395Reputation: 395Reputation: 395
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/ 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.
Old 09-19-2011, 10:34 PM   #8
Senior Member
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,385

Rep: Reputation: 186Reputation: 186
try this entry in your /etc/lilo.conf and rerun lilo
image = /vmlinuz
initrd = /initrd.img
root = /dev/sda?
label = debian
the ? will be the number of the partition that debian is installed on
Old 09-30-2011, 02:27 PM   #9
Registered: Apr 2005
Distribution: Slackware 13.37
Posts: 36

Rep: Reputation: 1
If you still want to try lilo ...

Do you have multiple hard disks ?

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 :


Last edited by svu; 09-30-2011 at 02:28 PM.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Slackware takes longer to reconnect to internet after suspending. piratesmack Slackware 3 01-31-2011 07:08 AM
lilo cannot installed on Windows 7 boot loader - MBR!!!!!!!!!! mpregos Slackware 12 06-02-2010 02:09 PM
Slackware's LILO overwrite XP's MBR andreas_skw Slackware - Installation 4 01-27-2008 08:09 AM
MBR deleted - I need to reinstall LILO without reinstalling Debian chaca1983 Linux - Software 12 03-26-2005 11:06 AM
slackware 9.1 + lilo could'nt write to MBR charlie.babitt Slackware - Installation 4 05-16-2004 04:23 AM

All times are GMT -5. The time now is 03:01 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration