Releases: rigelminer/rigel
Releases · rigelminer/rigel
Rigel 1.4.5
- (IronFish) Minor performance improvements for 30xx series GPUs
Rigel 1.4.4
- (IronFish) Minor performance improvements
Rigel 1.4.3
- (IronFish) Minor performance/efficiency improvements
Rigel 1.4.2
- (IronFish) Stratum v2 support for major pools, hashrate increase
Bug fixes:
- Overclock settings fail to apply on drivers older than v515
Rigel 1.4.1
- Add ZIL countdown display in TUI and console reports - experimental feature (enable with
--zil-countdown
) - (IronFish) Improve compatibility with mining pools - flexpool, herominers, kryptex
Rigel 1.4.0
- Add support for mining Alephium (
-a alephium
) and IronFish (-a ironfish
), dev fee 0.7%
Dual and triple modes with ETC, ETHW, OCTA and ZIL are supported too.
Bug fixes:
- Memory temperature is not displayed on 530+ drivers
Rigel 1.3.12
- Add
--stats-interval
parameter to configure GPU stats report frequency - Add support for mining Octa.Space coin
The coin uses ethash algorithm, however you need to set-a octa
to prevent the miner rebuilding DAG for dev fee
Dual and triple modes with Kaspa and Zil are supported too.
Bug fixes:
- (Kaspa, ETC) Duplicate shares when mining to Flexpool, K1, 2miners and some other pools
Rigel 1.3.11
- (Nexa) Minor performance/efficiency improvements
- Display average GPU power consumption instead of the most recent value reported by the driver - this reduces fluctuations in power readings and efficiency numbers. The averaging window size can be overridden with
--power-avg
parameter (default 10 seconds)
Rigel 1.3.10
- (Nexa) Performance/efficiency improvements
As with the previous version, set--kernel 2
to use a more energy efficient implementation for low-end/mid-range 30xx GPUs, otherwise the miner will aim for maximum hashrate even at a cost of higher power draw
Rigel 1.3.9
- (Nexa) Add
--kernel
parameter to switch between different nexapow implementations (see notes below)
Bug fixes:
- (UI) dual mining view switch (e.g. nexapow <-> zil) is broken on Windows
Additional notes
Some GPUs saw an efficiency drop in v1.3.8 compared to v1.3.7. This release allows opting in for 1.3.7 performance level by selecting kernel #2 for the affected GPUs.
Example: --kernel _,_,2,_
<- this will enable the "1.3.7 mode" for the third GPU. The rest will work as before (v1.3.8).
If all your GPUs were working better on 1.3.7, then it's sufficient to set --kernel 2
, it'll apply to all cards.
See --kernel
parameter description in README.md
or https://github.com/rigelminer/rigel for more details.