Op donderdag 8 september 2016 00:56:54 schreef Andreas Färber:
Am 07.09.2016 um 21:37 schrieb Freek de Kruijf:
Op woensdag 7 september 2016 14:03:38 schreef Roger Oberholtzer:
I get no activity on the device. No DHCP request. No activity on any of the 4 USB ports (where there should be a console login?).
openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.armv7l-2016.08.20-Build1.4.raw. xz
I tried that one too. Only got a colored screen. From the list I learned that soon there will be one that works. I had a older one from June, which works and I updated that one with "zypper up" and it still works.
IIRC colored screen means the proprietary firmware was loaded okay from the FAT partition. So maybe a problem with config.txt? ext4 should have nothing to do with that symptom.
openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3_aarch64.aarch64-2016.09.06-Buil d6 .1.raw.xz
I don't think that one will ever work on a RPi3.
Why not? I seem to be running a 2016.06.12 image, updated with zypper.
Did not read properly. My apologies. I tried the image 2016.09.06 but first it hanged on a connected USB storage device. After disconnecting the USB device it hangs on "stub: Exiting boot services and installing virtual address map..." After a number of tries with the update of armv7l-2016.06.28 I could isolate the problem to installing raspberrpi-firmware from the main openSUSE repository. As long as I keep the originally installed raspberrpi-firmware the system boots OK after the update. Also installing rapsberrypi-firmware.rpi3 installs the version from the main repository, which results in a non-bootable system which shows the colored screen on the HDMI device. -- 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