BzMiner v21.0.3
Release v21.0.3 of BzMiner. All feedback is welcome ;)
-- What's in this release (v21.0.3)
x New Coin: warthog
x Added option warthog_cpu_threads - Number of threads to use to compute the verus hashes. Default is 0, use number of cores available
x Added option warthog_max_ram_gb - Amount of RAM to use to store sha hashes while cpu threads are calculating verus hashes. Default is 4gb. Value of 0 will use max ram minux 1gb. If not enough avaiable ram, will use available ram minus 1gb. if still not enough ram, will use available ram / 2.
x Added option warthog_verus_hr_target - Specify the amount of verus hashrate each gpu should provide to the verus workers. If all gpu's have a verus hashrate specified, calibration will be skipped. Hashrates are specified in hashes per second, and are separated by spaces. Default is 0
- NOTE - Lower end cpus, or rigs with under 2gb may not be able to mine warthog, or may have very bad hashrate
- NOTE - Warthog gpu performance will depend on many variables, such as PCI generation (1,2,3,4), PCI lanes (1x, 4x, 8x, 16x), (if on risers, higher gen speeds can cause pci errors if cables are criss-crossed with other cables due to interference, leading to possible invalid sha shares sometimes), how many gpus are currently participating, ram speeds, ram and cpu caches, cpu speeds, and even the os (windows/linux) can have an impact. Just be aware that there are many reasons why different setups may cause the same card to have drasticaly different results from other setups using that same card.
- NOTE - Using all available processors will have a negative impact. If manually specifying threads, keep in mind that the os needs a processor to work on, bz itself needs a processor, gpus each need their own threads (they can share processors), and there's an additional processor pinned to 100% usage to distribute the work among the verus workers. bz will automatically reduce thread count to account for these if no thread count is specified.
- NOTE - Status column now shows gpu hashrate/verus hashrate, where gpu hashrate is how many sha hashes the gpu is doing, and verus hashrate is how many sha hashes its currently providing the verus workers. those numbers across the gpus should add up to match the verus hr in the pool status x Temporarily disabled Ironfish (next update should have ironfish back) x Other bug fixes
Thanks Son of a Tech for the BC-250! https://www.youtube.com/channel/UC0WNX0de8I1fgKUrjxiPaRA
--- Dynex Notes ---
- Fine tuning dynex_pow_ratio will likely give you better results than default settings
- intensity option will adjust how much vram is allowed to be used
- Intel ARC support still only for POW
-- dynex_pow_ratio -- Bz allows you to dedicate individual cards to either POW or POUW on Dynex using this option.
-
This is an array of values, one for each gpu
-
In config.txt , an example for 3 gpus would be "dynex_pow_ratio": [1.0, 1.0, 1.0]
-
In command line, and example for 3 gpus would be --dynex_pow_ratio 1.0 1.0 1.0
-
In hive, extra config args (notice the quotes around the array), an example for 3 gpus would be "dynex_pow_ratio": "[1.0, 1.0, 1.0]"
-
A value of 0.0 will mine ONLY POUW
-
A value of 1.0 (Default) will mine both POUW and POW. It will choose a POW ratio that matches POUW
-
A value of 2.0 will fully mine only POW. Any value higher than 1.0 will not mine POUW
-
A value between 0.0 and 1.0 will determine how much POW is mined, values closer to 1.0 will mine POW more intensely, while values closer to 0.0 will mine POW less intensely
-
A value between 1.0 and 2.0 will determine how intensely to mine ONLY POW
-
A statistic in the status column of the tables called "pow slip" will show you how much POW hashrate above or below the POUW hashrate you are doing. If below (-), you should increase your pow hashrate. If above, you are wasting resources doing unecessary POW hashrate and you should lower your POW hashrate. NOTE: It is not possible to be rewarded for POW hashrate above your POUW hashrate!
-- Dynex intensity -- The "intensity" option in Bz will determine how much vram to utilize to mine Dynex. a value of 64 (highest), will use all available ram, a value of 1 will use the minimum amount of ram. Default is 0 (converts to 64 internally)
https://www.bzminer.com/releases/v20.0.0/
-- Known Issues
- AMD polaris cards (eg. rx470, rx580) may not work with rethereum right now. Looking into this soon
- Only AMD opencl driver 21.50.2 and higher is currently supported, so update your amd driver if you run into opencl errors
- If you run into issues allocating larger Nexa LUT on Nvidia cards, please update Nvidia drivers
- Nvidia driver 530 - 535 have a bug that reports wrong clock frequencies. oc's should still be applied correctly. Please update to very latest nvidia driver (535 or higher) which appears to have fixed this bug
- If Nvidia memory temps are not showing, please update to latest nvidia driver
- Nexa is not working on Intel currently
NOTE: Nexa development is continued joint effort with Lolliedieb from lolMiner
Minerstat update command:
export version="21.0.3"; mstop; cd /tmp; wget https://bzminer.com/downloads/bzminer_v${version}_linux.tar.gz; tar -xvf bzminer_v${version}_linux.tar.gz; sudo cp bzminer_v${version}_linux/bzminer /home/minerstat/minerstat-os/clients/bzminer; mstart
MMPOS Update Command (Note: put in Initiate command prior to miner launch field in miner profile ->advanced)
export version="21.0.3" # Example version
if [ -f "/tmp/bzminer_v${version}_linux.tar.gz" ]; then
exit 0
else
cd /tmp; wget https://bzminer.com/downloads/bzminer_v${version}_linux.tar.gz; tar -xvf bzminer_v${version}_linux.tar.gz; sudo cp -adpR bzminer_v${version}_linux/bzminer /opt/mmp/miners/bzminer/
fi
Hive OS Update Command (assuming currently on v20.0.0)
wget https://bzminer.com/downloads/bzminer_v21.0.3_linux.tar.gz; tar -xvf bzminer_v21.0.3_linux.tar.gz; miner stop; cp bzminer_v21.0.3_linux/bzminer /hive/miners/bzminer/20.0.0/; miner start
Rave OS Update Command (assuming currently on v20.0.0)
stop && wget https://bzminer.com/downloads/bzminer_v21.0.3_linux.tar.gz && tar -xvf bzminer_v21.0.3_linux.tar.gz && cp -adpR bzminer_v21.0.3_linux/bzminer /app-data/miners/bzminer-20.0.0 && start
Checksums
bzminer_v21.0.3_windows.zip:
MD5: d73c83817048bc9646570f855510c950 SHA256: 307c39a7bfeb1935de6c1305c8868b83248e9eed3c2d26cdcb7e791cac7b5309
bzminer_v21.0.3_linux.tar.gz:
MD5: 7e1e09521fe1c936894e6f35e6afd7df SHA256: 111f3f047e91a0b46524ec9dd884469a4c47c185d9b117a36c2e08a2f5389b29