August 2013 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] Factory images fail to build
by Guillaume Gardet 17 Sep '13

17 Sep '13

Hi, all non-rootfs images in Factory fail to build with this error: ******************************************************************************** [ 1161s] Aug-28 10:18:01 <1> : Creating cpio archive... [ 1161s] Aug-28 10:18:01 <1> : EXEC [pwd] [ 1161s] Aug-28 10:18:01 <1> : EXEC [cd /usr/src/packages/KIWI-oem/oem/boot-VMX.SKsaMY/kiwi-VMXboot-5295 && find . | cpio --create --format=newc --quiet | gzip -9 -f > /usr/src/packages/KIWI-oem/oem/initrd-oemboot-suse-12.2.armv7l-2.7.1.gz] [ 1517s] Aug-28 10:23:57 <1> : Creating image MD5 sum... [ 1517s] Aug-28 10:23:57 <1> : EXEC [factor 130856257] [ 1517s] Aug-28 10:23:58 <1> : EXEC [cat /usr/src/packages/KIWI-oem/oem/initrd-oemboot-suse-12.2.armv7l-2.7.1.gz | md5sum - | cut -f 1 -d-] [ 1524s] Aug-28 10:24:05 <1> : EXEC [echo "4bb2c22a3b85568fac18e40b0aafe4bd 5051 25907" > /usr/src/packages/KIWI-oem/oem/initrd-oemboot-suse-12.2.armv7l-2.7.1.md5] [ 1524s] Aug-28 10:24:05 <1> : EXEC [rm -rf /usr/src/packages/KIWI-oem/oem/boot-VMX.SKsaMY] [ 1525s] Aug-28 10:24:05 <1> : Release package manager lock [ 1525s] Aug-28 10:24:05 <1> : EXEC [rm -f /var/lock/kiwi-init.lock] [ 1525s] Aug-28 10:24:05 <1> : Release package manager lock [ 1525s] Aug-28 10:24:05 <1> : EXEC [rm -f /var/lock/kiwi-init.lock] [ 1525s] Aug-28 10:24:05 <1> : EXEC [rm -f /var/cache/kiwi/zypper/zypper.conf.5295 /var/cache/kiwi/zypper/zypp.conf.5295] [ 1525s] Aug-28 10:24:05 <3> : Couldn't find kernel file: /usr/src/packages/KIWI-oem/oem/initrd-oemboot-suse-12.2.armv7l-2.7.1.kernel [ 1525s] Aug-28 10:24:05 <3> : KIWI exited with error(s) [ 1525s] Aug-28 10:24:05 <1> : EXEC [rm -rf /usr/src/packages/KIWI-oem/oem/boot-VMX.SKsaMY 2>&1] [ 1527s] /.build/build: line 371: 1087 Killed background_monitor_process [ 1529s] SysRq : Power Off [ 1529s] Power down. ******************************************************************************** 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

3 4

[opensuse-arm] Factory:Contrib for armStoneA8
by Andreas Färber 02 Sep '13

02 Sep '13

Hello, Can someone please create a "Contrib:armStone" subproject for devel:ARM:Factory and make me maintainer please? kernel-f+s from https://build.opensuse.org/project/show/openSUSE:12.2:ARM:Contrib:Armstone has been working fine on 12.3. Thanks, 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

3 5

[opensuse-arm] Chromebook S5P-MFC
by Guillaume Gardet 29 Aug '13

29 Aug '13

Hi, on my Chromebook running openSUSE 12.3, I noticed in dmesg that S5P firmwares were not found whereas kernel-firmware package is installed. The problem is that s5p-mfc-v6.fw and s5p-mfc.fw are in /lib/firmware/s5p-mfc and linux kernel is looking for those firmwares in /lib/firmware/. After making symlinks, no more complaint about missing firmwares. Which part is faulty? kernel-firmware or kernel-chromebook? What would be the best fix? Making a package with symlinks (if it is possible)? 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] What armv7hl can I use on the Raspberry PI.
by Chuck Payne 28 Aug '13

28 Aug '13

Guys, I see that the armv5 is gone, so what image can I use on the Raspberry, I don't see any images for armv6hl, so it safe to assume there is an image for the Pi on armv7hl? http://download.opensuse.org/ports/ aarch64/ 13-Aug-2013 15:56 - armv6hl/ 13-Aug-2013 16:22 - armv7hl/ 13-Mar-2013 12:30 - debug/ 13-Mar-2013 10:35 - ppc/ 27-Sep-2012 15:23 - update/ 16-Mar-2013 10:36 - Index of /ports/armv7hl/distribution/openSUSE-stable/images I didn't see any that say Pi. -- Terror PUP a.k.a Chuck "PUP" Payne (678) 636-9678 ----------------------------------------- Discover it! Enjoy it! Share it! openSUSE Linux. ----------------------------------------- openSUSE -- en.opensuse.org/User:Terrorpup openSUSE Ambassador/openSUSE Member Community Manager -- Southeast Linux Foundation (SELF) skype,twiiter,identica,friendfeed -- terrorpup freenode(irc) --terrorpup/lupinstein Register Linux Userid: 155363 Have you tried SUSE Studio? Need to create a Live CD, an app you want to package and distribute , or create your own linux distro. Give SUSE Studio a try. www.susestudio.com. See you at Southeast Linux Fest, June 7-9, 2013 in Charlotte, NC. www.southeastlinuxfest.org -- 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] factory not found
by Chuck Payne 28 Aug '13

28 Aug '13

Guys, I am trying to install software on my Raspberry PI, I am getting the error that Retrieving repository 'factory' metadata -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------[\] File '/media.1/media' not found on medium 'http://download.opensuse.org/ports/armv5tel/factory/repo/oss/' What do I need to do to fix this? Can I assume there update url? -- Terror PUP a.k.a Chuck "PUP" Payne (678) 636-9678 ----------------------------------------- Discover it! Enjoy it! Share it! openSUSE Linux. ----------------------------------------- openSUSE -- en.opensuse.org/User:Terrorpup openSUSE Ambassador/openSUSE Member Community Manager -- Southeast Linux Foundation (SELF) skype,twiiter,identica,friendfeed -- terrorpup freenode(irc) --terrorpup/lupinstein Register Linux Userid: 155363 Have you tried SUSE Studio? Need to create a Live CD, an app you want to package and distribute , or create your own linux distro. Give SUSE Studio a try. www.susestudio.com. See you at Southeast Linux Fest, June 7-9, 2013 in Charlotte, NC. www.southeastlinuxfest.org -- 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] No login with ttyS0 (JeOS for cubieboard)
by Johannes Nohl 27 Aug '13

27 Aug '13

Does someone know what I have to do to get a login on ttyS0? I can see cubieboard in the serial console booting, from u-boot to kernel, ending with: [ OK ] Started D-Bus System Message Bus. [ OK ] Started Login Service. [ OK ] Started YaST2 Firstboot. I tried to utilze systemd by adding serial-getty to the services: ln -s /usr/lib/systemd/system/serial-getty@.service /etc/systemd/system/getty.target.wants/serial-getty(a)ttyS0.service I used the image from http://download.opensuse.org/repositories/devel:/ARM:/12.3:/Contrib:/sunxi/…. Additionally I don't get eth0 up, whether on dhcp or static. Therefore I can't ssh inside. I really need the serial console. One of u-boot's env parameters is console=ttyS0,115200 (which isn't needed to see the boot stuff) so I guess the kernel takes this as an option. I'm thinking I'm missing stuff here because the underlaying JeOS is pretty small. Buz e.g. agetty is installed... Who can help me here? Johannes -- 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] ARMv7 kernel configs
by Guillaume Gardet 26 Aug '13

26 Aug '13

Hi, just a little question about armv7 configs. Recent kernel configs have disabled CONFIG_SWP_EMULATE (Emulate SWP/SWPB instructions). Is it on purpose? Moreover we have not enabled ThumbEE CPU extension (CONFIG_ARM_THUMBEE). Should we enable it? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 5

Fwd: Re: [opensuse-arm] Re: No login with ttyS0 (JeOS for cubieboard)
by Guillaume Gardet 25 Aug '13

25 Aug '13

Forward sent message to the list since I replied directly. :( Guillaume Le 24/08/2013 16:05, Johannes Nohl a écrit : > Hello Guillaume, > > 2013/8/21 Guillaume Gardet <guillaume.gardet(a)free.fr>: >> Le 21/08/2013 17:29, Johannes Nohl a écrit : >>> OK. I'm a bit clueless here. It may be that YaST firstboot stops the >>> boot process. But I can't be sure because I can't login. Anyhow when >>> turning firstboot of there's neither network nor tty. How can I solve >>> this? Thanks for any help. >> Remove the file /var/lib/YaST2/reconfig_system from filesystem and try to boot. It will boot without starting firstboot. >> >> Could you also send the content of boot.script file from boot partition, please? > thanks for replying. I really would like to get this going. In the > meanwhile I installed debian wheezy which worked perfectly so I can > rule hardware/kernel issues out. Furthermore I googled someone else > troubling the same result: > https://groups.google.com/forum/#!msg/cubieboard/LcE6MG-2YII/ (he > tried JeOSand XFCE packages). I got the same logging result as > attached there. I cannot access this google group. :( > > Please find attached the serial console log of the first boot after > flashing. After that I removed /var/lib/YaST2/reconfig_system and > booted again, see the second attachment. > > >From my point of view it isn't Firstboot or Serial Getty since it is > marked as started. Additionally I chrooted into the system once and I > could run firstboot (complaining about hardware of course). Thanks for > any help. > > My second guess would be the NIC. I can see (in my router's log) that > no new interface is comming up. Maybe the whole thing is freezing? Maybe, but strange. I have no cubieboard here, so I cannot test anything. Did you tried to enable a console on ttyS1? Did you plug a monitor? 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] Fwd: Post to opensuse-arm@opensuse.org denied
by Tony Su 20 Aug '13

20 Aug '13

Would be interesting if only ARMv5. Should be ARMv6 to run on RPi although I understand there are fewercompatibility issues between v5 and v6 compared to v6 and v7. Looking forward to your build. Tony On Tuesday, August 20, 2013, Guillaume Gardet <guillaume.gardet(a)free.fr> wrote: > > > Le 20/08/2013 17:05, Tony Su a =E9crit : >> 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 -- 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] armv6 rootfs fails to build (kiwi problem?)
by Guillaume Gardet 20 Aug '13

20 Aug '13

Le 20/08/2013 17:19, Tony Su a écrit : > Would be interesting if only ARMv5. > Should be ARMv6 to run on RPi although I understand there are fewercompatibility issues between v5 and v6 compared to v6 and v7. RPi is an armv6 and is also compatible with armv5 and previous. So RPi can run armv6 apps and also armv5 apps. But RPi cannot run armv7 apps. Our armv6 build should be better on RPi (compared to armv5 build) since it is armv6 and uses hardfloat. Guillaume > > Looking forward to your build. > > Tony > > On Tuesday, August 20, 2013, Guillaume Gardet <guillaume.gardet(a)free.fr <mailto:guillaume.gardet@free.fr>> wrote: > > > > > > 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/> <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> <mailto:guillaume.gardet@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> <mailto:guillaume.gardet@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> <mailto:opensuse-arm%2Bunsubscribe@opensuse.org <mailto:opensuse-arm%252Bunsubscribe@opensuse.org>> > >> >> To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org <mailto:opensuse-arm%2Bowner@opensuse.org> <mailto:opensuse-arm%2Bowner@opensuse.org <mailto:opensuse-arm%252Bowner@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

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

[opensuse-arm] Install arm64 packages
by Christoffer Dall 06 Aug '13

06 Aug '13

Hi all, I downloaded the root tarball from here (https://en.opensuse.org/Portal:ARM/AArch64) and have run the FS in the foundation model, but it seems I don't have vim or gcc or other build tools in that image. I tried using zypper to install it, but it can't find a vim package, it complains for vim-data telling me that nothing provides vim-base. I looked for gcc and make or development packages using "zypper se" but apparently I'm doing something wrong, because nothing shows up. Can anyone tell me what I'm doing wrong? Thanks, -Christoffer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 3