- openSUSE ARM

[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

[opensuse-arm] 4.10-rc2 kernel testing
by Andreas Färber 05 Jan '17

05 Jan '17

Hello, After the 4.9-rcX kernel troubles, Kernel:HEAD v4.10-rc2 is looking good so far: (+ = boots successfully, - = doesn't boot successfully) armv6hl: + Raspberry Pi Zero armv7hl: + BeagleBone Black (kernel-default) + Cubietruck (kernel-lpae) + Jetson TK1 (kernel-lpae) + Raspberry Pi 2 (kernel-lpae) aarch64: - Pine64 (new in 4.10, using U-Boot's dtb for lack of dtb-allwinner) + Raspberry Pi 3 Cheers, 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] cubox-i wireless setup
by Alessio Adamo 04 Jan '17

04 Jan '17

Hi guys, I have tumbleweed running on my cubox-i pro, and the wireless card is working. But I set it up when 13.2 just came up (to give you an idea) and now, on a fresh Tumbleweed or Leap 42.2 I don't remember anymore how I did it. The system doesn't seem to recognize the card. In yast when I add the wireless interface, I'm not able to select a pertaining kernel module, nor I'm able to scan the network. Any hint on how I should proceed? Many thanks. Regards Alessio -- 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] Cross compiling ARM on x64
by Roger Oberholtzer 04 Jan '17

04 Jan '17

I am currently building software for a Raspberry using a Raspberry as the build computer. It works surprisingly well. Nonetheless, I am considering setting up doing cross compiling on an intel x86 (non ARM) computer. I guess installing cross compilers and such tools from OBS is okay. I already do this for doing Windows (32- and 64-bit) cross compiling. I also install from OBS the various libraries needed for the Windows cross compile. They are nicely put in /usr/i686-w64-mingw32/sys-root/mingw or /usr/x86_64-w64-mingw32/sys-root/mingw. They are not installed in the Linux /usr/bin/ or /usr/lib/ trees. Unfortunately, I am guessing this would not be the case for ARM packages (e.g., libjpeg8-8.1.2-40.2.aarch64 and libjpeg8-devel-8.1.2-40.2.aarch64). They would be installed in the /usr/bin/ or /usr/lib/ trees, as that's where they are expected to be. Which is perhaps not what I want on a cross-compiling system Am I missing some brilliant thing to get these types of things installed in some other tree? Or is cross-compiling going to be more problematic than maintaining a Raspberry to do this work? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 18

[opensuse-arm] SUSE or openSUSE images for x86
by Jimmy PIERRE 03 Jan '17

03 Jan '17

Greetings, Somewhere around 22nd Dec 2016, RaspberryPi.org updated an image of Debian for x86. This of course can lure people to endorse Raspbian/Debian when their old PC dies for real. I am wondering, do SUSE or openSUSE have any project to cater for x86? This will help putting one foot in the door, figurately speaking and pave the way to x64 versions Tumbleweed, SUSE, Leap ... Just my two cents... May I take this opportunity to wish you a Happy New Year 2017, full of fun and above all health! Jimmy nui.fr -- 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] Raspi 3B: doesn't start correctly
by Edgar Dombrowski 02 Jan '17

02 Jan '17

Hallo, Raspbi-friends. I have download last sunday 2 Versions, but after installation te boot-activity stopped. 1. Version: openSUSE-Tumblewéed-ARM-E20-raspberrypi3-2ß16-11-23-Build4.21.raw.gz 2. Installation on a 16GB-SD-stick /dev/sdc1 200 MB /dev/sdc2 ext3 207 MB BOOT /dev/sdc3 btrfs 4,38 GB ROOT 3. When starting I get the following messages Menue: openSuse (vmx) (early messages not copied, to fast) FailSafe openSuse (vmx) Booting OpenSUSE.vmx (no text) loading linux.vmx loading initrd.vmx ( approx. 10 lines no text) EFI stub: Booting Linux Kernel EFI stub: UEFI Secure Boot is enabled EFI stub: Using DTB from configuration table EFI stub:Exiting boot servies and installing address map.... Thank you for any advice Regards Edgar Dombrowski, DJ3PU, Munich -- 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] Raspberry Pi2 images not booting
by Knurpht - Gertjan Lettink 02 Jan '17

02 Jan '17

Hi, It looks like none of the current TW images for Rpi2 are working. Am I correct or struck by the coincedence of three faulty SD cards that do work with other distros? -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 3

[opensuse-arm] Tumbleweed JeOS btrfs issue: dtb missing
by Andreas Färber 02 Jan '17

02 Jan '17

Hi, Retesting my JeOS-hikey image with U-Boot I noticed that with the recent btrfs enablement the dtb folder is on the wrong partition (btrfs instead of ext3) and thus cannot be loaded by U-Boot. I am assuming this is also the reason why people reported recent rpi3 images as non-working! Could one of you guys who made that change please look into why this is misbehaving or revert that change? Thanks, 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 1

[opensuse-arm] armv7l tumbleweed repo out of sync(?)
by Matwey V. Kornilov 25 Dec '16

25 Dec '16

1 1

[opensuse-arm] zypper issues on Raspberry PI3
by Roger Oberholtzer 22 Dec '16

22 Dec '16

I am trying to update my Raspberry PI3, and have a couple issues: 1. I can't seem to get zypper to download http://download.opensuse.org/ports/aarch64/factory/repo/oss/suse/noarch/ker… It gets 3 MB or so and then claims Timeout exceeded when accessing 2. I have a repository in OBS with some ARM packages (http://download.opensuse.org/repositories/home:/rogeroberholtzer/openSUSE_F…) When installing from there, I get this kind of error: blt-3.0a-57.5.aarch64.rpm: Header V3 DSA/SHA1 Signature, key ID 605a090d: NOKEY V3 DSA/SHA1 Signature, key ID 605a090d: NOKEY blt-3.0a-57.5.aarch64 (RSofT ARM): Signature verification failed [4-Signatures public key is not available] I can ignore it and the install continues. But I don't know why I get the error. I have repositories for other platforms and they have always worked fine. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 7

Re:Re: [opensuse-arm] User name and Passwd
by Edgar Dombrowski 18 Dec '16

18 Dec '16

Hallo, Linuxer. Vielen Dank für die vielen Hinweise. Es hat "natürlich" geklappt. Schönen 4. Advent MfG Edgar Dombrowski, DJ3PU, München -- 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] User name and Passwd
by Edgar Dombrowski 17 Dec '16

17 Dec '16

Thanks to Roger Oberholtzer I installed the Raspipi 3B file /openSUSE-Leap42.2-ARM-JeOS-raspberrypi3.aarch64-2016.11.25- Build1.9.raw.xz It took approx. 10 min. to ask for Username and Password. Can anny give this words when fist boot? Thanks for your help and all best for ete weekend. Edgar Dombrowski, DJ3PU, Munich -- 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] Kernel bug in runtime-wrappers.c
by LOIC DEVULDER 14 Dec '16

14 Dec '16

Hi all, Just for information, I ran into a kernel bug on my R120-P31 kernel (yes, another one :-)) and I have opened a bug for this: https://bugzilla.suse.com/show_bug.cgi?id=1015378 It's on openSUSE Leap 42.2 with latest kernel. Cheers, Loic -- 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] Request for testing help: openSUSE Leap 42.2 for ARMv7 images
by Dirk Müller 12 Dec '16

12 Dec '16

Hi All, over the last few days I've been pretty busy with enabling pre-configured appliances for ARMv7 and AArch64 on openSUSE Leap 42.2, and I'm happy to report that we now have some images available: http://download.opensuse.org/ports/armv7hl/distribution/leap/42.2/appliance… http://download.opensuse.org/ports/aarch64/distribution/leap/42.2/appliance… As you can see its a pretty elaborative list of images, and I don't have time to test all of them myself. so whoever is interested in having some of those variants working for him, please try them out and report both successes and failures. The overall goal is to announce the ARM port end of next week (Dec 1st) so it would be great to have some testing feedback before that (and << before that so that we can maybe even fix it before announcement). Thanks a lot in advance, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

14 19

[opensuse-arm] U-Boot update
by Guillaume Gardet 07 Dec '16

07 Dec '16

Hi, I would like to update u-boot to v2016.11 in Factory (and in Base:System) in order to start working on (and update :Staging to) 2017.01-rc1. Is there any objection? Guillaume -- 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] RFC: Expansion boards in the Wiki
by Andreas Färber 29 Nov '16

29 Nov '16

Hey guys, I recently started playing with connecting Raspberry Pi Hats and Arduino Shields to boards and am wondering where/how to document this. Hats may be compatible with multiple boards but may need board-specific instructions for the device tree. I am therefore thinking that an expansion-board-centric page with instructions for one or more boards may be the best approach. For ARM boards we are so far using the flat HCL namespace and a Category:ARM_devices to group them. Should we do the same for shields (HCL:Foo_Shield) and have another Category page to locate them? Or should we have some two-level namespace like HCL:Arduino_Shield/Foo? Another interesting question then is how would we generate a list of compatible expansion boards pages on, say, HCL:Raspberry_Pi2? Would that be possible if we had, e.g., Category:Raspberry_Pi_B+_Connector? Or should we rather manually maintain such bidirectional links? Any thoughts and suggestions appreciated. Cheers, 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 4

[opensuse-arm] SLES on RPi3
by Bill Merriam 23 Nov '16

23 Nov '16

It appears SUSE gave out free RPi3's with cool custom cases at SUSEcon. They had SLES installed on them. I wasn't there so I missed out on the cool case but it turns out you can still get a copy of SLES with a 365 day license and 60 days of patches. https://www.raspberrypi.org/blog/suse-linux-enterprise-server-for-raspberry… http://hackerboards.com/first-64-bit-distro-for-raspberry-pi-3-issuse/ https://www.suse.com/communities/blog/suse-linux-enterprise-server-raspberr… That blog post has this link for the download. Why do people use URL shorteners for links that are on web pages? http://tinyurl.com/slespi This weekend I have lots of versions of OpenSUSE for ARM and now SLES to test. Bill -- 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] Tumbleweed-Jeos fails on second boot on raspberry and pi and pi2
by Herbert Graeber 23 Nov '16

23 Nov '16

Hi! I tried the latest raspberry pi and pi2 images (armv6l-2016.1.15-Build57 resp. armv7l-2016.11.15-Build5.9). Both fail on the second boot with the error "ext4fs_devread read outside partition ...". Afterward it tries to boot from TFTP. Searching the net gives the suggestion, that the 64bit feature may be set on the ext4 partition, so that U-Boot cannot boot. I have found a matching opensuse bug report (boo#989284), too. But checking the partition with dumpe2fs and haven't found this feature. Are any hints how I can make the images work? How can help to resolve this issue? Here is the full log from the pi2: > U-Boot 2016.09.01 (Oct 15 2016 - 11:25:48 +0000) > > DRAM: 880 MiB > RPI 2 Model B (0xa01041) > 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:2... > Found U-Boot script /boot/boot.scr > ext4fs_devread read outside partition 2225344 > ## Executing script at 02000000 > Wrong image format for "source" command > SCRIPT FAILED: continuing... > 11691 bytes read in 128 ms (88.9 KiB/s) > > USB device 0: unknown device > Waiting for Ethernet connection... unable to connect. > missing environment variable: pxeuuid > missing environment variable: bootfile Herbert

1 0

[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] Tests with images from http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi3/images/
by Freek de Kruijf 19 Nov '16

19 Nov '16

I did tests with images from the above site on: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.aarch64-2016.11.15-Build7. [4-6].raw.xz All did show the Grub boot screen and continued, but stopped with a message on my TV screen as in the attached photo. -- fr.gr. member openSUSE Freek de Kruijf

1 2

[opensuse-arm] Image from download /ports/aarch64/tumbleweed does not boot at all
by Freek de Kruijf 18 Nov '16

18 Nov '16

I tried from http://download.opensuse.org/ports/aarch64/tumbleweed/images/ the image: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3_aarch64.aarch64-2016.06.03- Build4.1.raw.xz This one does not boot at all. Not a single message on the screen. Is there another image I should use on my RPi3? Maybe openSUSE-Tumbleweed-ARM-JeOS-efi.aarch64-2016.10.30-Build1.1.raw.xz ? I do not need any desktop on that device, just some servers. -- 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

3 2

[opensuse-arm] First boot of Leap 42.2 aarch64 image on RPI3
by Freek de Kruijf 18 Nov '16

18 Nov '16

I tried the image openSUSE-Leap42.2-ARM-JeOS- raspberrypi3_aarch64.aarch64-2016.11.09-Build3.2.raw.xz from http://download.opensuse.org/ports/aarch64/distribution/leap/42.2/appliance… on my RPi3 and found one problem. It hangs when a USB drive is connected, otherwise it works OK. -- 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

4 10

[opensuse-arm] Leap 42.2
by Bill Merriam 16 Nov '16

16 Nov '16

Leap 42.2 has been released (yeah!) and there are repositories for armv7 and aarch64 (YEAH!). Does anybody know if they work and if so on what machines? I notice there is an appliance for aarch64 rpi3 http://download.opensuse.org/ports/aarch64/distribution/leap/42.2-Current/a… and for a general EFI aarch64 device http://download.opensuse.org/ports/aarch64/distribution/leap/42.2-Current/a… . Also interestingly there is an ISO image http://download.opensuse.org/ports/aarch64/distribution/leap/42.2-Current/i… . Perhaps this is for the Softiron server. Does it work with something else? If I have Tumbleweed running on an ARM machine can I upgrade to Leap 42.2 with any hope of success? Bill -- 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] wlan getting new hw-address every 5 minutes on raspberry pi 3
by Jogchum Reitsma 15 Nov '16

15 Nov '16

Hi, After succeeding in getting wifi enabled on the pi 3 (see my previous posting 6th of nov., 20:31 WET, and follow ups) the next problem arises: every 5 minutes the wifi connection gets another hw-address, and hence another ip address... Rather inconvenient. Dmesg spits out the following: [ 1306.573949] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1306.576314] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 1306.576327] cfg80211: World regulatory domain updated: [ 1306.576341] cfg80211: DFS Master region: unset [ 1306.576341] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 1306.576347] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 1306.576352] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1306.576355] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 1306.576359] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1306.576362] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 1306.576366] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 1306.576370] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 1306.576373] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 1307.277503] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 1622.583086] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1622.585585] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 1622.585603] cfg80211: World regulatory domain updated: [ 1622.585611] cfg80211: DFS Master region: unset [ 1622.585611] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 1622.585618] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 1622.585623] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1622.585626] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 1622.585630] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1622.585634] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 1622.585637] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 1622.585641] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 1622.585644] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 1623.287611] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 1938.580273] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1938.587515] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 1938.587571] cfg80211: World regulatory domain updated: [ 1938.587604] cfg80211: DFS Master region: unset [ 1938.587604] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 1938.587617] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 1938.587633] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1938.587654] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 1938.587666] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1938.587676] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 1938.587687] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 1938.587694] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 1938.587705] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 1939.294771] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 2083.905735] fuse init (API version 7.23) [ 2254.629486] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2254.631800] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 2254.631815] cfg80211: World regulatory domain updated: [ 2254.631823] cfg80211: DFS Master region: unset [ 2254.631823] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 2254.631828] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 2254.631833] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 2254.631836] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 2254.631840] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 2254.631844] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 2254.631847] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 2254.631850] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 2254.631853] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 2255.303333] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready ================================================================ ever going. What is going on here, and what can be done? Of course I did some googling, but I didn't find anything alike... Regards, Jogchum -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 12

[opensuse-arm] raspberry pi 3 D-state hung
by Matwey V. Kornilov 15 Nov '16

15 Nov '16

Hello, I am running 4.4.24-4-default from devel:ARM:Factory:Contrib:RaspberryPi3 and sometimes see the following when do readings from /sys like # cat /sys/devices/system/cpu/cpu?/cpufreq/cpuinfo_cur_freq [ 9138.093049] INFO: task cat:4444 blocked for more than 50 seconds. [ 9138.093058] Not tainted 4.4.24-4-default #1 [ 9138.093060] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 9138.093073] cat D ffff800000086c28 0 4444 4426 0x00000001 [ 9138.093076] Call trace: [ 9138.093090] [<ffff800000086c28>] __switch_to+0x90/0xa8 [ 9138.093097] [<ffff800000749d14>] __schedule+0x234/0x758 [ 9138.093100] [<ffff80000074a278>] schedule+0x40/0xa0 [ 9138.093105] [<ffff80000074d25c>] schedule_timeout+0x214/0x280 [ 9138.093109] [<ffff80000074ae8c>] wait_for_common+0xb4/0x168 [ 9138.093113] [<ffff80000074af68>] wait_for_completion+0x28/0x38 [ 9138.093119] [<ffff8000005dd6f0>] rpi_firmware_property_list+0x120/0x280 [ 9138.093122] [<ffff8000005dd8d0>] rpi_firmware_property+0x80/0xc8 [ 9138.093133] [<ffff7ffffc115088>] bcm2835_cpufreq_get_clock+0x38/0x88 [bcm2835_cpufreq] [ 9138.093138] [<ffff7ffffc1150f4>] bcm2835_cpufreq_get+0x1c/0x28 [bcm2835_cpufreq] [ 9138.093144] [<ffff8000005d1264>] __cpufreq_get+0x34/0xc8 [ 9138.093148] [<ffff8000005d3304>] show_cpuinfo_cur_freq+0x24/0x78 [ 9138.093151] [<ffff8000005d1208>] show+0x48/0x70 [ 9138.093157] [<ffff8000002cb990>] sysfs_kf_seq_show+0xc0/0x158 [ 9138.093161] [<ffff8000002c9f94>] kernfs_seq_show+0x44/0x50 [ 9138.093166] [<ffff80000026cdac>] seq_read+0x17c/0x438 [ 9138.093169] [<ffff8000002cac34>] kernfs_fop_read+0x124/0x1b0 [ 9138.093175] [<ffff800000246430>] __vfs_read+0x48/0xf8 [ 9138.093178] [<ffff800000246e38>] vfs_read+0x88/0x160 [ 9138.093182] [<ffff800000247bc4>] SyS_read+0x54/0xb0 [ 9138.093187] [<ffff800000085e04>] el0_svc_naked+0x38/0x3c So, what do you think? Is it known? Probably I just need to try kernel 4.8.6 from openSUSE:Factory:ARM? -- 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] Booting a Surface RT (Arm based) from openSUSE media
by Greg Freemyer 14 Nov '16

14 Nov '16

I need to boot a Surface RT (Arm based) from boot media so I can grab a copy of the hard drive (SSD) contents. I don't specifically need openSUSE, but it is what I know best. The contents are encrypted, but I have the decryption keys so that isn't a problem. Can anyone point me at what I need to know / do for this to happen. Thanks Greg -- Greg Freemyer -- 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] Raspberry Pi 1&2 (probably 3, too) borken due to u-boot / grub setup.
by Stefan Seyfried 13 Nov '16

13 Nov '16

Hi, after years of just ignoring openSUSE for rpi, and using yocto/openembedded, I thought I'd try it again. After all, I could even get support for it on raspi3 (which I do not yet have) ;-) It is still broken the same as when I last tried. The reason when booted normally, as almost everyone does, start.elf reads config.txt, configures the hardware according to it *and passes some customized boot parameters to the kernel*. Example (on a working yocto/OE-build, but raspbian does the same): root@raspi02:~# cat /proc/cmdline dma.dmachans=0x7f35 bcm2708_fb.fbwidth=640 bcm2708_fb.fbheight=480 bcm2708.boardrev=0xe bcm2708.serial=0x6xxxxxxx smsc95xx.macaddr=B8:27:EB:A9:00:DE bcm2708_fb.fbswap=1 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x1fa00000 vc_mem.mem_size=0x20000000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait console=tty0 now some of these are static, namely root@raspi02:~# strings /media/mmcblk0p1/start.elf|grep root= console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait but others are dynamic, and filled in by start.elf root@raspi02:~# strings /media/mmcblk0p1/start.elf|grep ^dma\\. dma.dmachans=0x%x bcm2708_fb.fbwidth=%d bcm2708_fb.fbheight=%d bcm2708.boardrev=0x%x bcm2708.serial=0x%x root@raspi02:~# strings /media/mmcblk0p1/start.elf|grep vc_mem\\. vc_mem.mem_base=0x%x vc_mem.mem_size=0x%x The worst part of this is, that the serial number and the mac address are not set. The NIC comes up with a random mac address and the raspi gets a new IP address on every boot. Not nice. So what's needed to fix this? Due to the convoluted way openSUSE does boot, the command line needs to be passed from start.elf to u-boot (easy, see below), then from u-boot to grub2-efi (here I gave up) and then in grub.cfg to the kernel. I have a patched, working u-boot-rpi2 in https://build.opensuse.org/package/show/home:seife:branches:Base:System/u-b… (this is a proof of concept patch, it exports the command line as "bootargs_orig" variable to the u-boot shell) I'm back to openembedded on the raspis for now, will check if SLES12-SP2 is really sold with this bug too, once I get my hands on an raspberrypi3 :-) have fun, seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- 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 Pi3: working system?
by Edgar Dombrowski 11 Nov '16

11 Nov '16

Hi, OpenSuse-Raspberry Pi friends. I downloaded yesterday 2 of the "latest ?" Tumbleweed versions - the armV6 and the armV7-versions and installed them on 2 sd-sticks. After installation on a Raspi 3B - Board (and although on a Raspi-2B+ board) and applying power, only te PWR-Led lights, but not the ACT-Led and no further activity indicated on the Monitor. With "Debian-Jessie" no problemindicating tht the board is working. Using gparted on my main PC, shows 3 partitions: Nbr. 2 für "/BOOT" and Nbr. 3 für "/". I tried to ask a member of the Novell-Team at the actual ELECTRONICA-Fair in Munich, but he had no answer. Any ideas to solve my problem? Thank you for your assistance Mfg Edgar Dombrowski, DJ3PU, Munich -- 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] Still no wlan on Raspberry 3
by Jogchum Reitsma 08 Nov '16

08 Nov '16

Hi, Installing the latest aarch64 XFCE image (http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras…) I still cannot get wifi to work. Is there any chance it will be available soonish? Regards, Jogchum Reitsma -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 9

[opensuse-arm] grub2 at RPi3: press t to show the boot menu
by Matwey V. Kornilov 07 Nov '16

07 Nov '16

Hello, I am running aarch64 Raspberry Pi3 image with Tumbleweed, grub2-2.02~beta3-12.1.aarch64 u-boot-rpi3-2016.07-5.1.aarch64 At booting I see the following (I use serial console and don't use graphical terminal): ## Starting EFI application at 0x01000000 ... 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! Please press t to show the boot menu on this console And nothing happens until I press 't'. And I've failed to find the setting in /etc/default/grub to disable this waiting. Could you help me? -- 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] 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

Re: [opensuse-arm] BananaPi - usb out of function
by Stefan Mack 05 Nov '16

05 Nov '16

...solved... usb works fine! the reason: Modul axp20x_i2c isn't loaded during boot. the solution: vi /etc/modules-load.d/arm.conf axp20x_i2c Regards Stefan -------- Weitergeleitete Nachricht -------- Von: Stefan Mack <mack.stefan(a)web.de> An: Andreas Färber <afaerber(a)suse.de>, opensuse-arm(a)opensuse.org Betreff: Re: [opensuse-arm] BananaPi - usb out of function Datum: Wed, 02 Nov 2016 20:04:31 +0100 Hello Andreas, I just opened a Bugzilla ticket and CC to you. I hope everything is o.k. I did. With the actual banana-image (kernel 4.8.4) it usb dosn't work either. Thanks and regards Stefan -------- Weitergeleitete Nachricht -------- Von: Stefan Mack <mack.stefan(a)web.de> An: Andreas Färber <afaerber(a)suse.de>, opensuse-arm(a)opensuse.org Betreff: Re: [opensuse-arm] BananaPi - usb out of function Datum: Mon, 24 Oct 2016 19:32:18 +0200 Hello Andreas, today I installed a fresh JeOS-bananapi-image-Tumbleweed on my banana (SD-card). The results are: bananavdr:/home/stefan # dmesg |grep usb [ 0.391001] reg-fixed-voltage usb0-vbus: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/usb0_vbus_pin@0, defe rring probe [ 0.391068] reg-fixed-voltage usb1-vbus: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/usb1_vbus_pin@0, defe rring probe [ 0.391105] reg-fixed-voltage usb2-vbus: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/usb2_vbus_pin@0, defe rring probe [ 4.618572] usb0-vbus: disabling [ 4.618581] usb1-vbus: disabling [ 4.618594] usb2-vbus: disabling [ 10.227698] usbcore: registered new interface driver usbfs [ 10.227805] usbcore: registered new interface driver hub [ 10.235037] usbcore: registered new device driver usb bananavdr:/home/stefan # lsusb bananavdr:/home/stefan # -> NOTHING bananavdr:/home/stefan # uname -a Linux bananavdr 4.7.6-1-default #1 SMP PREEMPT Fri Sep 30 12:22:14 UTC 2016 (fb37fcc) armv7l armv7l armv7l GNU/Linux The same result with kernel-lpae - no difference to the kernel-default. Where can I open a Bugzilla ticket? Is this the correct account and I need an acount? https://login.microfocus.com/nidp/idff/sso?id=132&sid=2&option=credenti al&sid=2&target=https://esp.microfocus.com/LAGBroker?%22https://bugzill a.opensuse.org/accessmanagerlogin.cgi?target=enter_bug.cgi?product%3Dop enSUSE%2520Tumbleweed%26format%3Dguided%22 Sorry for the delay and thank you very much! bananavdr:/home/stefan # lsmod | grep usb musb_hdrc 131072 1 sunxi udc_core 24576 1 musb_hdrc phy_sun4i_usb 16384 1 sunxi extcon 24576 2 sunxi,phy_sun4i_usb usbcore 253952 5 musb_hdrc,ohci_platform,ohci_hcd,ehci_hcd,ehci_platform usb_common 16384 4 sunxi,musb_hdrc,udc_core,usbcore Regards Stefan -------- Weitergeleitete Nachricht -------- Von: Andreas Färber <afaerber(a)suse.de> An: Stefan Mack <mack.stefan(a)web.de>, opensuse-arm(a)opensuse.org Betreff: Re: [opensuse-arm] BananaPi - usb out of function Datum: Sat, 15 Oct 2016 18:17:46 +0200 Hi Stefan, Am 10.10.2016 um 18:59 schrieb Stefan Mack: > I have an original Banana Pi and I'm using the JeOS-bananapi-image > from > the link you've posted. > > Network and sata are working fine. After the boot I log in per ssh > and > can copy the sd-image to the ssd. All is fine except usb. > I use the original power-in and not the OTG. > > Only keyboard, mouse or usb sticks aren't recogniced in the log and > don't work. > > Is the log enough? Unfortunately no. I understood you boot from SD, can login via ssh and then USB doesn't work in the SD-booted running system? Nothing to do with the SSD yet? If that is the case, please do open a Bugzilla ticket and CC me on it, so that we can track this. The full dmesg including kernel version and command line as well as lsusb output would be useful as a start. On my A20 based Cubietruck with kernel-lpae 4.8.0 it looks like this: andreas@lastwagen:~> dmesg | grep usb [ 0.695769] reg-fixed-voltage usb0-vbus: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/usb0_vbus_pin@0, deferring probe [ 0.695808] reg-fixed-voltage usb1-vbus: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/usb1_vbus_pin@0, deferring probe [ 0.695843] reg-fixed-voltage usb2-vbus: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/usb2_vbus_pin@0, deferring probe [ 7.215472] usb0-vbus: disabling [ 7.218702] usb1-vbus: disabling [ 7.221930] usb2-vbus: disabling [ 10.404986] usbcore: registered new interface driver usbfs [ 10.410634] usbcore: registered new interface driver hub [ 10.424817] usbcore: registered new device driver usb [ 28.772266] ohci-platform 1c14400.usb: Generic Platform OHCI controller [ 28.854799] ohci-platform 1c14400.usb: new USB bus registered, assigned bus number 1 [ 28.948835] ohci-platform 1c14400.usb: irq 31, io mem 0x01c14400 [...] andreas@lastwagen:~> lsusb Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The connected USB UART adapter (third line) works just fine. kernel-lpae 4.7.6 or 4.7.4 worked equally well last time I checked. I note that the bananapi image uses kernel-default. Have you tried installing kernel-lpae and rebooting? Regards, Andreas -- 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] openSUSE Leap 42.2 on BeagleBone Black
by Matwey V. Kornilov 04 Nov '16

04 Nov '16

Hello, I've just booted Leap 42.2 on BBB: http://download.opensuse.org/repositories/home:/matwey:/experimental:/Leap:… Join the party! -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 8

[opensuse-arm] Last known working version of Raspberry Pi 2 Tumbleweed image
by Jimmy PIERRE 03 Nov '16

03 Nov '16

Greetings, I am preparing our next Software Freedom Day and has lost track of the working image for RPi 2 / RPi 3. Won't have time to test with Leap 42.2 and SLE 12 SP2 as well, would need a "plug and play" image :) Cheers, Jimmy nui.fr -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

Re: [opensuse-arm] BananaPi - usb out of function
by Stefan Mack 02 Nov '16

02 Nov '16

Hello Andreas, I just opened a Bugzilla ticket and CC to you. I hope everything is o.k. I did. With the actual banana-image (kernel 4.8.4) it usb dosn't work either. Thanks and regards Stefan -------- Weitergeleitete Nachricht -------- Von: Stefan Mack <mack.stefan(a)web.de> An: Andreas Färber <afaerber(a)suse.de>, opensuse-arm(a)opensuse.org Betreff: Re: [opensuse-arm] BananaPi - usb out of function Datum: Mon, 24 Oct 2016 19:32:18 +0200 Hello Andreas, today I installed a fresh JeOS-bananapi-image-Tumbleweed on my banana (SD-card). The results are: bananavdr:/home/stefan # dmesg |grep usb [ 0.391001] reg-fixed-voltage usb0-vbus: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/usb0_vbus_pin@0, defe rring probe [ 0.391068] reg-fixed-voltage usb1-vbus: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/usb1_vbus_pin@0, defe rring probe [ 0.391105] reg-fixed-voltage usb2-vbus: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/usb2_vbus_pin@0, defe rring probe [ 4.618572] usb0-vbus: disabling [ 4.618581] usb1-vbus: disabling [ 4.618594] usb2-vbus: disabling [ 10.227698] usbcore: registered new interface driver usbfs [ 10.227805] usbcore: registered new interface driver hub [ 10.235037] usbcore: registered new device driver usb bananavdr:/home/stefan # lsusb bananavdr:/home/stefan # -> NOTHING bananavdr:/home/stefan # uname -a Linux bananavdr 4.7.6-1-default #1 SMP PREEMPT Fri Sep 30 12:22:14 UTC 2016 (fb37fcc) armv7l armv7l armv7l GNU/Linux The same result with kernel-lpae - no difference to the kernel-default. Where can I open a Bugzilla ticket? Is this the correct account and I need an acount? https://login.microfocus.com/nidp/idff/sso?id=132&sid=2&option=credenti al&sid=2&target=https://esp.microfocus.com/LAGBroker?%22https://bugzill a.opensuse.org/accessmanagerlogin.cgi?target=enter_bug.cgi?product%3Dop enSUSE%2520Tumbleweed%26format%3Dguided%22 Sorry for the delay and thank you very much! bananavdr:/home/stefan # lsmod | grep usb musb_hdrc 131072 1 sunxi udc_core 24576 1 musb_hdrc phy_sun4i_usb 16384 1 sunxi extcon 24576 2 sunxi,phy_sun4i_usb usbcore 253952 5 musb_hdrc,ohci_platform,ohci_hcd,ehci_hcd,ehci_platform usb_common 16384 4 sunxi,musb_hdrc,udc_core,usbcore Regards Stefan -------- Weitergeleitete Nachricht -------- Von: Andreas Färber <afaerber(a)suse.de> An: Stefan Mack <mack.stefan(a)web.de>, opensuse-arm(a)opensuse.org Betreff: Re: [opensuse-arm] BananaPi - usb out of function Datum: Sat, 15 Oct 2016 18:17:46 +0200 Hi Stefan, Am 10.10.2016 um 18:59 schrieb Stefan Mack: > I have an original Banana Pi and I'm using the JeOS-bananapi-image > from > the link you've posted. > > Network and sata are working fine. After the boot I log in per ssh > and > can copy the sd-image to the ssd. All is fine except usb. > I use the original power-in and not the OTG. > > Only keyboard, mouse or usb sticks aren't recogniced in the log and > don't work. > > Is the log enough? Unfortunately no. I understood you boot from SD, can login via ssh and then USB doesn't work in the SD-booted running system? Nothing to do with the SSD yet? If that is the case, please do open a Bugzilla ticket and CC me on it, so that we can track this. The full dmesg including kernel version and command line as well as lsusb output would be useful as a start. On my A20 based Cubietruck with kernel-lpae 4.8.0 it looks like this: andreas@lastwagen:~> dmesg | grep usb [ 0.695769] reg-fixed-voltage usb0-vbus: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/usb0_vbus_pin@0, deferring probe [ 0.695808] reg-fixed-voltage usb1-vbus: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/usb1_vbus_pin@0, deferring probe [ 0.695843] reg-fixed-voltage usb2-vbus: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/usb2_vbus_pin@0, deferring probe [ 7.215472] usb0-vbus: disabling [ 7.218702] usb1-vbus: disabling [ 7.221930] usb2-vbus: disabling [ 10.404986] usbcore: registered new interface driver usbfs [ 10.410634] usbcore: registered new interface driver hub [ 10.424817] usbcore: registered new device driver usb [ 28.772266] ohci-platform 1c14400.usb: Generic Platform OHCI controller [ 28.854799] ohci-platform 1c14400.usb: new USB bus registered, assigned bus number 1 [ 28.948835] ohci-platform 1c14400.usb: irq 31, io mem 0x01c14400 [...] andreas@lastwagen:~> lsusb Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The connected USB UART adapter (third line) works just fine. kernel-lpae 4.7.6 or 4.7.4 worked equally well last time I checked. I note that the bananapi image uses kernel-default. Have you tried installing kernel-lpae and rebooting? Regards, Andreas -- 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] ANN: Raspberry Pi 2 Tumbleweed image
by Andreas Färber 31 Oct '16

31 Oct '16

Hello, Last weekend already the 4.8 kernel landed in Factory. Since then we have a usable JeOS-raspberrypi2 image in openSUSE:Factory:ARM. https://build.opensuse.org/package/show/openSUSE:Factory:ARM/JeOS-raspberry… These images have not been published yet, so you will need to download them from OBS (build.opensuse.org) rather than download.opensuse.org. For that reason the Wiki couldn't be updated with new instructions yet. https://en.opensuse.org/HCL:Raspberry_Pi2 Known issues: * The GRUB menu is only shown on HDMI, not on serial. Workaround: Attach a monitor for the first boot, then edit /etc/default/grub replacing GRUB_TERMINAL="gfxterm" with GRUB_TERMINAL="console" and run `update-bootloader` (or `grub2-mkconfig -o /boot/grub2/grub.cfg`). * Downstream kernels booted through GRUB might get a random MAC address. Workaround: edit GRUB menu entry or create a boot.scr script. The old images in devel:ARM:Factory:Contrib:RaspberryPi2 and :Staging will stay around for now, but you are encouraged to use the official image for new installations and, if needed, install only kernel-rpi2 and dtb-bcm2709 packages from the Contrib projects. Therefore please report success or problems with the new raspberrypi2 image. Thanks. Have a lot of fun, Andreas P.S. The 4.8 arm64 kernel has been tested to work on the Raspberry Pi 3 but U-Boot is looking for the .dtb file in the wrong place, breaking automatic boot. Therefore no official image yet. Workaround: symlink or `load mmc 0:2 $fdt_addr_r boot/dtb/broadcom/$fdtfile; boot` -- 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] bcm43xx-firmware not symlinked in RPi3 32 bits
by Guillaume Gardet 26 Oct '16

26 Oct '16

Hi, WiFi does not work out of the box on JeOS-raspberrypi3 armv7l image (downstream 32 bits) because: cat /sys/firmware/devicetree/base/compatible returns: brcm,bcm2710brcm,bcm2709 and not: *raspberrypi,3-model-b* But: cat /sys/firmware/devicetree/base/model returns: Raspberry Pi 3 Model B Could we add this case in bcm43xx-firmware script? Note that JeOS raspberry pi 3 (AArch64 contrib) has no WiFi, probably because of the following error: brcmfmac_sdio: probe of mmc1:0001:1 failed with error -110 brcmfmac_sdio: probe of mmc1:0001:2 failed with error -110 whereas mmc1 seems to be ok: [ 3.109301] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) [ 3.111430] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 3.113282] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 3.120140] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) [ 3.339697] random: nonblocking pool is initialized [ 3.357090] mmc1: new SDIO card at address 0001 Any idea why it happens? Guillaume -- 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] Factory:ARM dtb rebuild
by Guillaume Gardet 25 Oct '16

25 Oct '16

Hi, Could you trigger a rebuild of DTB packages in Factory:ARM, because dtb are still in 4.7.5 whereas kernel is at 4.8.*. Guillaume -- 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] BananaPi - usb out of function
by Stefan Mack 24 Oct '16

24 Oct '16

Hello all, usb is out of function on my bananapi with Tmbleweed. After boot up the USB power seems to be turned off. I found two links: http://lists.infradead.org/pipermail/linux-arm-kernel/2015-December/395 232.html https://patchwork.kernel.org/patch/7927841/ "With a new kernel, the kernel will turn off the USB power supply during boot by default if the driver isn't present." Can anybody help me with the patch? Which file I have to patch? After this I have to compile the kernel? Am I the only one with Banana and Opensuse? Thanks a lot Stefan Sorry for my bad English, I'm still learning... -- 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] Raspberry Pi 3 AArch64 DTB
by Guillaume Gardet 18 Oct '16

18 Oct '16

Hi, On devel:ARM:Factory:Contrib:RaspberryPi3 project, there are currently 2 DTB packages: * dtb-aarch64 : compiled broadcom DTBs from sources and output a bcm2837-rpi-3-b.dtb file too. * dtb-rpi3-aarch64 : pre-compiled bcm2837-rpi-3-b.dtb (from where?) Current JeOS uses the pre-compiled DT. WiFi is not working on AArch64 version, and I am wondering if it could be caused by the DTB used. Alex, Andreas, any idea? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 34

[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