Help needed: 8740w + GTX 1070

I've got recently a Zotac 1070. I've used an external display (DP) to install it, but the internal screen (eDP) is not recognized at all. Any input would be appreciated. Thanks.



@ChanceJackson @Prema

 

did you flash it to the MSI bios yet? I believe your laptop mobo id is 1520 correct? were there any lines in the unmodified nvbli.inf regarding the 1520?

 

Not yet, stock Zotac. Should I?

Nope, none at all. Should I download the latest driver that was intended for my machine? If yes, the 1070 wasn't available back then.

 

I suggest flashing to the msi 1070 mxm vbios and seeing if that will recognize the internal screen after reboot, the zotac vBios was never intended for use with eDP and likely lacks that info

if that doesn't work download the latest nvidia driver HP has for your machine and explore the nvbli.inf for all references to your machine 1520 chances are all official video card configuration use the same Section ID # investigate that section ID and make sure the same installer options in the Section ID you use in your modified INF mirrors what was in the official inf.


I have some vBioses in http://forum.notebookreview.com/thr...a-g1-zbook-15-but-its-not-perfect-yet.803964/


*Fair warning my laptop is Optimus capable and that is how i use my 1070n i wasn't able to get it to display to my internal screen with Hybrid Graphics off

 

How was the msi vBIOS working for you?

 

It was fine except it drew more power @Striker1234 was able to to get his zotac card to display on the internal screen of his eDP dell using the msi vbios

 

What version of NVFlash you've used? I've tried to no avail both Windows and DOS versions. The DOS ones say that they can't recognize the GPU. The Windows versions all list the Read Me file no matter which key I press, only Q works, but that's to quit.

 

hmm I t was a while ago but I used the windows version of nvflash from an elevated(Admin) command prompt

 

Elevated CMD is what I'm using as well. Can you check, or send me the version that you have used? Thanks!

 

I've no issue(flashing my 1080) by version posted by Mr.fox and Prema's work (on msi 16l13 thread). Take a try
https://drive.google.com/file/d/1YGpH7_Zkdnlx6v85ygErdm6ooPv-jciP/view?usp=sharing

 

Are you trying to launch NVflash by itself? Iirc you have to launch it with the specific command you want in the proper syntax on the same command line ex. "Nvflash.exe backup oemvbios.bin" (probably the wrong syntax though I hope you get the point) look up an Nvflash guide for the right commands

 

Thanks for the input! It worked with the latest version, not directly as you said, had to open the folder and then type "cmd" in the navbar and then the command "nvflash64 -6 xxxx.rom".

Anyway, new problems now: There's picture while booting, in Safe Mode and with disabled driver. With the driver installed, once it gets to actually load it in Windows the screen goes off and no external can be switched. Tried the msi vBIOS from your topic, the GeCube one and this one. So far only the stock ZOTAC works properly, but only on external. The display is an oddball - 10bit IPS RGBLED eDP (more like internally wired DP) with ColorBoard/converter to LVDS, but then why I can't switch to external?

@t456 @j95 @Mobius 1 - Hope you guys can chime in.

 

Yes, the only reason it's running at all is that ColorBoard; system turns out eDP and the board converts it to the screen's LVDS. A theory; the panel still identifies itself as being LVDS (which is true), but the Pascal driver thinks ' Hey! An LVDS; I can't drive that with eDP!' and promptly turns off the signal altogether.

Could try hot-plugging the cable between the decoder board and the lcd once the system has booted. Just be very, very careful and make dead-sure to insert it straight, not one side before the other. Might do a few attempts with the power off first; would be a shame to brick a DC.

 

Makes sense. Is there a workaround though? Sorry, but I won't dare to try the hot-plug. This way I've burned a GPU and a display in the past. I won't say that the 1070 would be easily sacrificed, but the DC is too much at stake. So yeah, I hope that there's more elegant solution.

 

shouldn't the adapter make the computer see it as eDP?

Correction: I meant eDP

 

I think the nVidia driver doesn't know how to handle your laptop, those kind of specifics are handled by the section ID you used

download the latest nvidia driver HP has for your machine and explore the nvbli.inf for all references to your machine 1520 chances are all official video card configuration use the same Section ID # investigate that section ID and make sure the installer options in the Section ID you use in your modified INF mirrors what was in the official inf.

 

Yes and no. First it is not exactly eDP, since it is missing a couple of eDP specific pins. That's why I said that it's more like internally wired DP. Second - I really don't know how HP made it to be recognized. Maybe they've used DP, since the LVDS would've been too thick and too much paths to be wired on the motherboard? Also I'm not sure if the MXM's LVDS can support 10bit at all. I think that it can't - 8bit max. Needs another data pair and it is not designed for it. This seems more like it. The question still remains how it is recognized?

I've tried quite a few section IDs and all the same. The last was ZBook 17 G2's K5100m (Section004). Excluding the GPU, the display is the same configuration - 10bit IPS RGBLED eDP (more like internally wired DP) with ColorBoard/converter to LVDS. I'm at loss. Could try 8770w's K5000, but I don't hold my breath to be honest.

 

The panel's edid will inform the system as to its interface type. You can check this with MonInfo. Could you copy/paste the 'raw data' bit too, while you're there?

 

except the g2 zbook is a strictly optimus compatible eDP system I wouldn't bother using the section ID of a different already configured laptop go back to the official driver and copy the specifics of that section ID over to your modified inf

 

Here you are:

Spoiler: LGD0270

Monitor
Windows description...... Generic PnP Monitor
Manufacturer............. LG Display
Plug and Play ID......... LGD0270
Serial number............ n/a
Manufacture date......... 2009, ISO week 0
Filter driver............ None
-------------------------
EDID revision............ 1.4
Input signal type........ Digital
Color bit depth.......... 10 bits per primary color
Color encoding formats... RGB 4:4:4, YCrCb 4:4:4
Screen size.............. 370 x 230 mm (17,2 in)
Power management......... Not supported
Extension blocs.......... None
-------------------------
DDC/CI................... n/a

Color characteristics
Default color space...... Non-sRGB
Display gamma............ 2,20
Red chromaticity......... Rx 0,686 - Ry 0,308
Green chromaticity....... Gx 0,206 - Gy 0,715
Blue chromaticity........ Bx 0,145 - By 0,045
White point (default).... Wx 0,313 - Wy 0,329
Additional descriptors... None

Timing characteristics
Range limits............. Not available
GTF standard............. Not supported
Additional descriptors... None
Preferred timing......... Yes
Native/preferred timing.. 1920x1200p at 60Hz
Modeline............... "1920x1200" 154,000 1920 1968 2000 2080 1200 1203 1209 1235 -hsync -vsync
Detailed timing #1....... 1920x1200p at 48Hz
Modeline............... "1920x1200" 123,200 1920 1968 2000 2080 1200 1203 1209 1235 -hsync -vsync
Detailed timing #2....... 1920x1200p at 50Hz
Modeline............... "1920x1200" 128,330 1920 1968 2000 2080 1200 1203 1209 1235 -hsync -vsync

Standard timings supported

Report information
Date generated........... 14.4.2018
Software revision........ 2.90.0.1020
Data source.............. Registry
Operating system......... 6.1.7601.2.Service Pack 1

Raw data
00,FF,FF,FF,FF,FF,FF,00,30,E4,70,02,00,00,00,00,00,13,01,04,B0,25,17,78,0A,BC,25,AF,4E,34,B7,25,
0B,50,54,00,00,00,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,28,3C,80,A0,70,B0,23,40,30,20,
36,00,6F,E8,10,00,00,19,20,30,80,A0,70,B0,23,40,30,20,36,00,6F,E8,10,00,00,19,A0,10,93,54,00,F8,
00,50,00,23,00,23,01,01,00,00,00,00,21,32,80,A0,70,B0,23,40,30,20,36,00,6F,E8,10,00,00,19,00,24

Optimus is disabled with DreamColor configurations.

 

Thanks for the interesting edid. This is the LP171WU8-SLB1?

It's indeed claiming it's using LVDS interface or, more accurately, it's been left empty, which is generally being interpreted as LVDS since there's no official setting for that.

Weirdly, there's a third timing block which is hidden from the MonInfo dump and presumably also from the system (it should've been between the 48Hz and 50Hz). The timing says 147x1528@120Hz, which is probably why the OS skipped it as being ' way out of range'. Either this is a freak error or it might be used for the second cable by that odd DC driver. Should guess that the system doesn't show this optional resolution anywhere?

Anyway, made a small modification for you to try:
LGD0270 - eDP mod.bin

It will identify itself as using eDP and substituted the third timing by a 1600x1024@85Hz option. That's only a small 3% overclock, so it shouldn't have any issue running that. This is merely an extra 'native' resolution, so just something you could potentially switch to.

Don't think the 1070 will permit you to flash that, but the old card should do fine.

 

I forgot about that

 

I'm not sure about that. LVDS is an Analog video format while the edid says "Input signal type........ Digital" which should be eDP or at least DP

 

No; LVDS is also a digital format (i.e., it uses logic levels to determine '0' or '1'). VGA, Composite and SCART would be defined as 'analog' within the edid standard. The odd thing is simply that the standard has no specific code for LVDS (unlike HDMI, DVI and DP), so it's left with '1***0000'/'digital: undefined', which is the same for every LVDS panel in existence.

Wikipedia has a nice summary (OpenLDI = LVDS): List of video connectors.

 

Yes, it is LP171WU8-SLB.

I haven't seen this resolution.

Thanks! Couple of questions before that:
How to back-up the stock EDID?
How to flash it?
There's a program that controls the color space, brightness and etc. I think that it is more of a ColorBoard controller, rather than display one, but do you think that there's a chance that it wont work after using this file?

Will try and let you know. If it doesn't let me, then I'm not sure when I'll be able to flash it.

 

Sent a pm.

 

Thanks, I know vga and component are analog but I thought lvds was too on account that it's been in use for over 25 years and modern gpus are ditching it

 

Tried to see what TeamView would show me - low and behold not a single display was found with the msi vBIOS and drivers installed.

@t456 so after quite a few drivers, even @j95 ones, I got to try the flashing as well. It didn't work. There are no I2C devices. Here's the funny part. I booted my external first and it was running @1024x768 (or something like that). Then I swapped vBIOSes, booted with the DreamColor and it was running @1920x1200. So I guess Linux recognizes it as a DP/eDP display and drives it properly. Then why the external was running at such low resolution and the other options were lower, nothing higher? BTW This was done with the 1070 (1ba1) in there as you can see from the report that I've attached.

This thing doesn't stop to amaze me.

 

Flashing edids on 10*0 hasn't had a single instance of success, so it wasn't very unexpected. It'd be interesting to see what happens when using the old card.

The linux driver might skip the interface check and proceeds to reading out all the specifics first, such as resolution and refresh rate, while the Windows version could halt right after seeing an LVDS display. Just a guess though, but it does explain the differences.

 

I see. I thought that it wont work at all. My bad. A bit hesitant to swap the GPUs, the 1070 sits so nice and tidy in there Should find time this week, because it really grinds my gears.

 

Thanks for the time @t456 but it didn't work. Swapped the GPUs, followed the guide (really nice work there), flashed the firmware, everything works as it should with the M8900, the 1070 is still a no-go. Funny thing, with the M8900 both displays were recognized properly and running naive resolution in the Lubuntu. The DC was listed as an eDP.

 

Bummer, the driver doesn't get tricked that easily then. Good to know flashing custom edid on a DreamColor is possible though; that also allows you to change calibration on the hardware level, independent of OS or drivers.

Btw, does the extra refresh rate show up in the monitor options, at least? And for Windows; you did uninstall the old display entries before re-installing the 'new' display and, lastly, the 1070 driver? Old edid entries of every monitor, in- or external, will remain in the registry until manually removed.

 

Or the vBIOS is the problem, or both.

Yeah, this is the good part. I was thinking about overclocking as well, but I have too many other things, so not of main concern of mine. The calibration on the other hand might have @83bj60 interested

Forgot to check, sorry Would it show it if the display drivers are not installed, so I can check it with the 1070, since it's a bit of a pain to swap the GPU's (I'm using K5-PRO as thermal pad replacement which is awesome, but a bit tedious for application).

None of these. After driver removing (with DDU) and then reinstalling, what else I'll have to do and where? Thanks!

 

Good question. It might still show up on the ' Monitor options' page; displays are read out and controlled by the graphics driver, but once they've done so their specifications would still be accessible. The registry locations to check are these two:

Code:

HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\
HKLM\SYSTEM\CurrentControlSet\Enum\DISPLAY\

Export those registry paths somewhere and we'll check their values first.

 

Here are the extracted registries:

 

The registry still has the old 'LVDS' edid and the driver sails by those parameters. You did follow the guide to the end, right? That means especially checking the last part where you re-run the edid dump in order to verify it's different from the pre-flash dump; some panels are write-protected, so even if the flash procedure says ' all good', that doesn't mean the values are actually written to the eeprom. Curiously enough, both the stock edid and my mod have the same '0x24' checksum (pure coincidence), so you'll have to look at some of the values to spot it has been changed.

If all is well then it simply needs the re-install in order make Windows and the driver aware of the 'new' display:

1. Uninstall gpu driver(s) with DDU.
2. Uninstall monitor in 'Device manager'.
3. Use the 'Check for hardware changes' thingie.
4. Install graphics driver.

The registry dump should now show up with the new edid and, so the theory goes, the graphics driver ought to contain the settings required to run an eDP panel.

 

Still no go. Do you want me to make a regdump for you?

 

Sure, but it'd probably still show the old edid. If you have a spare disk laying around; perhaps easier to do a quick clean install.

If that still doesn't show a different edid in the registry then the eeprom is likely write-protected (linux dump would also show a no-change). Soldering would be required then. Have this panel myself; could mod it as a proof-of-concept and at least verify it'll identify itself as being an eDP and still run happily. Don't have a Pascal card though, so can't do that very last check.

 

@triturbo can i look at your modified 8740w internal?

 

Clean W8.1 install and GPU drivers only - scrambled picture, like the GPU is defective. I can upload a picture if you want. I guess it can't be fooled this way, or I'm doing something wrong, or the problem is not there in first place. I'll try to flash back the original EDID and see how it behaves on a fresh W8.1 install.

If it's not too much of a hassle, I'd love to hear your results.

Here you are.

 

I'm throwing in the towel, boys and girls. Can't get the internal working under any Windows (10 UEFI including), works fine under Linux.