March 2019 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] cubox-i / leap 42.3: problems with automatic module loading after upgrade
by Miklos Vajna 13 Apr '19

13 Apr '19

Hi, Just asking if this is only me or it's a wider problem: I recently updated my cubox-i with zypper, pulling in kernel-default-4.4.114, and after reboot the box boots, but several drivers are missing, so there is no wired ethernet, no mmcblk, etc. After booting and waiting for a while, dmesg starts to complain about driver detection did not finish in time (sadly I don't have the backtrace at hand, it already went out of the buffer of the serial console). For now I worked around the problem this way: - download the repo-oss (ie. non-update) kernel-default-4.4.76 rpm on an other machine, copied it to an usb stick - install the old kernel-default from the usb stick - copy the /boot from the root fs to the usb stick - use the other machine to update the /boot on the mmcblk device where u-boot reads it So is this only me or do other cubox-i users see the same? Thanks, Miklos

2 3

[opensuse-arm] Emulate image for Raspberry Pi2 in QEMU
by Till Dörges 29 Mar '19

29 Mar '19

Hello all, I'm trying to get an openSUSE image for Raspberry Pi2 going in QEMU. But everything I've tried so far didn't work. --> I'd greatly appreciate any hints or pointers where to perform an RTFM. I started at https://en.opensuse.org/HCL:Raspberry_Pi2 with this image openSUSE-Leap15.0-ARM-JeOS-raspberrypi2.armv7l-2018.07.02-Buildlp150.1.1.raw >From looking around it appears one needs kernel, initrd and DTB separately. So I peeled them off the image and tried booting like this: --- snip --- INITRD=initrd-4.12.14-lp150.11-lpae KERNEL=zImage-4.12.14-lp150.11-lpae DTB=bcm2709-rpi-2-b.dtb HDDIMG=openSUSE-Leap15.0-ARM-JeOS-raspberrypi2.armv7l-2018.07.02-Buildlp150.1.1.raw qemu-system-arm \ -M raspi2 \ -kernel ${KERNEL} \ -initrd ${INITRD} \ -dtb ${DTB} \ -append "rw earlyprintk loglevel=8 console=ttyAMA0,115200 dwc_otg.lpm_enable=0 root=/dev/mmcblk0p2" \ -drive if=sd,format=raw,file=${HDDIMG} --- snap --- But this only gives a blank screen in the QEMU window (also on the serial console) and 100% CPU usage. I've tried a few variations but the symptoms stay the same. So how do I start one of the openSUSE images for Raspberry Pi2 in QEMU? Thanks and regards -- Till -- Dipl.-Inform. Till Dörges doerges(a)pre-sense.de Tel. +49 - 40 - 244 2407 - 0 Fax +49 - 40 - 244 2407 - 24 PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- 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] Problem with yast bootloader Paspi3B+
by Eric Schirra 27 Mar '19

27 Mar '19

Hello, i have a problem with Bootloader in Yast under xfce. I have not change the Bootloader itself. It is grub2. I only click okay and then it rise up an error at step three "configuration save": Details: unsupported combination of architecture aarch64 and disabled EFI Caller: /usr/share/YaST2/lib/bootloader/grub_install.rb:98 in 'target' Is this error known? Must i change to grub2 with Efi? But it is only Linux. No windows. So i need not EFI. This have i done in desktop lxqt. After that the error is the same. And the raspi have after reboot a black screen. No chance to login and use it. Can someone help me? -- Regards Eric -- 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] No sendfile64() supprt on 15.1 armv7l?
by Adrian Schröter 25 Mar '19

25 Mar '19

Hi, I have an apache server running on a Pi 2 using openSUSE 15.1 armv7l atm. While it can deliver smaller files, it errors out on a bit larger files with wrong Content-Length. Yes, file permissions and the Content-Length value are correct and local delivery is working :) I see in strace sendfile64(15, 16, [0], 194577) = -1 EOPNOTSUPP (Operation not supported) Trying to use kernel 5.0 just leaded to a not booting system :/ anyway, any ideas regarding the sendfile64 issue? -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian(a)suse.de -- 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] vcio, STRICT_DEVMEM
by Per Jessen 12 Mar '19

12 Mar '19

Well, at least I have a vcio module that builds now, we'll see it if it also works. The code for using the PWM to generate control signals for a line of WS2812Bs also uses /dev/mem to access the Raspi hardware - with the openSUSE kernel, this is blocked by CONFIG_STRICT_DEVMEM. I don't see any kernel argument or switch to disable that restriction. (I tried strict_devmem=0, didn't work). I'm rebuilding a kernel without CONFIG_STRICT_DEVMEM, but I can't help wondering if we shouldn't have a dedicated kernel optimized for use on the Raspi? Using kernel-default seems silly. -- Per Jessen, Zürich (11.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- 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] libgpiod on RasPi 3B+ apparently does not work
by Simon Gleissner 11 Mar '19

11 Mar '19

I'm using Tumbleweed JeOS (20190308, aarch64) on a RaspberryPI 3B+, which works astonishingly good and stable. During my attempts to use the GPIOs with libgpiod, i've found that the GPIOs are not named as they should be. Also setting GPIOs does not seem to work, if they are changed with gpioset. Regarding the naming of the GPIOs, all of them are unnamed: # gpioinfo pinctrl-bcm2835 gpiochip0 - 54 lines: line 0: unnamed unused input active-high line 1: unnamed unused input active-high line 2: unnamed unused input active-high line 3: unnamed unused input active-high line 4: unnamed unused input active-high ... line 29: unnamed "led0" output active-high [used] line 30: unnamed unused output active-high line 31: unnamed unused output active-high ... line 47: unnamed unused output active-high ... There are references for Raspian, that the 'unnamed' entries should contain the GPIO names, e.g. at https://www.beyondlogic.org/an-introduction-to-chardev-gpio-and-libgpiod-on… . Also the "led0" and other output-GPIOs do not match in their position. It seems that there is a mismatch in the device tree and I think the Tumbleweed kernel uses a generic .dts config file, whereas Raspian uses an adapted one. I have checked the mailing list and found, that the problem is not new: https://lists.opensuse.org/opensuse-arm/2018-09/msg00000.html I also have found an article in the opensuse wiki, which describes the functionality, but does not help with the mapping: https://en.opensuse.org/openSUSE:GPIO Additionally, I have tried setting all possible GPIOs with libgpiod's gpioset (some of them crashed the system), but it was not possible to change the GPIO output (I've connected a LED). However, with the deprecated sysfs GPIO subsystem this worked instantly without any problems (with offset N=458). Question: did anyone here succeeded in using libgpiod for setting GPIOs in Tumbleweed yet? -- 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] /dev/vcio for accessing the raspi "mailbox" ?
by Per Jessen 08 Mar '19

08 Mar '19

On my raspi 3b+, I'm trying out some code for controlling WS2812 LEDs - https://github.com/jgarff/rpi_ws281x The code uses /dev/vcio for mailbox communications - I guess there is a module that provides this interface, but I can't find it. It looks like bcm2835_mailbox is the right one, and it is part of the kernel. I also see in dmesg: [ 9.267410] bcm2835-mbox 3f00b880.mailbox: mailbox enabled What am I missing? -- Per Jessen, Zürich (6.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- 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] Raspberry Pi 3 B+ ?
by Per Jessen 04 Mar '19

04 Mar '19

I have just acquired two of these, one for my son's school project, one for our mediacentre. Using the KDE appliance, it boots up fine, but as soon as I start setting up the wifi, it crashes. Then I tried usig yast to set date&time - crash. -- Per Jessen, Zürich (7.5°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 16

[opensuse-arm] openSUSE 15 on Raspberry Pi 2
by 村川了 04 Mar '19

04 Mar '19

Hi I have 2 Raspberry Pi2. I burned openSUSE15 on 32GB SDHC card. One of them (named A) works fine. But other one (named B) didn't boot up. But Raspbian works on A and B. I changed SDHC card. But B doesn't boot up. Of course, I burned all images for openSUSE15 on SDHC card. But B doesn't boot up. Does anyone know the workaround for B? Only difference is when I bought. 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

3 3