Finally able to spend an afternoon working on this...

 * Since my last note, I've replaced the failed SSD with a 500 GB
   Samsung T7 SSD. I've also replaced the USB3 hub with a StarTechcom
   7-Port USB 3.0 Hub, as the previous hub had a loose USB connector to
   the RPI 4B. As I mentioned before, I'm running the lastest firmware
   ("Thu Apr 29 04:11:25 PM UTC 2021 (1619712685)"). FYI, the other
   devices on the hub are two Seagate hard drives (8 TB and 10 TB), a 1
   TB Crucial SSD, and a Blu-Ray drive.
     o There's been one change to boot behavior. I now need to unplug
       the hub from the RPI 4B until Tumbleweed has started booting. If
       I leave the hub connected, it never gets to Grub, unless all
       other devices are removed from the hub:

 * Since the SSD boots without the hub (even on the hub without the
   other devices) I guessed the issue had something to do with race
   conditions among the various devices, so I tried the following one
   at a time, to no avail, resetting back to the default at each step.
     o
       USB_MSD_PWR_OFF_TIME=2000 (default is 1000)
     o
       USB_MSD_PWR_OFF_TIME=0
     o
       USB_MSD_DISCOVER_TIMEOUT=30000 (default is 20000)
     o
       USB_MSD_LUN_TIMEOUT=3000 (default is 2000)
 * I then tried configuring a NETCONSOLE to capture debug logs, but I
   couldn't get it to work. I'll send a separate note about that.
 * So, I took some screen shots with my cell phone, the one above that
   fails to boot, and the following that was taken with the hub
   disconnected, which succeeds:



Any thoughts would be greatly appreciated. Thanks!

David


On 9/6/21 11:22 AM, David Walker wrote:
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.

David


On 9/2/21 2:51 AM, Guillaume Gardet wrote:

David,

Just to make sure, could you please update your EEPROM firmware by following this procedure:

https://en.opensuse.org/HCL:Raspberry_Pi4#Boot_from_USB_is_not_enabled_by_default

Cheers,

Guillaume

*From:* David Walker <[email protected]>
*Sent:* 30 August 2021 21:07
*To:* Matthias Brugger <[email protected]>; [email protected]
*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?)

David

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.



Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to