Re: 2.4.20 is (still) huge

[Emma Jane Hogbin <emmajane@xtrinsic.com>]

On Sun, Apr 13, 2003 at 09:09:59AM +0800, jqdkf@zju.edu.cn wrote:
> maybe you should check out bzImage under ./arch/i386/boot/, that is the
> kernel to boot with

Not me!

from /etc/lilo.conf

default=apr11d-2420
image=/vmlinuz.030411d
        label=apr11d-2420
        read-only

Here are my vmlinux files:
-rw-r--r--    1 root     root         1.1M Jan 22 21:33 vmlinuz.030222
-rwxr-xr-x    1 root     root         3.0M Apr 12 20:16 vmlinuz.030411
-rwxr-xr-x    1 root     root         2.3M Apr 12 20:57 vmlinuz.030411b
-rwxr-xr-x    1 root     root         1.6M Apr 12 21:17 vmlinuz.030411c
-rwxr-xr-x    1 root     root         1.5M Apr 12 21:43 vmlinuz.030411d

The first is a custom 2.4.18 kernel and will boot. The next four are 
2.4.20 kernels and are ALL too big. :(

I get the following errors:
debian:/usr/src/kernel-source-2.4.20# lilo -q
Linux           *
LinuxJan20      
WinNT(hda1)     
(Aren't I supposed to see the new names here?)

debian:/usr/src/kernel-source-2.4.20# lilo
Fatal: Kernel /vmlinuz.030411d is too big

*everything* I can find in the kernel that can be switched to a module 
has been switched to a module and it still won't work. 2.4.20 is required
to get ACPI working (and sound).

emma

-- 
Emma Jane Hogbin
[[ 416 417 2868 ][ www.xtrinsic.com ]]