-
-
Notifications
You must be signed in to change notification settings - Fork 504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No HDMI output for NanoPC T4 SD CARD Image #7339
Comments
Are there any kernel errors? dmesg -l 0,1,2,3 And did you try a different HDMI screen, just to rule out it is related to it, like HDMI signal not strong enough/cable too long or such thing? SBCs behave differently than PCs or Laptops. |
I can confirm that it isn't a cable's issue because it works well with armbian with kernel 5.x |
Ah, Linux 5.x is too old to consider, and not maintained anymore by anyone. But indeed there are related reports at Armbian as well (the last one from you), from which we imported the issue:
Interesting that features of such an old long mainline-supported board break. There have not been any significant changes recently, or at all, and its device tree does not define any HDMI-related thing anyway, while it works on other RK3399 boards: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm64/boot/dts/rockchip/rk3399-nanopc-t4.dts It is actually a good circumstance to test the new Linux 6.12 kernel build. Maybe it even fixes the issue: cd /tmp
wget https://dietpi.com/downloads/binaries/linux-{dtb,image}-current-rockchip64.deb
dpkg -i linux-{dtb,image}-current-rockchip64.deb
reboot If not, then the slightly newer edge kernel could be tested as well: apt install linux-{dtb,image}-edge-rockchip64
reboot |
The HDMI is defined in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm64/boot/dts/rockchip/rk3399-nanopi4.dtsi#n208 and include by https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm64/boot/dts/rockchip/rk3399-nanopc-t4.dts#n12 |
Yeah, and that is included by all other RK3399 boards, where HDMI works, and the part has no been touched in a while, as far as I can see: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/arch/arm64/boot/dts/rockchip/rk3399-nanopi4.dtsi |
Thank you for being willing to discuss this with me, you are the only one for now do we use an armbian kernel ?, if it's true , may be related armbian/build#2016 |
I tried the edge kernel, it works with HDMI
|
While this patch is not present anymore, is has later been disabled again, in a different way: https://github.com/armbian/build/pull/3260/files I mean it is HDMI for U-Boot only, not for the actual OS kernel. That time, obviously it did not break anything, but fixed HDMI, and today it does not break HDMI for any other board. But we can do a test build with the patch removed. Actually U-Boot messages on HDMI are quite appealing. The argumentation on the PR, that one cannot do inputs anyway, is misleading, since usually one does not want to change something in U-Boot, but simply wants to see logs/output in case the board does not boot. Otherwise one requires a USB-UART adapter for that. Probably HDMI audio is bot broken anymore by that, so that we can remove the patch in our Armbian fork, re-enabling U-Boot output on HDMI for all RK3399 boards. But please test the newer kernel builds first, as every change on our fork is a maintenance burden, which I want to avoid, if possible. |
I'm testing the EDGE kernel for now I will post any result if I finish it |
Great. Would be nice to know if the latest "current" kernel works as well. I have also no idea what might have changed. Probably a faulty (kernel) patch was dropped. Linux 6.6 to 6.12/6.13 also is quite something. |
|
The bad news is that the HDMI of the CURRENT kernel is broken too
so the HDMI is fixed when kernel is above 6.12 |
Interesting, thanks for testing. There have been quite some patches removed/consolidated with Armbian's edge branch, some of them which could be done on current branch as well, after it has been migrated to Linux 6.12. I'll have a closer look, maybe we can do some of them on our fork. But probably good to compare Linux 6.12 and 6.13 in Linux upstream first, maybe we missed something along the device tree includes. |
Creating a bug report/issue
Required Information
bookworm
[ 0.000000] Linux version 6.6.56-current-rockchip64 (build@armbian) (aarch64-linux-gnu-gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP PREEMPT Thu Oct 10 10:50:06 UTC 2024
NanoPC T4
12V2A
SanDisk Ultra
Steps to reproduce
Expected behaviour
Actual behaviour
Extra details
The text was updated successfully, but these errors were encountered: