April 2013 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] Problems with OS for Raspberry Pi
by Edgar Dombrowski 10 Apr '13

10 Apr '13

Hi, folks. Firstof all thanks to all of you who helped me with "username and Password" I start the program but I have still some questions (with OpenSuSe I am an oldtimer since 4,2): 1 Configuration of the network: the network card has been recognized by its MAC-Adress, but no access to the router - no "ping"-command 2. Is there a kind of tutorial available? 3. I am pleased that the ax25-devices are included, as I intend to use the board for Packet Radio Thanks for your your cooperation Edgar, DJ3PU, Munich -- 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 for Raspberry Pi
by Edgar Dombrowski 10 Apr '13

10 Apr '13

Hi, Raspberry Pi friends. I just download the latest version for the Raspberry Pi. Unfortunatly I forgot the the user name and the password. Can any one help me Thanks Edgar, DJ3PU, from Munich -- 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] We had to change the sign key (wohoo!)
by Dirk Müller 10 Apr '13

10 Apr '13

Hi, unfortunately we had a DSA key configured on devel:ARM (which means it affects all ARM related images, packages, everything) to a new, RSA based key. The new key is: :public key packet: version 4, algo 1, created 1365594473, expires 0 pkey[0]: [2048 bits] pkey[1]: [17 bits] keyid: 16C5D54F3F546F34 :user ID packet: "devel:ARM OBS Project <devel:ARM@build.opensuse.org>" :signature packet: algo 1, keyid 16C5D54F3F546F34 version 4, created 1365594473, md5len 0, sigclass 0x13 digest algo 2, begin of digest e6 f0 hashed subpkt 2 len 4 (sig created 2013-04-10) hashed subpkt 27 len 1 (key flags: 03) hashed subpkt 9 len 4 (key expires after 2y70d0h0m) hashed subpkt 11 len 5 (pref-sym-algos: 9 8 7 3 2) hashed subpkt 21 len 3 (pref-hash-algos: 2 8 3) hashed subpkt 22 len 3 (pref-zip-algos: 2 3 1) hashed subpkt 30 len 1 (features: 01) hashed subpkt 23 len 1 (key server preferences: 80) subpkt 16 len 8 (issuer key ID 16C5D54F3F546F34) data: [2047 bits] :signature packet: algo 17, keyid 3B3011B76B9D6523 version 4, created 1365594473, md5len 0, sigclass 0x13 digest algo 2, begin of digest 9d ae hashed subpkt 2 len 4 (sig created 2013-04-10) subpkt 16 len 8 (issuer key ID 3B3011B76B9D6523) data: [159 bits] data: [159 bits] pub 2048R/3F546F34 2013-04-10 devel:ARM OBS Project <devel:ARM@build.opensuse.org> sig 3F546F34 2013-04-10 [selfsig] sig 6B9D6523 2013-04-10 [User ID not found] Greetings, 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] mysterious segfault
by Ludwig Nussel 10 Apr '13

10 Apr '13

Hi, The attached piece of code randomly segfaults on a panda board with openSUSE 12.2. The same code works fine in a chroot with qemu on x86_64. The general method also works fine on x86_64. What could the reason for the segfault? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)

2 2

[opensuse-arm] OpenSUSE 12.3 for armv7 on Mirabox fails
by G. Heim 10 Apr '13

10 Apr '13

Standard, Mirabox is delivered with Debian. I would like to have it run OpenSUSE 12.3 for armV7 because I like openSUSE better :-) and it is natively compiled for armv7. Debian Squeeze (debian 6) is not (it is compiled for armv5 if I understand correctly, which sounds kind-of silly on an armv7 architecture). So I downloaded the opensuse image from http://download.opensuse.org/ports/armv7hl/distribution/12.3/images/openSUS… and put it on my sdcard. I made 2 partitions, one FAT ca. 100MB for uImage (from the rootfs in the tbz file) and the remainder ext4 for the rootfilesystem. I hoped it would work right away but it did not. Right after the loading phase of uboot it stopped after the message "uncompressing linux...done, booting the kernel" and nothing was displayed. Then I thought I might use the precompiled uImage (from the debian distribution) together with the /lib/modules files from the debian distribution, so I copied /lib/modules from debian rootfs to the opensuse rootfs and the uImage to the FAT partition of my sdcard. It did boot but during the boot process it gave all strange errors and did not complete. uImage was from https://code.google.com/p/mirabox/downloads/detail?name=uImage-v2.6.35.9-gt… and the debian rootfs from http://www.plugcomputer.org/405/us/mirabox/sources/rootfs/mira_fs-v5-0-1-12…. At some moment, I thought that might be logical because of the armv5 arch from debian and armv7 from opensuse. Then I tried running opensuse in a chroot on the mirabox with debian as a base, as described on http://en.opensuse.org/HCL:Chroot. That worked really wonderful. So that led me to the idea of compiling my own kernel on the mirabox when being in a chroot opensuse. I grabbed the kernel sources from http://www.plugcomputer.org/405/us/mirabox/sources/kernel/mira_kernel-v5-0-…, did not modify the configuration in .config, ran "make", "make uImage", "make install", "make modules_install" and then booted opensuse with the resulting kernel. That did not work either. Right after the loading phase of uboot it stopped after the message "uncompressing linux...done, booting the kernel" and nothing was displayed. Then I tried compiling the kernel sources from opensuse (obtained from package "kernel-source" and "kernel-devel" via /sbin/yast2 in opensuse) by tweaking in the armada370 bits (including the same kernel .config file) from the kernel sources from the previous paragraph but it was too much tweaking and twiddling so I gave up on that. Why doesn't it work? What did I miss? Do I not understand the kernel building process? Any help is really appreciated. Thanks, Ge -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 30

[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