Ongoing HDMI limited compatability

[rahlquist]

tllim in particular, but anyone else in the know too.

What plans if any are being made to help address the large amount of HDMI issues folks are reporting (myself included).  Of particular interest is simply being able to use the board at this point.

Thanks,

[Darkover]

Can you provide some links, where the HDMI problem is discussed?

I had no luck getting HDMI working with Asus MW221U 1680x1050 monitor, I will test it later with our LG 3D TV and another monitor. Unix OS tried.

[rahlquist]

Can you provide some links, where the HDMI problem is discussed?

I had no luck getting HDMI working with Asus MW221U 1680x1050 monitor, I will test it later with our LG 3D TV and another monitor. Unix OS tried.

Its all over the forum here. I personally have 4 TV/Montiors and the Pine works with only 1 of them. They all work with my Pi. 

I believe the general consensus is that the Pine outputs only one mode, 1080p, and doesn't negotiate as a true HDMI device should. Some have had various success with display adapters etc.  In the end though, it sucks. Would like to be able to use this with the 21" monitor I intended. For now all I can do is RDP in.

[tkaiser]

Did you ever had a look whether it's 'just' an issue like it was with Ethernet on the 2GB variant?

We're currently dealing with Allwinner's BSP kernel and do know that we already ran in issues with obviously untested 32-bit code (the aforementioned Ethernet issue). Could be the same with the display: EDID/HDMI contains an integer overflow, you connect one of your 3 displays --> the driver crashes and no signal on the HDMI port until next reboot (and crash )

Did you had a look already whether a driver crashes in your situation?

[longsleep]

We're currently dealing with Allwinner's BSP kernel and do know that we already ran in issues with obviously untested 32-bit code (the aforementioned Ethernet issue). Could be the same with the display: EDID/HDMI contains an integer overflow, you connect one of your 3 displays --> the driver crashes and no signal on the HDMI port until next reboot (and crash )

Well, there is no general issue with HDMI on Pine64+2GB as far as i can tell (mine works just fine).

[frewind]

I don't think it's a crash, as my monitor just goes into sleep mode, but ubuntu still comes up and you can ssh and rdp to it. I guess someone will have to wire up the serial port debugging and see if there are any error when the system boots.

[longsleep]

Well whatever it is, do not expect the situation to improve anytime soon. I do not care much about display and just made it work 1080p@60Hz no further questions asked.

To understand why I do not care you need to know that the HDMI driver in the BSP Kernel driver is missing sources for "libhdmi" (similar to libdram situation for SPL). See https://github.com/longsleep/linux-pine6...i_sun50iw1 for reference.

[rahlquist]

Did you ever had a look whether it's 'just' an issue like it was with Ethernet on the 2GB variant?

We're currently dealing with Allwinner's BSP kernel and do know that we already ran in issues with obviously untested 32-bit code (the aforementioned Ethernet issue). Could be the same with the display: EDID/HDMI contains an integer overflow, you connect one of your 3 displays --> the driver crashes and no signal on the HDMI port until next reboot (and crash )

Did you had a look already whether a driver crashes in your situation?

[   28.711244] libphy: 1c30000.eth: probed
[   28.715547] sunxi-gmac 1c30000.eth eth0: eth0: PHY ID 001cc915 at 0 IRQ poll (1c30000.eth-0:00)
[   28.771985] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   29.420764] libphy: 1c30000.eth: probed
[   29.425065] sunxi-gmac 1c30000.eth eth0: eth0: PHY ID 001cc915 at 0 IRQ poll (1c30000.eth-0:00)
[   29.480764] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   34.339313] libphy: 1c30000.eth-0:00 - Link is Up - 1000/Full
[   34.345621] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  378.466140] hdmi_clk_enable_prepare()L161

As you can see it was sitting idle till I hooked up the hdmi. Literally thats the only thing I see come over the serial console, is there anything else I should try/check to beat on it?

Disconnect and reconnect nets me;
[  668.940193] hdmi_clk_disable_prepare()L176
[  673.692845] hdmi_clk_enable_prepare()L161

[tkaiser]

Well, there is no general issue with HDMI on Pine64+2GB as far as i can tell (mine works just fine).

I was talking about Pine64 in general and not the 2GB model. And yes, mine also worked fine with every display connected to (even with DVI converter with the usual wrong colors that are fixable through OSM). But there are issues as already discussed (u-boot honouring .dtb settings but kernel not, different reports whether providing EDID in kernel cmdline or not does help).

Anyway I would assume it needs some experienced people that actually run into display issues to start debugging what's going on. And then there's still the libhdmi situation.

[rahlquist]

Well whatever it is, do not expect the situation to improve anytime soon. I do not care much about display and just made it work 1080p@60Hz no further questions asked.

To understand why I do not care you need to know that the HDMI driver in the BSP Kernel driver is missing sources for "libhdmi" (similar to libdram situation for SPL). See https://github.com/longsleep/linux-pine6...i_sun50iw1 for reference.

You know, I knew of A's reputation for not being very OSS supportive but based on the BS on the KS page I figured we would at least have basic functionality out the gate. 

I was a fool, I have now paid my stupid tax for the year. Lets hope nobody wants a double installment. At least it was cheap. 

Ohh look maybe I can pay stupid tax again! https://www.kickstarter.com/projects/udo...ecommended  LOL