• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Maxwell and Pascal GPUs Need Firmware Update To Support New DisplayPort Displays

yeah it ain't for mobile gpus, only add-in (usually desktop) parts
 
I don't even wanna ask how many bricks you have laying around in your closet

None. I have a hardware programmer so I can recover any "brick" on earth essentially. All my bricks are from thermal paste (see sig).

There are no checks: you can either decrypt the content (if it's signed by Nvidia) or you can't (if it's been tempered with).

Oh but there are (see above). What I seem to have discovered is it checks for a modded bios before modding it itself and resigning it. ie with the private key.

Unfortunately it seems to send the file for that private key signing along with some other details to a webserver for the job, if I'm not mistaken... but still...

Ask yourself what would happen if it did NOT check for a modded bios. ;)
 
Just a little update: I've not noticed any change in behaviour from my graphics card since the update. I'd hoped it would address the issue where the BIOS messages don't show on the DP port, but it hasn't.
 
If you are using Fast Boot (EFI boot + GPT OS drive), BIOS messages may not be shown.
 
If you are using Fast Boot (EFI boot + GPT OS drive), BIOS messages may not be shown.
Indeed I am, thanks. It shows on the other ports, so I don't get why it should blank on DP.
 
It could be related to the graphics card placement in what slot on the mainboard, and an on-board gpu if you have one. I also have a 1080 gtx(although sli), and windows sometimes went blank when searching displays, and suddenly blank on bios messages until windows loads, until I simply connected the displayport monitor to the top gpu instead of the bottom, now everything works.
 
Oh but there are (see above). What I seem to have discovered is it checks for a modded bios before modding it itself and resigning it. ie with the private key.

Unfortunately it seems to send the file for that private key signing along with some other details to a webserver for the job, if I'm not mistaken... but still...
Like I said, private keys don't see the light of day.

Ask yourself what would happen if it did NOT check for a modded bios. ;)
I honestly can't imagine. It would just replace it with stock, functional BIOS. But then again, I've long stopped pretending I can imagine everything ;)
 
Like I said, private keys don't see the light of day.

I was pretty sure that was the case, but you know, I was hoping made team green said "screw it" and thew us a bone...

I honestly can't imagine. It would just replace it with stock, functional BIOS. But then again, I've long stopped pretending I can imagine everything ;)

But it only patches the bios. DIFFs clearly show this. It doesn't replace it whole. Hence the mod check. If it was modded, mods would be retained, and signed.
 
I was pretty sure that was the case, but you know, I was hoping made team green said "screw it" and thew us a bone...
Yeah, I got that. It would have been a monumental blunder. Yet, nothing that hasn't happened before ;)


But it only patches the bios. DIFFs clearly show this. It doesn't replace it whole. Hence the mod check. If it was modded, mods would be retained, and signed.
I have to admit, I'm not that up to date with the firmware on modern video cards. I'll take your word for it.
 
So I ran the file on eight GPUs.
Two of them didn't need the update, and the other six did.
I have seen no changes in the way any of them perform either.
 
Ran it on one of my 980Ti - no issue. The other one I haven't bothered with since it just connects HDMI to the TV so I see no reason for it.
 
Back
Top