lilo problem - kernel too big - not!

lilo problem - kernel too big - not!

Post by jmgal.. » Sat, 07 Oct 2000 13:35:13



I can't get lilo to write a new boot sector. The error comes back
'kernel too big'. This kernel is not extremely large, and lilo has
booted larger images for me before. This IS a bzImage.


LILO version 21, Copyright 1992-1998 Werner Almesberger

Reading boot sector from /dev/sda
Merging with /boot/boot.b
Secondary loader: 8 sectors.
Boot image: /boot/vmlinuz-2.2.14-vpnmasq
Setup length is 7 sectors.
Kernel /boot/vmlinuz-2.2.14-vpnmasq is too big
Removed temporary file /boot/map~


total 1561
lrwxrwxrwx   1 root     root           25 Oct  5 20:45 System.map ->
System.map-2.2.14-vpnmasq
-rw-r--r--   1 root     root       150327 Feb 11  2000 System.map-2.2.14
-rw-r--r--   1 root     root       151541 Oct  5 19:21
System.map-2.2.14-vpnmasq
-rw-r--r--   1 root     root          512 Sep 23  1999 boot.0800
-rw-r--r--   1 root     root          512 Sep 23  1999 boot.0801
-rw-r--r--   1 root     root         4544 Apr 12  1999 boot.b
-rw-r--r--   1 root     root          612 Apr 12  1999 chain.b
-rw-r--r--   1 root     root       278785 Feb 11  2000 initrd-2.2.14.img
-rw-------   1 root     root        44032 Feb 11  2000 map
-rw-r--r--   1 root     root          620 Apr 12  1999 os2_d.b
-rw-r--r--   1 root     root       474569 Feb 11  2000 vmlinuz-2.2.14
-rw-r--r--   1 root     root       475639 Oct  5 19:21
vmlinuz-2.2.14-vpnmasq

boot=/dev/sda
disk=/dev/sda
   bios=0x80
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
image=/boot/vmlinuz-2.2.14-vpnmasq
        label=linux-2.2.14-vpnmasq
        root=/dev/sda1
        initrd=/boot/initrd-2.2.14.img
        read-only
        vga=1
image=/boot/vmlinuz-2.2.14
        label=linux-2.2.14
        root=/dev/sda1
        initrd=/boot/initrd-2.2.14.img
        read-only
        vga=1

Sent via Deja.com http://www.deja.com/
Before you buy.

 
 
 

1. RH6, lilo says kernel too big (but it's not)

RedHat 6.0... after compiling my own kernel with only the _bare_minimum_
(so the answer is not to "make bzImage"), lilo complains that it's too
big.  But it's not... the stock kernel is 617288 bytes, the new kernel
is only 493223 bytes.  What gives?  I'm currently trying to get 2.2.13
but it happens with all other kernels.  Do I need a newer lilo or
something?

TIA... CDR

Sent via Deja.com http://www.deja.com/
Before you buy.

2. Vikram Adve, Friday 12 March 1999: SYSTEMS

3. new kernel: LILO "kernel too big" error

4. What is PERL?

5. WANNABE ISP? READ THIS

6. ServeurX for Matrox Mystic

7. LILO (v.21) problem: kernel too big!

8. Linux v2.0 and LILO v19 (problem: Kernel /zImage is too big)

9. LILO problem: Kernel too big

10. I have a BIG, BIG,BIG problem with DOSEMU 0.98.5.

11. Lilo will not boot on big hard drive