Hello guys, I have an annoying issue with my OPiPC where I simply cannot get HDMI output. I am certain it is not a hardware issue! My OPiPC works fine with HDMI output & android. I have tried a known good HDMI->DVI-D adapter with various settings, and direct HDMI connection with various settings. It is a fresh install of Armbian 5.20 with apt-get update & apt-get upgrade.

 

I have tried a plethora of h3disp settings and direct bin2fex configs! What could be wrong?

 

Here is the current setup I am testing, which I would like to get working:

 

-LG W1942TQ ( 1440x900 native )

-Working HDMI cord and HDMI->DVI-D adapter

 

Interesting bits of the fex file:

 

[clock]

pll_video = 432

 

[boot_disp]

advert_disp = 0
auto_hpd = 1
output_type = 3
hdmi_channel = 0
hdmi_mode = 35
cvbs_channel = 1
cvbs_mode = 11
output_full = 1
hdmi_mode_check = 0
 

[disp_init]
screen0_output_type = 3
screen0_output_mode = 35
screen1_output_type = 3
screen1_output_mode = 35
disp_init_enable = 1
disp_mode = 0
fb0_format = 0
fb0_width = 0
fb0_height = 0
fb1_format = 0
fb1_width = 0
fb1_height = 0

 

[hdmi_para]
hdcp_enable = 0
hdmi_cts_compatibility = 1
hdmi_used = 1
hdmi_power = "vcc-hdmi-18"

 

 

---/etc/armbian-release---

 

BOARD=orangepipc
BOARD_NAME="Orange Pi PC"
VERSION=5.23
LINUXFAMILY=sun8i
BRANCH=default
ARCH=arm

 

 

---uname -r---

3.4.112-sun8i

 

 

 

 

BTW, 1440x900 is mode 39. If that doesn't work, you can try 720p with pll_video=297 and screen0_output_mode=5

my h3disp lists 1440x900 as -m 35, and won't take -m 39 ...

 

pll_video = 297 and screen0_output_mode=5 does not work with either PC monitor.

 

The W1942TQ does, however, go from "no signal"/sleep mode to a blank screen.

 

Settings now:

 

pll_video = 297

...

screen0_output_type = 3

screen0_output_mode = 5
screen1_output_type = 3
screen1_output_mode = 5
disp_init_enable = 1
disp_mode = 0
fb0_format = 0
fb0_width = 0
fb0_height = 0
fb1_format = 0
fb1_width = 0
fb1_height = 0

[hdmi_para]
hdcp_enable = 0
hdmi_cts_compatibility = 1
hdmi_used = 1
hdmi_power = "vcc-hdmi-18"
 

What's even stranger is that I remember these very same settings working in the past ( 5.05 maybe ? ).

 

PS: thank you for the quick response!

Sorry, 35 is correct one for your resolution. I looked at wrong number in patch. Does U-Boot show logo correctly? Can you try another cable?

I've tried another cable, and I've tried this cable in another system. No issues with the cable or adapters.

 

No U-boot logos or anything. Screen is completely blank..

 

I found some oddities in dmesg:

 

[    0.416818] [DISP]disp_module_init
[    0.417112] cmdline,init_disp=
[    0.417141] cmdline,disp=
[    0.426990] [DISP] Fb_map_kernel_logo,line:932:Fb_map_kernel_logo failed!

 

shouldn't this be type=3 ??
[    1.630056] [DISP] disp_device_attached_and_enable,line:159:attched ok, mgr0<-->device0, type=4, mode=35

 

[   10.618297] [DISP] disp_ioctl,line:1584:para err in disp_ioctl, cmd = 0x0,screen id = 65536


 

Internally, HDMI has type 4. Confusing, I know. Only last line indicate a possibility for some kind of error. Can you try clean desktop image?

This image is fresh from armbian, only with apt-get update & upgrade - and of course, the fex/bin configs. Should I try without the update & upgrade?

Yes, just to see if there is some issue in latest code.

just flashed 5.20, with absolutely no alterations. My TV did not show anything during the installation process. I used h3disp -m 1080p60 -d and moved to my 1080p monitor.... but no effect .

 

After a short while, the 1080p monitor showed a blank screen but the power was on.

 

Here is the important stuff from the fex:

 

pll_video = 594

pll_video = 297 (removed from fex manually)

 

 

[boot_disp]
advert_disp = 0
auto_hpd = 1
output_type = 4
hdmi_channel = 0
hdmi_mode = 4
cvbs_channel = 1
cvbs_mode = 11
output_full = 1
hdmi_mode_check = 1
 

[disp_init]
screen0_output_type = 3
screen0_output_mode = 10
screen1_output_type = 3
screen1_output_mode = 10
disp_init_enable = 1
disp_mode = 0
fb0_format = 0
fb0_width = 0
fb0_height = 0
fb1_format = 0
fb1_width = 0
fb1_height = 0

[hdmi_para]
hdcp_enable = 0
hdmi_cts_compatibility = 1
hdmi_used = 1
hdmi_power = "vcc-hdmi-18"

 

dmesg still has these errors:

 

[    0.416368] [DISP]disp_module_init
[    0.416679] cmdline,init_disp=
[    0.416705] cmdline,disp=
[    0.432454] [DISP] Fb_map_kernel_logo,line:932:Fb_map_kernel_logo failed!
[    0.468256] Console: switching to colour frame buffer device 240x67
[    0.504918] [DISP]disp_module_init finish

[    1.670041] [DISP] disp_device_attached_and_enable,line:159:attched ok, mgr0<-->device0, type=4, mode=10
 

[   10.326514] [DISP] disp_ioctl,line:1584:para err in disp_ioctl, cmd = 0x0,screen id = 65536

 

 

As would tkaiser suggest, use etcher, which will detect issues with writting. dd will just ignore or missed them.

reflashed with Etcher, verified with no issues. I've got some video coming out of the OPi but it's almost too garbled to make out. It's barely visible but it's there - and it only shows on my 1080p monitor. The W1942 doesn't display anything.

 

So, recap:

• Fresh install of 5.20, verified by Etcher
• ran h3disp -m 5 -d
• adjusted fex file to remove duplicate pll_video entry

Rebooted to some video but it's still unusable. Fex has the following settings:

 

pll_video = 297

screen0_output_mode = 5

screen0_output_type = 3

hdcp_enable = 0

hdmi_cts_compatibility = 1

 

What else can I try?

 

 

EDIT: Just for clarity, the screen is a blue image with moving red horizontal lines and moving green dots.

The cable, screen, and adapter are all known good.

EDIT: Just for clarity, the screen is a blue image with moving red horizontal lines and moving green dots.

The cable, screen, and adapter are all known good.

 

I'm having similar issues with an OPi +2E, an HDMI-to-DVI cable and a Dell 2007WFP monitor that has 1680x1050 native resolution (And is very picky otherwise). Sometimes, with a bit of luck, I see a sort-of stable picture, but the color red is just blinking/shifting like some sorft of static.

Create a post about it here

I haven't tested much after my last post, so I haven't found any solution for my case yet.

Just wanted to let you know about a similar situation.