Jump to content
NotebookTalk

JadeRover

Member
  • Posts

    126
  • Joined

  • Last visited

  • Days Won

    1

JadeRover last won the day on May 3

JadeRover had the most liked content!

2 Followers

About JadeRover

Recent Profile Visitors

1,221 profile views

JadeRover's Achievements

Enthusiast

Enthusiast (6/14)

  • Reacting Well
  • One Year In
  • Collaborator
  • One Month Later
  • Conversation Starter

Recent Badges

45

Reputation

  1. Ok, only using the power bios ?
  2. Yes, there is a certification issue, might be possible to bypass using OMGvflash by veil for turing cards, any newer cards will not work unfortunately. Pascal works. Even with a hardware flasher it will not work, card will refuse to boot and show error 43.
  3. Ok, I really don't have high hopes for the clock values as I got them by dividing the 4 bytes of hex by 32768. As it turns out you have to substract 16384 and then multiply by 2... on each 2 byte chunk of the 4 byte clock value ! See here : https://rog-forum.asus.com/t5/rog-gaming-notebooks/laptop-pascal-vbios-unlocks-quot-wip-quot/td-p/658321 I'll make a version only with power editing that way you can test that out (as it should work fingers crossed), while I fix the clock editing. Here is this [POWER ONLY] version 1.0 : Release v1.0 | [POWER ONLY] Nvidia-vBIOS-Clock-Power-Tweaker ยท JadeRover/Nvidia-vBIOS-Clock-Power-Tweaker
  4. Also very important, version 1.0 of my program might be saving the wrong clock values !! I will be making some actual vbios tests on my p3000 in my m6700 this week end. In the meantine no one should try to flash a custom vbios made from my program.
  5. Hello, this is P106m card vbios ? Manual looking at the clock table, it has only one core value of 1290Mhz and all the others are null (FF). For the memory clock it is 1500Mhz (in afterburner clock dual rank mode). Also the power table is a desktop type with 3 values (not supported by my program). Those I read from your vbios are all at 100w. I can make you a custom vbios to try if you want. I made one quickly, boost to 1910Mhz (I changed all the instances of 1290Mhz to 1910Mhz) and mem up to 2000 Mhz you can give it a try, the checksum was fixed as well. You will probably hit a vrel limit and be around the 1850Mhz mark p106m_vbios_checked.rom
  6. I don't have an ETA. This is a side project I have my active life to attend to. DP_B is probably DP++ so it can output either DP or HDMi or even DP+HDMi thanks to a demuxer switch on the laptop (splits the DP++ into one DP and one HDMi).
  7. That's right, fixing one byte and then fixing checksum causes error 43. However I know that upddating the GOP driver found inside the vbios doesn't brick the card : GOP Update and Extraction Tool (Turing) - BIOS/UEFI Modding / BIOS Modding/Flashing Tools - Win-Raid Forum I've tested the utility and it changes the 32 bit checksum but not the 8 bit value of the checksum (modulo 256 checksum is the same).
  8. Yes, the display table has tons of info here is a snippet (non parsed data): Highlighted is the entire display table, notice this repeating pattern of 6 lines lines 5F10 and 5F60 starting with header "60". These are the DP_X display entries from A to F
  9. Version 1.0 is released : Release v1.0 | Nvidia-vBIOS-Clock-Power-Tweaker ยท JadeRover/Nvidia-vBIOS-Clock-Power-Tweaker Editing and saving vbios is possible + checksum is fixed. Therefore I need volunteers with an external flasher to test on pascal cards these modifications !
  10. Hello, yes there is a way to do so. The mac rumor vbios have different output table from stock vbios + documentation exists on the "DCB" table (display table) of nvidia vbios, that's the next step of the program is to read and edit these outputs. Unfortunately when testing with an RTX3000 gpu, my custom vbios did not work, the card would be bricked with error 43. Moreover, changing 2 adjacent bytes in the bios by doing +1 and -1 to the hex value (so that checksum is the same) results in a brick as well for this Turing card = meaning that Turing has more security checks then Pascal and any custom vbios bricks the card (also this was documented on mac rumors). AKA turing custom vbios won't be possible ๐Ÿ˜ž
  11. Hello, I don't think that 240Hz will work as the 7720/7520 are limited to DP1.2 signal speeds so that would be 190fps max at 1440p (according to wikipedia). What happens is that when you select that refresh rate the screen artifacts and then windows reverts to 60Hz after 15s (since you can't press the accept changes button) I don't think there are 16:9 OLED panels that support >60Hz. 16:10 they do exists, also from the vivobook line but then you would have to make sure it can actually fit in the display cover of the laptop. Go through 15.6inch OLED panels in panelook to find all the model numbers + specs
  12. Yes, agreed, that info would be crucial. I had started a draft that would show the display table, all the info relative to "dispkay outputs" is stored in the DCB table : see here https://nvidia.github.io/open-gpu-doc/DCB/DCB-4.x-Specification.html Luckily this table has not been updated for a while so it should be compatible with all the bios from the Pascal-Lovelace era. If you want to help out you can contribute to the github. What we need is algorithms going through all the table entries and parsing the data in a user friendly format showing : DP_X = such interface + i2c controls ? (basically if it supports eDP) + enabled ?
  13. Updated the repository -> version 0.3 Now turing cards read properly and the standalone windows exe works. @ssj92 You can now properly read the clock values of your T1000 and RTX5000
  14. Yes that bitmap icon is killing me! It prevented me from exporting to a single exe file ๐Ÿ˜ž I would get an error
  15. Hello everyone ! linked is my very very very early version of a pascal to ada lovelace vbios editor. as of right now it can only read bioses !! Here is the link, the details are explained in the repository https://github.com/JadeRover/Nvidia-vBIOS-Clock-Power-Tweaker Pictures :
ร—
ร—
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Terms of Use