LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Reply
 
Search this Thread
Old 06-10-2001, 03:16 PM   #1
rdaves@earthlink.net
Member
 
Registered: May 2001
Location: Full-time traveler I live where I am.
Distribution: I use Red Hat V 7.1
Posts: 297

Rep: Reputation: 30

This is my second run at this problem (history is at http://www.linuxquestions.org/questi...hreadid=3109).

After recompiling kernel 2.4 and doing all the 'make' options, I ran 'lilo'. -
I have one problem and three questions:
-
PROBLEM:
When I run lilo, get the following:
-
"Warning: device 0x0306 exceeds 1024 cylinder limit.
Fatal: Sector 51220658 too large for linear mode
(try 'lba32' instead)".
-
Questions:
1.) How do I find out what device 0x0306 is?
2.) How do I find out what is on sector 51220658 and why the system says it is too big?
3.) I am booting from a floppy, which doesn't seem to care
about device 0x0306 or sector 51220658. Why isn't this a problem using a floppy?
Thanks to the guys that helped me the first time around and many thanks for taking another look. Hope I don't seem to be stupid or thankless, but, as yet, I don't understand.
 
Old 06-10-2001, 03:56 PM   #2
mcleodnine
Senior Member
 
Registered: May 2001
Location: Left Coast - Canada
Distribution: s l a c k w a r e
Posts: 2,731

Rep: Reputation: 45
Quote:
Originally posted by rdaves@earthlink.net
This is my second run at this problem (history is at http://www.linuxquestions.org/questi...hreadid=3109).

After recompiling kernel 2.4 and doing all the 'make' options, I ran 'lilo'. -
I have one problem and three questions:
-
PROBLEM:
When I run lilo, get the following:
-
"Warning: device 0x0306 exceeds 1024 cylinder limit.
Fatal: Sector 51220658 too large for linear mode
(try 'lba32' instead)".
-

Can you post your /etc/lilo.conf and /etc/fstab?

Since lilo can't see past the 1024 cylinder limit it can't do it's lilo thing. You can either use extended partitions or use a small partition that is completely under the 1024 cyl limit.

The newer version of lilo is supposed to be able to get over this, but I've never used it so I'm in the dark there.

[Edited by mcleodnine on 06-10-2001 at 05:21 PM]
 
Old 06-10-2001, 04:05 PM   #3
unSpawn
Moderator
 
Registered: May 2001
Posts: 27,492
Blog Entries: 54

Rep: Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910
Cant explain it all but I can add some remarks.
Quote:
1.) How do I find out what device 0x0306 is?
I read 0x03 is /dev/hda and 06 is the sixth partition on /dev/hda.
Quote:
2.) How do I find out what is on sector 51220658 and why the system says it is too big?
Havent seen a complete disk overview and I wont guess. I suggest u change lilo.conf like ure error message said & replace "linear" with "lba32", rerun lilo as "lilo -t -v" to test if thats ok, then rerun lilo to install the changes and reboot.
Quote:
3.) I am booting from a floppy, which doesn't seem to care about device 0x0306 or sector 51220658. Why isn't this a problem using a floppy?
Because your floppy contains its own boot loading mechanism and a kernel independant of ure hd's.
 
Old 06-10-2001, 11:18 PM   #4
rdaves@earthlink.net
Member
 
Registered: May 2001
Location: Full-time traveler I live where I am.
Distribution: I use Red Hat V 7.1
Posts: 297

Original Poster
Rep: Reputation: 30
Mcleodnine and Unspawn

Mcleodnine:
re:Can you post your /etc/lilo.conf and /etc/fstab?
Yes I will, but I am worn out after working on this beast all week-end. Will post this stuff tomorrow.

Unspawn:
I changed ‘linear’ in ‘lilo.conf’ to ‘lba32;
Then typed /sbin/lilo -t -v
And got:
[root@localhost /root]# /sbin/lilo -t -v
Lilo version 21.4.4 (test mode), copyright…
‘lba32’ extensions copyright…
Reading boot sector from /dev/hda
Merging with /boot/boot.b
Mapping message file /boot/message
Boot image: /boot/mykernel-2.4.0
Added new *
Boot image: /boot/vmlinux-2.2.16-22
Fatal: Kernel /bppt/vmlinux-2.2.16-22 is too big

I went back and edited ‘lilo.conf’ and put ‘Linear’ back in, and got:
[root@localhost /root]# /sbin/lilo -t -v
Lilo version 21.4.4 (test mode), copyright…
‘lba32’ extensions copyright…
Reading boot sector from /dev/hda
Merging with /boot/boot.b
Warning: device 0x0306 exceeds 1024 cylinder limit
Fatal: geo_comp_addr: Cylinder number is too big (3188) > 1023
**By the way, I am typing all this stuff on a second computer, putting it on a floppy and then copying and pasting it into my posts. Is there any way around this?
-
I went to System Commander, and got the following info about my hard drive:
Drive 0, Partition 0 = MultiFAT 32, size-14998MB, OS-Windows98
Drive 0, Partition 1 = Extended, size-14315MB
----Logical Partition 1, type FAT 32, size-10009MB, OS-none
----Logical Partition 2, type-Linux, size 23MB, OS-Linux
----Logical Partition 3, type-Linux, size-4212MB, OS-Linux
----Logical Partition 4, type-Linux Swap, size-70MB, OS-unformatted


 
Old 06-10-2001, 11:45 PM   #5
mcleodnine
Senior Member
 
Registered: May 2001
Location: Left Coast - Canada
Distribution: s l a c k w a r e
Posts: 2,731

Rep: Reputation: 45
Re: Mcleodnine and Unspawn

Quote:
Originally posted by rdaves@earthlink.net
Mcleodnine:
re:Can you post your /etc/lilo.conf and /etc/fstab?
Yes I will, but I am worn out after working on this beast all week-end. Will post this stuff tomorrow.

Unspawn:
I changed ?linear? in ?lilo.conf? to ?lba32;
Then typed /sbin/lilo -t -v
And got:
[root@localhost /root]# /sbin/lilo -t -v
Lilo version 21.4.4 (test mode), copyright?
?lba32? extensions copyright?
Reading boot sector from /dev/hda
Merging with /boot/boot.b
Mapping message file /boot/message
Boot image: /boot/mykernel-2.4.0
Added new *
Boot image: /boot/vmlinux-2.2.16-22
Fatal: Kernel /bppt/vmlinux-2.2.16-22 is too big

Kernel's too fat. Compile again with this...
Code:
make bzImage
or
Code:
make bzlilo
bzlilo will make the vmlinuz kernel compressed, pop it into /boot and run lilo for you, while bzImage will do the same but not run lilo.
[bold]

I went back and edited ?lilo.conf? and put ?Linear? back in, and got:
[root@localhost /root]# /sbin/lilo -t -v
Lilo version 21.4.4 (test mode), copyright?
?lba32? extensions copyright?
Reading boot sector from /dev/hda
Merging with /boot/boot.b
Warning: device 0x0306 exceeds 1024 cylinder limit
Fatal: geo_comp_addr: Cylinder number is too big (3188) > 1023
**By the way, I am typing all this stuff on a second computer, putting it on a floppy and then copying and pasting it into my posts. Is there any way around this?
-
I went to System Commander, and got the following info about my hard drive:
Drive 0, Partition 0 = MultiFAT 32, size-14998MB, OS-Windows98
Drive 0, Partition 1 = Extended, size-14315MB
----Logical Partition 1, type FAT 32, size-10009MB, OS-none
----Logical Partition 2, type-Linux, size 23MB, OS-Linux
----Logical Partition 3, type-Linux, size-4212MB, OS-Linux
----Logical Partition 4, type-Linux Swap, size-70MB, OS-unformatted


[/B]
Your first Linux partition is a good size for /boot, problem is that it's beyond the 1024 cylinder limit. Don't know how to get this to work, but the newer lilo was supposed to be able to get around this old problem.

Looking fwd to seeing the lilo.conf so we can get you set straight.

"Anybody? Anybody?... Beuller?"
 
Old 06-11-2001, 05:56 AM   #6
unSpawn
Moderator
 
Registered: May 2001
Posts: 27,492
Blog Entries: 54

Rep: Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910
Mcleodnine is right, uve got to recompile.

Next u gotta somehow move ure boot partition below the 1024th cylinder mark. If ure BIOS sez its using LBA translation that would be around the 8GB mark, meaning ure somewhere at 2/3rd of /dev/hda1 :-[ I use and recommend partition magic for this kind of stuff, its commercial, excellent stuff and has never failed me.

Or use lilo version 21.6 or higher which seems to read beyond the 1024th cylinder limit.
 
Old 06-11-2001, 10:57 AM   #7
rdaves@earthlink.net
Member
 
Registered: May 2001
Location: Full-time traveler I live where I am.
Distribution: I use Red Hat V 7.1
Posts: 297

Original Poster
Rep: Reputation: 30
/etc/lilo.conf and /etc/fstab

Here are the files requested:
-
FSTAB
LABEL=/ / ext2 defaults 1 1
LABEL=/boot /boot ext2 defaults 1 2
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 0
/dev/cdrom1 /mnt/cdrom1 iso9660 noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner,rw 0 0
none /proc proc defaults 0 0
none /dev/pts devpts gid=5,mode=620 0 0
/dev/hda8 swap swap defaults 0 0
-
lilo.conf
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
; lba32
Linear
default=new
image=/boot/mykernel-2.4.0
label=new
read-only
root=/dev/hda7

image=/boot/vmlinux-2.2.16-22
label=old
root=/dev/hda7
read-only

other=/dev/hda1
label=dos

; verbose=5

regarding mcleodnine's suggestion to recompile:
You suggest that my kernel is too fat and that I recompile using "make bzImage"; Make bzImage is the command I have been using. You provide an alternative to use "make bzlilo"; If I understand your explanation, both bzImage and bzlilo compress the kernel. The only difference between the two is that bzlilo runs lilo for you and bzImage does not. Do I understand correctly?
_
I have downloaded and am going to install lilo 21.7, then recompile and see what gives.



[Edited by rdaves@earthlink.net on 06-11-2001 at 06:01 PM]
 
Old 06-12-2001, 01:17 AM   #8
rdaves@earthlink.net
Member
 
Registered: May 2001
Location: Full-time traveler I live where I am.
Distribution: I use Red Hat V 7.1
Posts: 297

Original Poster
Rep: Reputation: 30
Latest progress

I upgraded and installed lilo 21.7.5. It looks like the problem with lilo complaining about my HD being too large is solved. However, the problem with my kernel being too big is still with me. I recompiled (used bzImage) as follows:
make menuconfig
make dep
make clean
make bzImage
make modules
make modules_install
make install
Then rebooted and typed
/sbin/lilo -t -v
and got the message, again, that my kernel is too big.
There must be a lot of options in the make menuconfig process that I said yes to but do not need.
What's next? Or should I guess that I have to get a lot more cozey with and understand the make menuconfig options?
 
Old 06-12-2001, 07:36 AM   #9
unSpawn
Moderator
 
Registered: May 2001
Posts: 27,492
Blog Entries: 54

Rep: Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910Reputation: 2910
U should definately exclude everything u dont need, or if unsure build em as modules so they will only be loaded when needed.

My current 2.2.19 /usr/src/linux/arch/i386/boot/bzImage is aprox 675K large with only misc, net and cdfs built as modules, the rest I need is built-in.
 
Old 06-12-2001, 09:24 AM   #10
rdaves@earthlink.net
Member
 
Registered: May 2001
Location: Full-time traveler I live where I am.
Distribution: I use Red Hat V 7.1
Posts: 297

Original Poster
Rep: Reputation: 30
modules, eh?

I built PPP support and VFAT support as modules. When I try to mount a vfat file system or use PPP, I get the message that these things lack kernel support. Looks like it might be time to read my manual on how to deal with stuff that you have configured as a module.
-
Question: What's the best way to determine the size of my kernel, and how big is too big?

I have manually logged my make menuconfig choices in a MSWord document and am going to put this document in another post for comments and help.
 
Old 06-12-2001, 09:31 AM   #11
rdaves@earthlink.net
Member
 
Registered: May 2001
Location: Full-time traveler I live where I am.
Distribution: I use Red Hat V 7.1
Posts: 297

Original Poster
Rep: Reputation: 30
Here's my "make menuconfig" manual log

I have deleted the extensive post showing my "make menuconfig" log. Too much to ask of anyone to sharpshoot so much data.

[Edited by rdaves@earthlink.net on 06-13-2001 at 02:05 AM]
 
Old 06-12-2001, 10:06 AM   #12
Adversary
LQ Newbie
 
Registered: Jun 2001
Posts: 6

Rep: Reputation: 0
With posts like that, no wonder Jeremy needs more disk space

The PPP's could be compiled as modules.

You could also have a peek in /lib/modules/2.4.x/ and check out to see what modules have been compiled after you have done the usual:

make dep ; make bzImage ; make modules ; make modules_install

Let us know how you get on with that.

Ads
 
  


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
Oops! Ran wrong lilo switch. Can I undo? newmoon Linux - General 7 06-23-2005 10:55 AM
Can't run LILO error : Fatal:raid_setup:stat("/dev/hdi1") robban59 Linux - Newbie 4 05-31-2005 04:44 PM
LILO Fatal Error on multi-disk config. skubik Linux - Software 12 05-05-2003 06:02 PM
LILO fatal error ggg Linux - Software 10 05-24-2002 08:35 AM
Problem with Lilo not updating (yes I ran lilo after changing the conf) webguy Linux - General 2 06-24-2001 07:12 PM


All times are GMT -5. The time now is 04:11 AM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration