Op maandag 1 februari 2016 14:57:56 schreef Freek de Kruijf: > Op maandag 1 februari 2016 13:34:40 schreef Jimmy PIERRE: > > On 1 February 2016 at 13:05, Alexander Graf <[email protected]> wrote: > > >> Am 01.02.2016 um 11:26 schrieb Jimmy PIERRE > > <[email protected]>: > > >>> On 1 February 2016 at 00:13, Dirk Müller <[email protected]> wrote: > > >>> Hi, > > >>> > > >>>> Please note that Tumbleweed images are currently broken for all > > >>>> flavors and architectures, it seems there is a kiwi (?) change that > > >>>> breaks rootdevice detection. I"ve not find a single image that > > >>>> boots... :-( > > >>> > > >>> ok, documenting findings .. the issue is that mmc_block.ko isn't > > >>> loaded on firstboot inird. my guess is that this is due to hwinfo > > >>> --storage crashing (since recently?). I've seen this both on machines > > >>> where mmc is behind USB and where it is not. > > >> > > >> Greetings, > > >> > > >> Our LUG owns three Raspberry boards PI 2 and have not been capable of > > >> making demonstrations with openSUSE at any of the events that we have > > >> attended since February 2015. > > >> > > >> We see other LUGs with "out of the box distributions", no tweaking, > > >> just burnt the image on SD card et voilà! > > >> > > >> We are more integrators than programmers and are willing to help by > > >> testing and sending reports of what went wrong. For doing that, and by > > >> putting ourselves in the place of the end user, we cannot afford to > > >> include a lot of pre/post commands while other distribution just make > > >> a DD and rock n'Roll. > > >> > > >> Please do tell us if you need us as Guinea pigs so that we can > > >> organise our planning. > > > > > > Thanks a lot for the offer! What we're missing is basically > > > someone/something screaming "broken!" as soon as something breaks in the > > > tree. On x86 we have OpenQA for that, but automating 32bit arm is not > > > that easy unfortunately. > > > > > > If you really mean the offer above, what you could do is to - as soon as > > > the image is fixed again - check whether it still works fibe every week. > > > That way we have a much easier time to find breakage correlations. As it > > > stands today, a regression could as well have been introduced 2 months > > > ago (and they stack!) > > > > Hallo Alex, > > > > Yes, we will help of course! > > > > I will follow the trend and as soon as image is fixed... > > > > Best wishes, > > Jimmy > > I tried both images build today 2016-02-01, from RaspberryPi2 and > RaspberrryPi2: but both do not boot. On the connected HDMI device the > message that nothing is connected disappears, so there is a living HDMI > connection. But I do not see any message from the basic boot system, which > appears when I have a bootable system.
Apparently the messages from the basic boot system have been suppressed. Waiting a little longer shows messages about setting up a swap partition and enlarging the main partition. After a while I was able to enter the system using ssh. This is good news. Thanks for all the efforts. Both the images from RaspberryPi2 and RasberryPi2:Staging can be used and as far as I can see result in the same system. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
