Bug 925 - LILO won't install
LILO won't install
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: lilo (Show other bugs)
5.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-01-22 17:56 EST by stpyang
Modified: 2016-12-06 12:25 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-02-04 17:24:28 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description stpyang 1999-01-22 17:56:48 EST
I get the following error message:

  Sorry, don't know what to do with device 0x2105

LILO worked on my computer with versions 5.0 and 5.1, but
not 5.2.
Comment 1 David Lawrence 1999-01-22 18:14:59 EST
First, is this happening during an install or is it happening when
you  run lilo from the command line?

Either way we will need to see your /etc/lilo.conf file to try to
replicate your setup.
Comment 2 stpyang 1999-01-23 06:25:59 EST
It happens when I run I run lilo from the command line.
I never got lilo to install in the first place, so I used a boot disk.

Here is my lilo.conf file:

boot=/dev/hde
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
image=/boot/vmlinuz-2.0.36-0.7
        label=linux
        root=/dev/hde1
        read-only
Comment 3 David Lawrence 1999-02-04 17:24:59 EST
Have you moved your drives around since your last version? Lilo will
not work properly with the hde device.

Lilo will only write properly to the first four devices.
hda
hdb
hdc
hdd
Comment 4 openshift-github-bot 2016-12-06 12:25:36 EST
Commit pushed to master at https://github.com/openshift/origin-web-console

https://github.com/openshift/origin-web-console/commit/f697f5017e25cf30e9d5d263568e21c060a6b981
Merge pull request #987 from sg00dwin/pipeline-stage-issue925

Merged by openshift-bot

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