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, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Am 01.02.2016 um 11:26 schrieb Jimmy PIERRE :

...

On 1 February 2016 at 00:13, Dirk Müller 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!) Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Op maandag 1 februari 2016 13:34:40 schreef Jimmy PIERRE:

On 1 February 2016 at 13:05, Alexander Graf wrote:

...

...

Am 01.02.2016 um 11:26 schrieb Jimmy PIERRE :

...

On 1 February 2016 at 00:13, Dirk Müller 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. -- 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

I also had good success the only problem I am having now is I am stuck in 800x480 resolution the raspberrypi-userland package needs to be uninstalled also and replaced with mesa EGL or you can't get any DE to launch, either way thouh the maximum resolution i can get is 800x480 with any monitor attached, currently i have an old Dell 1280x1024 max resolution screen, which works great at full res when i boot raspbian or ubuntu mate. Oherwise things are great it feels very fast loading apps and booting up. Another note seems sound card is also not being detected either. *sorry Freek i accidentally responded to you only yesterday some how the mailing list email got dropped in my response, anyway sorry if you are seeing this twice :) On Wed, Feb 3, 2016 at 7:25 AM, Freek de Kruijf wrote:

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

...

...

Am 01.02.2016 um 11:26 schrieb Jimmy PIERRE

:

...

...

...

...

On 1 February 2016 at 00:13, Dirk Müller 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: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

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

Hello Dirk, I am using this image here > https://build.opensuse.org/package/binaries/devel:ARM:Factory:Contrib:RaspberryPi2/JeOS-raspberrypi2?arch=armv7l&repository=images and by default it has raspberryi-userland package installed, this is preventing anything graphical from working correctly, if i install LXDE and KDM and i try to log into LXDE it totally hangs and never finishes loading, however if i replace rasperrypi-userland with the Mesa-libEGL packages then i can log in, but either way with or without raspberrypi-userland the highest resolution i can get is 800x480 and I have tried several different monitors some are pure HDMI others I am using a HDMI to DVI adapter, I get the same results regardless of what I plug into, but with Mesa I can at least log and use things, firefox for instance loads etc.. and everything seems quite fast just very low resolution. Second the sound just flat out doesnt work at all, I am using the onboard Raspberry Pi2 sound through the headphone jack, the monitor i normally plug my pi into is an older 1280x1024 dell with DVI to HDMI adapter, so no sound via HDMI for me, the problem is that tumbleweed isnt even seeing the hardware at all, i go into yast and sound and it asks me if i want to probe for hardware, and then it never finds anything, seems pulse nor alsa have any clue there is a sound card present at all. If you can offer me any guidance perhaps I am just truly doing something wrong, but I have been trying to get opensuse to boot on my Raspberry pi2 since I got it a year ago, the only luck i ever had was with 13.1 on my B+ unit, so far on my pi2 its been a dismal experience and I am mostly forced to use either Raspbian or Ubuntu Mate, which is a highly polished experience by comparison. Thanks for any feedback you can offer I would very much prefer to be running opensuse on all of my hardware, I am not a fan of Debian and Ubuntu. On Thu, Feb 4, 2016 at 4:10 AM, Dirk Müller wrote:

Hi Michael,

2016-02-03 21:05 GMT+01:00 Michael Emory Cerquoni :

...

I also had good success the only problem I am having now is I am stuck in 800x480 resolution the raspberrypi-userland package needs to be uninstalled

Do you mean it needs to be *installed* ? Because from what I can see, it is not part of the image.

...

also and replaced with mesa EGL or you can't get any DE to launch, either way thouh the maximum resolution i can get is 800x480 with any monitor attached, currently i have an old Dell 1280x1024 max resolution screen, which works great at full res when i boot raspbian or ubuntu mate. Oherwise things are great it feels very fast loading apps and booting up.

...

Another note seems sound card is also not being detected either.

Which sound card are you using? I have modules both for bcm2709 and for bcm2835 enabled as well as the hifiberry one. Do you expect sound to work via HDMI ?

Thanks, Dirk

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