February 2015 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] openSUSE ARM img compatible with Raspberry Pi 2
by Jimmy PIERRE 06 Mar '15

06 Mar '15

Hi all, I have been having a fight with loads of .xz raw files. Seems that there is an issue somewhere. Would appreciate that you point me to a working img file similar to the one from Bernhard Wiedemans of 2013. My BootCamp starts in less than two hours and I am desparate to show openSUSE on Raspberry Pi 2. Best wishes, Jimmy nui.fr -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

6 8

[opensuse-arm] Wi-Fi connections on Raspberry Pi 1 B
by Freek de Kruijf 27 Feb '15

27 Feb '15

Hi all, I have a strange problem with Wi-Fi connections to two somewhat different Access Points. Both use the same configuration in "YaST network", apart from SSID and IP address. Still the connection does succeed with one AP, but to the other AP it always fails. Using "iwlist wlan0 scan" the only obvious difference is that one reports to use CCMP, the one which succeeds, and the other uses TKIP, which does not succeed. In the information I found on the Internet I see that the configuration for wpa_supplicant may contain information about the support/use of these protocols. However the file /etc/wpa_supplicant/wpa_supplicant.conf does not contain this information, but the process wpa_supplicant has been started with the -u option, which enables a DBus control interface. So I assume that this kind of information will be supplied by wicked. However I can't find if TKIP is supported in openSUSE 13.2 for the the Raspberry Pi. Any information? -- fr.gr. 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

6 8

[opensuse-arm] openSuSE on Raspberry Pi 2 (armv7) when ? or how ?
by Tchelovek 27 Feb '15

27 Feb '15

Hello List, I am using a Raspberry Pi B+ with openSuSE already, now I have acquired a Raspberry Pi 2. Alas openSuSE doesnt seem to be prepared to provide an update to that end. Is anything in the works ? Or can one produce his own version using OBS ? I managed to run B. Wiedemann' s project altimagebuild locally ( with help from Bernhard ) and produce a running armv6 image, alas I lack the knowledge to modify it to match armv7. Any hint is appreciated. I actually run Arch Linux on it, but would really prefer to stick with openSuSE. Tchelovek -- 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] Please accept SR#287941 for JeOS
by Guillaume Gardet 26 Feb '15

26 Feb '15

Hi, could you please accept SR #287941 to get JeOS fixes and enhancements. 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] openSUSE Factory ARM DTBs are outdated
by Guillaume Gardet 25 Feb '15

25 Feb '15

Hi, the DTBs in Factory:ARM are all outdated. Could you trigger a rebuild, please? Currently, Beaglebone black does not boot due to a too old DTB (SD card not found). Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 10

[opensuse-arm] openQA: ARM
by Matwey V. Kornilov 24 Feb '15

24 Feb '15

Hi, What do you think about adding couple of test cases for ARM to our openQA? I remember two cases when our JeOSes were broken independently of hardware. First one, when u-boot was looking for boot.scr in wrong place, second one, when the kernel 3.14 was broken due to bug in depmod. So, I think that we could test JeOS-vexpress and JeOS-vexpress64 for armv7 and aarch64 using qemu emulation (I know that it is slow ;) ) Then just check that the image is booted for the first time, and for the second time, controlling the process through serial console. At the moment I have no idea how many efforts are needed to implement this. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

10 30

[opensuse-arm] kiwi v7.02 failed
by Matwey V. Kornilov 23 Feb '15

23 Feb '15

Hi, kiwi 7.02 is failed to Factory:ARM: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:ARM/kiwi… -- 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] Error message after installation of kernel-firmware
by Freek de Kruijf 22 Feb '15

22 Feb '15

Hi all, I got the following error message after the update of firmware-kernel in openSUSE 13.2 for Raspberry Pi. Warning: kernel-firmware-20141122git-5.1.noarch.rpm %posttrans script failed (returned 1) Bug report? -- fr.gr. 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 3

[opensuse-arm] WiFi does not come up on Raspberry Pi B
by Freek de Kruijf 21 Feb '15

21 Feb '15

I have a Raspberry PI B with openSUSE 13.2 (JeOS) which has two USB interfaces, a Bluetooth and WiFi (Realtek RTL8192cu). It worked OK during installation at home, but at its destination the WiFi connection does not come up. I can do "iwlist wlan0 scan" and I get the list of Access Points it the neighborhood. The device is configured with wicket. For access I use the Ethernet port (it works headless). I have the same system on another device, same software, same type of devices, same network configuration and that one works as expected. I can bring the interface down with "ifdown wlan0" and up again with "ifup wlan0 -o debug" and the last lines of the output are: wicked: waiting for 1 devices to become ready (1 explicitly requested) wicked: wlan0: state=firewall-up want=network-up, wait-for=link-up wicked: waiting for 1 devices to become ready (1 explicitly requested) wicked: wlan0: state=firewall-up want=network-up, wait-for=link-up wicked: waiting for 1 devices to become ready (1 explicitly requested) wicked: device wlan0 failed: operation timed out wicked: waiting for 0 devices to become ready (0 explicitly requested) wicked: finished with all devices. wicked: wlan0: changed state none -> device-exists, still waiting for event wlan0 setup-in-progress wicked: Exit with status: 162 On the device that does work, instead of the timeout I get: wicked: ... great, we were expecting this event wicked: wlan0: changed state firewall-up -> link-up, resuming activity wicked: wlan0: state=link-up want=network-up, trying to transition to link- authenticated wicked: wlan0: changed state link-up -> link-authenticated wicked: wlan0: successfully transitioned from link-up to link-authenticated wicked: wlan0: state=link-authenticated want=network-up, trying to transition to lldp-up wicked: wlan0: calling org.opensuse.Network.LLDP.lldpUp() wicked: wlan0: changed state link-authenticated -> lldp-up wicked: wlan0: successfully transitioned from link-authenticated to lldp-up wicked: wlan0: state=lldp-up want=network-up, trying to transition to network- up wicked: wlan0: calling org.opensuse.Network.Addrconf.ipv4.static.requestLease() wicked: wlan0: changed state lldp-up -> network-up wicked: wlan0: cancel timeout wicked: wlan0: successfully transitioned from lldp-up to network-up wicked: waiting for 0 devices to become ready (0 explicitly requested) wicked: finished with all devices. wicked: wlan0: tentative addresses check wlan0 up wicked: Exit with status: 0 I found on the Internet problems with the power drawn via the USB ports. But it that case the WiFi connection got established, but was unstable. The same device with the same interfaces and the same power supply worked for almost 9 month without any problem with openSUSE 13.1. Because the SD card broke down I had to reconfigure the software. I have a similar device doing the same thing, with the same type of devices and also with openSUSE 13.2 working OK. Any suggestions? -- fr.gr. 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] Please accept SR #286292 for JeOS
by Guillaume Gardet 20 Feb '15

20 Feb '15

Hi, could you please accept my SR #286292 to update JeOS. 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] Kernel testing at Linaro
by Andrew Wafaa 19 Feb '15

19 Feb '15

Hi, Could someone confirm that it is OK to forward our aarch64 config to Linaro for them to integrate into the kernelci loop? Currently kernelci.org only tests defconfigs which are rather minimal. Also can someone confirm what the stance is on page sizes? Will openSUSE support both 4K and 64K page sizes or just focus on one? Thanks, Andy -- 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] openSUSE 13.2 on the Acer Chromebook 13 CB5-311-T6R7 (nyan-big)
by Simon Gleissner 19 Feb '15

19 Feb '15

Hello, currently I try to install openSUSE 13.2 for armv7hl on my Acer Chromebook 13 CB5-311-T6R7 (nyan-big, 4 GB, FullHD-display). It is working, but there are some problems. For those who are interested, I have used the approach described here: https://github.com/lgeek/gnu-linux-on-acer-chromebook-13 The kernel is quite old and WLAN is not working, but the rest seems to be stable enough. I use XFCE and can compile, sign and install the kernel natively on the Chromebook. However, I am not happy with the missing WLAN, so I have tried to exchange the Chromeos-based kernel 3.10.18 against a vanilla 3.18.5 kernel, which has support for the tegra124/nyan-big plattform. This kernel does not work at all (just a black screen), so my question is: Does anyone have an approach for compile a working kernel with WLAN, e.g. a working .config file? Greetings, Simon -- 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] How to .tbz files in ARM factory?
by Freek de Kruijf 19 Feb '15

19 Feb '15

Hi All, In ARM factory http://download.opensuse.org/ports/armv6hl/factory/images/ I see a E17 version with extension raw.xz and I assume this one can be used as described in https://en.opensuse.org/HCL:Raspberry_Pi. However I am interested in the JeOS version which is only available as .tbz. How do use this .tbz version? -- fr.gr. 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 1

[opensuse-arm] OpenSusee-version 13.2 JeOS: Boot-Fragen
by Edgar Dombrowski 18 Feb '15

18 Feb '15

Hi, Rasperry-friends. I am actually playing around with the Build-Version 32,1. When booting I am getting the following error messages: 1. Just at the start: > reading ./uEnv.txt > unable to read file ./uEnv.txt missing ** 2. At the end of the boot process: > unable to start X-Display Manager How shall I proceed to solve these problems. Thanks to all of you 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

3 2

[opensuse-arm] Wrong type of connection between Rasberry Pi and Zyxel P-2812HNU-F1?
by Freek de Kruijf 17 Feb '15

17 Feb '15

Hi all, I am having problems with the wired connection, UTP, between the Rasberry Pi and the Zyxel router P-2812HNU-F1. Quite often after connecting the Raspberry Pi with openSUSE 13.2, the 5 indicator lights on the RPi should come up. However only PWR is on and there is no connection between the RPi and the Zyxel. After a power down/up of the Zyxel the normal connection comes up. I assume that the handshaking of the Ethernet connection goes wrong. The Zyxel should assume the master role and the RPi the slave role and apparently this goes wrong. Is there another way to establish a proper connection? Is there a command to make the Ethernet interface in the RPi the slave and to start a new negotiation? -- 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] Why is packet e2fsprogs not present in Rasberry Pi image?
by Freek de Kruijf 17 Feb '15

17 Feb '15

Hi all, Reading through the dmesg output on my Raspberry Pi I found an error message about missing programs fsck.ext3 and fsck.ext4, which I found in package e2fsprogs. This package is missing in the Raspberry Pi image. Shouldn't it be included? Bug report? -- 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] UIM package
by Andrew Wafaa 17 Feb '15

17 Feb '15

Does anyone know if we havea package for UIM - User Mode Init Manager for TI shared transport? I've looked on OBS and can't see one, but I may be missing something. This is needed for the Hikey from 96Boards. Linaro have a couple of patches and have also added a systemd service file and udev rule for uim. Thanks, Andy -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 6

[opensuse-arm] Boot camp Raspberry Pi 2 - 21FEB
by Jimmy PIERRE 17 Feb '15

17 Feb '15

Hi Guys! I have this problem, I am having a boot camp on Raspberry Pi 2 next Saturday, *but* the process of installing openSUSE ARM might jeopardize all efforts. I see that Debian, Feudora, openelec, Ubuntu, xbmc Risc OS have a simple installation... Give me some thoughts please... Best, Jimmy Pierre Twitter handle : @jpierre76 #openSUSE #suse #Raspberry PI #libreoffice #jmll.fr #nui.fr #Rouen http://www.agendadulibre.org/events/9116 #nui.fr #interopérabilité -- 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 version 2
by Bill Merriam 14 Feb '15

14 Feb '15

I imagine everyone is aware that a quad-core, ARMv7 version of the RPi is available. Does anybody know what is involved in using Opensuse on that device? I am hoping that I can use the normal ARMv7 repository for everything but the RPi specific packages. Should I branch those RPi packages and try building them for V7 or is someone already doing that? Thanks. Bill -- 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] Latest Raspi JeOS image
by Richard (MQ) 13 Feb '15

13 Feb '15

Hi, I'm trying to use openSUSE-13.2-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build36.2.raw.xz from http://download.opensuse.org/repositories/devel:/ARM:/13.2:/Contrib:/Raspbe…, write to SD card with xzcat as described in HCL:Raspberry_Pi Is this a working image file? For me, the boot process hangs at "Loading kernel" (no progress after several minutes) Same hardware (including same SD card) boots raspian 2014-12-24 version perfectly. FWIW it's an early model B (type 0002) My image file (.raw.xz) has md5sum f61450a3eb30ff5419463d153271fe0c, but I can't find an expected sum to compare with. Also, xzcat reports no issues when copying to SD card. If this image file is no good, can someone point me to the last good one? Many thanks Richard (MQ) -- 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] Raspberry Pi B+, No Revision or Serial?
by Evan McClain 11 Feb '15

11 Feb '15

Hi List, While setting up my new rpi B+, I noticed that my eth0's MAC address would change after each boot which was causing a new ip address to be issued by my router after every boot. I found this post roughly describing my issue: http://www.raspberrypi.org/forums/viewtopic.php?p=90975 My /proc/cpuinfo shows my Revision as 0000 (instead of 0010) and my Serial is also just 0s. Adding: program_serial_random=1 and program_board_rev=2 to Config.txt didn't fix the issue. Other raspberry pi distributions do show my Serial and Revision as expected, and eth0's MAC address isn't random. It appears that the command line doesn't get updated with the proper bcm2708.boardrev and bcm2708.serial (and possibly smsc95xx.macaddr) options. I have built an upstream kernel (3.18.0 branch) and that doesn't seem to help (I thought the default kernel may not be parsing the options). And I even tried updating the boot firmware to the raspberrypi's next branch with no impact. I'm not too familiar with opensuse's rpi boot process, but it looks fairly different from what I've seen on arch and raspbian (i.e. the vfat partition is used to start the boot.scr on the ext4's /boot directory). As this is my first rpi, I'm still trying to figure things out... Is it possible that the kernel parameters are not being passed properly when the kernel on the /boot/zImage is loaded? Also, do the previous pi revisions work or is this new to the B+? Or could this be an issue with the Factory port? Thanks -- Evan McClain /* No Comment */ https://keybase.io/aeroevan

2 1

[opensuse-arm] Graphic Terminal
by Edgar Dombrowski 10 Feb '15

10 Feb '15

Hi, Raspberry Friends and Supporters. I finally got the Build-Version36.2 installed with the help of the HCL-homepage. However I find some problems, which I will notify to you for any assistance, Problems will be detailed in separate mailings. Question 1: I would like to use the graphic mode by starting "startx" using an HDMI-Monitor. However the answer is: startx not found. How can I solve the problem. Thanks for your help. Regards 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

2 1

[opensuse-arm] kwrite and kate packages missing for openSUSE 13.2 armv7hl
by Simon Gleissner 03 Feb '15

03 Feb '15

Hello, I have tried to install KDE and KDevelop for openSUSE 13.2 armv7hl, but the depending packages kate and kwrite are not included in the repository. I have used http://download.opensuse.org/ports/armv7hl/distribution/13.2/repo/oss/suse/… . According to https://build.opensuse.org/project/show/openSUSE:13.2 , the armv7l build for kate is 'unresolvable', but kwrite is neither listed at 'succeded', nor anywhere else. Any chance that this might change? Greetings, Simon -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1