openSUSE ARM February 2012

arm@lists.opensuse.org

18 participants
20 discussions

[opensuse-arm] openSUSE ARM images
by Joop Boonen 27 Jun '12

27 Jun '12

Hi all, I now have two working openSUSE ARM images. For the Pandaboard and the Toshiba AC100. I wonder if we have a location where these images can be put so people who want to test or help out the openSUSE ARM project? These images can be used for a local native (osc/kiwi) build. Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

9 20

[opensuse-arm] openSUSE on Beagleboard xM
by Guillaume Gardet 06 Mar '12

06 Mar '12

Hi, I downloaded images from : http://download.opensuse.org/repositories/openSUSE:/Factory:/ARM/images/ for the beagleboard xM I managed to boot using this kernel and rootfs but I have no modules loaded and there is nothing in /lib/modules, so I can only use built-in drivers. The thing is I did not used initrd since I am not sure how to handle it. I think initrd has all the kernel modules. Could you tell me how to use the initrd with u-boot, please? Cheers, Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 48

[opensuse-arm] An update about fixed and packages being worked on.
by Joop Boonen 27 Feb '12

27 Feb '12

Hi all, MozillaFireFox 10 will be fixed for ARM with the option --disable-neon. I've already tested this patch for MozillaFirefox 9.0 and I'm building MozillaFirefox 9.0.1 in home:worldcitizen:armv7l . What way would be best to communicate so no double work will be done. An overview of who is fixing what. I've also created a bug report for webkit, as this is not an ARM only bug. https://bugs.webkit.org/show_bug.cgi?id=76798 Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 4

[opensuse-arm] ASUS EEE TRANSFORMER
by George Bratsos 27 Feb '12

27 Feb '12

Hello all, I am planning to buy an ASUS EEE TRANSFORMER TF101-1B141A 16GB. Will i be able to download and install any openSUSE-arm version??? I am new to arm so i want some general information about how to install it or what i must learn and watch out! Thanks in advance -- George Bratsos Etern4L @Freenode http://en.opensuse.org/User:Etern4L http://amb.opensuse.gr http://own.opensuse.gr http://etern4l.wordpress.com -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 6

[opensuse-arm] ARM and Virtualization
by Michal Hrusecky 24 Feb '12

24 Feb '12

Hi, I know we don't use native builds in obs for security reasons and for not working virtualization (kvm, xen), but I was going through FOSDEM videos and what sounded interesting was OpenVZ presentation and the presenter said that OpenVZ works on ARM already. Do you think that OpenVZ would be enough (regarding security) to connect our ARM devices to the public OBS? Is it worth exploring? Did somebody already tried that? -- Michal Hrusecky <Michal(a)Hrusecky.net> -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 2

[opensuse-arm] efika handed to dsterba
by Tomas Cech 23 Feb '12

23 Feb '12

Hi, efika.suse.cz was given to David Sterba from Labs, he's focused on fixing filesystem problems. Best regards, Tomas Cech Sleep_Walker

1 0

[opensuse-arm] Outcome of the round table meeting
by Andrew Wafaa 23 Feb '12

23 Feb '12

We had a round table meeting this morning in the SUSE offices in Nuremberg. The intention of the meeting was to try and get some form of milestones agreed, and work out our next moves and find out what tasks etc need to be done. Several decisions were made: 1.) ARMv7 is the focus. This isn't necessarily news, but we just wanted to reiterate the message. Also the ARMv5 builds are going to have their priorities in the OBS lowered to minimise the build power consumption. We're not deleting them, just not focusing on them; if someone *really* wants v5 builds then best you roll your sleeves up and get stuck in, we will provide support, guidance and encouragement. 2.) We are aiming for 12.2 to have full ARM support. So this means we need to freeze in time for 12.2 RC1, so we can not have any build failures. If there are we need to fix them, but some applications are known not to run on ARM, where these are identified we will just use "ExcludeArch: %arm". This needs to be done by 01June2012 at the latest. 3.) To ensure we can make the deadline we need to make sure that all sources are submitted into Factory via the respective devel projects. This means that we have no source overlays in the openSUSE:Factory:ARM repo. Also that all hacks and "fixes" are discussed with maintainers and either incorporated or better fixes are submitted. We will *NOT* have separate sources or patches for the ARM port, everything will have to be in Factory. 4.) We need to have a reference platform that *ALL* developers can use to verify 12.2 will work, this will be the Pandaboard. This does not mean we will not be supporting other devices, like Snowball, Beagleboard or Origen; they will be available but they may not have gone through the same rigorous tests. We will also look at having XFCE as the reference platform Desktop Environment. Now before anyone starts calling for blood, there were some reasons for refernece platform decision: a.) There are sufficient numbers of Pandaboards for developers to use b.) Pandaboard has the best upstream support out of all the devices c.) We already have Kiwi based images for it d.) XFCE is the only DE that builds almost completely and runs at the moment e.) 2D graphics work out of the box on the Pandaboard 5.) openSUSE's ARM port has gone on a diet. The Geeko is now FATless, this means we no longer have a separate FAT partition for the boot file system. All partitions are now ext3 by default, BTRFS is supported but isn't our default. 6.) The Kiwi generated images will use the OEM format rather than the Live Install format. Basically this means that a user will "dd" the image to the target SD card and then the "second boot" process will kick in when a user boots from the card so that they can configure passwords/network/etc and it will repartition to take up the whole of the card. 7.) Bernhard is going to look at integrating ARM support into OpenQA[0]. This means we can get advance notice of breakages etc. prior to releasing images. 8.) We will be triggering a rebuild of the ARM repo to ensure that builds take into account some of the big changes that have happened in Factory (like the Xorg changes), and also to clean out any "fixes" that were applied to the repo. This will most likely be initiated in batches rather than the complete repo, hopefully we can avoid the repo being out of commission for four weeks this way. Another outcome of the meeting was working out some tasks that needed to be completed. There aren't that many tasks and they are open to *EVERYONE* to help out with: I.) We need to keep a closer eye on the package failures. Using Dirk's Build Comparison page[1] will help to isolate failures due to qemu. All qemu bugs/issues need to be passed on to either Alexander Graf (agraf) or Andreas Farber (afarber) for fixing. II.) We need to look at YaST's second stage module and see if that will be of use to the ARM port. III.) We really need to re-work the wiki for the ARM port. It needs to be much more detailed as it hasn't been updated in a while. So that gives us three months or 12 weeks to get our house in order. Regards, Andy 0 = http://openqa.opensuse.org/ 1 = http://www.suse.de/~dmueller/arm-buildservice/ -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] OpenSUSE ARM and Raspberry Pi
by Alfio Emanuele 22 Feb '12

22 Feb '12

Hi guys. Maybe you've already heard about it, but recently something apparently cool came to my eyes. A group of British folks from the Cambridge University have built a credit-card-sized computer on top of an ARM CPU, called the "Raspberry Pi". The most impressing fact about this device is its price: 25 and 35 $ (respectively model A and B). Here are some spare specs from their website: - ARM 700Mhz Broadcom CPU - 128 and 256 MB RAM (depending on the model) - 1080p30 playback capabilities - HDMI and composite video output - 3,5 mm audio - 1 and 2 USB ports - an ethernet rj45 connector. For further info give a look at their website http://www.raspberrypi.org/ (specs into FAQs). Now, it has started like another OLPC project: a cheap machine for educational purposes, but because of its price, size and everything is great for industrial purposes too (there's someone at broadcom developing a cheap expansion card that can be used to drive motors, sensors and stuff like that - see http://www.raspberrypi.org/archives/500). Some guys at Fedora have been working on their ARM distribution and will be relasing their Raspberry version tomorrow - http://www.raspberrypi.org/archives/676 There also is a working Debian version with basic software such as LXDE a browser and a Python interpreter. Being interested in writing software for these machines and - first of all - in OpenSUSE, I was wondering if we had software able to run on the Pi. I started looking at the ARM opensuse project and, thanks to miska, I discovered that yes - we have some software ready. In particular the Pi processor is an ARM11 (ARMv6), and we have some compatible ARMv5 packages in the repository, but still not enough to have a nearly complete working desktop system. (There isn't any web browser, is there?) Also, it seems there are no enough ARM machines working to the Build Service to serve this project. I'd be glad to know how every thing's going on, how can I help and what can I do to help openSUSE beat Fedo.... I mean, rock all the way. But, principally, if someone else is interested in it. And, just a note: Because of their price, couldn't a couple more Pi take the place of the PandaBoards? Referring to the campaign, http://pledgie.com/campaigns/16098 With the money, ~415€, you could buy like 10 Pi boards plus SD cards and stuff, but this is just a flash idea) Maybe it's just a fool thought, but I sincerely hope to see a lot of geckos on these little machines. An old man once told me: You have to "... foster the success of Linux everywhere. We want Linux to be successful in a wide range of application domains like server, desktop, or development". Thanks and "have a lot of fun", Alfio. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] subscribe
by Bamvor Jian Zhang 17 Feb '12

17 Feb '12

1 0

[opensuse-arm] Reboot on Pandaboard
by Christian Galeffi 14 Feb '12

14 Feb '12

Hi, I' m using the image from http://download.opensuse.org/repositories/openSUSE:/Factory:/ARM/images/ on my Pandaboard, after restart the bootloader no longer find the boot partition. How can I fix this? Thanks, gallochri -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 6

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

openSUSE ARM February 2012