Jump to content
NotebookTalk

JadeRover

Member
 View Profile  See their activity

  • Posts

    133

  • Joined

  • Last visited

  • Days Won

    1

JadeRover last won the day on May 3

JadeRover had the most liked content!

2 Followers

Recent Profile Visitors

1,239 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. JadeRover
    Here is an updated version (core clocks are in the correct format). Set to 2000Mhz (again vrel limit before seing this value) You said the memory was good, it boosted to 2000/4000Mhz ? Because checking again my custom memory clock was not in the expected format, strange that it still worked. I change the memory clock in this _1 version. It is in the expected format in version _1. In version _2 it is in the same format as my last p106m vbios. if you can give both a try that would be good. p106m_OC_checked_1.bin p106m_OC_checked_2.bin
  2. JadeRover
    Interesting. I might add these IDs but as a read only to see what card is recognized, especially for P6 and other cards that have a non standard clock layout and need different calculations in order to display the correct values.
  3. JadeRover
    It should normally. I haven't tested it. When you say 8 bit checksum, you mean the header checksum ? Or the last 8 bits of the 32bit body checksum ?
  4. JadeRover
    Yep, base clock is now 1230Mhz and boost is now 2000Mhz (you will hit vrel limit before seing this value) Memory is now at 4000Mhz target power is 100w, limit power is 120w and power slider is enabled. Checksum was fixed as well. You can try this @ssj92 teslap6_OC_power_mod.rom
  5. JadeRover
    New version : Release v1.1 | Nvidia-vBIOS-Clock-Power-Tweaker · JadeRover/Nvidia-vBIOS-Clock-Power-Tweaker This one should correctly save the clock values, you can give it a try @ssj92. I made sure it would work for the p3200 and p4200, I tested some roms on techpowerup. (clocks are in the correct 2x2 byte format).
  6. JadeRover
    What does the GPU-Z windows show ?
  7. JadeRover
    Ok, because the v1.0 will not work i made a mistake for the clock calculations
  8. Tersy started following JadeRover
  9. JadeRover
    Ok, only using the power bios ?
  10. JadeRover
    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.
  11. JadeRover
    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
  12. JadeRover
    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.
  13. JadeRover
    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
  14. JadeRover
    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).
  15. JadeRover
    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).
  16. JadeRover
    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
×
×
  • 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