 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
|
Which firmware is for the s17 Pro?
Just want to be sure before I go tinkering around.
Also how does this compare to vnish and brainsos+ firmwares out there?
|
|
|
|
I see where my antminer X3 is supported but none of the coins are listed and the unspecified cryptonight options do not produce any results.
Is there a way to add coins or something else I need to do?
Awesome Miner can monitor any Antminer, including Antminer X3, no matter which pool you are mining on and no matter which coin you are mining. There are not many CryptoNight coins available these days, but you should be able to see a few if you go to the Coins tab in Awesome Miner and sort by algorithm. Please note that the coins in Awesome Miner only relates to the display of Revenue and Profit for the mining. You can mine any CryptoNight-based coin on any pool on your Antminer. Which pool/coin are you mining on right now? Got them pointed at Mining-Dutch on the multiport. This is mainly being used to heat the rooms, but was hoping to track wattage or revenue/profit and the like. |
|
|
|
|
I see where my antminer X3 is supported but none of the coins are listed and the unspecified cryptonight options do not produce any results.
Is there a way to add coins or something else I need to do?
|
|
|
|
[...]
Ok, but across all my Gekko Devices I have been getting 6Th+ and the pool is only showing about 2.5Th. |
|
|
|
|
I am still getting the "(Too low difficulty)" message after trying several other pools.
Do i need to set the difficulty to something higher than the "Diff:14.7T" that is currently showing in the cgminer terminal?
|
|
|
|
|
I am running the May 2019 firmware on a ubuntu 18.04 machine for my set up over the last year with no issues until recently.
I am noticing that on viabtc and slushpool i am getting more rejected than accepted shares. Cgminer reports "(Too low difficulty)" when I do not have a difficulty setting in place.
CGMiner is showing Diff:13.9T in all 6 terminal windows.
What should the difficulty be per Terminus R606?
I also have 11 NewPACs on 2 Gekko Hubs connected to the same machine giving the same difficulty message.
|
|
|
|
I have an ML2 that has quit working. I had 2 of these for some time running with an extra USB fan blowing on them in addition to their own fans as an extra measure of cooling. The fan on the unit still works when I swapped it to the other working ML2 and vice versa.
Is there any other testing that can be done to see if this is completely dead or still salvageable?
Not sure if this means anything but when I plug it into my USB power monitor the screen blinks rapidly.
you should be able to see it as a COM device under device manager, if it does not show up there then either windows blocked the silicon labs driver and/or you need to reinstall it. If it still does not show then yea it could be dead. No reason something is wrong with it if you haven't overclocked it like crazy or overheated...they should last a pretty long time. You can also try a different system in case its system related. Not showing up under com devices, no lights come on when I first plug it into either my Linux or windows machines Been running them at clock speed 756 and getting 4.4mhs average. never had an issue until last night when I noticed my hash rate was about half and saw that one unit was not blinking. |
|
|
|
|
I have an ML2 that has quit working. I had 2 of these for some time running with an extra USB fan blowing on them in addition to their own fans as an extra measure of cooling. The fan on the unit still works when I swapped it to the other working ML2 and vice versa.
Is there any other testing that can be done to see if this is completely dead or still salvageable?
Not sure if this means anything but when I plug it into my USB power monitor the screen blinks rapidly.
|
|
|
|
Thank you Kano, greatly appreciate the help. By (directly) you mean to run the first script from inside cgminer directory? While also having the second script looking like this: #!/bin/sh
./cgminer -o stratum+tcp://btc.viabtc.com:3333 -u Xylander.gekko1 -p x --suggest-diff 560 --gekko-newpac-detect --gekko-newpac-freq 425
pause
|
|
|
|
while [ 1 ]; do
./cgminer -o ....
sleep 5
done
If cgminer stops for any reason, this will wait 5 seconds and then restart the script. Just basically puts it into a loop. Since the last 2 updates I haven't really noticed it restarting, at least not like it was before the May updates. But at least this will kick them back off instead of remaining offline until you physically get back on the system to restart the script. I tried the following but it keeps loading new instances every 5 seconds. Is there something i'm missing here? while [ 1 ]; do
gnome-terminal -e "/home/cgminer/cgminer -o stratum+tcp://btc.viabtc.com:3333 -u Xylander.gekko1 -p x --suggest-diff 560 --gekko-newpac-detect --gekko-newpac-freq 425"
sleep 5
done
|
|
|
|
The blinkly lights has nothing to do with power or communication. It's an issue with the temp sensor, which is connected to the onboard microcontroller, which is not affected by voltage or USB anything.
Just to be double-clear, the white light is flashing while hashing on all of them, but on two of them the red volt-setting LEDs are blinking?
Without ASICBoost, the theoretical peak speed is about 575MHz (~800GH) on a wide-open USB bus. If the bus is shared out with something else and/or the processor is slow and timings aren't perfect, it'll be less than that. See the guy above whose pod, without AB, only saw about 500MHz. This is a USB limitation completely independent of core voltage setting. You may need to get a system working with AB, or plug into a more powerful controller, to get stock speed.
Thank you, will be moving to Kano pool, changing power supplies and will change the controller to a pi perhaps. |
|
|
|
|
Added the --gekko-noboost setting for btc.viabtc.com and it seems to be working. no crashes so far after 20 minutes.
I set the target freq of the R606 as 600. It has run over an hour and changed the target to 368 and then 15 minutes later changed again down to 362 which result in about 460gh. I have the R606 set to 450mv (setting 6) should I move it up to 7 or down to another setting to reach stock 750gh.
|
|
|
|
|
How would I go about saving a log of the cgminer instance so I can see why it keep crashing at varies stages?
|
|
|
|
Thank you VH, on top of it as always I see. I take it from what I have read so far that I will no longer need to run the 4 hours restart with this new build. Nicely done VH, Tried running it with this: /cgminer -o stratum+tcp://bch.viabtc.com:3333 -u Xylander.gekko1 -p x --suggest-diff 1280 --gekko-newpac-detect --gekko-newpac-freq 500 And after 15-20 seconds it would crash with this error: 0: GSH 10031523: BM1387:02+ 200.00MHz T:500 P:139 (24/171/94) | 72.9% WU:^7
1: GSH 10030254: BM1387:02+ 200.00MHz T:500 P:155 (24/171/94) | 80.8% WU:^7
2: GSH 10031531: BM1387:02+ 206.25MHz T:500 P:190 (23/169/91) | 93.2% WU:^9
3: GSH 10030194: BM1387:02+ 206.25MHz T:500 P:186 (23/170/91) | 92.8% WU:^9
4: GSH 10031522: BM1387:02+ 200.00MHz T:500 P:56 (24/171/94) | 6.4% WU:^
5: GSH 10031521: BM1387:02+ 200.00MHz T:500 P:170 (24/171/94) | 86.3% WU:^8
6: GSH 10030160: BM1387:02+ 200.00MHz T:500 P:151 (24/172/94) | 76.7% WU:^7
7: GSH 10030253: BM1387:02+ 200.00MHz T:500 P:149 (24/171/94) | 75.7% WU:^7
8: GSH 10030032: BM1387:02+ 200.00MHz T:500 P:53 (24/172/94) | 6.5% WU:^
9: GSH 10030237: BM1387:02+ 200.00MHz T:500 P:82 (24/171/94) | 10.0% WU:^1
10: GSH 10030030: BM1387:02+ 200.00MHz T:500 P:161 (24/171/94) | 83.6% WU:^8
11: GSH 10030174: BM1387:02+ 200.00MHz T:500 P:42 (24/171/94) | 4.8% WU:^
5% | 2.207G / 2.145Gh/s WU: 30.0/m----------------------------------------------
[2019-05-02 23:20:12.454] Accepted 0b959214 Diff 5.66K/4096 GSH 6
[2019-05-02 23:20:21.071] Accepted 16089615 Diff 2.97K/1280 GSH 10*** buffer overflow detected*** buffer overflow detected ***: ./cgminer ***: ./cgminer terminated
terminated
*** buffer overflow detected ***: ./cgminer terminated
Aborted (core dumped)
|
|
|
|
I am still running the December version on my Ubuntu 18.04 LTS machine. I am however trying the newer build posted 4/8/19 but i am having an issue that may be the 18.04 version or something else i'm doing wrong. Following VH's post on page 21: #rename the existing cgminer folder then...
git clone -b r606 https://github.com/vthoang/cgminer.git
cd cgminer
CFLAGS="-O2" ./autogen.sh --enable-gekko
make -j 2 I am getting the following error at the end of "make -j 2" line. driver-gekko.c: In function ‘compac_statline’:
driver-gekko.c:1724:68: warning: format ‘%d’ expects argument of type ‘int’, but argument 8 has type ‘double’ [-Wformat=]
sprintf(asic_statline, "BM1387:%02d%-1s %.2fMHz T:%.0f P:%.0f (%d/%d/%d/%.0fF)", info->chips, ab, info->frequency, info->frequency_requested, info->frequency_computed, info->scanhash_ms, info->task_ms, info->fullscan_ms, info->micro_temp);
~^ ~~~~~~~~~~~~~~~~~
%f
driver-gekko.c:1724:71: warning: format ‘%d’ expects argument of type ‘int’, but argument 9 has type ‘double’ [-Wformat=]
sprintf(asic_statline, "BM1387:%02d%-1s %.2fMHz T:%.0f P:%.0f (%d/%d/%d/%.0fF)", info->chips, ab, info->frequency, info->frequency_requested, info->frequency_computed, info->scanhash_ms, info->task_ms, info->fullscan_ms, info->micro_temp);
~^ ~~~~~~~~~~~~~
%f
driver-gekko.c:1724:74: warning: format ‘%d’ expects argument of type ‘int’, but argument 10 has type ‘double’ [-Wformat=]
sprintf(asic_statline, "BM1387:%02d%-1s %.2fMHz T:%.0f P:%.0f (%d/%d/%d/%.0fF)", info->chips, ab, info->frequency, info->frequency_requested, info->frequency_computed, info->scanhash_ms, info->task_ms, info->fullscan_ms, info->micro_temp);
~^ ~~~~~~~~~~~~~~~~~
%f
CCLD cgminer
/usr/bin/ld: cannot find -lz
collect2: error: ld returned 1 exit status
Makefile:847: recipe for target 'cgminer' failed
make[2]: *** [cgminer] Error 1
make[2]: Leaving directory '/home/HX/git/vthoang/cgminer'
Makefile:1831: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/HX/git/vthoang/cgminer'
Makefile:751: recipe for target 'all' failed
make: *** [all] Error 2 I have even tried using the instruction on the first page and created a new directory for cgminer. |
|
|
|
What would be the best way to adjust the Algorithms section for equihash and Decred when you add DR5s & Z11s.
I already have it set for myDR3s & z9 minis.
Can you please describe this request/question in a bit more detail? I understand that you are about to add your new Antminers, but what are the configuration or operation you want to do here? the current custom setting in the algorithm section for my Z9 minis is 10k/s @ 268w. When I added my Z11s they were showing 135k/s @ 4000w on the Main->Miners tab. Thanks for the update. These two miners have quite a different efficiency you noticed. For this reason, the linear power usage scaling in the Profit Profile will not make good predictions. Please go to the Options dialog, Profit Profile section and add a new profile for the Z11 miners. In this profile, you can enter a typical hashrate and power usage for the Z11, in the same way, to did in your previous profile for the Z9 miner. Finally, you can open the Properties of your External Miners representing the Z11 miners and select the new profit profile you created. Thank you very much for the detailed explanation. |
|
|
|
What would be the best way to adjust the Algorithms section for equihash and Decred when you add DR5s & Z11s.
I already have it set for myDR3s & z9 minis.
Can you please describe this request/question in a bit more detail? I understand that you are about to add your new Antminers, but what are the configuration or operation you want to do here? the current custom setting in the algorithm section for my Z9 minis is 10k/s @ 268w. When I added my Z11s they were showing 135k/s @ 4000w on the Main->Miners tab. |
|
|
|
|
What would be the best way to adjust the Algorithms section for equihash and Decred when you add DR5s & Z11s.
I already have it set for myDR3s & z9 minis.
|
|
|
|
https://releases.broked.net/Z11StockSSHNoSignature.zipThis is the stock Z11 firmware dated Tue Mar 12 19:47:06 CST 2019 + SSH has been enabled + Signature checking has been removed for future firmware updates + Protection against the known antminer malware has been added + No Dev-Fee/Call-Home + No additional features or changes exist. This can be used to enable AwesomeMiner to manage your Z11 ASIC. Hopefully, now you can find that extra 40k/sols. |
|
|
|
|
