Linux - SoftwareThis 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
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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.
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.
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
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.
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.
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]
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?
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.