HD4400 not able to detect internal screen on my laptop in win 10 after the screen was changed

[M_2]

Hi

The screen of my laptop is broken and I replaced It. The replacement was exactly the same display but the hw. revision was slightly different. It is an IPS AU Optronics 1080p panel. Since I changed the panel, the laptop is not able to detect the display using Win 10. I did some research and I'm 99,9% sure that this is a driver issue, here are my results:

OpenSuSE 42.3 - works perfectly, even HDMI, mini display port and audio over these interfaces

OpenSuSE 42.2 - works perfectly, even HDMI, mini display port and audio over these interfaces

Ubuntu 16.04.3 LTS - works perfectly, even HDMI, mini display port and audio over these interfaces

Windows 10 using Microsoft Basic display adapter - internal screen works, mini display port and HDMI does not work

Windows 10 using 2015 driver provided by Microsoft - internal screen works, however the brightness is so dark that It is almost impossible to see anything, and the internal brightness control does not work. Mini display port and HDMI work either, audio over these interfaces also works ok

Windows 10 using latest 15.40.37.4835 drivers - internal screen is not recognized, mini display port and HDMI works perfectly, when I look at the control panel, only one screen (the external one) is recognized (Dell Monitor), however, there is no "Generic PNP Monitor" entry for the internal screen. Intel control panel is not able to detect more displays, only the external monitor is detected.

System information

Acer v5-573g using intel i5 4.200U, latest bios is already installed. Screen is AU Optronics 1080p IPS panel, the same one that came with the laptop originally, but the hw revision is higher.

[idata]

mtruchado: Perfect, no problem at all, take your time to gather all those details.

Any questions, please let me know. Regards,Alberto R

[M_2]

Hi

here is the requested information

Do not hesitate to contact me in case you need anything

Thanks and regards

[idata]

Hi mtruchado: Thank you very much for providing those reports.

Besides those details, please provide the SSU report:https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows- https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows- And the DxDiag report:Click on the "Start Menu, Type "DxDiag", Press "Enter", Wait for the DirectX Diagnostic Tool to finish loadingIn the DirectX Diagnostic Tool, click "Save All Information" , Save the file DxDiag.txt Any questions, please let me know. Regards,Alberto R

[M_2]

Here It is

Just in case, Intel VBios under UEFI is:

Intel GOP 5.0.1028

[idata]

mtruchado: Thank you very much for providing those reports. We will do further research on this matter, as soon as I get any information I will post it on this thread.

Any questions, please let me know. Regards,Alberto R

[RonaldM_Intel]

Hello mtruchado,

I would like to jump in and try to help as well.

Even though the issue is only on Windows* environment, I doubt that it is specifically a driver bug, otherwise this would be something that your system would have shown before the screen was replaced. With that said, I'm suspecting the problem might be between the EDID (or lack thereof) of the current panel and the VBIOS programming (the VBIOS programming is done by the Original Equipment Manufacturer - OEM).

Let's try the following: connect all the displays you want to use and bring up the Intel(R) Graphics Control Panel, then go to 'Options and Support' --> 'Information Center' --> Click on 'Save' (lower right-hand corner) to generate a new .txt report. Attach the report here please, since I would like to see how the driver is reading each display's EDID, perhaps it can show us more relevant information and point us in the right direction.

Best Regards,

Ronald M.

[M_2]

Hi Ronald

First of all thanks a lot for help me in this one!

I can confirm you that under linux EDID is read from the EDP1 panel, the full report is attached, but here is a small snapshot

I will provide also the information that I get in windows as soon as I could find a external screen, as the internal as you know is not working there

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767

eDP1 connected primary 1920x1080+0+0 (0x49) normal (normal left inverted right x axis y axis) 340mm x 190mm

Identifier: 0x43

Timestamp: 6472

Subpixel: unknown

Gamma: 1.0:1.0:1.0

Brightness: 1.0

Clones:

CRTC: 0

CRTCs: 0 1 2

Transform: 1.000000 0.000000 0.000000

0.000000 1.000000 0.000000

0.000000 0.000000 1.000000

filter:

EDID:

00ffffffffffff0006afed4100000000

0019010495221378022e8e9558599329

25535a00000001010101010101010101

010101010101143780b4703826406c30

aa0058c110000018b82480b470382640

6c30aa0058c110000018000000000000

00000000000000000000000000000002

001048ff0f3c6e1e14216e2020200035

BACKLIGHT: 187

range: (0, 187)

Backlight: 187

range: (0, 187)

scaling mode: Full aspect

supported: None, Full, Center, Full aspect

Broadcast RGB: Automatic

supported: Automatic, Full, Limited 16:235

audio: auto

supported: force-dvi, off, auto, on

1920x1080 (0x49) 141.000MHz -HSync -VSync *current +preferred

h: width 1920 start 2028 end 2076 total 2100 skew 0 clock 67.14KHz

v: height 1080 start 1090 end 1100 total 1118 clock 60.06Hz

[M_2]

Hi

I have the requested report. As you can see under Windows 10 It is not able to recognize even the eDP1 display. Fascinating.

[RonaldM_Intel]

Hi again,

Sorry for answering until now, I try to stay away from work during weekends (and that includes replying in Forums )

Thanks for the information provided, I think I am putting together the puzzle pieces, yet there is something that is pinching in my brain on this one. After the screen was replaced, did you perform a clean Windows installation?

Looking forward to hearing from you again.

Regards,

Ronald M.

[M_2]

Yes

In fact, It was not so long ago when I discovered that my laptop contains a m-sata connector plus the sata connector. I used the sata connector with linux (where the screen works and as you can see the EDID can be read) and I took the advantage of this m-sata to install a ssd with windows 10 and... I got the eDP1 screen working only if I use the microsoft basic display driver.

[RonaldM_Intel]

Thanks for the confirmation. I was thinking that perhaps there was a conflict with the Windows registry entry (which includes the EDID) from the previous screen vs. the new one, but if it is a clean OS installation then I doubt that's the case.

Based on all the information we got so far, I am leaning towards this being an issue caused by the new screen and the current VBIOS programming.

Honestly I do not think it is a driver bug in its current form, otherwise this would have been a problem with the previous screen as well. Unfortunately our Windows driver is very dependent of the EDID, and if this one is missing then it reads of the VBIOS for eDP. My best suggestion would be contacting Acer* support, since they are the OEM and should be able to provide further guidance.

Feel free to post here any findings or conclusions from Acer* and I'll try to help to the best of my capacity.

Best Regards,

Ronald M.

[M_2]

If I understood correctly, the problem is that for whatever reason the EDID from the eDP1 cannot be read correctly under windows, but fortunately this value is stored in windows registry. Well, I can read It under linux. Can I use this to fix the registry and let the windows driver know that screen?

Acer is not taking care of my laptop anymore. Even It is not listed in the list of affected products by meltdown/spectre. Acer gave me this screen as a replacement, It was the very same that the broken one (just the Hw. revision was different) and this is all they are going to do for me.

[RonaldM_Intel]

I would like to clarify that a Local Flat Panel (LFP) may not necessarily need an EDID, since the video block data for said LFP may be programmed in the vBIOS by the system manufacturer.

However, in this case neither the EDID of the new screen, nor a matching vBIOS configuration for the new screen seems to be being picked up by the Windows driver. As per support staff policy, we do not provide guidance or support for modifying the Windows* registry. The most I can do is point out that the Display information should be stored in the following Windows Registry key (Windows 10): 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY'

I regret reading that Acer* is not supporting this laptop anymore. Since they were the ones that replaced the screen, perhaps they can follow up since it is not working as expected?

Best Regards,

Ronald M.

[M_2]

I can try but I don't think that Acer would help me on this one. This is more than one year that I bought the panel from them. As I said, I bought the laptop with no OS. When I installed the panel, every single thing worked out of the box... because I used linux only. It is now, when I saw that windows 10 is introducing some nice features that I wanted to try when I realized that the panel is not working there.

Regarding what you told me that this is not a driver issue, I still think It is, otherwise, how can you explain that I'm writing this message using my laptop under linux?

The panel works, the laptop starts pretty good, bios is working, linux is working, It is just not working under windows. By the way, I installed a win 7 in another hard disk and It is also not working there... so It must be a software issue.

[RonaldM_Intel]

Hi again mtruchado

Unless we have a reproducible case (i.e. the issue can be reproduced by us here with the same driver on a similar laptop) I'm afraid this is as far as Intel's support staff can go on this one. As it was previously stated, for years now we have successfully installed our generic Windows drivers on different laptops with HD Graphics 4600 and both internal and external display worked fine.

I still consider your best course of action would be checking with the party that gave you the laptop and the replacement screen for further assistance.

Best Regards,

Ronald M.

[M_2]

Hi again

I would like to close this thread, as my problem is solved. I was able to identify the issue. The issue is that under V5-573g Acer sold many different kind of laptops. Some of them were delivered even using glossy, non-glossy panels, some of them IPS, non-IPS, and even some of them got 1336 x 768 resolution instead of Full HD 1080p panels. I bought another panel, this time making sure that It was IPS, glossy and 1080p. For my surprise the new panel had nothing to do with the original one and the replacement I got. Both of them were from AU Optronics, this one is even from a different retailer... I thought that I got another wrong piece, but I just wanted to give It a try and... It's working perfectly in both linux and windows.

So yep, sometimes some panels are not recognized because how knows what the manufacturer did in the bios (white listing between all the providers they got, for exmaple). It looks like the linux stack driver does not care about that, but in windows things are different... hence please double check, triple check, that your panel is the right one. This cost me to buy a second panel and put the first in the trash.

Just in case you are curious, this is the screen I received now:

29: None 00.0: 10002 LCD Monitor

[Created at monitor.125] Unique ID: rdCR.Kt4DWXYhkM2 Parent ID: _Znp.rm9YlziB_z8 Hardware Class: monitor Model: "N156HCA-EAA LCD Monitor" Vendor: CMN "N156HCA-EAA" Device: eisa 0x15e5 Resolution: 1920x1080@60Hz Size: 344x193 mm Year of Manufacture: 2016 Week of Manufacture: 20 Detailed Timings # 0: Resolution: 1920x1080 Horizontal: 1920 2000 2054 2250 (+80 +134 +330) -hsync Vertical: 1080 1086 1094 1132 (+6 +14 +52) -vsync Frequencies: 152.84 MHz, 67.93 kHz, 60.01 Hz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: # 14 (VGA compatible controller)

http://www.panelook.com/N156HCA-EAA_Innolux_15.6_LCM_overview_30597.html Innolux N156HCA-EAA Overview - Panelook.com

The bright levels are not as good as the values I got with the AU Optronics, but this one works and the other did not.