Rock4 C+ Unable to get WiFi to work #6935
Comments
|
Many thanks for your report. You tried it via If so, the following command does not list the WiFi adapter, does it? ip lAre there some kernel errors shown? And can you also show the list of loaded kernel modules: dmesg -l 0,1,2,3
lsmodIt can be tested with a newer kernel build we host on our server: cd /tmp
wget https://dietpi.com/downloads/binaries/{linux-{image,dtb}-current-rockchip64.deb,armbian-firmware.deb}
dpkg -i linux-{image,dtb}-current-rockchip64.deb armbian-firmware.deb
rm linux-{image,dtb}-current-rockchip64.deb armbian-firmware.deb
reboot |
|
Correct, tried via dietpi-config ip l: dmesg -l 0,1,2,3 I've tried the commands below, and after reboot I am unable to ssh anymore. Will plug in a mini HDMI and see what shows up in the console |
|
Power off, power on and was able to SSH again, when doing dietpi-config: No WiFi adapter was detected on your device. |
|
Can you check whether the correct device tree is loaded? cat /proc/device-tree/modelEDIT: Interesting. There are two device tree blobs: Here is a patch from Armbian referring the old name: https://github.com/search?q=repo%3Aarmbian%2Fbuild%20rk3399-rock-pi-4c-plus&type=code I'll compare them when I find time, and in case send a PR to Armbian, removing this obsolete patch and/or patching the upstream dts with whichever is needed to fix e.g. onboard WiFi. But let's first see whether even one of those two device trees was picked. And maybe it was the old one (this is chosen by the bootloader in our case), and the new one works better. |
|
cat /proc/device-tree/model |
|
Wrong device tree, that explains it. Try this: G_CONFIG_INJECT 'fdtfile=' 'fdtfile=rockchip/rk3399-rock-4c-plus.dtb' /boot/dietpiEnv.txtA little sad that we then need to offer another dedicated image for this variant, like for the ROCK 4 SE before. Nasty that a single U-Boot build does not support all of them. It did in the past: https://dietpi.com/forum/t/rock-4c-how-do-i-get-the-temperature/17744/6 Can you also do this: sed -i '/^setenv bootargs/s/"$/ variant=${variant} board=${board} model=${model}"/' /boot/boot.cmd
mkimage -C none -A arm64 -T script -d /boot/boot.cmd /boot/boot.scrAnd after a reboot: cat /proc/cmdline |
|
Sorry about the delay but the old board did not boot anymore, so I had to place it. I just ran the following commands which I show below and rebooted. I haven't ssh'd yet but I just notice now the blue led on the board is blinking, it wasn't prior to tehse command and the reboot. root@DietPi:~# G_CONFIG_INJECT 'fdtfile=' 'fdtfile=rockchip/rk3399-rock-4c-plus.dtb' /boot/dietpiEnv.txt
[ OK ] G_CONFIG_INJECT | Added setting fdtfile=rockchip/rk3399-rock-4c-plus.dtb to end of file /boot/dietpiEnv.txt
root@DietPi:~# mkimage -C none -A arm64 -T script -d /boot/boot.cmd /boot/boot.scr
Image Name:
Created: Thu Feb 29 00:51:58 2024
Image Type: AArch64 Linux Script (uncompressed)
Data Size: 2749 Bytes = 2.68 KiB = 0.00 MiB
Load Address: 00000000
Entry Point: 00000000
Contents:
Image 0: 2741 Bytes = 2.68 KiB = 0.00 MiB
root@DietPi:~# cat /proc/cmdline
root=UUID=699a00ce-f9e7-483c-888c-f71a2e182070 rootfstype=ext4 rootwait console=tty1 consoleblank=0 coherent_pool=2M usb-storage.quirks= net.ifnames=0 variant= board=evb_rk3399 model=Now when I run ip l I can see it there!! 3: wlan0: <BROADCAST,MULTICAST> I did proceed to configure via dietpi-config and it WORKS!!!!!!!!!!!!!!!!!!! Thanks a million for always being so supportive! |
|
Can confirm, same behavior on device Doing the exact steps outlined in comment #6935 (comment) resolves both WiFi + HDMI. |
|
Could someone test the new image from here: https://dietpi.com/downloads/images/testing/ |
MichaIng
added
Testing/testers required 🔽
Solution available 🥂
Just managed to get a testing unit now and have some spare time to test. Just to confirm I am downloading this one: https://dietpi.com/downloads/images/testing/DietPi_ROCK4CPlus-ARMv8-Trixie.img.xz Will report once tested. Thanks |
|
Fresh Install, ran dietpi-config then > network options: adapters: WiFi : Not Found | [On] | Disconnected Enter No WiFi adapter was detected on your device. │ |
|
Has the correct device tree been selected? cat /proc/device-tree/model |
|
#root@DietPi:~# cat /proc/device-tree/model Radxa ROCK Pi 4Croot@DietPi:~# |
|
Hmm, the "Plus" is missing. So even that this is a U-Boot build for ROCK 4C Plus in particular, it seems to the the non-Plus device tree. So this does still fix it? G_CONFIG_INJECT 'fdtfile=' 'fdtfile=rockchip/rk3399-rock-4c-plus.dtb' /boot/dietpiEnv.txt
rebootThen I'll hardcode this device tree in our images. |
|
root@DietPi:~# G_CONFIG_INJECT 'fdtfile=' 'fdtfile=rockchip/rk3399-rock-4c-plus.dtb' /boot/dietpiEnv.txt [ OK ] G_CONFIG_INJECT | Added setting fdtfile=rockchip/rk3399-rock-4c-plus.dtb to end of file /boot/dietpiEnv.txt So I immediately notice two things, blue led starts blinking and second my video finally comes up via HDMI cable (I was starting to hesitate about my cable since I did a headless install and fished out the IP by DHCP). I am logging in now and after running dietpi-config: WiFi : Available | [On] | Disconnected Ran an ip add and see wlan0 has a valid IP address, so yeah it fixed a few things. |
|
And it also shows the correct model name? cat /proc/device-tree/model |
|
root@DietPi:~# cat /proc/device-tree/model Radxa ROCK 4C+root@DietPi:~# |
|
Okay great. I'm rebuilding the images. |
|
I moved the images to stable downloads and will add them to our download page now. Marking this as closed. |
Creating a bug report/issue
Required Information
G_DIETPI_VERSION_CORE=9 G_DIETPI_VERSION_SUB=1 G_DIETPI_VERSION_RC=1 G_GITBRANCH='master' G_GITOWNER='MichaIng' G_LIVE_PATCH_STATUS[0]='not applicable'bookworm6.1.63-current-rockchip64 #1 SMP PREEMPT Mon Nov 20 10:52:19 UTC 2023 aarch64 GNU/LinuxROCK 4 (aarch64)or (EG: RPi3)Additional Information (if applicable)
Expected behaviour
-Able to Configure WiFi
Actual behaviour
Extra details
The text was updated successfully, but these errors were encountered: