Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Distribution: Fedora, Debian, OpenSuSE and Android
Posts: 1,820
Rep:
I think XP has a similar utility on it's install disk, under repair. You will have to reinstall lilo after it repairs the ntloader, but that shouldn't be to tough.
The way I understand it at Lilo the system either:
A. Loads the Linux kernel selected or
B. Hands off boot responsibility to ntloader.
Thanks, I'll have to find that disk soon. I just don't get it. When one thing gets fixed, another thing goes wrong. When I first installed Slack on my 1.7ghz machine, it could have LILO boot into Windows, but it only saw my 40gb hard drive that Linux was on was only 4 GB. Now it sees the 40 GB, but I can't boot into Windows.... If I can't find that XP disk, I guess I'll have to use another Windows computer to make the boot disks for the broken machine.
I just don't get what's wrong with my setup
my boot section for lilo is:
other = /dev/hda2
label = WindowsXP
table = /dev/hda
Distribution: Fedora, Debian, OpenSuSE and Android
Posts: 1,820
Rep:
Not sure about lilo in this case as I use the Grub boot loader. Here is my grub.conf for my system. Maybe it can shed some light on the setup.
default=0
timeout=10
splashimage=(hd0,1)/grub/splash.xpm.gz
title Fedora Core (2.4.22-1.2115.nptl)
root (hd0,1)
kernel /vmlinuz-2.4.22-1.2115.nptl ro root=LABEL=/ rhgb
initrd /initrd-2.4.22-1.2115.nptl.img
title Windows 2000 Pro
rootnoverify (hd0,0)
chainloader +1
title Red Hat Linux 9 (2.4.20-24.9-XN patched)
root (hd0,1)
kernel /vmlinuz-2.4.20-24.9-XN ro root=/dev/hdc1
r_jensen - can you post your entire lilo.conf file? I don't think the problem is with your MBR or anything else, but rather that you've just labelled something incorrectly in lilo. I mean, the issue is simply that your PC can boot into Linux, but if you try to boot into Windows you get an error, correct? -- J.W.
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hde
#compact # faster, but won't work on all systems.
prompt
timeout = 100
# VESA framebuffer console @ 1024x768x32k
# vga = 790
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# DOS bootable partition config begins
image = /boot/vmlinuz-2.6.5
root = /dev/hde3
label = Linux-2.6.5
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# DOS bootable partition config ends
# Linux bootable partition config begins
other = /dev/hda2
label = dos
table = /dev/hda
#image = /boot/vmlinuz-2.4.22
# root = /dev/hde3
# label = Linux-2.4.22
# read-only
# Linux bootable partition config ends
And JW, I don't get any errors, that's the thing, it just hangs....
One odd thing is, though, that when I changed it from /dev/hda2 to /dev/hda1, /dev/hda1 showed up in cfdisk, whereas it was hidden before. I'm all confused about this.... If I have to, I'll ask my dad to put in the administrator's password (why does XP have to have that for install?) so that I can run fdisk /mbr, and then just either switch which mbr the computer searches for via bios (hda vs hde). This is all LILO's "smart" mode's fault, where it automates everything if you hit enter one too many times because the system's lagging and you don't know if you hit enter or not!
I guess everything's solved for the moment, now. Although I don't have it set up how I'd like it to be (windows's bootloader on hda's MBR and LILO on hde's MBR), both operating systems work!
I don't know what did it, but I'm taking a guess. I was really worried last night when I went to bed (feared facing family wrath), and that's when I remembered that I flagged /dev/hde3 as bootable. It might be because I had /dev/hda2 and /dev/hde3 flagged as bootable, and I only flagged /dev/hde3 bootable somewhere between my first Slack install and my second on this comuter (cfdisk complained about how there weren't any bootable partitions on the drive). SO I unflagged /dev/hde3 as bootable, and now it boots into XP or Linux, and XP runs how it used to. Thanks for the suggestions.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.