Le 16/03/2016 14:37, Alexander Graf a écrit :

...

Am 16.03.2016 um 14:00 schrieb Freek de Kruijf :

The Tumbleweed repository for RPi2 contains a new kernel 4.1.16. However updating/upgrading to that version of the kernel gives you a NONE-working system. Hm, maybe the device tree didn't get updated?

...

Also the newest images with 2016.03.09 in the name do boot, however a second boot fails. On second boot the system tries to boot via the network. That breakage is my fault, sorry again. It was fixed a few days ago, but we're still waiting for the change to land in Factory or rebuilds...

Fixed u-boot is finally in Factory: https://build.opensuse.org/request/show/369474 Just need to wait for images get rebuilt. Guillaume

Alex

...

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

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

On 17.03.16 03:40, Michael Emory Cerquoni wrote:

Is there any ETA on when a new image should be available?

You can see the current build status for "upstream" images here: https://build.opensuse.org/project/monitor?utf8=%E2%9C%93&commit=Filter%3A&succeeded=1&failed=1&unresolvable=1&broken=1&blocked=1&dispatching=1&scheduled=1&building=1&finished=1&signing=1&pkgname=&repo_factory=1&arch_armv7l=1&project=openSUSE%3AFactory%3AARM&defaults=0 and the status for the RPi2 images (which use a downstream kernel) here: https://build.opensuse.org/project/monitor?utf8=%E2%9C%93&commit=Filter%3A&succeeded=1&failed=1&unresolvable=1&broken=1&blocked=1&dispatching=1&scheduled=1&building=1&finished=1&signing=1&pkgname=&repo_images=1&arch_armv7l=1&project=devel%3AARM%3AFactory%3AContrib%3ARaspberryPi2&defaults=0 Whenever all images inside one repository are finished, they get published to the server. It's hard to put real ETAs on it, the scheduling algorithm works by prioritizing build jobs from repositories that are downloaded the most. We're currently waiting for wpa_supplicant to finish building before the image build can start. With a bit of luck, there may be images available tonight, but no promises :). Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Op donderdag 17 maart 2016 10:11:17 schreef Freek de Kruijf:

Op woensdag 16 maart 2016 14:00:36 schreef Freek de Kruijf:

...

The Tumbleweed repository for RPi2 contains a new kernel 4.1.16. However updating/upgrading to that version of the kernel gives you a NONE-working system.

Also the newest images with 2016.03.09 in the name do boot, however a second boot fails. On second boot the system tries to boot via the network. I start with Build389.1, which I downloaded on March 1st. I do a zypper up from the standard repositories, but I exclude crda, kernel-rpi2 and wireless- regdb as new packages and dtb-bcm2709, elfutils, u-boot-rpi2, and u-boot-tools as updated packages. After that I still have a working/bootable RPi2 system.

After the new version of Tumbleweed came available I used: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-2016.03.09-Build6.3.raw.xz This one is perfect. Also a forced install However starting with Build389.1 and performing a "zypper up" does not result a working system, The update is OK, however the reboot does not work. The error message is about a wrong device tree. After this the system is trying to boot via the network. There is an improvement; the first boot phase works. So the warning is still valid. -- 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