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 made the mistake of trying out Mint and it installed grub on my mbr, now I have installed Slack 14.2 but lilo won't overwrite grub and I can't boot except from the DVD install disk. Let me make it clear I want Lilo and not grub so there is no point in saying "use grub it's better." I have never in over 20 years had a problem with Lilo and I have had nothing BUT problems trying to use grub.
I have already tried to use DD to wipe the MBR off, I have tried several times running lilo but every time I reboot all I get is a grub error and I can't boot.
This error began after I installed Slack and I DID NOT run lilo during the installation, I was going to try and use grub instead and even though I did not run lilo upon installation of Slack, as soon as I rebooted grub errored out.
What did your dd command look like?
AFAIK, you'd need to use something like
Code:
dd if=/dev/zero of=/dev/sda
as opposed to /dev/sda1 for example.
This method has never failed for me when attempting to remove malingering boot code.
The dd only needs to run for about 30 seconds.
EDIT!
________the above will be destructive and require a re-install. As for simply removing GRUB and using LILO while preserving your installation I have no idea :-(
What did your dd command look like?
AFAIK, you'd need to use something like
Code:
dd if=/dev/zero of=/dev/sda
as opposed to /dev/sda1 for example.
This method has never failed for me when attempting to remove malingering boot code.
The dd only needs to run for about 30 seconds.
EDIT!
________the above will be destructive and require a re-install. As for simply removing GRUB and using LILO while preserving your installation I have no idea :-(
I used this "dd if=/dev/zero of=/dev/sda bs=446 count=1" The first 446 bytes is the Bootstrap.
Have you logged in to a terminal as the root user and run liloconfig? You should see the same options you do with a Lilo install during the OS installation including the install to MBR option. What exactly happens? There should be no need to overwrite the Grub code as installing Lilo to the MBR will do that. If you've been using Lilo that long I expect you are familiar with the expert option?
LILO should install it's information to the mbr overwriting Grub's without incident, unless you were doing so from a non-root account.
Truth be told, Grub is a more feature-filled bootloader, but Mint is a strange distribution, and often they do things that don't make sense, but you should not be locked out of assigning the mbr.
The question I would ask is, when you ran liloconfig, did you install LILO to the superblock, mbr, or a bootdisk?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.