@Mumbles86
did you try this?
Releases · LaneLyng/MobilePascalTDPTweaker
Tweak mobile Pascal cards' thermal design power. Contribute to LaneLyng/MobilePascalTDPTweaker development by creating an account on GitHub.
github.com
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iM 4,1-14,4 iMac 2011 Maxwell and Pascal GPU upgrade
- Thread starter G3llings
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
did you try this?
github.com
I did try earlier, it flags the vbios as 'unsupported'@Mumbles86
did you try this?
Releases · LaneLyng/MobilePascalTDPTweaker
Tweak mobile Pascal cards' thermal design power. Contribute to LaneLyng/MobilePascalTDPTweaker development by creating an account on GitHub.
I've done a bit more research into the TDPTweaker tool. It looks for the matching hex in the vbios file "000000000100E8030000" to read and modify the MaxTDP and other similar values based on a config list. Not only are Tesla Pascal cards not defined, the known hex value for MaxTDP is not present in the HP Tesla vbios.
Usually increasing just TDP values won’t provide gains, unless you see PerfCap reason PWR in gpu-z stats. Max clocks are the main reason of underperformance in mxm cards. I’ll take a look at vbios later this week (currently on holidays)
A quick look at the vbios shows no connector, display or gpio table entries that could make a display work with it. What's the point of having a card that can boot but can't use the display in the iMac ?
It definitely has limited uses in the iMac - remote rendering and compute tasks. It has a bit more utility on other systems that can use the iGPU for display. Is it still possible to push the power limit and clock speeds in this vbios? It currently hits 4300 in TimeSpy which is nice but far short of the ~5000 score an OC'd P4000 can hit. Given the P6's similarities to the P5000 i was hoping it could even go further.
Started playing around by comparing existing mods and the TDP Tweaker tool. I can create a profile for the tool that can find and update the TDP limits. I also found the area that should at least modify the Mem clock.
Unfortunately even just the TDP change results in the card not loading, error 43.
I also tried loading the P6 with both stock and OC versions of the P5000 vbios. This results in error 10 "Insufficient system resources exist to complete the API".
I was hoping the TDP would work at least - maybe something to do with the checksum?
- Edit -
Checksum was definitely wrong before because the original HP vbios file has the 0xFF end bytes trimmed which leads to the TDP Tweaker tool using an incorrect checksum value. Need to fill out those bytes in first.
Unfortunately still no luck after fixing checksum, still error 43.
Unfortunately even just the TDP change results in the card not loading, error 43.
I also tried loading the P6 with both stock and OC versions of the P5000 vbios. This results in error 10 "Insufficient system resources exist to complete the API".
I was hoping the TDP would work at least - maybe something to do with the checksum?
- Edit -
Checksum was definitely wrong before because the original HP vbios file has the 0xFF end bytes trimmed which leads to the TDP Tweaker tool using an incorrect checksum value. Need to fill out those bytes in first.
Unfortunately still no luck after fixing checksum, still error 43.
Last edited:
Last edited:
Much appreciated, but no diceYou can try this vbios. I did some changes, set 115w and fixed cheksum but didnt test it. Dont know if it will work.
gives an error code 10 which is a bit different from the usual 43 I was getting with my attempts.I also tried the 1070 vbios for funsies, also error code 10.
From what I can tell, Tesla pascal gpus are doing some additional check. It's not playing nice with even the slightest change.
Ok so we will try to rise only memory clocks to max 1750mhz ( I set it to 2000 but will be locked to 1750 ). This mod should 100% work. Works on my P4000 mod. If not then there is some new protection in this vbios. I am working on your vbios uploaded on 31.08. Check it.Much appreciated, but no dice
I also tried the 1070 vbios for funsies, also error code 10.
From what I can tell, Tesla pascal gpus are doing some additional check. It's not playing nice with even the slightest change.
Still no dice
even went through the whole routine of bios reset + DDU.I did notice the P6 has some missing components compared to a P4000 (no P5000 for reference unfortunately). If i wasn't currently using the P4000 i'd be tempted to swap them over. I have my doubts it would resolve the errors.
Apologies for the goopy photos 😅 the Tesla photo was also taken under a yellow light and has a copper shim that makes the die size look funny.
Hmm some new protections 🤔 if you have time you can try one more thing to be 100% sure. Take your 100% working vbios and edit it in Mobile Pascal TDP Tweaker. Enable powerslider setting to adjustable, save this change and then try to flash this modded vbios and check if this works.Still no dice
I did notice the P6 has some missing components compared to a P4000 (no P5000 for reference unfortunately). If i wasn't currently using the P4000 i'd be tempted to swap them over. I have my doubts it would resolve the errors.
Apologies for the goopy photos 😅 the Tesla photo was also taken under a yellow light and has a copper shim that makes the die size look funny.
In theory this change should also show error code and that would mean that this vbios has some new protections and its not going to be easy to bypass it like on for example P4000.
Took a look at clocks and power tables inside the P6 vbios, clocks seem to be limited to 1506 MHz and TDP to 90W. Also, the clocks tables are different from other Pascal cards (they have fewer power states, and most of them seem "empty"). Unfortunately this makes impossible to just copy/paste such tables from a P4000/P5000 card, I'd have to manually try to adjust existing table entries to some matching ones from other Pascal cards, and this would take a lot of work and testing...
Also, cross-flashing other cards vbios won't work since the device id is hardware encoded using strap resistors on the card, and checked by vbios/driver.
Also, cross-flashing other cards vbios won't work since the device id is hardware encoded using strap resistors on the card, and checked by vbios/driver.
Hey, I know it's a bit old but did the listing for the 1070 you used say "1B81" instead of 1BA1 for the hardware/device ID? I'm in the exact same situation as you where I want to put in a 1070 but don't want to have any issues regarding the incorrect card.