<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=7365&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / [SOLVED] tstgr pi-5-daedalus img file problem]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=7365</link>
		<description><![CDATA[The most recent posts in [SOLVED] tstgr pi-5-daedalus img file problem.]]></description>
		<lastBuildDate>Tue, 19 Aug 2025 22:04:43 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[[SOLVED] tstgr pi-5-daedalus img file problem]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=57345#p57345</link>
			<description><![CDATA[<p>testing rpi-5-devuan-daedalus-6.12.41-arm64-ext4-2025-08-19-0209.img</p><p> pi45 4gb previously tested ok w debian<br />..system boots to prompt and I tried some installs and found that the rootfs had an incorrect<br />free block count. I repaired this w fsck.ext4 -fvy device on&#160; my desktop devuan 5.1 system.<br />and then when i rebooted, it went through startx&#160; to a desktop login prompt, and then<br />to a broken xterm, or other terminal window in the upper left hand corner of the screen.<br />AND it re-broke the rootfs device so it had the incorrect size again and the filesystem is full<br />and that is the end of that.<br />It would&#160; be preferred that the system not startx automatically, i don&#039;t know why that happened.</p><p>8-20-25<br />installed rpi-5-devuan-daedalus-6.12.42-arm64-ext4-2025-08-20-0243.img<br />and the problems have been solved, &amp; was albe to install other packages without problems so far....</p>]]></description>
			<author><![CDATA[dummy@example.com (delvasto1)]]></author>
			<pubDate>Tue, 19 Aug 2025 22:04:43 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=57345#p57345</guid>
		</item>
	</channel>
</rss>
