Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
This is the error displayed by LILO upon booting:
"Loading failsafeEBDA is big, kernel setup stack overlaps LILO second stage."
Machine of course hangs there.
This is SUSE 10.3 installation that worked fine until (perhaps) the boot loader read info on (or tried to boot) a NTFS USB external drive left on by mistake.
Distro is located on a 320 GB serial drive, three partitions 2 GB swap ,20 GB root and the rest home partition.
Any ideas as to how to correct this?. Thanks in advance.
Well...yes..I had the opt' to install grub but the reason to install LILO in the first place was that I had so many incidents like this with grub, that I felt like trying something new.
It's amazing that the boot loader get so confused after a minor change to the available hardware, in particular, when it's not even part of the booting sequence.
In the past, under grub I fiddled with menu.lst and device.map to no avail. I tried booting off the (internet install) CD and was looking for a way to install a different boot loader to force the system to recognize all drives again, but no such option became available.
Will try what has been suggested (with my fingers crossed...).
Well... in lilo, you are expected to rerun lilo each time you change something important.
The only reason the bootloader would attempt to read the external drive is if you told it to look for the /boot partition there. Did you?
This dosn't faze grub, you just have to edit menu.lst to show the correct drive. Suspect your problem in in front of the kbd - these configs can be confusing. Perhaps you could use a few pointers?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.