openSUSE ARM June 2019

arm@lists.opensuse.org

14 participants
13 discussions

[opensuse-arm] Inconsistent names of Tumbleweed image for Raspberry Pi 1B in repository

by Freek de Kruijf

The latest Tumbleweed image for the Rasberry Pi 1B has two names on the web page: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-Current.raw.xz and openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2019.05.17- Snapshot20190607.raw.xz The corresponding sha256 files have the same content. The fourth line in these files contains the sha256 checksum followed by the name of the image. However this name is: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2019.05.17-Build1.43.raw So one needs to rename the image file before doing the checksum to this name. This name should however also have .xz added at the end. -- 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 year, 9 months

[opensuse-arm] RPi4

by Kasimir _

Hello everybody, can I use the new RPi4 with the images of RPi3 or does anyone alredy work on RPi4 images? Regards, Kasimir

1 year, 9 months

[opensuse-arm] raspbian on opensuse Leap KVM on Raspberry Pi

by 村川了

Hi I tried to run Raspbian on openSUSE Leap KVM on Raspberry Pi. I found the URL below. https://medium.com/@valdiz777/setting-up-kvm-on-raspberry-pi-3-using-a-64bi… But I can't find how to run Raspbian image on KVM. Any information/advice is helpful for me. Best Regards. Ryo -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 year, 10 months

[opensuse-arm] About temperature sensor device

by 村川了

Hi Do we have the list of the temperature sensor devices that openSUSE Leap 15/15.1 on Raspberry Pi 3B/3B+ can handle by default? Previously I asked DTH11. But I want to know this. If yes, I want to know if I can get the data with mraa? Best Regards. Ryo -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 year, 10 months

[opensuse-arm] Temperature sensor of DHT11

by 村川了

Hi I want to control the temperature sensor of DHT11 on openSUSE15 on Raspberry Pi 3B+. Now I try to develop python3 application with mraa. I want to know if openSUSE Leap 15 on Pi can handle DHT11 sensord with default or not. And what kind of action do I need to control this sensor with openSUSE Leap 15 ? Best Regards. Ryo -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 year, 10 months

[opensuse-arm] pxe

by Thierry Reijnhout

hay opensuse arm team/mailing list i have 3 raspberry pi's 1 b and 2 b+. i am running rasbian on 2 of those true pxe nfs boot without sd card... i woud love to run the 3e one on opensuse. i now there is now out of the box solution and for now i diddent find a way to get it gowing. starting kernel and then the divice hangs is how far i got. so my quistion is how can i help and how far are we whit pxe arm opensuse... and a more importend cuastion is how and where can i join in to help/test etc.... thanks for the all the work Grts Thierry Reijnhout NL http://openhoofd.nl trijenhout(a)hotmail.com N��r��y隊Z)z{.�櫛맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.�櫛�0��Ǩ�

1 year, 10 months

[opensuse-arm] Warning: aarch64 Tumbleweed JeOS images may require a manual update

by Guillaume Gardet

Hi, People using Tumbleweed on aarch64 from an "old" JeOS image may not have Tumbleweed update repo enabled out of the box. So, you can add it with: zypper ar -f http://download.opensuse.org/ports/aarch64/update/tumbleweed/ repo-update This will prevent breakage or repair your current setup, as you need some libopenssl fix from this update repo to prevent some segfault with zypper on current Tumbleweed snapshot. Thanks, Guillaume IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 year, 10 months

[opensuse-arm] wicked Error after 'zyyper up'.

by FZZ01471＠nifty.ne.jp

Hi I used openSUSE Thumbleweed "openSUSE-Tumbleweed-ARM-JeOS-ultra96.aarch64-2019.04.25-Build6.30". It worked fine. But yesterday I ran "zipper up" and reboot this, I got the error below when booting up. [FAILED] Failed to start wicked DHCPv4 supplicant service. See 'systemctl status wickedd-dhcp4.service' for details. [FAILED] Failed to start wicked AutoIPv4 supplicant service. See 'systemctl status wickedd-auto4.service' for details. [FAILED] Failed to start wicked DHCPv6 supplicant service. See 'systemctl status wickedd-dhcp6.service' for details. Starting wicked network management service daemon... [ **] (2 of 2) A start job is running for.ervice daemon (1min 53s / 3min 7s) After this, wifi doesn't work. I checked the wifi router, this gave IP to Ultra96 board. But I run "ip a" and found no ipv4 address. : wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 20:c3:8f:8c:bf:f6 brd ff:ff:ff:ff:ff:ff inet6 2001:240:2405:cbeb:6192:8bd:c571:ac43/64 scope global temporary dynamic valid_lft 604768sec preferred_lft 86180sec inet6 2001:240:2405:cbeb:22c3:8fff:fe8c:bff6/64 scope global dynamic mngtmpaddr valid_lft forever preferred_lft forever inet6 fe80::22c3:8fff:fe8c:bff6/64 scope link valid_lft forever preferred_lft forever Is this know bug? And is there any workaround for this? Best Regards. Ryo -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 year, 10 months

[opensuse-arm] Abount build image 4.39 for Ultra96

by FZZ01471＠nifty.ne.jp

Hi List Today I downloaded the image "openSUSE-Tumbleweed-ARM-JeOS-ultra96.aarch64-2019.05.17-Build4.39.raw.xz" and burned it on the SD card. But when I boot this and set Wifi on this, I got the error below. wl18xx_driver wl18xx.1.auto: Direct firmware load for ti-connectivity/wl18xx-fw-4.bin failed with error -2 [ 354.727758] wlcore: ERROR could not get firmware ti-connectivity/wl18xx-fw-4.bin: -2 But before this version, I could set wifi on Ultra96. Does anyone know the workaround for this? Best Regard. Ryo -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 year, 10 months

[opensuse-arm] Segmentation fault of python3-RPi.GPIO-0.6.5-lp151.4.1.aarch64.rpm

by 村川了

Hi I start doing GPIO test with the package on openSUSE 15.1 and Raspberry Pi 3B+. When I run the program in the document, I got "segmentation fault". My program is below. Python 2.7.14 (default, Oct 12 2017, 15:50:02) [GCC] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import RPi.GPIO as GPIO >>> GPIO.setmode(GPIO.BCM) >>> GPIO.setup(25,GPIO.OUT) Segmentation fault (core dumped) Does anyone work well with this gpio package? I want to know the workaround for this. And I know mraa library is the replacement for gpio. But I can't find how to write the code with mraa when we can write the code below with gpio. <gpio description> GPIO.set(24,GPIO.IN) GPIO.input(24) Does anyone tell me the hit for this? Best Regards. Ryo -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 year, 10 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

openSUSE ARM June 2019