klode82 2 Posted April 8, 2020 Share Posted April 8, 2020 Armbianmonitor: http://ix.io/2hae After a reboot, my HDMI does not send anymore signal. The resolution of my desktop (using x11vnc) is 1024x768. This is the pastebin from dmesg: dmesg from Pine64 There are some error on sunxi8. Can someone help me? 0 Quote Link to post Share on other sites
jernej 212 Posted April 10, 2020 Share Posted April 10, 2020 Resolution 1024x768 means that kernel was unable to read EDID so it sets default one. This happened now and then on my boards, most frequently with OrangePi PC2. I found out that this problem is solved if display driver in U-Boot is disabled. 0 Quote Link to post Share on other sites
klode82 2 Posted April 11, 2020 Author Share Posted April 11, 2020 14 hours ago, jernej said: Resolution 1024x768 means that kernel was unable to read EDID so it sets default one. This happened now and then on my boards, most frequently with OrangePi PC2. I found out that this problem is solved if display driver in U-Boot is disabled. Thanks @jernej for your reply. What is U-Boot, and how can I modify it? If you mean one of the file inside /boot folder, I have a boot.cmd with this setenv: setenv video-mode sunxi:1920x1080@50,monitor=dvi,hpd=0,edid=1 I don't remember if I've insert this setenv or it has always be there. Does I need to remove it? 0 Quote Link to post Share on other sites
jernej 212 Posted April 11, 2020 Share Posted April 11, 2020 U-Boot is a bootloader, which does low level HW initialization and is responsible for loading Linux and starting it. Sadly, it's not accessible trough file system and no variable will solve this issue. It needs to be re-compiled with display driver disabled and then re-flashed. @Igor how critical is U-Boot display driver? If it is not so critical, I would suggest that CONFIG_VIDEO_DE2 gets disabled for all devices. 0 Quote Link to post Share on other sites
Igor 2199 Posted April 11, 2020 Share Posted April 11, 2020 16 minutes ago, jernej said: how critical is U-Boot display driver? If it is not so critical, I would suggest that CONFIG_VIDEO_DE2 gets disabled for all devices. We can live without a display in u-boot, especially if this helps in proper detection. I'll try to squeeze this in next update. 0 Quote Link to post Share on other sites
klode82 2 Posted April 12, 2020 Author Share Posted April 12, 2020 Really, it works fine until I made some upgrade with apt, some months ago. But I'm not so sure about it. But I had screen in 1080p, even with x11vnc. 0 Quote Link to post Share on other sites
klode82 2 Posted April 12, 2020 Author Share Posted April 12, 2020 (edited) UPDATE: just for notice, I've changed the HDMI cable with another one, and now I can see again in 1080p. Sorry for inconvenience. Edited April 12, 2020 by klode82 Duplicated 0 Quote Link to post Share on other sites
jernej 212 Posted April 12, 2020 Share Posted April 12, 2020 Issue is real, so no apology needed. Cable can certainly be a cause for it, but even if it is ok, issue can still happen. 0 Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.