Re: Possible Install bug for the following hardware in FreeBSD Stable (4.3)
I had this problem after I enabled the '4092-cylinder limit' jumper on my Maxtor drive, because my BIOS (at that point) hung with a drive over 4092 cylinders. I flashed the BIOS afterwards, but forgot about the jumper, because windows/linux both (somehow) saw the full geometry of the drive. FreeBSD only saw 2014MB until I removed the jumper. Perhaps your drive has a similar jumper? check the manual. Thank you David for the tip. None the less, has this issue witht he driver been addressed? The driver should not bother about that, because the Hard disk reporst the correct size back. On the other, my drive does not have such a jumper, I just checked, so I am really at my wits ends. Thank you _very_ much for your help though, after about238623946 flames and 23862394 stupid replys yours is very nicely detailed...thank you. ad2 29314 MB IBM DTLA-307030 [5956/16/63 at at-1-master UDMA100 29314 * 1024 * 1024 bytes (i.e. 2914 megabytes) == 30736 * 1000 * 1000 bytes (i.e. 2914 million bytes) Its something harddrive manufacturers do to make their drives look bigger... YEs, I just realized that after doing the right calculation: 3736 cylinders of 16065 * 512 bytes I am not a hardware guru ;) Thank you. Content-Type: application/pgp-signature; charset=us-ascii; name=Attachment: 1 Content-Transfer-Encoding: 7bit Content-Description: -- si vis pacem, para bellum 'Doubt thou the stars are fire; Doubt that the sun doth move; Doubt truth to be a liar; But never doubt I love. - Hamelt, Shakespear To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Possible Install bug for the following hardware in FreeBSD Stable (4.3)
On Thu, 31 May 2001, Darian Lanx wrote: I had this problem after I enabled the '4092-cylinder limit' jumper on my Maxtor drive, because my BIOS (at that point) hung with a drive over 4092 cylinders. I flashed the BIOS afterwards, but forgot about the jumper, because windows/linux both (somehow) saw the full geometry of the drive. FreeBSD only saw 2014MB until I removed the jumper. Perhaps your drive has a similar jumper? check the manual. Thank you David for the tip. None the less, has this issue witht he driver been addressed? The driver should not bother about that, because the Hard disk reporst the correct size back. On the other, my drive does not have such a jumper, I just checked, so I am really at my wits ends. I'm not a hardware guru either, and I know very little about the internals of FreeBSD's IDE drivers, so I'm not sure how windows/linux are detecting the correct geometry, and FreeBSD isn't... Unfortunately, if your drive doesn't have a jumper like that, I've no idea what could be wrong... -- David Taylor [EMAIL PROTECTED] PGP signature
Re: Possible Install bug for the following hardware in FreeBSD Stable (4.3)
This should be 60034905 = 3737*255*63 No, that value is correct, has to do with internals how sysctl calculates the offsets, but that is an linux issue I am aware off This should be 59554/16/63 and you do not get all drive space. As I mentioned, I am aware, that I do not get all drive space, but over 800MB missing is too much. It seems your geometry is unmatched. Is LBA enabled in the cmos bios? Rich LBA is enabled by hand. My bios can auto dected all drive features, yet I chose to setup everything by hand and explicitly enabled LBA after being told to do so by several sources. -d Thank you for the quick answer -- si vis pacem, para bellum 'Doubt thou the stars are fire; Doubt that the sun doth move; Doubt truth to be a liar; But never doubt I love. - Hamelt, Shakespear To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
