openSUSE ARM January 2016

arm@lists.opensuse.org

22 participants
18 discussions

[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] 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] 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] 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] 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

[opensuse-arm] Tumbleweed images broken - modules missing
by Guillaume Gardet 22 Jan '16

22 Jan '16

Hi, I tested latest Tumbleweed image (11 jan) for Arndale (but all boards may be affected) and initrd does not include requested modules, only folders. Moreover, there are 2 folders in /lib/modules/ : *-default and *-lpae. Here, we should only have *-lpae, no? Any idea why? Any kiwi update which could break initrd modules? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 4

Re: [opensuse-arm] Re: Tumbleweed images broken - modules missing
by Guillaume Gardet 22 Jan '16

22 Jan '16

Le 22/01/2016 10:43, Marcus Schäfer a écrit : > Hi, > >> I have : <type image="oem" boot="oemboot/suse-tumbleweed" >> not vmxboot. >> So, kiwi should use OEM things, not VMX. No? > yes doesn't matter if oem or vmx, bootkernel applies in any case > >> I have it in <packages type="bootstrap">, not image. > That's fine too It seems that it is kiwi-desc-oemboot-requires (and maybe more kiwi rpm) which pull kernel-default. See requires here: https://build.opensuse.org/package/binary/openSUSE:Factory:ARM/kiwi?arch=ar… How to fix that? Guillaume > > Regards, > Marcus -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 1

Re: [opensuse-arm] Re: Tumbleweed images broken - modules missing
by Guillaume Gardet 22 Jan '16

22 Jan '16

Le 22/01/2016 10:25, Marcus Schäfer a écrit : > Hi, > >> Why does kiwi install kernel-default whereas we only need kernel-lpae? >> I guess this is because of this line: >> chroot /usr/src/packages/KIWI-oem/oem/boot-VMX.cPGEzD/kiwi-VMXboot-3950 zypper --non-interactive --pkg-cache-dir /var/cache/kiwi/packages --reposd-dir /var/cache/kiwi/zypper/repos --solv-cache-dir /var/cache/kiwi/zypper/solv --cache-dir /var/cache/kiwi/zypper --config /var/cache/kiwi/zypper/zypper.conf.3950 --no-gpg-checks install --auto-agree-with-licenses --no-recommends kernel-default > because you are using vmxboot with the standard profile which pulls in > kernel-default. You can do the following: I have : <type image="oem" boot="oemboot/suse-tumbleweed" not vmxboot. So, kiwi should use OEM things, not VMX. No? > > - In your <type> section tell kiwi to use a custom kernel > > <type .... bootkernel="custom"/> > > - In your <packages type="image"/> section tell kiwi which kernel to use > > <package name="kernel-lpae" bootinclude="true"/> > > The bootinclude statement is important otherwise no kernel will be > installed in the boot(initrd) image I have it in <packages type="bootstrap">, not image. > > That way only kernel-lpae should be visible in the log. If now still > another kernel is pulled in it happens because zypper thinks it is > required which means some package triggers it I do not think so, since it is pulled-in alone, not as dep. Guillaume > > Regards, > Marcus -- 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] all recent builds failed on aarch64
by Dirk Müller 21 Jan '16

21 Jan '16

Hi, sorry, I recently updated the build workers to QEMU 2.5.0 which seems to have all builds to hang after an hour or so and then being marked as failed. I've now reverted the upgrade and did a osc rebuildpac -f on those projects that I have access to. Feel free to do it yourself where you care when the build log ends with "build timed out on armbuild2X" after a very long hang period, hopefully that is fixed now with the downgrade. 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

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

openSUSE ARM January 2016