Raspberry Pi Image

Hi there,
I need to upgrade the installation of a quite old Raspberry Pi (1, model B).
Looking at the dedicated page, I see that the downstream kernel images are regularly updated but are listed only for the armv7l architecture, while the Raspberry 1 is armv6hl so these can’t be used:

Index of download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi/images/
[ICO]    Name    Last modified    Size    Metadata
[DIR]    Parent Directory         -      
 ]    openSUSE-Tumbleweed-ARM-E20-raspberrypi.armv7l.raw.xz    27-Nov-2017 00:49     641M     Details
 ]    openSUSE-Tumbleweed-ARM-E20-raspberrypi.armv7l.raw.xz.sha256    27-Nov-2017 00:49     670     Details
 ]    openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv7l-2017.11.22-Build1.3.packages    27-Nov-2017 01:57     45K     Details

At the same time, looking for the upstream images, these are also for the right architecture:

Index of download.opensuse.org/ports/armv6hl/tumbleweed/images/
[ICO]    Name    Last modified    Size    Metadata
[DIR]    Parent Directory         -      
 ]    openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2017.05.23-Build1.1.raw.xz    23-May-2017 08:22     222M     Details
 ]    openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2017.05.23-Build1.1.raw.xz.sha256    23-May-2017 08:22     671     Details
 ]    openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-Current.raw.xz    23-May-2017 08:22     222M     Details
 ]    openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-Current.raw.xz.sha256    23-May-2017 08:22     671     Details
 ]    openSUSE-Tumbleweed-ARM-JeOS.armv6-rootfs.armv6l-2017.05.23-Build1.1.tbz    23-May-2017 07:21     258M     Details
 ]    openSUSE-Tumbleweed-ARM-JeOS.armv6-rootfs.armv6l-2017.05.23-Build1.1.tbz.sha256    23-May-2017 07:21     669     Details
 ]    openSUSE-Tumbleweed-ARM-JeOS.armv6-rootfs.armv6l-Current.tbz    23-May-2017 07:21     258M     Details
 ]    openSUSE-Tumbleweed-ARM-JeOS.armv6-rootfs.armv6l-Current.tbz.sha256    23-May-2017 07:21     669     Details
 ]    openSUSE-Tumbleweed-ARM-JeOS.armv6-rootfs.armv7l-2017.11.22-Build1.6.tbz    26-Nov-2017 18:09     270M     Details
 ]    openSUSE-Tumbleweed-ARM-JeOS.armv6-rootfs.armv7l-2017.11.22-Build1.6.tbz.sha256    26-Nov-2017 18:09     665     Details
 ]    openSUSE-Tumbleweed-ARM-JeOS.armv6-rootfs.armv7l-Current.tbz    26-Nov-2017 18:09     270M     Details
 ]    openSUSE-Tumbleweed-ARM-JeOS.armv6-rootfs.armv7l-Current.tbz.sha256    26-Nov-2017 18:09     665     Details

What am I missing?

Many thanks in advance,
Best regards

You’re likely looking at the wrong HCL page for your model RPi.
There are different pages for the original/zero RPi, The RPi 2 and the RPi3.

The following page is for your model, and all image links should point to ARMv6 builds



…no, he is right, follow the link you posted:

“Installing openSUSE images using downstream kernel (includes hardware video decoding)”

there you find a link to arm7 images. No joke.

The upstream JeOS is arm6 dated 23-MAY-2017…

Upon closer inspection, there is more to the problem. Looks like maybe a bigger mistake was made and ARMv6 aren’t available at the moment


The individual downstream inks give me

Access forbidden!

        You don't have permission to access the requested object.     It is either read-protected or not readable by the server.      

If you think this is a server error, please contact the webmaster.
Error 403

…all of them.

So I’ll wait patiently for news about the right images… I’ll stay tuned

Thanks again for your support
Best regards

Just now checked,
And the problem has been resolved, ARMv6 (the proper files) are there, now.



Wow, then you have private internet! On my internet there is still

Access forbidden! You don’t have permission to access the requested object. It is either read-protected or not readable by the server.
If you think this is a server error, please contact the webmaster.
Error 403 download.opensuse.org
Tue Nov 28 07:42:20 2017
Apache/2.2.34 (Linux/SUSE)

for the downstream images…

It was correct yesterday when I checked.
Checking now, it looks like the files are incorrect again.

BTW - I originally reported this problem yesterday, you can add a comment if you wish but I’ve already given it a “Critical” rating so should be getting highest priority.


many thanks for your support!
I’ll stay tuned on the bug.

Thanks again,
Best regards