LinuxQuestions.org - [10.0] unable to use kernel 2.6.11

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - [10.0] unable to use kernel 2.6.11 (https://www.linuxquestions.org/questions/slackware-14/%5B10-0%5D-unable-to-use-kernel-2-6-11-a-315798/)

[10.0] unable to use kernel 2.6.11

1) I made sure i had all the tools needed (e.g. the correct version of gcc, binutils, ...)
2) I successfully compiled the kernel
3) I moved it in /boot and linked /boot/vmlinuz to it
4) The kernel size is of about 1.8MB
5) I'm now using a 2.4.26 kernel wich image size is of 2.2MB
6) When re-installing lilo it says: Fatal: Kernel /boot/vmlinuz is too big

how can i solve this problem?

thanks and bye

how are you 'reinstalling' lilo? And can we see an output of your lilo.conf ?

"reinstalling" lilo means executing the "lilo" command.

this is lilo.conf:

Code:

boot = /dev/hda

prompt

bitmap=/boot/bmplilo.bmp

bmp-colors=0,,233,25,,0

bmp-table=12,12

bmp-timer=60,27,233,0

timeout = 1200

change-rules

reset

vga = 773

append="hdc=ide-scsi hdd=ide-scsi"



#win

other = /dev/hdb1

  label = UindosIcspi

  table = /dev/hdb

  map-drive=0x80

  to=0x81

  map-drive=0x81

  to=0x80



#slack

image = /boot/vmlinuz

  root = /dev/hda1

  label = Slackware

  read-only

bye and thanks ;)

here is some news:
i installed centos... theese are the two kernels:

Code:

-rwxr-xr-x  1 root root 1433883 Apr 22 12:53 centos-kernel-2.6.9

-rwxr-xr-x  1 root root 1459880 Apr 22 16:14 slack-kernel-2.6.11

and this is the new lilo.conf:

Code:

boot = /dev/hda

prompt

bitmap=/boot/bmplilo.bmp

bmp-colors=0,,233,25,,0

bmp-table=12,12

bmp-timer=60,27,233,0

timeout = 1200

change-rules

reset

vga = 773

append="hdc=ide-scsi hdd=ide-scsi"



#win

other = /dev/hdb1

  label = UindosIcspi

  table = /dev/hdb

  map-drive=0x80

  to=0x81

  map-drive=0x81

  to=0x80



#centos

image = /boot/vmcentos

  root = /dev/hdb2

  label = CentOS

  read-only



#slack

image = /boot/vmslack

  root = /dev/hda1

  label = Slackware

  read-only

even if the size difference between the two kernels is minimal (25 KB) lilo output is the same:

Code:

Boot other: /dev/hdb1, on /dev/hdb, loader CHAIN

Added UindosIcspi *



Boot image: /boot/vmcentos -> centos-kernel-2.6.9

Added CentOS



Boot image: /boot/vmslack -> slack-kernel-2.6.11

Fatal: Kernel /boot/vmslack is too big

any suggestion? bye & thanks

another thing: LiLo can use kernels bigger than the MBR because it can access kernels on other part of the disk... so, can it be a filesystem-related matter? the fs where the kernels reside is reiserfs.. BUT it has ever worked (and still now work with 2.4.6 k) with reiserfs... dunno^2

2.6 kernels usually need an initrd.img file or initrd.gz file to boot. This will appear as /boot/initrd.gz or /boot/initrd.img if you have it. If not there is a mkinitrd script in Slack. Do a man mkinitrd for specifics (there are module options for your file system).

you don't need an initrd and it's not caused by the file being to big.
you could try to leave out all those symlinks, and use the real filenames in your lilo.conf.

it won't hurt to also delete any symlink in the /boot dir and use the 'normal' naming scheme.
(vmlinuz-2.6.11 ; System.map-2.6.11 ; config-2.6.11 )

egag

"you don't need an initrd"

Well maybe he does, did you compile in support for your filesystem? If not sure, then use:

mkinitrd -c -k 2.6.11 -m reiserfs

Quote:

Originally posted by tormented_one
"you don't need an initrd"

Well maybe he does, did you compile in support for your filesystem? If not sure, then use:

mkinitrd -c -k 2.6.11 -m reiserfs

well...do you think the lack of an initrd
would make lilo give an error " Fatal: Kernel /boot/vmlinuz is too big" ?

don't think so.....

egag

Sorry I agree with you. remove the links and use the vmlinuz from /boot.

i managed it :D

want to know how? just using bzImage instead of vmlinuz ... arch/i386/boot/bzImage has the same size og arch/i386/boot/compressed/vmlinux i used before but LiLo seems to love it!

thank you all very much :)

i don't think vmlinux is compressed.

egag

vmlinux is not compessed. vmlinuz is compressed.

-rw-r--r-- 1 root root 1964506 Apr 23 20:07 bzImage
-rwxr-xr-x 1 root root 1967656 Apr 23 19:31 vmlinux

the difference is minimal :D expecially if you consider the uncompressed one:
-rwxr-xr-x 1 root root 5194991 Apr 23 19:31 vmlinux

maybe tha arch/i386/boot/compressed/vmlinux is the same as the old zImage?

did you make install the kernel? If you do it will give you vmlinuz and not vmlinux, try that.