Hi, Am 26.07.2018 um 15:25 schrieb Sten Bert:

I'm referring to: https://en.opensuse.org/HCL:Raspberry_Pi3  -> "USB key installation method" -> 2. Copy the firmware and bootloader ... [snip]

You do realize that this is marked as advanced installation technique? I'd recommend you start with our ready-made JeOS-raspberrypi3 SD card image (use osc getbinaries to obtain the very latest version, search list archives). You will then see which files are currently needed on the FAT partition, which includes raspberrypi-firmware-dt package now. It'll also let you determine whether you need to blacklist anything; note that for iso installation you may need to set the cma= parameter. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Op donderdag 26 juli 2018 17:14:38 CEST schreef Sten Bert:

Thank you for the fast reply! Of course. - But that was the only path that was working rudimental and promised a similar way as on x86-PC. The section marked as(easiest)dind't work at all- rainbow screen! Maybe there's a hint missing about the preparation of the sd-card?

You may need to clear the highest blocks on the SD card. I use in bash: dev=sdX ssize=$(/usr/sbin/blockdev --getss /dev/$dev) [ $ssize -ne 512 ] && echo "Sector size not equal 512" && exit 1 size=$(/usr/sbin/blockdev --getsz /dev/$dev) dd if=/dev/zero of=/dev/$dev obs=1 seek=$(($size - 2)) count=2 -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

I think it lacks on an "openSUSE account for https://build.opensuse.org". Andreas assumed, that I have one. I need a little time. Originally I was looking for an actual rpi image in a released version/ official repo's. Regards Am 26.07.18 um 17:39 schrieb Alessio Adamo:

Did you set/check your credentials in ~/.config/osc/oscrc?

See also https://en.opensuse.org/openSUSE:OSC

Alessio

2018-07-26 17:14 GMT+02:00 Sten Bert :

...

Thank you for the fast reply! Of course. - But that was the only path that was working rudimental and promised a similar way as on x86-PC. The section marked as(easiest)dind't work at all- rainbow screen! Maybe there's a hint missing about the preparation of the sd-card?

Never worked withOBScommand line tools. ------------------------------------------------------- osc ls Server returned an error: HTTP Error 401: Unauthorized ------------------------------------------------------- Trying to get someuseful results from the list archives with your hints ...

Regards, Sten

Am 26.07.18 um 16:17 schrieb Andreas Färber:

...

Hi,

Am 26.07.2018 um 15:25 schrieb Sten Bert:

...

I'm referring to: https://en.opensuse.org/HCL:Raspberry_Pi3 -> "USB key installation method" -> 2. Copy the firmware and bootloader ... [snip]

You do realize that this is marked as advanced installation technique?

I'd recommend you start with our ready-made JeOS-raspberrypi3 SD card image (use osc getbinaries to obtain the very latest version, search list archives). You will then see which files are currently needed on the FAT partition, which includes raspberrypi-firmware-dt package now. It'll also let you determine whether you need to blacklist anything; note that for iso installation you may need to set the cma= parameter.

Regards, Andreas

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 27.07.18 11:19, Sten Bert wrote:

Freek,

Unfortunally - no success! Her'e my outputs:

./sd-card.sh 2+0 records in 1024+0 records out 1024 bytes (1.0 kB, 1.0 KiB) copied, 0.00331344 s, 309 kB/s

# df -h /dev/sdf1 Filesystem      Size  Used Avail Use% Mounted on /dev/sdf1        31G   16K   31G   1% /run/media/root/A402-8523

# xzcat openSUSE-Leap42.3-ARM-JeOS-raspberrypi3.aarch64-2017.07.26-Build1.1.raw.xz | dd bs=4M of=/dev/sdf1 iflag=fullblock oflag=direct; sync

of= needs to be /dev/sdf, not /dev/sdf1 :).

383+1 records in 383+1 records out 1607467008 bytes (1.6 GB, 1.5 GiB) copied, 136.038 s, 11.8 MB/s

# df -h /dev/sdf1 Filesystem      Size  Used Avail Use% Mounted on /dev/sdf1        31G   16K   31G   1% /run/media/root/A402-8523

Shouldn't be a difference there before/after?

Please also make sure you do not have any file system mounted when you do the dd. Otherwise an unmount afterwards might corrupt the newly written file system. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Alex - thank you for your little hints, /dev/sdf1 was choosen, 'cause /dev/sdf got me into the rainbow-screen (desperately!) After dd-ing the card automount(?) gets me 2 mounts in the filemanager: ROOT, EFI. What else should I do, than umount them? (openSUSE-Leap42.3-ARM-JeOS-raspberrypi3.aarch64-2017.07.26-Build1.1.raw.xz) The filesystem isn't destroyed, when I look a the card the next time.

...

I have a perfectly running system with this image. Indeed /dev/sdf1 needs to be /dev/sdf, there will be two partitions on the SD card and a lot of unused space.<<

Freek - are you talking about the RPi3b+? I have the actual (this year - 2018) board RPi3B+ and I'm looking for an (openSUSE!)image, that at least boots this board! From http://download.opensuse.org/ports/aarch64/ I took different xz-Images (15.0 JeOS, 15.0 LXQT, 42.3 JeOS). - They all produce different sd-card partition layouts! But none of them boots a RPi3B+! How can I get this running? Regards ... Am 27.07.18 um 11:38 schrieb Alexander Graf:

On 27.07.18 11:19, Sten Bert wrote:

...

Freek,

Unfortunally - no success! Her'e my outputs:

./sd-card.sh 2+0 records in 1024+0 records out 1024 bytes (1.0 kB, 1.0 KiB) copied, 0.00331344 s, 309 kB/s

# df -h /dev/sdf1 Filesystem      Size  Used Avail Use% Mounted on /dev/sdf1        31G   16K   31G   1% /run/media/root/A402-8523

# xzcat openSUSE-Leap42.3-ARM-JeOS-raspberrypi3.aarch64-2017.07.26-Build1.1.raw.xz | dd bs=4M of=/dev/sdf1 iflag=fullblock oflag=direct; sync of= needs to be /dev/sdf, not /dev/sdf1 :).

...

383+1 records in 383+1 records out 1607467008 bytes (1.6 GB, 1.5 GiB) copied, 136.038 s, 11.8 MB/s

# df -h /dev/sdf1 Filesystem      Size  Used Avail Use% Mounted on /dev/sdf1        31G   16K   31G   1% /run/media/root/A402-8523

Shouldn't be a difference there before/after? Please also make sure you do not have any file system mounted when you do the dd. Otherwise an unmount afterwards might corrupt the newly written file system.

Alex

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Op zondag 29 juli 2018 17:20:32 CEST schreef Sten Bert:

Alex - thank you for your little hints,

/dev/sdf1 was choosen, 'cause /dev/sdf got me into the rainbow-screen (desperately!) After dd-ing the card automount(?) gets me 2 mounts in the filemanager: ROOT, EFI. What else should I do, than umount them? (openSUSE-Leap42.3-ARM-JeOS-raspberrypi3.aarch64-2017.07.26-Build1.1.raw.xz) The filesystem isn't destroyed, when I look a the card the next time.

...

...

I have a perfectly running system with this image. Indeed /dev/sdf1

needs to be /dev/sdf, there will be two partitions on the SD card and a lot of unused space.<<

Freek - are you talking about the RPi3b+? I have the actual (this year - 2018) board RPi3B+ and I'm looking for an (openSUSE!)image, that at least boots this board! From http://download.opensuse.org/ports/aarch64/ I took different xz-Images (15.0 JeOS, 15.0 LXQT, 42.3 JeOS). - They all produce different sd-card partition layouts! But none of them boots a RPi3B+!

No I wasn't. Sorry I missed the + in your subject. Still you always have to dd to the whole disk, so /dev/sdf; not /dev/sdf1, when you use an image. If I understand the message from Andreas correctly, you can use the image for Tumbleweed or Leap 15.0, which you apparently already have. However after dd- ing, you do "mount /dev/sdf1 /mnt". In /mnt/ there is a file extraconfig.txt or you create that file and enter a line "arm_control=0x200", most likely without the "'s. After "umount /mnt", you put the SD in the RPi3B+ and boot. That should do the trick. Good luck. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

In the case of Tumbleweed, you can download the latest images with the following command: $ osc getbinaries openSUSE:Factory:ARM:Live JeOS:JeOS-raspberrypi3.aarch64 images aarch64 Depending on the flavor, just substitute JeOS with E20, KDE, XFCE, LXQT, X11 For Leap: $ osc getbinaries openSUSE:Leap:15.0:Ports:Live JeOS:JeOS-raspberrypi3.aarch64 images_arm aarch64 2018-07-30 7:33 GMT+02:00 Sten Bert :

Thank you guys for the replies!

Andreas, when I write "But none of them boots a RPi3B+!", that means - I've tested these appliances!

Here's my result for Leap 15.0 from http://download.opensuse.org/ports/aarch64/distribution/leap/15.0/appliances...: xzcat openSUSE-Leap15.0-ARM-JeOS-efi.aarch64-2018.07.02-Buildlp150.1.1.install.tar.xz | dd bs=4M of=/dev/sdf iflag=fullblock oflag=direct; sync 114+1 records in 114+1 records out 479426560 bytes (479 MB, 457 MiB) copied, 40.2379 s, 11.9 MB/s

- left an unpartitioned medium - not booting (that's logical):

# fdisk -l /dev/sdf Disk /dev/sdf: 30.2 GiB, 32395755520 bytes, 63272960 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes

.. for TW (hope t h i s is the current version): xzcat openSUSE-Tumbleweed-ARM-JeOS-efi.aarch64-2018.05.11-Build1.1.install.tar.xz | dd bs=4M of=/dev/sdf iflag=fullblock oflag=direct; sync 114+1 records in 114+1 records out 479426560 bytes (479 MB, 457 MiB) copied, 40.2379 s, 11.9 MB/s

- same as above

openSUSE-Leap15.0-ARM-LXQT-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz

- booted after activating 1st partition as active, but stopped with "incompatible licence, Press any key to continue" - with and without extraconfig.txt

OBS search gives me 6 pages of result and "osc ls openSUSE:Tumbleweed" has no results. Please excuse my weak knowledge about OBS. As I had to move from SUSE STUDIO - this stuff is new for me.

Regards Sten

Am 29.07.18 um 20:10 schrieb Freek de Kruijf:

...

Op zondag 29 juli 2018 17:20:32 CEST schreef Sten Bert:

...

Alex - thank you for your little hints,

/dev/sdf1 was choosen, 'cause /dev/sdf got me into the rainbow-screen (desperately!) After dd-ing the card automount(?) gets me 2 mounts in the filemanager: ROOT, EFI. What else should I do, than umount them?

(openSUSE-Leap42.3-ARM-JeOS-raspberrypi3.aarch64-2017.07.26-Build1.1.raw.xz) The filesystem isn't destroyed, when I look a the card the next time.

...

...

I have a perfectly running system with this image. Indeed /dev/sdf1

needs to be /dev/sdf, there will be two partitions on the SD card and a lot of unused space.<<

Freek - are you talking about the RPi3b+? I have the actual (this year - 2018) board RPi3B+ and I'm looking for an (openSUSE!)image, that at least boots this board! From http://download.opensuse.org/ports/aarch64/ I took different xz-Images (15.0 JeOS, 15.0 LXQT, 42.3 JeOS). - They all produce different sd-card partition layouts! But none of them boots a RPi3B+!

No I wasn't. Sorry I missed the + in your subject. Still you always have to dd to the whole disk, so /dev/sdf; not /dev/sdf1, when you use an image.

If I understand the message from Andreas correctly, you can use the image for Tumbleweed or Leap 15.0, which you apparently already have. However after dd- ing, you do "mount /dev/sdf1 /mnt". In /mnt/ there is a file extraconfig.txt or you create that file and enter a line "arm_control=0x200", most likely without the "'s. After "umount /mnt", you put the SD in the RPi3B+ and boot. That should do the trick.

Good luck.

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Am 30.07.18 um 20:42 schrieb Andreas Färber:

Am 30.07.2018 um 07:33 schrieb Sten Bert:

...

Here's my result for Leap 15.0 from http://download.opensuse.org/ports/aarch64/distribution/leap/15.0/appliances...:

xzcat openSUSE-Leap15.0-ARM-JeOS-efi.aarch64-2018.07.02-Buildlp150.1.1.install.tar.xz | dd bs=4M of=/dev/sdf iflag=fullblock oflag=direct; sync .tar.xz != .raw.xz And that's not a -raspberrypi3 image either.

If you dd the wrong file it can't possibly work. :)

...

openSUSE-Leap15.0-ARM-LXQT-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz

- booted after activating 1st partition as active, but stopped with "incompatible licence, Press any key to continue" Don't understand what exactly you're doing there and where exactly you're seeing that message.

...

- with and without extraconfig.txt If it boots, you don't have to touch extraconfig.txt. You only need that if ubootconfig.txt with that contents is missing (it was moved from one file to another and - Murphy's Law - the Tumbleweed image got published in between).

Cheers, Andreas

P.S. Please don't top-post. SUCCESS - SUCCESS - SUCSESS - SUCCESS

Andreas you're so right, taking the "Raspberry3"-named images worked! The challenge was to find out the right image for the RPi3B+ among the plenty of ARM images. Following results for systematic attempts on 2 Raspberry3 images from http://download.opensuse.org/ports/aarch64: Valid for all: arm_control=0x200 is already in config.txt (no extraconfig.txt necessary) 1) Leap 15.0 JeOS: openSUSE-Leap15.0-ARM-JeOS-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz.part - booting to login prompt - wonderful! 2) Leap 15.0 LXQT: openSUSE-Leap15.0-ARM-LXQT-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz - "You are in emergency mode. ..." - Timed out waiting for device dev-disk-by\x2duuid-9982\x2d4ABD.device. - Dependency failed for /boot/efi. - Dependency failed for Local File Systems. - after several attempts - success I have some trouble in the LXQt DE with "libEGL warning: DRI2: failed to authenticate" - but I think this sould ba a separate thread. Alessio, thanks for your help, but unfortunately I could only get JeOS. osc getbinaries openSUSE:Factory:ARM:Live X11:X11-raspberrypi3.aarch64 images aarch64 Server returned an error: HTTP Error 404: Not Found Regards -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

2018-07-30 21:38 GMT+02:00 Sten Bert :

Am 30.07.18 um 20:42 schrieb Andreas Färber:

...

Am 30.07.2018 um 07:33 schrieb Sten Bert:

...

Here's my result for Leap 15.0 from

http://download.opensuse.org/ports/aarch64/distribution/leap/15.0/appliances...:

xzcat

openSUSE-Leap15.0-ARM-JeOS-efi.aarch64-2018.07.02-Buildlp150.1.1.install.tar.xz | dd bs=4M of=/dev/sdf iflag=fullblock oflag=direct; sync

.tar.xz != .raw.xz And that's not a -raspberrypi3 image either.

If you dd the wrong file it can't possibly work. :)

...

openSUSE-Leap15.0-ARM-LXQT-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz

- booted after activating 1st partition as active, but stopped with "incompatible licence, Press any key to continue"

Don't understand what exactly you're doing there and where exactly you're seeing that message.

...

- with and without extraconfig.txt

If it boots, you don't have to touch extraconfig.txt. You only need that if ubootconfig.txt with that contents is missing (it was moved from one file to another and - Murphy's Law - the Tumbleweed image got published in between).

Cheers, Andreas

P.S. Please don't top-post.

SUCCESS - SUCCESS - SUCSESS - SUCCESS

Andreas you're so right, taking the "Raspberry3"-named images worked!

The challenge was to find out the right image for the RPi3B+ among the plenty of ARM images. Following results for systematic attempts on 2 Raspberry3 images from http://download.opensuse.org/ports/aarch64: Valid for all: arm_control=0x200 is already in config.txt (no extraconfig.txt necessary)

1) Leap 15.0 JeOS: openSUSE-Leap15.0-ARM-JeOS-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz.part - booting to login prompt - wonderful!

2) Leap 15.0 LXQT: openSUSE-Leap15.0-ARM-LXQT-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz - "You are in emergency mode. ..." - Timed out waiting for device dev-disk-by\x2duuid-9982\x2d4ABD.device. - Dependency failed for /boot/efi. - Dependency failed for Local File Systems.

- after several attempts - success

I have some trouble in the LXQt DE with "libEGL warning: DRI2: failed to authenticate" - but I think this sould ba a separate thread.

Alessio, thanks for your help, but unfortunately I could only get JeOS. osc getbinaries openSUSE:Factory:ARM:Live X11:X11-raspberrypi3.aarch64 images aarch64 Server returned an error: HTTP Error 404: Not Found

My mistake. My explanation was indeed confusing. The first JeOS should stay, only the one defining the image name should change: JeOS:X11-raspberrypi3.aarch64 JeOS:KDE-raspberrypi3.aarch64 JeOS:XFCE-raspberrypi3.aarch64 And so on Sorry about that. Alessio

Regards

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On Mon 30 Jul 2018 04:33:25 NZST +1200, Andreas Färber wrote:

SLES 15 boots on the B+, so I'd be surprised if Leap 15.0 doesn't.

Be surprised then: it simply doesn't boot. openSUSE-Leap15.0-ARM-JeOS-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz on 32GB microSD card inserted into RPi3B+. Powerup: Green LED flashes twice, stuck, with screen showing Net: No ethernet found. starting USB... USB0: Core release: 2.80a scanning bus 0 for devices... Mouse initialised, keyboard not. Ethernet not connected. Dead end. Tumbleweed, 2 months older, gives the same result. Not very useful. The July raspbian, configured on a microSD card in an RPi2B, works out of the box when inserted into this RPi3B+. Volker -- Volker Kuhlmann http://volker.top.geek.nz/ Please do not CC list postings to me. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

See $SUBJECT - the Leap 15.0 JeOS image fails to boot. openSUSE-Leap15.0-ARM-JeOS-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz dd the .raw to a 16GB micro SD card on a linux desktop computer. Check the config.txt: mount /dev/sd_usb3_uSD2 /mnt -r /mnt/boot/vc/config.txt contains arm_control=0x200 (Ugh, mount point not empty) mount /dev/sd_usb3_uSD1 /mnt/boot/ -r /mnt/boot/config.txt contains arm_control=0x200 The last 2 blocks of the micro SD card are zeroes. Powerup: Green LED flashes briefly, colourwheel screen shows + disappears, stuck, with screen showing Net: No ethernet found. starting USB... USB0: Core release: 2.80a scanning bus 0 for devices... (After over an hour I gave up; it'd be useless anyway if it took that long to boot.) RPi3B+ with USB keyboard + mouse connected, monitor connected, Ethernet not connected, boot from micro SD card. This image is about 6 weeks old and doesn't boot. Can that be made to work? Does anyone know how? Thanks muchly, Volker -- Volker Kuhlmann http://volker.top.geek.nz/ Please do not CC list postings to me. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Am Donnerstag, 16. August 2018, 10:13:16 CEST schrieb Volker Kuhlmann:

See $SUBJECT - the Leap 15.0 JeOS image fails to boot.

openSUSE-Leap15.0-ARM-JeOS-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.ra w.xz

Just for x-check, did you try e.g. the LXQT image? That worked fine for me.... -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Am 16.08.2018 um 09:37 schrieb Volker Kuhlmann:

Tumbleweed, 2 months older, gives the same result. Not very useful.

That's really boring to hear, as it means you're not reading this list! We've explained so many times a) how to download a newer image that works, b) how to fix the old published image to boot. Hint: /boot/efi/*config.txt are the relevant files, not /boot/vc/*. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Am Donnerstag, 16. August 2018, 12:40:06 CEST schrieb Volker Kuhlmann:

I didn't see an explanation of what the different options (JeOS, KDE, E20, LXQT, etc) actually do, and at least for half of them I can't guess.

JeOS: Just engough OS - a very basic system, no graphical desktop (if I remember right) KDE: comes wiht KDE Desktop E20: Enlightenment LXQT: LXQT Desktop ...and so on HTH Axel -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On Thu 16 Aug 2018 23:24:29 NZST +1200, Axel Braun wrote:

JeOS: Just engough OS - a very basic system, no graphical desktop (if I remember right) KDE: comes wiht KDE Desktop E20: Enlightenment LXQT: LXQT Desktop ...and so on

Thanks Axel, but this really needs to be on the download pages, like https://en.opensuse.org/HCL:Raspberry_Pi3 or a link to where those different download versions are explained. Eventually I'll find it, I was pointing out the lack of info in relevant places (or anywhere?), which does not help to encourage people to try leap on their RPi. Volker -- Volker Kuhlmann http://volker.top.geek.nz/ Please do not CC list postings to me. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On Thu 16 Aug 2018 23:22:17 NZST +1200, Alexander Graf wrote:

...

Powerup: Green LED flashes briefly, colourwheel screen shows + disappears, stuck, with screen showing Net: No ethernet found. starting USB... USB0: Core release: 2.80a scanning bus 0 for devices...

This sounds like the U-Boot USB stack is unhappy about something on your USB bus. What devices do you have connected via USB to your RPi3? Can you try to unplug all and see how far you get?

USB mouse and USB keyboard. You're right on the money, without those 2 connected (i.e., no USB devices, no Ethernet and only monitor connected), booting proceeds and initial setup runs (all while the screen is black, bad idea) until the console login prompt shows. It looks like there are some USB keyboards, and then some others. Booting shouldn't hang though. It's a cheap small E-Blue Delgado that I use for initial setups and emergencies. Then I tried a Promate EasyKey-2, and Leap15.0 boots fine with that (and a mouse) connected. However, neither keyboard works during the boot menu (press any key to stop - haha). There are key mapping faults of the E-Blue with raspbian on the console, but not in X11. The Promate is good on the console (no X11 to test). Why does it work with raspbian though? Thanks muchly, Volker -- Volker Kuhlmann http://volker.top.geek.nz/ Please do not CC list postings to me. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Am 17.08.18 um 03:24 schrieb Volker Kuhlmann:

On Thu 16 Aug 2018 23:13:02 NZST +1200, Andreas Färber wrote:

...

That's really boring to hear, as it means you're not reading this list! We've explained so many times a) how to download a newer image that works, b) how to fix the old published image to boot.

Hint: /boot/efi/*config.txt are the relevant files, not /boot/vc/*. I was only really interested in Leap, if I have to use Tumbleweed I'll use raspbian instead. Using ocr commands for another experimental construction isn't a solution if I actually wanted to use the RPi for something that needs to stay online reliably. So I chose b).

As the thing doesn't boot, it obviously needs mounting on another Linux machine (or RPi with a functional OS, but that'd give the same result). Instructions were to add arm_control=0x200, if missing.

# mount /dev/sd_usb3_uSD2 /mnt -r # mount /dev/sd_usb3_uSD1 /mnt/boot/efi -r # find /mnt/ | grep config.txt /mnt/boot/vc/config.txt /mnt/boot/efi/config.txt # grep 0x200 `find /mnt/ | grep config.txt` /mnt/boot/vc/config.txt:arm_control=0x200 /mnt/boot/efi/config.txt:arm_control=0x200

As it's there, there's no need to add. I had said as much. It looks like the problem is elsewhere.

Thanks,

Volker

Volker, seems to be a hardware problem. Just the same image I bootet with no problems: openSUSE-Leap15.0-ARM-JeOS-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz You found out by yourself, that there are different behaviours with different keyboards. - Try to to find the oldest USB-keyboard you can. - Only for installation purposes. For example: I had a 10-12 yr. old HP standard USB-Keyboard. Regards Sten -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 08/17/2018 03:12 AM, Volker Kuhlmann wrote:

On Thu 16 Aug 2018 23:22:17 NZST +1200, Alexander Graf wrote:

...

...

Powerup: Green LED flashes briefly, colourwheel screen shows + disappears, stuck, with screen showing Net: No ethernet found. starting USB... USB0: Core release: 2.80a scanning bus 0 for devices... This sounds like the U-Boot USB stack is unhappy about something on your USB bus. What devices do you have connected via USB to your RPi3? Can you try to unplug all and see how far you get? USB mouse and USB keyboard. You're right on the money, without those 2 connected (i.e., no USB devices, no Ethernet and only monitor connected), booting proceeds and initial setup runs (all while the screen is black, bad idea) until the console login prompt shows.

It looks like there are some USB keyboards, and then some others. Booting shouldn't hang though. It's a cheap small E-Blue Delgado that I use for initial setups and emergencies.

Is there any way to get my hands on one of those in Germany? I doubt it'll be a lot of fun to do remote debugging sessions :).

Then I tried a Promate EasyKey-2, and Leap15.0 boots fine with that (and a mouse) connected.

However, neither keyboard works during the boot menu (press any key to stop - haha). There are key mapping faults of the E-Blue with raspbian on the console, but not in X11. The Promate is good on the console (no X11 to test).

Why does it work with raspbian though?

That one I can explain. In the openSUSE boot flow we make use of 2 different USB stacks: The U-Boot dwg2 USB stack and the upstream Linux dwg2 USB stack. Because the USB hardware in the RPi chip has so many errata, Raspbian ships with yet another USB stack they came up with themselves. And because the Raspberry Pi foundation are the upstream friendly people they are, they don't care the least bit to transfer any knowledge their gained there to the upstream drivers. So in a nutshell, just because something with USB works in Raspbian doesn't mean it works with upstream Linux. OpenSUSE simply uses the upstream support, so we inherit all of its problems. Either way, we should try to figure out what exactly is breaking the devices you have. For me, all keyboards I have work just fine in both stacks. I have heard reports from others about broken HID devices with the RPi though, so there seems to be a pattern. I just simply don't have any breaking devices here to debug. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org