December 2017 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] http://download.opensuse.org/ports/aarch64/debug/tumbleweed is missing
by Andreas Schwab 11 Mar '18

11 Mar '18

... and the last published snapshot is Build20170831. This may be related. Andreas. -- Andreas Schwab, SUSE Labs, schwab(a)suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- 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] rock64
by Matwey V. Kornilov 10 Mar '18

10 Mar '18

Hello, I will receive my rock64 board soon. https://www.pine64.org/?page_id=7147 I would like to run some openSUSE on it. There are no upstream support but lets see what we could do. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

8 58

[opensuse-arm] openSUSE-Tumbleweed ARM JeOS-efi.armv7
by Matwey V. Kornilov 17 Feb '18

17 Feb '18

Hi, I am trying to run openSUSE-Tumbleweed-ARM-JeOS-efi.armv7l-2017.10.29-Build1.7.raw using qemu. When I use qemu-system-aarch64 with 64-bit UEFI code aavmf-aarch64-code.bin then the only I see is the EFI console: UEFI Interactive Shell v2.287477C2-69C7-11D2-8E39-00A0C969723B B8F1C820 EDK IIlProtocolInterface: 752F3136-4E16-4FDC-A22A-E5F46812F4CA B8F1FF18 UEFI v2.60 (EDK II, 0x00010000)008-7F9B-4F30-87AC-60C9FEF5DA4E B8348710 Mapping table FS0: Alias(s):HD1a0b:;BLK2: VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A00000000)/Scsi(0x0,0x0)/HD(1,GPT,E30D92E4-F475-4D50-9D3D-DF05DA812008,0x800,0x64004) BLK5: Alias(s): VenHw(F9B94AE2-8BA6-409B-9D56-B9B417F53CB3) BLK0: Alias(s): VenHw(8047DB4B-7E9C-4C0C-8EBC-DFBBAACACE8F) BLK1: Alias(s): VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A00000000)/Scsi(0x0,0x0) BLK3: Alias(s): VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A00000000)/Scsi(0x0,0x0)/HD(2,GPT,3DF8DD35-94BC-4FF0-B74C-12853D4B1811,0x65000,0x83004) BLK4: Alias(s): VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A00000000)/Scsi(0x0,0x0)/HD(3,GPT,38C4AA8C-4A7F-49C4-BCFD-6C2C755496BD,0xE8800,0x3DE781) Press ESC in 1 seconds to skip startup.nsh or any other key to continue. FSOpen: Open '\startup.nsh' Success FSOpen: Open '\startup.nsh' Success FSOpen: Open '\startup.nsh' Success Shell> bootarm FSOpen: Open '\efi\boot\bootarm.EFI' Success FSOpen: Open '\efi\boot\bootarm.EFI' Success FSOpen: Open '\efi\boot\bootarm.EFI' Success FSOpen: Open '\efi\boot\bootarm.EFI' Success [Security] 3rd party image[0] can be loaded after EndOfDxe: VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A00000000)/Scsi(0x0,0x0)/HD(1,GPT,E30D92E4-F475-4D50-9D3D-DF05DA812008,0x800,0x64004)/\efi\boot\bootarm.EFI. InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B B8EDE440 Unloading driver at 0x00000000000 Shell> Error Status: Unsupported (line number 1) As far as I understand, 64-bit Qemu UEFI code doesn't expect to see and run 32-bit EFI executable. When I try to use qemu-uefi-aarch32.bin as firmware, then I see the following: Initialization of device cfi.pflash01 failed: failed to read the initial flash content As far as I understand, qemu-uefi-aarch32.bin is in wrong format, but there are no other files in ovfm rpm package. What is the proper way to run JeOS-efi.armv7? Is it supposed to work in qemu? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 23

[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

[opensuse-arm] Packet fake-hwclock generated
by Freek de Kruijf 18 Dec '17

18 Dec '17

In Raspbian I noticed a packet always included in the image called fake- hwclock. I used the tar.gz file together with a .spec file to generate this packet for openSUSE distributions for systems without a Real Time Clock. The description is: Some machines don't have a working realtime clock (RTC) unit, or no driver for the hardware that does exist. fake-hwclock is a simple set of scripts to save the kernel's current clock periodically (including at shutdown) and restore it at boot so that the system clock keeps at least close to realtime. This will stop some of the problems that may be caused by a system believing it has travelled in time back to 1970, such as needing to perform file system checks at every boot. On top of this, use of NTP is still recommended to deal with the fake clock "drifting" while the hardware is halted or rebooting. Hope this is accepted to be included. -- 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

6 18

[opensuse-arm] No DMA on Raspberry Pi 3B using latest image
by Freek de Kruijf 15 Dec '17

15 Dec '17

I used repository: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/ RaspberryPi3/images and downloaded the image: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.aarch64-2017.12.04-Build4.5.raw.xz to start some testing. Earlier I used Build4.4 and upgraded from kernel- default-4.4.103 to 4.14.1, which resulted in regular messages about buffer full using DMA. So in the current test I left the kernel to 4.4.103. However journalctl -b shows the following error message: okt 26 14:29:18 rpi3tumhon kernel: mmc0: unable to initialise DMA channels. Falling back to PIO okt 26 14:29:18 rpi3tumhon kernel: mmc0: loaded - DMA disabled Should I enter a 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

6 11

[opensuse-arm] Problem with RPi2 image
by Freek de Kruijf 13 Dec '17

13 Dec '17

Using from repository: http://download.opensuse.org/ports/armv7hl/tumbleweed/images and image: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-2017.12.04-Build2.4.raw.xz sha256 check is OK, I can boot this image OK, however a reboot fails after having changed, via ssh, just minor things. Inspection of the microSD card using parted shows: Model: Generic STORAGE DEVICE (scsi) Disk /dev/sdg: 8069MB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 211MB 210MB fat16 vcboot 2 212MB 430MB 218MB ext4 lxboot legacy_boot 3 431MB 7551MB 7120MB lxroot 4 7552MB 8069MB 517MB linux-swap(v1) lxswap It looks like partition 3 above should not be there and should be part of 2. -- 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