October 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] [aarch64] TW on Pinebook?
by Alex Naumov 12 Dec '17

12 Dec '17

Hello, yesterday I finally got my 14'' Pinebook [1]. There is Ubuntu 16.04 MATE as a default OS, but I would like to use openSUSE TW on it of course. So, I found raw.xz XFCE-image for aarch64 [2] and used this command "to burn" image on the microSD card: # unxz -c openSUSE-Tumbleweed-ARM-XFCE-efi.aarch64-2017.06.10-Build2.3.raw.xz | sudo dd of=/dev/mmcblk1p No success. Pinebook tried to boot from microSD card, but... it seems that there is something wrong with bootloader. Here [3] I found this command: # xzcat openSUSE-Tumbleweed-ARM-XFCE-efi.aarch64-2017.06.10-Build2.3.raw.xz | dd bs=4M of=/dev/ mmcblk1p oflag=sync Exactly the same... image is there, echo $? tells 0, but pinebook ignore it. Image on microSD card is marked as a bootable. I checked it with parted(8). I asked Google and it showed me this [4]. This is HOWTO for fedora 21 on Cubietruck, but there is one interesting thing: step (4) Write U-Boot to Media. Do we also need to install bootloader extra? Because, as I said, for me it seems like a bootloader problem. If yes, where is this script or documentation about it? Also I would ask about rootfs-images. Do we have some information/HOWTOs about these? Cheers, Alex [1] https://www.pine64.org/?page_id=3707 [2] http://download.opensuse.org/ports/aarch64/tumbleweed/images/openSUSE-Tumbl… [3] https://en.opensuse.org/HCL:AArch64_EFI [4] https://kashyapc.fedorapeople.org/arm/installing-Fedora-21-on-microSD-card-… -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 7

Re: [opensuse-arm] Re: EspressoBin
by Matwey V. Kornilov 27 Nov '17

27 Nov '17

2017-10-22 9:31 GMT+03:00 Rick Ashford <Rick.Ashford(a)suse.com>: > There is a great thread on the Armbian forum about the EspressoBin, and it > helped me get things up and running with Tumbleweed. > > One of the guys there has a public Dropbox link that includes their images > for flashing the u-boot loader: > https://www.dropbox.com/sh/kmgmo1uubhcczx5/AAAYEvTIFxpBr0dHG2QcapTza?dl=0 > > The thread: > https://forum.armbian.com/index.php?/topic/4089-espressobin-support-develop… > > With their boot loader I was able to finally use BTRFS images as well as PXE > boot. It also has an EFI load function in the help that I need to get around > to trying. Well, If armian u-boot is able to boot our standard EFI-Grub JeOS, then we can recommend to use it with openSUSE and don't reinvent the wheel. > > Rick Ashford > Sales Engineering Manager - West > SUSE Linux > rick.ashford(a)suse.com > Office: 512-782-4318 > Mobile: 512-731-3035 > > On Oct 21, 2017, at 12:32 PM, Matwey V. Kornilov <matwey.kornilov(a)gmail.com> > wrote: > > 2017-10-21 19:47 GMT+03:00 Matwey V. Kornilov <matwey.kornilov(a)gmail.com>: > > 2017-10-21 19:35 GMT+03:00 Matwey V. Kornilov <matwey.kornilov(a)gmail.com>: > > 2017-10-20 18:02 GMT+03:00 Matwey V. Kornilov <matwey.kornilov(a)gmail.com>: > > 2017-10-20 17:37 GMT+03:00 Alexander Graf <agraf(a)suse.de>: > > > > On 20.10.17 16:21, Matwey V. Kornilov wrote: > > 20.10.2017 17:12, Alexander Graf пишет: > > > > On 20.10.17 13:57, Matwey V. Kornilov wrote: > > Hi, > > > I've just received EspressoBin 1G. Any success stories how to run openSUSE? > > > > I think you'll basically have to somehow flash a working U-Boot with > > distro boot onto it and then just dd the tumbleweed/42.3 iso onto a usb > > stick and cross your fingers that gets you to a point where you can > > install :) > > > It has microsd card, I think it should be able to boot from sd, no? > > I also need to to find serial console pins on the board :) > > > There seems to be a lengthy discussion on the mailing list. I guess you > > can select the boot device using DIP switches though? > > > Yes, I can. I think it is preferred way. Need to find expected layout > > to place u-boot image. > > > Well, at least while booting from SATA, they say that BootRom looks > > for code starting with zero offset, which implies that there can not > > be any GPT partition table. > > Probably, it is similar for SD. If so, we need to flash our EFI-aware > > u-boot instead of upstream one. > > > > Well, SATA flash image from here > > > http://wiki.espressobin.net/tiki-index.php?page=Boot+ESPRESSObin+from+SATA+… > > > suits for booting from microsd card, when it is flushed from zero > > offset and boot selection switchs are set to 7. > > > At least, there is non-destructive way to check out u-boot image. > > > Double checked. Seems that microsd boot doesn't work and is not > supported. At least for my V5 board. > It just falls back to SPINOR > > > > > http://espressobin.net/forums/topic/how-to-flash-u-boot/ > > > > Alex > > > > > -- > > With best regards, > > Matwey V. Kornilov > > > > > -- > > With best regards, > > Matwey V. Kornilov > > > > > -- > > With best regards, > > Matwey V. Kornilov > > > > > -- > With best regards, > Matwey V. Kornilov > -- > To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org > > -- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 10

[opensuse-arm] Samsung Chromebook (Snow) status?
by Daniel Bischof 20 Nov '17

20 Nov '17

Hi, I tried openSUSE-Tumbleweed-ARM-XFCE-chromebook.armv7l-2017.07.22-Build1.1 recently, but it just beeps and kicks me back to the boot screen immediately. No messages on screen, partition resizing, etc. Any hints? Some cgpt magic I could try from ChromeOS perhaps? Best regards, --D. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 10

[opensuse-arm] JeOS-2017-03-13 image for RPi 1 installs OK, Grub fails on reboot
by Alex Armstrong 14 Nov '17

14 Nov '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings, I was testing: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2017.03.13-Build1.8.raw.xz from: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras… On RaspberryPi 1 Model B It installs fine - expands the file system, creates the dracut based init and boots to a usable system. But when I reboot, grub fails with: error: attempt to read or write outside of partition. and drops me to the grub rescue system. Poking around the rescue system, I've found that I can see 4 partitions, one which is ext2 and has the normal Linux files. From here, most of the recovery guides say to set the root and prefix variables and then load the normal module. I can execute the commands: set root=(hd0,gpt2) set prefix=(hd0,gpt2)/boot/grub2 and list the files in the various directories - normal.mod exists in /boot/grub2/arm-efi/ - but when I try: insmod normal I still get the error: attempt to read or write outside of partition. Somewhat interestingly, if I miss-type the prefix (say; /boot/grub) the error changes to a "file not found" one. I was hoping someone might have some ideas about what to try next. - -Alex -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAljUJnYACgkQYZYc2javKOllFQCeNiB6oZYpnKxgmKsbdUtcQNrO mOIAoJBXe8913EIzBfD04P/PqfPjFv9e =ZZC3 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 9

[opensuse-arm] aaa_base for Tumbleweed on RPi3 (aarch64) lacks a number of entries for /etc/passwd, /etc/group and /etc/shadow
by Freek de Kruijf 27 Oct '17

27 Oct '17

I tried to use postfix in Tumbleweed on a Raspberry Pi 3B system with aarch64. I got an error message that account nobody is missing. I inspected some files delivered by aaa_base to set-up /etc/passwd, /etc/group, and /etc/shadow and found only root mentioned in the template for /etc/passwd. In Leap 42.3 for the same system these templates contain a lot more entries. Bug report: https://bugzilla.opensuse.org/show_bug.cgi?id=1065411 -- 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

2 2

[opensuse-arm] Enable SPI
by Alexander Bergmann 25 Oct '17

25 Oct '17

Hi everyone, I'm not sure how to enable SPI in openSUSE Leap 43.3. I've changed the config.txt file and added "dtparam=spi=on", this has however no affect on the hardware. The same steps are working in Raspbian. #> cat /proc/device-tree/soc/spi@7e204000/status disabled Any ideas? Ciao, Alex~ -- Alexander Bergmann <abergmann(a)suse.com>, Security Engineer, GPG:9FFA4886 SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg)

3 4

[opensuse-arm] EspressoBin
by Matwey V. Kornilov 21 Oct '17

21 Oct '17

Hi, I've just received EspressoBin 1G. Any success stories how to run openSUSE? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 7

[opensuse-arm] TW AArch64 images not published?
by Guillaume Gardet 17 Oct '17

17 Oct '17

Hi, Images from http://download.opensuse.org/ports/aarch64/tumbleweed/ are quite old: 17th of June 2017. I guess images publishing has problems? ISO files seem to be OK. 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] ARM64 installation DVD link on web page
by Loic Devulder 16 Oct '17

16 Oct '17

Hi! Small question: on this web page https://software.opensuse.org/distributions/tumbleweed we can find a link to download TW Ports, like the page we can found for Leap. But on the TW Ports there is no ARM64 link as for Leap: https://software.opensuse.org/distributions/tumbleweed/ports. Is a link to the installation DVD could be added like Leap or the other architectures? -- Loic Devulder - Senior QA Engineer email: ldevulder(a)suse.de Container & Storage Solutions Quality Assurance team (qa-css) SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. 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

4 5

[opensuse-arm] EFI boot device-tree
by Frank Kunz 15 Oct '17

15 Oct '17

Hi, I'm doing some test with EFI boot on an olinuxino board here: https:// build.opensuse.org/package/show/home:frank_kunz:branches:openSUSE:Factory:A… JeOS-olinuxinolime The image works and the kernel has a device-tree visible under /proc/device- tree. With non EFI configurations the device-tree is loaded by uboot from the boot partition dtb directory and is then passed to the kernel by boot command. For EFI there is no dtb directory. Also I haven't found a *.dtb file on the filesystem anywhere. How does the kernel get the device-tree in EFI boot mode? The background is that some hardware specific configurations need to be done per use case in the device-tree. E.g. adding a battery or a touch screen. Without the device-tree settings the kernel will not probe the devices. Enabling that on u-boot boot mode can be done by either modifying the device-tree file or create overlays and load them by u-boot script with "fdt apply" command. How can this be configured in EFI mode? Br, Frank -- 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] Nue OpenSUSE Build Service power outage / ARM
by Dirk Müller 13 Oct '17

13 Oct '17

Hi all, due to a large area power cut planned for this Saturday (tomorrow) affecting the building the SUSE and openSUSE server rooms are hosted we're going to shut down the OBS ARM architecture workers later today in a controlled fashion in order to not have them a hard power loss when this happens. As the servers are in a restricted environment it will probably take a few days to get everything back online. I'll start working on that on Monday during european office hours. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] Cargo bootstrap
by Dirk Müller 12 Oct '17

12 Oct '17

Hi, is anyone working already on the rust/cargo bootstrap for armv6/v7/aarch64 ? I don't want to waste/duplicate work. TIA, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] KVM on RPi3
by Loic Devulder 11 Oct '17

11 Oct '17

Hi guys! I would like to test virtual machines on my rpi3 (just for fun of course! with the limited memory...). I tried with a Leap 42.3 but I ran into some issue, mainly missing packages or not installed with the kvm_server pattern. So I had to add the "Virtualization" repo from OBS. But even with it, I get the following error when I try to create a VM: Initialization of device arm_gic failed: KVM with user space irqchip only works when the host kernel supports KVM_CAP_ARM_USER_IRQ I was able to execute a VM (YES!) after installing a 4.13 kernel from "Kernel Untested" repo. So, "simple" question: is it plan to add KVM_CAP_ARM_USER_IRQ in the official Leap 42.3 kernel? Or is it better to use Tumbleweed for KVM testing on rpi3? -- Loic -- 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] RPi3 camera module
by Alexander Bergmann 08 Oct '17

08 Oct '17

Hi, did anyone get the Raspberry Pi camera module working on a RPi3 with openSUSE Leap etc.? I couldn't find a package providing me raspistill. And the raspi-config script would add the line 'start_x=1' to '/boot/efi/config.txt' to enable the camera. This however will somehow break my setup and the system is not booting anymore. Any help would be appreciated. ;) Ciao, Alex~ -- Alexander Bergmann <abergmann(a)suse.com>, Security Engineer, GPG:9FFA4886 SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg)

2 1

[opensuse-arm] RPi3 poor WiFi performance
by Alexander Bergmann 07 Oct '17

07 Oct '17

Hi everyone, I've just installed Leap 42.3 on my RPi3 last night and had some bad WiFi performance. The SSH connection was nearly unusable. 21/21 packets, 0% loss, min/avg/ewma/max = 409.441/1454.630/1399.198/3025.166 ms At the end simply switching off the power_save option did the trick to have a working connection again. Details got discussed here [1]. #> iw dev wlan0 set power_save off The question is now, if we could disable power saving by default. There is already a patch [2] from the raspberrypi.org guys that is exactly doing that. Ciao, Alex~ [1] https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=138312#p919552 [2] https://github.com/lede-project/source/blob/master/package/kernel/mac80211/… -- Alexander Bergmann <abergmann(a)suse.com>, Security Engineer, GPG:9FFA4886 SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg)

3 2

[opensuse-arm] Upgrade of RPi3 to latest Tumbleweed shows a number of errors
by Freek de Kruijf 04 Oct '17

04 Oct '17

I used the image: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.aarch64-2017.09.09-Build3.11.raw.xz to initialize the SD card. After that, with some fiddling, I upgraded the system to Tumbleweed 20170920, including the kernel to 4.13.2-1. After the reboot I see the following error messages: sep 14 18:32:58 rpi3tum kernel: kvm [1]: Invalid trigger for IRQ4, assuming level low sep 14 18:32:58 rpi3tum kernel: OF: /soc/usb@7e980000: could not get #phy- cells for /phy and quite a lot of messages like: okt 03 23:42:29 rpi3tum kernel: bcm2835-dma 3f007000.dma: swiotlb buffer is full (sz: 221172 bytes) okt 03 23:42:29 rpi3tum kernel: bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 221172 bytes okt 03 23:42:29 rpi3tum kernel: mmcblk0: error -22 transferring data, sector 3465216, nr 1024, cmd response 0x900, card status 0xb00 okt 03 23:42:29 rpi3tum kernel: bcm2835-dma 3f007000.dma: swiotlb buffer is full (sz: 221172 bytes) -- 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

2 6

[opensuse-arm] Raspberry Pi1 is not booting
by Manu Maier 02 Oct '17

02 Oct '17

Hello, i test the factory image[1] of the Raspberry Pi 1 and is not booting. At Grub it makes a restart. U-Boot 2017.09 (Sep 13 2017 - 15:14:30 +0000) DRAM: 416 MiB RPI Model B+ (0x10) MMC: sdhci@7e300000: 0 reading uboot.env ** Unable to read "uboot.env" from mmc0:1 ** Using default environment In: serial Out: vidconsole Err: vidconsole Net: No ethernet found. starting USB... USB0: Core Release: 2.80a scanning bus 0 for devices... 4 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... 22299 bytes read in 121 ms (179.7 KiB/s) Found EFI removable media binary efi/boot/bootarm.efi reading efi/boot/bootarm.efi 475136 bytes read in 54 ms (8.4 MiB/s) ## Starting EFI application at 01000000 ... Scanning disk sdhci(a)7e300000.blk... Found 1 disks Welcome to GRUB! data abort pc : [<18ad3570>] lr : [<19f909b8>] reloc pc : [<feb7a570>] lr : [<000379b8>] sp : 19b5bf80 ip : 00000010 fp : 19f63aa8 r10: 00000007 r9 : 00000000 r8 : 19b5bffc r7 : 18ad3070 r6 : 18ad4000 r5 : 00000001 r4 : 00000000 r3 : 00000008 r2 : 00000010 r1 : 00000000 r0 : 00000000 Flags: nZCv IRQs off FIQs off Mode SVC_32 Resetting CPU ... resetting ... RPi2 and RPi3 boot without problems. Greetings, Manu [1] http://download.opensuse.org/ports/armv7hl/factory/images/openSUSE-Tumblewe…

2 7