Alan Cox wrote:
> Molle Bestefich wrote:
> > Not if, as proposed, there was a kernel switch to enable including the
> > HPA in the disc area.
>
> And users magically knew about it - thats why it has to default the
> other way.
Ok, so just to reiterate..
The current
een, not a firmware update...
Supposedly the BIOS can change the bounds of the HPA with special ATA commands..
Matthew Garrett wrote:
> Molle Bestefich wrote:
> > If HPA were exposed as /dev/.../hpa then it wouldn't be possible to
> > create such a filesystem. I'm guessing
Alan Cox wrote:
> > If the formula is to fix all the userspace apps to take into account a
> > potential HPA, then eg. FDISK + SFDISK + Disk Druid et al should also
> > be fixed. Because if you create a partition spanning your entire
> > disk, including the HPA area, and your boot files by some co
Alan Cox wrote:
> Greg Felix wrote:
> > Right. I get the output at bootup time. It reads that the HPA is
> > 20MB. Which is exactly the size of how far off the metadata is in
> > Linux (once the HPA is disabled).
>
> So your actual problem is nothing to do with the kernel or with the HPA
> beha
4 matches
Mail list logo
