RK3399 HDMI output and USB 3.0 not working with Linux 6.1

Troubleshooting
1

Hi,

I have installed the update 8.21.1 (dietpi-update from version 8.20).
After reboot one of USB 3.0 ports stopped working.
Any ideas can it be software problem?

Required Information

  • DietPi version |

G_DIETPI_VERSION_CORE=8
G_DIETPI_VERSION_SUB=21
G_DIETPI_VERSION_RC=1
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’

  • Distro version | bookworm

  • Kernel version | Linux Rose 6.1.46-current-rockchip64 #3 SMP PREEMPT Wed Aug 16 16:27:31 UTC 2023 aarch64 GNU/Linux

  • Architecture | arm64

  • SBC model | ROCK 4 (aarch64)

  • Power supply used | any

  • SD card used | any

Steps to reproduce

  1. Plug in any USB device into top USB-port
  2. Nothing happens
2

Please fill out the troubleshoot template, without this info we can just try a shot in the dark.

3

probably related to the kernel update done by the dietpi-update

@MichaIng can you have a look pls.

4

Dammit, many issues solved, but new issues introduced :smile:. At least it is just one USB port.

Interestingly there is one new rockpi4cplus-usb-host overlay. It is described as

Switches the top USB 3.0 port to host mode.
WARNING! Not officially supported by Rockchip!!!

Sounds promising, even that it is named after C+ variant.

There is also another one:

### dwc3-0-host

Forces port 0 of the DesignWare xHCI controller to host mode.

This can be used on plaforms such as NanoPC-T4, where devices plugged into the
USB-C port may not be detected otherwise.

Can you try them one after another?

G_CONFIG_INJECT 'overlays=' 'overlays=rockpi4cplus-usb-host' /boot/dietpiEnv.txt
reboot

Ah, and to be sure that your SBC is really detected as ROCK Pi 4B, respectively that the correct device tree is loaded:

cat /proc/device-tree/model
2 Likes
5 
cat /proc/device-tree/model
Radxa ROCK Pi 4B

cat /boot/dietpiEnv.txt
rootdev=UUID=21fbd909-5d4f-4ffe-8ad7-751b251a9f2a
rootfstype=ext4
# The init system logs to the console defined last.
consoleargs=console=tty1
usbstoragequirks=
extraargs=net.ifnames=0
docker_optimizations=off
overlay_path=rockchip
overlay_prefix=rockchip
overlays=rockpi4cplus-usb-host
user_overlays=

rebooted, no changes(

1 Like
7

HI,

I just wanted to say that with my rock pro 64 I also have the same problem on usb 3.0, I had all the data in an external ssd connected there, damn

8

Can you test the other one as well (both of your):

G_CONFIG_INJECT 'overlays=' 'overlays=dwc3-0-host' /boot/dietpiEnv.txt
reboot
9

I tried the command on the fly but since the directory “/boot/dietpiEnv.txt” did not exist, the command did not even work .
i try to launching only “overlays=dwc3-0-host”, but didnt work .
So I rolled back

10

no changes, again

11

Is is probably an older image where /boot/armbianEnv.txt exists instead?
Then it would be:

G_CONFIG_INJECT 'overlays=' 'overlays=dwc3-0-host' /boot/dietpiEnv.txt
reboot

Sadly I have only the NanoPi R4S with this SoC, but it only has two USB(-A) ports which both work.

Can you both check for kernel errors:

dmesg -l 0,1,2,3

I checked the Armbian forum but can’t find a related report for ROCK 4 series or ROCKPro64. When you find time, could you test the respective Armbian Bookworm minimal image:

1 Like
12

Hello, I thought about it and for the community this and more:

root@DietPi:~# G_CONFIG_INJECT 'overlays=' 'overlays=dwc3-0-host' /boot/armbianEnv.txt
[  OK  ] G_CONFIG_INJECT | Added setting overlays=dwc3-0-host to end of file /boot/armbianEnv.txt
root@DietPi:~# dmesg -l 0,1,2,3
[    2.365386] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[    2.455498] dw-apb-uart ff180000.serial: Failed to create device link (0x180) with 0-001b
[    2.604193] dw-apb-uart ff180000.serial: Failed to create device link (0x180) with vcc3v3-sys
[    2.830677] phy phy-ff7c0000.phy.6: phy poweron failed --> -110
[    2.831571] dwc3 fe800000.usb: error -ETIMEDOUT: failed to initialize core
[    2.869147] dw-apb-uart ff180000.serial: Failed to create device link (0x180) with 0-001b
[   15.971717] OF: graph: no port node found in /i2c@ff3d0000/typec-portc@22
root@DietPi:~# reboot

after reboot

root@DietPi:~# dmesg -l 0,1,2,3
[    2.361428] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[    2.451788] dw-apb-uart ff180000.serial: Failed to create device link (0x180) with 0-001b
[    2.598804] dw-apb-uart ff180000.serial: Failed to create device link (0x180) with vcc3v3-sys
[    2.826622] phy phy-ff7c0000.phy.6: phy poweron failed --> -110
[    2.827521] dwc3 fe800000.usb: error -ETIMEDOUT: failed to initialize core
[    2.864052] dw-apb-uart ff180000.serial: Failed to create device link (0x180) with 0-001b
[   10.576748] OF: graph: no port node found in /i2c@ff3d0000/typec-portc@22
root@DietPi:~#

So dosent work

I remain available for any of your tests, if you even want to connect remotely I can give you access @MichaIng
Pietro

13

can you crosscheck using Armbian Bookworm minimal image as requested by @MichaIng ?

1 Like
14

oh Yeah, sry

so from lsblk i see my 2 ssd

root@rockpro64:~# dmesg -l 0,1,2,3
[    2.425387] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[    2.519647] dw-apb-uart ff180000.serial: Failed to create device link (0x180) with 0-001b
[    2.674288] dw-apb-uart ff180000.serial: Failed to create device link (0x180) with vcc3v3-sys
[    2.934799] dw-apb-uart ff180000.serial: Failed to create device link (0x180) with 0-001b
[    3.894118] OF: graph: no port node found in /i2c@ff3d0000/typec-portc@22
[    5.824195] (sd-execut[344]: /usr/lib/systemd/system-generators/netplan failed with exit status 1.
[   13.061373] Bluetooth: hci0: command 0x0c03 tx timeout
[   21.221405] Bluetooth: hci0: BCM: Reset failed (-110)
root@rockpro64:~#

after launchin “sudo apt update && sudo apt install armbian-config”

root@rockpro64:~# dmesg -l 0,1,2,3
[    2.429418] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[    2.523867] dw-apb-uart ff180000.serial: Failed to create device link (0x180) with 0-001b
[    2.676054] dw-apb-uart ff180000.serial: Failed to create device link (0x180) with vcc3v3-sys
[    2.937142] dw-apb-uart ff180000.serial: Failed to create device link (0x180) with 0-001b
[    3.880681] OF: graph: no port node found in /i2c@ff3d0000/typec-portc@22
[   37.747289] (sd-execut[350]: /usr/lib/systemd/system-generators/netplan failed with exit status 1.
[   42.853419] Bluetooth: hci0: command 0x0c03 tx timeout
[   50.917439] Bluetooth: hci0: BCM: Reset failed (-110)
[  107.231722] (sd-executor)[2054]: /usr/lib/systemd/system-generators/netplan failed with exit status 1.
root@rockpro64:~# lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0 447.1G  0 disk 
sdb           8:16   0 465.8G  0 disk 
mtdblock0    31:0    0    16M  0 disk 
mmcblk1     179:0    0  29.8G  0 disk 
└─mmcblk1p1 179:1    0  29.5G  0 part /var/log.hdd
                                      /
zram0       251:0    0   1.9G  0 disk [SWAP]
zram1       251:1    0    50M  0 disk /var/log
zram2       251:2    0     0B  0 disk 
root@rockpro64:~#

i see the disk

15

Can you check kernel version used on plain Armbian

uname -a
1 Like
16 
root@rockpro64:~# uname -a
Linux rockpro64 6.1.30-rockchip64 #3 SMP PREEMPT Wed May 24 16:32:53 UTC 2023 aarch64 GNU/Linux
root@rockpro64:~#```
17

And booting the DietPi image reveals which kernel version? Just for comparison.

18 
root@DietPi:~# uname -a
Linux DietPi 6.1.46-current-rockchip64 #3 SMP PREEMPT Wed Aug 16 16:27:31 UTC 2023 aarch64 GNU/Linux
root@DietPi:~#
19

soo they are different.

@MichaIng would it be an option to downgrade?

20

@Joulinar Any update?
cc:
@MichaIng

21

@MichaIng is out this weekend, you would need to wait for his return.

1 Like