Op vrijdag 18 december 2015 10:39:46 schreef Freek de Kruijf: > Op donderdag 17 december 2015 09:15:12 schreef u: > > I have had the same experience have had to stop using opensuse on my pi's. > > It is very disappointing from what i can tell there is almost zero > > interest > > from the overall opensuse-arm community for supporting raspberry pi > > hardware properly. > > > > On Dec 17, 2015 7:04 AM, "Freek de Kruijf" <fr...@opensuse.org> wrote: > > > I tested the latest released Tumbleweed image for the Raspberry Pi 2B, > > > Build354.2 which shows a black screen and does not boot at all, same as > > > the > > > latest one from Staging, which is from a few days back. > > > > > > Currently there are no working Tumbleweed images for any of the > > > Raspberry > > > Pi > > > systems. Is there anything I can do, apart from testing the latest > > > images? > > The situation is not that negative. I have Tumbleweed systems running on > both RPi1 and RPi2 started from a working image, some month ago, on which I > am still able to update these to the latest version of Tumbleweed from the > repository. So it seems that the only problem is with the boot system, but > generating a new initrd still works.
The latest update to kernel 4.3.0 for RPi1 ruined the system. It does not start anymore. The error message on the screen said: File not found dtb.bcm2835-rpi-b.dtb -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
