Bug 54818 - lilo can't install 2.2.19-6.2.10smp.i686 on RedHat 6.2
lilo can't install 2.2.19-6.2.10smp.i686 on RedHat 6.2
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
6.2
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brock Organ
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-10-19 14:16 EDT by Need Real Name
Modified: 2007-03-26 23:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-10-19 14:16:33 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 Need Real Name 2001-10-19 14:16:29 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.2-2 i686)

Description of problem:
I have installed kernel-smp-2.2.19-6.2.10smp.i686 on my dual PIII.  
My lilo config looks like this

image=/boot/vmlinux-2.2.19-6.2.10smp
        label=linux
        initrd=/boot/initrd-2.2.19-6.2.10smp.img
        read-only
        root=/dev/rd/c0d0p1
        append="mem=512M"

initrd consists of the DAC960 module but doesnt seem to change the result
if I comment it out.

This is what I get when I try to install

[root@limbo ~]# lilo
Kernel /boot/vmlinux-2.2.19-6.2.10smp is too big
[root@limbo ~]# ls -l /boot/vmlinuz-2.2.19-6.2.10smp
-rw-r--r--    1 root     root       672416 Oct  9 09:21
/boot/vmlinuz-2.2.19-6.2.10smp

Help my machine is vulnerable!

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1) install kernel-smp-2.2.19-6.2.10
2) add /boot/vmlinuz-2.2.19-6.2.10smp to lilo.conf
3) run lilo


Actual Results:  lilo failed to install b/c the kernel image was too large.

Expected Results:  the kernel should have installed

Additional info:

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