Re: Problems with 2.6.10

[Bodo Eggert]

Fryderyk Mazurek wrote:

> At last I fixed my problem! I changed source to not enable "Host
> Protected Area". This means that on 2.6.10 I have 33,8GB disk, not
> 40GB, how on "true" 2.6.10. And now my BIOS detect my disk. But
> question is, what does "true" kernel do, and why influence to BIOS?
> Maybe this is kernel BUG?

I can see the reason why this happens: When you boot, your HDD will be in
a compatibility mode for broken BIOSes, but it will not enter compatibility
mode on reboot. (Is it supposed to work this way, or should the BIOS
completely reset the device?)

There may be two solutions for this problem:
 - Reset the drive (hdparm -w) before rebooting (just a quick workaround)
 - Remember the initial state during runtime and restore it before reboot

The first option may not work at all, I'm just guessing here.
The second option will require a feature enheancement to the IDE subsystem.

To quickly find out if option 1 is enough, you could boot a non-patched
kernel with init=/bin/sh. In the shell, enter:
# hdparm -w
# shutdown -n -r now

If it works for your problen, hdparm will probably disable propper access
to the HDD until reboot. (This could mean some other cases might be broken,
too.)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/