March 2012 - openSUSE ARM - openSUSE Mailing Lists

[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] Interview of the ARM team
by Kim Leyendecker 29 Apr '12

29 Apr '12

Howdy y'all, maybe you know about "People of openSUSE", a series of the news team to introduce openSUSE people to our users and news-readers. As ARM is one of the buzz words in the IT world this year, it might be interesting to hear something about our ARM team and what your doing in general. I planned to to a People of openSUSE special, and if you're interested, I'd be very glad to send you some questions to answer. kind regards, -- Kim Leyendecker, openSUSE Wiki Team GPG Key: 664265369547B825 | leyendecker(a)opensuse.org http://www.opensuse.org - Linux for open minds -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 7

[opensuse-arm] Bad kernel-omap2plus package ?
by Guillaume Gardet 17 Apr '12

17 Apr '12

Hi, I installed the latest raw image for BeagleBoard xM and then "zypper refresh && zypper up" and I get a lot of warnings (check attachment). Especially for kernel installation: ******************************************************************************** Installing: kernel-omap2plus-3.3.0-1.1 [done] Additional rpm output: WARNING: /etc/depmod.d/00-system.conf line 1: ignoring bad line starting with '4683/tcp' WARNING: /etc/depmod.d/00-system.conf line 2: ignoring bad line starting with 'spike' WARNING: /etc/depmod.d/00-system.conf line 4: ignoring bad line starting with 'rfid-rp1' WARNING: /etc/depmod.d/00-system.conf line 5: ignoring bad line starting with 'rfid-rp1' WARNING: /etc/depmod.d/00-system.conf line 7: ignoring bad line starting with 'autopac' WARNING: /etc/depmod.d/00-system.conf line 8: ignoring bad line starting with 'autopac' WARNING: kernel image for 3.3.0-1-omap2plus not found! ******************************************************************************** And a ls /boot show this: ******************************************************************************** -rw-r--r-- 1 root root 1,3K 20 mars 11:52 boot.readme -rw-r--r-- 1 root root 697 1 janv. 2000 boot.scr -rw-r--r-- 1 root root 625 1 janv. 2000 boot.script -rw-r--r-- 1 root root 81K 22 mars 12:50 config-3.3.0-1-omap2plus drwxr-xr-x 2 root root 1,0K 1 janv. 2000 grub lrwxrwxrwx 1 root root 24 23 févr. 02:11 initrd -> initrd-3.3.0-1-omap2plus -rw-r--r-- 1 root root 22M 13 mars 14:50 initrd.uboot -rw-r--r-- 1 root root 3,9M 13 mars 14:50 linux.vmx drwx------ 2 root root 12K 13 mars 14:50 lost+found -rwxr-xr-x 1 root root 29K 1 mars 00:37 MLO -rw-r--r-- 1 root root 73K 22 mars 13:43 symvers-3.3.0-1-omap2plus.gz -rw-r--r-- 1 root root 234 22 mars 13:43 sysctl.conf-3.3.0-1-omap2plus -rw-r--r-- 1 root root 1,9M 22 mars 13:32 System.map-3.3.0-1-omap2plus -rw-r--r-- 1 root root 331K 1 mars 11:27 u-boot.bin lrwxrwxrwx 1 root root 24 23 févr. 02:11 uImage -> uImage-3.3.0-1-omap2plus -rw-r--r-- 1 root root 4,0M 22 mars 13:43 uImage-3.3.0-1-omap2plus -rw-r--r-- 1 root root 4,9M 22 mars 13:37 vmlinux-3.3.0-1-omap2plus.gz ******************************************************************************** So, no initrd (except a broken link and the initrd.u-boot). Moreover, when I try to boot, u-boot is still looking for uImage-3.2.0-2-omap2plus which is no more here. (same for initrd). So I think something is broken somewhere! Guillaume

3 9

[opensuse-arm] Re: [opensuse-buildservice] [PATCH] [build] Map Debian ARM arches to OBS
by Adrian Schröter 15 Apr '12

15 Apr '12

Am Mittwoch, 28. März 2012, 04:49:01 schrieb Adrian Schröter: > Am Dienstag, 27. März 2012, 22:43:35 schrieb Hector Oron: > > Hello Adrian, > > > > On 27/03/12 22:32, Adrian Schröter wrote: > > > Am Dienstag, 27. März 2012, 20:55:41 schrieb Hector Oron: > > >> Debian ARM arches: > > >> - Debian 'armel', which defaults to ARMv4t (soft) maps to armv[4567]l > > >> - Debian 'armhf', which defaults to ARMv7 (hard-float) maps to armv7hl > > >> > > >> Note Ubuntu 'armel' deprecated after 'precise' release, defaults to ARMv7 > > >> (softfp). So Ubuntu 'armel' should really map armv7l, but its out of scope > > >> for this patch. > > > > > > Hm, doesnt it make sense to map armv7l and armv7hl to armhf ? AFAIK there are no > > > arm cpus on v7 level without hardware fp. > > > > > > On the other hand this is about optimization level here and not hardware capabilities... > > > > As I understand armv7hl is hard-float ABI, hence 'armhf'. > > > > armv7l can be ARMv7/softfp as Ubuntu was doing on their ARM port > > (armel), hence makes sense to me to map armv7l to 'armel'. > > > > OTOH, Debian armel can run on any of those platforms, armv[4567]l, maybe > > armv[4567]el should be added to the list. In other words, if I am > > building armv7l debian packages I would expect them to use 'armel' > > dependencies, while if I am building armv7hl, I would expect to build > > against 'armhf' dependencies. > > > > As a side note, I also see 'armv8el', I think that one comes from MeeGo, > > and it should be deprecated and mapped in the future to aarch64 (64-bit > > ARM architecture). > > That one is pure fantasy and will have nothing in common with real upcomming armv8, I think. > > But also architectures like armv7hl or armhf are fantasy when it comes to the linux > kernel. They are just a hack in the packagemanagement to avoid to handle ABI compatibility > on dependency level. But it makes for example impossible to install static binaries armv7l > on armv7hl and vice versa. Even though it would run on real hardware. > > Or it would be thinkable to have also an entire set of packages with softfp on hardfp and vice > versa. For that reason I selected just "armv7l" for our hardfp optimized distribution. > But I agree that we seems to be special in the arm world with that way (so in worst case > we need to switch to armv7hl as well and need to make armv7l and armv7hl as equivalent to avoid > the describe problems) :/ > > In any case we have the problem now that we can not detect the ABI from the architecture now... > > We can take your patch now, but armhf will not be selected right in our default settings. > > I would be happy, if anyone has a better proposal here. Thinking again on the way to work about it, I think the following is the right approach: 1) Take your patch as is (done) ;) 2) Keep schedulers running on armv7l only, because we have just one pool of systems to build for. The same machines can handle armv7 softfp and hardfp (is this right?, I am no expert in arm hardware) For our openSUSE arm distro: 3) Define default _cpu_target as armv7hl, so we get also .armv7hl.rpm packages 4) Trim our rpm on arm to handle armv7l and armv7hl as equivalent. 5) extend library depend&provides handling with a "(hf)" extension to be able to distinguish between hardfp and softfp packages on the same installation. Note: The last point 5) would make our rpms incompatible with the ones from Fedora. But it is IMHO the only way to handle mixed installations and the fedora way is IMHO technical just wrong. I would be happy to hear some more opinions on this. -- 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

[opensuse-arm] efika networking
by Peter Czanik 15 Apr '12

15 Apr '12

Hello, After yesterdays updates, networking does not work any more on the EFIKA. I still use the old Genesi kernel, as it arrived in the EFIKA image (2.6.31.14.26-efikamx) from http://lizards.opensuse.org/2012/01/21/opensuse-arm-image/ The non working wifi is definitely related to udev, there were related e-mails on the factory list also for x86, that firmware for Intel wifi can't be loaded either. But Ethernet on the smart top also does not work: it receives an initial IP address from the DHCP server, but after that there is no networking, even the DHCP server can't be reached again. Networking from Ubuntu works fine fine on the same machines. Any idea how to fix this? Bye, CzP -- 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] Unable to login on Beagleboard xM with latest image
by Guillaume Gardet 15 Apr '12

15 Apr '12

I tried a zypper dup today but it broke my board (unable to boot since kernel file name in /boot did not match anymore and no initrd was present.) So, I wanted to boot the latest raw image but trying to log in with root/linux but I get this error: *************************************************************** linux login: root Password: Permissions on the password database may be too restrictive *************************************************************** I looked at the /etc/shadow file which seems strange to me: *************************************************************** Event # Greg Bailey <gbailey&lxpro.com> February 2002 biolink-auth 3411/tcp # BioLink Authenteon server biolink-auth 3411/udp # BioLink Authenteon server # BioLink Support <reginfo&biolinkusa.com> February 2002 xmlblaster 3412/tcp # xmlBlaster xmlblaste *************************************************************** Replaced by my /etc/shadow from my running PC and I am able to login (with the password from my PC of course). Could you please 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 1

[opensuse-arm] Fix ARM kernel-default and kernel-u8500
by Guillaume Gardet 02 Apr '12

02 Apr '12

Hi, kernel-default and kernel-u8500 fail to build because eGalax touchscreen is enabled and use the function irq_to_gpio which is not available for default and u8500 kernels. Attached patches solve the problem by disabling the eGalax support for both kernels. Can anyone modify the default and u8500 config files accordingly, please? Guillaume

3 6

[opensuse-arm] armv5 progress
by Bernhard M. Wiedemann 30 Mar '12

30 Mar '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I made progress on the arm5 side of things (to get openSUSE to run on my two openRDs) disassembling some of the non-working programs had shown earlier that there were floating point instructions while Debian's gcc produced function calls in those places. I tried to compile the kernel with floating-point emulation without effect. Reading http://wiki.debian.org/ArmEabiPort I found mention of the __SOFTFP__ macro and that paradoxically it is not set by -mfloat-abi=softfp checking with :| gcc -dM -E -x c -|grep SOFT I found that this is set on Debian, but not on openSUSE. our gcc46.spec had in the armv5 section - --with-float=softfp which I changed to =soft for a local build (OBS does not let me branch a broken package). And it made gcc work finally for armv5 - yay! so please apply this patch: - --- gcc46.spec (revision b6148fab8499be9d98ff39bdabb170ec) +++ gcc46.spec (working copy) @@ -1697,7 +1719,7 @@ %endif %if "%{TARGET_ARCH}" == "armv5tel" --with-arch=armv5te \ - - --with-float=softfp \ + --with-float=soft \ --with-mode=arm \ --with-abi=aapcs-linux \ --disable-sjlj-exceptions \ When I tried to build locally on ARM, I also hit another strange bug, that I only saw on Factory ARM: # (cd /tmp/ ; sudo id ; echo $?) 143 - -- _=======.=======_ _---|____________\/ (____/ /\ _/ \_ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9ld/wACgkQSTYLOx37oWR+VACgl9PFYgyWYELnN67f5C8OJEZT pJMAoPvf+YIvA6DOgRLmRAU6cYziVR17 =dE2T -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 4

[opensuse-arm] friendlyarm mini2440
by Michael Monnerie 23 Mar '12

23 Mar '12

Hi, I'm going to buy a mini2440 board http://www.friendlyarm.net/products/mini2440 Can somebody tell me if I should try with openSUSE-arm, or is it very intensive work atm? I'm new to embedded and arm, so please forgive my unholy question. It's just I'm a fan of openSUSE, and would like to use it on the mini2440 too. Please answer me directly, I'm not subscribed on this list yet. -- mit freundlichen Grüssen, Michael Monnerie, Ing. BSc it-management Internet Services: Protéger http://proteger.at [gesprochen: Prot-e-schee] Tel: +43 660 / 415 6531

2 1

[opensuse-arm] Kernel omap2plus config - Add TI dsp bridge driver
by Guillaume Gardet 19 Mar '12

19 Mar '12

Hi, would it be possible to enable the TI dspbridge (staging) driver in the omap2plus kernel config, please ? As a module, not as built-in. The var is CONFIG_TIDSPBRIDGE. It will enable the use of the integrated DSP in the Texas Instrument SoC. At least the kernel part. Then we could try to package the userspace part. Regards, Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 10