How to understand the messages in the SRBMiner window? Share statistics, mining status, and working parameters.
What can you see in the miner window?
Before launching SRBminer, applies the environment parameters:
Detecting GPU Devices — the miner exposes graphics cards on which it can mine, forms received data into a table, and lists graphics cards and their parameters : - GPU0 GPU1 GPU2 - serial number of the graphics card in the miner (Please note that counting starts from 0); - radeon_rx_580_series — graphics card model; - ellesmere — the code name of graphics card; - MEM: 8 GB — graphics card memory amount; - CU: 36 — CU (Computing Units) number of computing units of the graphics card; - BUS 01 — PCIE number in the system.
Brief information about the miner's version and quick commands: - Press 's' to display stats — press s to get data on the mining statistics; - Press 'h' to display hashrate - press h to get hashrate data; - Press 'p' to switch to the next pool — press p to switch to the next pool (if additional pools were specified in the miner settings); - Press 'o'to switch to the previous pool — press o to switch to the last pool (if additional pools are set in the Miner settings); - Press 0-9 to disable/enable GPU 0-9, shift+0-9 for GPU 10-19 — use keys from 0 to 9 to enable and disable graphics cards from the first (GPU0) to 10 (GPU9), to enable/disable graphics cards from 11 to 20 use key combination from shift+0 to shift+9, respectively; - Press + or - to change GPU boost value — use keys + and - to adjust the algorithm to improve mining on graphics cards.
Information about the general parameters of the miner: - Algorithm\\s autolykos2 1% fee — the algorithms that are selected for mining and the miner developer's fee for them; - GPU mining enabled — reports whether graphics card mining is enabled (enabled or disabled); - CPU mining disabled — reports whether CPU mining is enabled (enabled or disabled); - Watchdog enabled — reports whether the miner's watchdog is enabled (enabled or disabled); - GPU tweaking enabled — reports whether the optimization of mining on graphics cards is (enabled or disabled);
The miner reports what mining intensity was used for the graphics cards. The data is shown in a table, where the serial number of the graphics card, the serial number of the PCIE in the system, and the selected intensity are displayed.
The miner reports that the mining optimization libraries are loaded.
The address of the pool, its port, and the algorithm that is set for mining.
The complexity of the share on the pool on a particular algorithm (set by the pool).
Graphics cards take turns forming a database (or DAG file, depending on the algorithm) for mining, block height, time for which the table (or DAG file) is formed, and the algorithm on which mining is started.
The miner reports which algorithms are applied to the graphics cards in order (you can manually adjust them with the + and - keys).
result rejected — the miner reports that the share is rejected and also reports on which graphics card. Rejected shares, often due to connection to the Internet, or just late shares (stale) — someone solved the job earlier. There is no way to get rid of them completely, but it is believed that the "norm" is 1-2% of the total number of all shares.
result accepted — message about successfully processed and verified share. It is reported which graphics card found it and for what period of time was confirmed on the pool.
The miner reports receiving a new job from the pool, its ID, block height, and algorithm.
Brief statistics about the mining reported periodically: - [autolykos2] — the algorithm being mined. The zero at the beginning means that it is the first and, in our case, the only algorithm. The miner counts down from zero. - list of graphics cards, which specifies the serial number of the graphics card, its hash rate, and the ratio of processed shares, where: [ 20 | 1 | 0 ] - 20 is the total number of shares processed (accepted share); - 1 is the number of rejected shares. Rejected shares, most often due to an Internet connection, or just late shares (stale) — someone solved the job earlier. There is no way to get rid of them completely, but it is accepted that the "norm" is 1-2% of the total number of all shares. - 0 — damaged, incorrect shares — such shares appear in case of overclocking, graphics card error, or memory failure. The graphics card counts wrong (2+2=5). - Total: - total hashrate of all graphics cards. - Brief summary of the state of graphics cards: - GPU0 — sequence number of graphics card; - T: 48c — (Temperature) temperature of the graphics card, in degrees Celsius; - CC: 1247MHz — (Core Clock) core frequency, in megahertz; - MC: 2030MHz — (Graphics Memory Clock) memory frequency, in megahertz; - RPM: 2350 — (Rotations Per Minute) fan speed, in rotations per minute; - P: 61W — (Power) power consumption in watts. Note that AMD graphics cards only show core consumption. They do not take memory consumption into account. So you can surely add about 30-35 watts to get more accurate numbers.
GPU2 DEAD  — Miner reports that the graphics card with serial number 2 (actually the third graphics card, miner counts graphics cards from 0) had a critical failure. The graphics card is not responding to miner's requests. In that case, the miner will try to restart automatically (watchdog work) to try to fix the situation. It may also indicate that the graphics card overclocking, tweaks, or improvements are not optimal. So reduce the load or mining intensity for that graphics card.
The miner stops the process of mining on all streams (active graphics cards).
The miner restarts, starting the process from point 1.