Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEAT] Detect GDDR VRAM type for dedicated GPUs. #993

Open
Get-Newsletters-Int opened this issue Jun 4, 2024 · 7 comments
Open

[FEAT] Detect GDDR VRAM type for dedicated GPUs. #993

Get-Newsletters-Int opened this issue Jun 4, 2024 · 7 comments
Labels
enhancement New feature or request

Comments

@Get-Newsletters-Int
Copy link

Wanted features:

Detect what type of VRAM dedicated GPUs are using, for example GDDR5, GDDR6, GDDR6X etc.

Motivation:

It is important information about graphics cards, that companies making them often show prominently on the model page.

@Get-Newsletters-Int Get-Newsletters-Int added the enhancement New feature or request label Jun 4, 2024
@CarterLi
Copy link
Member

CarterLi commented Jun 5, 2024

Doesn't seem to be possible because no public APIs of Nvidia / AMD / Intel drivers report this info AFAIK.

Do you know any open-source program can report it?

@Get-Newsletters-Int
Copy link
Author

Get-Newsletters-Int commented Jun 5, 2024

Nope, I think only GPU-Z detects it, but no idea how, maybe they don't and they do a database lookup instead.

@Calinou
Copy link

Calinou commented Jun 16, 2024

There is no API for this, so you need a database that can infer the VRAM type from the GPU model name. Luckily, pretty much all GPUs of a same model use a single VRAM type (e.g. all GTX 1080s use GDDR5X).

A few GPUs have different VRAM types depending on VRAM size (such as the Radeon HD 7750 or GeForce GT 1030), but this practice hasn't been seen in GPUs released since 2016 or so. In this case, I'd return the most commonly found VRAM type (GDDR5 and DDR3 respectively). If you really want to, you could get fancy by picking the correct VRAM type depending on VRAM size:

  • HD 7750 1 GB: GDDR5
  • HD 7750 2 GB: DDR3
  • GT 1030 1 GB: GDDR5
  • GT 1030 2 GB: DDR3

@Kseen715
Copy link

Kseen715 commented Aug 13, 2024

Integration with GPU-Z via SDK would be amazing tbh.

There is no API for this

I think it is (but more likely uses DB). TechPowerUp says: "We also offer a GPU-Z SDK, which is provided as simple-to-use DLL with full feature set that can be used from C/C++/.NET and others."

Maybe somebody could write to them and get SDK? It should include some sort of a database too, so later we should be able to create linux version using it

@Calinou
Copy link

Calinou commented Aug 13, 2024

Maybe somebody could write to them and get SDK? It should include some sort of a database too, so later we should be able to create linux version using it

GPU-Z's SDK is proprietary and Windows-only, and therefore not a good fit for an open source CLI tool that aims to be portable.

@LowJack187
Copy link

It should tell you in the vBIOS. Maybe poke a few tech YTbers that play with overclocking, if you can't get ahold of KingPin directly.

@xiaoran007
Copy link
Contributor

In fact this has been discussed before, see this link https://forums.developer.nvidia.com/t/memory-brand-type/51653.

Nope, I think only GPU-Z detects it, but no idea how, maybe they don't and they do a database lookup instead.

Because nvidia provides an interface to request memory information in the windows version driver, but not in linux version.

It should tell you in the vBIOS. Maybe poke a few tech YTbers that play with overclocking, if you can't get ahold of KingPin directly.

Yes, vbios defines the supported video memory types. But bypassing the driver to read the vbios at runtime doesn't seem to be a safe operation.

Another way is to read the vbios version through Nvidia's interface and create a database from here. But this method is not "elegant".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants