On 8/4/05, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
> All of these numbers are virtual, since CHS is not really used anymore, as
> we know. But, which of these fake CHS values (16383/16/63 | 65535/16/63 |
> 1023/255/63) is the right one? 255/63/4982 is another matter, since it
> [almost] matches
Jan Engelhardt wrote:
Simple: do not use BIOS values.
[ Yes, there should be some warning from kernel. ]
On that matter, I get a warning from LILO wrt cyls and stuff:
07:47 spectre:~ # cat /proc/ide/hda/geometry
physical 16383/16/63
logical 65535/16/63
07:58 spectre:~ # lilo
>Simple: do not use BIOS values.
>[ Yes, there should be some warning from kernel. ]
On that matter, I get a warning from LILO wrt cyls and stuff:
07:47 spectre:~ # cat /proc/ide/hda/geometry
physical 16383/16/63
logical 65535/16/63
07:58 spectre:~ # lilo
Warning: Kernel & BIOS return
Simple: do not use BIOS values.
[ Yes, there should be some warning from kernel. ]
On that matter, I get a warning from LILO wrt cyls and stuff:
07:47 spectre:~ # cat /proc/ide/hda/geometry
physical 16383/16/63
logical 65535/16/63
07:58 spectre:~ # lilo
Warning: Kernel BIOS return
Jan Engelhardt wrote:
Simple: do not use BIOS values.
[ Yes, there should be some warning from kernel. ]
On that matter, I get a warning from LILO wrt cyls and stuff:
07:47 spectre:~ # cat /proc/ide/hda/geometry
physical 16383/16/63
logical 65535/16/63
07:58 spectre:~ # lilo
On 8/4/05, Jan Engelhardt [EMAIL PROTECTED] wrote:
All of these numbers are virtual, since CHS is not really used anymore, as
we know. But, which of these fake CHS values (16383/16/63 | 65535/16/63 |
1023/255/63) is the right one? 255/63/4982 is another matter, since it
[almost] matches the
On 8/3/05, Mark Bellon <[EMAIL PROTECTED]> wrote:
> Bartlomiej Zolnierkiewicz wrote:
>
> >On 8/3/05, Mark Bellon <[EMAIL PROTECTED]> wrote:
> >
> >
> >>Bartlomiej Zolnierkiewicz wrote:
> >>
> >>
> >>
> >>>Hi,
> >>>
> >>>The topic was discussed to death on linux-kernel.
> >>>
> >>>Mark, you need
Bartlomiej Zolnierkiewicz wrote:
On 8/3/05, Mark Bellon <[EMAIL PROTECTED]> wrote:
Bartlomiej Zolnierkiewicz wrote:
Hi,
The topic was discussed to death on linux-kernel.
Mark, you need to fix your applications and stop using /proc/ide/hd*/geometry
or/and HDIO_GET_GEO ioctl (which
On 8/3/05, Mark Bellon <[EMAIL PROTECTED]> wrote:
> Bartlomiej Zolnierkiewicz wrote:
>
> >Hi,
> >
> >The topic was discussed to death on linux-kernel.
> >
> >Mark, you need to fix your applications and stop using /proc/ide/hd*/geometry
> >or/and HDIO_GET_GEO ioctl (which BTW your patch also
Bartlomiej Zolnierkiewicz wrote:
Hi,
The topic was discussed to death on linux-kernel.
Mark, you need to fix your applications and stop using /proc/ide/hd*/geometry
or/and HDIO_GET_GEO ioctl (which BTW your patch also affects).
Fixing the applications I can understand but the patch still
Hi,
The topic was discussed to death on linux-kernel.
Mark, you need to fix your applications and stop using /proc/ide/hd*/geometry
or/and HDIO_GET_GEO ioctl (which BTW your patch also affects).
Bartlomiej
On 8/3/05, Andre Hedrick <[EMAIL PROTECTED]> wrote:
>
> Did you read ATA-1 through
Andre Hedrick wrote:
Did you read ATA-1 through ATA-7 to understand all the variations?
Regardless of all of the geometry returns by the drives and their ATA
compliance, the existing code will fail for some drives and return
values. For instance, the existing code attempts to "fix up" LBA
Did you read ATA-1 through ATA-7 to understand all the variations?
On Tue, 2 Aug 2005, Mark Bellon wrote:
> The ATA specification tells large disk drives to return C/H/S data of
> 16383/16/63 regardless of their actual size (other variations on this
> return include 15 heads and/or 4092
Did you read ATA-1 through ATA-7 to understand all the variations?
On Tue, 2 Aug 2005, Mark Bellon wrote:
The ATA specification tells large disk drives to return C/H/S data of
16383/16/63 regardless of their actual size (other variations on this
return include 15 heads and/or 4092
Andre Hedrick wrote:
Did you read ATA-1 through ATA-7 to understand all the variations?
Regardless of all of the geometry returns by the drives and their ATA
compliance, the existing code will fail for some drives and return
values. For instance, the existing code attempts to fix up LBA 48
Hi,
The topic was discussed to death on linux-kernel.
Mark, you need to fix your applications and stop using /proc/ide/hd*/geometry
or/and HDIO_GET_GEO ioctl (which BTW your patch also affects).
Bartlomiej
On 8/3/05, Andre Hedrick [EMAIL PROTECTED] wrote:
Did you read ATA-1 through ATA-7 to
Bartlomiej Zolnierkiewicz wrote:
Hi,
The topic was discussed to death on linux-kernel.
Mark, you need to fix your applications and stop using /proc/ide/hd*/geometry
or/and HDIO_GET_GEO ioctl (which BTW your patch also affects).
Fixing the applications I can understand but the patch still
On 8/3/05, Mark Bellon [EMAIL PROTECTED] wrote:
Bartlomiej Zolnierkiewicz wrote:
Hi,
The topic was discussed to death on linux-kernel.
Mark, you need to fix your applications and stop using /proc/ide/hd*/geometry
or/and HDIO_GET_GEO ioctl (which BTW your patch also affects).
Fixing
Bartlomiej Zolnierkiewicz wrote:
On 8/3/05, Mark Bellon [EMAIL PROTECTED] wrote:
Bartlomiej Zolnierkiewicz wrote:
Hi,
The topic was discussed to death on linux-kernel.
Mark, you need to fix your applications and stop using /proc/ide/hd*/geometry
or/and HDIO_GET_GEO ioctl (which BTW
On 8/3/05, Mark Bellon [EMAIL PROTECTED] wrote:
Bartlomiej Zolnierkiewicz wrote:
On 8/3/05, Mark Bellon [EMAIL PROTECTED] wrote:
Bartlomiej Zolnierkiewicz wrote:
Hi,
The topic was discussed to death on linux-kernel.
Mark, you need to fix your applications and stop using
The ATA specification tells large disk drives to return C/H/S data of
16383/16/63 regardless of their actual size (other variations on this
return include 15 heads and/or 4092 cylinders). Unfortunately these CHS
data confuse the existing IDE code and cause it to report invalid
geometries in
The ATA specification tells large disk drives to return C/H/S data of
16383/16/63 regardless of their actual size (other variations on this
return include 15 heads and/or 4092 cylinders). Unfortunately these CHS
data confuse the existing IDE code and cause it to report invalid
geometries in
22 matches
Mail list logo
