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