Radeon VII @ newegg for 500 dollars US on 11-27

[paulunderwood]

Originally Posted by ewmayer

Thanks-
Per the readme, single minus sign ... from within a subdir 'run0' where I have created a worktodo.txt file containing a pair of PRP assignments, I tried 'sudo ../gpuowl -user ewmayer' ... after entering my sudo password the run echoed same as the 2nd #fail above, just with an added 'config: -user ewmayer' line. Trying to instead login as root and run that way [this the Ubuntu 19.10 setup I created last week] and using the same pwd gives 'Authentication failure'. I don't recall entering any other pwd during the set-pwd phase of Ubuntu 19.10 setup.

Not needed yet since I can't run at all, but how do determine the max stock voltage of my R7?

Two things:

Make sure you are in the group "video" by running id ewmayer. If not, you need to be added to it and re-login.

To create a root password run sudo passwd root and take it from there. It is best not to run X as root, but in a terminal type su and enter root's password.

[S485122]

Originally Posted by ewmayer

...
I don't recall entering any other pwd during the set-pwd phase of Ubuntu 19.10 setup.
...

If my memory serves well once installed there is no password for the root account and it can't be used because of that until you have set it via "sudo passwd root".

Jacob

[ewmayer]

Originally Posted by S485122

If my memory serves well once installed there is no password for the root account and it can't be used because of that until you have set it via "sudo passwd root".

Jacob

That worked - thanks - but even running as root, I still get the getDeviceIDs error, whether I use -user ewmayer, -user root, or no -user stuff at all.

I've PMed Mihai, hopefully he can provide further guidance.

[paulunderwood]

Originally Posted by ewmayer

That worked - thanks - but even running as root, I still get the getDeviceIDs error, whether I use -user ewmayer, -user root, or no -user stuff at all.

I've PMed Mihai, hopefully he can provide further guidance.

Did you login to root in a terminal by using su?

[ewmayer]

Originally Posted by paulunderwood

Did you login to root in a terminal by using su?

Yes ... 'su' using the newly-set root pwd, instead 'sudo'.

[kriesel]

Originally Posted by ewmayer

First I'd like to play with some basic single-instance running, but something is borked. The readme says "Self-test: simply start gpuowl with any valid exponent..." but does not say how to specify that expo via cmd-line flags. I tried just sticking a prime expo in there, then without any arguments whatever, both gave the following kind of error:

ewmayer@ewmayer-haswell:~/gpuowl$ ./gpuowl 90110269
2020-02-01 18:43:36 gpuowl v6.11-142-gf54af2e
2020-02-01 18:43:36 Note: not found 'config.txt'
2020-02-01 18:43:36 config: 90110269 
2020-02-01 18:43:36 device 0, unique id ''
2020-02-01 18:43:36 Exception gpu_error: DEVICE_NOT_FOUND clGetDeviceIDs(platforms[i], kind, 64, devices, &n) at clwrap.cpp:77 getDeviceIDs
2020-02-01 18:43:36 Bye
ewmayer@ewmayer-haswell:~/gpuowl$ ./gpuowl
2020-02-01 18:44:02 gpuowl v6.11-142-gf54af2e
2020-02-01 18:44:02 Note: not found 'config.txt'
2020-02-01 18:44:02 device 0, unique id ''
2020-02-01 18:44:02 Exception gpu_error: DEVICE_NOT_FOUND clGetDeviceIDs(platforms[i], kind, 64, devices, &n) at clwrap.cpp:77 getDeviceIDs
2020-02-01 18:44:02 Bye

Matt had noted to me, "If the PRP test starts we are good to go. If it fails with something along the lines ofclGetDeviceId then gpuowl couldn't see the card." How to debug that latter problem?

./gpuowl -help
should give a big list of fft lengths, then at the end a list of detected gpus. If that's an empty list, confirm it with something else like an OpenCL diagnostic tool. Possibly one of the tools listed at the top of page 3 of the pdf attachment at https://www.mersenneforum.org/showpo...74&postcount=6
Then fix the OpenCL driver installation somehow. (Can't help you there, too little gpu linux experience to go by.)

On Windows one can also use GPU-Z to check driver version, OpenCL and other standards' parameters, etc. Some of the other hardware monitoring tools listed on pages 1-2 of that same attachment might also allow that.

[preda]

Originally Posted by ewmayer

That worked - thanks - but even running as root, I still get the getDeviceIDs error, whether I use -user ewmayer, -user root, or no -user stuff at all.

I've PMed Mihai, hopefully he can provide further guidance.

Does clinfo work? (i.e. does it detect any devices)

If clinfo does not detect anything, then the problem is with the OpenCL setup in the system (i.e. drivers, ROCm).

[M344587487]

Maybe the issue is to do with me recommending he install ROCm using the upstream drivers ( https://github.com/RadeonOpenCompute...kernel-drivers ), it's been a long time since I did a ROCm setup and something in the installation procedure or environment may have changed breaking this method or requiring extra steps. rocm-smi can see the card but I didn't have him check clinfo or rocminfo.

[preda]

Originally Posted by M344587487

Maybe the issue is to do with me recommending he install ROCm using the upstream drivers ( https://github.com/RadeonOpenCompute...kernel-drivers ), it's been a long time since I did a ROCm setup and something in the installation procedure or environment may have changed breaking this method or requiring extra steps. rocm-smi can see the card but I didn't have him check clinfo or rocminfo.

If it's ROCm 3.0, it may have broken OpenCL, see https://github.com/RadeonOpenCompute/ROCm/issues/977

ROCm 2.10 works for me.

[paulunderwood]

Originally Posted by preda

If it's ROCm 3.0, it may have broken OpenCL, see https://github.com/RadeonOpenCompute/ROCm/issues/977

ROCm 2.10 works for me.

This looks like the best advice:

OlegSmelov commented on Dec 23, 2019

For those wondering how to revert to a previous version on Debian-based distros:

sudo apt autoremove rocm-dkms rock-dkms
sudo vim /etc/apt/sources.list.d/rocm.list

Replace http://repo.radeon.com/rocm/apt/debian/ with http://repo.radeon.com/rocm/apt/2.10.0/

sudo apt update
sudo apt install rocm-dkms # or any other set of packages you need

[ewmayer]

Originally Posted by kriesel

./gpuowl -help
should give a big list of fft lengths, then at the end a list of detected gpus. If that's an empty list, confirm it with something else like an OpenCL diagnostic tool. Possibly one of the tools listed at the top of page 3 of the pdf attachment at https://www.mersenneforum.org/showpo...74&postcount=6
Then fix the OpenCL driver installation somehow. (Can't help you there, too little gpu linux experience to go by.)

Thanks - note the help command needs --help or -h ... anyhow, that gives me

[build version]
Command line options:
...
-device <N>: select a specific device:
[timestamp] Exception gpu_error: DEVICE_NOT_FOUND clGetDeviceIDs(platforms[i], kind, 64, devices, &n) at clwrap.cpp:77 getDeviceIDs

I don't see the big list of FFT lengths you mentioned.

Originally Posted by preda

Does clinfo work? (i.e. does it detect any devices)

If clinfo does not detect anything, then the problem is with the OpenCL setup in the system (i.e. drivers, ROCm).

Is that supposed to be an installed command? 'which clinfo' comes up empty, and I don't see any such command in /opt/rocm/bin.

Originally Posted by preda

If it's ROCm 3.0, it may have broken OpenCL, see https://github.com/RadeonOpenCompute/ROCm/issues/977

ROCm 2.10 works for me.

That sounds like a possible suspect, given that I installed Ubunto 19.10, which is newer than the 19.04 Matt based his setup-recipe on.

How do I query the version number for the ROCm install on my system?

Once I do that, if it indeed is 3.0, I'll try the Debian-distro reversion commands Paul dug up, which hopefully will work similarly on Ubuntu.