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