https://bugzilla.suse.com/show_bug.cgi?id=1219908 https://bugzilla.suse.com/show_bug.cgi?id=1219908#c3 --- Comment #3 from David Mair <dmair@suse.com> --- I'm unable to get the solution from Stefan (Reporter) to work on 8GB RPi4b systems. It fails loading the boot loader FUSE images (At least what are mounted from images on the rootfs:/boot/ directory as /boot/efi and /boot/grub2/<arch>, possibly grub /boot/vc as well). I took a working micro-sd RPi Tumbleweed installation and on the rootfs tried moving /boot to /boot.brick and copying /boot from the micro-sd to the USB disk. renamed /boot to /boot/.brick copied the whole diretory tree /boot from the working sda to to the USB disk. I made the file-systems ID the same on the USB disk as those on the micro-sd. NO SUCCESS, I still have BRICKED RPi 4b devices. I do now get as far as the boot file-system product selection menu but the only option is UEFI Firmware Setting. After a while it clears to a simple console with this error message repeated twice: grub-core/script/function:119:can't find comand fusetup Supporting the idea that afer copying u-boot.bin from the working micro-sd then on the BRICKED USB installation the FUSE file-system images for boot don't mount and boot stops. At the same time, the working micro-sd install has no directory called script or a directory called grub-core on bootfs or rootfs, though I didn't boot it to look, they are probably in one of he FUSE file-systems and they don't mount for my USB disk. I took a look at the content of the /boot directory on both disks, it looks like the configuration now comes from symlinks. They all reference ../ IOW /boot/ Which presumably would lead to one of the FUSE file-systems because their current contents for all the symlinks are empty. The installed kernel should have been 6.1.8 and t 6.1.7 rootfs:/usr/lib/as the previous and the initrd for both i present in /boot but rootfs:/usr/lib/(kernel, modules) are empty of anything except the dracut recovery material. I don't think I have the patience, tolerence or drive to try rebulding it from what's already present from the in the currently installed kernel FUSE files. BRICKING this RPi 4b 8G has destroyed a mail spam filter server and I'll have to rebuild it by installing from a USB install image thumb drive. Hopefully it has an old enough u-boot/grub2/kernel to actually boot from the USB interface... Final point, the nature of the problem can be seen on the RPi 4 (maybe earlier) system board. The yellow/green LED should flicker but stays ON all time with no OF/ON. This indicates either that the EEPROM image wasn't programmed by the boot or that there is no disk I/O. Other references say the former so it has more relevance than my "disk I/O" assumption. -- You are receiving this mail because: You are on the CC list for the bug.