Mike Houston wrote:
On Sun, 9 Dec 2007 23:42:15 +0100
Jean Delvare <[email protected]> wrote:
On Sun, 09 Dec 2007 16:12:25 -0500, Elvis Pranskevichus wrote:
This indeed looks like a broken ACPI BIOS since the
aforementioned commit touches only the PNP ACPI driver. I'm not
sure how to work around this, though. Ideas?
Complaining to Gigabyte seems to be the best approach.
I just happen to have a Windows Vista installation on this box as
well, and I just thought to check. Sorry, I wish I'd have thought of
it sooner but I don't go there often. You folks might be interested
to know that Windows appears to have the same silly problem with the
i/o resources (from Device Manager):
[000000290 - 000000294] Motherboard resources
[000000290 - 00000029F] Motherboard resources
I don't have anything that reads sensors in Windows though, so I
couldn't tell you if it could access that it87 chip or not.
So this pretty much confirms that it's a motherboard/bios issue.
Mike Houston
I'm seeing this exact problem on an Asus Nforce4 based board. Prior to
moving to 2.6.24-rc4 it worked just fine. No additional acpi options
were selected in kernel config.
So add Asus A8N-E to the list of broken pnpacpi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]