- openSUSE ARM

[opensuse-arm] Cross-compiling for ARM
by Stefan Bruens 07 Jul '15

07 Jul '15

Hi, I tried to cross-compile some stuff for ARMv7hl on a x86_host, but have some issues. The installed compiler/binutils are: cross-armv7hl-gcc49-4.9.0+r211729-2.1.7.x86_64 cross-arm-binutils-2.25.0-215.1.x86_64 both from the devel:gcc OBS repository The first issue is the assembler (as) is not found by the compiler. According to "armv7hl-suse-linux-gnueabi-gcc-4.9 -v --print-search-dirs" it uses: /usr/lib64/gcc/armv7hl-suse-linux-gnueabi/4.9/ /usr/lib64/gcc/armv7hl-suse-linux-gnueabi/ /usr/lib64/gcc/armv7hl-suse-linux-gnueabi/4.9/../../../../armv7hl-suse-linux- gnueabi/bin/armv7hl-suse-linux-gnueabi/4.9/ /usr/lib64/gcc/armv7hl-suse-linux-gnueabi/4.9/../../../../armv7hl-suse-linux- gnueabi/bin/ and then falls back to $PATH. I can work around this by setting the GCC env var COMPILER_PATH to /usr/arm- suse-linux-gnueabi/bin/ , where the binutils are located. The problem here obviously is the different architecture in the gcc and binutils package, as the last search dir entry points to /usr/armv7hl-suse- linux-gnueabi/bin/ instead of /usr/arm-suse-linux-gnueabi/bin The second issue it hit is a missing "unwind.h". The x86_64 gcc provides one for its arch in /usr/lib64/gcc/x86_64-suse-linux/4.9/include/unwind.h, but the armv7hl gcc is missing it. Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 work: +49 2405 49936-424 -- 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] Experiences with Build317.3 for RPi2
by Freek de Kruijf 05 Jul '15

05 Jul '15

Still the same problem as before. The system boots the openSUSE kernel, which apparently crashes. After which it boots again. The partitioning of the SD card does not seem to changed. -- fr.gr. member openSUSE Freek de Kruijf -- 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] Build326.4 for RPi1 does not produce a proper ext4 partition
by Freek de Kruijf 04 Jul '15

04 Jul '15

I copied this image to my SD card and tried to mount the ext4 partition. Using parted showed that it it was not a proper ext4 partition. Did not know how to make it right without destroying the content. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 1

Re: [opensuse-arm] Experiences with Build325.4 for RPi1
by Freek de Kruijf 01 Jul '15

01 Jul '15

Op woensdag 1 juli 2015 13:53:47 schreef Alexander Graf: > On 30.06.15 17:43, Freek de Kruijf wrote: > > Op dinsdag 30 juni 2015 11:49:09 schreef u: > >> On 06/30/15 11:24, Freek de Kruijf wrote: > >>> Op dinsdag 30 juni 2015 10:57:31 schreef Alexander Graf: > >>>> On 06/30/15 10:55, Freek de Kruijf wrote: > >>>>> Earlier a second boot of a system generated with this build for > >>>>> Raspberry > >>>>> Pi 1B did not work. Now I have a system that works and can be booted > >>>>> again. > >>>>> > >>>>> However trying to start a module with yast (ncurses), I tried network, > >>>>> software repositories and software all end in the following error > >>>>> message: > >>>>> > >>>>> /sbin/yast: line 426: 19947 Segmentation fault $ybindir/y2base > >>>>> $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS > >>>>> > >>>>> However 19947 in the above message differs with the type of module > >>>>> called > >>>>> and with the locale used. > >>>>> > >>>>> The repository still does not contain the ruby 2.2 modules for > >>>>> libstorage. > >>>>> I build these modules, which went OK. I noticed gcc5 was used. > >>>>> > >>>>> I will continue with this build to configure the applications I use. > >>>> > >>>> Do you think you could gdb the y2base binary to figure out where > >>>> exactly > >>>> it segfaults? > >>> > >>> Alex, I have no experience with gdb. I know it is used to debug and one > >>> can > >>> set breakpoints and step through the code, but that's all I know. > >> > >> No worries, there's always a first time :). In this case, all we need is > >> to attach to the program and then do 'bt' when we see the segfault. > >> > >>> I tried to run yast in one console and did "gdb -p process-id" in > >>> another > >>> after installing yast2-core-debugger. However it likes to have > >>> yast2-core- > >>> debuginfo which is not available. After giving a c in gdb and selecting > >>> software in the ncurses console, gdb continues with the following > >>> output: > >>> > >>> (gdb) c > >>> Continuing. > >>> Detaching after fork from child process 20159. > >>> [Thread 0xb601f450 (LWP 20077) exited] > >>> [Thread 0xb631b450 (LWP 20076) exited] > >>> [Inferior 1 (process 20075) exited normally] > >> > >> This means that the process was doing just fine, no segfault. So maybe a > >> different PID was the one broken? Which PID did you attach to? According > >> to the log, "y2base" is the application that faults. > >> > >> If you can't find it, try to attach strace -f to the yast binary to > >> figure out which binary gets executed. The strace should also at least > >> print out which PID segfaulted. > > > > Attached you will find strace.2. I can't find anything about a segfault. > > Search for this line: > > [pid 25753] --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, > si_addr=0x10} --- > > That's where the segfault occurs :). I entered the following bug in bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=936788 The problem is apparently in the package yast2-pkg-bindings. -- fr.gr. member openSUSE Freek de Kruijf -- 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] Experiences with Build326.2 for RPi1 and Build316.1 for RPi2
by Freek de Kruijf 01 Jul '15

01 Jul '15

The Build for RPi1 works, but has the same problem as with the previous build when trying to use YaST with ncurses. The Build for RPi2 does not work. The same problem. After booting the openSUSE image the system boots from the start after some time and repeats this. So apparently the openSUSE image crashes. Inspecting the micro-SD card after this process shows no changes in the partitioning of this card. -- fr.gr. member openSUSE Freek de Kruijf -- 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] Experiences with Build325.4 for RPi1
by Freek de Kruijf 30 Jun '15

30 Jun '15

Earlier a second boot of a system generated with this build for Raspberry Pi 1B did not work. Now I have a system that works and can be booted again. However trying to start a module with yast (ncurses), I tried network, software repositories and software all end in the following error message: /sbin/yast: line 426: 19947 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS However 19947 in the above message differs with the type of module called and with the locale used. The repository still does not contain the ruby 2.2 modules for libstorage. I build these modules, which went OK. I noticed gcc5 was used. I will continue with this build to configure the applications I use. -- fr.gr. member openSUSE Freek de Kruijf -- 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] Experiences with Build325.3 for RPi1 and Build315.2 for RPi2
by Freek de Kruijf 25 Jun '15

25 Jun '15

Both have the same problem starting slow. The fix for this is on its way. It takes a bit more than 10 minutes before the RPi1 system really starts the start up process. I could follow this process because I had these systems connected via HDMI to my TV monitor. The set up of RPi1 also takes about 10 minutes. O.a. a new initrd is being build. The start of the RPi2 is repeating itself and never finishes. After the slow start RPi1 end up in a workable state in a headless situation. I can connect via ssh to the system via the Ethernet connection. I tried a zypper up, and as to be expected: Nothing to do. On the RPi1 I updated libstorage6 libstorage-ruby to my own earlier generated versions. After this "yast network" works. I changed nothing in the network configuration. However I add an LLADDR=<MAC address> to /etc/sysconfig/network/ifcfg-eth0 right after the xzcat process on my desktop. So I know what IP-address the RPi systems get from my DHCP server. After closing down the RPi1 system using "shutdown -r now", the RPi1 system does not boot anymore. There is no output via HDMI anymore. Not even the small messages I saw when booting the freshly made SD card. So I assume the BOOT partition is not properly build. I assume the UEFI partition is not touched in the set up process. The RPi2 system does not work. On my TV monitor the first 3 characters on a line are not displayed. I searched for a solution and found that setting overscan_left and overscan_right in config.txt on the UEFI partition could solve this problem. I tried 16 and 24. It does not seem to have any effect, except when setting these values to 20, in which case the I get a distorted display. -- fr.gr. member openSUSE Freek de Kruijf -- 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] Building existing package for armv7hl
by Miklos Vajna 25 Jun '15

25 Jun '15

Hi, There are a number of repos that don't have ARM enabled, e.g. server:irc. I supposed it's possible to build e.g. server:irc/bitlbee locally for armv7hl, but I failed to find out how to do so. ;-) On x86_64, after 'osc co repo/package', I can build a binary for 13.2 using 'osc build openSUSE_13.2'. However, here I can't seem to do that: $ osc build openSUSE_13.2 armv7l is not a valid arch for the repository openSUSE_13.2, use one of: i586, x86_64 or $ osc build openSUSE_13.2_ARM openSUSE_13.2_ARM is not a valid repository, use one of: SLE_11_SP3, SLE_12, openSUSE_13.1, openSUSE_13.2, openSUSE_Factory So how to build an existing package locally for armv7hl? (I think in this case the package does not depend on anything that's not provided by the stock 13.2 repo.) Thanks, Miklos

2 4

[opensuse-arm] conflicts with kernel-default-4.0.5-2.3.armv6hl
by Michael Ströder 23 Jun '15

23 Jun '15

HI! When upgrading kernel-default from 4.0.5-2.1 to 4.0.5-2.3 there are various file conflicts reported (see end of messages below). I did not let zypper finish the upgrade. So I can't tell whether it would work later. Ciao, Michael. -------------------------- snip -------------------------- [..] File /lib/modules/4.0.5-2-default/kernel/sound/usb/line6/snd-usb-toneport.ko from install of kernel-default-4.0.5-2.3.armv6hl(openSUSE-Factory-repo-oss) conflicts with file from package kernel-default-4.0.5-2.1.armv6hl(@System) File /lib/modules/4.0.5-2-default/kernel/sound/usb/line6/snd-usb-variax.ko from install of kernel-default-4.0.5-2.3.armv6hl(openSUSE-Factory-repo-oss) conflicts with file from package kernel-default-4.0.5-2.1.armv6hl(@System) File /lib/modules/4.0.5-2-default/kernel/sound/usb/misc/snd-ua101.ko from install of kernel-default-4.0.5-2.3.armv6hl(openSUSE-Factory-repo-oss) conflicts with file from package kernel-default-4.0.5-2.1.armv6hl(@System) File /lib/modules/4.0.5-2-default/kernel/sound/usb/snd-usb-audio.ko from install of kernel-default-4.0.5-2.3.armv6hl(openSUSE-Factory-repo-oss) conflicts with file from package kernel-default-4.0.5-2.1.armv6hl(@System) File /lib/modules/4.0.5-2-default/kernel/sound/usb/snd-usbmidi-lib.ko from install of kernel-default-4.0.5-2.3.armv6hl(openSUSE-Factory-repo-oss) conflicts with file from package kernel-default-4.0.5-2.1.armv6hl(@System)

2 1

[opensuse-arm] Newest images for RPi1 and RPi2 are not usable headless
by Freek de Kruijf 23 Jun '15

23 Jun '15

I tried Tumbleweed Build325.1 for RPi1 and Build314.1 for RPi2 in a headless situation, but both do do not end with an active Ethernet connection. Is this to be expected? u-boot problem? -- fr.gr. member openSUSE Freek de Kruijf -- 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 on Archos tablet
by ben 23 Jun '15

23 Jun '15

Hi All, Having a old Archos 10 1 internet tablet with ARM cpu 1GHz ARM Cortex A8 and a A101IT-V6 board . Is it possible to get openSUSE as a native system on this tablet. Its now on Android 2.4.83 and has Angstrom in the "bios" There was a dual boot possibillity once but is that also with openSUSE ARM ? Greetings Ben Henderson aka Benmh on the forum -- 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] KIWI vs btrfs
by Andreas Schwab 22 Jun '15

22 Jun '15

Since the JeOS arm64 EFI images has been switched to use btrfs they fail due to ENOSPC. Apparently kiwi underestimates the overhead when computing the size of the disk. https://build.opensuse.org/package/live_build_log/openSUSE:Factory:ARM/JeOS… Andreas. -- Andreas Schwab, SUSE Labs, schwab(a)suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- 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] Factory/Tumbleweed and the switch to GCC 5.x
by Dirk Müller 22 Jun '15

22 Jun '15

Hi, as you might know, Factory is currently in preparation of transitioning to use GCC 5.0.x as the system compiler. There are several oddities to sort out with that, and I would expect additional issues for our ARM architectures in the form of miscompiles and ICE's. To find those issues before they happen, I've created a Staging project of Factory which builds against GCC 5: https://build.opensuse.org/project/show/openSUSE:Factory:ARM:Staging:A its not the full factory tree, but the "DVD" ring (e.g. more or less what openqa tests) so we should be able to not only see build failures specific for aarch64 but also are maybe able to run openqa against it to verify that things are working smoothly. You're welcome to help and debug / fix issues there. 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 2

[opensuse-arm] RPi 2 XFCE image
by David Byte 19 Jun '15

19 Jun '15

In trying to chase down the issue on my RPi 2 and the graphics I performed a zypper up (93 packages). After giving a serious wait (20 minutes or so), I issued a reboot command. Now, the system will not boot. Thoughts? -- David Byte Sr. Technology Strategist Alliances and Integrated Systems SUSE dbyte(a)suse.com (P)918.528.4422 www.suse.com -- 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] kernel 3.11.4 fails to build with gcc 5
by Guillaume Gardet 18 Jun '15

18 Jun '15

Hi, I updated kernel-raspberrypi config to get initrd support but it fails to build with gcc 5. :( It is a kernel 3.11.4 where I added include/linux/compiler-gcc5.h Any idea how to fix it? https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:Raspberry… Guillaume -- 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] R:R:I am Lost: No Boot
by Edgar Dombrowski 18 Jun '15

18 Jun '15

Hi Raspi-Friends. First thanks to Alex, Freek et remerciements pour Guillaume.for indicating the Repos for the various files for the Raspi B and Raspi 2 and pointing out the different versionS JeoS; XCFE and LXQT. I have downloaded the there xz.files and installed them on a sd-stick. But when, I get the folowing messages: > Net: Net initialization skipped > No ethernet found ---------> Cable was connected to an HDLC-Router > hit any key to stop autoboot: 2 > 1 > 0 > switch to partitions #0: OK > mmc0 is current device > scanning mmc0:1... > Found U-Boot script /boot.scr > reading /boot.src > 115 bytes read in 420 ms (0 Bytes/s) > # executing script at 00000000 > 2708 bytes read in 420 ms (1000 Bytes/s) > # executing script at 00000200 > 4389568 bytes read in 56550 ms (75.2 KiB/s) No further reaction Do you have any explanation why the boot process had stopped? Thanks for you assistance. Edgar, DJ3PU, Munich P.S. I am preparing an article to be included in Magazine of the German Amateur Radio Club (DARC) on implementing Ham Radio Programs into the Rasberry Pi, succeding up to today with Debian-Squeeze, but with OpenSUSE ??? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 6

[opensuse-arm] AArch64 image format question
by Guillaume Gardet 17 Jun '15

17 Jun '15

Hi, In http://download.opensuse.org/ports/aarch64/tumbleweed/images/ most images are in "*.install.tar.xz" format instead of "*.raw.xz"; except for vexpress64 and old EFI images (which should be wiped). It seems it is because it uses "installpxe=true" option in kiwi file. Am I right or wrong? 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

[opensuse-arm] Support for Banana Pi
by Jeff Mahoney 16 Jun '15

16 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all - For some time I've had a Banana Pi device running an openSUSE 13.2 image that I downloaded from the Banana Pi site. Over time, I'd been gradually dragging it forward with self-built vendor kernels and u-boot, hoping that it wouldn't fall apart. The other day, I installed the Kernel:stable kernel-default and the Factory u-boot and it all just worked! Since the openSUSE ARM team has done such a fantastic job getting all of this stuff integrated, I decided to see what was necessary to get real out-of-the-box support set up. The effort was literally just adding 6 lines to two files. Super easy! So, I'm happy to share the results: https://en.opensuse.org/HCL:BananaPi The next time the Tumbleweed JeOS images are built, they will include Banana Pi support! Thanks to Dirk for his help and encouragement getting this included. Great work, team! - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) iQIcBAEBAgAGBQJVeuVhAAoJEB57S2MheeWyMxoP+wZ24jzzRp6MQKZ+3kzUoVu5 MUY+Zk8fDS3loIRHN39QoI5NAWnvPy154Q9GtY93YlVXwvxcI+8+S02n0Rx7j2DV VETQP33wMBPvIQ+SHgq0m6+hw83UiPKnTjHaHB80xF7clv+cxsO8Mxkndaytyn0u bTZTVMGQ/Qn8v9srKK15a6Pw692RvrhYX3/v3ZeF8DHQJto5CAwCTZNIrx8SYRpT +GlFjq88CipT9vHEow2TVnSR6x2nG+HxezXiDl+itU8IU7pSTGHgeS7MfXbCZP3E Mb6cW03WR+6AYSfIwFd8OaoBhY1iTQdTI5YPTSYHKfUyqnRf4eyNgO7NgyqDp+L/ FANZ8n5HqUalDck6WKhGDMA2n1JDKKl+XUDYiAMqtpY7hNmhVfskw0FHvZvxd3J5 ES/jWG6FBuq+UEianWV9+qMAGU6eNjcveqHleMhqt+LvJpjPricEbPAa6xyqf5+w qWF8sRpPiCh3exyf76UuzEpfVcQ1aAaWD9sJrCj+72VZQgm4U2aQ5dG22ItpT6bL ZdYJkTODG4ats/RKMUAkoDU6TreF9D7IIDReCNyDI9IzfTvo+i9D9xmF1zqGE8Jl 6EnzXQYnTMOwxLjXGWswT45tFfKlipaPUN2d8y2KWzzJ3kvVN5aK4uUteHh0Dm1c 04UDa4++OFXLw+JGQgbD =Eo8e -----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

3 3

Re: [opensuse-arm] Factory: boot.scr not updated
by Guillaume Gardet 15 Jun '15

15 Jun '15

Hi Marcus, Le 09/06/2015 12:22, Marcus Schäfer a écrit : > Hi, > >>> kiwi 7.02.54 is building, do you need a factory submit request ? >> Yes, please. > ok, but I have to wait for input to bug 931634 before I do the next > submission New kiwi is now in Factory and some images have been rebuilt and I tested one. Now, boot.script is updated by setupUBoot.sh script BUT boot.scr is not generated from this new boot.script, because installUBoot.sh is not found (checked in kiwi log). :( Both scripts are in initrd but no more in rootfs. I guess installUBoot.sh may be called when mmc rootfs has been remounted? 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 RPi2 image - no console on HDMI after first reboot
by Philip Vossler 13 Jun '15

13 Jun '15

The latest build factory image I've tested today (openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-1.12.1-Build311.1.raw.xz ) surrvive reboots and is accessible via ssh but after the first reboot there is no HDMI console. It does take a while to start but looks like its functional - I will need HDMI, so I'm going to try and find out why it's not working. Thanks for the work on this, really appreciated. Phil Vossler -- "You can not play God and wash your hands of things that you've created" William Adama -- 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] XFCE tumbleweed image problem
by David Byte 12 Jun '15

12 Jun '15

Well, there is definitely a problem with the tumbleweed image for xfce on the RPI 2.. The error I am seeing right now is this: xfce4-session: symbol lookup error: /usr/lib/libEGL.so.1: undefined symbol: glDiscardFrameBufferEXT I am sure I solved a similar issue before on the RPI I had, but I don't remember how. Any thoughts? David Byte Sr. Technology Strategist Alliances and Integrated Systems SUSE dbyte(a)suse.com (P)918.528.4422 www.suse.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] RPi2 images
by Philip Vossler 12 Jun '15

12 Jun '15

Please can someone advice if there is a known good image for the Raspberry Pi 2? The tumbleweed images appear to have issues. A pointer to a good 13.1 or 13.2 image would be really helpful. Thanks Phil Vossler -- "We don't have to survive, we have to deserve to survive.....You can not play God and wash your hands of things that you've created, sooner or later that day comes and you can't hide from the things that you've done anymore."...William Adama -- 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] E17 images rename
by Guillaume Gardet 12 Jun '15

12 Jun '15

Hi, Enlightenment bump from version 17 (0.17) to 19 (0.19), so E17 name is no more valid. Should we just rename it to E19. Or to Enlightenment, or something else? I would prefer Enlightenment, even if it is a bit long (and our images name are already long), otherwise, we should update things again when E20 or E21 will be out. Any opinion? Guillaume -- 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] BeagleBone black image not working?
by Zack Piper 11 Jun '15

11 Jun '15

Hi, Sorry to be a nuisance, but I have yet to obtain a serial cable for my BeagleBone Black. http://download.opensuse.org/ports/armv7hl/factory/images/openSUSE-Tumblewe… doesn't seem to boot at all (no LED indicators). It had previously booted with an earlier image (of which I have lost, and forgotten the filename). If somebody could flash it on there's and investigate, I'd be very appreciative (I can't because of the lack of mini-HDMI, or serial cable). Thanks! -- Zack Piper <zack(a)apertron.net> http://apertron.net

3 4

[opensuse-arm] Raspberry Pi 1 and GPT partition really booting?
by Guillaume Gardet 11 Jun '15

11 Jun '15

Hi, I tested (hybrid) GPT partitionned images for Raspberry Pi and it does not boot at all (even the GPU firmware which is the 1st stage). Is there someone here who booted such an image? If so, which Pi version and which openSUSE image version? Otherwise, I would like to revert to FAT16 boot partition. Guillaume -- 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] elementary needs to be rebuild
by Guillaume Gardet 11 Jun '15

11 Jun '15

Hi, Could an admin of Factory:ARM trigger a rebuild of elementary, please. It does block some packages (e17 and others) and E17 images build too. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 8

[opensuse-arm] Wiki page update
by Guillaume Gardet 11 Jun '15

11 Jun '15

Hi, I reworked openSUSE:AArch64 wiki page: https://en.opensuse.org/openSUSE:AArch64 and I created HCL:AArch64_EFI: https://en.opensuse.org/HCL:AArch64_EFI for generic EFI boards. If you have any comments, please share or edit wiki directly. 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] I am lost
by Edgar Dombrowski 10 Jun '15

10 Jun '15

Hi, Raspi-friends. With your activities to implement arm6 and arm7files for a variety of miniboards, I am lost to find the actual versions for RasperryPi B+ (am6) and the new Raspi 2B+ (arm7). Using OpenSuse since over 20 years, I prefer it instead of die actual Debian-Version. Thanks for your assistance Edgar Dombrowski, DJ3PU, Munich -- 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] RPi1 crashes during downloading phase of "zypper up"
by Freek de Kruijf 10 Jun '15

10 Jun '15

I do a "zypper up --download-only" on my Tumbleweed RPi1 system which is connected using Wi-Fi to the network. Rather regularly I get messages about a wrong checksum. But after discarding such a package and a retry it is downloaded OK. However somewhat later during a download the system crashes and restarts. I did not experience such a problem in earlier updates using an Ethernet connection. How can I investigate such a problem? Retrying the whole process gives the crash at another point. -- fr.gr. member openSUSE Freek de Kruijf -- 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] Problem using YaST because rebuild of ruby packet is blocked by boost library
by Dirk Müller 10 Jun '15

10 Jun '15

Hi Freek, >> A new factory ftp tree has been published (finally). Does that one >> work as well for you? > It works for RPi2 (date is June 3), but for RPi1 it is not published yet (date > still February). Great, thanks for confirming. ARMv6hl also published now, but the package is old due to it no longer building: [ 7148s] +qemu: uncaught target signal 11 (Segmentation fault) - core dumped We need one of the qemu experts to look into that. 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] Signing key for repository 'Factory-Contrib-RPi' expires
by Freek de Kruijf 10 Jun '15

10 Jun '15

I get the following message when trying to update my RPi1 system: Retrieving repository 'Factory-Contrib-RPi' metadata ---------------------------------------------------------------------[\] The gpg key signing file 'repomd.xml' will expire in 9 days. Repository: Factory-Contrib-RPi Key Name: devel:ARM OBS Project <devel:ARM@build.opensuse.org> Key Fingerprint: 1D6571D6 77CD36CE F6B93856 16C5D54F 3F546F34 Key Created: Wed Apr 10 13:47:53 2013 Key Expires: Fri Jun 19 13:47:53 2015 (expires in 9 days) Rpm Name: gpg-pubkey-3f546f34-51655169 -- fr.gr. member openSUSE Freek de Kruijf -- 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] ARM build workers updated
by Dirk Müller 09 Jun '15

09 Jun '15

Hi, I just finished updating the majority of armv7l/aarch64 build workers to newer software versions (qemu 2.3.0, kernel 4.0.4, various bug + security fixes). It looks good to me, and I also fixed a few broken ones alongway, so we have more build power than before. Let me know if there are new issues. 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] Factory: boot.scr not updated
by Guillaume Gardet 09 Jun '15

09 Jun '15

Hi, after testing some factory images, it appears that boot.scr/boot.script are not updated, so board is unbootable after first boot. Anything changed in config or kiwi? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 19

[opensuse-arm] Difference between Release supported platforms and Community supported platforms
by Guillaume Gardet 09 Jun '15

09 Jun '15

Hi, On this page: https://en.opensuse.org/openSUSE:Supported_ARM_boards What is the difference between "Release supported platforms" and "Community supported platforms"? I though it was based on upstream/downstream kernel, but it seems I am wrong, or the list needs a big update. Guillaume -- 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] Problem using YaST because rebuild of ruby packet is blocked by boost library
by Freek de Kruijf 08 Jun '15

08 Jun '15

I reported a bug in http://bugzilla.suse.com/show_bug.cgi?id=933274 about an Internal error in YaST. This problem is caused by a non-up-to-date ruby module on armv7l which is blocked by a boost library. Is it possible to look into the problem with the boost library in armv7l? -- fr.gr. member openSUSE Freek de Kruijf -- 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] Image repos needs cleanup
by Guillaume Gardet 08 Jun '15

08 Jun '15

Hi, in http://download.opensuse.org/ports/armv7hl/factory/images/ we need to remove all *Factory* images since they have been renamed *Tumbleweed*. Contrib repos should be affected too. 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] OS 13.2 for Raspi B
by Edgar Dombrowski 01 Jun '15

01 Jun '15

Hi, Raspbi friends. I am trying to install dhe OS13.2-xxx JeOS-xx Build 36.3 on my< Raspi-B Initializatio n using YAST ok. But I try to install other files according to the rules outlined in HCL:RaspberryPi, all the zypper commands fail. 1. zypper update says repository opneSUSE13.2-repo-update seems to be outdated. Consider using any different mirror or repo. 2. zypper ref says Repository: 13.2-Contrib-RaspberryPi is up to date (same for repo-oss and repo-update 3. I want e.g. to install zypper install yast2-basis, I get the same reply as per 1) and in addition no provider for yast2_basis found. I would appreciate any support. Thanks for your help 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] kiwi - Add bootflag to partition #2 when vboot is used
by Guillaume Gardet 29 May '15

29 May '15

Hi Marcus, now, u-boot lists all bootable partitions to look for boot scripts. If no partition has a bootflag, it falls back to 1st partition. This break Chromebook (and maybe Raspberry Pi?) images, since 1st partition is hidden and we use partition 2 for our boot script, kernel and initrd. Could we add the boot flag to partition number 2 when vboot is used? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 7

[opensuse-arm] aarch64 build workers updated
by Dirk Müller 28 May '15

28 May '15

Hi, I just updated the aarch64 build workers to a newer host kernel. Let me know if there are new issues. 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] openQA : ARM qemu and real hardware?
by Guillaume Gardet 28 May '15

28 May '15

Hi, I know that some work have been done to get openQA working on ARM through qemu, but also on real hardware. What is working for now? I would like to perform some tests and maybe contribute, if I am able to do so. So, please share any hints/pointers that could help. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 4

[opensuse-arm] sunxi device tree outdated
by Frank Kunz 28 May '15

28 May '15

Hi, it seems that there is a build dependency missing between kernel and device tree meta packages: Logs taken from (build today afternoon): https://build.opensuse.org/package/binary/home:frank_kunz:branches:openSUSE… contains up to date kernel: kernel-default|(none)|4.0.1|1.1|armv7hl|obs://build.opensuse.org/openSUSE:F… But the device tree is still the old one: dtb-sun4i|(none)|4.0.0|40.2|armv7hl|obs://build.opensuse.org/openSUSE:Facto… Br, Frank -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 8

[opensuse-arm] 2 Questions
by Edgar Dombrowski 26 May '15

26 May '15

Hi, raspi-friends. I am trying to compile a ham-radio-terminal program TNT using OS-13.2-Jeos-Version downloaded on 28-2-15 , but I get two error messages when trying to install "ncurses-dev: using zypper: 1. repository opensuse 13.2-repository-update appears to be outdated 2. no provider for nvurses-dev. Any suggestion? Thank you for your assistance 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

2 1

[opensuse-arm] RaspberryPi and openSuse 13.2
by Thomas Aichinger 21 May '15

21 May '15

Hi, I run into a problem with my RasPi Model B+ V1.2 with openSuse 13.2. I type: raspi:~ # cat /proc/cpuinfo processor : 0 model name : ARMv6-compatible processor rev 7 (v6l) Features : swp half thumb fastmult vfp edsp java tls CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xb76 CPU revision : 7 Hardware : BCM2835 Revision : 0000 Serial : 0000000000000000 From serveral other sources I heard that Hardware should be BCM2708, Revision 0010 and there should be a valid serial number. The same hardware with raspbian says: Hardware : BCM2708 Revision : 0010 Serial : 00000000c2c2clcfbb The problem is that many libs are looking into this information to determine what type of raspi they are running on. Furthermore serial not set properly means that raspi does not have a stable MAC. Every time you boot it has another MAC. Any suggestions how I can fix this? -- Viele Grüße Thomas Aichinger ---------------------------- http://www.datamagic.at ---------------------------- Data Magic Datenservice GmbH Schönbrunner Straße 140 1120 Wien -- 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] Updating RPi 2B image to kernel 4.0.1 leaves non-bootable system
by Freek de Kruijf 19 May '15

19 May '15

I had a running image on my RPi 2B and saw kernel 4.0.1 being available. Using zypper I updated the kernel, but after that the system was no longer bootable. The newest image still has a 3.19 kernel. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 7

[opensuse-arm] Fwd: raspberry PI 2
by Sean Fabian 19 May '15

19 May '15

Evening All I require your assistance in the following two fields Where can I find the hal package for armv7(Raspberry PI 2)? and do I need to rebuild it for armv7? How can I rebuild the openvpn package for armv7, to have a custom compiled openvpn? Greetings Sean -- 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] yast error when reading network device configuration
by Frank Kunz 17 May '15

17 May '15

Hi, when testing the image: https://build.opensuse.org/package/binaries/home:frank_kunz:branches:openSU… I got: Internal error. Please report a bug report with logs. Details: undefined method `ReadHardware' for #<Yast::LanItemsClass:0xf044b8> Caller: /usr/share/YaST2/modules/LanItems.rb:988:in `ReadHw' when I try to change the network settings in yast. Is that a new issue? Any ideas? Br, Frank -- 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] Raspberry Pi 2 and rrdtool: undefined symbol glDiscardFramebufferEXT
by Robert Kaiser 15 May '15

15 May '15

Hi everyone, For one thing: I just bought a Raspberry Pi 2, and I was and am amazed that I can use openSUSE on it, in the form of the JeOS Tumbleweed image (and stuff I installed from the repos since). This is amazing and thanks to everyone involved in getting this set up! Now for the "fun": As I wanted to get my usual system monitoring scripts running on that system as well, I installed rrdtool. Running it, it surprised me by a "undefined symbol glDiscardFramebufferEXT" in libEGL.so.1 - and of course did not work. In the end, as this is a headless system where I probably don't need working graphics, I decided to be daring and try installing Mesa-libEGL1 instead of raspberrypi-gfx and that did get rrdtool working. For one thing, I wanted to mention this in case anyone else stumbles over the issue. For the other, is this a known issue with raspberrypi-gfx? Cheers, KaiRo -- 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] Problem updating Tumbleweed on Raspberry Pi 1B
by Freek de Kruijf 13 May '15

13 May '15

I tried to update a Tumbleweed system on a Raspberry Pi 1B system using "zypper up". During downloading the kernel-default rpm the system crashes and restarts. I was able to update zypper and curl to the latest versions. However retrieving kernel-default-4.0.1-1.1.armv6hl.rpm makes the system crash. I was able to download the rpm using curl. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 1

[opensuse-arm] Factory rebuild for icu / boost / ruby 2.2
by Dirk Müller 10 May '15

10 May '15

Hi, a couple of updates went into Factory in the last few days that broke ARM, mainly due to bootstrap loops that needed to be resolved manually. I've done that now, and things are rebuilding. Hopefully tomorrow morning there should be a working tree again (unless something else enters factory inbetween). 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] openSUSE 13.2 on cubieboard works
by Volker Kuhlmann 08 May '15

08 May '15

I have managed to get oS 13.2 to boot on a cubieboard by doctoring the installation image and transplanting the factory boot loader and kernel into it. Steps are a bit complicated so I made a script[1]. Inputs are the 13.2 and factory installation images, and script constants need version adjustment. When installing the modified image the system boots, reboots (not something to take for granted...), and at least passes the sanity checks. So far, so good. Is the 13.2 kernel working on the cubieboard? I couldn't get that one to go, it hangs at "starting kernel", even with a newer boot loader. The 13.2 boot loader is broken and needs a newer version, but that shouldn't affect the kernel directly. Never mind. I've updated https://en.opensuse.org/HCL:CubieBoard accordingly. Volker [1] http://volker.top.geek.nz/soft/script/cubieboard-oS13.2-transplant-boot -- Volker Kuhlmann http://volker.top.geek.nz/ Please do not CC list postings to me. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 18