From: Chuck Gelm on
<snip>
>
> I have been using versions of a third party boot manager since 1998. It
> occupies the mbr and booted the Dell utility, WinXP, DOS6.22 and Linux
> with lilo installed in the boot = /dev/hda6 superblock and the 2.4.31
> kernel from the Slackware 10.2 package. When I installed the 2.6 kernel
> that wouldnt work because lilo.conf boot = /dev/sda overwrote the 3rd
> party boot manager in the mbr. I could boot linux but cant boot the
> Dell utility, WinXP or DOS6.22. That is why I want lilo in the root
> superblock. Unless I can find some workaround that system will have to
> be replaced.
>
> Do you have WinXP and if so how do you boot it? What about the Dell
> Utility?

Yes. Thus:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
append="hdd=ide-scsi hdc=ide-scsi nousb noparport"
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 999
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# End LILO global section
# Windows bootable partition config begins
other = /dev/sda1
label = Windows
boot-as=0x80
table = /dev/sda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda3
label = Linux
read-only
# Linux bootable partition config ends

No on Dell Utility.

HTH, Chuck

> Thanks for your response,
>
> Bob
From: Grant on
On Mon, 15 Jan 2007 17:23:30 -0600, Robert Rappaport <paperbag(a)cox.net> wrote:

>Hi,
>
>I have a Dell D520 laptop with Slackware 10.2 and a 2.6.19 kernel. This
>laptop and the 2.6 kernel recognize the hard drive as device sda. I
>would like to set /etc/lilo.conf up to boot from the root superblock in
>/dev/sda6 which is my / partition. I have been able to boot with "boot
>= /dev/sda" but when I try "boot = /dev/sda6" I get the message
>"Fatal: raid_setup: stat ( "/dev/sda6" )". I have "root = /dev/sda6"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Error message generated while checking boot= option, gets thrown if
lilo cannot reference the given boot= option, or, if the device node
is missing. The latter just bit me ;) Dunno if this helps...

Grant.
--
http://bugsplatter.mine.nu/
First  |  Prev  | 
Pages: 1 2
Prev: 2.6.19.2 Kernel Headers
Next: Compiz on Slackware