Bug 2591 - need summary
need summary
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: lilo (Show other bugs)
6.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-05-06 03:32 EDT by xintian
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:
Environment:
Last Closed: 1999-05-11 14:28:49 EDT
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 xintian 1999-05-06 03:32:04 EDT
Lilo seems to have some problems with the "append" command
in /etc/lilo.conf.

The machine has 1GB RAM on board, which causes the kernel
panic. I have to specify "mem=1000m" to the kernel.

When I manually type "linux mem=1000m" at the lilo prompt,
everything works fine. However, if I use the following
/etc/lilo.conf and run lilo to install the loader. The
kernel panic remains as if I've done nothing.

boot=/dev/sda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
append="mem=1000m"
image=/boot/vmlinuz-2.2.5-15smp
        label=linux
        root=/dev/sda2
        initrd=/boot/initrd-2.2.5-15smp.img
        read-only
image=/boot/vmlinuz-2.2.5-15
        label=linux-up
        root=/dev/sda2
        initrd=/boot/initrd-2.2.5-15.img
        read-only
Comment 1 xintian 1999-05-06 20:28:59 EDT
Just let you know, it's working this morning. I am quite confused
at this time. Maybe it's because of my mistake. Sorry.
Comment 2 Michael K. Johnson 1999-05-11 14:28:59 EDT
Unless it happens again, we'll assume that you accidentally
forgot to run lilo after modifying lilo.conf -- something that
has happened to most of us.  :-)

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