January 2017 - 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] weird userspace crashes with 42.2 aarch64
by Josua Mayer 16 Feb '17

16 Feb '17

Hi everybody, I am approaching you with a collection of unusual crashes that occur on my test machine: It is an early version of the 8040 Community Board by SolidRun running a patched 4.9.0 kernel with the 42.2 rootfs from http://download.opensuse.org/ports/aarch64/distribution/leap/42.2/appliance… Now what I see are the following situations: 1) unhandled level XY translation fault (11) at 0xYYYYYYYY, esr 0xYYYYYYYY I have seen this with level 0, 1, 2 and 3 so far. So far I have seen it with zypper, where it freezes seemlinly at random, and ctrl+x produces this kind of error in dmesg. 2) undefined instruction: pc=... This one causes a program to crash and exit without any delay. I actively observed this twice with zypper, but the kernel log suggests it can happen to other applications too. Attached to this mail you can find a full system log with both kinds of crashes. You will find that I played with qemu when this log was produced. Sadly I did not save the initial log with the zypper crashes, except for one extract. I am quite unsure what to do about this. Has anybody seen such behaviour with other boards? br Josua Mayer

4 6

[opensuse-arm] "installing" openSuSE on raspberry pi2 using nfsroot
by Paul Neuwirth 28 Jan '17

28 Jan '17

Hello group, as I am really unlucky with sd cards, every one has bad sectors, data are partly not fully written without notice... ... I want to try to install openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2 image using a nfsroot. anyone who tried this? my idea was first to install to an sdcard (hope this will work) then try to build a initrd with network/nfs support (or does the original already have?) modify boot params to use nfsroot (and of course put the rootfs on an nfs share). even better would be a pxe-bootloader.. googling around i did not find such for arm/raspberry pi.. any hints? Thank you for any input and ideas nice weekend Paul -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 7

[opensuse-arm] openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.aarch64-2017.01.13-Build4.1.raw booting from usb-hdd/thumb drive without SD-Card
by Freigeist 28 Jan '17

28 Jan '17

Hello All, let me first thank all those of you who made the above mentioned image possible. To me, it is the first image since at least October 2016 that ist booting on my rpi3 without any problems. The only thing not working is wifi. But that was to be expected (as it sports kernel 4.9), as Andreas Färber already said on this list. So, Thank you and keep up the good work. As most of you may already know it is possible to boot an rpi3 without SD-Card from usb (hdd or thumb drive) directly since August 2016, following the instructions given in the link below: https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/ms… I tried that and it works without problems using Raspbian on both, an hdd and a thumb drive. Since my rpi3 is now unlocked and able to boot from usb I tried to make it boot with openSUSE using the image in the subject and copying bootcode.bin und start.elf from here https://github.com/raspberrypi/firmware/tree/next/boot to /dev/sda1/efi on my usb-hdd and - alternatively - to my usb thumb drive, replacing the original files on it. To make a long story short: It works! ...sort of (more about that later). It is possible to boot openSUSE-aarch64 on an rpi3 without SD-card directly from usb. And now we come to the "sort of" part of the boot process. - Grub2 appears and loads the kernel and initrd - all kinds of boot messages appear about services that were started and targets that were reached. But then the system hangs indefinitely with the following line: "A start job is running for dev-sda2.device (xys/no limit)" I spent the last two weeks trying to figure out what the problem is and how to solve it but did not find a solution. Here is what I found out and tried so far: 1. The message originates from systemd-fstab-generator a) To me it is not clear, though, why the system boots to this point and stops here. Since /boot on /dev/sda2 is found, services are started and targets reached, why is it a problem to find /dev/sda2.device? b) It does not matter how partition names are given to sda2. No matter if the name is derived from uuid, id, block device, anything else, the boot process stops here. 2. I tried to circumvent systemd-fstab-generator by a) adding fstab=0 or "no" to the kernel command line to prevent it from generating this line from my /dev/sda2 fstab entry. This is ignored by systemd-fstab-generator, the problem persists. b) adding "x-systemd.device-timeout=10" to the /dev/sda2 line of fstab. This is ignored by systemd-fstab-generator, the problem persists. c) renaming the file to systemd-fstab-generator.nil in /usr/lib/systemd/generators and creating an new initrd without it. The system still hangs at the same point but without the start job message. My questions are - Why does the system hang with the above message and won't boot on? - How can this problem be resolved? Any kind of help is appreciated. Best regards, Freigeist -- On a long enough timeline the survival rate for everyone drops to zero... -- 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] Watchdog trigger during first boot
by Frank Kunz 27 Jan '17

27 Jan '17

Hello, I have a problem when adding a new board to openSUSE (DE0-nano-SoC). The upstream u-boot for that board enables the watchdog with a 30 seconds timeout. That causes the board to get reset during the system partition resizing at first startup. To get watchdog support enabled I added the dw_wdt kernel module in config.sh to the dracut config. That is not enough, some service needs to use the driver to periodically trigger the watchdog (systemd, etc.). Is there a way to get that at the fist startup phase while the installation is completed? https://build.opensuse.org/package/show/home:frank_kunz:branches:openSUSE:F… Br, Frank -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 8

[opensuse-arm] openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.aarch64-2017.01.13-Build4.1.raw.xz
by Warren Stockton 21 Jan '17

21 Jan '17

I noticed that there was a new image at http://download.opensuse.org/ports/ aarch64/tumbleweed/images/ for the RPi3 that I hoped included a 4.9 kernel. I downloaded and transferred to the SD card but it has been stuck for over 30 minutes during the install. The last messages on the serial console when it hung are: [ 255.487262] systemd-journald[15489]: Received request to flush runtime journ1 [ OK ] Started Flush Journal to Persistent Storage. [ OK ] Started udev Wait for Complete Device Initialization. Starting Activation of LVM2 logical volumes... [ OK ] Started Activation of LVM2 logical volumes. [ OK ] Reached target Encrypted Volumes. Starting Activation of LVM2 logical volumes... [ OK ] Started Activation of LVM2 logical volumes. Starting Activation of LVM2 logical volumes... [ OK ] Started Activation of LVM2 logical volumes. [ OK ] Reached target Remote File Systems (Pre). [ OK ] Reached target Remote File Systems. Has anyone been able to successfully use this image? -- 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] BananaPi: Leap and sata
by Stefan Mack 20 Jan '17

20 Jan '17

Hello to all, yesterday I installed Leap from this source: http://download.opensuse.org/ports/armv7hl/distribution/leap/42.2/appli ances/ The first boot finished with a black screen - nothing happened even after a few minutes!? After this: poweroff an poweron - the second boot was fine. :-) Then I tried to copy the root-partition from the sd-card to a ssd like I did with the Tumbleweed-Images. I changed the bootargs in the boot.script and created a new boot.scr. But the boot isn't possible - see below the last lines of the log. Now my questions: - Why is the first boot with Leap not ok? - Is the u-boot of Leap without ahci-support? Thanks a lot Stefan ... Jan 01 01:00:14 linux systemd[1]: Starting Create Static Device Nodes in /dev... Jan 01 01:00:14 linux systemd[1]: Starting Apply Kernel Variables... Jan 01 01:00:14 linux systemd[1]: Started Create Static Device Nodes in /dev. Jan 01 01:00:14 linux systemd-sysctl[142]: Couldn't write '0' to 'dev/cdrom/autoclose', ignoring: No such file or directory Jan 01 01:00:14 linux systemd-sysctl[142]: Couldn't write '0' to 'net/bridge/bridge-nf-call-ip6tables', ignoring: No such file o Jan 01 01:00:14 linux systemd-sysctl[142]: Couldn't write '0' to 'net/bridge/bridge-nf-call-iptables', ignoring: No such file or Jan 01 01:00:14 linux systemd[1]: Started Apply Kernel Variables. Jan 01 01:00:14 linux systemd[1]: Started dracut cmdline hook. Jan 01 01:00:14 linux systemd[1]: Starting udev Kernel Device Manager... Jan 01 01:00:14 linux systemd-udevd[170]: Network interface NamePolicy= disabled by default. Jan 01 01:00:14 linux systemd[1]: Started udev Kernel Device Manager. Jan 01 01:00:14 linux systemd[1]: Starting udev Coldplug all Devices... Jan 01 01:00:15 linux systemd[1]: Started udev Coldplug all Devices. Jan 01 01:00:15 linux systemd[1]: Reached target Remote File Systems (Pre). Jan 01 01:00:15 linux systemd[1]: Reached target Remote File Systems. Jan 01 01:00:15 linux systemd[1]: Mounting Configuration File System... Jan 01 01:00:15 linux systemd[1]: Mounted Configuration File System. Jan 01 01:00:16 linux kernel: usbcore: registered new interface driver usbfs Jan 01 01:00:16 linux kernel: usbcore: registered new interface driver hub Jan 01 01:00:16 linux kernel: usbcore: registered new device driver usb Jan 01 01:00:16 linux kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Jan 01 01:00:16 linux kernel: ehci-platform: EHCI generic platform driver Jan 01 01:00:16 linux kernel: sunxi-mmc 1c0f000.mmc: No vqmmc regulator found Jan 01 01:00:16 linux kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Jan 01 01:00:16 linux kernel: ohci-platform: OHCI generic platform driver Jan 01 01:00:16 linux kernel: sunxi-mmc 1c0f000.mmc: Got CD GPIO Jan 01 01:00:16 linux kernel: sunxi-mmc 1c0f000.mmc: base:0xf08fe000 irq:28 Jan 01 01:00:16 linux kernel: mmc0: host does not support reading read-only switch, assuming write-enable Jan 01 01:00:16 linux kernel: mmc0: new high speed SDHC card at address e624 Jan 01 01:00:16 linux kernel: mmcblk0: mmc0:e624 SU08G 7.40 GiB Jan 01 01:00:16 linux kernel: mmcblk0: p1 p2 p3 -- 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] imx6 (sabrelite) Ethernet problem
by Guillaume Gardet 15 Jan '17

15 Jan '17

Hi, I am testing the latest Tumbleweed image on the Sabrelite (imx6q board) and the board freeze if I plug an Ethernet cable! And as soon as I unplug the cable, the board reboot. If I do a 'ifconfig eth0 down' before plugging the cable, all is fine, until I run 'ifconfig eth0 up'. So, I guess it is a driver problem. Does anyone already see a similar problem with imx6 boards? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 2

[opensuse-arm] Current Raspi 1 images
by Richard (MQ) 15 Jan '17

15 Jan '17

Hi List I've been trying to boot some recent opensuse tumbleweed images on my Raspi 1B. The images are all from: http://download.opensuse.org/ports/armv6hl/tumbleweed/images/ Tried openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2017.01.14-Build1.1.raw.xz openSUSE-Tumbleweed-ARM-LXQT-raspberrypi.armv6l-2017.01.14-Build1.1.raw.xz openSUSE-Tumbleweed-ARM-XFCE-raspberrypi.armv6l-2017.01.14-Build1.1.raw.xz - and before that, a few with build date 2016.11.23 All seem to fail booting with "initramfs unpacking failed: write error" followed unsurprisingly by a kernel panic, apart from JeOS where the screen shows just the Tux logo without any text. Please can anyone on this list advise if they are able to boot these images? Assuming not, is there an archive of last-known-good images for Raspi? Many thanks Richard -- Richard (MQ) Linux user # 439271 -- 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] Adding new board: No boot device
by Frank Kunz 10 Jan '17

10 Jan '17

Hello, I try to add a new ARM board (JeOS-socfpgade0nanosoc) to factory ARM. Now I have some problems to get the image [1] to work on the target. It cannot find a boot device during first startup (see appended serial console output). To debug that I did a setenv append kiwidebug=1 saveenv on u-boot console and by that the boot process should start a console. But problem 1: [1483747199.877840] Starting boot shell on /dev/tty2 [1483747200.888525] Searching for boot device... [1483747233.661872] Failed to find boot device ! Press Enter for maintenance (or press Control-D to continue): after that no input is accepted, neither Enter nor Control-D. I tried to reconfigure my serial terminal to test with CR, LF and CRLF line endings, all the same result. I guess that it has to do with the console on /dev/tty2, which is not the serial console. How can this be changed? Problem 2: The system immediately restarts with the latest images when it reached that point, that was not the case one week ago or so. How to debug or change that? Br, Frank [1] https://build.opensuse.org/package/show/home:frank_kunz:branches:openSUSE:F… Serial output: U-Boot SPL 2017.01-rc3 (Jan 06 2017 - 14:29:12) drivers/ddr/altera/sequencer.c: Preparing to start memory calibration drivers/ddr/altera/sequencer.c: CALIBRATION PASSED drivers/ddr/altera/sequencer.c: Calibration complete Trying to boot from MMC1 U-Boot 2017.01-rc3 (Jan 06 2017 - 14:29:12 +0000) CPU: Altera SoCFPGA Platform FPGA: Altera Cyclone V, SE/A4 or SX/C4, version 0x0 BOOT: SD/MMC Internal Transceiver (3.0V) Watchdog enabled I2C: ready DRAM: 1 GiB MMC: dwmmc0@ff704000: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: Terasic DE0-Nano(Atlas) Net: Error: ethernet@ff702000 address not set. No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:2... Found U-Boot script /boot.scr 2767 bytes read in 11 ms (245.1 KiB/s) ## Executing script at 02100000 switch to partitions #0, OK mmc0 is current device 7667392 bytes read in 545 ms (13.4 MiB/s) 41831930 bytes read in 2871 ms (13.9 MiB/s) 17507 bytes read in 73 ms (233.4 KiB/s) ## Loading init Ramdisk from Legacy Image at 07000000 ... Image Name: Initrd Created: 2017-01-07 21:42:27 UTC Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 41831866 Bytes = 39.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 06f00000 Booting using the fdt blob at 0x6f00000 reserving fdt memory region: addr=0 size=1000 Loading Device Tree to 03ff8000, end 03fff462 ... OK Starting kernel ... setterm: cannot (un)set powersave mode: Inappropriate ioctl for device Sat Jan 7 00:00:00 UTC 2017 [1483747200.768671] Searching for boot device... [1483747233.594935] Failed to find boot device ! KIWI Log: KIWI .profile contents: kiwi_align='1048576' kiwi_bootkernel='custom' kiwi_bootloader='uboot' kiwi_bootprofile='default' kiwi_cmdline='loglevel=3 splash=silent plymouth.enable=0 rootflags=size=100% console=ttyS0,115200n8' kiwi_cpio_name='initrd-oemboot-suse-tumbleweed' kiwi_delete='Mesa cracklib-dict-full fillup gdbm info insserv make mingetty openSUSE-release pam pam-modules perl perl-Bootload er permissions python python-base' kiwi_displayname='openSUSE' kiwi_drivers='crypto/*,drivers/acpi/*,drivers/acpi/dock.ko,drivers/ata/*,drivers/block/brd.ko,drivers/block/cciss.ko,drivers/bl ock/loop.ko,drivers/block/virtio_blk.ko,drivers/cdrom/*,drivers/char/hw_random/virtio-rng.ko,drivers/char/lp.ko,drivers/dma/*,d rivers/firmware/edd.ko,drivers/gpio/*,drivers/gpu/*,drivers/gpu/drm/*,drivers/hid/*,drivers/hwmon/*,drivers/ide/*,drivers/input /keyboard/*,drivers/input/mouse/*,drivers/md/*,drivers/message/fusion/*,drivers/mmc/*,drivers/mmc/card/*,drivers/mmc/host/*,dri vers/net/*,drivers/parport/*,drivers/phy/*,drivers/regulator/*,drivers/scsi/*,drivers/staging/hv/*,drivers/thermal/*,drivers/us b/*,drivers/virtio/*,fs/binfmt_aout.ko,fs/binfmt_misc.ko,fs/btrfs/*,fs/exportfs/*,fs/ext2/*,fs/ext3/*,fs/ext4/*,fs/fat/*,fs/fus e/*,fs/hfs/*,fs/isofs/*,fs/jbd/*,fs/jbd2/*,fs/mbcache.ko,fs/nls/nls_cp437.ko,fs/nls/nls_iso8859-1.ko,fs/nls/nls_utf8.ko,fs/over layfs/*,fs/quota_v1.ko,fs/quota_v2.ko,fs/squashfs/*,fs/udf/*,fs/vfat/*,fs/xfs/*,lib/crc-t10dif.ko,lib/crc16.ko,lib/libcrc32c.ko ,lib/zlib_deflate/zlib_deflate.ko,net/packet/*' kiwi_firmware='ofw' kiwi_fsmountoptions='noatime,nobarrier' kiwi_iname='initrd-oemboot-suse-tumbleweed' kiwi_iversion='2.7.1' kiwi_language='en_US' kiwi_loader_theme='openSUSE' kiwi_oemataraid_scan='true' kiwi_oemmultipath_scan='true' kiwi_oemskipverify='true' kiwi_oemswap='true' kiwi_oemswapMB='500' kiwi_profiles='default,custom' kiwi_revision='0845f334f23450ad03841febae8ddd10cb3b4a0b' kiwi_sectorsize='512' kiwi_splash_theme='openSUSE' kiwi_startsector='2048' kiwi_strip_delete='/etc/services /etc/udev/hwdb.bin /lib/firmware/brcm/*-pcie.bin /lib/firmware/radeon /lib/i686/nosegneg /lib/ modules/*/kernel/crypto /lib/modules/*/kernel/drivers/infiniband /lib/modules/*/kernel/drivers/isdn /lib/modules/*/kernel/drive rs/md /lib/modules/*/kernel/drivers/media /lib/modules/*/kernel/drivers/net /lib/modules/*/kernel/drivers/scsi /lib/modules/*/k ernel/net /lib/modules/*/kernel/sound /usr/bin/busybox /usr/bin/curl /usr/bin/diff /usr/bin/fbiterm /usr/bin/gawk /usr/bin/host /usr/bin/journalctl /usr/bin/rsync /usr/lib*/gconv /usr/lib/genisoimage /usr/lib/grub2 /usr/lib/ldscripts /usr/lib/perl5 /usr/ lib/rpm /usr/lib/systemd/catalog /usr/lib/systemd/system/busnames.target.wants /usr/lib/systemd/system/local-fs.target.wants /u sr/lib/systemd/system/multi-user.target.wants /usr/lib/systemd/system/poweroff.target.wants /usr/lib/systemd/systemd-backlight /usr/lib/systemd/systemd-bus-proxyd /usr/lib/systemd/systemd-coredump /usr/lib/systemd/systemd-localed /usr/lib/systemd/systemd -logind /usr/lib/systemd/systemd-machined /usr/lib/systemd/systemd-networkd /usr/lib/systemd/systemd-timesyncd /usr/lib/systemd /user /usr/lib/systemd/user-generators /usr/lib/udev/hwdb.d /usr/lib/wicked /usr/lib64/ldscripts /usr/sbin/wicked /usr/share/X1 1/locale /usr/share/backgrounds /usr/share/fbiterm /usr/share/fonts /usr/share/grub2/backgrounds /usr/share/help /usr/share/icu /usr/share/info /usr/share/kbd /usr/share/locale /usr/share/misc/magic /usr/share/pci.ids /usr/share/pci.ids.d /usr/share/spla shy /usr/share/tc /usr/share/wicked /usr/src/packages /var/adm /var/cache/zypp /var/log/* usr/share/bash-completion usr/share/b ash/helpfiles usr/share/emacs usr/share/sgml usr/share/zoneinfo usr/share/zsh' kiwi_strip_libs='libaio libdevmapper libdmraid-events-isw libdrm libfontenc libfreetype libgcc_s libjpeg libkmod libkms libnsl libnss_compat libnss_dns libnss_files libply-boot-client libply-splash-graphics libpng libresolv librt libselinux libsepol libs plashy libsplashycnf libsysfs libutempter libutil' kiwi_strip_tools='arch ata_id atftp atftpd awk basename bash bc blkid blockdev blogd btrfs btrfsck btrfsctl btrfstune b U-Boot SPL 2017.01-rc3 (Jan 06 2017 - 14:29:12) drivers/ddr/altera/sequencer.c: Preparing to start memory calibration drivers/ddr/altera/sequencer.c: CALIBRATION PASSED drivers/ddr/altera/sequencer.c: Calibration complete Trying to boot from MMC1 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 9