Op donderdag 8 september 2016 08:14:01 schreef Roger Oberholtzer:
On Thu, Sep 8, 2016 at 1:54 AM, Stefan Bruens
wrote: Aside from the ext4 problems, the JeOS RPi3 aarch64 image works, tested myself. You can either (after writing the image to the SD) modify the ext4 partition to disable the 64bit feature, or use an image with a patched U-Boot which supports the 64bit feature.
I cannot get either image to work. I do have a number of other images (non openSUSE) and they all work. I am fairly certain I know what I am doing with respect to getting an image installed and accessing the device. All my working images get an IP address from my DHCP server and are available as expected. I was happy to see that one of the OS images even advertised itself with Avahi. They just work.
But the openSUSE images are a different matter. I do not even see it request a DHCP address (DHCPDISCOVER).
Since I only have the 4 USB ports, I cannot see what the console is telling.
There is a problem with the current image, openSUSE-Tumbleweed-ARM-JeOS- raspberrypi3.armv7l-2016.08.20-Build1.4.raw.xz, and that problem now also exists after updating an older version of the RPI3 image. I used openSUSE- Tumbleweed-ARM-JeOS-raspberrypi3.armv7l-2016.06.28-Build1.5.raw.xz and did a "zypper up" after which I again only get the colored screen, where, without the update, the system was running properly. So I am waiting for the newer image and updated Tumbleweed repository. -- 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