LinuxQuestions.org - Problems with updating LILO for a kernel recompile..

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Problems with updating LILO for a kernel recompile.. (https://www.linuxquestions.org/questions/slackware-14/problems-with-updating-lilo-for-a-kernel-recompile-299170/)

Problems with updating LILO for a kernel recompile..

I just wiped and reloaded my machine - I've got Windows on a 160GB HD as primary-master, and Linux on a 200GB HD as primary slave. I use XOSL as my bootloader, and have LILO loaded on the root partition.

I installed Slackware 10.1 and got everything running hunky doory.

Anyway, I downloaded the 2.6.7 source and proceeded to update my lilo.conf..

Now, after changing my lilo.conf to this:

Code:

# LILO configuration file

# generated by 'liloconfig'

#

# Start LILO global section

boot = /dev/hdb1

#compact        # faster, but won't work on all systems.

prompt

timeout = 50

# VESA framebuffer console @ 1024x768x256

vga = 773

# 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

# Linux bootable partition config begins

image = /boot/vmlinuz

  root = /dev/hdb1

  label = 2.6.7

  read-only # Non-UMSDOS filesystems should be mounted read-only for checking

image = /boot/vmlinuz.old

  root = /dev/hdb1

  label = 2.4.29

  read-only

# Linux bootable partition config ends

I would run lilo, and get this

Quote:

Reference: disk "/dev/hda" (3,0) 0300

LILO wants to assign a new Volume ID to this disk drive. However, changing
the Volume ID of a Windows NT, 2000, or XP boot disk is a fatal Windows error.
This caution does not apply to Windows 95 or 98, or to NT data disks.

Is the above disk an NT boot disk? [Y/n]Y
Aborting ...

I obviously can't recompile until I get this working. What is going wrong?

you said you have a Windows partition, but it's not in your lilo.conf, i think, but im not sure, you need to add something like this, some how got erased

other = /dev/hda1
label = Windows
table = /dev/hda
# Windows bootable partition config ends

change "/dev/hda" to where ever its you Windows partition, but again, im *not* sure if this is the problem

I don't really have any desire to boot Windows from Linux - I have XOSL to handle that. I'll look into it, though.

*edit* nope, that didn't fix it.

maybe try to unplug the hda, reboot and install lilo....

egag

Quote:

Originally posted by egag
maybe try to unplug the hda, reboot and install lilo....

egag

If it comes down to it I'll try that, but I've never had to do that before - doesn't make sense that I would have to now.

Update: I redid my Slackware install just to check to make sure I didn't miss anything, and I realized.. I didn't have Windows set up when I installed originally. I tried to go through the install of Lilo, and it appeared to hang (however, it was really waiting for me to say Y/N about the drive label issue, even though it didn't prompt me). I hit Y, hit enter, and it moved on. Obviously, LILO isn't installed anymore. Before doing this I tried to download the latest version and install it, however that didn't work either.

So, yeah. Seems like I have a small problem now. I NEED to get my system up and running today, tomorrow afternoon at the very latest. I have work to do, and I need both a Linux and a Windows install up and running quickly and permanently (I'm on spring break - I go back to college Sunday, and won't have time to mess with my system).

I've ran similar configurations for the past 3 years using Slackware and Windows.

:/

You said that linux is primary slave, so I would think it is /dev/hdb isn't it ?

Correct - just as my lilo.conf states.

So why not just run
lilo -b /dev/hdb

That worked, thanks.

Why isn't it reading the boot line from my lilo.conf?

I don't know how XOSL see your bootable partition, if it 'cant boot linux, try at least
lilo -b /dev/hdb1

If it continue to fail on boot linux, see XOSL docs