Comments (19)
Could someone test the new image from here: https://dietpi.com/downloads/images/testing/ It uses a new ROCK 4C Plus U-Boot build, which selects the right device tree automatically.
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
from dietpi.
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:~# reboot
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.
Please let me know if you want me to test any further
from dietpi.
Okay great. I'm rebuilding the images.
from dietpi.
I moved the images to stable downloads and will add them to our download page now. Marking this as closed.
from dietpi.
Many thanks for your report.
You tried it via dietpi-config
, right? Because some WiFi-related kernel modules are blacklisted by default, and need to be loaded first.
If so, the following command does not list the WiFi adapter, does it?
ip l
Are there some kernel errors shown? And can you also show the list of loaded kernel modules:
dmesg -l 0,1,2,3
lsmod
It 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
from dietpi.
Correct, tried via dietpi-config
ip l:
1: lo: <LOOPBACK,UP,LOWER_UP>
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP>
dmesg -l 0,1,2,3
[ 1.601255] dw-apb-uart ff180000.serial: Failed to create device link (0x180) with 0-001b
[ 1.764960] dw-apb-uart ff180000.serial: Failed to create device link (0x180) with vcc3v3-sys
[ 1.930008] rk808 0-001b: failed to read the chip id at 0x17
[ 7.122682] es8316 1-0011: ASoC: error at soc_component_write_no_lock on es8316.1-0011 for register: [0x00000000] -6
[ 7.143217] es8316 1-0011: ASoC: error at soc_component_write_no_lock on es8316.1-0011 for register: [0x00000000] -6
[ 7.184481] es8316 1-0011: ASoC: error at soc_component_write_no_lock on es8316.1-0011 for register: [0x0000000c] -6
[ 7.186518] es8316 1-0011: ASoC: error at soc_component_write_no_lock on es8316.1-0011 for register: [0x00000003] -6
[ 7.188760] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000022] -6
[ 7.190256] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000022] -6
[ 7.190612] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000025] -6
[ 7.192234] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000030] -6
[ 7.194809] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000013] -6
[ 7.198119] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000013] -6
[ 7.199856] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000014] -6
[ 7.200177] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000014] -6
[ 7.200875] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000014] -6
[ 7.201130] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000014] -6
[ 7.203147] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x00000009] -6
[ 7.203428] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x0000000a] -6
[ 7.203643] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x0000000b] -6
[ 7.203846] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x00000001] -6
[ 7.226889] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000000d] -6
[ 7.232023] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000000d] -6
[ 7.232756] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000000d] -6
[ 7.233174] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000022] -6
[ 7.234128] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000000d] -6
[ 7.234435] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000000d] -6
[ 7.234962] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000001] -6
[ 7.235351] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000022] -6
[ 7.235794] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000022] -6
[ 7.237306] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000025] -6
[ 7.238718] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000000a] -6
[ 7.239092] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000030] -6
[ 7.239428] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000000d] -6
[ 7.239690] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000001] -6
[ 7.239940] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000002f] -6
[ 7.240241] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000002f] -6
[ 7.240717] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000013] -6
[ 7.241122] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000013] -6
[ 7.241669] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000015] -6
[ 7.242057] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000015] -6
[ 7.242365] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000015] -6
[ 7.242617] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000015] -6
[ 7.242871] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000017] -6
[ 7.243296] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000017] -6
[ 7.243563] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000001a] -6
[ 7.243878] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000001] -6
[ 7.244182] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000017] -6
[ 7.244482] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000017] -6
[ 7.244762] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000019] -6
[ 7.245030] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000018] -6
[ 7.245290] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000018] -6
[ 7.245924] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x00000017] -6
[ 7.246165] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x00000015] -6
[ 7.246392] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x0000002f] -6
[ 7.246623] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x00000001] -6
[ 7.246854] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x0000000d] -6
[ 7.247261] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x00000019] -6
Module Size Used by
cfg80211 946176 0
rfkill 32768 2 cfg80211
snd_soc_simple_card 24576 0
snd_soc_audio_graph_card 20480 0
snd_soc_spdif_tx 16384 0
snd_soc_es8316 45056 1
snd_soc_rockchip_i2s 28672 2
rockchip_rng 20480 0
snd_soc_simple_card_utils 28672 2 snd_soc_audio_graph_card,snd_soc_simple_card
panfrost 69632 0
rng_core 20480 1 rockchip_rng
gpu_sched 49152 1 panfrost
snd_soc_core 270336 6 snd_soc_spdif_tx,snd_soc_audio_graph_card,snd_soc_simple_card_utils,snd_soc_rockchip_i2s,snd_soc_simple_card,snd_soc_es8316
drm_shmem_helper 24576 1 panfrost
hantro_vpu 139264 0
rockchip_rga 20480 0
rockchip_vdec 45056 0
snd_compress 24576 1 snd_soc_core
v4l2_vp9 24576 2 rockchip_vdec,hantro_vpu
snd_pcm_dmaengine 16384 1 snd_soc_core
videobuf2_dma_contig 24576 2 rockchip_vdec,hantro_vpu
snd_pcm 131072 5 snd_compress,snd_soc_simple_card_utils,snd_soc_core,snd_soc_es8316,snd_pcm_dmaengine
v4l2_h264 20480 2 rockchip_vdec,hantro_vpu
snd_timer 40960 1 snd_pcm
snd 98304 4 snd_timer,snd_compress,snd_soc_core,snd_pcm
videobuf2_dma_sg 16384 1 rockchip_rga
soundcore 16384 1 snd
v4l2_mem2mem 36864 3 rockchip_vdec,hantro_vpu,rockchip_rga
videobuf2_memops 20480 2 videobuf2_dma_contig,videobuf2_dma_sg
videobuf2_v4l2 32768 4 rockchip_vdec,hantro_vpu,rockchip_rga,v4l2_mem2mem
videobuf2_common 61440 8 rockchip_vdec,videobuf2_dma_contig,videobuf2_v4l2,hantro_vpu,rockchip_rga,videobuf2_dma_sg,v4l2_mem2mem,videobuf2_memops
videodev 258048 6 rockchip_vdec,videobuf2_v4l2,hantro_vpu,rockchip_rga,videobuf2_common,v4l2_mem2mem
mc 65536 6 rockchip_vdec,videodev,videobuf2_v4l2,hantro_vpu,videobuf2_common,v4l2_mem2mem
cpufreq_dt 20480 0
dm_mod 143360 0
ip_tables 32768 0
x_tables 45056 1 ip_tables
autofs4 45056 2
realtek 32768 1
dwmac_rk 32768 0
stmmac_platform 24576 1 dwmac_rk
stmmac 237568 3 stmmac_platform,dwmac_rk
pcs_xpcs 20480 1 stmmac
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
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
from dietpi.
Power off, power on and was able to SSH again, when doing dietpi-config:
No WiFi adapter was detected on your device.
from dietpi.
Can you check whether the correct device tree is loaded?
cat /proc/device-tree/model
EDIT: Interesting. There are two device tree blobs: rk3399-rock-pi-4c-plus.dtb
following the old naming, and rk3399-rock-4c-plus.dtb
following the new one. I guess some recent changes or fixes are applied to only one of them, but not sure which one. And also not sure which one the bootloader picks. Found some issue on Armbian's GitHub, stating that with the old one it does not boot anymore, but only with the new one. But there was no more investigation done, e.g. whether some patches apply to the old one etc. Quite possible that this is the reason why some things do not work anymore. Upstream linux contains the new one only, as well on Linux 6.1: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm64/boot/dts/rockchip?h=linux-6.1.y
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
Also present on all newer kernel versions: https://github.com/armbian/build/blob/main/patch/kernel/archive/rockchip64-6.1/add-board-rock-pi-4c-plus.patch
This is the reason why there are two device trees. While upstream ships a new device tree now, it is possible that the one from Armbian has some additional features. But it does not boot anymore, at least not with newer Linux versions.
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.
from dietpi.
cat /proc/device-tree/model
Radxa ROCK Pi 4Broot@
from dietpi.
Wrong device tree, that explains it. Try this:
G_CONFIG_INJECT 'fdtfile=' 'fdtfile=rockchip/rk3399-rock-4c-plus.dtb' /boot/dietpiEnv.txt
A 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
But we could at least check whether there is a variable in the U-Boot environment, like $variant
, $model
or $board
, which indicates the variant, so we could select the correct device tree dynamically in our boot.scr
.
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.scr
And after a reboot:
cat /proc/cmdline
from dietpi.
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!
from dietpi.
Can confirm, same behavior on device Radxa ROCK 4C+
. Brand new install with latest version (9.2) using image https://dietpi.com/downloads/images/DietPi_ROCKPi4-ARMv8-Bookworm.img.xz
Doing the exact steps outlined in comment #6935 (comment) resolves both WiFi + HDMI.
root@DietPi:~# dmesg -l 0,1,2,3
[ 1.025561] spi-nor spi0.0: unrecognized JEDEC id bytes: ff ff ff ff ff ff
[ 1.746125] rk8xx-i2c 0-001b: Failed to set masks in 0x4d: -6
[ 1.746666] rk8xx-i2c 0-001b: error -ENXIO: Failed to add irq_chip
[ 7.183139] es8316 1-0011: ASoC: error at soc_component_write_no_lock on es8316.1-0011 for register: [0x00000000] -6
[ 7.190210] es8316 1-0011: ASoC: error at soc_component_write_no_lock on es8316.1-0011 for register: [0x00000000] -6
[ 7.232932] es8316 1-0011: ASoC: error at soc_component_write_no_lock on es8316.1-0011 for register: [0x0000000c] -6
[ 7.234261] es8316 1-0011: ASoC: error at soc_component_write_no_lock on es8316.1-0011 for register: [0x00000003] -6
[ 7.235887] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000022] -6
[ 7.237890] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000022] -6
[ 7.239163] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000025] -6
[ 7.240398] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000030] -6
[ 7.242180] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000013] -6
[ 7.244353] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000013] -6
[ 7.245688] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000014] -6
[ 7.247538] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000014] -6
[ 7.248526] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000014] -6
[ 7.248770] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000014] -6
[ 7.250207] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x00000009] -6
[ 7.252135] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x0000000a] -6
[ 7.253646] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x0000000b] -6
[ 7.254920] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x00000001] -6
[ 7.264413] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000000d] -6
[ 7.266940] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000000d] -6
[ 7.268716] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000000d] -6
[ 7.270207] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000022] -6
[ 7.271880] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000000d] -6
[ 7.273755] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000000d] -6
[ 7.275508] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000001] -6
[ 7.277140] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000022] -6
[ 7.279307] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000022] -6
[ 7.281283] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000025] -6
[ 7.282907] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000000a] -6
[ 7.284382] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000030] -6
[ 7.286104] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000000d] -6
[ 7.289833] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000001] -6
[ 7.291616] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000002f] -6
[ 7.293358] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000002f] -6
[ 7.294770] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000013] -6
[ 7.296167] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000013] -6
[ 7.298437] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000015] -6
[ 7.299837] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000015] -6
[ 7.301327] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000015] -6
[ 7.302820] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000015] -6
[ 7.304091] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000017] -6
[ 7.305605] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000017] -6
[ 7.307242] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x0000001a] -6
[ 7.308804] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000001] -6
[ 7.311306] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000017] -6
[ 7.313859] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000017] -6
[ 7.315347] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000019] -6
[ 7.316685] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000018] -6
[ 7.317958] es8316 1-0011: ASoC: error at soc_component_read_no_lock on es8316.1-0011 for register: [0x00000018] -6
[ 7.319611] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x00000017] -6
[ 7.321476] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x00000015] -6
[ 7.323314] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x0000002f] -6
[ 7.325559] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x00000001] -6
[ 7.327951] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x0000000d] -6
[ 7.329781] es8316 1-0011: ASoC: error at snd_soc_component_update_bits on es8316.1-0011 for register: [0x00000019] -6
root@DietPi:~# cat /proc/device-tree/model
Radxa ROCK Pi 4B
root@DietPi:~# G_CONFIG_INJECT 'fdtfile=' 'fdtfile=rockchip/rk3399-rock-4c-plus.dtb' /boot/dietpiEnv.txtot/dietpiEnv.txt
[ OK ] G_CONFIG_INJECT | Added setting fdtfile=rockchip/rk3399-rock-4c-plus.dtb to end of file /boot/dietpiEnv.txt
root@DietPi:~# sed -i '/^setenv bootargs/s/"$/ variant=${variant} board=${board} model=${model}"/' /boot/boot.cmd
root@DietPi:~# mkimage -C none -A arm64 -T script -d /boot/boot.cmd /boot/boot.scr
Image Name:
Created: Fri Apr 5 15:25:36 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=ae38a42e-5770-46b5-b4ba-970dfa3e50a0 rootfstype=ext4 rootwait console=ttyS2,1500000 console=tty1 consoleblank=0 coherent_pool=2M usb-storage.quirks= net.ifnames=0
root@DietPi:~#
from dietpi.
Could someone test the new image from here: https://dietpi.com/downloads/images/testing/
It uses a new ROCK 4C Plus U-Boot build, which selects the right device tree automatically.
from dietpi.
Fresh Install, ran dietpi-config then > network options: adapters:
WiFi : Not Found | [On] | Disconnected
Enter
No WiFi adapter was detected on your device. │
│ │
│ Would you like to disable WiFi? │
│ - NB: Connections may drop!
from dietpi.
Has the correct device tree been selected?
cat /proc/device-tree/model
from dietpi.
#root@DietPi:~# cat /proc/device-tree/model
Radxa ROCK Pi 4Croot@DietPi:~#
from 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
reboot
Then I'll hardcode this device tree in our images.
from dietpi.
And it also shows the correct model name?
cat /proc/device-tree/model
from dietpi.
root@DietPi:~# cat /proc/device-tree/model
Radxa ROCK 4C+root@DietPi:~#
from dietpi.
Related Issues (20)
- dietpi-letsencrypt installation HOT 3
- DietPi-Software | Add desktop selection to main menu
- Can't update Jellyfin HOT 4
- Motioneye Telegram notification error HOT 1
- Radxa Rock 3B
- Errors were encountered while processing: raspi-firmware E: Sub-process /usr/bin/dpkg returned an error code (1) HOT 4
- Error caused by update to v9.4.2 and by Dietpi-Software install attempt HOT 12
- Odroid C1 | USB ports are not functional HOT 1
- Dietpi on Rockchip RK3066 HOT 1
- LUKS on Pine64 Quartz64 Model A not working HOT 3
- Portainer / Docker Odroid C4 fails HOT 2
- Dietpi-Software installs microblog.pub instead of build-essential package HOT 3
- Mediawiki: Image upload with default installation not possible HOT 4
- Gen. x86 PC ISO installer should detect when running in a VM, not print CPU temp HOT 2
- Open Beta v9.5 | Please help testing and hardening our upcoming release HOT 1
- Home Assistant is missing dependency HOT 1
- dietpi-update error while upgrading to latest DietPi version HOT 4
- Docker pull error on Pine64 Quartz64 Model A HOT 3
- /boot not mounted by PARTUUID HOT 3
- System gets stuck when initiating a reboot (x86_64/EFI/Bookworm) HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dietpi.