Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 10391 - Installer removes necessary LILO options
Installer removes necessary LILO options
Status: CLOSED DUPLICATE of bug 10390
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Erik Troan
Depends On:
  Show dependency treegraph
Reported: 2000-03-28 10:46 EST by Rob Russell
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-04-24 08:42:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rob Russell 2000-03-28 10:46:03 EST
I did an upgrade from CD of a 6.1 installation to 6.2.  The video card was
an ATI XPert99 (Rage 128), so I was using XF86_FBDev and I had a VGA=791
line in lilo.conf.

The installer correctly upgraded XF86_FBDev, but reinstalled LILO without
the VGA=791 line.  The machine came up and kept tyring to start the X
Server unsucessfully.

The installer should pay very careful attention to /etc/lilo.conf for
things like this, as well as other things like boot passwords.

At the LILO: prompt, type "linux 3" to bring the system up in text mode.
Log in as root, run "setup" and choose X Configuration.  It will then
detect the video card and install the correct XServer, and no longer need
the framebuffer.  Type "init 5" to bring the machine all of the way up.
Comment 1 Jay Turner 2000-04-24 08:42:59 EDT
The old lilo.conf is backed up to lilo.conf.rpmsave, so you can always flip over
at the end of the installation and make the appropriate changes.  We should have
this resolved in the next cut of the installer.

*** This bug has been marked as a duplicate of 10390 ***

Note You need to log in before you can comment on or make changes to this bug.