Just asking if this is only me or it's a wider problem: I recently
updated my cubox-i with zypper, pulling in kernel-default-4.4.114, and
after reboot the box boots, but several drivers are missing, so there is
no wired ethernet, no mmcblk, etc.
After booting and waiting for a while, dmesg starts to complain about
driver detection did not finish in time (sadly I don't have the
backtrace at hand, it already went out of the buffer of the serial
For now I worked around the problem this way:
- download the repo-oss (ie. non-update) kernel-default-4.4.76 rpm on an
other machine, copied it to an usb stick
- install the old kernel-default from the usb stick
- copy the /boot from the root fs to the usb stick
- use the other machine to update the /boot on the mmcblk device where
u-boot reads it
So is this only me or do other cubox-i users see the same?
For Leap 15.x on x86_64, images (Live media, JeOS and the base container) are
continuously rebuilt, tested and published in openSUSE:Leap:15.x.
It's also the location the official opensuse/leap base image is released from
Currently there is a similar project for :ARM at openSUSE:Leap:15.1:ARM:Live,
but it does not support building/releasing after the main project is finalized
and is also not coupled to openQA AFAICT.
As I'd like to have the base container setup the same for all archs (continuous
testing and updates is a requirement) it would be very useful to use the same
setup as x86_64 Leap. What's missing is a subproject :ToTest with similiar
config to openSUSE:Leap:15.1:Images:ToTest and some mostly trivial changes to the
It might also require some mapping changes inside OBS so that the released
images end up in the right location on download.opensuse.org.
Once that's done, some openQA tests for the JeOS-EFI flavor could be added and
that would then also run the docker_ and podman_image tests.
What do you think?
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org