Re: LILO cylinder problem
On Fri, 25 Apr 1997, David Pfitzner wrote: 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? I seem to recall reading that you can have problems with partitations where are not _entirely_ within 1023 cylinders, because the kernel image could happen to be in that part of the partition which is past the 1023 cylinder. Exactly. And what I do to deal with the problem is create a very small partition for the /boot directory, where vmlinuz and the other LILO stuff resides. Mine is 4 mb but 2 mb is more than sufficient. Perry -- If red tape were nutritious, we could feed the world. Perry Piplanihttp://perrypip.netservers.com [EMAIL PROTECTED] http://www.netservers.com -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: LILO cylinder problem
A. M. Varon wrote: On Thu, 24 Apr 1997, Rick Jones wrote: I'm reposting this since I haven't gotten any responses yet. Any ideas would be greatly appreciated. If your motherboard is new, you could turn on lba in the bios of your computer. Linux has no problems accessing my 2.0 gb. EIDE harddisk. regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Andre M. Varon Lasaltech, Incorported Technical Head Fax-Tel: (034)433-3520 e-mail : [EMAIL PROTECTED] web page: http://www.lasaltech.com/andre.html =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . Linux has no problems with my 5 gig eide disk. :) [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: LILO cylinder problem
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? I seem to recall reading that you can have problems with partitations where are not _entirely_ within 1023 cylinders, because the kernel image could happen to be in that part of the partition which is past the 1023 cylinder. But I could be wrong, and/or this could have nothing to do with your particular problem... -- David Pfitzner -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: LILO cylinder problem
On Thu, 24 Apr 1997, Rick Jones wrote: I'm reposting this since I haven't gotten any responses yet. Any ideas would be greatly appreciated. If your motherboard is new, you could turn on lba in the bios of your computer. Linux has no problems accessing my 2.0 gb. EIDE harddisk. regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Andre M. Varon Lasaltech, Incorported Technical Head Fax-Tel: (034)433-3520 e-mail : [EMAIL PROTECTED] web page: http://www.lasaltech.com/andre.html =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: LILO cylinder problem
I'm reposting this since I haven't gotten any responses yet. Any ideas would be greatly appreciated. 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? I have used this same partition setup before without any trouble. Anyone have a clue? 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? --Rick [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . --Rick [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: LILO cylinder problem
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] .
LILO cylinder problem
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? I have used this same partition setup before without any trouble. Anyone have a clue? 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? --Rick [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
