It's been almost a year since the first AMDGPU-Pro driver release. There are now two main release versions; 16.40 and 16.60. Although both versions supposedly support Ubuntu 16.04, version 16.40 with Ubuntu Desktop 16.04.2 is the only combination that works without a kernel update.
Ubuntu 16.04.2 is the first 16.04 release to use kernel version 4.8 instead of version 4.4. Using 16.40 with kernel version 4.4 would sometimes lead to problems such as kernel message log floods or powerplay problems. The typical powerplay problem was that the card would not switch to the full system and memory clock when running OpenCL programs.
Before a fresh Ubuntu install, I suggest disabling safeboot, since the AMDGPU-Pro drivers are not signed and therefore do not work with safeboot. If safeboot is already set up on your system, the driver install script will prompt you to disable it. Unlike the fglrx drivers, I have found the AMDGPU-Pro drivers will work along with the Intel i915 drivers. In a multi-GPU system, I like to leave a monitor connected to the on-board video for a system console. GPUs can easily be swapped in and out without having to move the monitor connection.
Before installing the driver, make sure your card is detected by running, "lspci | grep VGA". The installation instructions are straightforward, and don't forget to update the video group as mentioned at the end of the instructions. Otherwise OpenCL programs will not detect the GPU. Note that there is a bug in clinfo (/opt/amdgpu-pro/bin/clinfo) that causes it to display 14 for "Max compute units" instead of the actual number of GPU compute units. This bug is fixed in 16.60, which requires kernel 4.10 to work properly.
To test your GPU and the driver, you could try my ethminer fork. Although I built and tested it on Ubuntu 14.04/fglrx, it works perfectly on Ubuntu 16.04.2 with AMDGPU-Pro 16.40. Once you've started ethminer (or any other OpenCL program), you can check the core and memory clocks with the following commands:
The driver does not come with a tool like aticonfig for custom clock control. The driver does expose ways of controlling the clocks and voltage, and some developers have written custom programs using information from the kernel headers. Although nobody seems to have released a utility, the sgminer-gm sysfs code could likely be used as a template to create a stand-alone utility.
Hey Ralph, what does your fork do that is different than Genoils? Is it just stability changes or did you make performance changes too? Also, are there any downsides to update to the 4.10 kernel on 16.04.2 like you mention in your newer posts? Btw, your posts are very helpful. Thanks!!!ReplyDelete
Mainly stratum improvements, virtually all of which were merged back upstream. The big difference is I do Linux binary builds and JW(Genoil) did Windows builds. My 1.2.0nr build hangs with the 16.60 drivers, but was OK with 16.40. I took out some old #pragmas from the OpenCL kernel and it seems to work OK. Haven't had much time to work on it lately, but if I can free up an hour or two in the next few weeks I'll merge the 110 branch into main and push an updated binary that works with 16.60 (and hopefully 17.10 too).Delete