<?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=7089&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / Raspberry Pi Devuan, multiboot, uefi, grub, no uboot, no image dd]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=7089</link>
		<description><![CDATA[The most recent posts in Raspberry Pi Devuan, multiboot, uefi, grub, no uboot, no image dd.]]></description>
		<lastBuildDate>Mon, 27 Oct 2025 17:23:09 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: Raspberry Pi Devuan, multiboot, uefi, grub, no uboot, no image dd]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=58798#p58798</link>
			<description><![CDATA[<p>For a semi-manual way of changing the kernel for the next boot, from a running system (not from a boot menu), Git can be used.</p><p>I successfully used this approach to test a new kernel built from &quot;rpi-image-builder&quot;.</p><p>With a system running from a Rasp Pi 4 image (from &quot;<a href="https://arm-files.devuan.org/" rel="nofollow">https://arm-files.devuan.org/</a>&quot;), I created a Git repo in &quot;/boot&quot;, checked-in the current files on a &quot;6.1.93&quot; branch, created a new branch for &quot;6.12.55&quot;, installed the new kernel image package, then checked-in that branch.</p><p>The new kernel booted; if it hadn&#039;t, the SD card would be moved to another box (with Git installed) so Git could be used to switch the SD card boot dir to the earlier, working branch.</p><p>(Repos could also be created in the other dirs touched by a kernel install, &quot;/etc&quot;, &quot;/usr/lib&quot;, and &quot;/usr/share/doc&quot;, with kernel-specific branches.)</p><p>This approach doesn&#039;t provide a boot menu, but it does provide a simple-ish way to get a Rasp Pi booting again while experimenting with new kernel versions.</p>]]></description>
			<author><![CDATA[dummy@example.com (davesp)]]></author>
			<pubDate>Mon, 27 Oct 2025 17:23:09 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=58798#p58798</guid>
		</item>
		<item>
			<title><![CDATA[Raspberry Pi Devuan, multiboot, uefi, grub, no uboot, no image dd]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=54652#p54652</link>
			<description><![CDATA[<p>Some interesting experiments here with a raspberry pi 3b+ I was given. Some of this may well apply to other models. It&#039;s a different way from the usual dd of someone else&#039;s image, or compilation&gt;dd from e.g. rpi-image-builder <a href="https://github.com/pyavitz/rpi-img-builder" rel="nofollow">https://github.com/pyavitz/rpi-img-builder</a> (thanks c0rnelius).</p><p>Early days so far and I didn&#039;t document everything very well.</p><p>The sd card was partitioned, using a Devuan system, with a small fat32 &quot;boot&quot; partition. To this was copied (not dd&#039;d) the &quot;virtual&quot; uefi from here <a href="https://github.com/pftf/RPi3" rel="nofollow">https://github.com/pftf/RPi3</a> .. Other files needed were EFI/boot/bootaa64.efi (simple to make and the bootloader found it automatically) and boot/grub with the usual (arm64) layout and a custom grub.cfg ..</p><p>The rest was formatted ext2 containing Devuan Daedalus loaded via mmdebstrap (superior IMO to debootstrap), then built up in chroot, complete with standard kernel.</p><p>On boot the grub menu appears and behaves normally. Everything seems to work including wireless. Bluetooth sound was more challenging, now working with alsa only + bluez-alsa. No xserver for now.</p><p>Interestingly I can chain the grub to another grub on a usb pen which (sdcard) grub always detects as /dev/sda. Other distributions are installed there, including another Daedalus and Ceres. Alternative kernels are installed there including a self-compiled mainline 6.13 (used default arm64 defconfig) and one compiled as a deb package using rpi-image-builder. Apparently 6.13 has improved pi support but they all work. A normal update-grub enables them all in the secondary grub menu.</p><p>Another revelation: I can boot a custom live image from iso. I never saw that done for arm64.</p><p>Anyone else here tried a pi setup like that? Multiboot with uefi, grub, no uboot, no image dd. Pure Devuan except in this case some maybe unnecessary firmware. Maybe you found something I missed or have better or different ideas. If something similar was posted here before either I never found it or it&#039;s way outdated.</p>]]></description>
			<author><![CDATA[dummy@example.com (dzz)]]></author>
			<pubDate>Thu, 27 Feb 2025 19:07:54 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=54652#p54652</guid>
		</item>
	</channel>
</rss>
