Hi,
Just asking if this is only me or it's a wider problem: I recently
updated my cubox-i with zypper, pulling in kernel-default-4.4.114, and
after reboot the box boots, but several drivers are missing, so there is
no wired ethernet, no mmcblk, etc.
After booting and waiting for a while, dmesg starts to complain about
driver detection did not finish in time (sadly I don't have the
backtrace at hand, it already went out of the buffer of the serial
console).
For now I worked around the problem this way:
- download the repo-oss (ie. non-update) kernel-default-4.4.76 rpm on an
other machine, copied it to an usb stick
- install the old kernel-default from the usb stick
- copy the /boot from the root fs to the usb stick
- use the other machine to update the /boot on the mmcblk device where
u-boot reads it
So is this only me or do other cubox-i users see the same?
Thanks,
Miklos
I'm getting the error message on ARM builds:
326s] /usr/lib64/gcc/aarch64-suse-linux/7/../../../../aarch64-suse-linux/bin/ld: cannot find -lieee
See
https://build.opensuse.org/package/live_build_log/home:hpcoder1/ecolab/open…
libieee is part of glibc, so should always be available. The
dependency is coming in through the TCL linker flags.
Something is askew with the ARM build service.
--
----------------------------------------------------------------------------
Dr Russell Standish Phone 0425 253119 (mobile)
Principal, High Performance Coders
Visiting Senior Research Fellow hpcoder(a)hpcoders.com.au
Economics, Kingston University http://www.hpcoders.com.au
----------------------------------------------------------------------------
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
mono-core build fails for AArch64 in OBS due to an unhandled exception. Log: [1]
Locally it builds fine with "osc build", both chroot and KVM. Any idea what could be wrong with the OBS workers?
Guillaume
[1]: https://build.opensuse.org/build/openSUSE:Factory:ARM/standard/aarch64/mono…
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
Some ARM images are failing to build because they run out of disk space.
Is the _constraints file working for kiwi image builds in OBS?
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
Currently, some packages are failing in Factory ARM (aarch64 and armv6 only, armv7 seems to be ok) because of wrong rpmlint errors on licenses such as :
invalid-license (Badness: 100000) GPL-2.0-or-later
I guess rpmlint used on OBS workers for aarch64 and armv6 should be updated?
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
I used to download files with names openSUSE...Current.raw.xz.sha256 and found
in line 4 not only the sha256 sum but also the name of the image with the date
and Build number followed the sha256 sum.
At least for Tumbleweed-ARM-JeOS for Raspberry Pi 1 and 2 this is no longer
the case. Only the sha256 sum is present. For the Raspberry Pi 3 this still is
the case.
Is it possible to include that name in the ...Current.raw.xz.sha256 files?
--
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
I used image openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.aarch64-2018.02.02-
Build1.2.raw.xz to build a new Raspberry Pi 3B system and performed a "zypper
dup --no-recommends" to TW20180305. Even before a reboot zypper does not work
anymore. It stops on a segmantation fault. The basic system seems to work OK.
However using git gives a coredump of git. Also wget. However rsync, which I
installed before the upgrade still works. So I downloaded
strace-4.21-1.1.aarch64.rpm and used rsync to get it in the RPi3. I installed
it and used "strace zypper se git" to get an strace. Did not give a clue to me
about what caused the segmentation fault. Last part is:
write(3, "2018-03-12 12:02:53 <1> rpi3tumh"..., 164) = 164
openat(AT_FDCWD, "/dev/null", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 4
openat(AT_FDCWD, "/var/lib/YaST2/cookies", O_RDONLY) = -1 ENOENT (No such file
or directory)
mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) =
0xffff870a6000
mprotect(0xffff870a7000, 8388608, PROT_READ|PROT_WRITE) = 0
clone(child_stack=0xffff878a3820, flags=CLONE_VM|CLONE_FS|CLONE_FILES|
CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|
CLONE_CHILD_CLEARTID, parent_tidptr=0xffff878a3fe0, tls=0xffff878a4600,
child_tidptr=0xffff878a3fe0) = 1045
ppoll(NULL, 0, {tv_sec=0, tv_nsec=4000000}, NULL, 0) = 0 (Timeout)
ppoll(NULL, 0, {tv_sec=0, tv_nsec=8000000}, NULL, 0) = 0 (Timeout)
ppoll(NULL, 0, {tv_sec=0, tv_nsec=16000000}, NULL, 0 <unfinished ...>) = ?
+++ killed by SIGSEGV (core dumped) +++
Bug report: https://bugzilla.opensuse.org/show_bug.cgi?id=1084796
I do have coredumps and can produce a full strace.
Please advice.
--
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
... and the last published snapshot is Build20170831. This may be related.
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