Slack 10: Lilo not booting Windows (though 9.1 did!)
SlackwareThis Forum is for the discussion of Slackware 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.
Slack 10: Lilo not booting Windows (though 9.1 did!)
I upgrade one of my machines from Slackware 9.1 to 10.0, and everything is working just fine. However, I can't boot into Windows anymore, no matter what I try to do!
hda1 - swap
hda2 - slackware10
hda3 - windows
When I installed Slackware 10, I formatted the hda2 partition (with slackware 9.1 on it) with the install program, and used it as my root partition. And although Windows is not on the first partition, it worked just fine with Lilo before. After selecting Windows in Lilo, the machine hangs straight away on a black screen.
Reading other posts in this forum let me to believe it is either a Slack10 specific problem, or has got something to do with the 2.6.7 kernel Slack10 allows you to chose from. Nevertheless, the posted solutions either do not apply (I tried 'boot-as=0x80', but this is clearly intended for machines with multiple hard-disk on them), or do not work (removing the 'table = /dev/hda' line) and Googling did not reveal any useful information.
Here is the relevant section of my lilo.conf, which is exactly the same as the working one I had for Slackware 9.1.
other = /dev/hda3
label = Windows2000
table = /dev/hda
Using 'lilo -v' at the command line reveals no different information than on my similarly configured (and working!) Slackware 9.1 & Windows 2000 notebook.
*** SOLVED *** SEE BELOW ***
Last edited by arnostienen; 07-18-2004 at 03:37 AM.
I realize this is not overly helpful to you but Slack 10 (with 2.6.7) dual boots into Windows XP for me fine. This is probably not the issue/solution but on your working laptop is hda3 marked as a bootable partition? How about the one that is not working? There is also the issue that some (particularly RedHat users) suffered with 2.6.x, I remember it was not disto specific but not what the problem was.
Thanks for the suggestions, but removing 'table=/dev/hda' nor adding 'master-boot' or the likes changed anything. Do note that due to the order of installation, my working with Slack 9.1 notebook has it's Windows partition on /dev/hda1, whereas the non-working workstation with Slack 10 has got it on /dev/hda3 (but it really used to work just fine with Lilo before).
Initially, both /dev/hda2 en hda3 where bootable, according to cfdisk, but removing this from the hda2 (Slackware) partition made no difference.
I'm currently thinking of either replacing the newer Lilo with the version comming with Slackware 9.1 (is this possible?), or using Grub. But it still bugs me that I can't just get it working with Lilo! There has to be a solution!
One thing that has helped me in the past has been to boot into KDE and in the control panel open the module to edit the lilo bootloader. After entering the root password you will be able to click on an option that will probe for OS's or something similar to that. (forgive me - I'm at work now)
In the past this has added options to my lilo menu that worked whereas the ones that we there after an install did not. I then edited out the menu option that were not bootable.
I installed Grub and got a nice experience out of this, but again, Windows did not boot. Then I though of 'fixing' the Windows partition by using the Windows Setup CD. Like with the boot managers, it just hang on the first screen. So, hardware problem then? I removed one or two cards without getting results...
The I remembered that Slackware 9.1 would not power down the machine after shutdown, and I 'fixed' this for Slackware 10 by enabling ACPI in the BIOS. Surely this could not have been the reason why Windows would not boot anymore... Well, you guessed it. It was. Disabling ACPI again did no harm to Slackware 10, but does allow you to boot to Windows!