We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Don't worry about him, that user no longer uses Launchpad (thankfully).
This isn't a hardware error, it is an obvious bug in lilo auto
configuration. Can you reproduce this problem in Jaunty? Thank you.
** Changed in: lilo (Ubuntu)
Importance: Undecided => High
** Changed in: lilo (Ubuntu)
I agree, how can something like a missing option be a hardware error?
It's a hardware detection error and I guess more steps are needed in
that hardware detection in order for lilo.conf to be complete.
Maybe there should be three modes for LILO (or bootloader in general)
installation: "Novice" mod
Excuse me?
How can it be a hardware error that certain things are missing from
lilo.conf
Also how can anything be a hardware error that you are able to fix with
specifying an option to a hardware???
** Changed in: lilo (Ubuntu)
Status: Fix Released => New
--
Default /etc/lilo.conf
this is not a bug , this is a hardware error
** Changed in: lilo (Ubuntu)
Status: New => Fix Released
--
Default /etc/lilo.conf options not optimal
https://bugs.launchpad.net/bugs/125737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
The option large-memory is also gravely needed on recent installs. Its omission
from lilo.conf prevents the newly installed 8.04.1 server from booting on amd64
arch.
Even better, provide a way to edit the lilo.conf before lilo is written
to the target place.
--
Default /etc/lilo.conf options
