<?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=6420&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / ACPI Error: Could not disable RealTimeClock events]]></title>
		<link>http://dev1galaxy.org/viewtopic.php?id=6420</link>
		<description><![CDATA[The most recent posts in ACPI Error: Could not disable RealTimeClock events.]]></description>
		<lastBuildDate>Sat, 17 Feb 2024 22:04:04 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: ACPI Error: Could not disable RealTimeClock events]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=48268#p48268</link>
			<description><![CDATA[<p>netinstall 5.0.1 is linux-image-6.1.0-10<br />since then Devuan has provided 6.1.0-11|12|15|18<br />the bug feature has arrived with 18<br />I have determined this by having installed 10|11|12|15|18<br />I have ran through them all with shutdown -h now and unpugging the power for more than 5 seconds.<br />I tried kexec-tools which is wicked, but the Error remained up &amp; down the versions?! shady<br />This bug feature is currently officially reported by others.<br />It does not bother me but may bother others running ntpsec and many other programs.<br />It only manifests on certain pieces of crap BIOS &amp; hardware.</p>]]></description>
			<author><![CDATA[dummy@example.com (bilhook)]]></author>
			<pubDate>Sat, 17 Feb 2024 22:04:04 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=48268#p48268</guid>
		</item>
		<item>
			<title><![CDATA[ACPI Error: Could not disable RealTimeClock events]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=48170#p48170</link>
			<description><![CDATA[<p>One of my computers has got a defective quality BIOS, and an upgrade is not going to happen.<br />On boot I get annoying messages, &#039;ACPI Error: Could not disable RealTimeClock events ...&#039;<br />In a console, I do, tail -f /var/log/syslog<br />In another console I change the clocksource,<br />echo hpet|acpi_pm &gt; /sys/devices/system/clocksource/clocksource0/current_clocksource<br />When I change from tsc to hpet to acpi_pm I still get the same Error message in syslog, when I hwclock --systohc.<br />I think this is a newer kernel bug feature.<br />I am not going to worry about it.</p>]]></description>
			<author><![CDATA[dummy@example.com (bilhook)]]></author>
			<pubDate>Thu, 15 Feb 2024 16:09:10 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=48170#p48170</guid>
		</item>
	</channel>
</rss>
