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