LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 04-21-2005, 03:04 PM   #1
MD3
Member
 
Registered: Apr 2004
Location: Italy
Distribution: Gentoo
Posts: 81

Rep: Reputation: 15
[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
 
Old 04-21-2005, 04:01 PM   #2
xushi
Senior Member
 
Registered: Jun 2003
Location: UK
Distribution: Gentoo
Posts: 1,288

Rep: Reputation: 45
how are you 'reinstalling' lilo? And can we see an output of your lilo.conf ?
 
Old 04-22-2005, 02:10 AM   #3
MD3
Member
 
Registered: Apr 2004
Location: Italy
Distribution: Gentoo
Posts: 81

Original Poster
Rep: Reputation: 15
"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
 
Old 04-22-2005, 09:23 AM   #4
MD3
Member
 
Registered: Apr 2004
Location: Italy
Distribution: Gentoo
Posts: 81

Original Poster
Rep: Reputation: 15
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
 
Old 04-22-2005, 11:55 AM   #5
MD3
Member
 
Registered: Apr 2004
Location: Italy
Distribution: Gentoo
Posts: 81

Original Poster
Rep: Reputation: 15
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
 
Old 04-22-2005, 12:43 PM   #6
linuxhippy
Senior Member
 
Registered: Sep 2004
Location: Philadelphia, PA
Distribution: Xubuntu, Mythbuntu, Lubuntu, Picuntu, Mint 18.1, Debian Jessie
Posts: 1,207

Rep: Reputation: 47
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).
 
Old 04-22-2005, 04:57 PM   #7
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 53
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
 
Old 04-22-2005, 05:31 PM   #8
tormented_one
Member
 
Registered: Oct 2004
Location: Small Town USA
Distribution: slamd64 2.6.12 Slackware 2.4.32 Windows XP x64 pro
Posts: 383

Rep: Reputation: 30
"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
 
Old 04-22-2005, 05:39 PM   #9
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 53
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
 
Old 04-22-2005, 09:37 PM   #10
tormented_one
Member
 
Registered: Oct 2004
Location: Small Town USA
Distribution: slamd64 2.6.12 Slackware 2.4.32 Windows XP x64 pro
Posts: 383

Rep: Reputation: 30
Sorry I agree with you. remove the links and use the vmlinuz from /boot.
 
Old 04-23-2005, 08:25 AM   #11
MD3
Member
 
Registered: Apr 2004
Location: Italy
Distribution: Gentoo
Posts: 81

Original Poster
Rep: Reputation: 15
i managed it

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
 
Old 04-23-2005, 11:16 AM   #12
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 53
i don't think vmlinux is compressed.

egag
 
Old 04-23-2005, 12:29 PM   #13
tormented_one
Member
 
Registered: Oct 2004
Location: Small Town USA
Distribution: slamd64 2.6.12 Slackware 2.4.32 Windows XP x64 pro
Posts: 383

Rep: Reputation: 30
vmlinux is not compessed. vmlinuz is compressed.
 
Old 04-23-2005, 01:08 PM   #14
MD3
Member
 
Registered: Apr 2004
Location: Italy
Distribution: Gentoo
Posts: 81

Original Poster
Rep: Reputation: 15
-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 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?
 
Old 04-23-2005, 03:25 PM   #15
tormented_one
Member
 
Registered: Oct 2004
Location: Small Town USA
Distribution: slamd64 2.6.12 Slackware 2.4.32 Windows XP x64 pro
Posts: 383

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


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel 2.4 in Zipslack (Waring: unable to open an initial console | Kernel Panic...) kurtamos Linux - General 2 05-10-2006 12:58 PM
Kernel upgrade: Unable to handle kernel paging request deviantintegral Debian 4 07-14-2004 04:59 PM
Unable to build NVIDIA kernel module / determin kernel version Night Ink Fedora 2 05-31-2004 04:54 PM
Strange kernel error: "Unable to handle kernel NULL pointer dereference..." EcceVery Debian 4 04-12-2004 06:34 AM
Kernel Message:unable to handle kernel NULL pointer dereference at virtual address... dave_d Linux - General 0 02-14-2001 05:01 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:41 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration