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 noticed a number of images/support for Banana Pi systems having an armv7
type processor architecture. Also using names with sinovoipbpi in the name of
the image.
This name is also present in information about the Banana Pi M64 of which the
processor architecture is aarch64. There is even an openSUSE Tumbleweed image,
dating a year back, which runs on this system.
Will there be support for the Banana Pi M64 with a more recent image? It does
seem very complicated to have such an image available in the ports repository
for aarch64.
--
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
----- Axel Braun <docb(a)opensuse.org> a écrit :
> Am Dienstag, 30. Oktober 2018, 15:24:47 CET schrieb Guillaume GARDET:
> > Hi,
> >
> > Which Raspberry Pi is it? Model 2B, 3B or 3B+ ?
>
> I'm not sure, it may be a 3B or 3B+
> hwinfo does not answert this. Can I see this on the CPU revision?
It is written on the board itself.
Guillaume
>
> Thx
> Axel
>
>
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Am Dienstag, 30. Oktober 2018, 15:48:48 CET schrieb Brüns, Stefan:
> On Dienstag, 30. Oktober 2018 15:15:38 CET Axel Braun wrote:
> > Hi,
> >
> > I installed a new image with LXQT desktop today, together with falkon as
> > browser.
> >
> > When calling it, it crashes. From the command line:
> > linux:~ # falkon
> > libEGL warning: DRI2: failed to authenticate
>
> > [1030/140331.137334:WARNING:stack_trace_posix.cc(648)] Failed to open
file:
> ...
>
> > [1867:1896:1030/140331.881644:ERROR:gl_implementation.cc(246)] Failed to
> > load /usr/bin/libGLESv2.so: /usr/bin/libGLESv2.so: cannot open shared
>
> Tries to load a shared library from /usr/bin ...
>
> > object file: No such file or directory
> > Falkon: 1 extensions loaded
> > [1867:1896:1030/140342.503582:ERROR:gl_surface_qt.cpp(701)] Requested
> > OpenGL implementation is not supported. Implementation: 0
> > *** stack smashing detected ***: <unknown> terminated
> > Received signal 6
> > #0 0xffff8
> > [end of stack trace]
> > Calling _exit(1). Core file will not be generated.
> > linux:~ #
> >
> > I installed Mesa-libGLESv2-2, but that did not fix it.
> > Any ideas? Bugreport?
>
> You can try - **as a temporary hack** - if symlinking libGLESv2 works.
ln -s /usr/lib64/libGLESv2.so.2 /usr/bin/libGLESv2.so
-> now it does not find the next library /usr/bin/libEGL.so
After creating this symlink it starts!
>
> The next question is which part of Falkon tries to open the library. ldd may
> give you some hints. Next, try "grep libGLESv2.so" on the binary and linked
> libraries.
linux:~ # ldd /usr/bin/falkon | grep libGLESv2.so
libGLESv2.so.2 => /usr/lib64/libGLESv2.so.2 (0x0000ffff87595000)
Does that help?
Cheers
Axel
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
I Installed a new image with LXQT desktop today, and ran an update afterwards.
After the reboot the DNS did not work anymore. TCP/IP itself was working.
Wicked was set by default.
After changing the network to Networkmanager and another reboot it worked
again.
Is wicked broken?
Cheers
Axel
--
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 update my 42.3 cubietruck to leap 15, but it seems the
current image does not work, it's end up on on
"[ OK ] Reached target Remote File Systems.".
I tried this several times with different SD cards - always the same
(sha256 on the image is OK).
The tumbleweed image boots fine, it stops for a while on the same stage
on the first boot, but has an additional line on the serial console:
...
"[ OK ] Reached target Remote File Systems."
Starting dracut pre-mount hook..."
then it continues with expanding the disk.
Here the full serial output from the leap15 boot:
U-Boot SPL 2018.03 (Apr 12 2018 - 15:19:29 +0000)
DRAM: 2048 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1
U-Boot 2018.03 (Apr 12 2018 - 15:19:29 +0000) Allwinner Technology
CPU: Allwinner A20 (SUN7I)
Model: Cubietech Cubietruck
I2C: ready
DRAM: 2 GiB
MMC: SUNXI SD/MMC: 0
Loading Environment from FAT... *** Warning - bad CRC, using default
environment
Failed (-5)
Loading Environment from MMC... *** Warning - bad CRC, using default
environment
Failed (-5)
Setting up a 1024x768 vga console (overscan 0x0)
In: serial
Out: vga
Err: vga
Allwinner mUSB OTG (Peripheral)
SCSI: Target spinup took 0 ms.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Net: eth0: ethernet@01c50000
Warning: usb_ether using MAC address from ROM
, eth1: usb_ether
starting USB...
USB0: USB EHCI 1.00
USB1: USB OHCI 1.0
USB2: USB EHCI 1.00
USB3: USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2576 bytes read in 21 ms (119.1 KiB/s)
## Executing script at 43100000
switch to partitions #0, OK
mmc0 is current device
6956352 bytes read in 725 ms (9.1 MiB/s)
22721440 bytes read in 1520 ms (14.3 MiB/s)
52901 bytes read in 240 ms (214.8 KiB/s)
## Flattened Device Tree blob at 43000000
Booting using the fdt blob at 0x43000000
Using Device Tree in place at 43000000, end 4300fea4
Starting kernel ...
Welcome to openSUSE Leap 15.0 dracut-044-lp150.13.3 (Initramfs)!
[ OK ] Listening on udev Control Socket.
[ OK ] Listening on Journal Socket (/dev/log).
[ OK ] Reached target Local File Systems.
[ OK ] Listening on Journal Socket.
[ OK ] Reached target Swap.
[ OK ] Created slice System Slice.
Starting dracut cmdline hook...
[ OK ] Reached target Slices.
Starting Create list of required st�.|ce nodes for the current
kernel...
[ OK ] Reached target Timers.
[ OK ] Listening on Journal Audit Socket.
Starting Journal Service...
[ OK ] Started Dispatch Password Requests to Console Directory Watch.
[ OK ] Reached target Encrypted Volumes.
[ OK ] Reached target Paths.
[ OK ] Listening on udev Kernel Socket.
[ OK ] Reached target Sockets.
Starting Load Kernel Modules...
[ OK ] Started Journal Service.
[ OK ] Started Create list of required sta�.|vice nodes for the
current kernel.
Starting Create Static Device Nodes in /dev...
[ OK ] Started Load Kernel Modules.
Starting Apply Kernel Variables...
[ OK ] Started Create Static Device Nodes in /dev.
[ OK ] Started Apply Kernel Variables.
[ OK ] Started dracut cmdline hook.
Starting dracut pre-udev hook...
[ OK ] Started dracut pre-udev hook.
Starting udev Kernel Device Manager...
[ OK ] Started udev Kernel Device Manager.
Starting dracut pre-trigger hook...
[ OK ] Started dracut pre-trigger hook.
Starting udev Coldplug all Devices...
Mounting Kernel Configuration File System...
[ OK ] Started udev Coldplug all Devices.
[ OK ] Mounted Kernel Configuration File System.
[ OK ] Reached target System Initialization.
[ OK ] Reached target Basic System.
Starting dracut initqueue hook...
[ OK ] Found device
/dev/disk/by-uuid/fe3ad73f-0035-4969-9a3f-479234fd9162.
[ OK ] Reached target Initrd Root Device.
[ OK ] Started dracut initqueue hook.
Starting dracut pre-mount hook...
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Reached target Remote File Systems.
Any ideas what to do ?
Best regards
Karsten
--
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 that I have been hit by GnuTLS bug which is already fixed in
Tumbleweed for x86_64 but not for armv7.
Fixes I need are with changelog
* Fri Sep 14 2018 Luis Henriques <lhenriques(a)suse.com>
- Backport of upstream fixes (boo#1108450)
* gnutls-3.6.3-backport-upstream-fixes.patch
Fixes taken from upstream commits:
* * 3df5b7bc8a64 ("cert-cred: fix possible segfault when resetting cert retrieval function")
* * 42945a7aab6d ("allow no certificates to be reported by the gnutls_certificate_retrieve_function callbacks")
* * 10f83e36ed92 ("hello_ext_parse: apply the test for pre-shared key ext being last on client hello")
The patch was taken from https://github.com/weechat/weechat/issues/1231
I don't want to rebuild subtree of system which uses gnutls just for myself.
Do you have idea when next snapshot could be available?
Hello,
I am (stilL) trying to boot openSUSE on Rock64. I use JeOS image from
Contrib:Rockchip and manually built bootloader (with
0001-XXX-openSUSE-XXX-Prepend-partition-.patch). And currently I see the
following new issue:
mmc1 is current device
Scanning mmc 1:2...
52462 bytes read in 43 ms (1.2 MiB/s)
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Scanning mmc 1:1...
Found EFI removable media binary efi/boot/bootaa64.efi
reading efi/boot/bootaa64.efi
1247744 bytes read in 58 ms (20.5 MiB/s)
## Starting EFI application at 02000000 ...
Card did not respond to voltage select!
mmc_init: -95, time 10
Scanning disk rksdmmc(a)ff520000.blk...
Scanning disk rksdmmc(a)ff500000.blk...
Found 2 disks
Welcome to GRUB!
ethernet@ff540000 Waiting for PHY auto negotiation to complete.........
TIMEOUT !
Could not initialize PHY ethernet@ff540000
GNU GRUB version 2.02
Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists possible
device or file completions.
grub>
I see that both dtb file and EFI GRUB executable are loaded. But instead
of GRUB menu I see GRUB command line. I suppose it means that grub
failed to fetch GRUB configuration. How could I debug further what is wrong?
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org