Sorry for the delay in answering; I've been recovering from a failed SSD (the one that boots but not when connected to a hub).
I do have the latest EEPROM firmware installed, using the "From a running system on the RPi" method.
I'm restoring everything to a replacement SSD and then will retry booting via the USB hub.
On 9/2/21 2:51 AM, Guillaume Gardet wrote:
Just to make sure, could you please update your EEPROM firmware by following this procedure:
*From:* David Walker David@WalkerStreet.info *Sent:* 30 August 2021 21:07 *To:* Matthias Brugger firstname.lastname@example.org; email@example.com *Subject:* Re: Booting Tumbleweed from USB on Raspberry Pi 4B
The unrecognized keyboard is a SIIG USB Mini Multimedia Keyboard; lsusb lists it as: "Bus 001 Device 009: ID 046e:6000 Behavior Tech. Computer Corp. USB Keyboard". I now have an official Raspberry Pi Keyboard that works fine.
I can open a bug, but I've recently started wondering if a number of funny quirks I've been seeing (/e.g./, not booting when the USB boot SSD is plugged into a hub, GDM running 100% - https://bugzilla.opensuse.org/show_bug.cgi?id=1188182, or display mysteriously crashing overnight - https://bugzilla.opensuse.org/show_bug.cgi?id=1187510) might be due to the fact that I installed Tumbleweed from the DVD ISO (on a USB flash drive), rather than using the pre-built image. Would the ISO have built things like /boot/efi correctly for a Raspberry Pi 4B? On casual inspection, my /boot/efi seems to be different from the pre-built image, but I don't have deep enough knowledge to know what difference would be material.
Would it make sense to copy, for example, /boot/efi from a pre-built image to find out? (Is it as simple as just copying files?)
On 8/30/21 4:20 AM, Matthias Brugger wrote:
Hi David, On 27/08/2021 18:29, David Walker wrote: This isn't quite your configuration (if your HD is truly a spinning disk), but I've been successful booting Tumbleweed on a USB-connected SSD, although only if the SSD is plugged directly into one of the RPI 4B's USB ports. It doesn't work if plugged into a USB hub that has other devices attached. I haven't investigated why the placement of my boot disk in the USB tree matters (my keyboard isn't recognized by u-boot or grub2), but I have an official RPI Can you share what keyboard you use? If you are interested, please open a bug and we can investigate what's happening. This seems to be a regression in U-Boot. Regards, Matthias keyboard on order. I'll report back if I learn anything. David On 8/26/21 5:04 PM, Sid Boyce wrote: I booted and setup from microSD and followed https://en.opensuse.org/HCL:Raspberry_Pi4. Next I also installed openSUSE-Tumbleweed-ARM-KDE-raspberrypi.aarch64-2021.08.06-Snapshot20210818.raw.xz to a USB HD. I read the Wiki and ran "rpi-eeprom-update -a -d" When I reboot it stops at the grub prompt when booted with the microSD in. grub> ls (proc) (hd0) (hd0,msdos3) (hd0,msdos2) (hd0,msdos1) (hd1,msdos3) (hd1,msdos2) (hd1,msdos1) Booting with onlu the USB HD, in a loop looking for the hard drive. No problem when booting with just a Ubuntu USB hard drive with no microSD card in. Ubuntu setup is quite straightforward. Anyone succeeded with Tumbleweed? Regards Sid.