 Show Posts
|
|
Pages: [1] 2 »
|
|
Only 0,5% of hashrate improvement... probably wrong the Changelog.
|
|
|
|
Wait are you for real? The DAG file isn't even up to 5GB yet, im guessing it should be around 4.7/4.8 DAG file Size, I am glad that lol miner still works for you but for how long? Have you tried every other ETH miners like Trex and NBminer?  I tryed all the different miners in HiveOS (TRex, NBMiner, GMiner, ... ) and the only working is lolMiner, I see DAG size is nearly 4.9Gb... It has stopped from yesterday. Happy to continue mining with it :-) |
|
|
|
|
Hi,
After new epoch 487 my 1060 5Gb and P102-100 5Gb, have stop working. I tried different miners and only lolMiner is working. Let's see how many time still working.
|
|
|
|
Finally we are able to see Memory Temps thanks to lolMiner 1.47 in HiveOS UI. Just only run this command to see Memory Temp in the HiveOS UI: Memory Temp: sed -i 's/Core_Temp/Mem_Temp/g' /hive/miners/lolminer/h-stats.sh Core Temp: (Revert) sed -i 's/Mem_Temp/Core_Temp/g' /hive/miners/lolminer/h-stats.sh Here are a pair of videos showing it: https://www.youtube.com/watch?v=aUONTFvEMUEhttps://www.youtube.com/watch?v=KVrogExW6BwIt will work for: RTX2070S RTX2080S RTX2080TI RTX 3070 TI RTX 3080 10GB RTX 3080 12GB RTX 3080 TI RTX 3090 A2000 A4000 A5000 Some Models of: RTX2060 RTX2070 RTX2080 3060TI |
|
|
|
It is finally able in HiveOS  |
|
|
|
Any news on lhr side of cminer?
thanks
alex
Yes I'm waiting too... I hope with the actual situation no Corona situation with the developers...  |
|
|
|
Any option to have it in RaveOS??
You could try to ask RaveOS in telegram group, I did for HiveOS but no answer yet... |
|
|
|
0.6-212@211211 🐧
What's new?
MINERS 👷♂️
⛏ TeamRedMiner v0.8.7
* added offline benchmark mode for almost all algos, see --benchmark;
* improved situations with the "Dev pool failed to connect." error message appearing;
* users in China should preferably run with --dev_location=cn;
* added experimental support for DNS-over-HTTPS, see --dns_https and --dns_https_sni
⛏ T-Rex v0.24.8
* added DNS-over-HTTPS support when resolving mining pool domain names, see dns-https-server for details;
* added an option not to set mining pool domain name in SNI header for SSL connections, see no-sni;
* resolve domain names through SOCKS5 proxy if proxy is set;
* display mining pool IP address in console; bug fixes
⛏ TeamBlackMiner v1.32
* fixed CPU validation error on ethproxy pools that caused rejects/skipping valid work;
* added LHR detector and reset the device if detected, removed behavior which reset GPUs every hour which was in v1.30-v1.31;
* removed some LHR code for non LHR cards;
* CUDA devices that are busy/unavailable will be skipped instead of program exit;
* reduced the use of stack, also reduced the overall memory needed;
* removed memleak in --list-devices and --version
I cannot install in all my rigs CMiner. I follow the Custom Miner guide, I was able in nearly all of them, but I cannot do it. Is it any option to be included as a common miner by HiveOS?.That sure will go then. Many thanks |
|
|
|
How is the API looks like? Do you take a API format from another miner to see hashrate and so on in HiveOS?
Hello Sir. Well, the API does not mimic any existing miner at the moment, but is indeed used by the custom miner package we did build for HiveOS. In fact the current Api was heavily inspired by the requirements of the Hive custom miner packages, but it is not final yet. For example we plan to add the GPU names, the watts consumed as well as the accepted and rejected shares per graphic card in the next version. At the moment the API output is a json file over http (so it can be requested via curl) with the following format - here an example of a 3070 LHR + 3070 FHR on moderate clocks. {
"total_hs": 102656.72095372647,
"hs": [41565.117000464095, 61091.603953262376],
"hs_units": "khs",
"temp": [48,61],
"fan": [40,44],
"uptime": 390,
"ver": "21.12.15",
"ar": [12,0],
"bus_numbers": [2,3]
}
You see the interface is very basic at the moment, but in our opinion a solid base to build upon. I'm really happy with the integration with HiveOS... it really make easy to mine and to controll it many thanks!! I have try also LHR. I have to be honest, it is not the best at the moment, but it hasn't get locked in all the test I did. I hope there will be more improvements . There are also some youtubers showing how to install it: https://www.youtube.com/watch?v=6b7KxXS9aGM |
|
|
|
Thanks for reporting back. Really appreciate it! We are working on a LHR code and hope to have it done before the years change. Speed is looking decent there, but we still have the one or other lock that we would like to avoid for a better UX. Likely before we will add ETC support early next week and currently also researching on how to add UBIQ. Beside that one of our engineers at the moment looking into the structure of Hive and RaveOs custom miners requirements, so we can build a statistics reading API that can be used with it. Very busy to get things done  Any new information when it will be some of these updates released? |
|
|
|
Thanks for reporting back. Really appreciate it! We are working on a LHR code and hope to have it done before the years change. Speed is looking decent there, but we still have the one or other lock that we would like to avoid for a better UX. Likely before we will add ETC support early next week and currently also researching on how to add UBIQ. Beside that one of our engineers at the moment looking into the structure of Hive and RaveOs custom miners requirements, so we can build a statistics reading API that can be used with it. Very busy to get things done That will be really interesting... Is it any option to select devices in case we have a mix rig with LHR to put the NO LHR with CMiner? |
|
|
|
I come with my 24h test results: I have to be honest... I'm really surprised with the result of the miner, I was complete incredulous but after the 24h test, I see an amazing result, reported is nearly like average. The result after 24hours in at the pool. Reported = 689.7 Mhs Average = 686.9 Mhs (with my previous miners I was around 674-680 that's nearly 1%-2% less) Stales are also really good a bit lower than before, but that could be something with the connection.   I really hope you are able to open LHR with these results, to try more rigs. |
|
|
|
|
I'm a bit spectish about that, but I will try it 24hours... To say how much inflate or not.
At the moment the values it shows are incredible in my Nvidia Rig... but I want to check at the pool.
RTX 3070
62.70 Mhs CMiner
62.56 Mhs TRex
62.55 Mhs NBMiner
62.44 Mhs GMiner
62.25 Mhs PhoenixMiner
61.91 Mhs lolMiner
61.80 Mhs Nanominer
I will come back with my test
|
|
|
|
|
Totally agree, the are new updates of the test in the webpage!!
|
|
|
|
--kernel [5] --xintensity [4096] (no add --tweak and no add --dagintensity) Pictures say more than words. This is a real test on a real mining pool.. With a real profit difference. The hashrate you see is real. The hashrate reported in the miner window is confirmed. Why don't you do a test on the 2miners pool with --xintensity 4096? Compare it with all the other miners. And you will see why more and more ppl are switching to the Team Black Miner... --kernel [5] --xintensity [4096] (no add --tweak and no add --dagintensity) Pictures say more than words. This is a real test on a real mining pool.. With a real profit difference. The hashrate you see is real. The hashrate reported in the miner window is confirmed. Why don't you do a test on the 2miners pool with --xintensity 4096? Compare it with all the other miners. And you will perhaps you will understand why more and more ppl are switching to the Team Black Miner... Yes it said all... You said Pool 53 Mhs and is 50Mhs... where are this 3Mhs? Team Bluff Miner! (TBM)! Please stop lying the people!! When you give real Numers you will have people using it. Do it really, is not a problem, people like the support, not the lies!! |
|
|
|
|
Yes it said all... You said Pool 53 Mhs and is 50Mhs... where are this 3Mhs?
|
|
|
|
This is not a real test. The TRM Ethash Miner Tester v1.0.0 is reducing the difficulty too much. Why don't you do a real test with 1 million shares on a normal pool? When the difficulty is low, the gpu mining software will need to submit all the found solutions in a warp to the pool,. On high diff only 1 solution is found, but on low diff 16 or more could be found, and this could cause the miningsoftware to skip sending solutions to the pool because 2 or 4 is the maximum solutions limit per warp in the optimized code.. An other problem is that on low difficulty the jobs enter the miner much more rapidly, and then the gpu has to abort work more often. So by reducing the workload (intensity) of each warp it will give an advantage in the test. This means that it is easy to improve the "test results" in the simulation, but it won't improve the profit on the pool... Users who have switched to the team black miner has reported more than +5% poolside profit. Check it out... https://www.youtube.com/watch?v=YtFqb8I_eVIAnd read the faq for the optimal pools and settings. https://github.com/sp-hash/TeamBlackMiner/blob/main/FAQ.mdHow can you see is not a real test?. You can put more difficulty in the test if you want it ... it will only take more time. I test your miner, and I discard it fast when I see how dishonest is your hashrate... In our groups we call it instead of Team Black Miner (TBM) the Team Bluff Miner (TBM). Please, be honest with your hashrate and you will have people that use it, with the great support you give. But I don't accept the lies!! |
|
|
|
Could you please run latest SRBMiner (0.8.3) too, im curious how it compares to this company of 'famous' miners ?
It is not my website... I only look on it... It will be interesting SRBMiner, Miniz and ethermine. My test with SRBMiner in ERGO have been always honestly reports. |
|
|
|
I did not understand how these experts conducted their tests. All tests must be carried out synchronously and on the same video cards.
Of course, you need to count the received shares, but in practice the difference is not big.
The problem can also be in the case of excessive overclocking and the mining farm is unstable.
All important points but as you say the difference is not big, and it's not big enough to be significant. But it's being used to claim dishonesty in hash reporting when there are many other factors that could cause bigger differences. The history is a feud between 2 closed source miners and claims of which was the fastest. One of the miner's devs decided to prove it with a challenge and a test tool. The feud seemed to have died down but this may be an attempt to revive it. It is very important for a miner to achieve stable work from a mining farm. For example, I use T-Rex, I learned how to fine tune this miner for my AMD video cards. No article will convince me to change the miner, because even if I lose 1-3% of the shares, this will not greatly affect my profit. Miners do not pay attention to such articles, because they understand that identical video cards can have different hash rates and different overclocking options. "For example, I use T-Rex, I learned how to fine tune this miner for my AMD video cards." Are you payed from T-Rex?? 1st time I read T-Rex in AMD ... |
|
|
|
It is updated to last miners release in ETH:  |
|
|
|
|
