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
Hello,
Just tried latest 316/318 Tumbleweed images for Samsung Chromebook and noticed
that u-boot wont auto load boot.scr now and output contain alot errors
about extlinux pxeboot. If i load boot.scr manualy, with ext2load mmc
1:2 0x50000000 boot.scr and then source 0x50000000 boot starts fine.
Also lcd screen stays black after kernel start, probably some drm
module still missing.
---
Best Regards,
Misha Komarovskiy
zombahatgmaildotcom
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi everyone,
as the RaspberryPI kernel is nowadays "configured" by the device tree, there
are some issues for the current openSUSE images.
By default the dtbs as shipped disable any optional hardware, which is a good
thing. On the other hand things like SPI are no longer working.
Raspbian tackles this with so called overlays and some help from the binary
start.elf bootloader:
1. start.elf reads the dtb from the fat boot partition
a) a file defined in config.txt, "device_tree=foo.dtb"
b) a hardcoded hardware specific default file, "bcm2708-rpi-<variant>.dtb"
2. if the config.txt specifies "dtoverlay=foo-overlay"
1. the boot loader reads "overlays/foo-overlay.dtb" from the fat partition
2. the overlay is patched into the flattened device tree
3. the boot loader puts the device tree at address 0x100 (override with
"device_tree_address=0xabcd1234"
4. the boot loader loads the specified kernel
As openSUSE does not directly jump into the kernel, but starts u-boot, this
does not work here.
Issues:
1. u-boot does not have overlay support
2. u-boot loads its own dtb from storage, e.g. bcm2835-rpi-b.dtb
3. The u-boot boot.scr is loaded at address 0, and overwrites the boot loader
provided dtb.
The 3rd issue can be worked around with a "device_tree_address=0x1000" in
config.txt. I tried to replace the "loadfdt" function in the boot.scr with
a "fdt move 0x1000 0x2000000". Although the move succeeds, the kernel start
crashes afterwards:
----
4443840 bytes read in 1041 ms (4.1 MiB/s)
6946368 bytes read in 1403 ms (4.7 MiB/s)
Copying FDT ...
Kernel image @ 0x1000000 [ 0x000000 - 0x43cec0 ]
data abort
pc : [<17f63d68>] lr : [<17f644e0>]
reloc pc : [<0001dd68>] lr : [<0001e4e0>]
sp : 17b48a50 ip : 17b521e9 fp : 17f51c54
r10: 17f91354 r9 : 17b49ee8 r8 : 17f922bc
r7 : 17f922b8 r6 : 17b521e0 r5 : 00000003 r4 : 33554432
r3 : 00000000 r2 : 00000010 r1 : 00000000 r0 : 33554432
Flags: nZCv IRQs off FIQs off Mode SVC_32
Resetting CPU ...
----
instead of:
----
4443840 bytes read in 1268 ms (3.3 MiB/s)
6946368 bytes read in 1753 ms (3.8 MiB/s)
8127 bytes read in 56 ms (141.6 KiB/s)
Kernel image @ 0x1000000 [ 0x000000 - 0x43cec0 ]
## Flattened Device Tree blob at 02000000
Booting using the fdt blob at 0x2000000
Using Device Tree in place at 02000000, end 02004fbe
----
So either this approach needs more work, or a completely different approach is
needed to get overlays to work.
Any ideas?
Kind regards,
Stefan
--
Stefan Brüns / Bergstraße 21 / 52062 Aachen
home: +49 241 53809034 mobile: +49 151 50412019
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
HI!
It seems kernel 4.1.3 has landed in Factory repo for armv6 but I have some
doubts about package dtb-bcm2835:
v | openSUSE-Factory-repo-oss | dtb-bcm2835 | 4.0.5-41.1
| 4.1.2-45.1 | armv6hl
v | openSUSE-Factory-repo-oss | kernel-default | 4.0.5-3.1
| 4.1.3-1.1 | armv6hl
As you can see its version is 4.1.2-45.1. Does that fit kernel 4.1.3?
Ciao, Michael.
Hello,
After upgrading 13.2 from kernel-lpae-3.16.7-7 to -11/-21 (why is it
installing two new kernels btw?) I no longer have network.
Diagnosing this is difficult because, as reported previously, the kernel
does not provide any serial output to ttyS0. The LED lights up, which is
done by my boot.local script, so it is coming up to some degree, just
not far enough to login via ssh, and it's not reachable by ping either.
I doubt this is just the dtb getting out of sync again?
Originally it was a U-Boot 2014.10, but same with 2015.07 (and still
working with a downgraded kernel/initrd).
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, 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
Hi list,
After rebasing my pi setup on a recent openSUSE image (since I was
using raspberrypi branch kernels), it took me longer than I'm willing
to admit to realize that the B+ needs to use the B+ dtb for things like
USB to work. The kernel does boot with the rpi-b.dtb, but since USB
isn't up the network devices aren't up and you can't plug in a keyboard
to do anything about it.
The ethernet MAC, serial, and revision still aren't being picked up,
but this time I'm going with the ifcfg-eth0 change instead of switching
kernels and editing the boot args.
Have a lot of fun,
Evan
HI!
openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build327.8 does not
work. It soon runs into a "rebootException" after start.
FWIW openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build327.6 seems
to work. Could someone look at the difference(s)?
Ciao, Michael.
I have for many months been trying to build Libreoffice on ARM with no
success. There is a working build of it on Debian so it must be
possible. I suspect the first thing they did is remove a whole bunch of
obscure options that are hardly every used. This would remove
pre-requisite packages and reduce the build time.
I am trying now to build LO 5.0. It runs for a day and then starts over
again. Can someone explain why this never builds?
I am going to look at the package on Debian and see what options they
use and how they break it into sub-packages. Maybe I will try building
the Debian package on the openSuse Build System to see if there is a
problem with the build system.
Any thoughts on this would be appreciated.
Bill
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
When trying to build an updated package which was not available in the
repository I needed the file:
/usr/lib/perl5/5.20.1/armv6l-linux-thread-multi/Fcntl.pm
which gives gives an error
Right after putting the image on the SD card, I mounted the lxroot partition
on /mnt/ll and got the following on the command:
# ls -l /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux-thread-multi/
ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux-
thread-multi/Fcntl.pm: Invoer-/uitvoerfout
ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux-
thread-multi/Config.pod: Invoer-/uitvoerfout
ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux-
thread-multi/Config_git.pl: Invoer-/uitvoerfout
ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux-
thread-multi/.packlist: Invoer-/uitvoerfout
ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux-
thread-multi/Encode.pm: Invoer-/uitvoerfout
ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux-
thread-multi/GDBM_File.pm: Invoer-/uitvoerfout
ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux-
thread-multi/DynaLoader.pm: Invoer-/uitvoerfout
ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux-
thread-multi/Config.pm: Invoer-/uitvoerfout
ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux-
thread-multi/Config_heavy.pl: Invoer-/uitvoerfout
ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux-
thread-multi/DB_File.pm: Invoer-/uitvoerfout
ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux-
thread-multi/Errno.pm: Invoer-/uitvoerfout
ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux-
thread-multi/Cwd.pm: Invoer-/uitvoerfout
ls: kan geen toegang krijgen tot /mnt/ll/usr/lib/perl5/5.20.1/armv6l-linux-
thread-multi/B.pm: Invoer-/uitvoerfout
totaal 428
[....]
-r--r--r-- 1 root root 20519 23 jun 17:39 encoding.pm
-????????? ? ? ? ? ? Errno.pm
-????????? ? ? ? ? ? Fcntl.pm
drwxr-xr-x 3 root root 4096 9 jul 04:38 File
[....]
--
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