- openSUSE ARM

[opensuse-arm] chroot-ed openSUSE on Samsung Galaxy S2 - howto
by Gábor Nyers 09 Apr '13

09 Apr '13

Hi, I've created this HOWTO on setting up a chroot-ed openSUSE on the Galaxy S2: https://en.opensuse.org/User:Gnyers/openSUSE-12.3-on-SGS2 > This HOWTO describes the steps to get the ARM port of openSUSE working on > the Samsung Galaxy S2. With possible minor changes, the procedure should > also work for any modern and "root"-able Android device. Once set up, > openSUSE will run in a "chroot"-ed environment, which is akin to a very > simple form of virtualization. This means that despite Android and > openSUSE being distinct environments, they will run on the phone side by > side. That is, even while openSUSE is running, the device may be used > normally. Besides the mentioned "root"-ed device requirement, there is no > need for any change to the hardware or in the Android OS. Comments are welcome, but also feel free to correct any technical, spelling or grammar errors, mangled English phrases or add new information to the document. Regards, Gábor -- 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] standard vs qemu repo in Factory
by Adrian Schröter 08 Apr '13

08 Apr '13

In case you do local builds for factory, you need to use the "qemu" repository from now on for factory builds. The "standard" one works only on native hardware. This is valid for armv7 and armv5 builds. Please note that the armv5el packages got merged into "standard" repository also. That means I will remove the old "armv5el" repository in near future. The wiki pages got updated as well to reflect this change. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- 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] missing /dev/fd symlink also hits armv7l builds
by Dirk Müller 04 Apr '13

04 Apr '13

Hi, the "udev is not running" issue that we have on aarch64 is also hitting the armv7l native builds because we do not have /dev/fd available: https://build.opensuse.org/package/live_build_log?arch=armv7l&package=kerne… for now, I add the symlink hack to the build script again but I guess we need a more permanent solution. Do we really want to start udev during the build process? then we need to get a initrd for the guest kernel.. This seems to be blocking the 12.3 kernel update, as that one fails to build. Thanks, Dirk -- 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] Additional information on the Beagleboard XM usb patch
by lists＠lazygranch.com 02 Apr '13

02 Apr '13

This is from the Fedora arm list, perhaps of use for opensuse: ------------------------- One problem with that patch, it will break boot on all omap34xx/35xx based systems. (aka BeagleBoard A/B/Cx's, igepv2's, overo's, etc boards) that share the same kernel image as the xM.. Main thread on the issue/patch is here: http://www.spinics.net/lists/linux-omap/msg64931.html Regards, -- Robert Nelson http://www.rcn-ee.com/ -- 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] Fw: gcc47 for Aarch64
by Valery Reznic 02 Apr '13

02 Apr '13

Hello. I am running openSUSE 12.3 for aarch64 (openSUSE-12.3-AArch64-JeOS-alpha1.raw) and trying to install gcc47 from here: http://download.opensuse.org/repositories/devel:/ARM:/AArch64:/12.3/standar… But this package requires glibc-devel and glibc-devel I am unable to find. I found linux-glibc-devel package but it doesn't help :( So, how can I proceed? Should I install gcc using rpm's --nodeps option or glibc-devel rpm is available somewhere? Unfortunately, cross-compilation is not an option - it will require too many changes. I need install gcc aarch64 native. Thank you. Valery -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 11

[opensuse-arm] Optimisation and porting of assembly code
by Andrew Wafaa 27 Mar '13

27 Mar '13

Hi, Not sure if anyone noticed, but Steve McIntyre of Debian/ARM/Linaro fame has done some long and laborious work scanning packages for Fedora & Ubuntu as part of the Linaro Enterprise Group. He has done a good write up of the exercise[0], and the spreadsheet attached to that wiki page has some interesting info. Is this something worth doing on openSUSE to confirm the findings? Regards, Andy 0 - https://wiki.linaro.org/LEG/Engineering/OPTIM/Assembly -- 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

4 3

[opensuse-arm] CuBox
by Peter Czanik 27 Mar '13

27 Mar '13

Hello, What's the current status of CuBox support? I see that 12.2 should work: https://en.opensuse.org/HCL:CuBox But does 12.3 also support it? Bye, CzP -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 8

Re: [opensuse-arm] chrome
by lists＠lazygranch.com 27 Mar '13

27 Mar '13

Do you have a good source (link) for how to build a distribution for arm? What I would do is just start by building one for the Beagleboard, i.e. known hardware, so as to get my feet wet. I'm trying to walk the line between being a nuisance and being useful. ;-) I'm not sure if anyone has stopped and meditated on the nature of linux and these SBCs versus running linux on a desktop or notebook. For the desktop or notebook, you get it going and don't mess with something that is working. But for these SBCs, a new OS is a cheap SDHC card away. You can actually "have a lot of fun!" ------Original Message------ From: Alexander Graf To: gary Cc: opensuse-arm(a)opensuse.org Subject: Re: [opensuse-arm] chrome Sent: Mar 26, 2013 5:49 PM On 27.03.2013, at 01:35, gary wrote: > Now I understand the Mirabox post. Basically the poster took the package (perhaps not the right word) for arm7, but used a different boot loader, presumably whatever the Mirabox requires. > > Does that mean it is possible to run opensuse on this board? >> http://www.hardkernel.com/renewal_2011/products/prdt_info.php?g_code=G13523… Yes, if you have a working kernel and u-boot for it, it's a matter of throwing our rootfs onto it. It's also fairly similar to the Origen board. So maybe you could even create a working SD card image for the Odroid-X2 based on that one. Please bear in mind that exynos4 support is in abysmal state upstream. I haven't managed to get any recent kernels working at all. Alex

3 2

[opensuse-arm] chrome
by J.Witvliet＠mindef.nl 27 Mar '13

27 Mar '13

Just a simple Q. Can I replace the software of a chromebook by 12.3 Doe these machines have a decent bios that would allow me to select any boot device to boot from: A) internal HD B) external DVD C) external mem-stick Hans ______________________________________________________________________ Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 5

[opensuse-arm] login problem on serial fixed (workarounded)
by Guillaume Gardet 26 Mar '13

26 Mar '13

Hi, for people having problems to login through serial, just remove plymouth: zypper rm plymouth reboot and then your serial backs to normal. I have no idea why but it does fix it. Should we remove plymouth from JeOS/XFCE images? Guillaume -- 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] 12.3 JEOS missing usb patch
by gary 25 Mar '13

25 Mar '13

Just a FYI, the JEOS version of the Beagle 12.3 is missing the usb patch neede for the Beagleboard XM. > http://download.opensuse.org/ports/armv7hl/distribution/12.3/images/ -- 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: Re : Re: [opensuse-arm] omapdrm problem
by Rob Clark 21 Mar '13

21 Mar '13

On Thu, Mar 21, 2013 at 10:37 AM, Tomi Valkeinen <tomi.valkeinen(a)ti.com> wrote: > On 2013-03-21 16:16, Guillaume Gardet wrote: >> >> Le 21/03/2013 15:08, Tomi Valkeinen a écrit : >>> On 2013-03-21 16:00, Guillaume Gardet wrote: >>> >>>> Ping. >>>> Is there any information or things to do to debug it? >>> Can you summarize the problem? I couldn't figure it out from the posts... >> >> On a Beagleboard xM rev. B, omapdrm does not output anything on my >> screen (screen goes in power save mode) with vanilla kernel 3.9-rc1 >> whereas it did work with openSUSE 12.2 kernel (3.4*). >> >> First post with logs: >> http://lists.opensuse.org/opensuse-arm/2013-03/msg00042.html >> * kernel 3.4: omapdrm OK >> * kernel 3.9-rc1 : omapdrm KO > > Ok. I can repro on -rc3 with beagle. > > I applied the attached patches, that have been sent to mailing list. > This seemed to fix it. Can you try them out? I didn't study which of > them actually fixes this issue, though (I don't know much about omapdrm). sorry for late reply.. I'm still in the process of moving and don't have internet at home yet.. I'd have to suspect patch #2 (drm/omap: Fix and improve crtc and overlay manager correlation) is the one improving things. BR, -R > Tomi > -- 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] armv5 build problem
by Guillaume Gardet 21 Mar '13

21 Mar '13

Hi, there is a problem with armv5 builds. Some packages are in failed status whereas all is OK, except build job is killed at the end of the build. Alsa package for example: https://build.opensuse.org/package/live_build_log?arch=armv5el&package=alsa… Any idea what is going on? 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] Re: Beagleboard xM - Bogomips are very low
by Guillaume Gardet 20 Mar '13

20 Mar '13

Le 20/03/2013 13:48, Frank Agius a écrit : > On 3/19/2013 11:17 AM, Guillaume Gardet wrote: >> Hi, >> >> On a Beagleboard xM rev. B, I noticed that vanilla kernel 3.4.6 have the >> folowing bogomips for 300MHz and 800 MHz operations: 262.08 and 700.57. >> >> With kernel 3.7.10, I have : 175.65 and 467.41 bogompis. >> >> Any idea why bogomips are so low now? >> > > I believe this is the reason for the BogoMIPS change: > > http://www.spinics.net/lists/arm-kernel/msg221672.html > > It looks like BogoMIPS reporting changed because of the delay routine patch introduced in 3.6. So the change in BogoMIPS is real, but should not be a concern. Thanks for the pointer. So, it should not affect performances. I will try to bench it, to be sure there is no hidden problem. Thanks. Guillaume > > frank agius > >> Guillaume >> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-omap" in >> the body of a message to majordomo(a)vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> > > -- 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] Volunteers needed : Vnc fails to build for amv7l
by Dirk Müller 20 Mar '13

20 Mar '13

Hi, we got a bugreport (!) :-) Anyone interested in looking at the vnc build failures: https://bugzilla.novell.com/show_bug.cgi?id=799562 Thanks, Dirk -- 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 12.3 builds
by Michal Hrusecky 19 Mar '13

19 Mar '13

Hi guys, I'm trying to build few packages for my ARM board, some of them builds fine for Factory, but since 12.3 released last week, I migrated my boards to 12.3, but my project with 12.3 enable rebuilt everything for Factory, but 12.3 is still in scheduled state for few days... Am I doing something wrong? -- 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 7

[opensuse-arm] Geeko Pumping Iron Session - openSUSE ARM Hackathon 08-12Apr
by Andrew Wafaa 14 Mar '13

14 Mar '13

Now that openSUSE 12.3 is out, the openSUSE ARM Team[0] want to step up a gear. As the cycle was shorter than normal, there are a few wrinkles that need to be ironed out and also a whole heap of new things that can be added. After some discussion at FOSDEM, it was decided to hold a Hackathon to address these items. The Hackathon will take place on 08 to 12 April, both at the SUSE offices in Nuremberg as well as online for those that can't attend in person. We have a TODO list which comprises the following: * AArch64 fixes for 12.3 & Factory * Resolve outstanding 12.3 package issues * Test and release 12.3 images * Create OpenStack images for ARM * Get KVM and Xen on Chromebook & Arndale running * OBS improvements There will also be the opportunity for new device bring up for those that want to, but our intention is to work through and complete as much of the above TODO list as possible first. For those interested in joining in the fun, please either join us in Nuremberg and/or join the opensuse-arm mailing list[1], the #opensuse-arm IRC channel on Freenode[2] and also keep an eye on the openSUSE on ARM Trello board[3]. If you have any questions please let us know on the mailing list or on IRC. 0 - https://en.opensuse.org/Portal:ARM 1 - http://lists.opensuse.org/opensuse-arm 2 - irc://freenode.net/#opensuse-arm 3 - https://trello.com/board/opensuse-on-arm/5007cfc12cf0ae352e21d8dc -- 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] armv5 build broken?
by Guillaume Gardet 12 Mar '13

12 Mar '13

Le 11/03/2013 08:39, Adrian Schröter a écrit : > > On Freitag, 8. März 2013, 17:14:40 wrote Guillaume Gardet: > > > Hi, > > > > > > I just tried a local armv5 build for Factory, and I get this error : > > > > > > [ 7s] running aaa_base preinstall script > > > [ 7s] chroot: failed to run command 'sh': No such file or directory > > > [ 7s] running aaa_base postinstall script > > > [ 7s] chroot: failed to run command 'sh': No such file or directory > > > [ 7s] running qemu-accel-armv5tel postinstall script > > > [ 7s] chroot: failed to run command 'sh': No such file or directory > > > [ 7s] initializing rpm db... > > > [ 7s] chroot: failed to run command '/usr/bin/rpmdb': No such file or directory > > A --clean build just works here. > It does not here. > You may need to manually call /usr/sbin/qemu-binfmt-conf.sh as root, it should > > not be needed though ... > In /var/tmp/build-root, I have no usr/sbin/qemu-binfmt-conf.sh, but: ./usr/bin/qemu-arm: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, for GNU/Linux 2.6.32, BuildID[sha1]=0xbfd9d561bd8b4255f340474425b14f0e94100e46, stripped ./usr/bin/qemu-arm-binfmt: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, for GNU/Linux 2.6.32, BuildID[sha1]=0x3e65f1f3c937d713d77fb712c0f520326b6a1bf1, stripped Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 4

[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] armv5 build broken?
by Guillaume Gardet 11 Mar '13

11 Mar '13

Hi, I just tried a local armv5 build for Factory, and I get this error : [ 7s] running aaa_base preinstall script [ 7s] chroot: failed to run command 'sh': No such file or directory [ 7s] running aaa_base postinstall script [ 7s] chroot: failed to run command 'sh': No such file or directory [ 7s] running qemu-accel-armv5tel postinstall script [ 7s] chroot: failed to run command 'sh': No such file or directory [ 7s] initializing rpm db... [ 7s] chroot: failed to run command '/usr/bin/rpmdb': No such file or directory Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 3

[opensuse-arm] libportaudio
by gary 10 Mar '13

10 Mar '13

I loaded libportaudio2 and got a link libportaudio.so -> /usr/lib/x86_64-linux- Damn, the text got chopped off from my terminal window. But basically link goes to the wrong place. The library does exist in opensuse arm. I created this link: libportaudio.so -> /usr/lib/libportaudio.so.2 I'm a bit prone to "pilot error" not being a programmer, so perhaps someone can check this out. -- 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] 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

Re: [opensuse-arm] Beagleboard XM freezes; suspect USB issue
by Guillaume Gardet 06 Mar '13

06 Mar '13

Le 06/03/2013 10:53, gary a écrit : > This is from fbset. > > mode "1024x768" > geometry 1024 768 1024 768 32 > timings 0 0 0 0 0 0 0 > accel true > rgba 8/16,8/8,8/0,8/24 > endmode > > Of course I'm using SSH, so I don't see the HDMI output. > > So the question here is how does the patch kill the use of the HDMI. It does not. As I said before, current factory kernel has a broken DVI output. Guillaume > > Is there some clever way for me to see if the keyboard is being received by the SBC. [I'm going to use SBC from now on to save me from typing out Beagleboard XM.] > > My setup uses a KVM, so I can easily push the button to use the keyboard or mouse for that matter on the SBC rather than using SSH via "terraterm". [I have opensuse on a notebook, but not on the KVM. My desktop linux motherboard blew out the power supply caps.] > > -- 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] 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

[opensuse-arm] Native ARM build fails with an unknown error
by Guillaume Gardet 06 Mar '13

06 Mar '13

Hi, I am trying a native build for JeOS-beagle from openSUSE:Factory:ARM on my Beagleboard xM (using a 12.2 image) but I get this error: ****************************************************************************************** Verifying integrity of cached packages using keys from openSUSE:Factory:ARM Writing build configuration Running build [Errno 2] No such file or directory ****************************************************************************************** Any idea why? strace give me: ****************************************************************************************** write(1, "Running build\n", 14Running build ) = 14 pipe([7, 8]) = 0 fcntl64(7, F_GETFD) = 0 fcntl64(7, F_SETFD, FD_CLOEXEC) = 0 fcntl64(8, F_GETFD) = 0 fcntl64(8, F_SETFD, FD_CLOEXEC) = 0 clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xb6bc5328) = 2522 close(8) = 0 mmap2(NULL, 1052672, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb5bb3000 read(7, "cexceptions\nOSError\np0\n(I2\nS'No "..., 1048576) = 462 mremap(0xb5bb3000, 1052672, 4096, MREMAP_MAYMOVE) = 0xb5bb3000 close(7) = 0 wait4(2522, [{WIFEXITED(s) && WEXITSTATUS(s) == 255}], 0, NULL) = 2522 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=2522, si_status=255, si_utime=2, si_stime=3} --- stat64("/usr/lib/python2.7/encodings/string_escape", 0xbeb12ce0) = -1 ENOENT (No such file or directory) open("/usr/lib/python2.7/encodings/string_escape.so", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/python2.7/encodings/string_escapemodule.so", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/lib/python2.7/encodings/string_escape.py", O_RDONLY|O_LARGEFILE) = 7 fstat64(7, {st_mode=S_IFREG|0644, st_size=953, ...}) = 0 open("/usr/lib/python2.7/encodings/string_escape.pyc", O_RDONLY|O_LARGEFILE) = 8 fstat64(8, {st_mode=S_IFREG|0644, st_size=2069, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb5cb3000 read(8, "\3\363\r\n\4!OPc\0\0\0\0\0\0\0\0\3\0\0\0@\0\0\0s\242\0\0\0d\0"..., 4096) = 2069 fstat64(8, {st_mode=S_IFREG|0644, st_size=2069, ...}) = 0 read(8, "", 4096) = 0 close(8) = 0 munmap(0xb5cb3000, 4096) = 0 close(7) = 0 write(2, "[Errno 2] No such file or direct"..., 35[Errno 2] No such file or directory) = 35 write(2, "\n", 1 ) = 1 munmap(0xb5bb3000, 4096) = 0 wait4(2522, 0xbeb17af4, WNOHANG, NULL) = -1 ECHILD (No child processes) close(4) = 0 munmap(0xb6f5c000, 4096) = 0 close(5) = 0 munmap(0xb6f5b000, 4096) = 0 close(6) = 0 munmap(0xb5cb4000, 4096) = 0 unlink("/tmp/rpmlist.OmXPfK") = 0 rt_sigaction(SIGINT, {SIG_DFL, [], 0x4000000 /* SA_??? */}, {0xb6e4fe38, [], 0x4000000 /* SA_??? */}, 8) = 0 rt_sigaction(SIGHUP, {SIG_DFL, [], 0x4000000 /* SA_??? */}, {0xb6e4fe38, [], 0x4000000 /* SA_??? */}, 8) = 0 rt_sigaction(SIGTERM, {SIG_DFL, [], 0x4000000 /* SA_??? */}, {0xb6e4fe38, [], 0x4000000 /* SA_??? */}, 8) = 0 rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1], [], 8) = 0 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 exit_group(1) = ? +++ exited with 1 +++ ****************************************************************************************** Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

Re: [opensuse-arm] Beagleboard XM freezes; suspect USB issue
by Guillaume Gardet 06 Mar '13

06 Mar '13

Le 05/03/2013 22:07, gary a écrit : > I'm keeping this reply off the list as to not clog up email for those not involved. If you think I should send the files to the list as well, let me know. > > There are three attached files. > lsmod.txt > cmdline.txt > dmesg.txt > > Not to distract focus from the problem at hand, but you may recall I mentioned that one of the bugs with opensuse versus ubuntu is the Beagleboard XM didn't reboot properly. That is, you would issue the reboot command, the display would indicate processes shutting down, but you never got a login prompt. Well it turns out that using SSH, the Beagleboard XM does shutdown and restart. To elaborate, you issue a reboot command, the lan connection goes away as the machine goes offline. But checking the router client list, I saw the board reconnect via DHCP, and could then SSH into it like normal. > > So if you can follow that lengthy story, it might be that whatever you need to "start" to make the SBC work normally might also fix the reboot issue. > > Also note Ubuntu has a more up to date driver for the GPU. I get the full 1920x1200 with ubuntu, while opensuse is less. [Exact resolution I forget.] Latest Factory JeOS-beagle image shows nothing on DVI output either, so there is a bug somewhere in factory kernel whereas omapdrm is loaded. :( CONFIG_DRM_OMAP_NUM_CRTCS var have been changed from 1 to 2. Is it related? I should try to recompile a kernel with CONFIG_DRM_OMAP_NUM_CRTCS=1 and test, but not sure I will have enough time to do it. What does fbset command return? Then, if you want to have something on your serial, add console=/dev/ttyO2 to the command line passed to kernel, from u-boot. You have not it, since your image is XFCE based. Guillaume > > > > On 3/5/2013 2:14 AM, Alexander Graf wrote: >> >> On 05.03.2013, at 11:09, Guillaume Gardet wrote: >> >>> Hi gary, >>> >>> >>> Le 04/03/2013 21:36, gary a écrit : >>>> I did a yast2 -i on the 19mbyte patch and didn't use the other two RPM files. This was on a freshly installed image of 12.2 XFCE. >>>> >>>> I can't log into the system "normally", i.e. keyboard and monitor via HDMI/usb. Nor can I log into the system via the serial port. However, I can log into the system with SSH. Thus I can run some diagnostics if you have suggestions. >>> >>> Could you give us output of thoses commands, please: >>> cat /proc/cmdline >>> lsmod >> >> dmesg would be helpful too >> >> >> Alex >> >> -- 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] [Announcement] openSUSE 12.3 preview available for AArch64
by Dirk Müller 06 Mar '13

06 Mar '13

Hi cross-distro readers, the openSUSE on ARM team was quite busy the last few weeks with getting openSUSE 12.3 for AArch64 ready. At the time of this post, we have finished around 4000-4100 packages (out of ~ 6000) of the current state of the openSUSE 12.3 project for AArch64. With those successfully built packages, we’re also able to build a regular openSUSE image for you to try and run in the ARMv8 System emulator (ARMv8 Foundation Model). This is a huge achievement and milestone for us, thanks to lots of helpful hands in openSUSE. Just to put this into context: This is not a minimal system with a couple of toolchain packages. It is also not an embedded variant of a Linux environment. No, this is the full featured, standard openSUSE distribution as you’re used to, ported to AArch64, up and running. We have built it based on (slightly newer versions of) standard openSUSE 12.3 packages, and the changes are mostly already merged back into openSUSE Factory. For 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 [1]. As an open distribution, it is important to make contributions easy and we worked hard to enable others to participate in our effort. We extended OBS (the Open Build Service) to automatically spawn a Foundation Model virtual machine when you want to build for aarch64. This works remotely on the OBS server as well as locally using osc build. Building for AArch64 is therefore as easy as building for any other architecture, and it feels native to all who are familiar with the OBS. More information on this is available on the respective wiki page [2]. So, dive right into it: Get the image and start with openSUSE on AArch64 by following our wiki page: https://en.opensuse.org/Portal:ARM/AArch64. Please contact the openSUSE Team at opensuse-arm(a)opensuse.org Greetings, Dirk (openSUSE ARM Team) [1] https://build.opensuse.org/project/show?project=devel:ARM:AArch64:12.3 [2] https://en.opensuse.org/Portal:ARM/AArch64 -- 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] Beagleboard XM freezes; suspect USB issue
by Guillaume Gardet 05 Mar '13

05 Mar '13

Hi gary, Le 04/03/2013 21:36, gary a écrit : > I did a yast2 -i on the 19mbyte patch and didn't use the other two RPM files. This was on a freshly installed image of 12.2 XFCE. > > I can't log into the system "normally", i.e. keyboard and monitor via HDMI/usb. Nor can I log into the system via the serial port. However, I can log into the system with SSH. Thus I can run some diagnostics if you have suggestions. Could you give us output of thoses commands, please: cat /proc/cmdline lsmod Regards, Guillaume > > The following in the output on the serial port. > > >> >> >> Texas Instruments X-Loader 1.5.0 (Sep 8 2012 - 02:21:18) >> Beagle xM >> Reading boot sector >> Error: reading boot sector >> fat load failed, trying ext2 >> Loading u-boot.bin from mmc >> >> >> U-Boot 2011.09 (Sep 08 2012 - 02:13:25) >> >> OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz >> OMAP3 Beagle board + LPDDR/NAND >> I2C: ready >> DRAM: 512 MiB >> WARNING: Caches not enabled >> NAND: 0 MiB >> MMC: OMAP SD/MMC: 0 >> *** Warning - readenv() failed, using default environment >> >> In: serial >> Out: serial >> Err: serial >> Beagle xM Rev C >> No EEPROM on expansion board >> Die ID #67dc00029ff80000016849a90401601a >> Net: No ethernet found. >> Hit any key to stop autoboot: 0 >> The user button is currently NOT pressed. >> SD/MMC found on device 0 >> Loading file "uEnv.txt" from mmc device 0:1 (xxa1) >> ** File not found uEnv.txt >> Loading file "boot.scr" from mmc device 0:1 (xxa1) >> 711 bytes read >> Loaded script from boot.scr >> Running bootscript from mmc0 ... >> ## Executing script at 80200000 >> ## Error: "kerneladdr" not defined >> ## Error: "ramdiskaddr" not defined >> Loading file "uImage" from mmc device 0:1 (xxa1) >> 4242344 bytes read >> Loading file "initrd" from mmc device 0:1 (xxa1) >> 12464100 bytes read >> ## Booting kernel from Legacy Image at 88000000 ... >> Image Name: Linux-3.7.9-0-omap2plus >> Image Type: ARM Linux Kernel Image (uncompressed) >> Data Size: 4242280 Bytes = 4 MiB >> Load Address: 80008000 >> Entry Point: 80008000 >> Verifying Checksum ... OK >> ## Loading init Ramdisk from Legacy Image at 81600000 ... >> Image Name: Initrd >> Image Type: ARM Linux RAMDisk Image (uncompressed) >> Data Size: 12464036 Bytes = 11.9 MiB >> Load Address: 00000000 >> Entry Point: 00000000 >> Verifying Checksum ... OK >> Loading Kernel Image ... OK >> OK >> >> Starting kernel ... >> >> Uncompressing Linux... done, booting the kernel. > > > > On 3/4/2013 1:03 AM, Guillaume Gardet wrote: >> >> Le 02/03/2013 01:28, gary a écrit : >>> I'm not sure if my direct replies are being caught in a spam filter. >>> There were no instructions with the patch, which is 3 RPMs. I placed >>> all three RPMs on the SD card for the Beagleboard XM. [Basically just >>> do a save as with the sd card in an intel computer running opensuse.] >>> >>> I booted the Beagleboard XM and ran all three patches, then rebooted. >>> At that point I could no longer log into the Beagleboard XM. Not >>> through the serial port or the "normally" (display driver and usb). >> >> What is the output on the serial port (I mean from u-boot and then if >> you have something then)? >> Did you try a SSH login? >> >>> >>> I have a program on the Beagleboard XM that I set up as a service that >>> provides "telemetry" over a lan. That service was running since I >>> coudl get data off the Beagleboard XM. I ran it for 3 days without a >>> crash. [At that point I went to a different SD card / OS to work on >>> other software.] The best I ever got prior to the patch is about 8 >>> hours. >>> >>> However, I think the performance of the software I was running was >>> hampered by the patch since it seemed to be putting out less data. >>> Since I couldn't log into the board, I have no way to analyze this. >>> >>> So again, I am asking for someone to either explain how to apply the >>> patch, or apply the patch to an image. >>> >> >> Install RPM kernel-omap2plus provided by Alex, using zypper and reboot. >> >>> As I stated before the JEOS wasn't booting on the Beagleboard XM. [The >>> XFCE image works.] This might be a good way to get the bug out of JEOS >>> and test the patch at the same time. >> >> Try your patch on XFCE image first. One thing at a time. ;) >> >>> >>> Since this appears to be a design flaw in the beagleboard XM, I'm sure >>> all the board have an issue with this to some degree. My board is just >>> worse than most. Thus I have a good test vehicle for the patched >>> kernel, well provided I get one. >> >> Thanks for your help in testing. >> >> >> Guillaume >> >> >>> >>> >>> >>> On 2/25/2013 4:05 PM, Alexander Graf wrote: >>>> >>>> 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 >>>> >>>> >> >> > -- 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] openSUSE:12.3:Ports now configure for native builds
by Guillaume Gardet 05 Mar '13

05 Mar '13

Hi, Tested just now as local build on x86_64, error is still there in Factory images build. Did you pushed a fix? 12.3 native build is not yet started in OBS (scheduled status for all except JeOS which is succeeded). Guillaume Le 02/03/2013 08:22, Adrian Schröter a écrit : > > JFYI, the openSUSE:12.3:Ports project is now configured for native building > > to workaround some reported problems there. > > I think, I saw also the error why it can't work with qemu in the config > > (an added Ignore: line to qemu-linux-arm package), but since 12.3 also > > building native, it is just consequent to do the same with the ports project. > > In can not watch if this really works in the next hours unfortunatly. > > sorry > > adrian > > -- > > Adrian Schroeter > > SUSE Linux Products GmbH > > email: adrian(a)suse.de > -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 2

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] openSUSE:12.3:Ports now configure for native builds
by Adrian Schröter 02 Mar '13

02 Mar '13

JFYI, the openSUSE:12.3:Ports project is now configured for native building to workaround some reported problems there. I think, I saw also the error why it can't work with qemu in the config (an added Ignore: line to qemu-linux-arm package), but since 12.3 also building native, it is just consequent to do the same with the ports project. In can not watch if this really works in the next hours unfortunatly. sorry adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de

1 0

[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

[opensuse-arm] Rebooting opensuse 12.2 on the beagleboard xm
by gary 21 Feb '13

21 Feb '13

If I request a reboot from xfce, the system does shut down, but it doesn't reboot. Does anyone else have this problem? Is there a fix? -- 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] Booting difficulty jeos on Beagleboard XM
by gary 21 Feb '13

21 Feb '13

I've run openuse for arm on a beagleboard XM few weeks ago. I used the sd card to try out another distribution. In the mean time, I bought a few more SD cards and am trying to install openuse for arm again. [The JEOS version.] The initial boot fails. I get this message: ---------- [ 272.571441] Fixing recursive fault but reboot is needed! _____________ I reboot and end up in this infinite loop. ----------- Waiting for Ethernet connection... done. EHCI timed out on TD - token=0x8008d80 Using sms0 device TFTP from server 192.168.123.1; our IP address is 192.168.123.43 Filename 'pxelinux.cfg/01-2e-50-fc-05-68-01'. Load address: 0x86000000 Loading: T T EHCI timed out on TD - token=0x88008d80 T EHCI timed out on TD - token=0x88008d80 T T T EHCI timed out on TD - token=0x88008d80 T T EHCI timed out on TD - token=0x88008d80 T T Retry count exceeded; starting again ------------------- I have formatted the SDHC card prior to writing the new image. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 3

[opensuse-arm] How to setup audio on Pandaboard ES
by endym 20 Feb '13

20 Feb '13

Hi all, how do I setup audio on the Pandaboard ES? The command alsaconf (and yast too) does not found any soundcard. Regards, endym -- 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] FOSDEM feedback
by Guillaume Gardet 19 Feb '13

19 Feb '13

Hi, some of you guys where at FOSDEM and some have made talks (Alexander, Andrew, maybe more?). It would be nice to have some feedbacks, especially from an ARM point of view. ;) Some videos are available on FOSDEM website but not the ARM ones ATM. Guillaume -- 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] no TUN in kernel?
by Ciaran Farrell 18 Feb '13

18 Feb '13

I just tried to use openvpn on the CuBox. I got this error in /var/log/messages: Note: Cannot open TUN/TAP dev /dev/net/tun: No such file or directory (errno=2) Looks as if there was no support for TUN so I checked: linux:/etc/openvpn # modprobe tun FATAL: Module tun not found Does this mean that the kernel was compiled without TUN or is something else going wrong? Ciaran -- Ciaran Farrell, Attorney at Law SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuremberg, DE GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer, HRB 16746 (AG Nuremberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 3

[opensuse-arm] Chromebook kernel configs
by Andrew Wafaa 15 Feb '13

15 Feb '13

Aloha all, I'm trying to build and package a new kernel for the Chromebook based on 3.8-rc4. I've managed to create a default config (with virt extensions enabled) and build a kernel natively, but when I did a diff of that default config and the config we use for the 3.4 kernel I noticed quite a few items missing. So I then changed the config and tried rebuilding, problem is that new config fails to build when it tries to build the Mali modules I think, I've attached the three configs in question and was wondering if someone more kernel config aware could advise on what I've done wrong - other than trying to build a new kernel :) chromebook-3.4 is the current working config chromebook-3.8-rc4 is the default auto generated config with virt extensions enabled chromebook-3.8-rc4_merge is the tweaked 3.8 config Thanks, Andy -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F

1 0

[opensuse-arm] Potential GSOC projects
by Andrew Wafaa 13 Feb '13

13 Feb '13

Hi all, Google's Summer of Code is starting again, and I was wondering if anyone had any thoughts on potential projects relating to ARM? It would be great if openSUSE was accepted again, and having a few ARM projects would be even better. Any and all ideas are welcome, but preferably potential projects that could help openSUSE as well as the wider world. Regards, 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

1 0

[opensuse-arm] Beagleboard xM Factory image tests
by Guillaume Gardet 06 Feb '13

06 Feb '13

Hi, here are my tests about latest factory image for beagle (kernel 3.7.2-3-omap2plus). At boot I get lots of this error message: systemd-udevd[1307]: failed to execute '/usr/lib/udev/socket:/org/kernel/dm/multipath_event' 'socket:/org/kernel/dm/multipath_event': No such file or directory And also this one once: systemd[1]: Cannot add dependency job for unit xdm.service, ignoring: Unit xdm.service failed to load: No such file or directory. See system logs and 'systemctl status xdm.service' for details. Audio: ok but I installed alsa tools and configured sound using: wget http://guillaume.gardet.free.fr/openSUSE/beagleboard-alsa.conf alsactl -f beagleboard-alsa.conf restore Maybe we could add it in OBS? (I will try something later). CPU: bogomips are 175.65/467.41 instead of 262.08/700.57 DSP: ok but still need some modprobe. I guess it may be done in OBS using /etc/modprobe.d/. (I will try it later). Ethernet: ok SD/MMC: ok UART: ok USB: ok DVI: NO output whereas omapdrm module is loaded. "dmesg | grep drm" returns: [ 15.567138] [drm] Initialized drm 1.1.0 20060810 [ 15.776214] omapdrm: module is from the staging directory, the quality is unknown, you have been warned. [ 16.004364] omapdrm omapdrm.0: DMM not available, disable DMM support [ 16.011444] omapdrm omapdrm.0: dvi has no driver.. skipping it [ 16.023498] [drm] Cannot find any crtc or sizes - going 1024x768 [ 16.254211] fb0: omapdrm frame buffer device [ 16.258789] drm: registered panic notifier [ 16.263244] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 16.270294] [drm] No driver support for vblank timestamp query. [ 16.276611] [drm] Initialized omapdrm 1.0.0 20110917 on minor 0 yast2-firstboot not loaded on firstboot whereas config.sh has: #====================================== # Trigger yast2-firstboot on first boot #-------------------------------------- touch /var/lib/YaST2/reconfig_system If I touch it manually and then reboot, nothing is done either. Once rebooted, I have some problem with serial console. Some key pressed are not shown and I get the following message: stty: standard input: unable to perform all requested operations Another reboot (from ssh) and the problem seems to be gone. Very strange. We may also add the following packages to JeOS: * alsa tools (said earlier in this mail) * command-not-found (but it requires some python packages :( ) * wget (usefull to download things from cmd line) Oh, and heartbeat led does not blink anymore. 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] Alternative ARMv8 simulator
by Dirk Müller 04 Feb '13

04 Feb '13

Hi, it seems there is also an alternative simulator available for simulating ARMv8: http://www.cavium.com/thundersdk_access_application.html Reportedly it is (perhaps only a fraction?) faster than the ARM Foundation model. Greetings, Dirk -- 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] AArch64 RPM tools available
by Guillaume Gardet 04 Feb '13

04 Feb '13

Hi, I just pushed rpm tools to our bootstrap rootfs (and RPMS folder). I tested it and rpmbuild is working! :) Only problem I had is our /bin/sh which does not understand the 'function' keyword. (See my previous mail) I will update it because it uses lib folder instead of lib64 but you can already update your rootfs to build and install RPM since I added /usr/lib to /etc/ld.so.conf and ran ldconfig. Guillaume -- 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] How to get the latest stable stuff?
by endym 02 Feb '13

02 Feb '13

Hi, I'm using the image "openSUSE-12.2-ARM-JeOS-panda.armv7l-1.12.1-Build1.46.1.raw.xz" (uname -r -> 3.4.6-2.10-omap2plus) for the Pandaboard ES. Is this the latest one, because the current images does not have a version number anymore? If not, can I upgrade to the latest stable via zypper? Actually the default software repositories are: sudo zypper lr -u # | Alias | Name | Enabled | Refresh | URI --+-----------------------------+----------------------------+-----------+---------------+----------- 1 | openSUSE-12.2-ARM-Repo-OSS | openSUSE-12.2-ARM-Repo-OSS | Yes | No | http://download.opensuse.org/ports/armv7hl/distribution/12.2/repo/oss/ 2 | openSUSE-12.2-ARM-Updates | openSUSE-12.2-ARM-Updates | No | Yes | http://download.opensuse.org/ports/armv7hl/update/12.2/ I had to disable repo 2, because it is invalid (error message while refreshing it). Is this a known error? Is there a valid update repository? Regards, endym -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 6

[opensuse-arm] AArch64 shell problem
by Guillaume Gardet 01 Feb '13

01 Feb '13

Hi, our current bootstrap rootfs has a shell (/bin/sh) which does not understand the 'function' keyword. The problem is that some SPEC files uses it. A workaround is to remove this keyword but it would be better if our shell understand it. Our /bin/sh is a busybox shell which seems to miss some features. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 2

[opensuse-arm] AArch64 and lib - lib64 directories
by Guillaume Gardet 31 Jan '13

31 Jan '13

Hi, I was wondering if we want to use /lib64 and /usr/lib64 for AArch64 or use /lib and /usr/lib. It seems Fedora uses lib64 whereas linaro uses lib. Debian seems to use a symlink so that lib and lib64 are the same. Some people discussed about that on cross-distro list some times ago; AArch64 triplet thread: http://lists.linaro.org/pipermail/cross-distro/2012-November/thread.html It seems Fedora is right using lib64 convention. Should we use it also? It is better to decide now since aarch64 is at an early stage. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 17