Plead to coder of GPU-Z

[farmdve]

I am new here, however I wanted to ask the author of GPU-Z if it is possible to expose some code of how he accesses the VRM temps of a Graphics card or otherwise tell me how one can fetch them.

The AMD ADL library does not expose any wrapper to fetch the temps, thus only software like this have the option to.

 

[TheLaughingMan]

I don't think Wizz is going to tell you that. From what I understand companies like MSI, GIGABYTE, and anyone else that uses GPU-Z as a base for their own OC tools have to pay him for the privilege.

I could be wrong though.

 

[W1zzard]

first you need to figure out how to do i2c transfers on the card (ask AMD). next you need to know the register structure of the voltage controller (ask CHiL/Volterra).

with that info it should be a matter of writing glue code around it, oh and you probably need your own signed kernel mode driver which can access gpu registers as ADL doesn't expose that functionality

 

[farmdve]

I found an existing implementation which to use to query VRMs, however it is linux specific. In windows I must map the PCI bus memory to userspace which from what I am reading is much harder in Windows 7.

Let's hope \Device\PhysicalMemory will work.

Also, your executable is a single file, where on earth are you loading a driver from?

 

[W1zzard]

I found an existing implementation which to use to query VRMs, however it is linux specific

i didn't know there was a linux app that could do that. what program is it ?

Also, your executable is a single file, where on earth are you loading a driver from?

extract at runtime

 

[farmdve]

The program is called radeonvolt. It's opensource https://github.com/ius/radeonvolt.

It supports a small range of cards, the 58xx series only, but it is a nice proof of concept. It also does not require any external driver at all due to how linux works(quite amazing).

I've already compiled pciutils so scanning the PCI bus-es is not a problem. Mapping that same memory to userspace is, let's hope phymem can help me.

I've also understood that querying a card via I2C using multiple programs(or sometimes just one) can sometimes cause voltage to spike to the max possible because I2C register writing gets screwy, killing the card.