-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
____/ Homer on Wednesday 29 Jun 2011 08:58 : \____
> Verily I say unto thee, that Roy Schestowitz spake thusly:
>>
>> Kernel Log: BIOS bugs behind greater power use
>>
>> ,----[ Quote ]
>> | Since version 2.6.38, kernels have used more power because, in
>> | certain situations, they disable the power-saving ASPM feature. New
>> | stable and long-term kernels offer corrections; however, one of them
>> | is conspicuously lagging behind.
>> |
>> | In April, the Phoronix web site reported that some systems require
>> | more power with Linux 2.6.35 and 2.6.38 than they did with the
>> | previous versions. Phoronix says it has now found the reason for the
>> | increased power consumption in 2.6.38.
>> `----
>>
>> http://www.h-online.com/open/features/Kernel-Log-BIOS-bugs-behind-greater-power-use-1269032.html
>
> [quote]
> The culprit is said to be the "PCI: Disable ASPM if BIOS asks us to"
> change that was integrated in 2.6.38. According to its commit comment,
> the feature is designed to fix problems that occur when the BIOS
> activates the ASPM (Active State Power Management) power-saving feature
> with certain PCIe chips but declares that it doesn't support the ASPM in
> the FADT (Fixed ACPI Description Table), which is consulted by Linux.
> The modification allows the kernel to consider the information in the
> ACPI tables and attempt to disable ASPM for all PCIe devices if the BIOS
> permits it to do so.
>
> However, in a large number of systems, the BIOS apparently provides
> incorrect ASPM support information via the FADT.
>
> ...
>
> That Linux actually approaches some situations more correctly than
> Windows is irrelevant: highly specification-compliant operational
> procedures coupled with inaccurate notebook BIOS ACPI tables have been
> among the causes of many ACPI problems that have troubled Linux users
> over the years. Things got better when the Linux ACPI interpreter began
> to imitate that of Windows, making some of the same mistakes ("bug
> compatibility").
> [/quote]
>
> http://www.h-online.com/open/features/Kernel-Log-BIOS-bugs-behind-greater-power-use-1269032.html
>
> IOW manufacturers seem to be deliberately introducing incompatibilities
> by deviating from the ACPI standard, then compensating using Windows
> only drivers, which must then be analysed by other OS vendors to mimic
> their behaviour, in order to use that hardware with anything other than
> Windows.
>
> That, quite bluntly, is sabotage.
>
> I wonder what could possibly motivate them to do that?
>
> Hmmm.
>
> [quote]
> Company sold me a computer motherboard, model G33M-S, claiming that it
> was compliant with ACPI versions 1.0, 2.0, and 3.0.
>
> Linux and FreeBSD do not work with this motherboard due to it's ACPI
> configuration, using a disassembler program, I have found that it
> detects Linux specifically and points it to bad DSDT tables, thereby
> corrupting it's hardware support, changing this and setting the system
> to override the BIOS ACPI DSDT tables with a customized version that
> passes the Windows versions to Linux gives Linux ACPI support stated on
> the box, I am complaining because I feel this violates an anti-trust
> provision in the Microsoft settlement, I further believe that Microsoft
> is giving Foxconn incentives to cripple their motherboards if you try to
> boot to a non-Windows OS.
> [/quote]
>
> http://ubuntuforums.org/showthread.php?t=869249
>
> Foxconn were eventually pressured into fixing the BIOS after being
> publicly exposed, berated and humiliated.
Turns out that "TheAlmightyCthulhu" is in fact Ryan from our IRC channel
(or so he claims). :-)
- --
~~ Best of wishes
Dr. Roy S. Schestowitz (Ph.D. Medical Biophysics), Imaging Researcher
http://Schestowitz.com | GNU/Linux administration | PGP-Key: 0x74572E8E
Editor @ http://techrights.org & Broadcaster @ http://bytesmedia.co.uk/
GPL-licensed 3-D Othello @ http://othellomaster.com
Non-profit search engine proposal @ http://iuron.com
Contact E-mail address (direct): s at schestowitz dot com
Contact Internet phone (SIP): schestowitz@xxxxxxxxx (24/7)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAk4K6D4ACgkQU4xAY3RXLo48+QCeMogA1/Avvz+W5ef+j2G5gFEr
1d4Anj9J6lwDv8CixYFpl/+Oi9tY2lt/
=qlQC
-----END PGP SIGNATURE-----
|
|
