Developing AMD GPU Utilities

Message boards : Number crunching : Developing AMD GPU Utilities
Message board moderation

To post messages, you must log in.

Previous · 1 · 2 · 3 · 4

AuthorMessage
Profile RueiKe Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 14 Feb 16
Posts: 492
Credit: 378,512,430
RAC: 785
Taiwan
Message 1985746 - Posted: 18 Mar 2019, 11:19:27 UTC - in response to Message 1985744.  

Thanks, the message disappeared, now it complains about amdgpu package missing:

user@host:~/amdgpu-utils# ./amdgpu-ls 
AMD Wattman features enabled: 0xffff7fff
Command '['dpkg', '-l', 'amdgpu']' returned non-zero exit status 1.
Error: amdgpu drivers not installed, exiting...



I made the failed dpkg call result in a warning instead of an error. Master is updated.
ID: 1985746 · Report as offensive
Profile [A.S.a.M.]koschi

Send message
Joined: 8 Jan 01
Posts: 15
Credit: 5,947,861
RAC: 15
Message 1985748 - Posted: 18 Mar 2019, 11:42:36 UTC

Thanks, the ls and monitor now work for root and my user.
pac works for my user, but segfaults for root:

root@host:~/amdgpu-utils# ./amdgpu-pac 
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
AMD Wattman features enabled: 0xffff7fff
Command '['dpkg', '-l', 'amdgpu']' returned non-zero exit status 1.
Warning: amdgpu drivers not may not be installed.
1 AMD GPUs detected, 1 may be compatible, checking...
1 are confirmed compatible.


(amdgpu-pac:4395): Gtk-CRITICAL **: 12:36:00.559: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed

(amdgpu-pac:4395): Gtk-CRITICAL **: 12:36:00.559: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed

(amdgpu-pac:4395): Gtk-CRITICAL **: 12:36:00.559: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
Segmentation fault (core dumped)


No big deal though :-)
ID: 1985748 · Report as offensive
Profile RueiKe Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 14 Feb 16
Posts: 492
Credit: 378,512,430
RAC: 785
Taiwan
Message 1986698 - Posted: 23 Mar 2019, 5:30:01 UTC

I have just released a new version of amdgpu-utils:
https://github.com/Ricks-Lab/amdgpu-utils/releases/tag/v2.3.1

This version is mostly to clean things up, fix a few bugs, and include a user guide:
    Fixed and improved Python/Kernel compatibility checks.
    Added Python2 compatible utility to check amdgpu-utils compatibility.
    Fixed confusing mode/level fileptr names.
    Removed CUSTOM PPM mode until I figure out syntax.
    Implemented classification of card type based on how it implements frequency/voltage control. This is reported by amdgpu-ls and alters the behavior of both amdgpu-pac and amdgpu-monitor.
    Changed dpkg error to a warning to handle custom driver installs.
    Initial User Guide - Need contributors!

ID: 1986698 · Report as offensive
Profile RueiKe Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 14 Feb 16
Posts: 492
Credit: 378,512,430
RAC: 785
Taiwan
Message 1988112 - Posted: 31 Mar 2019, 8:09:53 UTC

I have just released a new version of amdgpu-utils:
https://github.com/Ricks-Lab/amdgpu-utils/releases/tag/v2.4.0

This version is includes full functionality for newer GPU compatibility and clearer messages:
    Implemented amdgpu-pac feature for type 2 Freq/Voltage controlled GPUs, which includes the Radeon VII.
    Implemented the amdgpu-pac --force_write option, which writes all configuration parameters to the GPU, even if unchanged. The default behavior is changed to now only write changed configuration parameters.
    Indicate number of changes to be written by PAC, and if no changes, don't execute bash file. Display execute complete message in terminal, and update messages in PAC message box.
    Implemented a new GPU type 0, which represent some older cards whose p-states can not be changed.
    Tuned amdgpu-pac window format.

ID: 1988112 · Report as offensive
Profile RueiKe Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 14 Feb 16
Posts: 492
Credit: 378,512,430
RAC: 785
Taiwan
Message 1991666 - Posted: 27 Apr 2019, 4:54:32 UTC

I have just released a new version of amdgpu-utils:
https://github.com/Ricks-Lab/amdgpu-utils/releases/tag/v2.5.0
    Implemented the --plot option for amdgpu-monitor. This will display plots of critical GPU parameters that update at an interval defined by the --sleep N option.
    Errors in reading non-critical parameters will now show a warning the first time and are disabled for future reads.
    Fixed a bug in implementation of compatibility checks and improved usage of try/except.

ID: 1991666 · Report as offensive
Profile [A.S.a.M.]koschi

Send message
Joined: 8 Jan 01
Posts: 15
Credit: 5,947,861
RAC: 15
Message 1998955 - Posted: 20 Jun 2019, 21:18:44 UTC

Hi Rick,

today we configured an RX580 to BOINC on Linux Mint 19.1. clinfo works, BOINC utilizes the GPU, however, amdgpu-utils don't find the card.
amdgpu-monitor showed "No AMD GPUs detected, exiting..." num_amd_gpus must have been 0 there. I couldn't fully understand how gpu_list.num_gpus() is defined to check what it was looking for.

Being Linux Mint, the official driver doesn't install, so I used the extracted OpenCL parts from AMDGPU-PRO 19.10. I'm doing that on Ubuntu 19.04 as well, there the tools work without problems.
What are you checking in that moment, where does that data come from?

Thanks!
ID: 1998955 · Report as offensive
Profile RueiKe Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 14 Feb 16
Posts: 492
Credit: 378,512,430
RAC: 785
Taiwan
Message 1999234 - Posted: 22 Jun 2019, 22:57:34 UTC - in response to Message 1998955.  

Hi Rick,

today we configured an RX580 to BOINC on Linux Mint 19.1. clinfo works, BOINC utilizes the GPU, however, amdgpu-utils don't find the card.
amdgpu-monitor showed "No AMD GPUs detected, exiting..." num_amd_gpus must have been 0 there. I couldn't fully understand how gpu_list.num_gpus() is defined to check what it was looking for.

Being Linux Mint, the official driver doesn't install, so I used the extracted OpenCL parts from AMDGPU-PRO 19.10. I'm doing that on Ubuntu 19.04 as well, there the tools work without problems.
What are you checking in that moment, where does that data come from?

Thanks!

Manually installing OpenCL is necessary to get compute working for SETI, but other components of the driver package are required for interacting with the GPU. The first thing that amdgpu-utils looks for to determine compatibility is the file:
/sys/class/drm/card?/device/pp_od_clk_voltage

There are many device files that are used from this location to read and write from the GPU. If critical files are missing or not readable, then the card is classified as not compatible.
ID: 1999234 · Report as offensive
Previous · 1 · 2 · 3 · 4

Message boards : Number crunching : Developing AMD GPU Utilities


 
©2025 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.