openSUSE ARM August 2017

arm@lists.opensuse.org

22 participants
14 discussions

[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

[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] Khadas VIM2 Max TV Box
by Loic Devulder 22 Sep '17

22 Sep '17

Hi all! Sounds a very interesting card: https://www.gearbest.com/tv-box/pp_676880.html?lkid=10642329 64GB of eMMC for this price is not too bad, as 3GB of RAM too (4GB could have been better :-p). According to the specs this card has UEFI boot, it would be good to try to install UEFI aarch64 version :-) Just need to see the status of S912 SoC in the mainline kernel (at least in the openSUSE kernel). Now I still don't know what to choose between Rock64 and this one... -- Loic -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 8

[opensuse-arm] Tumbleweed AArch64 not publishing anymore?
by Guillaume Gardet 06 Sep '17

06 Sep '17

Hi, it seems that AARch64 Tumbleweed is no more updated on download.opensuse.org server. AArch64 images are from June whereas newer images are available on OBS. Update repo is from 4th of august. kernel is 4.11.8 whereas 4.12.8 is ready in OBS. Is there a never ending build problem which prevent publishing or maybe just a publish problem? Guillaume -- 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] Kernel configs for new boards
by Rick Ashford 31 Aug '17

31 Aug '17

What is the preferred method for submitting changes to the default kernel configs and device trees to add support for new boards? Pull requests on GitHub? Patch requests in OBS? Something else? I am in the process of trying to get the EspressoBin board enabled for Tumbleweed. I have it working with my own 4.12 build, but I'd like to make it so the Tumbleweed kernel supports it out of the box. -- Rick Ashford Sales Engineering Manager - West rick.ashford(a)suse.com M:(512)731-3035

2 1

[opensuse-arm] Raspberry Pi 3 Ad-Hoc WiFi
by Roger Oberholtzer 29 Aug '17

29 Aug '17

I am trying to set the wlan0 interface on a Raspberry Pi 3 to be Ad-Hoc instead of Managed. I am using commands that I have used on openSUSE that work. But I cannot get it to work on the Pi 3. The network is managed by wicked. The commands are: ip link set wlan0 down iwconfig wlan0 essid myId mode Ad-Hoc ip link set wlan0 up ip addr add 10.1.1.10 dev wlan0 route add default gw 10.1.1.10 It is the iwconfig command that fails: # iwconfig wlan0 essid myId mode Ad-Hoc Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Device or resource busy. And I do not know why. How can it be busy? ip addr reports: 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether b8:27:eb:9a:00:74 brd ff:ff:ff:ff:ff:ff I have also tried this in YaST. There is no error reported, but the device is unchanged. The settings are remembered by YaST. But the device is unchanged. There are some errors in the log: [91050.345081] brcmfmac: brcmf_cfg80211_change_iface: iface validation failed: err=-16 [91090.214264] brcmfmac: brcmf_cfg80211_change_iface: iface validation failed: err=-16 [92274.237410] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [92274.353955] brcmfmac: brcmf_cfg80211_escan: Connecting: status (3) [92274.353974] brcmfmac: brcmf_cfg80211_scan: scan error (-11) [92322.032508] brcmfmac: brcmf_cfg80211_change_iface: iface validation failed: err=-16 [92350.696929] brcmfmac: brcmf_sdio_readframes: RXHEADER FAILED: -110 [92350.696948] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK [92376.662941] brcmfmac: brcmf_cfg80211_change_iface: iface validation failed: err=-16 I found similar instructions at https://www.raspberrypi.org/forums/viewtopic.php?f=36&t=18771 and it seemed to work for that user. It was with Raspbian. I am not sure what to make of the error. -- Roger Oberholtzer -- 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] Wireless interface on Raspberry Pi 3
by Roger Oberholtzer 29 Aug '17

29 Aug '17

My wireless device does not show up on my Raspberry Pi 3, running an up-to-date Leap 42.2 I have seen a number of places suggest editing /etc/dracut.conf.d/raspberrypi_modules.conf and removing sdhci-iproc so that the file becomes: add_drivers+=" bcm2835-sdhost bcm2835_dma mmc_block " # Workaround for Wifi # omit_drivers+=" sdhci-iproc" Then run mkinitrd -f Two questions;: 1. Is this the appropriate edit? 2. Does one run mkinitrd and not dracut on the Raspberry? I really do not want to mess up the initrd file! -- Roger Oberholtzer -- 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] eSATA support broken in Leap 42.3
by Alessio Adamo 28 Aug '17

28 Aug '17

Hi guys, After a Tumbleweed upgrade broke my Cubox-i Pro, since Leap was going to be released soon, I decided to switch to Leap. By the way, I'm interested in your thoughts about Leap ARM stability compared to Tumbleweed. Anyway, going back on topic... I banged my head against the wall for two days trying to boot from eSATA but the partitions wouldn't mount. I thought there was something wrong with boot.scr configuration or maybe with the rootfs. Finally, I decided to try Tumbleweed and it worked like a charm. Any ideas what could be wrong with Leap? Thanks Alessio -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

openSUSE ARM August 2017