Headache with Raspberry Pi 3 / USB installation.

English Install/Boot/Login
1

Hey!

For the past two days, I have been trying to install OpenSUSE E20 onto my ***RPi3 ***on a ***USB ***stick. I have been following the instructions from the wiki, and I both tried the Etcher way and the terminal way, and have tried all images available on the page.

  • For Leap, I don’t have any video signal.
  • For Tumbleweed (both versions) the Pi boots the first time expands the partition, but then times out on both sda1 and sda3, and enters emergency mode. If I then reboot, U-Boot won’t detect my USB stick anymore.

I would really appreciate any help I can get!

Olivier

2

Hi
Have a look at the HowTo here;
https://forums.opensuse.org/showthread.php/523341-Create-a-USB-Bootable-aarch64-openSUSE-Raspberry-Pi-3

Do you have USB to TTL convertor to connect to the RPI?

3

Hi!

I did a fair bit of Googling and had already read that guide, but after reading:

Subsequent to writing up this How-To, the “non-upstream” branch of openSUSE Tumbleweed was modified to incorporate changes that make the distribution image USB-bootable (!).

I figured that it probably had to be something else since the non-upstream version doesn’t work either. (or it’s a regression).

I do not have a USB to TTL converter, but I can provide screenshots, run commands and post the results, or provide files as needed if it helps!

Thank you!

4

Hi
AFAIK, you still need to check and flip the hardware USB boot in section I. Also sometime the USB device itself can be an issue (slow to recognize), that’s why a USB to TTL cable is needed at times… What is the USB device brand, size etc?

So what version are you using Tumbleweed or Leap 42.2? I just tested 42.2 on SD card, it works fine, I’m downloading Tumbleweed E20 release and will pop that onto a USB device and see how it goes.

5

I am certain that I flipped the USB boot switch on the device. The USB boots the first time though, (Leap only shows a black screen, so Tumbleweed, and Tumbleweed non-upstream are my main concern) and it works fine as a storage device in Raspbian. (It’s a Sandisk Ultra CZ48 256GB USB 3.0)

I have ordered a USB to SATA adapter which will hopefully be delivered within the next hour, and I’ll see how that behaves! I’ll definitely keep you updated.

6

Hi
So, tested via copying the Tumbleweed image to a Patriot USB 3.0 64GB device;

Copying to device;


 xzcat openSUSE-Tumbleweed-ARM-E20-raspberrypi3.aarch64-2017.06.10-Build2.5.raw.xz | dd bs=4M of=/dev/sdb iflag=fullblock oflag=direct
999+1 records in
999+1 records out
4191158272 bytes (4.2 GB, 3.9 GiB) copied, 372.617 s, 11.2 MB/s
sync
sync

System boots up and goes through it’s install routine logged in via serial to setup a user, then logged into the GUI, my monitor is connected HDMI->DVI on a ViewSonic VX924 (1280x1024).

Booting from device on a RPI3 serial output;


Welcome to minicom 2.7.1

OPTIONS: I18n 
Port /dev/ttyUSB0, 09:45:43

Press CTRL-A Z for help on special keys



U-Boot 2017.05 (May 08 2017 - 15:27:50 +0000)

DRAM:  880 MiB
RPI 3 Model B (0xa22082)
MMC:   bcm2835_sdhci: 0
Card did not respond to voltage select!
mmc_init: -95, time 22
** Bad device mmc 0 **
Using default environment

In:    serial
Out:   lcd
Err:   lcd
Net:   Net Initialization Skipped
No ethernet found.
starting USB...
USB0:   Core Release: 2.80a
scanning bus 0 for devices... 6 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
       scanning usb for ethernet devices... 1 Ethernet Device(s) found
Hit any key to stop autoboot:  2 Timeout poll on interrupt endpoint
 0
Card did not respond to voltage select!
mmc_init: -95, time 24

USB device 0:
    Device 0: Vendor:          Rev: PMAP Prod: Patriot Memory
            Type: Removable Hard Disk
            Capacity: 60304.0 MB = 58.8 GB (123502592 x 512)
... is now current device
Scanning usb 0:1...
20731 bytes read in 327 ms (61.5 KiB/s)
Found EFI removable media binary efi/boot/bootaa64.efi
reading efi/boot/bootaa64.efi
731136 bytes read in 406 ms (1.7 MiB/s)
## Starting EFI application at 01000000 ...
Scanning disks on usb...
Scanning disks on mmc...
Card did not respond to voltage select!
mmc_init: -95, time 24
MMC Device 1 not found
MMC Device 2 not found
MMC Device 3 not found
Found 4 disks
Welcome to GRUB!

error: terminal `gfxterm' isn't found.
EFI stub: Booting Linux Kernel...
EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
EFI stub: ERROR: Could not determine UEFI Secure Boot status.
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...

Welcome to openSUSE Tumbleweed 20170610 - Kernel 4.11.3-1-default (ttyS0).

eth0: xxx.xxx.xxx.xxx xxxx::xxxx::xxxx:xxxx::xxxx


localhost login: root
Password:
Have a lot of fun...
localhost:~ #
7

A general suggestion…
Especially if this is an untested (successfully) install image,
Recommend first install should be as simple as possible which means running on an SDCARD.
Only after you’ve verified the image is valid, then try re-configuring or re-installing to point to USB storage.

TSU

8

Sorry about the poor quality, but this is where it messes up for me. Just for reference. My package didn’t arrive, it’ll only be delivered tomorrow, sadly.http://i.imgur.com/Ae4Jxvd.jpg

9

Hard to see, but to me looks like your boot is failing looking or the boot files.
So, if you’re trying to boot from your USB device, then recognizing and reading the file system on the USB device is still a problem.

TSU

10

Well, this is after quite a bit of stuff has already happened (still within the first boot, but the OpenSUSE boot menu already showed up, partition resizing already happened, etc.).

I will try it on an SD card (but I’m fairly certain it’ll work), I will first need to backup my Raspbian for that though. I’m just not quite sure how to do that reliably…

11

On Mon 31 Jul 2017 06:36:01 PM CDT, Doriphor wrote:

tsu2;2832237 Wrote:
> Hard to see, but to me looks like your boot is failing looking or the
> boot files.
> So, if you’re trying to boot from your USB device, then recognizing
> and reading the file system on the USB device is still a problem.
>
> TSU
Well, this is after quite a bit of stuff has already happened (still
within the first boot, but the OpenSUSE boot menu already showed up,
partition resizing already happened, etc.).

I will try it on an SD card (but I’m fairly certain it’ll work), I will
first need to backup my Raspbian for that though. I’m just not quite
sure how to do that reliably…

Hi
OK, so what I did was create the usb device, then it will fail. At
this point enter the root password (linux) in rescue mode and in the
HowTo section III step 3, change the usb device reference to sda
references BUT leave the the other bits the same and rebuild grub;


GRUB_CMDLINE_LINUX=" root=/dev/sda2 disk=/dev/sda resume=/dev/sda3
quiet splash=silent plymouth.enable=0  swiotlb=512,force cma=384M
console=ttyS0,115200n8 console=tty quiet"

grub2-mkconfig -o /boot/grub2/grub.cfg

Then modify /etc/fstab to the sda references;


/dev/sda2 / ext4 noatime,nobarrier 1 1
/dev/sda1 /boot/efi vfat defaults 0 0
/dev/sda3 swap swap defaults 0 0

Reboot and it should finish the setup, I tested a USB 2.0 8GB device
and that worked… maybe a USB 3.0 thing…

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.74-18.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!