June 2015 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] Attempt to run KIWI on unsupported architecture 'armv8l'
by Dirk Müller 12 Apr '17

12 Apr '17

Hi, this is a known OBS bug, asked the admins to deploy a fix shortly. Greetings, Dirk -- 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] 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