February 2013 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] Local ARM JeOS image build fails (kiwi problem?)
by Guillaume Gardet 12 Mar '13

12 Mar '13

Hi, I tried to rebuild factory JeOS-beagle image as usual with : osc build images armv7l JeOS-beagle.kiwi But I get this problem of "$pdev uninitialized" and it increase disk size by 10M and loops again: ******************************************************************* [ 9534s] Feb-28 15:13:32 <1> : Increasing disk size by 10M to: 2011M [ 9534s] . [ 9534s] Feb-28 15:13:32 <1> : EXEC [qemu-img create /usr/src/packages/KIWI-oem/oem/openSUSE-Factory-ARM-JeOS-beagle.armv7l-1.12.1.raw 2011M 2>&1] [ 9534s] Feb-28 15:13:32 <1> : EXEC [/sbin/losetup -f --show /usr/src/packages/KIWI-oem/oem/openSUSE-Factory-ARM-JeOS-beagle.armv7l-1.12.1.raw 2>&1] [ 9534s] Feb-28 15:13:32 <1> : EXEC [bash -c "PATH=$PATH:/sbin which parted" 2>&1] [ 9534s] Feb-28 15:13:32 <1> : EXEC [bash -c "PATH=$PATH:/sbin which parted" 2>&1] [ 9534s] Feb-28 15:13:32 <1> : EXEC [dd if=/dev/zero of=/dev/loop0 bs=512 count=1 2>&1] [ 9534s] Feb-28 15:13:32 <1> : EXEC [/usr/sbin/parted -s /dev/loop0 mklabel msdos 2>&1] [ 9535s] Feb-28 15:13:33 <1> : EXEC [/usr/sbin/parted -m /dev/loop0 unit s print | head -n 3 | tail -n 1 | cut -f2 -d:] [ 9535s] Feb-28 15:13:33 <1> : Disk Sector count is: 4118527 [ 9535s] Feb-28 15:13:33 <1> : PARTED input: /dev/loop0 [mkpart primary 2048 411655] [ 9535s] Feb-28 15:13:33 <1> : EXEC [/usr/sbin/parted -s /dev/loop0 unit s mkpart primary 2048 411655 2>&1] [ 9536s] Feb-28 15:13:34 <1> : EXEC [bash -c "PATH=$PATH:/sbin which parted" 2>&1] [ 9536s] Feb-28 15:13:34 <1> : EXEC [/usr/sbin/parted -m /dev/loop0 unit s print | grep :2048 | cut -f3 -d:] [ 9536s] Feb-28 15:13:34 <1> : PARTED input: /dev/loop0 [mkpart primary 411656 4118527] [ 9536s] Feb-28 15:13:34 <1> : EXEC [/usr/sbin/parted -s /dev/loop0 unit s mkpart primary 411656 4118527 2>&1] [ 9537s] Feb-28 15:13:34 <1> : PARTED input: /dev/loop0 [set 1 type 0x83] [ 9537s] Feb-28 15:13:34 <1> : EXEC [/usr/sbin/parted -s /dev/loop0 unit s set 1 type 0x83 2>&1] [ 9537s] Feb-28 15:13:35 <1> : PARTED input: /dev/loop0 [set 2 type 0x83] [ 9537s] Feb-28 15:13:35 <1> : EXEC [/usr/sbin/parted -s /dev/loop0 unit s set 2 type 0x83 2>&1] [ 9537s] Feb-28 15:13:35 <1> : PARTED input: /dev/loop0 [set 1 boot on] [ 9537s] Feb-28 15:13:35 <1> : EXEC [/usr/sbin/parted -s /dev/loop0 unit s set 1 boot on 2>&1] [ 9537s] Feb-28 15:13:35 <1> : EXEC [/sbin/kpartx -a /dev/loop0 2>&1] [ 9537s] Use of uninitialized value $pdev in concatenation (.) or string at /usr/share/kiwi/modules/KIWIBoot.pm line 5872. [ 9537s] Feb-28 15:13:35 <1> : EXEC [blockdev --getsize64 2>&1] [ 9538s] Feb-28 15:13:36 <1> : EXEC [sync] [ 9539s] Feb-28 15:13:37 <1> : EXEC [sync] [ 9539s] Feb-28 15:13:37 <1> : EXEC [kpartx -d /dev/loop0 2>&1] [ 9539s] Feb-28 15:13:37 <1> : EXEC [losetup -d /dev/loop0 2>&1] [ 9539s] Feb-28 15:13:37 <1> : Increasing disk size by 10M to: 2021M [ 9539s] . ******************************************************************* Seems a kiwi problem to me. Anybody has this error too? Any idea to solve this? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 17

[opensuse-arm] U-boot from factory is KO
by Guillaume Gardet 08 Mar '13

08 Mar '13

Hi, I wanted to test latest u-boot for beagleboard (we currently use an old linaro u-boot for beagleboard). And I found some problems about ext2 to ext4 transition (due to u-boot update I guess). First error is in mlo-ext2.patch in spl/Makefile: +LIBS-$(CONFIG_SPL_FAT_SUPPORT) += fs/ext2/libext2fs.o should be replaced with: +LIBS-$(CONFIG_SPL_FAT_SUPPORT) += fs/ext4/libext4fs.o otherwise, we have a build error since ext2 does not exist! Once fixed, boot from MMC hangs early because "ext4fs_set_blk_dev" function is misused. We are using: err = ext4fs_set_blk_dev(&mmc->block_dev, CONFIG_SYS_MMC_SD_FAT_BOOT_PARTITION); But arg number 2 must be "disk_partition_t *info" and not "int" as it was the case for ext2fs_set_blk_dev! Alex, could you have a look at it? According to the *.changes files, you are the best to fix it! ;) Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 3

[opensuse-arm] Re: AArch64 status and Debian/Ubuntu announcement
by Alexander Graf 06 Mar '13

06 Mar '13

On 27.02.2013, at 09:49, Guillaume Gardet wrote: > > Le 27/02/2013 09:33, Dirk Mueller a écrit : >> Hi Guillaume, >> >> Look at devel:ARM:AArch64:12.3, we have around 1500 packages as well. No image yet though. > > Oh, 2113 packages in succeeded state! Awesome! Too bad that we have no image yet. > I guess kiwi need some hack to get AArch64 image? > >> >> The plan was to do an announcement about the state today. Too bad that Debian was faster :-( > > Indeed but if we say: 2113 packages built, it is not so bad. :) > >> >> Any help with the announcement for s greatly appreciated. > > Not too much time today but I will try to give some help about that. Any etherpad or wiki page for collaboration? Email should be fine. Let's take the text below as a starting point. We really need to get this out this week or on Monday. Jos, I would greatly appreciate any help you could provide. openSUSE on AArch64 openSUSE is joining the crowd of 64 bit enabled ARM distributions. Within the past few months, the openSUSE team has worked very hard to get openSUSE up and rolling on ARM's new 64 bit capable architecture. By now, about 2400 packages built successfully. This is more than one third of the whole distribution. From all we know it's also more successful package builds than any other Linux distribution has on AArch64! If you'd like to see the status yourself, please check out the OBS repository we created for this [0]. As an open distribution, we also worked really hard to enable contributors to easily participate in the effort. For this, we extended osc (the OBS command line client) to automatically spawn a Foundation Model [1] virtual machine when you want to build for aarch64. More information on this is available on the respective wiki page [2]. Our next big milestone is going to he a working JeOS image - complete with YaST, openssh and everything you need for a simple and small system. We will create that using our standard image building tool kiwi and provide a ready-made image for the Foundation Model. Stay tuned! If all of the above got you curious and / or you would like to participate in this awesome effort, please join us on the openSUSE-ARM mailing list [3]. There is a lot of fun work to do and and you like open open source work, you are guaranteed to feel right at home. Your openSUSE ARM team [0] https://build.opensuse.org/project/show?project=devel%3AARM%3AAArch64%3A12.3 [1] http://www.arm.com/products/tools/models/fast-models/foundation-model.php [2] http://en.opensuse.org/Portal:ARM/AArch64 [3] http://lists.opensuse.org/opensuse-arm/-- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

8 28

Re: [opensuse-arm] Beagleboard XM freezes; suspect USB issue
by lists＠lazygranch.com 04 Mar '13

04 Mar '13

Actually, I haven't tried the patch. The instructions are not detailed enough for me to use. The person who wrote has "issues" and isn't helpful. Let's leave it at that. If anyone can explain in detail how to patch a kernel, I'm willing to try it. Otherwise, my beagleboard XM is useless. It will crash in 5 minutes or 5 hours. They are willing to RMA the unit for the exact same flawed design. But all that means is the lockup issue might be less frequent, but still be there. That to me is a reliability issue anyone buying a Beagleboard XM will face. Maybe instead of crashing daily it would crash weekly or monthly. Given that this is a hardware bug, I believe all Beagleboard XMs have this problem. But some worse than others. FWIW, it seems Ubuntu runs longer than Opensuse. Not so with Fedora. It crashes as fast as openuse. Ubuntu 12.04 yielded diagnostics on the serial port and in fact returned control to the serial port instead of crashing. That is how it was determined that the USB chip was the problem. Ubuntu 12.10 does not return control to the serial port. It just crashes and has to be rebooted to use again. This makes me think they patched the kernel and the patch is not sufficient in totally fixing the problem. Another issue is the Beagleboard XM under openuse cannot be rebooted with init 6. It just shuts down. Ubuntu can reboot the hardware. Canonical doesn't work in the open as much as Fedora or Opensuse, so I don't know how to reach anyone working on the Arm distribution. But clearly they have fixed some bugs and these fixes have not found their way out of the company. ------Original Message------ From: Alexander Graf To: gary Cc: opensuse-arm(a)opensuse.org Subject: Re: [opensuse-arm] Beagleboard XM freezes; suspect USB issue Sent: Feb 25, 2013 5:00 AM On 21.02.2013, at 06:39, gary wrote: > In an effort to figure out this problem, I loaded some other linux distributions. It turns out Ubuntu can recover from this problem rather than lock up. It also provides some useful diagnostics. It turns out the lock up can be (in theory) cured with this patch: > >> https://github.com/RobertCNelson/stable-kernel/blob/v3.7.x/patches/omap_spr… > > Any help on how to apply this patch would be appreciated. Or has the patch already been applied and 12.3 will have the fix? Have you found any particular reason this patch hasn't gone upstream? If no, it might be a good idea to send it yourself. We should easily get it back through the normal Linux stable tree then. I'm quite reluctant to move this only into the openSUSE kernel. That's not how community work should look like :). Alex N§²æìržyéZ)z{.±æ«ë§²æìržz^Ë¬zàN(Ö¶Ø^£ ÞéZ)z{.±æ«ê0êè¥éìºÇš®

4 4

[opensuse-arm] 12.3 release schedule
by Andrew Wafaa 27 Feb '13

27 Feb '13

Aloha all, I've been asked by the guys preping the release announcement for 12.3 about the status fo ARM and if it will be available for release alongside x86. My initial response was to say it will be a few weeks late, but would confirm. Is my assumption correct that we will not have a release in time? Would it be fair to say that the next ARM release will be in the middle of April? Thanks, Andy -- 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

2 1

Re: [opensuse-arm] 12.3 release schedule
by Andrew Wafaa 27 Feb '13

27 Feb '13

Excellent!! Thanks for confirming Dirk. I take it the list of devices supported is the same as 12.2 with the addition of Chromebook and Arndale, are there any others? Regards, Andy On 27 February 2013 09:49, Dirk Müller <dirk(a)dmllr.de> wrote: > Hi Andrew, > > We aim for having a release alongside of 12.3. > > The announcement for 12.3 should say that we do ARM (which can be extended > to ARM64 at a later point in time). For now just including ARM as a first > class openSUSE Port of 12.3 should be in the announcement. > > Greetings, > Dirk > > Am 27.02.2013 10:31 schrieb "Andrew Wafaa" <awafaa(a)opensuse.org>: >> >> Aloha all, >> >> I've been asked by the guys preping the release announcement for 12.3 >> about the status fo ARM and if it will be available for release >> alongside x86. My initial response was to say it will be a few weeks >> late, but would confirm. >> >> Is my assumption correct that we will not have a release in time? >> Would it be fair to say that the next ARM release will be in the >> middle of April? >> >> Thanks, >> >> Andy >> >> -- >> 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 >> > -- 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

Re: [opensuse-arm] Beagleboard XM freezes; suspect USB issue
by lists＠lazygranch.com 26 Feb '13

26 Feb '13

Great. And 12.3 to boot. I will load it in a few hours and see how long it runs. (I suspect we are in different time zones with a pond between us.) Thanks again. ------Original Message------ From: Alexander Graf To: lists(a)lazygranch.com Cc: opensuse-arm(a)opensuse.org Subject: Re: [opensuse-arm] Beagleboard XM freezes; suspect USB issue Sent: Feb 25, 2013 4:05 PM On 25.02.2013, at 19:00, Alexander Graf wrote: > > On 25.02.2013, at 18:50, lists(a)lazygranch.com wrote: > >> Actually, I haven't tried the patch. The instructions are not detailed enough for me to use. The person who wrote has "issues" and isn't helpful. Let's leave it at that. >> >> If anyone can explain in detail how to patch a kernel, I'm willing to try it. > > I guess it's easiest if either Guillaume or me create a special kernel for you to try with that patch applied. I won't get to it before midnight today, but maybe can create one after that tonight that you can give a whirl. My Beagleboard XM is about 2 km away with lots and lots of snow lying in between me and it. :) http://csgraf.de/tmp/omap3/ This is the 12.3 kernel + the patch you posted. Alex

1 0

[opensuse-arm] Beagleboard XM freezes; suspect USB issue
by gary 25 Feb '13

25 Feb '13

I have a Beagleboard XM rev C. I find that applications that work fine on an intel machine under 12.2 cause the Beagleboard XM to freeze. Apparently the Beagleboard has a history of USB issues, which had I known I probably would have gone with the Panda. Since the board locks up, I don't know how to diagnose the problem. There is nothing useful beyond the boot information on the serial port. I have posted the issue to the google groups arm forum, which in turn suggested I go to the opensuse forum to see if there is a way to get diagnostics from the serial port or other means. The programs that cause the lock up are rtl_adsb and dump1090. > https://github.com/antirez/dump1090 > https://github.com/keenerd/rtl-sdr I don't believe the problem is specific to these programs, which run well on intel, but rather it is related to the usb traffic. The freeze can occur in minutes or hours. There is no pattern that I can detect. Suggestions? Anything to dump? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

[opensuse-arm] openSUSE (with XFCE) on Android devices
by Guillaume Gardet 25 Feb '13

25 Feb '13

Hi, here is a post on lizards about openSUSE (with XFCE) on Android devices: https://lizards.opensuse.org/2013/02/20/opensuse-on-phonestablets/ Regards, Guillaume -- 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] Raspberry Repos
by Mathias Tröbs 21 Feb '13

21 Feb '13

Hello there, I installed the latest image from Bernhard which I found here zq1.de/~bernhard/linux/opensuse/raspberrypi-opensuse-20130110.img.gz and put it on a raspberry pi. It is running well! Now I need to install some packages but unfortunately the repo openSUSE:Factory:ARM/armv5el is not there any longer. I'm wondering where I could get some packages for my RPi. Is there any alternative? Mathias -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 2