Image | Radxa ROCK 3B #7327
Labels
Milestone
Comments
|
That Radxa package sudo mkdir -p /usr/share/sddm/themes/breeze
sudo touch /usr/share/sddm/themes/breeze/Main.qml
sudo apt purge radxa-sddm-theme
sudo rmdir -p /usr/share/sddm/themes/breeze |
|
I did as requested, with slight changes: root@rock-3b:/tmp/DietPi-Installer# sudo mkdir -p /usr/share/sddm/themes/breeze Afterwards the install is successful but I lose my two onboard NICs, the wlan is still ok, but I get some errors on the bluetooth side.. I've got the dmseg output linked. I tried to install the audio, but failed also. |
|
I know that, the board is in the kernel https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm64/boot/dts/rockchip/rk3568-rock-3b.dts since v6.10... If yes which binary should I use ? |
|
Why did you use a vendor image, and not our ROCK 3A image? While it can work with any pre-image, there is not guarantee, as especially these vendor images are pretty messy and kinda malformed often. The Radxa package which tries to remove a non-existing file and even fails to uninstall completely, if that file does not exist, is a prefect example. Please try our image first, before we start to debug an issue which might be entirely related to the vendor pre-image, like faulty firmware placed into the filesystem without APT package reference and such stuff. |
|
I used the vendor image because the Rock 3B is not supported nor proposed to be downloaded, only the Rock 3A. They do share the same CPU but the 3B has two NICs instead of one. Also there's the fact that for instance , there's a difference of implementation of the DRAM on the Rock 4 and Rock 4SE, I figured that I should choose the generic device road to be sure. I'll try the Rock 3A firmware on it and will give you the feedback. |
|
Ah right, I missed the little important difference 3A and 3B 😉. Hmm, based on your logs, I guess the Debian Bookworm firmware packages cause the issue, as the Radxa image contains However, I'd try something different, as you recognised, mainline Linux supports this SBC already. Do you have a WiFi adapter at hand, to establish Internet access with that one temporarily? If so:
If this works, we can add some preliminary support to DietPi. If upstream U-Boot supports it as well, we can add support to our Armbian fork natively. |
|
It happens 😄 |
|
Okay, kernel build has finished, hence this could be tried now. |
|
Using the Rock 3A image is fine as far as:
|
|
Did you upgrade the kernel first, and does it contain the expected device tree? ls -l /boot/dtb/rockchip/rk3568-rock-3b.dtbAh shit, my mistake, I built the ... build running: https://github.com/MichaIng/DietPi/actions/runs/12547993860 |
|
Its partially ok now :
Thi here's the journactl : |
|
|
|
@Joulinar : I wasn't aware of that, my bad. Report: Below I've got the two NICs plugged to my router, only eth0 aka eth2 physically is up. Even with a fresh restart eth1 aka eth1 physically stays down. |
|
Here's more info : lsmod : from the vendor image : journalctl : |
|
For the second adapter, you could define in a own config, like: cat << '_EOF_' > /etc/network/interfaces.d/eth1.conf
allow-hotplug eth1
iface eth1 inet static
address 192.168.1.100/24
_EOF_
systemctl daemon-reload
ifup eth1depending on what you aim to do with it. |
|
I plan to either use it as a WAN or LAN port for a firewall, or with eth0 as a part of a etherchannel / LACP port, not quite sure yet... |
|
Yeah, above just an example. |
|
I tried your solution, the adapter won't show up, only eth0 & the wlan are available |
|
after a check, I discovered that : I manually modified the last line to fdtfile=rockchip/rk3568-rockb-3.dtb , now I've got my two NICs present, but only one up, despite both cables plugged. I tried to use nmcli to turn on the NICs to no avail : |
|
Great. So we can add support for the SBC in general, using ROCK 3A bootloader and adjusting the device tree only. Of course a ROCK 3B bootloader would be better, for network boot capabilities, but a rare use case. |
|
Is there some benchmark or or test or procedure that I can do, for you to validate the support of the board ? |
|
Not really needed. If it boots and those hardware features which differ from the ROCK 3A work, then all is good. |
|
So it's 99.9% OK as I can't use both NICs at the same time yet... |
|
But both do now show up in |
|
Yes they do. I tried the method you provided / tried with nmcli / mntui , they do both appear when I use Those are when only eth1 is plugged : Also when I try to activate eth1 with nmtui it fails |
|
How did you try to configure |
|
I used your method ` dmesg : journalctl |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Details:
apt-get -y autopurge gawk original-awkLinux rock-3b 5.10.160-18-rk356x #425b07550 SMP Thu Oct 12 08:48:55 UTC 2023 aarch64 GNU/Linuxarm64Steps to reproduce:
Expected behaviour:
Actual behaviour:
Extra details:
Additional logs:
log_failed_install_Rock3B.txt
The text was updated successfully, but these errors were encountered: