mancaveman Posted November 25, 2016 Posted November 25, 2016 I'm trying to use 1080p60 with a DVI-HDMI cable on an Orange Pi One so I run h3disp -m 1080p60 -d and restart. Monitor shows randomly moving white lines on both sides of the display (probably the console text all garbled) for a few seconds then goes to sleep. Tried with a TV (using an HDMI-HDMI cable) and it cycles between Unsupported Mode and No Signal. 1080p without the DVI flag works on the TV but the monitor doesn't even come out of sleep with it. Other resolutions seem to work fine with the DVI flag on the monitor, including 720p and 1080i. The monitor also works fine with a 1080p output from a PC. Image: Armbian_5.20_Orangepione_Debian_jessie_3.4.112_desktop.7z Any ideas? Thanks
Christos Posted November 25, 2016 Posted November 25, 2016 Using the same mode here, with OPi, but with latest self build image, Armbian 5.24 Jessie 3.4.113 desktop, it works just fine. Can you build an image with these instructions? -> https://github.com/igorpecovnik/lib
mancaveman Posted November 25, 2016 Author Posted November 25, 2016 I tried. Fresh install Xenial build host, x64. The resulting image flip-flops between a purple screen and one of uBoot hanging at Starting the Kernel .... EDIT: Apparently the image was missing the script.bin. Not sure if this is normal or not. Copied it over from 5.2 which made the new image boot but the 1080p problem persists. Ideas? EDIT2:
mancaveman Posted November 26, 2016 Author Posted November 26, 2016 I dropped ppl_video for the mode from 594 to 297 in h3disp and it appears to work just fine this way. Not sure if there are any side-effects to doing this but I can't see anything wrong with the image at least. Looks like someone else had a similar experience: https://forum.armbian.com/index.php/topic/752-tutorial-h3disp-change-display-settings-on-h3-devices/?p=19134
jernej Posted November 26, 2016 Posted November 26, 2016 No, 297 is default value and the only correct one for 1080p 1
tkaiser Posted November 26, 2016 Posted November 26, 2016 No, 297 is default value and the only correct one for 1080p I would assume this will be fixed with next release: https://github.com/igorpecovnik/lib/commit/144f704c41e4adea0d8cc00670069cfed0383600#commitcomment-19969929 1
Recommended Posts