<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="http://dev1galaxy.org/extern.php?action=feed&amp;tid=5667&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / acpi   -  power button working and system logging]]></title>
		<link>http://dev1galaxy.org/viewtopic.php?id=5667</link>
		<description><![CDATA[The most recent posts in acpi   -  power button working and system logging.]]></description>
		<lastBuildDate>Sun, 23 Apr 2023 10:18:50 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[acpi   -  power button working and system logging]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=41950#p41950</link>
			<description><![CDATA[<p>Hello, <br />recently I started playing with acpid. <br />read the manual briefly and noticed systemd supposedly handles acpi events. </p><p>Upon running acpid. My power button functions as it should, prior to running it the power button did not function on specific machines.<br />Due to acpi in system firmware being a component of hardware enumeration. </p><p>Not always happy with the dmesg results on acpi tables loading up early. I like to imagine watching your first step includes the first couple seconds of boot up. acpi is one of those things. <br />The bios pushes the tables which get reserved memory by the kernel I believe. That memory as far as I understand cannot be regained by the user without some serious control. I saw some black hat talks where apic registers were movable and exploited but only on one obscure cpu architecture.&#160; But also most SMM entry methods I&#039;ve seen involved very specific timing attacks which ultimately is only practical with in depth knowledge of the hardware.</p><p>Most of acpi functions seem trivial. power management and the like. However, because it handles hardware enumeration, as I mention before and after reading a mention of Mark Shuttleworth who compared ACPI with Trojan horses.&#160; My thoughts might not be entirely baseless. Even if it&#039;s a slightly un-informed opinion. I am just feeling with my gut and reading dmesg outputs every now and again. </p><p>With the behavior of certain hardware vendors. Is there even a good reason to trust their code when it comes to acpi?<br /><a href="https://www.markshuttleworth.com/archives/1332" rel="nofollow">https://www.markshuttleworth.com/archives/1332</a><br />Here is a opinion piece from the Ubuntu dev. </p><p>What can we do on the software side of things to mitigate the impact of acpi?&#160; Setting up logging might be maybe a half hearted step. Any other reading pieces out there I can divulge in?</p>]]></description>
			<author><![CDATA[dummy@example.com (czeekaj)]]></author>
			<pubDate>Sun, 23 Apr 2023 10:18:50 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=41950#p41950</guid>
		</item>
	</channel>
</rss>
