In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes:
I don't know if this is relevant, but some IDE controllers only
recognize the first 128 GB(binary) = 137*10^9 bytes.
I've heard of one that only supportds dma on the smaller disks,
and non-dma mode will work with larger disks.
--
Blars
On Tue, Jul 20, 2004 at 10:33:18AM +1000, Sara Falamaki wrote:
On Mon, Jul 19, 2004 at 04:15:36PM -0400, Rick Thomas wrote:
I don't know if this is relevant, but some IDE controllers only
recognize the first 128 GB(binary) = 137*10^9 bytes.
Is it possible that your controller has two
Rick Thomas wrote:
Controllers that don't believe in disks larger than 137 GB(decimal)
report any disk larger than that as being exactly 137 GB in size.
This is probably why cfdisk et al are telling you that your partitions
go beyond the end of the disk -- as far as they know, the disk ends
package: installation-reports
Debian-installer-version:
http://cdimage.debian.org/pub/cdimage-testing/sid_d-i/i386/20040718/sarge-i386-netinst.iso
uname -a: Linux swish 2.4.26-1-386 #2 Sat May 1 16:31:24 EST 2004
i686 unkown
Date: Mon Jul 19 22:29:13 EST 2004
Method: downloaded image from above
I'll paste it below for your convenience:
Problems with the debian (sarge) installer
For the record, after the IRC talk we had : this was reproducible on
20040718 sid_d-i image
I have asked Sara to try reproducing with a 2.6 install.
Quoting Christian Perrier ([EMAIL PROTECTED]):
I'll paste it below for your convenience:
Problems with the debian (sarge) installer
For the record, after the IRC talk we had : this was reproducible on
20040718 sid_d-i image
I have asked Sara to try reproducing with a 2.6 install.
Quoting Christian Perrier ([EMAIL PROTECTED]):
I'll paste it below for your convenience:
Problems with the debian (sarge) installer
For the record, after the IRC talk we had : this was reproducible on
20040718 sid_d-i image
I have asked Sara to try reproducing with a 2.6 install.
I don't know if this is relevant, but some IDE controllers only
recognize the first 128 GB(binary) = 137*10^9 bytes.
Is it possible that your controller has two modes? Windows uses one
mode that recognizes the whole disk, and Linux uses the other
(compatibility?) mode that only recognizes the
Controllers that don't believe in disks larger than 137 GB(decimal)
report any disk larger than that as being exactly 137 GB in size.
This is probably why cfdisk et al are telling you that your
partitions go beyond the end of the disk -- as far as they know,
the disk ends before the beginning
9 matches
Mail list logo
