The miner runs for varying lengths of time and then encounters a 'no response'. Then it remains stuck (see below) until I hit ctrl+c to cancel the current task. Sometimes it runs for several hours before encountering this issue, sometimes only a few minutes.
In another thread it was recommended to run it with increased verbosity and so I did, but I couldn't figure out why it came to a stop. In yet another thread I saw the suggestion to increase --response-timeout and I've tried several values from 30 to 360 seconds which seem to delay the issue temporarily but alas the error keeps occurring.
In the former windows environment the card was running in previously to the current OS it ran at Mem OC +1200MHz regularly at ~59MH/s without any issues. Now in Mint it is running at stock clock yielding about 49MH/s and the issue described above.
Any help figuring out what to investigate in order to resolve the issue is greatly appreciated! Thanks!
The miner runs for varying lengths of time and then encounters a 'no response'. Then it remains stuck (see below) until I hit ctrl+c to cancel the current task. Sometimes it runs for several hours before encountering this issue, sometimes only a few minutes.
In another thread it was recommended to run it with increased verbosity and so I did, but I couldn't figure out why it came to a stop. In yet another thread I saw the suggestion to increase --response-timeout and I've tried several values from 30 to 360 seconds which seem to delay the issue temporarily but alas the error keeps occurring.
In the former windows environment the card was running in previously to the current OS it ran at Mem OC +1200MHz regularly at ~59MH/s without any issues. Now in Mint it is running at stock clock yielding about 49MH/s and the issue described above.
Any help figuring out what to investigate in order to resolve the issue is greatly appreciated! Thanks!
The command
Expected behavior Should be mining for days on end until forced restart.
The error
pressing ctrl+c yields
Environment: