August 2013 - openSUSE ARM - openSUSE Mailing Lists

Re: [opensuse-arm] armv6 rootfs fails to build (kiwi problem?)
by Guillaume Gardet 20 Aug '13

20 Aug '13

Le 20/08/2013 17:05, Tony Su a écrit : > I found this, RPi req v6 > > Http://zq1.de/~bernhard/linux/opensuse/ <Http://zq1.de/%7Ebernhard/linux/opensuse/> > > Bernhard is a major figure building and supporting openSUSE. Yes, this private repo was veryhard to find, and it should be considered experimental. If you don't get an answer to your Q you may wanttolook him up. Yes, I know him and those images, but they are only armv5, not armv6. Guillaume > > Tony > > On Tuesday, August 20, 2013, Guillaume Gardet <guillaume.gardet(a)free.fr <mailto:guillaume.gardet@free.fr>> wrote: > > Hi, > > > > > > Le 20/08/2013 16:48, Tony Su a écrit : > > > > Hi Guillame, > > > > Am curious but also very interested in why you are building images like this one that already exists, in this case to have another go at RPi. > > > > No openSUSE armv6 image exists AFAIK. THe goal is to have a working openSUSE image for RPi. > > > > Would understand if it's only for exercise, but if you believe your result will be an improvement, that'd also be important to know. > > > > An improvement compared to what? > > > > > > Guillaume > > > > Tony > > > > On Aug 20, 2013 1:22 AM, "Guillaume Gardet" <guillaume.gardet(a)free.fr <mailto:guillaume.gardet@free.fr>> wrote: > >> > >> Hi, > >> > >> I have an armv6 rootfs which fails to build because it cannot find packages during build whereas repos are setup correctly. > >> > >> See: https://build.opensuse.org/package/show/home:Guillaume_G:branches:openSUSE:… > >> > >> Same rootfs builds fine for armv7. > >> > >> Is it a kiwi problem? > >> > >> > >> Regards, > >> > >> Guillaume > >> > >> -- > >> To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org <mailto:opensuse-arm%2Bunsubscribe@opensuse.org> > >> To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org <mailto:opensuse-arm%2Bowner@opensuse.org> > >> > > > > -- 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] Additional repos available for ARM
by Guillaume Gardet 20 Aug '13

20 Aug '13

Hi, We have some additional repos available for armv7. In OBS: * Games repo for 12.3: http://download.opensuse.org/repositories/games/openSUSE_12.3_Ports/ In packman: * Essential for 12.3 : http://pmbs.links2linux.de:82/Essentials/openSUSE_12.3_ARM/ Builds are on the way for : * Essential for Factory * Multimedia for 12.3 * Multimedia for Factory So, you can now play lots of games on your ARM device and install/update your gstreamer, ffmpeg, vlc and more. Tests and feedback are welcome. If you have ARMv7 devices you can provide ARM build power (through openvpn) to packman to help to build ARM packages. If you are interested, just ping me. 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] armv6 rootfs fails to build (kiwi problem?)
by Guillaume Gardet 20 Aug '13

20 Aug '13

Hi, I have an armv6 rootfs which fails to build because it cannot find packages during build whereas repos are setup correctly. See: https://build.opensuse.org/package/show/home:Guillaume_G:branches:openSUSE:… Same rootfs builds fine for armv7. Is it a kiwi problem? 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] Contrib images need to be fixed
by guillaume.gardet＠free.fr 16 Aug '13

16 Aug '13

Hi, Most Factory Contrib images need to be fixed because of JeOS updates. Could anyone have a look at it, please? Moreover, some contrib images are disabled. Would it be possible to re-enable them or are they disabled on purpose? 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] Bluez fails to build for armv6
by Guillaume Gardet 14 Aug '13

14 Aug '13

Hi, Bluez fails to build for armv6 but is needed for qemu which is needed to build Raspberry Pi image. So it would be good to fix bluez problem. It fails in test with: ******************************************************************************** [ 832s] + make check [ 832s] make --no-print-directory check-am [ 832s] make --no-print-directory check-TESTS [ 834s] FAIL: unit/test-eir [ 835s] make --no-print-directory all-am [ 835s] make[5]: Nothing to be done for `all-am'. [ 838s] ============================================================================ [ 838s] Testsuite summary for bluez 4.101 [ 838s] ============================================================================ [ 838s] # TOTAL: 1 [ 838s] # PASS: 0 [ 838s] # SKIP: 0 [ 838s] # XFAIL: 0 [ 838s] # FAIL: 1 [ 838s] # XPASS: 0 [ 838s] # ERROR: 0 [ 838s] ============================================================================ [ 838s] See ./test-suite.log [ 838s] ============================================================================ [ 838s] make[3]: *** [test-suite.log] Error 1 [ 838s] make[2]: *** [check-TESTS] Error 2 [ 838s] make[1]: *** [check-am] Error 2 [ 838s] make: *** [check] Error 2 [ 838s] error: Bad exit status from /var/tmp/rpm-tmp.5cCjxF (%check) ******************************************************************************** The log give us more info: ******************************************************************************** =================================== bluez 4.101: ./test-suite.log =================================== # TOTAL: 1 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: unit/test-eir =================== Running suite(s): EIR check_run.c:431: Error in call to timer_create: Function not implemented ******************************************************************************** It seems that timer_create function is not available. Sounds very strange. Any idea to solve this problem? 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] Panda board SPL broken?
by Guillaume Gardet 14 Aug '13

14 Aug '13

Hi, with JeOS panda image from Factory I get the following error (after workarounded BOOT files problem also reported for beagle, see previous thread): ******************************************************************************** OMAP4430 ES2.2 OMAP SD/MMC: 0 mmc_send_cmd : timeout: No status update Card did not respond to voltage select! spl: mmc init failed: err - -17 ### ERROR ### Please RESET the board ### ******************************************************************************** Does anyone have the same problem? I did not tried another SD card yet but this one is working fine with Raspberry Pi and in my camera, so I guess it is a panda problem. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 5

[opensuse-arm] Factory images broken!
by Guillaume Gardet 14 Aug '13

14 Aug '13

Hi, I tested beagle image from factory (but this problem should occur on all other boards) and it does not boot at all, with this message: ************************************************************ U-Boot SPL 2013.04 (May 28 2013 - 14:13:22) OMAP SD/MMC: 0 spl: error reading image u-boot.bin, err - -1 ### ERROR ### Please RESET the board ### ************************************************************ First problem is in BOOT partition, all available files are under a boot/ folder and nothing at the root of the partition. Then u-boot starts but I get this error: ******************************************************************************** U-Boot SPL 2013.04 (May 28 2013 - 14:13:22) OMAP SD/MMC: 0 U-Boot 2013.04 (May 28 2013 - 14:13:22) OMAP3630/3730-GP ES1.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0 *** Warning - readenv() failed, using default environment In: serial Out: serial Err: serial Beagle xM Rev A No EEPROM on expansion board Die ID #5e3c00011ff00000015739eb0a01c005 musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 1.800 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Peripheral mode controller at 480ab000 using PIO, IRQ 0 Net: usb_ether Hit any key to stop autoboot: 0 mmc0 is current device gpio: pin 173 (gpio 173) value is 0 gpio: pin 4 (gpio 4) value is 0 SD/MMC found on device 0 ** File not found uEnv.txt ** 1576 bytes read in 5 ms (307.6 KiB/s) Running bootscript from mmc0 ... ## Executing script at 80200000 kerneladdr=0x80200000 ramdiskaddr=0x81000000 mmc0 is current device 4338904 bytes read in 385 ms (10.7 MiB/s) 65842548 bytes read in 5656 ms (11.1 MiB/s) Unknown command '1' - try 'help' Wrong Image Format for bootm command ERROR: can't get kernel image! Booting from nand ... no devices available Wrong Image Format for bootm command ERROR: can't get kernel image! OMAP3 beagleboard.org # ******************************************************************************** I guess the "unknown command" problem comes from the u-boot script: ********** if itest 1${loadfdt} == 11; then setenv load_fdt 'ext2load ${bootdev} ${bootpart} ${fdt_addr} ${fdt}' else setenv load_fdt '1' fi ********** When u-boot want to run load_fdt for non device tree board, it tries to run 1. Which is wrong but should not be fatal. If (under uboot) I run: setenv boottype bootz and then: run doit the kernel starts but it crashed after 10/12 seconds. "file linux.vmx" returns: linux.vmx: Linux kernel ARM boot executable zImage (little-endian) Have we switched to zImage for all boards? at least the ones supported by default kernel? The kernel crash is maybe only a kernel problem and not related to the rest of this e-mail. 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] Status of Raspberry Pi for openSUSE
by Dirk Stöcker 14 Aug '13

14 Aug '13

Hallo, for half a year we're trying now to get openSUSE working on Raspberry Pi and still no success. The normal images don't build and the replacement image from http://en.opensuse.org/HCL:Raspberry_Pi works, but is ARM5 and thus does not work together with any project in the OBS, as these are all ARM6. On OBS it seems impossible to build anything from ARM5 anymore. So in my eyes the state is: - a non-standard image can be installed and works, but it is impossible to build packages for it. - all packages build in OBS are for ARM6, but can't be used, as I have no image to start from. Is there anything I overlook? How do I use Raspberry Pi with openSUSE and especially with the chance to build own packages for it? Ciao -- http://www.dstoecker.eu/ (PGP key available) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

10 20

[opensuse-arm] [Important] unification of AArch64 and ARMv6l under standard
by Dirk Müller 13 Aug '13

13 Aug '13

Hi, In an effort to get the ftp product tree building working finally on openSUSE:Factory:ARM, we've united the AArch64 and armv6hl trees into one standard/ repository. In cases where you linked openSUSE:Factory:ARM/armv6hl before, you should switch over to openSUSE:Factory:ARM/standard. Hopefully soon within the next hours there should be real content under: http://download.opensuse.org/ports/armv6hl/factory/repo/oss/ http://download.opensuse.org/ports/aarch64/factory/repo/oss/ 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] RFC armv6 default config
by Guillaume Gardet 13 Aug '13

13 Aug '13

Hi, our current default kernel for ARMv6 supports: * Versatile Platform Baseboard for ARM926EJ-S * Versatile Application Baseboard for ARM926EJ-S * Versatile platform from device tree The first 2 platforms are ARM926E which is armv5, not armv6! DT for versatile are also for PB and AB platforms. I would like to modify this configuration with a multi-platform armv6 (similar to armv7) with all supported platforms, including upstream Raspberry Pi, model B. Are you ok with that? Is there any objection? If everybody is ok, I will submit a patch to the kernel ML to do this update. 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