Skip to main content

Fixing a Buggy ACPI BIOS Updated for Windows 8 and Linux Kernel 3.x


In the BIOS, there is a table that configures/determines a number of hardware values for ACPI and your system to use.

One of the features of ACPI is that the values and methods used can be differentiated at boot time depending on what OS you run. Each version of MS Windows has a unique identifier and while Linux can identify as "Linux", the Linux ACPI gurus have decided that Linux will always identify itself as "Windows NT". Even if you force Linux to identify itself as Linux, the Linux ACPI code still lies to the BIOS, except for the computers specifically listed in drivers/acpi/blacklist.

If you are running very new hardware intended for Windows Vista or Windows 8, you might get better performance on ACPI-related issues if you identify, or "spoof", your Linux OS as Vista or Windows 8 )or a later version of Windows). This is done by adding the boot-time kernel parameter of acpi_osi="Windows 2006" or "Windows 2012" respectively (and the quotes are necessary). still, it best to know exactly what version of windows your BIOS explicitly supports.

[I don't know if BSD has similar functionality. Anybody? Bueller? Anybody?]

If you want to know what your particular BIOS will actually allow for
an OS name, install the psutils and iasl packages, then follow these directions until you get the disassembled dsdt.dsl file and look at the section where you find the word "Windows". All the allowed values of the OS name for your BIOS will be right around there. My Acer laptop BIOS reports "Linux" as well as "Windows 2006" and my older desktop reports only "Microsoft Windows NT" as valid names.

NOTE
If you specify nothing, the default OS definition for the Linux kernel is "Microsoft Windows NT" and this information is found in acconfig.h.

From kernel-parameters.txt, is states that to spoof as Windows 98, use
acpi_osi="Microsoft Windows"

From uteval.c (used to be there, I don't know where it is found nowadays), the values given are:
"Windows 2000", /* Windows 2000 */
"Windows 2001", /* Windows XP */
"Windows 2001 SP1", /* Windows XP SP1 */
"Windows 2001 SP2", /* Windows XP SP2 */
"Windows 2001.1", /* Windows Server 2003 */
"Windows 2001.1 SP1", /* Windows Server 2003 SP1 */
"Windows 2006", /* Windows Vista */
"Windows 2009" will spoof for Windows 7
"Windows 2012" should spoof for Windows 8
"Windows 2013" should spoof for Windows 8.1
"Microsoft Windows" will spoof for Windows98
"Windows 2015"  spoofs for Windows 10
"Windows 2016"   spoofs for  Windows 10, version 1607
"Windows 2017"   spoofs for  Windows 10, version 1703
"Windows 2017.2" spoofs for Windows 10, version 1709
"Windows 2018 "   spoofs for Windows 10, version 1803
"Windows 2018.2"spoofs for Windows 10, version 1809
"Windows 2019" Windows 10, version 1903

"Windows 2020" Windows 10, version 2004

Some values can be found in a Microsoft White Paper.

Remember, the quotes are needed. And, if the value you are passing is not found in your ACPI BIOS, it will default to the ACPI BIOS default, whatever that is. You need to disassemble your ACPI BIOS as directed above to know for certain.

As a bonus, you might even be able to fix your broken DSDT and it's
easy to add it to your initrd.img.

REFERENCES

ACPI provides two mechanisms for determining the OS

Overriding the DSDT
http://powersave.sourceforge.net/powersave/DSDT.html

Linux ACPI FAQ
http://www.lesswatts.org/projects/acpi/faq.php

Linux ACPI Howto
http://web.archive.org/web/20070714030032/http://www.cpqlinux.com/acpi-howto.html

How to debug ACPI Problems

http://lwn.net/Articles/237085/

ACPIDUMP
http://www.linux-support.com/cms/en/magazine/man-pages/27771

DSDT: Overview
http://acpi.sourceforge.net/dsdt/index.php

Kernel Parameters
http://www.kernel.org/doc/Documentation/kernel-parameters.txt

HOWTO: Fix A Buggy DSDT file
http://forums.linuxmint.com/viewtopic.php?f=42&t=20719

How To Fix Your Buggy DSDT
http://forums.opensuse.org/how-faq-read-only/unreviewed-how-faq/386054-how-fix-your-buggy-dsdt.html

Store(Local0, Local0) generates an error
https://lists.linux-foundation.org/pipermail/bugme-new/2003-November/009350.html

Store(LocalX,LocalX) now produces an error
http://acpica.org/bugzilla/show_bug.cgi?id=785

HOWTO: Fix Common ACPI Problems (DSDT, ECDT, etc.)
http://forums.gentoo.org/viewtopic.php?t=122145

DSDT compilation issues
http://www.mail-archive.com/linux-acpi@vger.kernel.org/msg06782.html

Overriding a DSDT
http://www.lesswatts.org/projects/acpi/overridingDSDT.php
Sensors not updated causing CPU to heat after suspend/hibernate on laptop
https://bugs.launchpad.net/linux/+bug/182929

ACPI Specifications - Toshiba
http://uk.computers.toshiba-europe.com/innovation/download_whitepaper.jsp?service=UK&WHITEPAPER_ID=00000004c6

Comments

Georgi Georgiev said…
Hi to answer your question:

"[I don't know if BSD has similar functionality. Anybody? Bueller? Anybody?]
"

Yes BSD has similar functionality:

Check out this link - http://www.pc-freak.net/blog/how-to-disable-acpi-power-saving-support-in-freebsd-disable-acpi-on-bsd-kernel-boot-time/

Popular posts from this blog

DOS4GW.EXE Version 2.01a and Alternative DOS Extenders

DOS4GW.EXE The Tenberry DOS extender DOS4GW.EXE was used by many early DOS games. I still enjoy playing many of these games and DOS4GW.EXE is usable with DOSBox , so they can be played on Linux. However, the version of DOS4GW.EXE that was included with the game was whatever was current at the time. The most recent version that includes many bugfixes that possibly affected the games when used with DOSBox have been fixed in the latest version, 2.01a. It's not free at US$49, but you can downloaded it here . Simply substitute it for whatever version of DOS4GW.EXE your game provided and enjoy the bug-fixed goodness. Tenberry also makes a "high-performance" "pro" version of DOS4GW.EXE, but it costs $300. I think that they could sell quite a few of these to hobby users (since, you know, DOS is dead) for US$5. Open Souce to the Rescue There are better performing, free and Open Source alternatives available and worth a look. DPMI Explained Let's unders

Return to Castle Wolfenstein for Modern Linux

Return to Castle Wolfenstein is a first-person shooter originally released on November 19, 2001. The game, like many other classic games, is available at GOG.com and costs only US$5.99. iortcw for Linux Don't bother with old and crusty Linux binaries offered by idsoft; they are problematic and it's painful to use them on a modern Linux. Fortunately for us, there are more modern GPL-licensed Linux binaries available for 32- and 64-bit systems as well as high resolution textures packages. The project at GitHub provides source code that can also be compiled for MS Windows using MinGW. iortcw for Windows and Mac You can download pre-compiled binaries for 32- and 64-bit Linux, MS Windows and Mac from here . Let's put our files in /usr/local/games/rtcw . As root, extract the downloaded .ZIP file for your architecture to  /usr/local/games/rtcw . All we are missing are the game data files. I purchased them from GOG.com. The game installer downloaded from GOG.com can be

Unreal Tournament GOTY/UT99 for Modern Linux

Released on November 16, 1999, Unreal Tournament (also known as UT99) is an arena first-person shooter for Multiplayer on-line competition or you can play against bots off-line. It features several game types, with more details provided at Wikipedia . The game was re-released on February 25, 2000 as Unreal Tournament Game of the Year Edition (GOTY) which included the three bonus packs released previously and additional mods, or game modifiers that had become popular. It is the GOTY version that is available from STEAM or  GOG.com . The GOG version for Windows installs in Linux and plays well using WINE , PlayOnLinux or Codeweaver's Crossover . There is a Linux binary available in two versions, one for the original game and one for the GOTY edition . Also provided at that site is the Official Bonus Pack with a Linux installer. All these Linux installers are created with makeself . There are some issues using such a crusty old Linux binary. Let's see why getting a Lin