Re: Lilo Boot Problems with 1.7GHZ P4 HP Pavillion
The append line is for the kernel only, it has nothing to do with the lilo configuration.
The CRC error is strange, though you could try the "compact" statement instead of "linear" or "lba32".
Re: lilo help with rh7.1 and winME
The way you used to install all of this baffled my quite a bit. Nevertheless, from the information you provided I like to conclude/answer several things:
> and here is the error message i get
> when i run the /sbin/lio program:
> Warning: /etc/lilo.conf should be
> writeable only for root
> Warning: LBA32 addressing assumed
> Warning: COMPACT may conflict with
> LBA32 on some systems.
> Added linux *
> Device 0x0300: Invalid partition
> table, 3rd entry
> 3d address: 1/0/0/ (0)
> Linear address: 1/0/1024 (1032192)
The partition table DiskDruid made for you is totally wrong! Lilo actually starts complainting because the third partition is partially covering the fourth and fifth partition! This results in the bailing out of Lilo on the "DOS" partition.
> finally, here's my fdisk -l info
> (partition table information):
> Device Boot Start End Blocks ID System
> /dev/hda1 1 102 51376+ 83 Linux
> /dev/hda2 103 58168 29265264
> 5 Extended
> /dev/hda3 * 1025 21342 10240272
> c Win95 FAT32 (LBA)
> /dev/hda5 20421 20681 131512+ 82 Linux
> /dev/hda6 20682 58168 18893416+
> 83 Linux
> /dev/hda1 is boot partition at about
> /dev/hda3 is my windows partition at
> /dev/hda5 is my linux swap partition
> at 256MB (I think)
> /dev/hda6 is my / directory.
If this problem is corrected you can select which OS to boot by default, this is _different_ from which partition to boot first! The star fdisk shows, is the bootable partition, in contrast, the star of Lilo is the OS to boot by default. There's a huge difference between those two. NOTE: your swap is 131512 KBytes which is in fact around 128 MB ...
The 'easiest way' to create a dual-boot system is:
1. Partition your harddisk. Create _all_ needed partitions, so think first, act later (hmmm, did I say that?)
2. Install Windows on its destined partition,
3. Install Linux and Lilo.
lilo help with rh7.1 and winME
i am trying to make lilo boot both winME and redhat linux 7.1. i have installed them in this order:
- disk druid on the rh7.1 cd to partition the /boot (at 50 MB) and / (filling up the rest of the disk, about 28 GB)
- fdisk from the dos prompt on the winME install disk to partition a windows fat32 filesystem at 10GB, and install windows. booted up into windows, and it worked.
- went back to disk druid on the rh7.1 install cd. i redefined mount points (these are not stored in the partition table), and saw that what once was a 28GB partition on /, was now 18GB; which is exactly what I thought should happen.
- installed linux, and booted up. everything was fine, but I could not get linux to load the windows partition.
so now I am in linux and can boot linux fine. lilo, however, wont even recognize that I have a windows to boot up, *even though I have it in my lilo.conf file*!! when I type "dos" at the boot prompt, it tells me that it cannot even see that there is a dos to be loaded. here's /etc/lilo.conf:
# LILO configuration created by QuickInst 21 Mon Nov 5 03:46:05 CST 2001
boot = /dev/hda
delay = 50 # optional, for systems that boot very quickly
vga = normal # force sane state
root = current # use "current" root
image = /boot/vmlinuz
label = linux
other = /dev/hda3
table = /dev/hda
label = dos
and here is the error message i get when i run the /sbin/lio program:
Warning: /etc/lilo.conf should be writeable only for root
Warning: LBA32 addressing assumed
Warning: COMPACT may conflict with LBA32 on some systems.
Added linux *
Device 0x0300: Invalid partition table, 3rd entry
3d address: 1/0/0/ (0)
Linear address: 1/0/1024 (1032192)
finally, here's my fdisk -l info (partition table information):
Device Boot Start End Blocks ID System
/dev/hda1 1 102 51376+ 83 Linux
/dev/hda2 103 58168 29265264 5 Extended
/dev/hda3 * 1025 21342 10240272 c Win95 FAT32 (LBA)
/dev/hda5 20421 20681 131512+ 82 Linux swap
/dev/hda6 20682 58168 18893416+ 83 Linux
/dev/hda1 is boot partition at about 50MB
/dev/hda3 is my windows partition at 10GB
/dev/hda5 is my linux swap partition at 256MB (I think)
/dev/hda6 is my / directory.
so, answer me this:
why must it say "added linux * " _every time_ that I start lilo, and yet the winME partition still is the one with the * to activate it?
actually, that's not really the important question :)... I just thought it might be a helpful one. the most important question is: how to i get lilo to load linux _and_ windows?
it has been conjectured that since I did the partitioning in a weird order, the part that I should be booting from on /boot is actually on the windows partition. is this the case?
thanx in advance for any help
Re: Graphical Lilo
> I have noticed that some Linux
> Distributions are starting to add a
> graphical component to lilo (VGA mode).
> I have particularly noticed this on
> Redhat 7 and Corel Linux.
> It would be great if such a feature
> could be introduced to the mainstream
> distribution of Lilo, in the form of a
> patch, OR directly embedded into the
> current code.
Mandrake unfortunately does this too, and there
really isn't a choice. You CAN choose a "Text"
Lilo, but it's not completely "Text" becuase it
Yes, I think it is a bad thing, mostly because
they kicked the original Lilo alltogether. :(
You can make the original Lilo look pretty cool,
acutally. You can edit the file /boot/message
and put your own ASCII art in there, or perhaps
some ASCII art you got off the net.
This is also a good way to hide your boot options,
if you don't want other people snooping around
in your non-default OS.
It all depends on your personal preferences, I guess.
I happen to like the text Lilo alot better, for the above
Just my Two Cents.
Lilo Boot Problems with 1.7GHZ P4 HP Pavillion
I get a CRC mismatch error if I specify a kernel Image to boot. The kernel is actually fine since if I let the LILO timeout expire, the kernel boots perfectly. This is with versions 21.4.4-13 and 22.0.2. RedHat 7.1. And 80 GB IDE drive. Here is the lilo.conf file:
The hdc=ide-scsi doesn't seem to matter. Nor does using linear mode.
Catastrophic bug in ALPHA and BETA release of 22.1
A catastrophic bug has been found in the following alpha and beta codes:
lilo-22.1-beta6 -- latest as of 10/25/2001
The tarballs to these were posted on the developer's (my) site at:
They have now been removed.
lilo-22.1-alpha3 and earlier do not have the bug.
The bug involves writing more than the boot loader to the boot sector. This trashes the first partition table entry, with disastrous results.
I need some help here !
I just installed my RedHat Linux 6.0 in my PC. But the LILO come with the package unable to detect my /boot partition. Now I downloaded LILO 22.0.2 from here. But .. I don't know how to install in into my Linux. Can anyone help me? Thank you.
My E-mail: email@example.com (mailto:firstname.lastname@example.org)
Version 22 beta (08-Aug-2001)
The version 22 beta test codes were updated 08-Aug-2001. The previous update to the beta test version was 23-Jun-2001. Updates affect only RAID installation on a RAID array running in degraded mode (not all disks on-line).
Re: Compilation problems
> Has anyone gotten this 21.5 version to
> compile? Every as86-related line throws
> up errors, (I have bin86-0.4), but after
> I re-tried 3 or 4 times, (very "DOS" of
> me!), it seemed to work, but my machine
> now won't boot properly, and throws up
> "Unexpected EOF" errors. Any ideas
Hi. If you didn't do so already, go grab & build the latest bin86 tools (search on freshmeat!); I had the same problem but the new bin86 tools fixed it.
you can download a patch for lilo at http://www.linuxnews.ch/alfs/
An open, cross-platform journaling program.
A scientific plotting package.