
After 11 months of grueling work, openSUSE is pleased to announce the first Release Candidate for openSUSE 12.2 on the ARM architecture. After discussing ARM first at the openSUSE Conference in 2011, the openSUSE ARM team has managed to bring up openSUSE from nowhere to being a truly usable and functional distribution on the ARM version 7 architecture in time for the new openSUSE Conference in Prague next month!
Hardware and device support
This RC1 release is focused on ARMv7 which encompasses the Cortex-A processor profile from the Cambridge, UK based chip designer. Due to the current nature of the existing ARM landscape it doesn’t mean that all devices that use a v7 SoC are supported though. As such openSUSE took the engineering decision to focus on a subset of devices to minimize the time it takes to bring the distribution up on the architecture. The supported SoC vendors for this release are Texas Instruments’ OMAP3 & OMAP4 and Freescale I.MX51; the supported devices running with these SoCs are the Beagleboard, Beagleboard-xM, Pandaboard, Pandaboard-ES and the EfikaMX smarttop/smartbook. There is also an image for the VersatileExpress which is suitable for use in Qemu as well as a generic root file system tarball that users and developers may use to help bring up unsupported devices. The images are available from the download section, the .xz archive files contain the full image (filesystem + kernel + initrd) and the .tar.bz do NOT contain a filesystem (kernel + initrd only).
More information
Information for each platform is available on this wiki page and a quick guide on how to get up and running with openSUSE on ARM is available on this page. As with everything that openSUSE does, we invite everyone who is interested in joining in and help make openSUSE the premier distribution for the ARM platform. There is a brief guide on how to submit package fixes for ARM, for those that wish to see what the Action Items and the TODO list are there is a Trello Board which is open to everyone, there are also the usual communications channels of IRC(#opensuse-arm on Freenode) and mailing list (subscription to the list is required, here is the list archive). If you have a device that isn’t currently supported, openSUSE would love to help you get it up and running.
Thanks
The openSUSE-ARM effort has been built using the Open Build Service, leveraging Qemu for emulation of the target architecture, ensuring a single package source for all architectures and simplifying software maintenance. This method has led to numerous bugs being found and subsequently fixed with all fixes submitted upstream to Qemu, OBS, Kiwi as well as many other packages. A native build farm mirrored the OBS environment to verify package failures as well as testing builds. This native farm would not have been possible if it were not for the sponsorship of hardware from Texas Instruments/Pandaboard Project, Genesi, ARM and the openSUSE community.
Both comments and pings are currently closed.



Will it work as chroot environment on Nokia N900?
Theoretically it has TI OMAP 3430, 600 MHz ARM Cortex-A8, so it should work. I’m going to test it.
Anyway good job openSUSE-ARM team!
Tell us if it works ;)
Almost.
Nokia-N900:~ # zypper -v ref
Verbosity: 1
Initializing Target
Specified repositories:
Checking whether to refresh metadata for openSUSE-12.2-ARM
Retrieving: repomd.xml ……………………………..[done]
Repository ‘openSUSE-12.2-ARM’ is up to date.
Building repository ‘openSUSE-12.2-ARM’ cache …………[done]
Error building the cache:
[|] Failed to cache repo (4).
History:
– ‘repo2solv.sh’ ‘-o’ ‘/var/cache/zypp/solv/openSUSE-12.2-ARM/solv’ ‘/var/cache/zypp/raw/openSUSE-12.2-ARM’
rpmmd2solv: repo_rpmmd: unclosed token at line 25897:39
Skipping repository ‘openSUSE-12.2-ARM’ because of the above error.
Could not refresh the repositories because of errors.
On my PC in qemu-powered chroot everything works fine.
Hmm… might see if I can make a Pi of it should mine ever show up. Time to stock up on SD cards, methinks!
What is Marvell armadaXP 510?
Differs from Marvell armada 510? https://origin-www.marvell.com/application-processors/armada-500/
Mention of Marvell Armada in the first version of this news was mistake?
marvell like qualcomm and apple have an architectural license for designing their own cpu.
Any info about toshiba ac100 who use a tegra 2?
I know some people was able to run suse 12.1.
Great work guys. Kudos. Any plan for a Raspberry Pi version?
Yes, a Raspberry Pi version would be really great !
Hi
any chance on having this on asus trnsformer prime (quadcore tegra 3 )
mraix