openSUSE ARM April 2015

arm@lists.opensuse.org

21 participants
22 discussions

[opensuse-arm] Attempt to run KIWI on unsupported architecture 'armv8l'

by Dirk Müller

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

5 years, 5 months

[opensuse-arm] openSUSE 13.2 on cubieboard works

by Volker Kuhlmann

I have managed to get oS 13.2 to boot on a cubieboard by doctoring the installation image and transplanting the factory boot loader and kernel into it. Steps are a bit complicated so I made a script[1]. Inputs are the 13.2 and factory installation images, and script constants need version adjustment. When installing the modified image the system boots, reboots (not something to take for granted...), and at least passes the sanity checks. So far, so good. Is the 13.2 kernel working on the cubieboard? I couldn't get that one to go, it hangs at "starting kernel", even with a newer boot loader. The 13.2 boot loader is broken and needs a newer version, but that shouldn't affect the kernel directly. Never mind. I've updated https://en.opensuse.org/HCL:CubieBoard accordingly. Volker [1] http://volker.top.geek.nz/soft/script/cubieboard-oS13.2-transplant-boot -- Volker Kuhlmann http://volker.top.geek.nz/ Please do not CC list postings to me. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 years, 4 months

[opensuse-arm] u-boot update - Need package rename

by Guillaume Gardet

Hi, I have updated u-boot to latest stable (2015.04) in Base:System but I need an admin to rename package u-boot-colibrit20iris to u-boot-colibrit20 to follow upstream which renamed colibri_t20_iris_defconfig to colibri_t20_defconfig. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 years, 5 months

[opensuse-arm] openSUSE:Factory:ARM / aarch64 is now building on native hardware

by Dirk Müller

Hi, for a couple of weeks we've been experimenting with native builds for aarch64, and are now happy to announce that we consider the current state stable enough to announce it as being available. == What changes == If you have packages enabled for building against openSUSE:Factory:ARM, nothing really changes for you. Just that the package will be build on native hardware now instead of using the user mode emulation on x86_64 that we've used before. Specifically, the macro %qemu_user_space_build is no longer set to 1. That said, for now it would still be a good idea to keep the %qemu_user_space_builds sections in your spec file as they are, as we still use user mode building for armv6 and for older targets (e.g. openSUSE 13.2). == What if I want to build locally? == Due to the use of user-mode qemu emulation, it was previously possible to build locally for aarch64 on a x86_64 host by running "osc build <project> <package> standard aarch64". This does not work anymore, since the "standard" repository is now requiring native aarch64 hardware. You can still build with user mode emulation by using this command: "osc build <project, e.g. openSUSE:Factory:ARM> <package> qemu aarch64". Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 years, 5 months

[opensuse-arm] Some issues with boot-wrapper-aarch64

by Guoqing Jiang

Hi, I tried to build aarch64 image by follow https://en.opensuse.org/openSUSE:AArch64#Boot-wraper. 1. However seems some steps maybe missed before "Cross-compile *.axf file", I guess the following steps should be run under boot-wrapper-aarch64 folder, is my understanding correct? $ autoreconf -i $ ./configure --host=<toolchain-triplet> --with-kernel-dir=<kernel-dir> <other-options> 2. I used below cmds to compile boot-wrapper-aarch64 1) ./configure --host=aarch64-linux-gnu --with-kernel-dir=<kernel-dir> --with-dtb=<kernel-dir>/arch/arm64/boot/vexpress-foundation-v8.dtb Boot wrapper configuration ========================== Linux kernel build dir: /home/gjiang/linaro-aarch64/ Device tree blob: /home/gjiang/linaro-aarch64/arch/arm64/boot/vexpress-foundation-v8.dtb Linux kernel command line: console=ttyAMA0 earlyprintk=pl011,0x1c090000 Embedded initrd: NONE Use PSCI? no CPU IDs: 0x0,0x1,0x2,0x3 Use GICv3? no 2) make CROSS_COMPILE=aarch64-linux-gnu- BOOTARGS='"root=/dev/vda2 consolelog=9 rw console=ttyAMA0"' FDT_SRC=vexpress-foundation-v8.dts IMAGE=linux-system-foundation.axf gic.S: Assembler messages: gic.S:26: Error: invalid address at operand 2 -- `ldr x1,=' gic.S:42: Error: invalid address at operand 2 -- `ldr x1,=' make: *** [gic.o] Error 1 But apparently some errs happened due to can't find the addrs for GIC_DIST_BASE and GIC_CPU_BASE, and I do following changes to fix it. diff --git a/arch/arm64/boot/dts/vexpress-foundation-v8.dts b/arch/arm64/boot/dts/vexp index 5e566a7..23e8e95 100644 --- a/arch/arm64/boot/dts/vexpress-foundation-v8.dts +++ b/arch/arm64/boot/dts/vexpress-foundation-v8.dts @@ -64,7 +64,7 @@ }; gic: interrupt-controller@2c001000 { - compatible = "arm,cortex-a9-gic"; + compatible = "arm,cortex-a15-gic"; #interrupt-cells = <3>; #address-cells = <0>; interrupt-controller; 3. Unfortunately, the axf can't boot well with foundation model finally. NR_IRQS:64 nr_irqs:64 0 Kernel panic - not syncing: No interrupt controller found. Call trace: [<ffffffc0000874e0>] dump_backtrace+0x0/0x130 [<ffffffc0003b22ec>] dump_stack+0x14/0x1c [<ffffffc0003b2534>] panic+0xe4/0x204 [<ffffffc0004ccd1c>] init_IRQ+0x2c/0x34 [<ffffffc0004cb634>] start_kernel+0x1b4/0x2e8 Seems the value of gic is not correct in vexpress-foundation-v8.dts, could someone can help me about it? Thanks in advance. Regards, Guoqing -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 years, 5 months

[opensuse-arm] NFS root fs

by Markus Weber

Hello Guys, i wonder if it is possible to boot opensuse-arm JeOS, e.g. this image http://download.opensuse.org/ports/armv6hl/factory/images/openSUSE-Factory-… from an nfs share and what adjustments have to be made to the bootloader or vice versa. Background: i have a pi v1 and want to use my DLink NAS as nfs server to boot from. I found a few tutorials on the net, but none is suitable for opensuse. Can anybody give me a guide to the pi part to accomplish this? so far i have: - A nfs share with no_root_squash and insecure (if necessary) flags, - A small (2gb) sd card, - A pi (obviously) - no glue how i can add boot parameters. Any help appreciated and thanks in advance. markus -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 years, 5 months

[opensuse-arm] oS 13.2 on cubieboard1 doesn't start booting

by Volker Kuhlmann

I am trying to install openSUSE 13.2 on a cubieboard1 that I bought about 2 years ago. It has an A10 and the PCB is labelled 2012-09-09. Out of the box it boots flawlessly into the Android 4.0.4, kernel 3.0.8 Nov 2012, stored on its nand flash ex factory. See its serial output below. Putting this http://download.opensuse.org/ports/armv7hl/distribution/13.2/appliances/ope… on a uSD card (32G Adata, 16G Lexar 600x - same result) and powering up the board gives a black screen and no keyboard or mouse activity. The serial terminal (once opened, somehow) only shows: U-Boot SPL 2014.10 (Nov 30 2014 - 00:17:30) DRAM: 1024 MiB CPU: 1008000000Hz, AXI/AHB/APB: 3/2/2 ### ERROR ### Please RESET the board ### Anything I can do/test here? Thanks, Volker Booting the android in nand flash: HELLO! BOOT0 is starting! boot0 version : 1.5.1 dram size =1024 Succeed in opening nand flash. Succeed in reading Boot1 file head. The size of Boot1 is 0x0003c000. The file stored in 0X00000000 of block 2 is perfect. Check is correct. Ready to disable icache. Succeed in loading Boot1. Jump to Boot1. [ 0.133] boot1 version : 1.4.0 [ 0.133] pmu type = 3 [ 0.134] bat vol = 0 [ 0.161] axi:ahb:apb=3:2:2 [ 0.161] set dcdc2=1400, clock=1008 successed [ 0.163] key [ 0.175] no key found [ 0.175] flash init start [ 0.226] flash init finish [ 0.227] fs init ok [ 0.228] fattype FAT16 [ 0.229] fs mount ok [ 0.236] script finish [ 0.237] power finish [ 0.244] BootMain start [ 0.244] 0 [ 0.264] key value = 0 [ 0.264] recovery key high 6, low 4 [ 0.265] unable to find fastboot_key key_max value [ 0.273] test for multi os boot with display [ 0.274] show pic finish [ 0.277] load kernel start [ 0.301] load kernel successed [ 0.301] start address = 0x4a00000 U-Boot 2011.09-rc1 (Nov 26 2012 - 14:01:52) Allwinner Technology CPU: SUNXI Family Board: A10-EVB DRAM: 512 MiB NAND: 3776 MiB In: serial Out: serial Err: serial --------fastboot partitions-------- -total partitions:11- -name- -start- -size- bootloader : 1000000 1000000 env : 2000000 1000000 boot : 3000000 2000000 system : 5000000 14000000 data : 19000000 20000000 misc : 39000000 1000000 recovery : 3a000000 2000000 cache : 3c000000 8000000 private : 44000000 1000000 sysrecovery : 45000000 14000000 UDISK : 59000000 93000000 ----------------------------------- Hit any key to stop autoboot: 0 NAND read: device 0 offset 0x3000000, size 0x2000000 33554432 bytes read: OK Starting kernel ... [ 0.181151] cryptomgr_test used greatest stack depth: 6672 bytes left [ 0.181535] cryptomgr_test used greatest stack depth: 6480 bytes left [ 0.183443] cryptomgr_test used greatest stack depth: 6388 bytes left [ 0.184385] cryptomgr_test used greatest stack depth: 6280 bytes left [ 0.217351] sw_ahci sw_ahci.0: forcing PORTS_IMPL to 0x1 [ 0.790418] [LCD] lcd_module_init [ 0.857446] regulator_init_complete: axp20_buck3: incomplete constraints, leaving on [ 0.865489] regulator_init_complete: axp20_buck2: incomplete constraints, leaving on [ 0.873517] regulator_init_complete: axp20_ldo4: incomplete constraints, leaving on [ 0.881461] regulator_init_complete: axp20_ldo3: incomplete constraints, leaving on [ 0.889376] regulator_init_complete: axp20_ldo2: incomplete constraints, leaving on [ 0.897360] regulator_init_complete: axp20_ldo1: incomplete constraints, leaving on [ 0.905093] sunxi-rtc sunxi-rtc: hctosys: unable to read the hardware clock [ 0.966821] init: to sleep 1 seconds. [ 1.970789] init: has waken up. [ 1.973981] init: [william] hdmistatus = 1! [ 1.978578] init: width = 1280 [ 1.981696] init: height = 720 [ 1.984756] init: s.st_size = 3686400 [ 2.155357] init: do_umount: /data [ 2.279486] e2fsck used greatest stack depth: 5696 bytes left [ 2.413573] init: do_umount: /cache [ 2.452029] init: dont need format /dev/block/nandk [ 2.458235] init: dont need format /dev/block/nandi [ 2.519475] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead. [ 2.533583] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery' [ 3.550659] android_usb: already disabled [ 5.110541] init: untracked pid 99 exited [ 5.114581] init: untracked pid 101 exited [ 5.118703] init: untracked pid 103 exited [ 11.876030] sunxi-rtc sunxi-rtc: rtc only supports 63��2010��2073�� years [ 12.145692] BatteryStats-Wr used greatest stack depth: 5648 bytes left [ 16.606513] wemac wemac.0: WARNING: no IRQ resource flags set. [ 18.727648] netd used greatest stack depth: 5416 bytes left -- Volker Kuhlmann http://volker.top.geek.nz/ Please do not CC list postings to me. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 years, 5 months

[opensuse-arm] gnutls armv7l build failure

by Andreas Färber

Hi, Has anyone already looked into why gnutls is failing to build in Factory? It seems to be failing three tests for armv7l (but not for aarch64 or armv6l): [ 1261s] PASS: pathlen [ 1264s] PASS: aki [ 1267s] FAIL: pem-decoding [ 1274s] PASS: certtool [ 1280s] PASS: invalid-sig [ 1288s] FAIL: email [ 1291s] FAIL: crq [ 1291s] SKIP: template-test [ 1291s] ============================================================================ [ 1291s] Testsuite summary for GnuTLS 3.4.0 [ 1291s] ============================================================================ [ 1291s] # TOTAL: 8 [ 1291s] # PASS: 4 [ 1291s] # SKIP: 1 [ 1291s] # XFAIL: 0 [ 1291s] # FAIL: 3 [ 1291s] # XPASS: 0 [ 1291s] # ERROR: 0 [ 1291s] ============================================================================ [ 1291s] See tests/cert-tests/test-suite.log [ 1291s] Please report to bugs(a)gnutls.org [ 1291s] ============================================================================ [ 1291s] Makefile:1508: recipe for target 'test-suite.log' failed [ 1291s] make[4]: *** [test-suite.log] Error 1 https://build.opensuse.org/package/show/openSUSE:Factory:ARM/gnutls This seems to block the build of further packages such as QEMU due to further library dependency updates (unresolvable). Thanks, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg)

7 years, 5 months

[opensuse-arm] Syslog problems

by Volker Kuhlmann

I have 2 problems with syslog I can't seem to solve. The first is /dev/log not accepting connections: # logger "Log string" logger: socket /dev/log: Connection refused This causes ntpd.service to fail. systemd-journald.service is running, but lsof /dev/log shows lots but nothing with /dev/log in the NAME column. The second is a truckload of syslog audit messages being pooped all over the serial terminal, which makes the terminal almost unusable. I already uninstalled all apparmor rpms (except libapparmor1) and this stuff keeps on spurting forth. It's factory with all rpms up to date (there was a big lot, 20150401 "Tumbleweed). It's possible I broke it with excessive use of systemctl. Which parts should I check to get this under control again? I had installed the syslog-ng package and syslog-service, both uninstalled again. Is it relevant that /var is on its own ext4 partition? Thanks muchly, Volker -- Volker Kuhlmann http://volker.top.geek.nz/ Please do not CC list postings to me. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 years, 5 months

[opensuse-arm] How to use Rapsberry Pi Factory image headless

by Freek de Kruijf

I tried to use openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1- Build280.1.raw.xz from http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras… on a headless system. When using the 13.2 image I have to remove the file /var/lib/YaST2/reconfig_system and the system boots and I can log in via ssh. However the image above does not have such a file and I don't see the Ethernet interface coming up. -- 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

7 years, 5 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

openSUSE ARM April 2015