(Solved)J4205-ITX HDMI output

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

 Event4101 wrote:

Zzenz
It would seem like the HDMI on your board may have failed. From what I have read of other people having HDMI problems with these Apollo Lake boards, even the ones manufactured by Intel, they usually can get either the HDMI or DVI port working in some fashion through various combinations of updates (drivers, video firmware, BIOS). As I wrote in a previous post, the HDMI port would work with the Microsoft default video driver, it was the Intel driver that created my problem. Obviously I don't know where you purchased the board, but I assume it has gone beyond the return for a refund date.

You seem like a tech savvy person, but have you tried a different HDMI cable? During my extensive reading about this problem it did appear that these boards could be picky about the quality of the HDMI cable. Some reported using a better quality HDMI cable solved the problem. I got the impression that you had used your HDMI cable with other AV equipment so was hesitant to make the suggestion since it seems unlikely that is the problem.

Just curious, are you able to get a video signal from the on-board VGA port? That is, if you have access to monitor or TV with a VGA port.  I never encountered a problem with the VGA port.  If the VGA port is working you should be able to get into Windows Device Manager and see the video driver that is being used. If it is the Intel driver, you can switch back to the Microsoft Basic Display Adapter driver to see if that will resurrect the HDMI port.  At least that would tell you if the HDMI port has failed or if it is a driver issue. Of course I'm also assuming that you haven't tossed the board in the trash and moved-on with your life. :)

Stefan75
I tried your approach and it didn't work for me. I powered-on the computer with the TV powered-off.  Once the computer had booted I powered-on the TV and was met by the usual black screen and flashing mouse pointer.  I pressed the ESC key and there was no change.  I pressed Enter, Space bar, and still nothing.  If you are entering a PIN then I assume you are using a Microsoft account to log-in to your computer. My Windows 10 installation doesn't use a Microsoft account, I'm using local accounts, but I doubt that would make a difference.

It seems odd that if you are experiencing the HDMI driver problem that pressing the ESC key would resolve it.  Just curious, once you see the black screen and flashing mouse pointer, then log-in, if you view the Windows System log do you see recent Event Id 4101 Warning entries with a description that points to a problem with the display driver igfx?

One odd thing I did encounter when I was experiencing the HDMI video problem, if I logged-in to the computer using Windows Remote Desktop from my laptop, I could get the computer desktop to display on my laptop.  Once I logged-out of the Remote Desktop session then the Intel video driver would start working with the TV HDMI port.  Remote Desktop is only available with the Windows "Professional" version so the "Home" version doesn't have the feature.  Still, Remote Desktop really wasn't a convenient solution to the problem, but I thought it was a peculiar observation that appeared to solve the problem until the computer was shutdown.

Thanks for the reply.. HDMI works sometimes  as  does DVI to HDMI  
converter.. But when I say sometimes, I mean 1  out of 100. DVI seems  
to work  ok if I use a native DVI  monitor.. (but this is a Media 
Player/plex server, so need HDMI)

Yes the d-sub when I just re tested it seems to work fine.

Remote desktop works either team viewer , VNC or AnyDesk.

Damned board also seems  to want to forget my boot drive every now and again as well. Intel SSD.. And no  it is not the bios battery as everything else is remembered etc.

Honestly a system just should not need this much work put into it just to get it going. I have  over 25 years in IT  and have tried everything I  can think of... It is just plain and simply a  badly designed and  implemented motherboard  with poor bios software or hardware  or both  implementation and a shocking DP to HDMI  bridge.... 