[Request]LED panel will be show garbage when launch HWiNFO tool on Lenovo laptops.

A

Amina

Member
Hey,

We found the LED panel will be show garbage when launch HWiNFO(6.24 for Windows),
Analysis:
1. Check panel VCOM voltage changed when issue happened.
2. Check panel I2C signal found write a 0xFE data on address 0x4F through GPUI2C via NVAPI.
3. for Address 0x4F is VCOM coverter address,
4. if we uncheck GPUI2C via NVAPI from Seetings-->SMBus / I2C don't have this problem and HWiNFO tool also can get GPU information.

We hope you can give some suggestion or show a warning and uncheck GPUI2C via NVAPI when HWiNFO tool run our product

Thanks
 
Last edited:
Thanks for your report. HWiNFO uses only read commands via I2C, in this case it issues I2C Read Byte command. Is the VCOM sensitive to such commands too?
Is it possible to somehow detect the affected panels, so I could add an exception for them?
 
Hi Martin,
Thanks for your quick reply.
It would be a good suggestion to exclude failure panel, our panel ID is "BOE08E8" can be found it in devices manager(Monitors-->Generic PnP monitor-->Details--> Property--> Hardwave Ids--> MONITOR\BOE08e8)
 
Hi Martin,
Yes，Only found this panel ID using the VCOM till now， if you build test or beta version of HWiNFO I will to try it. :)Thanks
 
Here the test build: www.hwinfo.com/beta/hwi64_625_4122.zip
It should automatically skip I2C address 0x4F if it detects the "BOE08E8" monitor without the need to do any manual exceptions. So please make sure to revert the I2C exclusion in HWiNFO to test properly.
If it won't work, please attach the HWiNFO Debug File from this build for analysis.
 
Hi Martin,
Sorry for monitor ID wrong.
Thank you very much, for 4124 build is work, can not duplicate monitor garbage problem. I will double confirm more monitors whether have simlar problem, if other monitor have simlar problem please also add fail monitor ID in test build version.
another one, Do you add this solution to the official version? Thanks
 
Add more details, for old version build we check the “4” of GPU I2C Bus Exclusion item, still can not duplicate this problem. Thanks
 

Attachments

  • HWinfo.png
    HWinfo.png
    1.4 MB · Views: 2
Amina said:
Hi Martin,
Sorry for monitor ID wrong.
Thank you very much, for 4124 build is work, can not duplicate monitor garbage problem. I will double confirm more monitors whether have simlar problem, if other monitor have simlar problem please also add fail monitor ID in test build version.
another one, Do you add this solution to the official version? Thanks
Click to expand...

Thanks for testing. Yes, this change will be included in official release (as first in Beta). If you provide more monitor IDs or there would be an universal method how to detect those controllers, I will add that too.
 
You must log in or register to reply here.
Back
Top