October 2016 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] All Raspberry Pi images EFI-enabled - call for testing
by Andreas Färber 18 Oct '16

18 Oct '16

Hi, Both the Tumbleweed raspberrypi image and the Contrib raspberrypi, raspberrypi2 and raspberrypi3 images now boot from U-Boot into GRUB. This feature was already enabled for the raspberrypi3_aarch64 image and until recently had been impacted by the ext4 64bit feature breakage. Now that we have a workaround and are preparing to enable raspberrypi2 in Tumbleweed, it was time to clean this up. I had already been successfully running manually GRUB2-converted installations for many weeks. Now Tumbleweed based raspberrypi and raspberrypi2 images were tested; for the Contrib projects I have faked the filenames U-Boot expects, based on upstream vs. downstream .dtb filenames and testing of rpi-2-b as well as $fdtfilename in u-boot-rpi332b v2016.09.01. As a side effect, the faked .dtb filenames also fix the model B+, which was using the model B's .dtb so far. Known issues: * Overwriting an SD card that had the old partitioning scheme with separate /boot partition leads to a GRUB rescue shell, i.e. unbootable system. Workaround: Either zero out the old GPT or the full SD card (took ~45 min for 32 GB...) before dd'ing the image. https://lists.opensuse.org/opensuse-arm/2016-10/msg00082.html Please report if any other boot issues remain with the updated images. Outlook: * With my bcm28*.dtb symlinks in place for the Contribs, we can drop the hardcoded $fdtfile bcm27*.dtb values in uboot-image-setup.in now (b-plus vs. b TODO comment). * We could also drop some non-$is_efi paths in uboot-image-install.in once we're confident we don't need to switch back in any branch. * Once Factory gets the 4.8 kernel (sr#435703), we can build official Tumbleweed images for Raspberry Pi 2 and 3. Have a lot of fun, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, 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

1 0

[opensuse-arm] RPi image - Need info how it's supposed to work
by Tony Su 17 Oct '16

17 Oct '16

Right now, When I insert the RPi 1 image into my RPi Zero, it just sits there... nothing happening. I'd ordinarily expect the LED light to be blinking furiously as the system boots up, so it's likely the image just isn't bootable. Have written the image 2 ways... Following the instructions as described on the following link using xzcat to decompress the JEOS .xz file, which is then piped to dd, writing to the sdcard. https://en.opensuse.org/HCL:Raspberry_Pi I also extracted the file, then used Win32DiskImager to write results to the sdcard blindly which still wouldn't work... When both failed, I took a look at what the uncompressed result was, and I see not a raw file system but executable binary files and the main image in ELF format. Is the flow for how these files are supposed to execute documented somewhere? Or, is the source for all this publicly visible(I've looked around, can't find in OBS, Studio, GitHub)? It's kind of hard to see where the problem might be when the code is in binary format... Thx, Tony . -- 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] RPi zero unable to boot images
by Tony Su 17 Oct '16

17 Oct '16

Decided to take another look at trying to boot TW RPi 1 images on a RPi zero, hooked up to a monitor to see stdout. Have tried the following TW LXQT and JeOS images, the LXQT is the latest build and the JeOS is one release older. openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2016.09.27-Build1.8.raw.xz openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2016.06.12-Build2.10.raw.xz Both have same results. The boot process proceeds until unable to find a "config.txt" file. Knowing the file should actually have a capital "C" I renamed the file to "Config.txt" But with no different result. The following is a link to a photo image of stdout when boot stops, is the same for both images https://goo.gl/photos/uV2FyFdwv2SkQToT8 >From that boot prompt, I can type "help" but if there is a command that might continue while also referencing or injecting the Config.txt file, I don't know what that might be. I've waited over an hour each time in case the boot might just have taken longer than expected, but there's no difference. The display is the same (as the photo). Each time, when the boot has failed, I've inserted the card back in a big machine, and I can see that the boot process has at least created 3 partitions, EFI, boot and root. I didn't try to mount the card or partitions to inspect the contents of the partitions. Anything else to try? TIA, Tony -- 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] U-Boot v2016.11-rc1 in Staging
by Andreas Färber 16 Oct '16

16 Oct '16

Hello, With v2016.09.01 in Base:System and on its way to Factory, I have updated Base:System:Staging to v2016.11-rc1: https://build.opensuse.org/project/show/Base:System:Staging All patches rebased cleanly. All builds are green. rpi2 and rpi3 tested. It's still early in the release cycle, so I imagine any EFI/ext4/... bug fixes should still go to tumbleweed-2016.09 branch and Base:System. But anyone facing problems with v2016.09.01 can now easily test whether v2016.11-rc1 works any better. Have a lot of fun, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, 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

1 0

[opensuse-arm] JeOS-raspberrypi3_aarch64 fail to boot
by Matwey V. Kornilov 15 Oct '16

15 Oct '16

Hello, I am trying to boot from openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3_aarch64.aarch64-2016.10.15-Build1.1.raw from openSUSE:Factory:ARM I see the following: U-Boot 2016.07 (Sep 28 2016 - 15:18:17 +0000) DRAM: 880 MiB RPI 3 Model B (0xa22082) MMC: bcm2835_sdhci: 0 reading uboot.env ** Unable to read "uboot.env" from mmc0:1 ** Using default environment In: serial Out: lcd Err: lcd Net: Net Initialization Skipped No ethernet found. starting USB... USB0: Core Release: 2.80a scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 1 Ethernet Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found EFI removable media binary efi/boot/bootaa64.efi reading efi/boot/bootaa64.efi 729088 bytes read in 83 ms (8.4 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC ## Starting EFI application at 0x01000000 ... WARNING: Invalid device tree, expect boot to fail Scanning disks on usb... Scanning disks on mmc... MMC Device 1 not found MMC Device 2 not found MMC Device 3 not found Found 5 disks Welcome to GRUB! error: terminal `gfxterm' isn't found. EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied EFI stub: ERROR: could not determine UEFI Secure Boot status. EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... EFI stub: ERROR: Failed to update FDT and exit boot services and nothing else happens. -- 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] openSUSE on Nexbox z68 (GeekBox like TV box)
by LOIC DEVULDER 13 Oct '16

13 Oct '16

Hello all! I have a Nexbox z68 android TV box with a RK3368 processor that I want to play with. This box is like the GeekBox but cheaper (I bought mine for 30€). And, of course, also with less connectors, but it’s really cheap for a 2GB RAM / 16GB eMMC box. The hardware of the two box are pretty close, I’ve been able to boot the Ubuntu GeekBox version without any problem. One of missing function is the serial console by default (like a lot of TV box) but I’ve been able to use it with some minor work. If you want to try, give a look at my post on FreakTab (I tried to add the link but it seems that it's not allowed by the forum rules, my message was denied). Now, I want to try openSUSE on it. I saw that Andreas has a WIP on GeekBox (https://en.opensuse.org/HCL:GeekBox) and, as I understand, it’s possible to boot openSUSE with both the vendor U-Boot or the mainline U-Boot. For the moment, I want to stay with the vendor version because at this time I don’t known how to enter MaskRom mode (there is two test points near the eMMC chip, I just need to test it). Here my question (finally!): what openSUSE image do I use? And where to find the initrd? I found a kernel in the generic JeOS image but no initrd... Regards, Loic N��r��y隊Z)z{.�櫛맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.�櫛�0��Ǩ�

3 8

[opensuse-arm] JeOS structure and _links
by Fabian Vogt 10 Oct '16

10 Oct '16

Hi, I'm currently working on getting the Pine64 upstream image updated to latest sources (firmware, u-boot, kernel and dtb) and the SRs are ready. However, due to the current structure of _links in the ARM projects on OBS merging will probably break some if not most of those, as told by afaerber. I propose generating the uboot-*.tgz files with the C preprocessor as well, just like Images.kiwi.in, so that changes in the uboot-image-install.in or uboot-image-setup.in files only affects the .tgzs for the relevant boards. That way changes in the parent JeOS package can be merged easily, even automatically in most cases. It would also result in more readable scripts (IMO) as the relationship between board and installation procedure is more obvious, compared to guessing which file relates to which boards. Suggestions, opinions? Cheers, Fabian -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, 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

5 11

[opensuse-arm] No wlan on raspberry pi 3
by Jogchum Reitsma 08 Oct '16

08 Oct '16

I installed openSUSE-Tumbleweed-ARM-XFCE-raspberrypi3_aarch64.aarch64-2016.09.27-Build8.4.raw.xz in my PI 3, but got no wlan. Yast shows only eth0, as does 'ip a'. Having read the thread started by Freek de Kruijff on Mar 26 this year on this list, I found the files brcmfmac43430-sdio.bin and brcmfmac43430-sdio.txt where missing indeed in /lib/firmware/brcm/ So I downloaded them from https://github.com/RPi-Distro/firmware-nonfree/raw/master/brcm80211/brcm/ to /lib/firmware/brcm/ and rebooted, but still no wlan. What can I do to get wlan working? Jogchum Reitsma -- 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] pine64 tumbleweed image
by Paul Gonin 04 Oct '16

04 Oct '16

Hi ! I gave a try today to the pine64 non-upstream openSUSE Tumbleweed image [1] Writing the image to sdcard went fine and I was able to boot. I did not get to a prompt though. It stopped at Loading linux.vmx... Loading initrd.vmx... EFI stub: Booting Linux Kernel... EFI stub: UEFI Secure Boot is enabled. EFI stub: Generating empty DTB EFI stub: Exiting boot services and installing virtual address map... U-Boot EFI: Relocation at 00000000bffacff0 is out of range (1fffc1d0) U-Boot EFI: Relocation at 00000000bffad000 is out of range (1fffc1e8) U-Boot EFI: Relocation at 00000000bffad010 is out of range (1fffc1e8) U-Boot EFI: Relocation at 00000000bffad020 is out of range (1fffc058) Any advice what I can try next ? Anything I can do to help ? Thanks Paul [1] http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Pin… -- 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] openSUSE Leap 42.2: RPI3 aarch64
by Matwey V. Kornilov 02 Oct '16

02 Oct '16

Hello, There is aarch64 port for Leap 42.2. But I can not find images for RPi3. It would be great to test. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 2