On Wed, 23 Apr 1997, Rick Jones wrote: > I don't understand why lilo is doing this. I've never had this problem > before. > > I just repartitioned my drive and put linux on hda2. When I try to run > lilo to boot linux from hda2 instead of hda1 it gives me this error about > my cylinders. > > geo_comp_addr: Cylinder number is too big (2312 > 1023) > > I am aware that, for whatever reason, lilo won't look beyond cylinder > 1023, the 540MB line that M$ drew out of ignorance years ago. (It might > not have been Bill but I like blaming shit on him anyway.) > > Anyway. The point is that I took this into account and started hda2 at > cylinder 817. I gave hda1 405MB, hda2 792MB, and hda3 is a 20MB rescue > partition. > > So why in the hell does lilo report cylinder 2312 which I'm fairly sure is > in hda3 when I'm setting up hda2 which starts at 817?
A bit of back-of-the-envelope maths: hda1=405MB=816cyl, i.e. 2cyl per MB. Therefore hda2 ends at about 1200MB=2400cyl. I don't run large EIDE disks, but I think the entire partition has to come in under the 1023 limit. After all, you have no control over precisely where in the partition the kernel resides. > > I have used this same partition setup before without any trouble. Anyone > have a clue? Perhaps the kernel was nearer the start of the partition. > When is lilo going to recognise hard drives larger than 540MB? This is an > ignorant limitation. Now that BIOS can read them when is lilo going to be > updated? -- David Wright, Open University, Earth Science Department, Milton Keynes MK7 6AA U.K. email: [EMAIL PROTECTED] tel: +44 1908 653 739 fax: +44 1908 655 151 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .