September 2016 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] Attempt to run KIWI on unsupported architecture 'armv8l'
by Dirk Müller 12 Apr '17

12 Apr '17

Hi, this is a known OBS bug, asked the admins to deploy a fix shortly. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 3

[opensuse-arm] ARM auto tests
by Guillaume Gardet 21 Nov '16

21 Nov '16

Hi ARM guys! I think current openQA AArch64 tests are done using qemu (at least virtualization). But, how far is ARM tests on real hardware? It seems os-autoinst support real hardware and I remember that some people worked on it during hackweeks. I would like to collect all information in order to maybe work on it a bit. For example, which devices do you use to power on/off boards. Did you use os-autoinst or some other tests tools? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 5

[opensuse-arm] Turris Omnia (prototype) enablement report
by Andreas Färber 06 Nov '16

06 Nov '16

Hello, This weekend I've had the opportunity to test openSUSE on a prototype of CZ.NIC's Indiegogo-funded Turris Omnia router [1]. In a FOSDEM 2016 talk a prototype had already been shown to the public, whereas this was the first time we could peek at the current software environment of a running prototype ourselves and provide some early third-party distro feedback to its creators. Known for being overly critical and aiming at perfect solutions, let me say in advance that the Armada 385 mainline kernel support looks quite good already, needing only the Turris Omnia Device Tree [2] apparently. Turris Omnia's U-Boot [3] is quite usable but will need a little more love before we can benefit from new features such as UEFI boot support (both upstream where it's not yet using the distro defaults [4] and downstream for deriving a clean new turris_omnia_defconfig). I'm confident that most of the functional limitations I observed can be fixed until the final board version ships to backers. That said, here's a quick how-to I would've added to the Wiki [1] if it let me... == Manual installation == As of 2016-03-18, the prototype's U-Boot does not yet support XHCI, so that the two USB ports cannot be used for booting. That leaves eMMC and mSATA as local boot options. === Building an upstream kernel === Use mvebu_v7_defconfig and enable CONFIG_BTRFS_FS. === Installation to USB === As of 2016-03-18, the prototype's U-Boot does not yet support XHCI and therefore does not recognize any USB devices on either of the two USB ports. Still you can place your rootfs onto USB. As of 2016-03-18, the prototype's kernel has USB drivers built as modules and no initrd, so you cannot directly boot a USB rootfs with it. An easy solution is to build an upstream kernel yourself with those drivers built-in and to copy it to the eMMC's /boot directory (e.g., zImage-next). Note: In linux-next.git next-20160318 kernel only USB 3.0 devices work. Partition your USB disk with GPT or MBR. Create a partition for the rootfs and extract an [http://download.opensuse.org/ports/armv7hl/tumbleweed/images/openSUSE-Tumbl… openSUSE-Tumbleweed-JeOS.armv7-rootfs.armv7l-Current.tbz] tarball. Then boot similar to this (derived from bootargs and mmcboot variables): setenv bootargs 'console=ttyS0,115200 root=/dev/sda1 rootfstype=ext4 rootwait rw' btrload mmc 0 0x01000000 boot/zImage-next @ btrload mmc 0 0x02000000 boot/dtb @ bootz 0x01000000 - 0x02000000 Note: As always, "/dev/sda1" is unsafe as it may become, e.g., /dev/sdb1 when an mSATA SSD or a second USB storage device is connected. You could save those commands in a U-Boot environment variable, otherwise you will need to re-type them on each boot. === Installation to mSATA === Unless you have another device with mSATA port, you may find it difficult to set up the SSD. As of 2016-03-18, the prototype's OpenWrt kernel did not recognize a Samsung SSD 850 EVO 120 GB mSATA card (while U-Boot's scsi scan does). As workaround you can compile an upstream kernel (cf. [[#Building_an_upstrea_kernel|above]]), copy it under a new name to /boot on the eMMC (e.g., zImage-next) and boot OpenWrt with this new kernel (derived from mmcboot variable): btrload mmc 0 0x01000000 boot/zImage-next @ btrload mmc 0 0x02000000 boot/dtb @ bootz 0x01000000 - 0x02000000 Now that you have a /dev/sda device for the mSATA SSD, you may find that OpenWrt does not come with parted, fdisk or gdisk tools for partitioning this device. One solution is to boot into openSUSE Tumbleweed, where you can easily install those tools, from USB (cf. [[#Installation_to_USB|above]]): setenv bootargs 'console=ttyS0,115200 root=/dev/sdb1 rootfstype=ext4 rootwait rw' btrload mmc 0 0x01000000 boot/zImage-next @ btrload mmc 0 0x02000000 boot/dtb @ bootz 0x01000000 - 0x02000000 >From inside openSUSE verify that /dev/sda is your mSATA card and partition it using gdisk (zypper in gptfdisk). Format your new partition and extract a JeOS rootfs tarball. For now just copy zImage-next and dtb over. mount /dev/sda1 /mnt tar xvjf [http://download.opensuse.org/ports/armv7hl/tumbleweed/images/openSUSE-Tumbl… openSUSE-Tumbleweed-JeOS.armv7-rootfs.armv7l-XXX.tbz] -C /mnt cp /boot/zImage-next /mnt/boot/zImage-next cp /boot/dtb /mnt/boot/armada-385-turris-omnia.dtb ln -sf zImage-next /mnt/boot/zImage ln -sf armada-385-turris-omnia.dtb /mnt/boot/dtb Boot similar to this: setenv bootargs 'console=ttyS0,115200 root=/dev/sda1 rootfstype=btrfs rootwait rw' setenv fdtfile armada-385-turris-omnia.dtb scsi scan btrload scsi 0:1 0x01000000 boot/zImage-next btrload scsi 0:1 0x02000000 boot/dtb/$fdtfile bootz 0x01000000 - 0x02000000 It's beginning to look much more like openSUSE, just lacking an openSUSE kernel still. === Installation to eMMC === In theory you can also replace OpenWrt with openSUSE, optionally backing it up as btrfs snapshot. To do so you'll need to boot from some other root device such as USB or mSATA. mount /dev/mmcblk0p1 /mnt btrfs subvolume snapshot /mnt/@ /mnt/root-pre-opensuse rm -rf /mnt/@/* tar xvjf [http://download.opensuse.org/ports/armv7hl/tumbleweed/images/openSUSE-Tumbl… openSUSE-Tumbleweed-JeOS.armv7-rootfs.armv7l-XXX.tbz] -C /mnt/@ cp /boot/zImage-next /mnt/@/boot/zImage-next cp /boot/dtb /mnt/(a)/boot/armada-385-turris-omnia.dtb ln -sf zImage-next /mnt/@/boot/zImage ln -sf armada-385-turris-omnia.dtb /mnt/@/boot/dtb Then on next boot you should boot into openSUSE automatically. === openSUSE kernel === Unlike mvebu_v7_defconfig, the openSUSE kernels build drivers as modules whenever possible. To boot you will need additional driver modules in a ramdisk. There's two easy ways to create such an initrd file. Either use Kiwi (as done for our JeOS SD card images) or boot into the system once without modules and have the initrd be created by dracut. If you zypper up or zypper dup the system for the first time, chances are a new kernel-default package gets installed and generates an initrd; you can force this the easy way by reinstalling the package (zypper in -f kernel-default) or figure out the lengthy dracut command line. Try to boot it like this: setenv bootargs 'console=ttyS0,115200 root=/dev/sda1 rootfstype=btrfs rootwait rw' scsi scan btrload scsi 0:1 0x01000000 boot/zImage btrload scsi 0:1 0x02000000 boot/dtb/armada-385-turris-omnia.dtb btrload scsi 0:1 0x03000000 boot/initrd bootz 0x01000000 0x03000000:$filesize 0x02000000 This resulted in: Kernel image @ 0x1000000 [ 0x000000 - 0x6f2d78 ] Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid ''To be investigated - U-Boot lacking CONFIG_SUPPORT_RAW_INITRD?'' This is blocking creation of a JeOS disk image. Cheers, Andreas [1] https://en.opensuse.org/HCL:Turris_Omnia [2] https://gitlab.labs.nic.cz/turris/openwrt/tree/test/target/linux/mvebu/file… [3] https://gitlab.labs.nic.cz/turris/turris-omnia-uboot/commits/omnia [4] http://git.denx.de/?p=u-boot.git;a=blob;f=include/configs/db-88f6820-gp.h;h… -- 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

2 2

[opensuse-arm] Raspberry Pi JeOS cleanups
by Andreas Färber 26 Oct '16

26 Oct '16

Hello, Here's a quick heads-up about some cleanups I've been doing for our Kiwi images. The relationships of the images have been slightly tweaked and there are two new experimental images. Rough overview over the new _link relations (E20, LXQT, XFCE left out): openSUSE:Factory:ARM/JeOS |`- openSUSE:Factory:ARM/JeOS-raspberrypi |`- home:a_faerber:branches:openSUSE:Factory:ARM/JeOS-raspberrypi2 (NEW) | (=> to be created in openSUSE:Factory:ARM - still without USB) |`- devel:ARM:Factory:Contrib:HEAD/JeOS (new) | |`- devel:ARM:Factory:Contrib:HEAD/JeOS-efi.aarch64 | | (previously a direct _link to openSUSE:Factory:ARM) | `- devel:ARM:Factory:Contrib:HEAD/JeOS-raspberrypi3 (NEW) |`- devel:ARM:Factory:Contrib:RaspberryPi/JeOS-raspberrypi |`- devel:ARM:Factory:Contrib:RaspberryPi2/JeOS-raspberrypi2 | `- devel:ARM:Factory:Contrib:RaspberryPi2:Staging/JeOS-raspberrypi2 | (previously a direct _link to openSUSE:Factory:ARM, broken) |`- devel:ARM:Factory:Contrib:RaspberryPi2/JeOS-raspberrypi3 | `- devel:ARM:Factory:Contrib:RaspberryPi2:Staging/JeOS-raspberrypi3 | (previously a direct _link to openSUSE:Factory:ARM) `- devel:ARM:Factory:Contrib:RaspberryPi3/JeOS-raspberrypi3_aarch64 Main motivation was to facilitate testing of openSUSE kernel based Raspberry Pi 2 and 3 images (help needed with debugging: why no USB?!) and to simplify maintenance of derived Contrib images. While most of the .kiwi[.in] changes merge just fine, any .tgz updates require manual conflict resolution - the above scheme should require less such merges. Note: These changes are independent of the ext4 fixes on the U-Boot level that Stefan has been working on - no functional changes yet. Regards, 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

3 7

[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] 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] Image for RPi3, using architecture aarch64 works
by Freek de Kruijf 02 Oct '16

02 Oct '16

Just tried the image for the Raspberry Pi 3 openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3_aarch64.aarch64-2016.09.27- Build6.1.raw.xz and I have a working system. The only problem I had was, when I had a USB storage device connected, the system did not continue in the boot process, or I was too inpatient. I disconnected that device and started the boot process again and now I have a working system. -- 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 4

[opensuse-arm] Raspberry PI Images broken
by Torsten Rosenberger 26 Sep '16

26 Sep '16

Good Morning I tried the last 2 weeks some images for the Raspberry PI. But all stops during boot. After the kernel loads i got /lib/modules/4.3.3-5-raspberrypi/kernel/drivers/net/usb/usbnet.ko error=No such file or directory and also after that a second boot ist not possible the partitions are damaged. I dowload the images from https://en.opensuse.org/HCL:Raspberry_Pi openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2016.09.16-Build1.2.raw.xz But also the grafik images have the same error. BR Torsten -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 11

[opensuse-arm] JeOS: choice for fast_gettext
by Andreas Färber 24 Sep '16

24 Sep '16

Hello, All Factory JeOS images seem unresolvable due to choice for a rubygem fast_gettext (with -1_1 vs. without) pulled in by YaST. Should this be addressed by a Prefer in the project config? Or via our JeOS package list? Regards, 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

2 1

[opensuse-arm] Is kernel same as used for raspbian?
by Tony Su 24 Sep '16

24 Sep '16

Starting a project using a RPi Zero, which is the $5 minimalist version of RPi, launched a few months ago in May 2016. Because of its minimalist hardware, Setting up for development is a fairly unique procedure. Unless I want to try the alternative method setting up a monitor and keyboard, Apparently the current kernel in the Raspbian image includes modules to enable a headless ethernet connection over a USB B/B cable. This is the base article which includes the instructions to declare, then load a module called dwc2 in the boot loader. http://blog.gbaman.info/?p=791 Absent that, Maybe someone who is running a current openSUSE_TW ARM image can check whether the dwc2 module exists (although not likely loaded). TIA, TSU -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 6