You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can't connect to my RockPi 4C through WiFi IPv4. I got only IPv6 with the new system image but I use in my network IPv4 and I don't want to change this. Also there a lot of driver fails and log spam in the serial console, so it's hard to do anything there.
BTW: I also tested the Android 10 for RockPi 4c https://rock.sh/rockpi4c-android10-gpt-download with my RPI DSI display which working on RPI. The Download description shows 'DSI 480P: Canvas size 480800 Support Raspberry Pi official 7" Display' but the screen leave black and off. In the log through serial console shows some errors in the dw-drm-mipi-dsi layer. Some OF(DTS) properties/phandles not found i.e. 'rockchip,grf'. It seems to be incomplete buggy DTS binding or dw--drm implementation.
I'm frustrated with the HW/OS I bought:
I would be very happy about a production-ready 'consumer'-compatible operating system. I finally want to finish my project without operating system development or kernel error analysis. After all, I bought hardware for cash on the assumption, as described on the website, that it works with the connections listed. Of course, this also includes a functioning operating system, as is generally the case.
Dear Staff
I installed the RockPi 4C with the image (- the 3rd image test): https://dl.radxa.com/rockpi/images/ubuntu/rockpi4c_ubuntu_focal_minimal_arm64_20200820_1207-gpt.img.gz
I can't connect to my RockPi 4C through WiFi IPv4. I got only IPv6 with the new system image but I use in my network IPv4 and I don't want to change this. Also there a lot of driver fails and log spam in the serial console, so it's hard to do anything there.
BTW: I also tested the Android 10 for RockPi 4c https://rock.sh/rockpi4c-android10-gpt-download with my RPI DSI display which working on RPI. The Download description shows 'DSI 480P: Canvas size 480800 Support Raspberry Pi official 7" Display' but the screen leave black and off. In the log through serial console shows some errors in the dw-drm-mipi-dsi layer. Some OF(DTS) properties/phandles not found i.e. 'rockchip,grf'. It seems to be incomplete buggy DTS binding or dw--drm implementation.
I'm frustrated with the HW/OS I bought:
I would be very happy about a production-ready 'consumer'-compatible operating system. I finally want to finish my project without operating system development or kernel error analysis. After all, I bought hardware for cash on the assumption, as described on the website, that it works with the connections listed. Of course, this also includes a functioning operating system, as is generally the case.
LOG ---------------------------------------
[ 4.037632] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
[ 4.209574] rk3x-i2c ff110000.i2c: timeout, ipd: 0x00, state: 1
[ 5.213575] rk3x-i2c ff110000.i2c: timeout, ipd: 0x00, state: 1
[ 6.041658] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
[ 6.213573] rk3x-i2c ff110000.i2c: timeout, ipd: 0x00, state: 1
[ 7.217576] rk3x-i2c ff110000.i2c: timeout, ipd: 0x00, state: 1
[ 8.217574] rk3x-i2c ff110000.i2c: timeout, ipd: 0x00, state: 1
[ 9.253583] rk3x-i2c ff110000.i2c: timeout, ipd: 0x00, state: 1
[ 10.045616] cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2
[ 10.253577] rk3x-i2c ff110000.i2c: timeout, ipd: 0x00, state: 1
[ 11.253576] rk3x-i2c ff110000.i2c: timeout, ipd: 0x00, state: 1
[ 12.253582] rk3x-i2c ff110000.i2c: timeout, ipd: 0x00, state: 1
root@rockpi4c:~# [ 5491.165276] rk3x-i2c ff110000.i2c: timeout, ipd: 0x00, state: 1
[ 5492.165273] rk3x-i2c ff110000.i2c: timeout, ipd: 0x00, state: 1
[ 5493.165536] rk3x-i2c ff110000.i2c: timeout, ipd: 0x00, state: 1
[ 5494.165571] rk3x-i2c ff110000.i2c: timeout, ipd: 0x00, state: 1
[ 5495.165547] rk3x-i2c ff110000.i2c: timeout, ipd: 0x00, state: 1
ifconf[ 5496.165320] rk3x-i2c ff110000.i2c: timeout, ipd: 0x00, state: 1
ig -a[ 5497.165541] rk3x-i2c ff110000.i2c: timeout, ipd: 0x00, state: 1
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether ae:1c:6a:88:a1:0b txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 24
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1 (Local Loopback)
RX packets 178 bytes 14670 (14.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 178 bytes 14670 (14.6 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::8525:217b:cdd9:5080 prefixlen 64 scopeid 0x20
inet6 fe80::2a80:49be:dd69:2b9c prefixlen 64 scopeid 0x20
ether 6c:21:a2:41:b9:52 txqueuelen 1000 (Ethernet)
RX packets 131 bytes 12044 (12.0 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 277 bytes 39965 (39.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@rockpi4c:~# [ 5498.165318] rk3x-i2c ff110000.i2c: timeout, ipd: 0x00, state: 1
The text was updated successfully, but these errors were encountered: