August 2015 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] Strange problem with Wi-Fi connection
by Freek de Kruijf 12 Aug '15

12 Aug '15

I have a RPi 1B with a Wi-Fi USB interface using the latest image for this system. The network is configured with a fixed IP address and obviously default gateway and DNS are configured as well. IPv6 is disabled. When I start the system, or later when things went wrong restart the network, I get a proper connection and can run "zypper up" with no problem. I access that system from my desktop via ssh. When I use the command "ip -d ne" I get the following: 192.168.178.1 dev wlan0 lladdr 9c:c7:a6:0a:1f:48 REACHABLE 192.168.178.6 dev wlan0 lladdr e0:cb:4e:cd:d7:b6 REACHABLE The first line shows the default gateway/router/Wi-Fi AP However after some time I get the following: 192.168.178.1 dev wlan0 lladdr 9c:c7:a6:0a:1f:48 STALE 192.168.178.6 dev wlan0 lladdr e0:cb:4e:cd:d7:b6 REACHABLE So I still have a connection from my desktop via the Wi-Fi AP to the RPi. When I try a ping to the default gateway I do not get a response. I used tcpdump on the RPi to catch the traffic. When doing the ping I see ARP requests for the MAC address of the IP address of the default gateway. However there is no response from the router. Puzzled!! -- 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 5

[opensuse-arm] ARM 13.2 update broken
by Guillaume Gardet 12 Aug '15

12 Aug '15

Hi, http://download.opensuse.org/ports/update/13.2/ repo is outdated. Last update is from 25th of june. Any idea what is the problem? OBS problem? 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] Support for device-tree overlays
by Stefan Bruens 08 Aug '15

08 Aug '15

Hi everyone, as the RaspberryPI kernel is nowadays "configured" by the device tree, there are some issues for the current openSUSE images. By default the dtbs as shipped disable any optional hardware, which is a good thing. On the other hand things like SPI are no longer working. Raspbian tackles this with so called overlays and some help from the binary start.elf bootloader: 1. start.elf reads the dtb from the fat boot partition a) a file defined in config.txt, "device_tree=foo.dtb" b) a hardcoded hardware specific default file, "bcm2708-rpi-<variant>.dtb" 2. if the config.txt specifies "dtoverlay=foo-overlay" 1. the boot loader reads "overlays/foo-overlay.dtb" from the fat partition 2. the overlay is patched into the flattened device tree 3. the boot loader puts the device tree at address 0x100 (override with "device_tree_address=0xabcd1234" 4. the boot loader loads the specified kernel As openSUSE does not directly jump into the kernel, but starts u-boot, this does not work here. Issues: 1. u-boot does not have overlay support 2. u-boot loads its own dtb from storage, e.g. bcm2835-rpi-b.dtb 3. The u-boot boot.scr is loaded at address 0, and overwrites the boot loader provided dtb. The 3rd issue can be worked around with a "device_tree_address=0x1000" in config.txt. I tried to replace the "loadfdt" function in the boot.scr with a "fdt move 0x1000 0x2000000". Although the move succeeds, the kernel start crashes afterwards: ---- 4443840 bytes read in 1041 ms (4.1 MiB/s) 6946368 bytes read in 1403 ms (4.7 MiB/s) Copying FDT ... Kernel image @ 0x1000000 [ 0x000000 - 0x43cec0 ] data abort pc : [<17f63d68>] lr : [<17f644e0>] reloc pc : [<0001dd68>] lr : [<0001e4e0>] sp : 17b48a50 ip : 17b521e9 fp : 17f51c54 r10: 17f91354 r9 : 17b49ee8 r8 : 17f922bc r7 : 17f922b8 r6 : 17b521e0 r5 : 00000003 r4 : 33554432 r3 : 00000000 r2 : 00000010 r1 : 00000000 r0 : 33554432 Flags: nZCv IRQs off FIQs off Mode SVC_32 Resetting CPU ... ---- instead of: ---- 4443840 bytes read in 1268 ms (3.3 MiB/s) 6946368 bytes read in 1753 ms (3.8 MiB/s) 8127 bytes read in 56 ms (141.6 KiB/s) Kernel image @ 0x1000000 [ 0x000000 - 0x43cec0 ] ## Flattened Device Tree blob at 02000000 Booting using the fdt blob at 0x2000000 Using Device Tree in place at 02000000, end 02004fbe ---- So either this approach needs more work, or a completely different approach is needed to get overlays to work. Any ideas? Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 -- 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] armv6 kernel update 4.1.3
by Michael Ströder 06 Aug '15

06 Aug '15

1 3

[opensuse-arm] Some tests with RPi 1 images
by Freek de Kruijf 06 Aug '15

06 Aug '15

I tested Build319.9 in /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi/ This image shows an error message about not finding the boot device and reboots again after 120 sec., etc. So there is something wrong in the partition boot. None of the images in this repository works. I tested Build330.7 in upstream /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/ which still contains the bug in yast in bug report https://bugzilla.opensuse.org/show_bug.cgi?id=936788 When booting I see an error message about an error in a udev rule, but the system still boots. This system appears usable. I tested Build330.8 in upstream /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/ which boots, but shows an error about /home and finally reboots again after a wait time of 120 sec., so does not work. -- 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 1

[opensuse-arm] Tests with RPi2 images
by Freek de Kruijf 06 Aug '15

06 Aug '15

I tested Build320.12 from the repository: /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi2/ which works OK. I tested Build321.14 from the repository: /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi2:/Staging/ which works OK. Both these images do NOT show any message on the screen after the initial boot. As soon as the openSUSE boot image is used the screen blanks and only the final prompt is shown. It would be more instructive to see how the partitions are expanded and configured. When starting the image for the first time the date/time is set, apparently at about the date/time the image is build (Aug 05 02:00 CEST). Booting the image the next time this date/time is Jan 1 1970 02:00 CEST. I wonder if it is possible to preserve the shutdown time so that the next boot gets that time. In that case date/time in logs are ascending. -- 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 0

[opensuse-arm] armv7hl kernel-default config have tegra20 serial output broken
by Misha Komarovskiy 05 Aug '15

05 Aug '15

Hello, I found that latest images for my armv7 board (paz00/ac100) which use kernel-default have kernel panic on start without any output to serial console, but serial output was working last time i tested image back in may. I cloned kernel-source git repo made sequence-patched kernel and recompiled it with enabling DEBUG_LL,TEGRA UART_A and EARLYPRINTK config options added to config/armv7hl/default config, but found that there is no ttyS0 output, only earlycon here is paste: http://paste.opensuse.org/31390203 Recompiling same kernel with multi_v7_defconfig config and same debug/earlyprintk options have no panics and normal serial output: http://paste.opensuse.org/13080662 Maybe kernel-default config require some extra tricks now to have serial output? I want to catch that panic. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 4

[opensuse-arm] u-boot update - Jetson TK1 patches
by Guillaume Gardet 05 Aug '15

05 Aug '15

Hi Andreas, you submitted u-boot patches for Jetson TK1 against 2015.07 version. I want to update to 2015.10-rc1 but your patches does not apply anymore. Probably because of tegra 210 addition. Could you provide an updated version of your patches against my home project, please? https://build.opensuse.org/package/show/home:Guillaume_G:branches:Base:Syst… Guillaume -- 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] Cubietruck 13.2 regression
by Andreas Färber 05 Aug '15

05 Aug '15

Hello, After upgrading 13.2 from kernel-lpae-3.16.7-7 to -11/-21 (why is it installing two new kernels btw?) I no longer have network. Diagnosing this is difficult because, as reported previously, the kernel does not provide any serial output to ttyS0. The LED lights up, which is done by my boot.local script, so it is coming up to some degree, just not far enough to login via ssh, and it's not reachable by ping either. I doubt this is just the dtb getting out of sync again? Originally it was a U-Boot 2014.10, but same with 2015.07 (and still working with a downgraded kernel/initrd). Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 3