February 2016 - openSUSE ARM - openSUSE Mailing Lists

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

12 Apr '17

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

3 3

[opensuse-arm] RPi2, Tumbleweed and "official" 7" RPi touchscreen
by Robert Kaiser 26 Mar '16

26 Mar '16

Hi, I've had one RPi2 running headless with Tumbleweed for quite some time now, and it does fine, so thanks everyone for making that work! That said, I now have acquired the "official" RPi 7" touchscreen to use with a second RPi2, and it actually displays the text console nicely on first boot of the Build 385 JeOS image, but on second boot it stays completely black (not even the backlight is on). In addition, the network interface also does not come up (same as on first boot), so the build gets completely unusable for me. I tried the old build 307 that I had used initially to get the other RPi2 up months ago, and the screen is completely black with that, but the network is fine and I could update it to a current Tumbleweed, which it still boots fine and is accessible from the network. That said, the screen stays dark on this as well. Given that the first boot with build 385 works and AFAIK uses the same kernel and probably bootloader, and the difference is there right from booting the system, it feels like it can't be that hard to get it working in the end. That said, the difference has to be in some parameters or things available during boot. I attached two dmesg outputs, one ("noscreen") from the updated-to-current system that can be accessed remotely, one ("screenworking") from a build 385 first boot. One difference that strikes me there is that the non-working version says (omitting times): simple-framebuffer 3db79000.framebuffer: framebuffer at 0x3db79000, 0x81800 bytes, mapped to 0xb7d00000 simple-framebuffer 3db79000.framebuffer: format=r5g6b5, mode=592x448x16, linelength=1184 simple-framebuffer 3db79000.framebuffer: fb1: simplefb registered! The working version has the following instead: simple-framebuffer fdb3f000.framebuffer: framebuffer at 0xfdb3f000, 0xbb800 bytes, mapped to 0xb7d00000 simple-framebuffer fdb3f000.framebuffer: format=r5g6b5, mode=800x480x16, linelength=1600 simple-framebuffer fdb3f000.framebuffer: fb1: simplefb registered! The "mode=800x480x16" actually fits this screen correctly. Any idea what I can try to get it working? I have found out enough to play with kernel command line parameters by editing boot.script and regenerating boot.scr from it, but I got stuck there as removing this from the commandline didn't help and I'm not sure what else I can do there that may help. That said, once the display actually shows stuff, the second question will be the touch input - if the rpi-ft5406 driver available in the kernel right now? I saw there are sources for it in https://github.com/raspberrypi/linux/blob/rpi-4.5.y/drivers/input/touchscre… at least for 4.5, not sure for how far back they exist/work. Thanks, KaiRo

3 5

[opensuse-arm] Which ARMv8 board to choose?
by Guillaume Gardet 14 Mar '16

14 Mar '16

Hi, I would like to purchase an (affordable) armv8 board but I do not know which one. Could you give me some hints, please? I found the HiKey: https://www.96boards.org/products/ce/hikey/ which is $75 (or $99 in 2GB RAM version), plus shipping. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 6

[opensuse-arm] RPi2, Tumbleweed and "official" 7" RPi touchscreen
by Michael Emory Cerquoni 11 Mar '16

11 Mar '16

I have been trying for a year or so to get this working correctly with absolutely zero luck, and so far have not found any way to get the GPU working correctly for the opensuse-arm Raspberry Pi2 images, it uses an ancient kernel (3.18) and no one seems interested in updating and making sure things work properly, i would suggest if you really need this you switch to Raspbian or Ubuntu Mate, you will have considerably better luck and much better community support, I hate to sound negative and really I am not happy about having to recommend you use a different operating system, but chances are you will not be able to get opensuse working very well, there seems to be very little interest in making this hardware work correctly on opensuse. -- Michael Emory Cerquoni -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

10 30

[opensuse-arm] opensuse on odroid u3?
by Dieter Thalmayr 04 Mar '16

04 Mar '16

Hi there, Guillaume Gardet helped me to get an odroid u3 running with a SUSE anything younger than a 12.3. Actually, we used an image that can be found at http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Odr… That image is "factory". We had many issues with the uboot bootloader, but after months and close to one dozen tries the bootloader boots the kernel. But then: ----snip ---- U-Boot 2016.01 (Jan 25 2016 - 22:47:58 +0000) CPU: Exynos4412 @ 1 GHz Model: Odroid based on Exynos4412 Board: Odroid based on Exynos4412 Type: u3 DRAM: 2 GiB LDO20(a)VDDQ_EMMC_1.8V: set 1800000 uV; enabling LDO22(a)VDDQ_EMMC_2.8V: set 2800000 uV; enabling LDO21(a)TFLASH_2.8V: set 2800000 uV; enabling MMC: SAMSUNG SDHCI: 0, EXYNOS DWMMC: 1 *** Warning - bad CRC, using default environment Net: No ethernet found. Hit any key to stop autoboot: 0 2721 bytes read in 135 ms (19.5 KiB/s) ## Executing script at 42000000 autoboot=if test -e mmc 0 boot.scr; then; run boot_script; elif test -e mmc 0 I; baudrate=115200 boardname=odroidu3 boot_fit=setenv kerneladdr 0x42000000;setenv kernelname Image.itb;run loadkerne} boot_script=run loadbootscript;source ${scriptaddr} boot_uimg=setenv kerneladdr 0x40007FC0;setenv kernelname uImage;run check_dtb;r; boot_zimg=setenv kerneladdr 0x40007FC0;setenv kernelname zImage;run check_dtb;r; bootargs=Please use defined boot bootcmd=run autoboot bootdelay=0 check_dtb=if run loaddtb; then setenv fdt_addr ${fdtaddr};else setenv fdt_addr;; check_ramdisk=if run loadinitrd; then setenv initrd_addr ${initrdaddr};else set; console=console=ttySAC1,115200n8 consoleoff=set console console=ram; save; reset consoleon=set console console=ttySAC1,115200n8; save; reset dfu_alt_info=Please reset the board dfu_alt_system=uImage fat 0 1;zImage fat 0 1;Image.itb fat 0 1;uInitrd fat 0 1;2 fdtaddr=40800000 fdtcontroladdr=bae47f70 fdtfile=exynos4412-odroidu3.dtb fileaddr=42000000 filesize=aa1 initrdaddr=42000000 initrdname=uInitrd kernel_args=setenv bootargs root=/dev/mmcblk${mmcrootdev}p${mmcrootpart} rootwa} loadbootscript=load mmc ${mmcbootdev}:${mmcbootpart} ${scriptaddr} boot.scr loaddtb=load mmc ${mmcbootdev}:${mmcbootpart} ${fdtaddr} ${fdtfile} loadinitrd=load mmc ${mmcbootdev}:${mmcbootpart} ${initrdaddr} ${initrdname} loadkernel=load mmc ${mmcbootdev}:${mmcbootpart} ${kerneladdr} ${kernelname} mmcbootdev=0 mmcbootpart=1 mmcrootdev=0 mmcrootpart=2 scriptaddr=0x42000000 soc_id=4412 soc_rev=2.0 Environment size: 2090/4092 bytes switch to partitions #0, OK mmc0 is current device 7420680 bytes read in 4206 ms (1.7 MiB/s) 68337422 bytes read in 31408 ms (2.1 MiB/s) 53476 bytes read in 464 ms (112.3 KiB/s) Kernel image @ 0x40007fc0 [ 0x000000 - 0x713b08 ] ## Loading init Ramdisk from Legacy Image at 44007fc0 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 68337358 Bytes = 65.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43f07fc0 Booting using the fdt blob at 0x43f07fc0 Using Device Tree in place at 43f07fc0, end 43f180a3 Starting kernel ... --- snap --- and afterwards only the sad sound of the ventilator. Does anybody have an idea what goes wrong? What can I do to get more information Plus, I would be very interested in building an image on my own. Is there somewhere a howto that can help me with the first steps? Although I have to admit that I am only a high-hearted amateur if it comes down to real technics.. Greetings Dieter -- magnum opus GmbH Tel: 08441/ 7978 107 Eichendorffstr. 19a Fax: 08441/ 7977 114 D-85276 Pfaffenhofen/Ilm http://www.magnum-opus.de GF: Dieter Thalmayr, Dieter Jäger RG: Neuburg / Donau · HRB 91.238 Ust-IdNr DE227355001 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

8 14

[opensuse-arm] Newest image for Raspberry Pi 1 looks promising
by Freek de Kruijf 02 Mar '16

02 Mar '16

Finished testing the newest image openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build377.2.raw.xz from http://download.opensuse.org/ports/armv6hl/tumbleweed/images/ for Raspberry Pi 1B This image is much smaller than its predecessor: 160 MiB versus 230 MiB. I test it with a HDMI device connected, so I can see the messages. First it shows the u-boot messages, shows for a short while Tux and shows a black screen for quite a while. Apparently during this time the SD card is changed to have a swap partition at the end and the ROOT partition is enlarged to cover the remaining space on the SD card. After that it shows a number of messages typical ones one see during boot. There is an an error message about being not able to mount /boot/efi The system ends in an emergency state. After power down and up it does not boot anymore but it looks the system is trying to boot via the network. One of the last messages is that one should run "journalct -xb" to see what went wrong. I mounted the SD card, or rather the ROOT partition, on my desktop and started the command "journalctl -D <path-to-/var/log/journal-on-ROOT> -xb" which showed me the messages. Most likely the problem is the mounting of /boot/vfat; the error message reports: mount[5289]: mount: unknown filesystem type 'vfat', so apparently there is a missing module in the kernel. -- 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

5 8

[opensuse-arm] armv7 images broken: Initramfs unpacking failed: write error
by Guillaume Gardet 01 Mar '16

01 Mar '16

Hi, ARMv7 images are broken. On boot, with latest build (kernel 4.4.0-3-default) I get the following error: "Initramfs unpacking failed: write error". Full kernel log (for beaglebone black): ******************************************************** Starting kernel ... [ 0.000530] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0' [ 0.000538] This ensures that you still see kernel messages. Please [ 0.000545] update your kernel commandline. [ 5.154972] Initramfs unpacking failed: write error [ 5.351054] omap_voltage_late_init: Voltage driver support not added [ 5.357567] sr_dev_init: No voltage domain specified for smartreflex0. Cannot initialize [ 5.365720] sr_dev_init: No voltage domain specified for smartreflex1. Cannot initialize [ 5.563828] sr_init: platform driver register failed for SR [ 5.575720] Unable to find PPMU node [ 5.586412] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 [ 5.586412] [ 5.595610] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-3-default #1 [ 5.601901] Hardware name: Generic AM33XX (Flattened Device Tree) [ 5.608068] [<c022876c>] (unwind_backtrace) from [<c0221904>] (show_stack+0x20/0x28) [ 5.615856] [<c0221904>] (show_stack) from [<c0575ee8>] (dump_stack+0x9c/0xdc) [ 5.623125] [<c0575ee8>] (dump_stack) from [<c03803c0>] (panic+0xb0/0x248) [ 5.630039] [<c03803c0>] (panic) from [<c0274e54>] (complete_and_exit+0x0/0x2c) [ 5.637383] [<c0274e54>] (complete_and_exit) from [<c0274eec>] (do_group_exit+0x4c/0xcc) [ 5.645510] [<c0274eec>] (do_group_exit) from [<c0274f8c>] (__wake_up_parent+0x0/0x34) [ 5.653464] [<c0274f8c>] (__wake_up_parent) from [<c021ce60>] (ret_fast_syscall+0x0/0x34) [ 5.661690] Rebooting in 90 seconds.. ******************************************************** Note that there is no early message (except warning on console, for which I will send a JeOS SR). Any idea what is wrong? Any kernel config update related to initramfs? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

9 33

[opensuse-arm] Raspberry Pi 3 - 64-bit
by Guillaume Gardet 29 Feb '16

29 Feb '16

Hi, I just noticed that there is a new raspberry pi. See: https://www.raspberrypi.org/blog/raspberry-pi-3-on-sale/ It is a quad-core Cortex A53 (64-bit). Probably not EFI compatible. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 5

Re: Re : Re: [opensuse-arm] Re: armv7 images broken: Initramfs unpacking failed: write error
by Dirk Müller 21 Feb '16

21 Feb '16

2016-02-21 10:45 GMT+01:00 <guillaume.gardet(a)free.fr>: > Thanks for taking care of this problem. I'm down to 32MB now, which seems okayish for a few hours of hacking. Next problem I noticed that we have enabled "CMA" in our kernel config for arm (it is disabled on other architectures), which seems to take away quite some memory for unpacking the kiwi initrd. with artificially lowering the memory to Raspberry Pi 1 levels I can run out of memory while unpacking initrd, which is bad. Any objection to disabling that ? I couldn't quite figure out why we want it to be enabled, as usual the git commit messages that enabled it are sparse :( Greetings, Dirk -- 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] First attempt to check ARM image
by Jimmy PIERRE 21 Feb '16

21 Feb '16

Hi, I have a program that moniyors this directory and it tells me tthat a few things have changed. Having a Raspberry PI 2: Index of /repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi2/images Icon Name Last modified Size -------------------------------------------------------------------------------- [DIR] Parent Directory - [ ] openSUSE-Tumbleweed-ARM-E17-raspberrypi2.armv7l-1.12.1-Build372.1.packages 04-Feb-2016 02:43 155K Details [ ] openSUSE-Tumbleweed-ARM-E17-raspberrypi2.armv7l-1.12.1-Build372.1.raw.xz 04-Feb-2016 02:43 650M Details [ ] openSUSE-Tumbleweed-ARM-E17-raspberrypi2.armv7l.raw.xz 04-Feb-2016 02:43 650M Details [ ] openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-1.12.1-Build372.1.packages 04-Feb-2016 08:06 41K Details [ ] openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-1.12.1-Build372.1.raw.xz 04-Feb-2016 08:06 238M Details [ ] openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l.raw.xz 04-Feb-2016 08:06 238M Details [ ] openSUSE-Tumbleweed-ARM-LXQT-raspberrypi2.armv7l-1.12.1-Build372.2.packages 04-Feb-2016 17:58 160K Details [ ] openSUSE-Tumbleweed-ARM-LXQT-raspberrypi2.armv7l-1.12.1-Build372.2.raw.xz 04-Feb-2016 17:58 617M Details [ ] openSUSE-Tumbleweed-ARM-LXQT-raspberrypi2.armv7l.raw.xz 04-Feb-2016 17:58 617M Details [ ] openSUSE-Tumbleweed-ARM-XFCE-raspberrypi2.armv7l-1.12.1-Build370.3.packages 02-Feb-2016 19:27 183K Details [ ] openSUSE-Tumbleweed-ARM-XFCE-raspberrypi2.armv7l-1.12.1-Build370.3.raw.xz 02-Feb-2016 19:27 632M Details [ ] openSUSE-Tumbleweed-ARM-XFCE-raspberrypi2.armv7l.raw.xz 02-Feb-2016 19:27 632M Details -------------------------------------------------------------------------------- Please advise which one you want checked first, then second etc. Cheers, Jimmy -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

6 11

[opensuse-arm] kpartx hangs in armv6 images builds
by Guillaume Gardet 20 Feb '16

20 Feb '16

Hi, All armv6l (raspberry pi) images hang after a call to kpartx. See: https://build.opensuse.org/package/live_build_log/devel:ARM:Factory:Contrib… Local (chroot) build is ok, so I guess this is a qemu problem? Any idea how to fix that ? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

9 33

[opensuse-arm] Factory u-boot-am335x: ### ERROR ### Please RESET the board ###
by Matwey V. Kornilov 17 Feb '16

17 Feb '16

Hello, I am trying to boot from openSUSE-Tumbleweed-ARM-JeOS-beaglebone.armv7l-1.12.1-Build375.1.raw and I see the following: U-Boot SPL 2016.01 (Feb 09 2016 - 16:10:32) Trying to boot from MMC bad magic bad magic SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### -- 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] Root device not found
by Oscar C 16 Feb '16

16 Feb '16

Hi, I'm trying to boot my udoo quad board (imx6) but it fails because the root device is not found: [1454973205.868008] Searching for boot device... [1454973205.922481] Waiting for device /dev/mmcblk0p2 to settle... [1454973207.943315] Waiting for device /dev/mmcblk0p2 to settle... [1454973209.964210] Waiting for device /dev/mmcblk0p2 to settle... [1454973211.985181] Waiting for device /dev/mmcblk0p2 to settle... [1454973214.005732] Waiting for device /dev/mmcblk0p2 to settle... [1454973216.026237] Waiting for device /dev/mmcblk0p2 to settle... [1454973218.047048] Waiting for device /dev/mmcblk0p2 to settle... [1454973220.067520] Waiting for device /dev/mmcblk0p2 to settle... [1454973266.552193] Specified root device /dev/mmcblk0p2 not found. Found devices: [1454973267.286059] root device not found... fatal ! Looking at the full log I see that the problem may be that the mmc module is not loaded. I unpacked the initram and there are some modules, but I don't know which one is for the imx6 platform: mmc/card: total 80 -rw-r--r-- 1 oscar users 51882 feb 10 00:31 mmc_block.ko -rw-r--r-- 1 oscar users 25090 feb 10 00:31 sdio_uart.ko mmc/core: total 192 -rw-r--r-- 1 oscar users 195402 feb 10 00:31 mmc_core.ko mmc/host: total 848 -rw-r--r-- 1 oscar users 13766 feb 10 00:31 dw_mmc-exynos.ko -rw-r--r-- 1 oscar users 10746 feb 10 00:31 dw_mmc-k3.ko -rw-r--r-- 1 oscar users 47662 feb 10 00:31 dw_mmc.ko -rw-r--r-- 1 oscar users 9662 feb 10 00:31 dw_mmc-pltfm.ko -rw-r--r-- 1 oscar users 12670 feb 10 00:31 dw_mmc-rockchip.ko -rw-r--r-- 1 oscar users 31746 feb 10 00:31 mmci.ko -rw-r--r-- 1 oscar users 4338 feb 10 00:31 mmci_qcom_dml.ko -rw-r--r-- 1 oscar users 32278 feb 10 00:31 mtk-sd.ko -rw-r--r-- 1 oscar users 23894 feb 10 00:31 mvsdio.ko -rw-r--r-- 1 oscar users 25982 feb 10 00:31 mxcmmc.ko -rw-r--r-- 1 oscar users 41634 feb 10 00:31 omap_hsmmc.ko -rw-r--r-- 1 oscar users 29522 feb 10 00:31 omap.ko -rw-r--r-- 1 oscar users 33522 feb 10 00:31 rtsx_usb_sdmmc.ko -rw-r--r-- 1 oscar users 13990 feb 10 00:31 sdhci-bcm-kona.ko -rw-r--r-- 1 oscar users 8046 feb 10 00:31 sdhci-dove.ko -rw-r--r-- 1 oscar users 25314 feb 10 00:31 sdhci-esdhc-imx.ko -rw-r--r-- 1 oscar users 11086 feb 10 00:31 sdhci_f_sdh30.ko -rw-r--r-- 1 oscar users 11574 feb 10 00:31 sdhci-iproc.ko -rw-r--r-- 1 oscar users 63518 feb 10 00:31 sdhci.ko -rw-r--r-- 1 oscar users 14966 feb 10 00:31 sdhci-msm.ko -rw-r--r-- 1 oscar users 10978 feb 10 00:31 sdhci-of-arasan.ko -rw-r--r-- 1 oscar users 10030 feb 10 00:31 sdhci-of-at91.ko -rw-r--r-- 1 oscar users 15682 feb 10 00:31 sdhci-of-esdhc.ko -rw-r--r-- 1 oscar users 13890 feb 10 00:31 sdhci-pltfm.ko -rw-r--r-- 1 oscar users 18354 feb 10 00:31 sdhci-s3c.ko -rw-r--r-- 1 oscar users 11770 feb 10 00:31 sdhci-spear.ko -rw-r--r-- 1 oscar users 13054 feb 10 00:31 sdhci-st.ko -rw-r--r-- 1 oscar users 11382 feb 10 00:31 sdhci-tegra.ko -rw-r--r-- 1 oscar users 35430 feb 10 00:31 sh_mmcif.ko -rw-r--r-- 1 oscar users 15674 feb 10 00:31 sh_mobile_sdhi.ko -rw-r--r-- 1 oscar users 23906 feb 10 00:31 sunxi-mmc.ko -rw-r--r-- 1 oscar users 38210 feb 10 00:31 tmio_mmc_core.ko -rw-r--r-- 1 oscar users 7730 feb 10 00:31 tmio_mmc.ko -rw-r--r-- 1 oscar users 35670 feb 10 00:31 usdhi6rol0.ko -rw-r--r-- 1 oscar users 12182 feb 10 00:31 ushc.ko -rw-r--r-- 1 oscar users 43886 feb 10 00:31 vub300.ko -rw-r--r-- 1 oscar users 18750 feb 10 00:31 wmt-sdmmc.ko Can I set a debug flag or something to see why the modules are not being loading? Thanks! -- Oscar -- 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] New package: sunxi-tools
by Andreas Färber 15 Feb '16

15 Feb '16

Hello, In my ongoing quest to clean up our ARM packages I have submitted the sunxi-tools package from devel:ARM:Factory:Contrib:sunxi to hardware project and am proposing its inclusion in Factory. https://build.opensuse.org/request/show/359205 Among others, its tools are used for (de)compiling Allwinner script.bin files (a predecessor/alternative to FDT files) or for booting via USB. 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

1 2

[opensuse-arm] Tumbleweed for AArch64 being converted to OpenQA publishing
by Dirk Müller 12 Feb '16

12 Feb '16

Hi, Over the last couple of months, a couple of contributors have been working on enabling openQA for aarch64, and the current state looks good enough for a start. To learn more about openQA , visit http://os-autoinst.github.io/openQA/ (there is also openqa.org which is however completely unrelated). So far, publishing and testing of Tumbleweed for ARM (aarch64) was happening completely independent. It is however better if the automated testing result is used to decide whether or not the current snapshot will be published to end users. As recently of bigger changes have entered tumbleweed (https://news.opensuse.org/2016/02/10/systemd-updates-ambitious-yast-changes…), it seems now is a good timing to switch to a tested publishing method. This means from now on openQA will test the snapshot first in a staging area, and only if it passes the defined testing criteria the snapshot will be published. So far, snapshots were published and only afterwards tested. Since publishing happened via the build service, which due to the recent upgrades is significantly bottlenecked and took several days or more, we have enough time to test the snapshot (which does not have to be published right away) and then decide on whether or not to publish the current tree without significant drawbacks. Therefore, publishing happens from now on not directly anymore but only via openQA. As the current state is failing the testing, it is actually a good thing as we'll be ironing out the issues and then have a stable snapshot (including images) published. That however also means there will likely not be a snapshot update for the next few days as we'll work out kinks and issues. Please note that armv6/v7hl is currently not covered by openQA and hence is published like before. However I started a bit on enabling testing of armv7 as well, but that will take a bit more time until we can make the switch. Greetings, Dirk -- 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] Running openSUSE as lxc container on a armv6 raspberry Pi 1 B+
by Johannes Kastl 08 Feb '16

08 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, I have a raspberry 1 B+ running Raspbian, but would like to migrate an existing VM on the raspi, but running as a lxc container. Has anyone run a opensuse (13.1/13.2/Leap/TW) as an lxc container on a armv6 raspi? Anyone tried this on armv7 (raspi2)? As far as I can see the main problems with running openSUSE on raspberries seems to be booting or rather finding an image that boots correctly. So maybe running inside a container (without u-boot and dtb's and stuff) could work? Or am I naive? ;-) Johannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAla44esACgkQzi3gQ/xETbLWBQCgiMBAqr2kbMbqL5+7E+DecON5 1boAnRHeQaEIfjB8jglORdxT6UPhNZBN =cLXm -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] pihwm package relocated
by Andreas Färber 07 Feb '16

07 Feb '16

Hello, Earlier this week I moved the pihwm package from :Contrib:RaspberryPi to hardware and cleaned it up a little: https://build.opensuse.org/package/show/hardware/pihwm If the .a static library is needed for anything, please package it in a devel-static sub-package. If you want to get this submitted to Factory, please step up as maintainer and start the process: do an SR from hardware to openSUSE:Factory and write an email to opensuse-factory mailing list pointing to SR# and explaining the package (cf. raspberrypi-firmware). Why? This is a further step towards untangling generally useful userspace packages from interim downstream kernels. Effects? Current users of pihwm will need to add hardware's openSUSE_Factory_ARM repository for now; if submitted and accepted into Factory that will no longer be necessary. Users of openSUSE:Factory:ARM or other openSUSE kernels can drop the :Contrib:RaspberryPi repo. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

[opensuse-arm] Temporary outage
by Dirk Müller 05 Feb '16

05 Feb '16

Hi, There is a network connectivity issue to the ARMv7 Build cluster right now on OBS. It is being investigated today. Hopefully workers are back up before the weekend. Greetings, Dirk -- 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] Current Pi2 image
by Chuck Payne 04 Feb '16

04 Feb '16

Guys, I was at SCaLE last week and I wanted to demo the current Pi2 image. So I followed the instruction and got the SD card load, but when I but booth up the pi, the two lights would stay on and no video. The images I was using was openSUSE-Tumbleweed-ARM-E17-raspberrypi2.armv7l.raw.xz Is that normal, I waited about 10 mins before shutting off the Pi. -- Terror PUP a.k.a Chuck "PUP" Payne ----------------------------------------- Discover it! Enjoy it! Share it! openSUSE Linux. ----------------------------------------- openSUSE -- Terrorpup openSUSE Ambassador/openSUSE Member skype,twiiter,identica,friendfeed -- terrorpup freenode(irc) --terrorpup/lupinstein Register Linux Userid: 155363 Have you tried SUSE Studio? Need to create a Live CD, an app you want to package and distribute , or create your own linux distro. Give SUSE Studio a try. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

6 11

[opensuse-arm] How to add u-boot-udoo package to factory
by Oscar C 01 Feb '16

01 Feb '16

Hi, Some days ago I created a SR to build u-boot for udoo boards. That SR is accepted but I cannot build the jeOS image because the package u-boot-udoo doesn't exist in factory. I have it in my own project. How do I submit it? Thanks! -- Cheers -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2