June 2012 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] armStoneA8: Failed to mount /dev
by Andreas Färber 02 Dec '12

02 Dec '12

Hello, On the armStoneA8 board, using NBoot V14 and U-Boot, I'm trying to boot the downstream 3.3.7 kernel (BSP V1.1) from SD with a LimeJeOS rootfs on SD. I had to reconfigure the kernel with CONFIG_LBDAF to mount the ext3[*] rootfs r/w. This is what I get now: [...] mmc0: new high speed SDHC card at address b368 IPv6 over IPv4 tunneling driver mmcblk0: mmc0:b368 NCard 7.48 GiB NET: Registered protocol family 17 can: controller area network core (rev 20090105 abi 8) mmcblk0: p1 NET: Registered protocol family 29 can: raw protocol (rev 20090105) can: broadcast manager protocol (rev 20090105 t) Registering the dns_resolver key type VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2 s3c-rtc s3c64xx-rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) kjournald starting. Commit interval 5 seconds EXT3-fs (mmcblk0p1): using internal journal EXT3-fs (mmcblk0p1): recovery complete EXT3-fs (mmcblk0p1): mounted filesystem with ordered data mode VFS: Mounted root (ext3 filesystem) on device 179:1. Freeing init memory: 148K Failed to mount /dev: No such device Our rootfs definitely contains /dev, so what is this complaining about? Thanks, Andreas [*] U-Boot seemed to hang loading zImage from ext4. -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- 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] parted and x86 bootinfo in the MBR
by Alexander Graf 03 Jul '12

03 Jul '12

Hi Petr, When running parted to create or modify an MBR label, it tries to be clever and throws a dummy x86 boot sector onto the MBR, so the disk is bootable on PCs. While that's nice and helpful for a bunch of use cases, it doesn't exactly help when running on ARM. Some ARM devices, such as the OMAP3 series, have a buggy boot rom that simply goes into nirvana if it finds non-0 in the first 4 bytes of the SD card. Please see libparted/labels/dos.c:1271 for the place that copies a generic x86 asm MBR into the MBR when its first byte is 0. We need to have the first byte be 0 though. Otherwise later on the whole machine won't be bootable anymore :). Any idea how to resolve this? The easy fix I could imagine would be to just not do the fixup on ARM, but that sounds slightly hackish :(. Alex -- 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] openSUSE openjdk 1.7 on ARM
by Alexander Graf 29 Jun '12

29 Jun '12

Hi Michal, Currently compiling openjdk on ARM fails for us with what looks like a generic zero engine issue. Do you have any idea what could be causing this? Did someone change internal interfaces and not update the zero vm? g++ -DLINUX -D_GNU_SOURCE -DCC_INTERP -DZERO -DTARGET_ARCH_NYI_6939861=1 -DARM -DZERO_LIBARCH=\"arm\" -DPRODUCT -I. -I/home/abuild/rpmbuild/BUILD/java-1_7_0-openjdk/openjdk/hotspot/src/share/vm/prims -I/home/abuild/rpmbuild/BUILD/java-1_7_0-openjdk/openjdk/hotspot/src/share/vm -I/home/abuild/rpmbuild/BUILD/java-1_7_0-openjdk/openjdk/hotspot/src/share/vm/precompiled -I/home/abuild/rpmbuild/BUILD/java-1_7_0-openjdk/openjdk/hotspot/src/cpu/zero/vm -I/home/abuild/rpmbuild/BUILD/java-1_7_0-openjdk/openjdk/hotspot/src/os_cpu/linux_zero/vm -I/home/abuild/rpmbuild/BUILD/java-1_7_0-openjdk/openjdk/hotspot/src/os/linux/vm -I/home/abuild/rpmbuild/BUILD/java-1_7_0-openjdk/openjdk/hotspot/src/os/posix/vm -I../generated -DHOTSPOT_RELEASE_VERSION="\"23.0-b21\"" -DHOTSPOT_BUILD_TARGET="\"product\"" -DHOTSPOT_BUILD_USER="\"abuild\"" -DHOTSPOT_LIB_ARCH=\"arm\" -DHOTSPOT_VM_DISTRO="\"OpenJDK\"" -DTARGET_OS_FAMILY_linux -DTARGET_ARCH_zero -DTARGET_ARCH_MODEL_zero -DTARGET_OS_ARCH_linux_zero -DTARGET_OS_ARCH_MODEL_linux_zero -DTARGET_COMPILER_gcc -fpic -fno-rtti -fno-exceptions -D_REENTRANT -fcheck-new -fvisibility=hidden -D_LITTLE_ENDIAN -pipe -g -O3 -fno-strict-aliasing -gstabs -DVM_LITTLE_ENDIAN -DINCLUDE_TRACE -Werror -Wpointer-arith -Wsign-compare -c -MMD -MP -MF ../generated/dependencies/cppInterpreter_zero.o.d -o cppInterpreter_zero.o /home/abuild/rpmbuild/BUILD/java-1_7_0-openjdk/openjdk/hotspot/src/cpu/zero/vm/cppInterpreter_zero.cpp /home/abuild/rpmbuild/BUILD/java-1_7_0-openjdk/openjdk/hotspot/src/cpu/zero/vm/cppInterpreter_zero.cpp: In static member function 'static void CppInterpreter::process_method_handle(oop, Thread*)': /home/abuild/rpmbuild/BUILD/java-1_7_0-openjdk/openjdk/hotspot/src/cpu/zero/vm/cppInterpreter_zero.cpp:817:7: error: 'get_ek_bound_mh_info' is not a member of 'MethodHandles' /home/abuild/rpmbuild/BUILD/java-1_7_0-openjdk/openjdk/hotspot/src/cpu/zero/vm/cppInterpreter_zero.cpp:965:7: error: 'get_ek_adapter_opt_swap_rot_info' is not a member of 'MethodHandles' The full log is available here once it's finished rebuilding again: https://build.opensuse.org/package/live_build_log?arch=armv7l&package=java-… Alex-- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 5

[opensuse-arm] introduction and bootstrap questions
by DuChene, StevenX A 28 Jun '12

28 Jun '12

Hello all: I have a couple of ARM systems here that have a four core chip by Marvell on a System On Module or SOM made by Cogent. This SOM is then socketed into a development motherboard that has four full size USB ports, two 1Gig-E network ports, two SATA ports, and a built-in serial-to-USB console. The SOM has 2GB of memory and the Marvell MV78460 chip has hardware floating point so the architecture shows up as armv7l or armv7hl or armv7hfp depending on what OS bits are loaded. I am supposed to be receiving a third system shortly for additional testing. Right now I have Fedora-13 ARM distro bits installed on a partition on a 500GB SATA hard drive. I was able to do this with a tarball of the root filesystem provided by the Fedora project. Once I had that unpacked on the hard drive I was able to alter the u-boot environment to still use the kernel resident on the internal NAND flash but use the root filesystem on the SATA disk. Later for ease of testing new kernel images I altered the u-boot environment again to use a kernel downloaded via tftp. I had downloaded the complete group of rpms Fedora-13 for ARM so I could setup a yum repo to facilitate adding more packages to the systems as needed. Unfortunately neither Marvell or Cogent are feeding any sort of platform support patches they have developed back to the standard kernel development process so I am limited to working with the source tree they have provided for right now. That is currently based around a 3.0.6 kernel tree. What I am wondering is if the OpenSUSE-arm project has a similar root filesystem tarball available that I could use to boot strap one of these systems to the current OpenSuSE-arm bits if they are released at all. That way I could do some testing of that build on this platform. -- Steven DuChene

2 1

[opensuse-arm] armv5 images
by Guillaume Gardet 28 Jun '12

28 Jun '12

Hi, would it be possible to enable JeOS image creation for armv5 so that we can have a rootfs for armv5 targets? I should receive my Raspberry Pi this week and I would like to test openSUSE armv5el on it. Cheers, Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 5

[opensuse-arm] xorg-x11-drv-omapfb config file
by Guillaume Gardet 27 Jun '12

27 Jun '12

Hi, Is there any reason to have all the lines commented in the config file 20-omapfb.conf for xorg-x11-drv-omapfb? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 11

[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] ARM demo at Solutions Linux in Paris
by Guillaume Gardet 26 Jun '12

26 Jun '12

Hi, I am back from Solutions Linux [0] in Paris where we hold a booth. We also had a demo of openSUSE running on ARM, on a Beagleboard xM. Some pictures: http://guillaume.gardet.free.fr/openSUSE/SSL_2012/ It was very attractive to have a little ARM board on our booth, lots of people come to our booth. The demo was quite simple, it was only a video playing (Big buck bunny [1]). We did not used the DSP accelerated codecs since it does not work yet with gstreamer but we used a software player based on libav and designed for omap devices (Beagleboards (xM) and pandaboards (ES)): omapfbplay. The demo was running all the day without any problem. omapfbplay is available on my personnal build service [2] and directly from my repo [3]. For the next booth, I hope to have a real little computer on my Beaglebord xM. (Xorg, firefox, ...) If you have any question, please ask. Cheers, Guillaume [0]: http://www.solutionslinux.fr/?lg=en [1]: http://www.bigbuckbunny.org/ [2]: https://build.opensuse.org/package/show?package=omapfbplay&project=home%3AG… [3]: http://download.opensuse.org/repositories/home:/Guillaume_G:/ARM/openSUSE_F… -- 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] Exynos boards
by Guillaume GARDET 26 Jun '12

26 Jun '12

Hi andrew, I saw you added support to Exynos in opensuse. Could you please fill the following page with boards supported by your kernel config: http://en.opensuse.org/openSUSE:Supported_ARM_boards You may also add support for "Flattened Device Tree based board for EXYNOS SoCs". Cheers, 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] Updated ARM configs for review
by Andrew Wafaa 22 Jun '12

22 Jun '12

Aloha Geekos, Attached is a patch for all the current ARM configs rebasing them against kernel 3.5.0-rc3. Before I send it to the kernel folks, please could you review it to make sure I haven't completely screwed things up? Many thanks, Andy -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F

3 4

[opensuse-arm] Exynos4 & 5 config for review
by Andrew Wafaa 22 Jun '12

22 Jun '12

Aloha geekos, If possible could someone kindly review the attached patch which creates a config for Samsung Exynos based devices, like the Origen. This patch covers both Exynos4 and Exynos5, I checked with some folk at work and they believe it should be fine to unify the config in the same way as the omap2plus. I haven't tested it yet, as I'm having a few u-boot issues. Many thanks, Andy -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F

1 0

[opensuse-arm] Presentation of openSUSE on ARM
by Andrew Wafaa 22 Jun '12

22 Jun '12

Aloha all, I was wondering what collateral, if any, there is for presenting openSUSE on ARM? I've been asked to do a presentation of sorts at work and would like to give as much detail as possible. Things I'd like to raise are issues encountered what fixes/hacks/workarounds have had to be used and why; what benchmarking if any has been done; more info on the tools used (so mostly OBS); what optimisations have been carried out; what standardisation needs we have; any profiling/benchmarking carried out and the results. I believe that some have already done some presentations on the port, and was wondering if we could collaborate? I was thinking of having the deck in a git repo so that it is easy for all. Many 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

1 0

[opensuse-arm] Dynamic linker change for ARM finally coming...
by Andreas Jaeger 22 Jun '12

22 Jun '12

Richard just accepted my patch (taken from upstream GCC trunk) to build for ARM with the new dynamic linker path. Once this is in Factory/12.2, ARM should be completely rebuild. Please give it proper testing. My request: https://build.opensuse.org/request/diff/125668 and the forward to Factory: https://build.opensuse.org/request/diff/125574 Coolo, please check that this goes into the 12.2 branch as well, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- 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] LimeJeOS-openSUSE-12.2-ARM-panda.armv7l-1.12.2-Build1.1.raw.xz
by endym 17 Jun '12

17 Jun '12

Hello, I get following error with the image "LimeJeOS-openSUSE-12.2-ARM-panda.armv7l-1.12.2-Build1.1.raw.xz" on a Pandaboard ES: U-Boot SPL 2011.09 (Jun 01 2012 - 22:47:25) Texas Instruments OMAP4460 ES1.1 OMAP SD/MMC: 0 mkimage signature not found - ih_magic = 0 Assuming u-boot.bin .. After this nothing happens. Regards, endym -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 4

[opensuse-arm] JeOS-beagle unresolvable because of missing non ARM things
by Guillaume Gardet 15 Jun '12

15 Jun '12

Hi, JeOS-beagle image is unresolvable because of missing non ARM things: gfxboot, kernel-desktop, grub and others. Check it here: https://build.opensuse.org/package/show?package=JeOS-beagle&project=openSUS… Any idea why? Problem with kiwi? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 8

[opensuse-arm] Full ARM rebuild
by Guillaume Gardet 13 Jun '12

13 Jun '12

Hi, libselinux have been updated, so a full rebuild happens. 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] No ARM JeOS* images built due to kiwi : command not found!
by Alexander Graf 13 Jun '12

13 Jun '12

On 12.06.2012, at 17:11, Guillaume Gardet <guillaume.gardet(a)free.fr> wrote: > > > Le 12/06/2012 15:34, Adrian Schröter a écrit : >> >> Am Dienstag, 12. Juni 2012, 15:32:10 schrieb Alexander Graf: >>> Adrian Schröter wrote: >>>> Am Dienstag, 12. Juni 2012, 13:13:23 schrieb Guillaume Gardet: >>>> >>>>> Le 12/06/2012 10:29, Guillaume Gardet a écrit : >>>>> >>>>>> Le 12/06/2012 09:55, Adrian Schröter a écrit : >>>>>> >>>>>>> Am Dienstag, 12. Juni 2012, 09:50:56 schrieb Guillaume Gardet: >>>>>>> >>>>>>> [...] > > A new problem: mkimage is not found. > > Jun-12 14:44:56 <1> : Creating uBoot initrd image... > Jun-12 14:44:56 <1> : EXEC [mkimage -A arm -O linux -T ramdisk -C none -a 0x0 -e 0x0 -n 'Initrd' -d /tmp/kiwiboot.DnMD1C/boot/initrd.vmx /tmp/kiwiboot.DnMD1C/boot/initrd.uboot] > Jun-12 14:44:57 <1> : EXEC [Failed: bash: line 0: type: mkimage: not found > ] > failed > Jun-12 14:44:57 <3> : Failed to create uboot initrd image: bash: line 0: type: mkimage: not found > : command not found > failed > Jun-12 14:44:57 <1> : EXEC [sync] > Jun-12 14:44:57 <1> : EXEC [rm -rf /tmp/kiwiboot.DnMD1C 2>&1] > Jun-12 14:44:57 <1> : EXEC [rm -rf /tmp/kiwiloop.DTuE3s 2>&1] > Jun-12 14:44:58 <3> : KIWI exited with error(s) > done > Jun-12 14:44:58 <1> : EXEC [umount /usr/src/packages/KIWI-oem/mnt-3932 2>&1] > Jun-12 14:44:58 <1> : EXEC [rm -rf /usr/src/packages/KIWI-oem/boot-VMX.0UOfmU 2>&1] > Jun-12 14:44:58 <1> : EXEC [umount /usr/src/packages/KIWI-oem/mnt-3932 2>&1] > [ 2548.375663] SysRq : Power Off > [ 2550.225255] Power down. > > > Any idea? u-boot tools not installed? Alex > > Guillaume >

3 7

[opensuse-arm] No ARM JeOS* images built due to kiwi : command not found!
by Guillaume Gardet 12 Jun '12

12 Jun '12

No JeOS images built due to error: kiwi: command not found https://build.opensuse.org/project/monitor?arch_armv7l=1&defaults=0&failed=… The logs show the installation of kiwi: ********** [6/202] installing kiwi-tools-5.03.12-3.1 [...] [202/202] installing kiwi-5.03.12-3.1 ********** To finally get: ********** running kiwi --prepare for tbz... -bash: kiwi: command not found ********** Any idea why? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 8

[opensuse-arm] Fixing perl
by Guillaume Gardet 12 Jun '12

12 Jun '12

I am trying to fix perl. I made a patch and I am currently compiling it. It is already further and I hope it will built fine until the end. I will keep you up-to-date. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 18

[opensuse-arm] armv7l vs. armv7hl rpm arch
by Adrian Schröter 12 Jun '12

12 Jun '12

Hi, to avoid package incompatibilities with other rpm based distros, I am about to switch the rpm architecture to "armv7hl" again. "armv7l" will be used as backward compatibility, so it should not cause trouble. However, I will wait for the new gcc with new runtime linker path before doing an entire rebuild. Just in case you wonder why we will have both rpm architectures for some time. We will not hack the kernel to report (the not existing) armv7hl architecture, we will go with a hack in rpm instead assuming that armv7l hardware is always armv7hl. In case we want to have armv7l (or armv7nhl or whatever) later on in parallel, we will need to enhance the rpm dependency scripts to extend the keys similar to the 64bit approach. But there is no cross distro standard atm. 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

5 11

[opensuse-arm] icecream for armv7l broken
by Alexander Graf 06 Jun '12

06 Jun '12

Howdy, After a bit of debugging, I was able to isolate some build failures we have, like the following: > rpm: error while loading shared libraries: /lib/libselinux.so.1: unexpected reloc type 0x03 At least one major difference I can see in compiling between an icecream gcc invocation and a native gcc invocation is the following: > toonie:/home/abuild/rpmbuild/BUILD/libselinux-2.1.9/src> gcc -O2 -g -march=armv7-a -mfloat-abi=hard -mthumb -mabi=aapcs-linux -I../include -I/usr/include -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -fPIC -DSHARED -c -o enabled.lo enabled.c > enabled.c: In function 'is_selinux_enabled': > enabled.c:34:1: warning: visibility attribute not supported in this configuration; ignored [-Wattributes] > enabled.c: In function 'is_selinux_mls_enabled': > enabled.c:69:1: warning: visibility attribute not supported in this configuration; ignored [-Wattributes] > toonie:/home/abuild/rpmbuild/BUILD/libselinux-2.1.9/src> /usr/bin/gcc -O2 -g -march=armv7-a -mfloat-abi=hard -mthumb -mabi=aapcs-linux -I../include -I/usr/include -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -fPIC -DSHARED -c -o enabled.lo enabled.c So for some reason gcc doesn't seem to believe our linker knows what hidden attributes are. Weird, eh? So let's check out the gcc armv7l icecream build log: > checking for armv7l-suse-linux-gnueabi-as... no > checking what assembler to use... > checking for armv7l-suse-linux-gnueabi-ld... no > basename: missing operand > Try 'basename --help' for more information. > checking whether we are using gold... no > checking what linker to use... > checking for armv7l-suse-linux-gnueabi-nm... no > checking what nm to use... > checking for armv7l-suse-linux-gnueabi-objdump... no > checking what objdump to use... not found > checking for readelf... /usr/bin/readelf > checking what readelf to use... /usr/bin/readelf > checking assembler flags... > checking assembler for .balign and .p2align... no > checking assembler for .p2align with maximum skip... no > checking assembler for .literal16... no > checking assembler for working .subsection -1... no > checking assembler for .weak... no > checking assembler for .weakref... no > checking assembler for .nsubspa comdat... no > checking assembler for .hidden... no > checking linker for .hidden support... no > checking linker read-only and read-write section mixing... unknown Huh? It really doesn't know what its linker should be, so it isn't able to figure out its features, thus disables them internally. But why? Well, let's see what the s390 build has to say: > checking what assembler to use... /usr/s390x-suse-linux/bin/as > checking whether we are using gold... no > checking what linker to use... /usr/s390x-suse-linux/bin/ld > checking what nm to use... /usr/s390x-suse-linux/bin/nm > checking what objdump to use... /usr/s390x-suse-linux/bin/objdump > checking for readelf... /usr/bin/readelf > checking what readelf to use... /usr/bin/readelf > checking assembler flags... > checking assembler for .balign and .p2align... yes > checking assembler for .p2align with maximum skip... yes > checking assembler for .literal16... no > checking assembler for working .subsection -1... yes > checking assembler for .weak... yes > checking assembler for .weakref... yes > checking assembler for .nsubspa comdat... no > checking assembler for .hidden... yes > checking linker for .hidden support... yes > checking linker read-only and read-write section mixing... read-write Funny. The s390x target finds its cross binutils in /usr/s390x-suse-linux/. Why don't we find ours for armv7l then? Maybe it's because we don't have cross-armv7l-binutils that store something in /usr/armv7l-suse-linux/, but instead we have cross-arm-binutils that have their stuff in /usr/arm-suse-linux/? How does gcc's configure know where to search for the cross binutils? I'm fairly sure we're doing something pretty wrong there today :) Alex -- 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] openSUSE 12.2 Beta for ARM
by Alexander Graf 05 Jun '12

05 Jun '12

Hi Dirk and Coolo, Since Adrian is on FTO this week, this one goes to the 2 of you :). I would really like to see us publish a sort-of-working 12.2 Beta for ARM. Now that the official 12.2 beta is out, all we need to do is take the current state of openSUSE:Factory:ARM, branch that off into its own OBS project and freeze it, right? That would allow the build to settle down for said release, so we can have images for people outside to test and get eager to have a working 12.2 on ARM eventually! Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 3

Re: [opensuse-arm] armStoneA8: Failed to mount /dev
by Joop Boonen 03 Jun '12

03 Jun '12

On Sun, June 3, 2012 4:15 pm, Andreas FÃ¤rber wrote: > Am 03.06.2012 10:10, schrieb Alexander Graf: >> >> On 03.06.2012, at 06:35, Andreas FÃ¤rber wrote: >> >>> On the armStoneA8 board, using NBoot V14 and U-Boot, I'm trying to boot the downstream 3.3.7 kernel (BSP V1.1) from SD with a LimeJeOS rootfs on >>> SD. I had to reconfigure the kernel with CONFIG_LBDAF to mount the ext3[*] rootfs r/w. This is what I get now: >>> >>> [...] >>> mmc0: new high speed SDHC card at address b368 >>> IPv6 over IPv4 tunneling driver >>> mmcblk0: mmc0:b368 NCard 7.48 GiB >>> NET: Registered protocol family 17 >>> can: controller area network core (rev 20090105 abi 8) >>> mmcblk0: p1 >>> NET: Registered protocol family 29 >>> can: raw protocol (rev 20090105) >>> can: broadcast manager protocol (rev 20090105 t) >>> Registering the dns_resolver key type >>> VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2 s3c-rtc s3c64xx-rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) >>> kjournald starting. Commit interval 5 seconds >>> EXT3-fs (mmcblk0p1): using internal journal >>> EXT3-fs (mmcblk0p1): recovery complete >>> EXT3-fs (mmcblk0p1): mounted filesystem with ordered data mode VFS: Mounted root (ext3 filesystem) on device 179:1. >>> Freeing init memory: 148K >>> Failed to mount /dev: No such device >>> >>> Our rootfs definitely contains /dev, so what is this complaining about? >> >> Please make sure that you have support for tmpfs and (if running w/o initrd) devtmpfs in the kernel :). > > Thanks, found two devtmpfs options through search in menuconfig. > > Now I'm finally getting into the system but am seeing some failures (reformatted for readability): > > Starting System Logging Service... > Starting LSB: Purge old kernels... > Starting LSB: Configure the localfs depending network interfaces... Starting Login Service... > Starting Permit User Sessions... > Started Console System Startup Logging [ OK ] Started LSB: Framebuffer setup [ OK ] Failed to start System Logging Service [FAILED] See 'systemctl status syslog.service' for details. > Started LSB: Purge old kernels [ OK ] Started Permit User Sessions [ OK ] Starting Serial Getty on ttySAC0... > Started Serial Getty on ttySAC0 [ OK ] Starting Getty on tty1... > Started Getty on tty1 [ OK ] Starting D-Bus System Message Bus... > Started D-Bus System Message Bus [ OK ] Starting System Logging Service... > Failed to start System Logging Service [FAILED] See 'systemctl status syslog.service' for details. > Starting System Logging Service... > Started Login Service [ OK ] Failed to start System Logging Service [FAILED] See 'systemctl status syslog.service' for details. > Starting System Logging Service... > Failed to start System Logging Service [FAILED] See 'systemctl status syslog.service' for details. > Starting System Logging Service... > Failed to start System Logging Service [FAILED] See 'systemctl status syslog.service' for details. > Starting System Logging Service... > Failed to start System Logging Service [FAILED] See 'systemctl status syslog.service' for details. > Starting System Logging Service... > Failed to start System Logging Service [FAILED] See 'systemctl status syslog.service' for details. > > > linux:~ # systemctl > Failed to get D-Bus connection: No connection to service manager. > > But D-Bus seemed to have started "[ OK ]" above. > > linux:~ # pstree > systemdââ¬âagetty > ââconsole-kit-daeâââ64*[{console-kit-dae}] > ââcron > ââdbus-daemon > ââdhcpcd > ââloginâââbashâââpstree > ââpolkitdâââ{polkitd} > ââsshd > ââsystemd-journal > ââsystemd-logind > ââudevdâââ2*[udevd] > > What could be going wrong here? More kernel options needed? I've build a kernel for this board in :home:worldcitizen:armv7l kernel-armstonea8 . The config is also there. I've tested it quite some time ago. I don't know if I saw these errors. I use the kernel supplied by F&S Elektronik Systeme GmbH. > > Andreas > > -- > SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 NÃ¼rnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix ImendÃ¶rffer; HRB 16746 AG NÃ¼rnberg -- Regards, Joop. -- 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] gcc for aarch64
by Alexander Graf 01 Jun '12

01 Jun '12

Hi guys, I just learned from Peter that the AArch64 (armv8) port of gcc went public: http://old.nabble.com/-AARCH64---PATCH-0-3--AArch64-Port-td33907309.html This doesn't mean we can compile aarch64 code yet, as we're still lacking binutils to generate binary output from the assembly, but we're getting closer. Alex -- 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] kernel-tegra?
by Andreas Färber 01 Jun '12

01 Jun '12

Hello, Has anyone been successful in using the kernel-tegra package? I tried with the following Android boot image: ${DIR}/abootimg --create opensuse-tegra.img -c "name=kernel-tegra" \ -c "cmdline=mem=448M@0M console=tty0 tegraboot=sdmmc tegrapart=recovery:300:a00:800,boot:d00:1000:800,mbr:1d00:200:800 root=/dev/mmcblk1p1 rw rootwait" \ -c "kerneladdr=0x10008000" -c "ramdiskaddr=0x11000000" -c "tagsaddr=0x10000100" \ -k uImage-3.4.0-1-tegra -r initrd.cpio.gz where uImage-... is from the openSUSE:Factory:ARM kernel-tegra .rpm and initrd.cpio.gz is the same as for Joop's kernel-tegra-ac100 and the addresses are from my previous Ubuntu kernel. With this flashed, I just got a blank screen on my AC100. I wonder if we need to change the kernel config for it to build a zImage, too? Or might the above addresses be wrong for our kernel? Regards, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0