- openSUSE ARM

[opensuse-arm] openSUSE:Factory:ARM/armv6 outage, recovering
by Dirk Müller 07 May '15

07 May '15

Hi, it seems recently qemu-linux-user 2.3.0 has been accepted to factory, which however immediately crashes on startup, so all the builds in the last two days (if I see correctly) have been hanging in an endless crash/rebuild loop. I've manually injected a qemu 2.2.0 build again and locked 2.3.0 out to get things moving. 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 17

[opensuse-arm] ARM sunxi devicetree not up to date
by Frank Kunz 03 May '15

03 May '15

Hi, it seems that the sunxi device trees are not rebuild ans still have kernel 3.19 data included instead of version 4. This prevents (at least) the sun4i based boards from booting due to changes in the mmc drivers and device trees. It look that there is a build dependency missing when the kernel is updated. -Frank linux:~ # zypper info dtb-sun4i Loading repository data... Reading installed packages... Information for package dtb-sun4i: ---------------------------------- Repository: openSUSE-Factory-repo-oss Name: dtb-sun4i Version: 3.19.0-40.1 Arch: armv7hl Vendor: openSUSE Installed: Yes Status: up-to-date Installed Size: 192.1 KiB Summary: Allwinner sun4i based systems Description: Device Tree Files for Allwinner sun4i based systems. linux:~ # cat /etc/os-release NAME=openSUSE VERSION="20150428 (Tumbleweed)" VERSION_ID="20150428" PRETTY_NAME="openSUSE 20150428 (Tumbleweed) (armv7hl)" ID=opensuse ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:opensuse:20150428" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://opensuse.org/" ID_LIKE="suse" linux:~ # -- 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] Some problems with Tumbleweed on Raspberry Pi B 1
by Dirk Müller 02 May '15

02 May '15

Hi Freek, >> The build is not disabled, not sure where you looked: >> https://build.opensuse.org/package/show/openSUSE:Factory:ARM/libzypp > > https://build.opensuse.org/package/show/openSUSE:Factory/libzypp Ah, ok. All the ARM stuff is being built in a subproject (:ARM), it shares however the sources with openSUSE:Factory. >> > 2. Updating kernel-default to 3.19.3-1.1 gives an unbootable system. >> Known problem, already fixed in kernel 4.0.0 which is being synced out >> (see above). This kernel is now published. There is still one zypp related dependency issue, which I just fixed (hopefully syncs out within the next 24 h or so). 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 5

[opensuse-arm] Some problems with Tumbleweed on Raspberry Pi B 1
by Freek de Kruijf 01 May '15

01 May '15

I am using openSUSE-Factory-ARM-JeOS-raspberrypi.armv6l-1.12.1- Build266.3.raw.xz, which works OK. I tried updating the software to the newest versions available in the repository and noticed: 1. zypper can't be updated because the proper version of libzypp is not available. In openSUSE Build I see building of libzypp for Factory disabled for all ARM architectures. Is there a problem with building this library? 2. Updating kernel-default to 3.19.3-1.1 gives an unbootable system. Any solution? I noticed some error messages when dracut is executed: /usr/lib/dracut/dracut-functions.sh: line 1585: host_modules: bad array subscript -- 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

2 2

[opensuse-arm] u-boot update - Need package rename
by Guillaume Gardet 29 Apr '15

29 Apr '15

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

3 5

[opensuse-arm] openSUSE:Factory:ARM / aarch64 is now building on native hardware
by Dirk Müller 29 Apr '15

29 Apr '15

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

5 8

[opensuse-arm] Some issues with boot-wrapper-aarch64
by Guoqing Jiang 27 Apr '15

27 Apr '15

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

2 4

[opensuse-arm] NFS root fs
by Markus Weber 27 Apr '15

27 Apr '15

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 12

[opensuse-arm] oS 13.2 on cubieboard1 doesn't start booting
by Volker Kuhlmann 27 Apr '15

27 Apr '15

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

4 10

[opensuse-arm] gnutls armv7l build failure
by Andreas Färber 26 Apr '15

26 Apr '15

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)

2 1

[opensuse-arm] Syslog problems
by Volker Kuhlmann 24 Apr '15

24 Apr '15

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

2 3

[opensuse-arm] How to use Rapsberry Pi Factory image headless
by Freek de Kruijf 23 Apr '15

23 Apr '15

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

3 7

[opensuse-arm] cloud-init in JeOS
by Matwey V. Kornilov 18 Apr '15

18 Apr '15

Hi, What do you think? I found that deploying JeOS onto SD card is similar to deploying virtual machine. -- 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] Status of cuboxi images
by Miklos Vajna 18 Apr '15

18 Apr '15

Hi, Did anybody try the openSUSE 13.2 cuboxi image on any CuBox versions? If so, any idea what is the state of them, are they working, broken, etc? I'm asking as I plan to order (probably) a CuBox-i2eX and plan to run openSUSE on it, but I thought better to ask what's the experience with it before going ahead. :-) Thanks, Miklos

3 2

[opensuse-arm] Getting software for ARM
by Volker Kuhlmann 13 Apr '15

13 Apr '15

What is the current situation for getting more packages? E.g. 13.2 x86 has a lot of other repos with tools. Is there something similar for ARM? The fedora nedit works on factory, but I'm looking for others too, like jailkit. Are the source packages for factory available? Can't find a repo for them. Thanks, 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

4 4

[opensuse-arm] JeOS missed ifconfig
by Matwey V. Kornilov 13 Apr '15

13 Apr '15

Hi, Is it only for me? Recent Factory JeOSes seems to miss ifconfig, as well as route2 tools. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 5

[opensuse-arm] armv6l' cmake or clang or gcc is broken
by Dmitriy Perlow 10 Apr '15

10 Apr '15

https://build.opensuse.org/package/live_build_log/home:DarkSS/HuffmanArchiv… [ 206s] /usr/bin/ld: cannot find crtbegin.o: No such file or directory [ 206s] /usr/bin/ld: cannot find -lgcc [ 206s] /usr/bin/ld: cannot find -lgcc_s Everything is fine for x86, ppc64 & armv7l. -- Best regards, Dmitriy DA(P).DarkneSS Perlow @ Linux x64 -- 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] Boot images 13.2
by Volker Kuhlmann 10 Apr '15

10 Apr '15

http://download.opensuse.org/ports/armv7hl/distribution/13.2/appliances/ The images seem to get rebuilt every so often. Can whoever is looking after the upload please find a process to keep the .sha256 files in sync? These are commonly mismatched: openSUSE-13.2-ARM-JeOS-cubieboard.armv7l-Current.raw.xz openSUSE-13.2-ARM-JeOS-cubieboard.armv7l-Current.raw.xz.sha256 openSUSE-13.2-ARM-JeOS-cubieboard.armv7l-1.12.1-Build33.6.raw.xz openSUSE-13.2-ARM-JeOS-cubieboard.armv7l-1.12.1-Build33.4.raw.xz.sha256 Or delete all the .sha256 altogether, xz compression should provide for download error detection. The gpg sig doesn't help if it's for the wrong file... Not sure about the usefulness of the "Current" symlinks either. 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

2 1

[opensuse-arm] Old host kernels on aarch64 workers?
by Andreas Schwab 07 Apr '15

07 Apr '15

It looks like the host kernels on the aarch64 workers are rather old, I see a lot of CPU stalls reported. Anything older than 3.19.x is not recommended. Andreas. -- Andreas Schwab, SUSE Labs, schwab(a)suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 7

[opensuse-arm] aarch64 in openQA
by Ludwig Nussel 07 Apr '15

07 Apr '15

Hi, As you may have noticed openqa.opensuse.org has some aarch64 jobs. It was quite some effort to get there but it's far from done yet. 1. Build Power At the moment there's one openQA worker running on a PPC64 host (power8). That host is fast enough to run the emulation reasonably well. To do serious tests we need real hardware with kvm though. Not just for openQA but also for OBS. The image in openQA is just the NET iso that installs from a static ftp repo from two weeks ago. The ftp tree wasn't published since then as it never finished building. Factory is moving too fast, aarch64 can't catch up. Meanwhile maybe an installation DVD could help. The limited set of packages on the DVD probably has a chance to finish in time. 2. Project Setup To get a real Tumbleweed for aarch64 the OBS setup needs to be changed: - openSUSE:Factory:ARM/_product need to become a link to openSUSE:Factory/_product. That way arm inherits the Tumbleweed version number. - openSUSE:Factory:ARM:ToTest needs to be created to hold the snapshots that go into openQA 3. Scripts The magic factory scripts (totest manager, pattern generator) need to be adjusted. Dinar did most of the heavy lifting for ppc so the scripts are now able to handle another architecture. The spots needed for aarch64 should be easy to find by searching for ppc. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5; 90409 Nürnberg; Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 5

[opensuse-arm] Re: Broken RaspberryPi 1 images
by Michael Ströder 07 Apr '15

07 Apr '15

Alex Armstrong wrote: > Michael Ströder wrote: >> Dirk Müller wrote: >>> kernel-default from here: >>> >>> http://download.opensuse.org/repositories/home:/dirkmueller:/branches:/Kern… >>> >> >> Unfortunately kernel-default-3.19.2-6.1.g7088b79 did not make it into >> the download repo above. >> >> Although it seems to be built: >> >> https://build.opensuse.org/package/binaries/home:dirkmueller:branches:Kerne… >> >>> contains the minimal fixes neede and seems to work fine according to >>> Michael, and shortly there will be a >> >> Sorry! I've messed up files with kernel versions during testing. I >> have to re-test myself once kernel-default-3.19.2-6.1.g7088b79 is >> available for download. >> > Yes, I saw that too. I tested the > kernel-default-3.19.2-5.1.gb5cf33a.armv6hl.rpm and it's working. Strange. This particular version did not work for me. The USB devices were not accessible, > I'll also check kernel-default-3.19.2-6.1.g7088b79 when it's available. This seems to work! :-) # uname -a Linux srv10 3.19.2-6.g7088b79-default #1 Wed Apr 1 15:14:39 UTC 2015 (7088b79) armv6l armv6l armv6l GNU/Linux Ciao, Michael.

3 3

Re: [opensuse-arm] openSUSE ARM img compatible with Raspberry Pi 2
by Andreas Färber 03 Apr '15

03 Apr '15

Am 06.03.2015 um 18:13 schrieb Dirk Müller: > > Am 06.03.2015 17:54 schrieb "Jimmy PIERRE" > <jimmypierre.rouen.france(a)gmail.com > <mailto:jimmypierre.rouen.france@gmail.com>>: >> >> On 1 March 2015 at 00:39, Andreas Färber <afaerber(a)suse.de > <mailto:afaerber@suse.de>> wrote: >> > Am 24.02.2015 um 22:57 schrieb Dirk Müller: >> >> Hi, >> >> >> >>> There's a v3 patchset on the u-boot mailing list, but that's > surely not >> >>> yet in our Base:System u-boot package. You'd need a u-boot-rpi2 > Contrib >> >>> package with those patches applied to create an image. >> >> >> >> The u-boot patches are actually in git already >> > >> > Indeed they were applied Feb 22, but on Feb 21 weren't yet. :) >> > >> > Cheers, >> > Andreas >> > >> >> and will be in the next >> >> stable release then, so that part i >> Greetings, Hallo, >> >> Tell me, is it the place to find the .img please: >> > >> > http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras… >> > > Yes, it will be the right place (or rather a newly created images > subdir) once it built. No, Kiwi images would not go into standard but into images. And that folder does not exist today. Regards, 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) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

6 17

[opensuse-arm] armv6l is missing on repository openSUSE-13.2-repo-update
by Freek de Kruijf 03 Apr '15

03 Apr '15

When running zypper up on my Raspberry Pi I get a warning about an obsolete repository openSUSE-13.2-repo-update. Looking at http://download.opensuse.org/ports/update/13.2/ I do not see anything about armv6l I wonder why? -- fr.gr. 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 11

[opensuse-arm] u-boot-vexpressaemv8a dropped upstream
by Guillaume Gardet 03 Apr '15

03 Apr '15

Hi, I am updating u-boot to 2015.04-rc5 and u-boot-vexpressaemv8a has been dropped. Instead, we have 2 flavours: vexpress_aemv8a_juno_defconfig and vexpress_aemv8a_semi_defconfig. Should we simply drop our aemv8a config or enable one or both new configs? Not sure if it is used at all. Guillaume -- 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] GCC ICE compiling today's linux-next.git on 13.2 armv7hl
by Andreas Färber 31 Mar '15

31 Mar '15

Hi, It seems I am running into https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49423 compiling mm/migrate.c from linux-next.git (exynos_defconfig-derived config) natively on armv7hl: gcc (SUSE Linux) 4.8.3 20140627 [gcc-4_8-branch revision 212064] Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. The above link indicates the fix was backported as 215686 - does that mean we are missing a gcc48 branch update in 13.2? Regards, 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) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 5

[opensuse-arm] openSUSE on Beagleboard xM
by Wojciech Kazubski 31 Mar '15

31 Mar '15

I am trying to install openSUSE 13.2 on Beagleboard xM rev. B. If I am correct, I should use the image labelled "beagle" for this board. So far I managed to get JeOS version working, I can connect using serial console or SSH protocol (after configuring the network). With E17 an XFCE versions I get the last last message "Starting kernel" on serial port but no console output. The screen goes plain yellow soon after reset and then black and message "No input signal" appears. It seems that keyboard is working, as I can toggle keyboard LEDs wih "Caps Lock" and "Scroll Lock" keys, but I can't do anything more. I suspect that there is some problems with configuring video hardware, missing/bad kernel module or so. Should JeoS version of openSUSE for ARM produce output to the local console? -- Wojciech Kazubski Instytut Radioelektroniki Politechniki Warszawskiej -- 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] Yast problems
by Volker Kuhlmann 29 Mar '15

29 Mar '15

I prefer to use yast-x11 on the cubieboard, it takes a looong time to start but then runs OK (over ssh). There are 2 problems with it: 1) The software management shows 37 autoinstall packages, including alsa-oss, bash-doc, glibc-extra, openssh-helpers, perl-HTML-Tidy, unzip-doc. zypper up shows nothing to do, as does yast-ncurses, and both show the locked packages apache2-mod_perl mariadb php5 Why does yast-x11 want to install a pile of stuff that is definitely ot needed by anything, like the -doc packages? Why is this difference in behaviour between x11/ncurses versions? 2) No keyboard input is accepted anywhere in yast. This stdout/err of yast-x11 says why: libEGL warning: DRI2: could not open /dev/dri/card0 (No such file or directory) xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb Qt: Failed to create XKB context! Use QT_XKB_CONFIG_ROOT environmental variable to provide an additional search path, add ':' as separator to provide several search paths and/or make sure that XKB configuration data directory contains recent enough contents, to update please see http://cgit.freedesktop.org/xkeyboard-config/ . Ooops, no X11 keyboard input installed! To fix: zypper in xf86-input-keyboard (another 27 packages) I installed yast-x11 with zypper in yast2-x11 yast2-control-center-qt libyui-qt6 xauth which installs ca 265 rpms, so something is missing a dependency on basic keyboard input. Or is this intentional? Otherwise I'll file a bug. I don't expect this to be specific to armv7hl, though it's triggered there because it's a smaller minimal system to start with. This is on factory, cubieboard, and I ran zypper up previously (giving me e.g. a new kernel). Thanks, 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

2 2

[opensuse-arm] NTP service fails to start
by Volker Kuhlmann 29 Mar '15

29 Mar '15

The NTP daemon doesn't start journalctl -xn shows: Mar 26 15:13:45 linux start-ntpd[1779]: /usr/sbin/start-ntpd: line 144: logger: command not found Mar 26 15:13:45 linux systemd[1]: Failed to start NTP Server Daemon. Yep no logger command, and no rpm providing it (on 12.3 it's in util-linux). It seems like an essential command - is it missing deliberately? Thanks, 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

6 10

[opensuse-arm] kernel update breaks rasperry pi 1
by Michael Ströder 26 Mar '15

26 Mar '15

HI! After the recent kernel update from Factory_ARM my rasperry pi 1 does not boot anymore! It hangs with message "Starting kernel...". Any clue how to work around this? I have another rasperry with files before the recent kernel update. Ciao, Michael.

4 15

[opensuse-arm] BeagleBone A6 (AKA BeagleBone White) does not boot.
by Robin Holt 26 Mar '15

26 Mar '15

Has anybody booted the JeOS...33.3 image on either a BBB or BBW? When I attempt to boot the opensuse 13.2 JeOS...33.3 image on a BeagleBone White, the kernel gets through boot, but then fails to exec init, et. al. After some tweaking of kernel command line parameters, I managed to get the the shell in the initrd. Nearly none of the commands worked as many of the libraries reported they were not compatible with the processor. This is for a work project where we pulled the A6 rev board off a shelf. Since I ran into the troubles, and due to the plan for this project to be BeagleBone Black based, I have ordered a BBB which should arrive today or tomorrow. Thank you, Robin Holt -- 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] Moving rootfs to SATA
by Volker Kuhlmann 26 Mar '15

26 Mar '15

Instructions for moving the rootfs from uSD card to SATA disk, because I couldn't find it anywhere: Connect SATA disk. An old 2.5" should do, a 3.5" should work too as long as it's powered from somewhere (not the cubieboard). A cheap PATA/SATA converter works too and it's possible to make use of old 2.5" PATA disks if they have enough space for the purpose. My cubieboard was shipped with a nifty power/data SATA cable, with a plug to go onto the board's "SATA 5V" 2-pin header. This power header turned out to be useless (I tried half a dozen different disks, some SATA) because it doesn't provide enough voltage for the disk to spin up. I measured around 4.5V. So it's necessary to power the 2.5" from some other source too. There are some cubietruck mounting boards that might fit here. Boot the cubieboard, I assume from uSD card. The SATA disk can be connected any time, the SATA port is hot-pluggable! Yes SATA ports and SATA power are always hot-pluggable without damaging hardware, but that doesn't mean the kernel driver will also play that game. This one works, the disk is immediately recognised. Nifty! The rootfs is on /dev/mmcblk0p2, let's say the SATA partition is /dev/sda1 # mkfs -text4 -m1 /dev/sda1 (or whatever preference) # mount /dev/sda1 /mnt # nice cp -ax / /mnt/ (copy rootfs) # cd /boot Edit boot.script, replacing /dev/mmcblk0p2 with /dev/sda1. Re-create boot.scr: # mkimage -C none -A arm -T script -d boot.script boot.scr Fix up fstab: # cd /mnt/etc Edit fstab, replacing /dev/mmcblk0p2 with /dev/sda1. In my case, /mnt/proc was not copied, but the system hangs on boot if it doesn't exist. Check, and do # cd /mnt # mkdir proc # chmod 555 proc Done. # reboot Note that /boot is still located on uSD card, /dev/mmcblk0p1. Apparently the hardware can not boot from SATA directly, although it should be possible to move /boot into the nand flash - but I don't know how. Until then a (very small) uSD card remains necessary. Swap space is also still located on the uSD card, /dev/mmcblk0p3. To move it to SATA disk, create a partition for it, and initialise it. Edit /etc/fstab (on the rootfs, now on SATA disk!) to activate it and reboot. HTH, 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

1 0

[opensuse-arm] Cubieboard monitor output not activated after power-on
by Volker Kuhlmann 26 Mar '15

26 Mar '15

openSUSE-Factory-ARM-JeOS-cubieboard.armv7l-1.12.1-Build269.1.raw.xz The DPMI output is not activated when a VGA monitor is connected with a DPMI/VGA adapter and the cubieboard is powered up. Guessing, something doesn't wait long enough for the adapter to respond. Sorry I can't imagine too many cubieboards on DPMI monitors, but retired VGA stuff is plentiful. ;-) The adapters are 10 bucks. U-Boot SPL 2015.04-rc3 (Mar 09 2015 - 21:02:35) DRAM: 1024 MiB CPU: 1008000000Hz, AXI/AHB/APB: 3/2/2 U-Boot 2015.04-rc3 (Mar 09 2015 - 21:02:35) Allwinner Technology CPU: Allwinner A10 (SUN4I) I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial When the system is rebooted by command (from Linux, Android), the DPMI output is activated: HDMI connected: Setting up a 1280x1024 hdmi console In: serial Out: vga Err: vga There is no reset button on board, so reset is with the power cable. Just as well I'm planning to use this headless... 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

1 1

[opensuse-arm] armv7 workers are broken
by Andreas Schwab 24 Mar '15

24 Mar '15

[ 0s] Using BUILD_ROOT=/var/cache/obs/worker/root_4/.mount [ 0s] Using BUILD_ARCH=armv7l:armv6l:armv5tel [ 0s] Doing kvm build in /var/cache/obs/worker/root_4/root [ 0s] [ 1s] [ 1s] armbuild18 started "build exaile.spec" at Tue Mar 24 08:56:31 UTC 2015. [ 1s] [ 1s] Building exaile for project 'openSUSE:Factory:ARM' repository 'standard' arch 'armv7l' srcmd5 '8b532eeba6b98fb5fe5eccd4482f2568' [ 1s] [ 1s] processing recipe /var/cache/obs/worker/root_4/.build-srcdir/exaile.spec ... [ 1s] running changelog2spec --target rpm --file /var/cache/obs/worker/root_4/.build-srcdir/exaile.spec [ 1s] init_buildsystem --configdir /var/run/obs/worker/4/build/configs --cachedir /var/cache/build --prepare --clean --rpmlist /var/cache/obs/worker/root_4/.build.rpmlist /var/cache/obs/worker/root_4/.build-srcdir/exaile.spec build rpmlint-Factory ... [ 2s] hostname: Name or service not known [ 2s] unpacking preinstall image openSUSE:Factory:ARM/standard/preinstallimage-base [5bc6056231bc911005b9fc63638e5440] [ 11s] ................. [ 11s] [ 11s] copying packages... [ 15s] reordering...cycle: gio-branding-upstream -> libgio-2_0-0 [ 15s] breaking dependency libgio-2_0-0 -> gio-branding-upstream [ 15s] cycle: girepository-1_0 -> libgirepository-1_0-1 [ 15s] breaking dependency libgirepository-1_0-1 -> girepository-1_0 [ 15s] done [ 16s] ### WATCHDOG MARKER START ### [ 16s] booting kvm... [ 16s] linux64 /usr/bin/qemu-system-arm -no-reboot -nographic -vga none -net none -enable-kvm -M virt -cpu host -mem-prealloc -mem-path /dev/hugepages -kernel /boot/zImage.guest -initrd /boot/initrd -append root=/dev/disk/by-id/virtio-0 panic=1 quiet no-kvmclock nmi_watchdog=0 rw rd.driver.pre=binfmt_misc elevator=noop console=ttyAMA0 init=/.build/build -m 1020 -drive file=/var/cache/obs/worker/root_4/root,if=none,id=disk,serial=0,cache=unsafe -device virtio-blk-device,drive=disk -drive file=/var/cache/obs/worker/root_4.swap,if=none,id=swap,serial=1,cache=unsafe -device virtio-blk-device,drive=swap -smp 1 [ 17s] Cannot set up guest memory 'mach-virt.ram': Cannot allocate memory [ 17s] ### WATCHDOG MARKER END ### [ 17s] No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl) [ 17s] or the build host has a kernel or hardware problem... Andreas. -- Andreas Schwab, SUSE Labs, schwab(a)suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 14

[opensuse-arm] qemu-linux-user breakage - armv6l / aarch64
by Andreas Färber 23 Mar '15

23 Mar '15

Hello everyone, Virtualization qemu package was updated to v2.3.0-rc0 last week. This included a bug that broke forking. A fix is submitted [1] and building. Factory should not be affected (I don't submit -rc0), only OBS setups using qemu-linux-user from the Virtualization project directly, such as the armv6l and aarch64 builds (but not armv7l). If you see weird package failures, please check that (usually the x86_64 version of) qemu-linux-user has succeeded building and then trigger a rebuild of your package. https://build.opensuse.org/package/show/Virtualization/qemu-linux-user If someone has good ideas how to run some form of test suite in OBS to catch such breakages, please feel free to make proposals. Sorry for the inconvenience, Andreas [1] https://build.opensuse.org/request/show/292450 -- 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) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 5

[opensuse-arm] Trying to build the newest version of clamav in OBS for Raspberry Pi 1 B
by Freek de Kruijf 21 Mar '15

21 Mar '15

I tried to branch a clamav project in OBS in order to build the newest version of clamav for the Raspberry Pi 1 B. I tried to branch the 13.2 Update project, which already contains the newest clamav tar file, however I could not find how to build it for armv6l. I tried to branch the 13.2 project which shows a build for armv6l, however with an old tar file. However after that the armv6l architecture is no longer available. Any hints on how to proceeed? -- fr.gr. 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

1 0

[opensuse-arm] phpBB 3.1.0 new version
by phpbb200＠gmail.com 20 Mar '15

20 Mar '15

Hello, phpBB 3.1.0 is now available , please be sure to backup your forum before staring in the update process . we are happy to help you in updating your forum safely, please reply to this email if you are interested in our paid sevices . thank you -- 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] ncurses-dev
by Edgar Dombrowski 19 Mar '15

19 Mar '15

Hallo, Raspi-Friends. I am trying to install a packet radio-program tnt based on the latest (?) OS13.2 version. I need to install the ncurses-dev files. Is the any provider? (Using Debia-Squeeze, I got it) Thanks for your assistance Regards Edgar, DJ3PU, Munich -- 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] Indebted for driving on toll road #0000689285
by E-ZPass Manager 19 Mar '15

19 Mar '15

Notice to Appear, You have a unpaid bill for using toll road. Please, do not forget to service your debt. The invoice is attached to this email. Yours faithfully, Bill Lee, E-ZPass Manager.

3 2

[opensuse-arm] Problem with openSUSE Factory on samsung chromebook (snow)
by Guillaume Gardet 17 Mar '15

17 Mar '15

Hi, Current Factory image does boot on Chromebook (repartition append) but display stay black. I have no serial cable for this laptop, so I cannot debug further. Is there anyone who could have a look, please? I sent SR #290617 to fix 2nd boot when booting from SD. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 13

[opensuse-arm] How to build 13.2 armv7l packages?
by Miklos Vajna 15 Mar '15

15 Mar '15

Hi, As far as I see, in case I want to build armv7l packages for Factory, then all I need is: <repository name="openSUSE_Factory_ARM"> <path project="openSUSE:Factory:ARM" repository="standard"/> <arch>armv7l</arch> </repository> in 'osc meta prj -e', and the packages will be built on Factory for armv7l, too. How can I do the same for 13.2? <repository name="openSUSE_13.2_ARM"> <path project="openSUSE:13.2:ARM" repository="standard"/> <arch>armv7l</arch> </repository> is what I tried, but osc says: Sending meta data... BuildService API error: unknown_project (404) openSUSE:13.2:ARM so that doesn't work, something else is needed. Thanks, Miklos

2 2

[opensuse-arm] Re: [opensuse-kernel] Raspberry Pi "classic" model B random MAC address on every boot (only with openSUSE)
by Andreas Färber 15 Mar '15

15 Mar '15

Hi, Am 14.03.2015 um 12:09 schrieb Stefan Seyfried: > just for fun I thought I'd try out openSUSE on my old Raspi model B. > > How surprised I was, when it got a different IP address than before! > > With every distribution I tried before (raspbian, arch, openelec and all > home built Yocto versions), it had the MAC address > b8:27:eb:a9:00:de, now with opensuse 13.2 it is 1e:e0:10:10:1e:dc > > I'm guessing the SUSE kernel is doing something wrong wrt. the mac address? The openSUSE kernel is not doing anything special for the Raspberry Pi. Differences to Raspbian et al. might be that they use a kernel directly (doesn't Raspbian use a downstream kernel from Raspberry Pi Foundation?) while openSUSE uses U-Boot, with an upstream based kernel. Please provide further details of what exactly you've tried to opensuse-arm mailing list, where much more Pi users are around: Did you start with an official JeOS image or did you do your own boot setup? As usual you can tweak /etc/sysconfig/network/ifcfg-eth0 config with LLADDR= to assign a stable MAC address. I don't remember having to do that on the Raspberry Pi with 13.2 though. Regards, 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) -- 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] Building an EFI image
by Andrew Wafaa 12 Mar '15

12 Mar '15

Aloha, What are the steps needed to build an EFI based image? Take into account that the target board is not yet included in upstream tianocore but is in a downstream repo. Thanks, Andy -- 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] kernel-obs-build and qemu/arm/ppc
by Adrian Schröter 11 Mar '15

11 Mar '15

Hi, I found this in 13.2 prjconf: # On qemu arches, kernel-obs-build does not make any sense # on ARMv7 you can not boot the kernel as a guest, there is a special # guest kernel. Same is true for PPC %ifnarch armv6l armv6hl armv7l armv7hl aarch64 ppc VMinstall: kernel-obs-build %endif first of all, it makes sense to use kernel-obs-build also for qemu to avoid situations like in the last days were the worker host initrd&kernel is not sufficient anymore for building. Just an exportfilter is needed to get the kernel-obs-build package from the right architecture. regarding armv7 and ppc, if there is a special guest kernel, this one should be packaged inside of kernel-obs-build. will try to fix the initrd on the hosts anyway again. But this has limits, since we may can not have a single kernel version for all distros ... -- Adrian Schroeter email: adrian(a)suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 4

[opensuse-arm] openSUSE ARM img compatible with Raspberry Pi 2
by Jimmy PIERRE 06 Mar '15

06 Mar '15

Hi all, I have been having a fight with loads of .xz raw files. Seems that there is an issue somewhere. Would appreciate that you point me to a working img file similar to the one from Bernhard Wiedemans of 2013. My BootCamp starts in less than two hours and I am desparate to show openSUSE on Raspberry Pi 2. Best wishes, 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

6 8

[opensuse-arm] Please create missing _link from u-boot-rpi2 to u-boot in Base:System
by Guillaume Gardet 04 Mar '15

04 Mar '15

Hi, I just updated u-boot to 2015.04-rc3 in Base:System, but we are missing u-boot-rpi2 package which should _link to u-boot. Could you fix this, please? 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] No graphic terminal
by Edgar Dombrowski 01 Mar '15

01 Mar '15

Hi, Raspi-friends. I just installed the OS13.2-JeOs-Build35.1-Version with all the additional software as described in the HCL:RaspberyPi-Homepage. However I could not start the graphic terminal with the command "startx", as this gile is not available. Any advice would be appreciated. Regards Edgar, 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] Wi-Fi connections on Raspberry Pi 1 B
by Freek de Kruijf 27 Feb '15

27 Feb '15

Hi all, I have a strange problem with Wi-Fi connections to two somewhat different Access Points. Both use the same configuration in "YaST network", apart from SSID and IP address. Still the connection does succeed with one AP, but to the other AP it always fails. Using "iwlist wlan0 scan" the only obvious difference is that one reports to use CCMP, the one which succeeds, and the other uses TKIP, which does not succeed. In the information I found on the Internet I see that the configuration for wpa_supplicant may contain information about the support/use of these protocols. However the file /etc/wpa_supplicant/wpa_supplicant.conf does not contain this information, but the process wpa_supplicant has been started with the -u option, which enables a DBus control interface. So I assume that this kind of information will be supplied by wicked. However I can't find if TKIP is supported in openSUSE 13.2 for the the Raspberry Pi. Any information? -- fr.gr. 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

6 8

[opensuse-arm] openSuSE on Raspberry Pi 2 (armv7) when ? or how ?
by Tchelovek 27 Feb '15

27 Feb '15

Hello List, I am using a Raspberry Pi B+ with openSuSE already, now I have acquired a Raspberry Pi 2. Alas openSuSE doesnt seem to be prepared to provide an update to that end. Is anything in the works ? Or can one produce his own version using OBS ? I managed to run B. Wiedemann' s project altimagebuild locally ( with help from Bernhard ) and produce a running armv6 image, alas I lack the knowledge to modify it to match armv7. Any hint is appreciated. I actually run Arch Linux on it, but would really prefer to stick with openSuSE. Tchelovek -- 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] Please accept SR#287941 for JeOS
by Guillaume Gardet 26 Feb '15

26 Feb '15

Hi, could you please accept SR #287941 to get JeOS fixes and enhancements. Guillaume -- 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 Factory ARM DTBs are outdated
by Guillaume Gardet 25 Feb '15

25 Feb '15

Hi, the DTBs in Factory:ARM are all outdated. Could you trigger a rebuild, please? Currently, Beaglebone black does not boot due to a too old DTB (SD card not found). Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 10