1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Voltage support for AMD Fury?

Discussion in 'MSI AfterBurner Overclock Application Discussion' started by aNoN_, Jun 26, 2015.

  1. aNoN_

    aNoN_ Member

    Messages:
    47
    Likes Received:
    3
    Is this something that may be introduced in the near future? Or is the card voltage locked? I sincerely hope it's not!
     
  2. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,404
    Likes Received:
    1,420
  3. aNoN_

    aNoN_ Member

    Messages:
    47
    Likes Received:
    3
    Thanks and sorry for not seeing that the question was already answered.

    Moreover, it's amazing how many people are dependent on you Unwinder. Your work is grandly appreciated.

    Why doesn't the Fury card support voltage tweaking in the first place? Strange decision by AMD, it only makes the card look worse in reviews... My guess would be that the card most likely have really good overclocking potential, perhaps it can even surpass Titan X at occasions where higher resolution and more bandwidth is required.
     
  4. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,404
    Likes Received:
    1,420
    It is not a question of "strange decision by AMD" at all. It is a question of very limited AMD ADL API. NVIDIA cards simply have unified GPIO/VID based voltage control functions inside NVAPI, so it is very easy and fast to support voltage control on new cards (within driver allowed voltage control range of course) or even provide voltage control for future cards without even seeing them.
    It doesn't apply to AMD. To support voltage control on new cards developers first need to implement low-level I2C aceess support for each new GPI family (which can be troublesome for new GPU architecture), then provide support for each new voltage controller model. That's not the task that can be done without hardware.
     

  5. BoMbY

    BoMbY Member Guru

    Messages:
    185
    Likes Received:
    0
    GPU:
    Fury X
    Is there any way to speed up the process? I've a Fury X and some developer experience. What would you need to implement the basics?
     
  6. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,404
    Likes Received:
    1,420
    There is nothing you can do to speed up development of low-level I2C driver, sorry. However, I've got hint from one source that AMD could leave driver-level I2C access unlocked for Fiji, which means that even current AB 4.1.1 can easily access VRM if it is really the case.
    So you could verify it by scanning I2C bus with the following command line switches and posting the results here:

    MSIAfterburner.exe /i2cd
     
  7. Hilbert Hagedoorn

    Hilbert Hagedoorn Don Vito Corleone Staff Member

    Messages:
    36,089
    Likes Received:
    5,128
    GPU:
    AMD | NVIDIA
    Already tried that two weeks ago with the ref sample Alex, it resulted in a complete crash.
     
  8. BoMbY

    BoMbY Member Guru

    Messages:
    185
    Likes Received:
    0
    GPU:
    Fury X
    Exactly the same thing for me. On Windows 8.1 x64 with the 15.15 drivers, if that helps.
     
  9. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,404
    Likes Received:
    1,420
    Define "complete crash". Application crash? System crash?
     
  10. BoMbY

    BoMbY Member Guru

    Messages:
    185
    Likes Received:
    0
    GPU:
    Fury X
    System crash. Black screen, and nothing else anymore. Had to do a hard reboot.
     
    Last edited: Jun 30, 2015

  11. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,404
    Likes Received:
    1,420
    That's actually a good thing. Assuming that AMD driver's I2C API is not completely broken and not cause a crash after using it as is, black screen is most likely a result of accessing some I2C device critical to scanning. So at least I2C is not completely locked and some device is actually being accessed. Instead of complete I2C dump you may try to scan expected IR3567B address range only:

    MSIAfterburner.exe /i2cd,30
     
  12. BoMbY

    BoMbY Member Guru

    Messages:
    185
    Likes Received:
    0
    GPU:
    Fury X
    Sorry, same result. Only a black screen.
     
  13. Lucky_n00b

    Lucky_n00b New Member

    Messages:
    2
    Likes Received:
    0
    GPU:
    Intel HD Graphics
    Doing i2c dump indeed cause black screen crash. But if we scan some specific areas we can get the values:
    Scanning GPU VEN_1002&DEV_7300&SUBSYS_0B361002&REV_C8&BUS_3&DEV_0&FN_0...
    Scanning I2C bus 0...
    Probing device 30...
    Invalid device
    Scanning I2C bus 1...
    Probing device 30...
    Invalid device
    Scanning I2C bus 2...
    Probing device 30...
    Invalid device
    Scanning I2C bus 3...
    Probing device 30...
    Invalid device
    Scanning I2C bus 4...
    Probing device 30...
    Invalid device
    Scanning I2C bus 5...
    Probing device 30...
    Invalid device
    Scanning I2C bus 6...
    Probing device 30...
    29 14 1B 0F 16 1E 7C 49 4A 7D 11 66 66 44 FF FF
    A2 22 80 10 29 FF 20 00 00 00 00 00 00 00 00 00
    00 00 60 60 1C 1E FF 8D 3C 26 A3 31 38 A1 1F 31
    38 07 FC 74 6F 05 05 1D 81 A0 60 00 00 66 00 00
    A8 90 00 00 00 00 3C 00 14 14 00 40 80 60 60 FF
    FF 00 40 88 34 88 44 12 02 02 88 00 20 20 00 3C
    3C 03 7D 61 3C 9C 24 88 80 00 00 00 00 FF 06 FF
    FF 20 00 00 00 00 00 00 00 00 00 00 15 15 00 00
    00 00 3C 00 00 00 00 00 88 88 01 C2 44 00 00 1F
    00 05 43 68 28 01 30 70 5E A8 73 A6 02 3C 1E 1F
    00 00 00 00 00 00 01 01 08 55 A0 8F CF 00 00 05
    04 00 00 00 00 FF 23 C3 00 00 7A 6E 9E 15 3C 00
    00 00 00 77 13 00 00 00 00 00 00 03 00 44 00 00
    00 00 AD 50 0C 00 10 00 3F 00 00 00 23 C0 F0 1E
    00 1F 00 10 01 03 01 88 00 00 00 00 3C 00 00 00
    00 00 00 00 00 33 00 00 00 00 00 00 00 00 00 00
    Scanning I2C bus 7...
    Probing device 30...
    29 14 1B 0F 16 1E 7C 49 4A 7D 11 66 66 44 FF FF
    A2 22 80 10 29 FF 20 00 00 00 00 00 00 00 00 00
    00 00 60 60 1C 1E FF 8D 00 26 A3 31 38 A1 1F 31
    38 07 FC 74 6F 05 05 1D 81 A0 60 00 00 66 3C 00
    A8 90 00 00 00 00 00 00 14 14 00 40 80 60 60 FF
    FF 00 40 88 34 3C 44 12 02 02 88 00 20 20 00 3C
    3C 03 7D 61 68 9C 24 88 80 00 00 00 00 FF 06 FF
    3C 20 00 00 00 00 00 00 00 00 00 00 15 15 00 00
    00 00 00 00 00 00 00 00 88 88 01 3C 44 00 00 1F
    00 05 43 68 28 01 F0 70 5E A8 73 A6 02 01 1E 1F
    00 00 00 00 00 00 01 01 08 55 A0 8F 3C 00 00 05
    06 00 00 00 00 FF 23 C3 00 00 7A 6E A9 15 00 00
    00 00 FF 77 13 00 00 00 00 00 00 03 01 3C 00 00
    00 00 AD 50 0C 00 10 00 3F 00 00 00 23 C0 F0 00
    00 00 00 10 01 03 01 88 00 00 00 00 00 00 3C 00
    00 00 00 00 00 33 00 00 00 00 00 00 00 00 00 00

    Probing with /ri6, 30, 92 (or ri7,30,92), gives 43 response, so I'm trying to use the third party voltage control method and made msiafterburner.oem2 file consist on these lines:

    ;OEM
    [VEN_1002&DEV_7300&SUBSYS_0B361002&REV_C8]
    VDDC_IR3567B_Detection=6:30h
    VDDC_IR3567B_Type= 1
    VDDC_IR3567B_Output= 0

    And the voltage control shows a value that can be controlled up to +100mV *sorry can't post image/link yet*, but every time I alter those voltages, the Card frequencies are sometimes stuck in 300Mhz even with 3D load.

    I tried the other way using normal voltage control method, adding this line to the hardware profiles using
    [Settings]
    VDDC_IR3567B_Detection = 30h
    VDDC_IR3567B_Output = 0

    But the result is the same, the voltage control shows a slider to +100mV but when you set it, the card stuck to 2D Frequencies.

    I'll probably do more test when my preordered card is delivered, the one I'm testing with already returned back to AMD.
     
  14. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,404
    Likes Received:
    1,420
    That's both positive and negative info. Positive: device 30h in the dump is IR3567B with no doubts, so driver-level I2C access is indeed working and VRM can be accessed on software level. Negative: such reaction on overvolting (graphics card downclocking) smells by hitting some hardware limit, I'm not too optimistic on improving it.
     
  15. Anvi

    Anvi Member Guru

    Messages:
    127
    Likes Received:
    0
    GPU:
    R9 390 8GB
    Kinda OT, but without Unwinder's efforts AMD GPU's probably wouldn't have voltage control software available at all..

    Overclocking without voltage control isn't very good and it's going to cost AMD millions in missed sales. Wish they learned from Nvidia.
     

  16. Lendox

    Lendox Member

    Messages:
    10
    Likes Received:
    0
    GPU:
    2x Fury X
    I do not know a lot about GPU BIOS modification, so does someone here know what would have to be done in order to get a BIOS editing tool for the Fury X's BIOS like the VBE?
     
    Last edited: Jul 15, 2015
  17. aNoN_

    aNoN_ Member

    Messages:
    47
    Likes Received:
    3
    The world stands still until Fury X gets voltage support! Well, at least I do... My purchase choice are all up to if Fury can OC decently or not. Are you gonna be receiving a card soon Unwinder?
     
  18. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,404
    Likes Received:
    1,420
    No, it is even not in the way yet.
     
  19. A M D BugBear

    A M D BugBear Ancient Guru

    Messages:
    2,887
    Likes Received:
    186
    GPU:
    2 1080ti-XOC BIOS
    Question, Do you think you might have it ready by the end of this year? The voltage unlocking and possibly hbm memory overclocking???
     
  20. cowie

    cowie Ancient Guru

    Messages:
    13,192
    Likes Received:
    286
    GPU:
    GTX
    ha ha or ever
    bear when he gets one we will know shortly after
     

Share This Page