Pages:
Author

Topic: [ANN] Rigel 1.13.0 - Radiant, Nexa and IronFish GPU miner (Nvidia only) - page 11. (Read 6424 times)

newbie
Activity: 1
Merit: 0
After switching to zil, the miner does not return to nexa.
newbie
Activity: 62
Merit: 0
need dual mining, with intensity setting nexa+ergo nexa+kaspa nexa+ergo+kaspa
jr. member
Activity: 45
Merit: 3
Rigel 1.3.0

* Add Nexa mining support (2% dev fee)

Bug fixes:
* Miner terminates connection with a pool if it issued a job but didn't respond to a previously sent RPC request
newbie
Activity: 22
Merit: 0
Dear dev,
I really look forward to the function of the failover pools in pools.txt file!

You can set failover pools by repeating "-o" parameter for each pool:
Code:
-o -o -o -o
Hello.
I am aware of this possibility.
But I would like to have this functionality in a separate file with backing pools.txt, like Claymore did!

Hi, apart from development effort this would require some extra design work as we'd be introducing another way of passing pool URLs to the miner and need to figure out what takes precedence when and so on. I may put this on my todo list but I'm afraid it'll be low priority for now. Thanks for understanding.

OK, when you do that (add in pools.txt ), inform. We and our clients will use your program.

Thanks.
jr. member
Activity: 45
Merit: 3
Rigel 1.2.1

* (Kaspa) Minor performance improvements, mainly Pascal GPUs
* Add `--mt` parameter to enable memory tweaks for GDDR5/GDDR5X Pascal GPUs

Bug fixes
* (Kaspa) Stale shares when mining to ks_pplns
* (Windows) Miner sometimes fails to find NVML library (e.g. driver 466.77)
* `--fan-control` argument validation is broken
newbie
Activity: 11
Merit: 0
´PUT THE MINER IN HIVEOS PLZ
jr. member
Activity: 45
Merit: 3
IT WORKS IN HIVEOS?


No, but if you could approach their support with a request to integrate Rigel that would be great  Smiley
newbie
Activity: 11
Merit: 0
IT WORKS IN HIVEOS?
jr. member
Activity: 45
Merit: 3
Rigel 1.2.0
* (Kaspa) Minor performance improvements
* Add dev fee:
  * ethash - 0.7%
  * etchash - 0.7%
  * zil - 0%
  * kheavyhash - 0.7%
* (ETHW, ETC) Using `stratum` protocol in the pool URL will now resolve to `ethstratum` for Nicehash, and `ethproxy` for all other pools. Previously `ethstratum` was used by default.

Bug fixes:
* (Kaspa) mining to ETC Hiveon pool is broken
jr. member
Activity: 45
Merit: 3
Dear dev,
I really look forward to the function of the failover pools in pools.txt file!

You can set failover pools by repeating "-o" parameter for each pool:
Code:
-o -o -o -o
Hello.
I am aware of this possibility.
But I would like to have this functionality in a separate file with backing pools.txt, like Claymore did!

Hi, apart from development effort this would require some extra design work as we'd be introducing another way of passing pool URLs to the miner and need to figure out what takes precedence when and so on. I may put this on my todo list but I'm afraid it'll be low priority for now. Thanks for understanding.
newbie
Activity: 22
Merit: 0
Dear dev,
I really look forward to the function of the failover pools in pools.txt file!

You can set failover pools by repeating "-o" parameter for each pool:
Code:
-o -o -o -o
Hello.
I am aware of this possibility.
But I would like to have this functionality in a separate file with backing pools.txt, like Claymore did!
What is the difference for mining?
Older miners prefer the line with the settings in the BAT file.
On Linux, you also add additional settings.
Or is it difficult for you to backup a BAT file to run the miner?
Or you can't make a BAT file?


In a BAT file, this is inconvenient, confusing, distracting! I agree with Dubai-Industry.
Many beginners do not work with such programs because of this.

Inconvenient? Confusing? lol
Maybe it is better for you to look for another hobby? Maybe fishing?
Claymore style is outdated for many years.

Everything is clear with you ...
I don't see anything wrong with the fact that there are different people in mining (beginners, inexperienced, those who are used to working with 1 program and use mining as a hobby, etc.) and want to configure it differently.

If you are not ready to work with clients, then why start doing anything at all...
member
Activity: 1558
Merit: 69
Dear dev,
I really look forward to the function of the failover pools in pools.txt file!

You can set failover pools by repeating "-o" parameter for each pool:
Code:
-o -o -o -o
Hello.
I am aware of this possibility.
But I would like to have this functionality in a separate file with backing pools.txt, like Claymore did!
What is the difference for mining?
Older miners prefer the line with the settings in the BAT file.
On Linux, you also add additional settings.
Or is it difficult for you to backup a BAT file to run the miner?
Or you can't make a BAT file?


In a BAT file, this is inconvenient, confusing, distracting! I agree with Dubai-Industry.
Many beginners do not work with such programs because of this.

Inconvenient? Confusing? lol
Maybe it is better for you to look for another hobby? Maybe fishing?
Claymore style is outdated for many years.
newbie
Activity: 10
Merit: 2
Dear dev,
I really look forward to the function of the failover pools in pools.txt file!

You can set failover pools by repeating "-o" parameter for each pool:
Code:
-o -o -o -o
Hello.
I am aware of this possibility.
But I would like to have this functionality in a separate file with backing pools.txt, like Claymore did!
What is the difference for mining?
Older miners prefer the line with the settings in the BAT file.
On Linux, you also add additional settings.
Or is it difficult for you to backup a BAT file to run the miner?
Or you can't make a BAT file?


In a BAT file, this is inconvenient, confusing, distracting! I agree with Dubai-Industry.
Many beginners do not work with such programs because of this.
legendary
Activity: 1834
Merit: 1131
Dear dev,
I really look forward to the function of the failover pools in pools.txt file!

You can set failover pools by repeating "-o" parameter for each pool:
Code:
-o -o -o -o
Hello.
I am aware of this possibility.
But I would like to have this functionality in a separate file with backing pools.txt, like Claymore did!
What is the difference for mining?
Older miners prefer the line with the settings in the BAT file.
On Linux, you also add additional settings.
Or is it difficult for you to backup a BAT file to run the miner?
Or you can't make a BAT file?
newbie
Activity: 19
Merit: 0
Dear dev,
I really look forward to the function of the failover pools in pools.txt file!

You can set failover pools by repeating "-o" parameter for each pool:
Code:
-o -o -o -o
Hello.
I am aware of this possibility.
But I would like to have this functionality in a separate file with backing pools.txt, like Claymore did!
jr. member
Activity: 45
Merit: 3
Dear dev,
I really look forward to the function of the failover pools in pools.txt file!

You can set failover pools by repeating "-o" parameter for each pool:
Code:
-o -o -o -o
newbie
Activity: 19
Merit: 0
Dear dev,
I really look forward to the function of the failover pools in pools.txt file!
member
Activity: 1558
Merit: 69
how run on HiveOS?

HiveOS don´t support it yet native. So wait for the integration.
mmpos integrated rigelminer in the last agent 3.0.20.
newbie
Activity: 49
Merit: 0
how run on HiveOS?
member
Activity: 1558
Merit: 69
Rigel 1.1.1

* Improve Kaspa mining performance
* DNS-over-HTTPS support (see `--dns-over-https`)
* Allow setting hashrate averaging window (see `--hashrate-avg`)
* Add `--password` (`-p`) parameter to set the password for pool authorisation
* Fix applying negative core and memory clock offsets

nice release. 5% more hashrate on Kaspa compared the previous version - and also slightly higher as lolminer.
Really good miner, many good features from the start.
Pages:
Jump to: