January 2018 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] Fail with openSUSE JeOS pine 64 image
by Paul Gonin 08 Jan '18

08 Jan '18

Hi, I tried today the pine64 JeOS ipage on pine64 board with 2GB RAM Connected on ethernet (with dhcp server) Collected boot output with serial access on EXP port http://paste.opensuse.org/54338867 It seems to be failing with error (and keeps rebooting to same error status) echo -e '[1512344931.067261] Failed to find boot device !' Not sure what I can do from there... options seem limited. Thanks Paul -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 9

[opensuse-arm] RaspberryPi 3 and wifi
by Hartmut Krummrei 03 Jan '18

03 Jan '18

Hello, I managed to get Opensuse 42.3 running on my Raspi 3. That took my just one day. After another day with the effortless tries to get the built-in-wifi runnung I am at end. Was anyone able to get the wifi-device working? What did I try: evrywhere is written, that you have to edit the raspberry-file in /etc/dracut.d/, but I have no such file. So what do I edit? I tried to manage the listed modules by hand, but if I remove sdhc_ipc the system freezes. Every package named "raspberry pi" is installed (for pi 3) and bcmxxx too. Other seems to have difficulties too: https://lists.opensuse.org/opensuse-arm/2017-08/msg00028.html Regards, Hartmut -- ------------------------------------------------------------------------ "Ich habe keine besondere Begabung, sondern bin nur leidenschaftlich neugierig." (Einstein) spielmops.org <http://spielmops.org> -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 12

[opensuse-arm] How to use gpio pins via sysfs
by Frank Kunz 02 Jan '18

02 Jan '18

I try to control a few gpio pins via bash script. Board and OS version is: cat /proc/device-tree/compatible olimex,a13-olinuxinoallwinner,sun5i-a13 cat /etc/os-release NAME="openSUSE Leap" VERSION="42.3" ID=opensuse ID_LIKE="suse" VERSION_ID="42.3" PRETTY_NAME="openSUSE Leap 42.3" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:42.3" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" In /sys/class/gpio I do: echo 3 > export ls export gpio3 gpiochip0 unexport ls gpio3/ active_low device/ direction power/ subsystem/ uevent value cat gpio3/direction in So when I want to change the pin direction: echo out > gpio3/direction bash: echo: write error: Unknown error 517 That is EPROBE_DEFER. The kernel signals that the requested device might be probed later, ...or never. I guess that there might be some device tree item missing, but from the kernel documentation I haven't found a solution for that. Does anybody have an idea how to get that working? 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 2

[opensuse-arm] RPi 3 video requires CMA memory which is not automatically configures
by Michal Suchánek 01 Jan '18

01 Jan '18

Hello, for testing I installed stable and master kernel on Leap 42.3 E20 image. Initially it would work fine but later I would have to add cma=256MB (some random value found on a forum) to kernel commandline for video output to work. Has the cma requirement changed as a result of recent vc4 changes? Can the kernel allocate the required size automatically? The vc4 has probably some configuration in devicetree. As I understand it the devicetree is taken from some place other than the kernel. Is this devicetree ever updated after copying the image to the SD card? Thanks Michal -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 6