LinuxQuestions.org
Register a domain and help support LQ
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 05-05-2012, 09:35 PM   #1
leeeoooooo
Member
 
Registered: Jan 2009
Distribution: Slackware 14.1 (current)
Posts: 108

Rep: Reputation: 18
lilo: Setup length exceeds 63 maximum;


Well,

I finally put together an initrd to run the generic kernel on this eeepc. ('testing' with huge has exceeded all expectations).

I've done this on other systems with no problem, but this time, when I try to add the initrd.gz as an additional boot option, lilo tells me "Fatal: Setup length exceeds 63 maximum; kernel setup will overwrite boot loader."

I've tried reducing the additional modules to just ext4, but I get the same thing.

This error isn't mentioned in the lilo docs, and the message threads I read here seem to have a lot of theories, but no solutions besides "install GRUB." Surely I don't need to go that far.
 
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 05-05-2012, 09:46 PM   #2
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Rep: Reputation: 147Reputation: 147
Upgrade LILO.
 
Old 05-06-2012, 02:49 AM   #3
hua
Member
 
Registered: Oct 2006
Location: Slovak Republic
Distribution: Slackware 14.0, 14.1, current
Posts: 416

Rep: Reputation: 52
Quote:
Originally Posted by leeeoooooo View Post
Well,

I finally put together an initrd to run the generic kernel on this eeepc. ('testing' with huge has exceeded all expectations).
...
Whith initrd you always use the generic kernel and not the huge. Huge kernel should not be used with initrd.
The difference between the two kernel images is that the huge kernel has lot of built in kernel modules as a part of the kernel. In contrast with generic which doesn't have and in initrd you specify which kernel modules you need to load into the kernel.
Actually this is the reason why the huge kernel is "bigger" and the lilo reports it.
Anyway I think that the modules that you are trying to load in initrd are already built into the huge kernel.
 
Old 05-06-2012, 05:53 AM   #4
AlleyTrotter
Member
 
Registered: Jun 2002
Location: Coal Township PA
Distribution: Slackware64-14.1 (4.2.0) UEFI enabled
Posts: 379

Rep: Reputation: 79
say again; upgrade lilo

Quote:
Originally Posted by guanx View Post
Upgrade LILO.
guanx is correct
I had this same problem. Upgrading to the 'lilo' in current fixed it.

john
 
Old 05-06-2012, 08:09 AM   #5
leeeoooooo
Member
 
Registered: Jan 2009
Distribution: Slackware 14.1 (current)
Posts: 108

Original Poster
Rep: Reputation: 18
I've been 'testing' with huge.
Now I'm setting up an initrd to run with generic.

I'm running current. Don't I already have the newest lilo? 23.2

Last edited by leeeoooooo; 05-06-2012 at 08:13 AM.
 
Old 05-06-2012, 12:09 PM   #6
leeeoooooo
Member
 
Registered: Jan 2009
Distribution: Slackware 14.1 (current)
Posts: 108

Original Poster
Rep: Reputation: 18
mkinitrd_command_generator.sh recommended:

mkinitrd -c -k 3.2.13-smp -f ext4 -r /dev/sda1 -m usb-storage:ehci-hcd:uhci-hcd:jbd2:mbcache:ext4 -u -o /boot/initrd.gz

When I tried to set up the resulting initrd.gz in lilo, it gagged with the error:

"Fatal: Setup length exceeds 63 maximum; kernel setup will overwrite boot loader."

I renamed the first initrd-tree to initrd1-tree and tried again:

mkinitrd -c -k 3.2.13-smp -m ext4 -u -o /boot/initrd.gz

...hoping for a slightly smaller output. Same result.

shall I just give up and stick with huge and all those extras that I just don't need?
 
Old 05-06-2012, 01:22 PM   #7
wadsworth
Member
 
Registered: Aug 2007
Distribution: Slackware64 13.37
Posts: 215

Rep: Reputation: 65
Would using the "large-memory" option in lilo.conf make any difference here?
 
Old 05-06-2012, 02:50 PM   #8
leeeoooooo
Member
 
Registered: Jan 2009
Distribution: Slackware 14.1 (current)
Posts: 108

Original Poster
Rep: Reputation: 18
I didn't find any reference to "large-memory" in the lilo docs or man page, but I found an example in the forums here.

No difference.

Thanks anyway...

Last edited by leeeoooooo; 05-06-2012 at 02:51 PM.
 
Old 05-06-2012, 03:49 PM   #9
XGizzmo
Member
 
Registered: Mar 2007
Distribution: Slackware
Posts: 264

Rep: Reputation: 68
It still sounds like you are loading an initrd with a huge kernel. Show the output of ls -l /boot/vmlinuz* and show us your lilo.conf.
 
Old 05-08-2012, 07:06 AM   #10
leeeoooooo
Member
 
Registered: Jan 2009
Distribution: Slackware 14.1 (current)
Posts: 108

Original Poster
Rep: Reputation: 18
I wiped my initrd-tree and rebuilt to be sure.

No difference.

Here are my vmlinuzes:

Quote:
lrwxrwxrwx 1 root root 30 May 7 19:05 vmlinuz -> vmlinuz-generic-smp-3.2.13-smp
-rw-r--r-- 1 root root 3034896 Mar 23 23:22 vmlinuz-generic-smp-3.2.13-smp
-rw-r--r-- 1 root root 6134240 Mar 24 04:02 vmlinuz-huge-smp-3.2.13-smp
lrwxrwxrwx 1 root root 27 Apr 28 21:55 vmlinuz1 -> vmlinuz-huge-smp-3.2.13-smp
 
Old 05-08-2012, 10:23 AM   #11
zakame
Member
 
Registered: Apr 2012
Distribution: Debian, Ubuntu, Slackware
Posts: 156

Rep: Reputation: 63
What EeePC are you using? I ran into a similar issue with my Asus 1215B, but it only occurred once, when I built my first 3.3.4 kernel for my then-13.37 install(basing off config-huge-2.6.37.6.) I rebuilt my kernel later using config-generic-3.2.13 from -current and the LILO problem went away.
 
Old 05-09-2012, 01:47 AM   #12
hua
Member
 
Registered: Oct 2006
Location: Slovak Republic
Distribution: Slackware 14.0, 14.1, current
Posts: 416

Rep: Reputation: 52
Just use this in lilo.
Code:
...
image = /boot/vmlinuz-generic-smp-3.2.13-smp
initrd = /boot/initrd.gz
...
image = /boot/vmlinuz is good too, but the link must point to the correct image - this sometimes can mess up. (And point to different image as we expected)
(Best help for us to help you is to post your lilo.conf - /etc/lilo.conf)

Last edited by hua; 05-09-2012 at 01:51 AM.
 
Old 05-09-2012, 02:31 AM   #13
wildwizard
Member
 
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 838

Rep: Reputation: 257Reputation: 257Reputation: 257
Quote:
Originally Posted by XGizzmo View Post
It still sounds like you are loading an initrd with a huge kernel. Show the output of ls -l /boot/vmlinuz* and show us your lilo.conf.
Hmm some testing here and there is no difference in the sector count between the generic and huge kernel in Slackware despite the kernel image for huge been double that of the generic image.

Code:
Boot image: /boot/vmlinuz-generic-3.2.13
Setup length is 32 sectors.
Compaction removed 6042 BIOS calls.
Mapped 6172 sectors.
Mapping RAM disk /boot/initrd-3.2.13.gz
Compaction removed 6095 BIOS calls.
RAM disk: 6192 sectors.
The initial RAM disk will be loaded in the high memory above 16M.
Added Linux  +  *

Boot image: /boot/vmlinuz-huge-3.2.13
Setup length is 32 sectors.
Compaction removed 12030 BIOS calls.
Mapped 12256 sectors.
Mapping RAM disk /boot/initrd-3.2.13.gz
Compaction removed 6095 BIOS calls.
RAM disk: 6192 sectors.
The initial RAM disk will be loaded in the high memory above 16M.
Added Linux-huge  +
 
2 members found this post helpful.
Old 05-09-2012, 08:36 PM   #14
leeeoooooo
Member
 
Registered: Jan 2009
Distribution: Slackware 14.1 (current)
Posts: 108

Original Poster
Rep: Reputation: 18
Quote:
Originally Posted by hua View Post
Just use this in lilo.
Code:
...
image = /boot/vmlinuz-generic-smp-3.2.13-smp
initrd = /boot/initrd.gz
...
image = /boot/vmlinuz is good too, but the link must point to the correct image - this sometimes can mess up. (And point to different image as we expected)
(Best help for us to help you is to post your lilo.conf - /etc/lilo.conf)
THAT solved the problem! I used /boot/vmlinuz because I'm confident about the link.

The cryptic error did not show itself. Lilo updated successfully. Now I have to work on getting it to mount my SDD card on boot -- my next project.


For the record, this is an Asus Eeepc 2G Surf. Xandros was messed up when I got it, so for the first couple of weeks I ran an extremely cut down 13.37 on the 2G internal SDD 'HD' (no KDE, no CD stuff, no printing, no server, the barest bit of X), mostly just to prove it could be done.

I kept finding features I missed and it didn't leave me much free space (I was constantly trimming logs to free up space).

My solution was a *full* install, with a 16G SDD card mounted as /usr. This works really well, and leaves me lots of space for books and tunes and videos.

I couldn't find a driver for my new plug-in extension wi-fi antenna, so I upgraded to current and now everything works just fine.

I now take this little thing with me *everywhere* (it fits in my jacket pocket!) and use it for everything.
 
  


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
Error 18 : Selected cylinder exceeds maximum supported by BIOS Jakepal Linux - Newbie 3 09-20-2011 03:55 PM
Error 18: Selected cylinder exceeds maximum supported by BIOS brjoon1021 Linux - General 2 04-07-2008 03:37 PM
grub error 18: selected cylinder exceeds maximum supported by bios raport Linux - General 3 05-10-2007 01:55 AM
new kernel causes lilo crash; /sbin/lilo = Warning: device 0x0305 exceeds 1024 cylind dandysf Linux - Software 0 08-26-2003 04:50 PM
Triple boot cylinder exceeds maximum supported by the bios wlfdgcrkz Linux - Software 1 06-15-2003 11:14 PM


All times are GMT -5. The time now is 11:45 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration