Open jmsjr opened 3 years ago
Looking at CLMiner.cpp, the check that is happening above, quoted in here :
// Check whether the current device has sufficient memory every time we recreate the dag
if (m_deviceDescriptor.totalMemory < RequiredMemory)
{
cllog << "Epoch " << m_epochContext.epochNumber << " requires "
<< dev::getFormattedMemory((double)RequiredMemory) << " memory. Only "
<< dev::getFormattedMemory((double)m_deviceDescriptor.totalMemory)
<< " available on device.";
pause(MinerPauseEnum::PauseDueToInsufficientMemory);
return true; // This will prevent to exit the thread and
// Eventually resume mining when changing coin or epoch (NiceHash)
}
... happens earlier than the changes in that commit hash that I indicated earlier, so it could not possibly allow AMD cards with 4GB to work / "extend their life".
So maybe I misunderstood that commit about "Extend the life of 4GB AMD cards" ??
Version: ethminer-0.19.0 compiled from source OS: Ubuntu 20.04.2 LTS Kernel: 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:39:42 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux AMD CPU card: Radeon RX 580 Series AMD GPU Pro driver: amdgpu-pro-21.10-1247438-ubuntu-20.04 ( https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-linux-21-10 )
I have a few AMD Radeon 4GB cards ( Radeon RX 580 Series ) that I have not used for a long time but would like to use them again for mining ( Note I also have a few nvidia 8GB cards that works quite well with ethminer-0.19.0 but is irrelevant for this issue ).
I noticed the following commit for 0.19.0 :
https://github.com/ethereum-mining/ethminer/commit/83ebd320885d8db97d4a3793836487d6a5f41624?branch=83ebd320885d8db97d4a3793836487d6a5f41624&diff=unified
... from @jean-m-cyr , and I was wondering, after having built 0.19.0 from source, is there anything else that I need to do ( e.g. a new command-line switch ? ) to enable this feature for 4GB AMD cards ?
I get a SIGSEGV below :
Benchmark has no errors / issues :
Simulation has no errors / issues as well :
I noticed that when running either the benchmark or the simulation, it shows:
... but when actually mining, that kind of output is not shown.