You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 24, 2022. It is now read-only.
Describe the bug
When using the Mesa OpenCL runtime on an AMD Radeon RX 480, no shares are submitted and frequently this line is reported: GPU 0 gave incorrect result. Lower overclocking values if it happens frequently.
To Reproduce
Steps to reproduce the behavior:
Install Mesa OpenCL, without RocM or AMDGPU=Pro OpenCL installed.
Run ethminer with Nicehash as the pool.
Expected behavior
Shares are submitted successfully.
Screenshots (Optional)
Environment (please complete the following information):
Operating System: Gentoo Linux kernel 5.15.7-gentoo, Mesa 21.3.2.
Additional context
AMDGPU-Pro works but fails after a while and causes kernel panics: #2385. RocM does not work at all due to lack of PCI-E atomics support in my motherboard. I am not overclocked at all, or even have overclocking software enabled, so the overclock message does not make sense unless the default values are not sane.
The text was updated successfully, but these errors were encountered:
Describe the bug
When using the Mesa OpenCL runtime on an AMD Radeon RX 480, no shares are submitted and frequently this line is reported:
GPU 0 gave incorrect result. Lower overclocking values if it happens frequently.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Shares are submitted successfully.
Screenshots (Optional)
Environment (please complete the following information):
Additional context
AMDGPU-Pro works but fails after a while and causes kernel panics: #2385. RocM does not work at all due to lack of PCI-E atomics support in my motherboard. I am not overclocked at all, or even have overclocking software enabled, so the overclock message does not make sense unless the default values are not sane.
The text was updated successfully, but these errors were encountered: