It is a spinning self powered hard disk and I have tried both using a hub and plugged into the Pi4B. I am now buring a 128GB USB stick to try. Regards Sid. On 27/08/2021 17: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 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.

-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks

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 https://bugzilla.opensuse.org/show_bug.cgi?id=1188182, or display mysteriously crashing overnight - https://bugzilla.opensuse.org/show_bug.cgi?id=1187510 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.

Am Donnerstag, 2. September 2021, 11:51:01 CEST schrieb Guillaume Gardet:

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_de fault

JFTR, as the above wiki is inaccurate: The Raspi imager is available for openSUSE in between: opi rpi-imager does the job Cheers Axel

Am Freitag, 3. September 2021, 08:50:57 CEST schrieb Matthias Brugger:

On 02/09/2021 17:01, Axel Braun wrote:

...

Am Donnerstag, 2. September 2021, 11:51:01 CEST schrieb Guillaume Gardet:

...

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 _de fault

JFTR, as the above wiki is inaccurate: The Raspi imager is available for openSUSE in between: opi rpi-imager does the job

Axel, good to hear that. Would you mind to add the information in the wiki so that we have a central place?

Done that already Cheers Axel

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_de...

Cheers,

Guillaume

*From:* David Walker *Sent:* 30 August 2021 21:07 *To:* Matthias Brugger ; arm@lists.opensuse.org *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.

On Tue 21 Sep 2021 at 04:31, David Walker wrote:

As I mentioned in my previous note, I've been trying to get NETCONSOLE configured on my RPI 4B to collect debug logs while booting. The RPI 4B is 192.168.3.6, and I used "sudo nc -u -l 6666" to collect the output on 192.168.3.1 (on the same subnet).

Usingrpi-eeprom-config on Tumbleweed and documentation at https://www.raspberrypi.org/documentation/computers/raspberry-pi.html, I tried a number of variations of:

CLIENT_IP=192.168.3.6 SUBNET=255.255.255.0 NETCONSOLE=6665@192.168.3.6/,6666@/

The CLIENT_IP and SUBNET options are needed, as there's no DHCP server on that subnet. I tried "TFTP_IP=192.168.3.1", as the documentation indicated that it was needed along with CLIENT_IP and SUBNET to skip DHCP, but it didn't help. I also tried making NETCONSOLE's argument string more explicit, but there's a 32-character limit, so I couldn't do much there.

Has anyone gotten this to work who could provide some tips?

Thanks!

David

-- Sent from my iPad

Thanks I shall give that a try tomorrow with the USB stick first. RasPiOS and Ubuntu have been quite straightforward -- burn to 1TB hard drive and boot from the hard drive. At the moment it's up on Ubuntu 21.04 + KDE Regards Sid. On 11/09/2021 16:12, Freek de Kruijf wrote:

Op donderdag 2 september 2021 11:51:01 CEST schreef Guillaume Gardet:

...

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_d efault Cheers, Guillaume I have been doing some experiments with booting from a USB stick.

I use the Leap 15.3 NET iso to boot from.

Only with this storage device connected the system finally tries to boot via the network. It gives a message that there are 0 USB storage devices.

During boot I enter a character to interrupt the boot process and gets the prompt U-Boot>. I did some experiments with the command "usb". First "usb part" does not show any partition on the USB stick. However after "usb reset" not "usb start" this command shows the two partitions, a vfat and ext4 partition. Using printenv I found an environment variable usb_boot, which looks like a set commands to boot from usb. So I tried "run usb_boot", and it did work. It started the NET installation system.

This usb_boot contains the command "usb start", which apparently does not do the right thing when you did not use "usb reset" first.

Most likely this is the culprit. I reopened a closed bug report about a problem to boot from a USB device on a RPi4.

-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks

I only want to be able to boot from a USB drive, just as I do with Ubuntu, a 1TB plugged into a USB 3.0 hub. I burned a 128GB USB stick -- plugged into the Pi4B, at the graphical boot screen all is OK, I hit enter but it never gets further than the  "-" cursor in the top left of the LCD even after many hours. The reason for trying to boot with both was just something I thought worth a try just to see. No problems when booting from a microSD card. Regards Sid. On 30/08/2021 12:23, Matthias Brugger wrote:

On 27/08/2021 02:04, 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'm not quite sure why you are doing this. Do you want to boot from USB or from the uSD card? Why do you plug-in both?

...

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.

Can you stop U-Boot before booting and type then:

setenv xtrace 1 boot

And provide the information.

Regards, Matthias

...

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.

-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks

On 31/08/2021 10:55, Matthias Brugger wrote:

On 31/08/2021 00:30, Sid Boyce wrote:

...

I only want to be able to boot from a USB drive, just as I do with Ubuntu, a 1TB plugged into a USB 3.0 hub.

I burned a 128GB USB stick -- plugged into the Pi4B, at the graphical boot screen all is OK, I hit enter but it never gets further than the  "-" cursor in the top left of the LCD even after many hours.

Ok, so you use a LCD as display, you didn't mention that. Can you check if the system comes up on the serial console/HDMI. Please double-check if you forgot to add any overlay on your USB stick installation.

Regards, Matthias

...

The reason for trying to boot with both was just something I thought worth a try just to see.

No problems when booting from a microSD card. Regards Sid.

On 30/08/2021 12:23, Matthias Brugger wrote:

...

On 27/08/2021 02:04, 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'm not quite sure why you are doing this. Do you want to boot from USB or from the uSD card? Why do you plug-in both?

...

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.

Can you stop U-Boot before booting and type then:

setenv xtrace 1 boot

And provide the information.

Regards, Matthias

...

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.

Hi Matthias, For both the 128GB microSD card and the 128GB USB stick or a 1TB USB 2.0 hard drive. xzcat/home/lancelot/ftp/AUG21/openSUSE-Tumbleweed-ARM-KDE-raspberrypi.aarch64-2021.08.06-Snapshot20210818.raw.xz | dd bs=4M of=/dev/sde iflag=fullblock oflag=direct status=progress; sync Pi4B ... keyboard, mouse, 7 inch HDMI touch LCD. The microSD boots no problems. I have a full desktop and was able to do a zypper dup to Snapshot20210829 and reboots always OK. Removing the microSD and booting from the USB stick, I hit enter at the graphical boot screen and it displays a "-" in the top left of the screen and gets no further. The process to boot from USB is different on Ubuntu but I am able to boot and run from a 1TB Toshiba USB HD on a USB 3.0 hub. I also run Ubuntu on a Pi3B from a USB stick. There seems to be only a problem with hard drives and USB sticks on Tumbleweed. I have a colleague who wants to run Tumbleweed on a Pi4B as his main desktop so it would be helpful if he could boot and run from a USB hard drive. I am downloading Snapshot20210829 to try with the USB stick. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks

On 01/09/2021 12:32, Matthias Brugger wrote:

On 01/09/2021 13:26, Sid Boyce wrote:

...

On 31/08/2021 10:55, Matthias Brugger wrote:

...

On 31/08/2021 00:30, Sid Boyce wrote:

...

I only want to be able to boot from a USB drive, just as I do with Ubuntu, a 1TB plugged into a USB 3.0 hub.

I burned a 128GB USB stick -- plugged into the Pi4B, at the graphical boot screen all is OK, I hit enter but it never gets further than the  "-" cursor in the top left of the LCD even after many hours.

Ok, so you use a LCD as display, you didn't mention that. Can you check if the system comes up on the serial console/HDMI. Please double-check if you forgot to add any overlay on your USB stick installation.

Regards, Matthias

...

The reason for trying to boot with both was just something I thought worth a try just to see.

No problems when booting from a microSD card. Regards Sid.

On 30/08/2021 12:23, Matthias Brugger wrote:

...

On 27/08/2021 02:04, 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'm not quite sure why you are doing this. Do you want to boot from USB or from the uSD card? Why do you plug-in both?

...

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.

Can you stop U-Boot before booting and type then:

setenv xtrace 1 boot

And provide the information.

Regards, Matthias

...

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.

Hi Matthias,

For both the 128GB microSD card and the 128GB USB stick or a 1TB USB 2.0 hard drive.

xzcat/home/lancelot/ftp/AUG21/openSUSE-Tumbleweed-ARM-KDE-raspberrypi.aarch64-2021.08.06-Snapshot20210818.raw.xz | dd bs=4M of=/dev/sde iflag=fullblock oflag=direct status=progress; sync

Pi4B ... keyboard, mouse, 7 inch HDMI touch LCD.

The microSD boots no problems. I have a full desktop and was able to do a zypper dup to Snapshot20210829 and reboots always OK.

Removing the microSD and booting from the USB stick, I hit enter at the graphical boot screen and it displays a "-" in the top left of the screen and gets no further.

Did you made sure that you enabled booting from USB in the RPi firmware? If you don't get to U-Boot you should check the first partition of your USB stick to see if you have u-boot.bin, dtb's, config.txt, grub etc in place.

Regards, Matthias

Pi4-3:~ #rpm -qa|grep raspberrypi-firmware raspberrypi-firmware-2021.03.10-2.2.noarch raspberrypi-firmware-config-2021.03.10-2.2.noarch raspberrypi-firmware-dt-2021.03.15-2.2.noarch I did the update before rebooting. Pi4-3:~ #rpi-eeprom-update -a BOOTLOADER: up to date   CURRENT: Thu Apr 29 16:11:25 UTC 2021 (1619712685)    LATEST: Thu Apr 29 16:11:25 UTC 2021 (1619712685)   RELEASE: critical (/lib/firmware/raspberrypi/bootloader/critical)            Use raspi-config to change the release.  VL805_FW: Dedicated VL805 EEPROM     VL805: up to date   CURRENT: 000138a1    LATEST: 000138a1 1TB Hard drive plugged in running from microSD. Disklabel type: dos Disk identifier: 0x92055551 DeviceBoot  Start     End Sectors SizeIdType /dev/sda1          8192   139263   131072   64M  c W95 FAT32 (LBA) /dev/sda2        139264  1163263  1024000  500M 82 Linux swap / Solaris /dev/sda3       1163264 11685854 10522591    5G 83 Linux ----------- Pi4-3:~ #mount /dev/sda1 /1 Pi4-3:~ #l /1 total 6322 drwxr-xr-x  4 root root   16384 Jan  1  1970 ./ drwxr-xr-x 19 root root    4096 Sep  1 12:15 ../ drwxr-xr-x  3 root root    2048 Aug 18 19:50 EFI/ -rwxr-xr-x  1 root root    1594 Mar 10 10:36 LICENCE.broadcom* -rwxr-xr-x  1 root root   30030 May 27 21:49 bcm2708-rpi-b-plus.dtb* -rwxr-xr-x  1 root root   29378 May 27 21:49 bcm2708-rpi-b-rev1.dtb* -rwxr-xr-x  1 root root   29767 May 27 21:49 bcm2708-rpi-b.dtb* -rwxr-xr-x  1 root root   29689 May 27 21:49 bcm2708-rpi-cm.dtb* -rwxr-xr-x  1 root root   30705 May 27 21:49 bcm2708-rpi-zero-w.dtb* -rwxr-xr-x  1 root root   29512 May 27 21:49 bcm2708-rpi-zero.dtb* -rwxr-xr-x  1 root root   30905 May 27 21:49 bcm2709-rpi-2-b.dtb* -rwxr-xr-x  1 root root   31054 May 27 21:49 bcm2710-rpi-2-b.dtb* -rwxr-xr-x  1 root root   33171 May 27 21:49 bcm2710-rpi-3-b-plus.dtb* -rwxr-xr-x  1 root root   32552 May 27 21:49 bcm2710-rpi-3-b.dtb* -rwxr-xr-x  1 root root   31050 May 27 21:49 bcm2710-rpi-cm3.dtb* -rwxr-xr-x  1 root root   53250 May 27 21:49 bcm2711-rpi-4-b.dtb* -rwxr-xr-x  1 root root   52954 May 27 21:49 bcm2711-rpi-400.dtb* -rwxr-xr-x  1 root root   53362 May 27 21:49 bcm2711-rpi-cm4.dtb* -rwxr-xr-x  1 root root   52456 Mar 10 10:36 bootcode.bin* -rwxr-xr-x  1 root root    2652 Apr  9 12:50 config.txt* -rwxr-xr-x  1 root root    7311 Mar 10 10:36 fixup.dat* -rwxr-xr-x  1 root root    5442 Mar 10 10:36 fixup4.dat* drwxr-xr-x  2 root root   20480 Aug 18 19:31 overlays/ -rwxr-xr-x  1 root root 2955008 Mar 10 10:36 start.elf* -rwxr-xr-x  1 root root 2230880 Mar 10 10:36 start4.elf* -rwxr-xr-x  1 root root       9 Aug 18 19:55 startup.nsh* -rwxr-xr-x  1 root root  649624 Aug 12 07:23 u-boot.bin* -rwxr-xr-x  1 root root      35 Aug 12 07:23 ubootconfig.txt ------------ Pi4-3:~ #mount /dev/sda3 /3 Pi4-3:~ #l /3 total 88 drwxr-xr-x  17 root root  4096 Aug 18 19:50 ./ drwxr-xr-x  19 root root  4096 Sep  1 12:15 ../ lrwxrwxrwx   1 root root     7 Aug  3 20:51 bin-> usr/bin/ dr-xr-xr-x   5 root root  4096 Aug 18 19:50 boot/ -rw-r--r--   1 root root   116 Aug 18 19:50 config.bootoptions -rw-r--r--   1 root root    71 Aug 18 19:42 config.partids drwxr-xr-x   3 root root  4096 Aug 18 19:42 dev/ drwxr-xr-x 109 root root  4096 Aug 18 19:42 etc/ dr-xr-xr-x   2 root root  4096 Aug 18 19:26 home/ lrwxrwxrwx   1 root root     7 Aug  3 20:51 lib-> usr/lib/ lrwxrwxrwx   1 root root     9 Aug  3 20:51 lib64-> usr/lib64/ drwx------   2 root root 16384 Aug 18 19:42 lost+found/ dr-xr-xr-x   2 root root  4096 Aug 18 19:26 mnt/ dr-xr-xr-x   2 root root  4096 Aug 18 19:26 opt/ drwxr-xr-x   2 root root  4096 Aug 18 19:24 proc/ drwx------   4 root root  4096 Aug 18 19:31 root/ drwxr-xr-x   2 root root  4096 Aug 18 19:41 run/ lrwxrwxrwx   1 root root     8 Aug  3 20:51 sbin-> usr/sbin/ dr-xr-xr-x   4 root root  4096 Aug 18 19:31 srv/ drwxr-xr-x   2 root root  4096 Aug 18 19:24 sys/ drwxrwxrwt   2 root root  4096 Aug 18 19:49 tmp/ drwxr-xr-x  13 root root  4096 Aug 18 19:26 usr/ drwxr-xr-x  11 root root  4096 Aug 18 19:31 var/ Regards Sid.

...

The process to boot from USB is different on Ubuntu but I am able to boot and run from a 1TB Toshiba USB HD on a USB 3.0 hub. I also run Ubuntu on a Pi3B from a USB stick.

There seems to be only a problem with hard drives and USB sticks on Tumbleweed.

I have a colleague who wants to run Tumbleweed on a Pi4B as his main desktop so it would be helpful if he could boot and run from a USB hard drive.

I am downloading Snapshot20210829 to try with the USB stick.

Regards

Sid.

-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks

On 03/09/2021 07:49, Matthias Brugger wrote:

On 01/09/2021 14:26, Sid Boyce wrote:

...

On 01/09/2021 12:32, Matthias Brugger wrote:

...

On 01/09/2021 13:26, Sid Boyce wrote:

...

On 31/08/2021 10:55, Matthias Brugger wrote:

...

On 31/08/2021 00:30, Sid Boyce wrote:

...

I only want to be able to boot from a USB drive, just as I do with Ubuntu, a 1TB plugged into a USB 3.0 hub.

I burned a 128GB USB stick -- plugged into the Pi4B, at the graphical boot screen all is OK, I hit enter but it never gets further than the  "-" cursor in the top left of the LCD even after many hours.

Ok, so you use a LCD as display, you didn't mention that. Can you check if the system comes up on the serial console/HDMI. Please double-check if you forgot to add any overlay on your USB stick installation.

Regards, Matthias

...

The reason for trying to boot with both was just something I thought worth a try just to see.

No problems when booting from a microSD card. Regards Sid.

On 30/08/2021 12:23, Matthias Brugger wrote: > On 27/08/2021 02:04, 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'm not quite sure why you are doing this. Do you want to boot from USB or > from > the uSD card? Why do you plug-in both? > >> 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. >> > Can you stop U-Boot before booting and type then: > > setenv xtrace 1 > boot > > And provide the information. > > Regards, > Matthias > >> 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. >> Hi Matthias,

For both the 128GB microSD card and the 128GB USB stick or a 1TB USB 2.0 hard drive.

xzcat/home/lancelot/ftp/AUG21/openSUSE-Tumbleweed-ARM-KDE-raspberrypi.aarch64-2021.08.06-Snapshot20210818.raw.xz

| dd bs=4M of=/dev/sde iflag=fullblock oflag=direct status=progress; sync

Pi4B ... keyboard, mouse, 7 inch HDMI touch LCD.

The microSD boots no problems. I have a full desktop and was able to do a zypper dup to Snapshot20210829 and reboots always OK.

Removing the microSD and booting from the USB stick, I hit enter at the graphical boot screen and it displays a "-" in the top left of the screen and gets no further.

Did you made sure that you enabled booting from USB in the RPi firmware? If you don't get to U-Boot you should check the first partition of your USB stick to see if you have u-boot.bin, dtb's, config.txt, grub etc in place.

Regards, Matthias

Pi4-3:~ #rpm -qa|grep raspberrypi-firmware raspberrypi-firmware-2021.03.10-2.2.noarch raspberrypi-firmware-config-2021.03.10-2.2.noarch

raspberrypi-firmware-dt-2021.03.15-2.2.noarch

I did the update before rebooting.

Pi4-3:~ #rpi-eeprom-update -a BOOTLOADER: up to date   CURRENT: Thu Apr 29 16:11:25 UTC 2021 (1619712685)    LATEST: Thu Apr 29 16:11:25 UTC 2021 (1619712685)   RELEASE: critical (/lib/firmware/raspberrypi/bootloader/critical)            Use raspi-config to change the release.

 VL805_FW: Dedicated VL805 EEPROM     VL805: up to date   CURRENT: 000138a1    LATEST: 000138a1

Do you have access to the serial console to see where the boot process is hanging? That would be crucial to debug the issue.

...

1TB Hard drive plugged in running from microSD.

Disklabel type: dos Disk identifier: 0x92055551

DeviceBoot  Start     End Sectors SizeIdType /dev/sda1          8192   139263   131072   64M  c W95 FAT32 (LBA) /dev/sda2        139264  1163263  1024000  500M 82 Linux swap / Solaris /dev/sda3       1163264 11685854 10522591    5G 83 Linux

Hm, maybe sda1 isn't marked as bootable, is this output from fdisk? Other then that things look good.

Regards, Matthias

...

-----------

Pi4-3:~ #mount /dev/sda1 /1

Pi4-3:~ #l /1 total 6322 drwxr-xr-x  4 root root   16384 Jan  1  1970 ./ drwxr-xr-x 19 root root    4096 Sep  1 12:15 ../ drwxr-xr-x  3 root root    2048 Aug 18 19:50 EFI/ -rwxr-xr-x  1 root root    1594 Mar 10 10:36 LICENCE.broadcom* -rwxr-xr-x  1 root root   30030 May 27 21:49 bcm2708-rpi-b-plus.dtb* -rwxr-xr-x  1 root root   29378 May 27 21:49 bcm2708-rpi-b-rev1.dtb* -rwxr-xr-x  1 root root   29767 May 27 21:49 bcm2708-rpi-b.dtb* -rwxr-xr-x  1 root root   29689 May 27 21:49 bcm2708-rpi-cm.dtb* -rwxr-xr-x  1 root root   30705 May 27 21:49 bcm2708-rpi-zero-w.dtb* -rwxr-xr-x  1 root root   29512 May 27 21:49 bcm2708-rpi-zero.dtb* -rwxr-xr-x  1 root root   30905 May 27 21:49 bcm2709-rpi-2-b.dtb* -rwxr-xr-x  1 root root   31054 May 27 21:49 bcm2710-rpi-2-b.dtb* -rwxr-xr-x  1 root root   33171 May 27 21:49 bcm2710-rpi-3-b-plus.dtb* -rwxr-xr-x  1 root root   32552 May 27 21:49 bcm2710-rpi-3-b.dtb* -rwxr-xr-x  1 root root   31050 May 27 21:49 bcm2710-rpi-cm3.dtb* -rwxr-xr-x  1 root root   53250 May 27 21:49 bcm2711-rpi-4-b.dtb* -rwxr-xr-x  1 root root   52954 May 27 21:49 bcm2711-rpi-400.dtb* -rwxr-xr-x  1 root root   53362 May 27 21:49 bcm2711-rpi-cm4.dtb* -rwxr-xr-x  1 root root   52456 Mar 10 10:36 bootcode.bin* -rwxr-xr-x  1 root root    2652 Apr  9 12:50 config.txt* -rwxr-xr-x  1 root root    7311 Mar 10 10:36 fixup.dat* -rwxr-xr-x  1 root root    5442 Mar 10 10:36 fixup4.dat* drwxr-xr-x  2 root root   20480 Aug 18 19:31 overlays/ -rwxr-xr-x  1 root root 2955008 Mar 10 10:36 start.elf* -rwxr-xr-x  1 root root 2230880 Mar 10 10:36 start4.elf* -rwxr-xr-x  1 root root       9 Aug 18 19:55 startup.nsh* -rwxr-xr-x  1 root root  649624 Aug 12 07:23 u-boot.bin* -rwxr-xr-x  1 root root      35 Aug 12 07:23 ubootconfig.txt

------------

Pi4-3:~ #mount /dev/sda3 /3 Pi4-3:~ #l /3 total 88 drwxr-xr-x  17 root root  4096 Aug 18 19:50 ./ drwxr-xr-x  19 root root  4096 Sep  1 12:15 ../ lrwxrwxrwx   1 root root     7 Aug  3 20:51 bin-> usr/bin/ dr-xr-xr-x   5 root root  4096 Aug 18 19:50 boot/ -rw-r--r--   1 root root   116 Aug 18 19:50 config.bootoptions -rw-r--r--   1 root root    71 Aug 18 19:42 config.partids drwxr-xr-x   3 root root  4096 Aug 18 19:42 dev/ drwxr-xr-x 109 root root  4096 Aug 18 19:42 etc/ dr-xr-xr-x   2 root root  4096 Aug 18 19:26 home/ lrwxrwxrwx   1 root root     7 Aug  3 20:51 lib-> usr/lib/ lrwxrwxrwx   1 root root     9 Aug  3 20:51 lib64-> usr/lib64/ drwx------   2 root root 16384 Aug 18 19:42 lost+found/ dr-xr-xr-x   2 root root  4096 Aug 18 19:26 mnt/ dr-xr-xr-x   2 root root  4096 Aug 18 19:26 opt/ drwxr-xr-x   2 root root  4096 Aug 18 19:24 proc/ drwx------   4 root root  4096 Aug 18 19:31 root/ drwxr-xr-x   2 root root  4096 Aug 18 19:41 run/ lrwxrwxrwx   1 root root     8 Aug  3 20:51 sbin-> usr/sbin/ dr-xr-xr-x   4 root root  4096 Aug 18 19:31 srv/ drwxr-xr-x   2 root root  4096 Aug 18 19:24 sys/ drwxrwxrwt   2 root root  4096 Aug 18 19:49 tmp/ drwxr-xr-x  13 root root  4096 Aug 18 19:26 usr/ drwxr-xr-x  11 root root  4096 Aug 18 19:31 var/

Regards

Sid.

...

...

The process to boot from USB is different on Ubuntu but I am able to boot and run from a 1TB Toshiba USB HD on a USB 3.0 hub. I also run Ubuntu on a Pi3B from a USB stick.

There seems to be only a problem with hard drives and USB sticks on Tumbleweed.

I have a colleague who wants to run Tumbleweed on a Pi4B as his main desktop so it would be helpful if he could boot and run from a USB hard drive.

I am downloading Snapshot20210829 to try with the USB stick.

Regards

Sid.

I tried another 128GB USB stick with same result. Next I used the microSD card in a reader, that also fails to boot completely, stuck with the "-" in the upper left of the 7 inch LCD. This is the same microSD card that boots to KDE when in the on board slot. Raspbian 64-bit boots from the 1TB USB hard drive. I'll next try TW XFCE. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks

On 31/08/2021 10:55, Matthias Brugger wrote:

On 31/08/2021 00:30, Sid Boyce wrote:

...

I only want to be able to boot from a USB drive, just as I do with Ubuntu, a 1TB plugged into a USB 3.0 hub.

I burned a 128GB USB stick -- plugged into the Pi4B, at the graphical boot screen all is OK, I hit enter but it never gets further than the  "-" cursor in the top left of the LCD even after many hours.

Ok, so you use a LCD as display, you didn't mention that. Can you check if the system comes up on the serial console/HDMI. Please double-check if you forgot to add any overlay on your USB stick installation.

Regards, Matthias

The system does not come up fully on the HDMI with USB boot, just sits there displaying the dash in the top left of a blank screen. Another indication that the boot process stalls somewhere is that it's not seen with "nmap -sT 192.168.10.0/24". This is what I see remotely when it's network is up. Nmap scan report for Pi4-3.site (192.168.10.227) Host is up (0.00067s latency). Not shown: 999 closed ports PORT   STATE SERVICE 22/tcp open  ssh MAC Address: DC:A6:32:8D:3E:DD (Raspberry Pi Trading) Regards Sid.

...

The reason for trying to boot with both was just something I thought worth a try just to see.

No problems when booting from a microSD card. Regards Sid.

On 30/08/2021 12:23, Matthias Brugger wrote:

...

On 27/08/2021 02:04, 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'm not quite sure why you are doing this. Do you want to boot from USB or from the uSD card? Why do you plug-in both?

...

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.

Can you stop U-Boot before booting and type then:

setenv xtrace 1 boot

And provide the information.

Regards, Matthias

...

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.

-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks