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