Talk:DSDT

From ArchWiki
Latest comment: 9 December 2023 by Solstice in topic About acpi_osi

ToDo

Sounds better than using an initrd, which poses a security concern. I'm still using grub-legacy, so I cannot currently elaborate on that feature. T1nk3r3r (talk) 15:42, 15 July 2012 (UTC)Reply[reply]
Reading that again, the GRUB2 insertion may also have security implications. It would depend on any integrity checks that might be performed each boot. Any such process should be elaborated in the GRUB2 article and linked to from here. T1nk3r3r (talk) 02:02, 18 July 2012 (UTC)Reply[reply]
I have tested this and from what I can tell it is working. However for the file 01_acpi to work right on most GRUB2 installations "libdir=${exec_prefix}/lib" should be changed to "libdir=${exec_prefix}/share". Ns89 (talk) 22:29, 27 February 2013 (UTC)Reply[reply]
When I get enough spare time, I/you can add a new section concerning code insertion which contains this info. Probably in the next couple days... I'm glad people are finding this article useful! T1nk3r3r (talk) 06:00, 28 February 2013 (UTC)Reply[reply]
New sections added. Although on retrospect, I feel that bootloader specific info might be better organized in their respective articles with a link coming from here. In the end, replacing ACPI code is up to the kernel options. At the moment, I cannot verify if these are enabled in stock -ARCH. Feel free to move this info into the article for the time being. Eventually it may get a merge tag. T1nk3r3r (talk) 22:28, 1 March 2013 (UTC)Reply[reply]
The broken link, which is http://www.lesswatts.org/projects/acpi/, was at DSDT#Recompiling it yourself. It is broken now too. I replaced it with https://01.org/linux-acpi. I am not sure there are no better URLs. Regid (talk) 15:37, 15 April 2017 (UTC)Reply[reply]

CPIO archive

In "Using a CPIO archive" section it says:

cp dsdt.aml ssdt1.aml kernel/firmware/acpi

but what's "ssdt1.aml" file? Where does it come from? There is no other reference to it in entire page. --J1simon (talk) 11:12, 7 April 2017 (UTC)Reply[reply]

Sorry for the (very) late reply, in case it's still an issue or if someone else has the same question: That's just an example, SSDT stands for "secondary system description table" and is usually one of the ACPI table files, found in the same folder as the DSDT file. I included it as an example to demonstrate how the other ACPI files belong in the same directory, in case someone found them to be faulty as well and fixed them. If you haven't done anything with those files, you can ignore them. Tonnz (talk) 12:39, 9 June 2018 (UTC)Reply[reply]

About acpi_osi

I think the example acpi_osi="!Windows2012" is wrong, you need to add a space there.

Also, the syntax is more complex than that.

From what I read on https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt

acpi_osi="!string" just remove than one string so acpi_osi="!Windows 2012" remove only that string and is useless for other Windows version. So this is very likely uneffective


A more effective way to remove any string and add a string with for exmaple:

acpi_osi=! acpi_osi="Windows 2022"


Also the list of windows string can be extended to:

Windows 2012

Windows 2013

Windows 2015

Windows 2016

Windows 2017

Windows 2017.2

Windows 2018

Windows 2018.2

Windows 2019

Windows 2020

Windows 2021

Windows 2022


list taken from https://learn.microsoft.com/en-us/windows-hardware/drivers/acpi/winacpi-osi

More info at https://www.kernel.org/doc/html/latest/firmware-guide/acpi/osi.html. acpi_osi="Linux" is not really recommended, unless you have a bad BIOS that use _OSI(Linux) and you want to match for it.

solsTiCe (talk) 15:38, 9 December 2023 (UTC)Reply[reply]