FreedomBox testing images are based on Debian testing (Bookworm). Please note that FreedomBox images use vanilla Debian kernels (which are in turn mostly upstream Linux kernels). If upstream kernel has no support for Lamobo R1 network devices, then there is very slim chance that Debian or FreedomBox has support for it.
From what you are reporting, it looks like there is a regression in the kernel sometime between Buster and Bullseye.
Lamobo R1 and the Olimex A20-OLinuXino-Lime2 share many of the same features like: A20 or 1000MBit native Ethernet.
On Buster, the A20 doesn’t use its potential, just 100MBit:
admin@freedombox:~$ ip r
default via 192.168.9.1 dev eth0 proto dhcp metric 100
10.42.0.0/24 dev wan proto kernel scope link src 10.42.0.1 metric 101
10.42.1.0/24 dev wlxaca2135cac7d proto kernel scope link src 10.42.1.1 metric 600
192.168.11.0/24 dev eth0 proto kernel scope link src 192.168.9.14 metric 100
Forgive my ignorance, maybe there is a link where I can read about this?:
Is it possible or forseen to have individual software that is not in the Debian build, like a modul for the BCM53125 PHY (7 port ethernet chip), its Distributed Switch Architecture (DSA) and Realtek rtl WiFi?
Sorry that it took me so long to come back after our chat in the last call, it was a busy week.
I doug out my UART cable and flashed Bullseye and started Lamobo R1.
It doesn’t apply for an IP-Address on the router, so it is impossible to reach the device without UART.
[ 6.139744] bcm53xx stmmac-0:1e: failed to register switch: -517
[ 19.193238] usb 2-1: firmware: failed to load rtlwifi/rtl8192cufw.bin (-2)
…two of the most important modules are missing or failed to load? See my post above for description of the modules. Can you add these to the image?
U-Boot SPL 2021.01+dfsg-5 (May 23 2021 - 04:32:45 +0000)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1
U-Boot 2021.01+dfsg-5 (May 23 2021 - 04:32:45 +0000) Allwinner Technology
CPU: Allwinner A20 (SUN7I)
Model: Lamobo R1
I2C: ready
DRAM: 1 GiB
MMC: mmc@1c0f000: 0
Loading Environment from FAT... Unable to use mmc 0:1... In: serial
Out: serial
Err: serial
Net: eth0: ethernet@1c50000
starting USB...
Bus usb@1c14000: USB EHCI 1.00
Bus usb@1c14400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
scanning bus usb@1c14000 for devices... 1 USB Device(s) found
scanning bus usb@1c14400 for devices... 1 USB Device(s) found
scanning bus usb@1c1c000 for devices... 2 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
2909 bytes read in 1 ms (2.8 MiB/s)
## Executing script at 43100000
5022208 bytes read in 286 ms (16.7 MiB/s)
26960 bytes read in 5 ms (5.1 MiB/s)
23327932 bytes read in 1314 ms (16.9 MiB/s)
Booting Debian 5.10.0-8-armmp-lpae from mmc 0:1...
## Flattened Device Tree blob at 43000000
Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
Loading Ramdisk to 489c0000, end 49fff4bc ... OK
Loading Device Tree to 489b6000, end 489bf94f ... OK
Starting kernel ...
[ 0.006825] /cpus/cpu@0 missing clock-frequency property
[ 0.006870] /cpus/cpu@1 missing clock-frequency property
[ 6.139744] bcm53xx stmmac-0:1e: failed to register switch: -517
/scripts/local-bottom/mdadm: 2: /scripts/local-bottom/mdadm: rm: not found
[ 15.896226] sun4i-drm display-engine: attempt to add DMA range to existing map
[ 15.907217] debugfs: Directory '1c22c00.codec' with parent 'sun4i-codec' already present!
[ 19.176005] usb 2-1: firmware: failed to load rtlwifi/rtl8192cufw_TMSC.bin (-2)
[ 19.183533] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[ 19.193238] usb 2-1: firmware: failed to load rtlwifi/rtl8192cufw.bin (-2)
[ 40.894926] rtl8192c_common: Polling FW ready fail! REG_MCUFWDL:0x00000006.
[ 40.902068] rtl8192c_common: Firmware is not ready to run!
[ 42.458015] rtl8192c_common: Polling FW ready fail! REG_MCUFWDL:0x00000006.
[ 42.465109] rtl8192c_common: Firmware is not ready to run!
Debian GNU/Linux 11 freedombox ttyS0
FreedomBox
To start using FreedomBox and to create an account, access using a web browser
one of the following URLs.
http://freedombox.local/
http://127.0.1.1/
http://[::ffff:127.0.1.1]/
Only administrators can login unless otherwise configured in Security section.
FreedomBox also provides a web console for system administration using Cockpit.
Web console: https://localhost:9090/
freedombox login: [ 46.428213] rtl8192c_common: Polling FW ready fail! REG_MCUFWDL:0x00000006.
[ 46.435301] rtl8192c_common: Firmware is not ready to run!
Debian GNU/Linux 11 freedombox ttyS0
FreedomBox
To start using FreedomBox and to create an account, access using a web browser
one of the following URLs.
http://freedombox.local/
http://10.42.0.1/
http://[fe80::8867:ade:8fed:4a21]/
Only administrators can login unless otherwise configured in Security section.
FreedomBox also provides a web console for system administration using Cockpit.
Web console: https://localhost:9090/
freedombox login:
This firmware file is available in the firmware-realtek package. It is a non-free package, but probably makes sense to include it in the lamobo-r1 image (which would become a non-free image).
Thank you for you message.
I see, but this RTLwifi is not a priority I think - your introduction film explains how to connect a cable to the router, this is where the BCM53 comes into play.
The A20 has only one connection for Ethernet, but the device comes physically with 5-sockets. To serve these ports we have to enable the BCM53125 PHY (7 port ethernet chip). It is controlled/driver via Distributed Switch Architecture (DSA). Because of the ports it needs a sane network config file (which is not so difficult as I have experience from the past).
bcm53xx stmmac-0:1e: failed to register switch:
What is the next step to find out why the bcm failed to register?
Do you guys @jvalleroy , @sunil know who built the image for buster?
Network wise everything works, I even get an access point. Can you point me to the source on gitlab how the image was built?
The kernel was: vmlinuz → boot/vmlinuz-4.19.0-10-armmp-lpae