I remember with the older Avalons you you could adjust voltage/frequency/fan speed. Not sure if its possible with this input, don't remember the commands. Now that the More Options entry box is back we just have to wait for someone to find what the command formats for it are. The A7, 8, & 9's all have their quirks in the the commands used... |
|
|
|
As an example for setting minimum speed of 10% and max of 30%, under More Options use --avalon8-fan 10-30 Full list of A8 commands: USE_AVALON8
OPT_WITH_CBARG("--avalon8-voltage-level",
set_avalon8_voltage_level, NULL, &opt_set_avalon8_voltage_level,
"Set Avalon8 default level of core voltage, range:[0, 15], step: 1"),
OPT_WITH_CBARG("--avalon8-voltage-level-offset",
set_avalon8_voltage_level_offset, NULL, &opt_set_avalon8_voltage_level_offset,
"Set Avalon8 default offset of core voltage level, range:[-2, 1], step: 1"),
OPT_WITH_CBARG("--avalon8-freq",
set_avalon8_freq, NULL, &opt_set_avalon8_freq,
"Set Avalon8 default frequency, range:[25, 1200], step: 25, example: 800"),
OPT_WITH_ARG("--avalon8-freq-sel",
set_int_0_to_7, opt_show_intval, &opt_avalon8_freq_sel,
"Set Avalon8 default frequency select, range:[0, 7], step: 1, example: 7"),
OPT_WITH_CBARG("--avalon8-fan",
set_avalon8_fan, NULL, &opt_set_avalon8_fan,
"Set Avalon8 target fan speed, range:[0, 100], step: 1, example: 0-100"),
OPT_WITH_ARG("--avalon8-temp",
set_int_0_to_100, opt_show_intval, &opt_avalon8_temp_target,
"Set Avalon8 target temperature, range:[0, 100]"),
OPT_WITH_ARG("--avalon8-polling-delay",
set_int_1_to_65535, opt_show_intval, &opt_avalon8_polling_delay,
"Set Avalon8 polling delay value (ms)"),
OPT_WITH_ARG("--avalon8-aucspeed",
opt_set_intval, opt_show_intval, &opt_avalon8_aucspeed,
"Set AUC3 IIC bus speed"),
OPT_WITH_ARG("--avalon8-aucxdelay",
opt_set_intval, opt_show_intval, &opt_avalon8_aucxdelay,
"Set AUC3 IIC xfer read delay, 4800 ~= 1ms"),
OPT_WITH_ARG("--avalon8-smart-speed",
opt_set_intval, opt_show_intval, &opt_avalon8_smart_speed,
"Set Avalon8 smart speed, range 0-1. 0 means Disable"),
OPT_WITH_ARG("--avalon8-th-pass",
set_int_0_to_65535, opt_show_intval, &opt_avalon8_th_pass,
"Set A3210 th pass value"),
OPT_WITH_ARG("--avalon8-th-fail",
set_int_0_to_65535, opt_show_intval, &opt_avalon8_th_fail,
"Set A3210 th fail value"),
OPT_WITH_ARG("--avalon8-th-init",
set_int_0_to_65535, opt_show_intval, &opt_avalon8_th_init,
"Set A3210 th init value"),
OPT_WITH_ARG("--avalon8-th-ms",
set_int_0_to_32767, opt_show_intval, &opt_avalon8_th_ms,
"Set A3210 th ms value"),
OPT_WITH_ARG("--avalon8-th-timeout",
opt_set_uintval, opt_show_uintval, &opt_avalon8_th_timeout,
"Set A3210 th timeout value"),
OPT_WITH_ARG("--avalon8-th-add",
set_int_0_to_1, opt_show_intval, &opt_avalon8_th_add,
"Set A3210 th add value"),
OPT_WITH_ARG("--avalon8-th-mssel",
set_int_0_to_1, opt_show_intval, &opt_avalon8_th_mssel,
"Set A3210 th mssel value"),
OPT_WITH_ARG("--avalon8-lv2-th-add",
set_int_0_to_1, opt_show_intval, &opt_avalon8_lv2_th_add,
"Set A3210 lv2 th add value"),
OPT_WITH_ARG("--avalon8-lv2-th-ms",
set_int_0_to_32767, opt_show_intval, &opt_avalon8_lv2_th_ms,
"Set A3210 lv2 th ms value"),
OPT_WITH_ARG("--avalon8-lv3-th-add",
set_int_0_to_1, opt_show_intval, &opt_avalon8_lv3_th_add,
"Set A3210 lv3 th add value"),
OPT_WITH_ARG("--avalon8-lv3-th-ms",
set_int_0_to_32767, opt_show_intval, &opt_avalon8_lv3_th_ms,
"Set A3210 lv3 th ms value"),
OPT_WITH_ARG("--avalon8-lv4-th-add",
set_int_0_to_1, opt_show_intval, &opt_avalon8_lv4_th_add,
"Set A3210 lv4 th add value"),
OPT_WITH_ARG("--avalon8-lv4-th-ms",
set_int_0_to_32767, opt_show_intval, &opt_avalon8_lv4_th_ms,
"Set A3210 lv4 th ms value"),
OPT_WITH_ARG("--avalon8-lv5-th-add",
set_int_0_to_1, opt_show_intval, &opt_avalon8_lv5_th_add,
"Set A3210 lv5 th add value"),
OPT_WITH_ARG("--avalon8-lv5-th-ms",
set_int_0_to_32767, opt_show_intval, &opt_avalon8_lv5_th_ms,
"Set A3210 lv5 th ms value"),
OPT_WITH_ARG("--avalon8-lv6-th-add",
set_int_0_to_1, opt_show_intval, &opt_avalon8_lv6_th_add,
"Set A3210 lv6 th add value"),
OPT_WITH_ARG("--avalon8-lv6-th-ms",
set_int_0_to_32767, opt_show_intval, &opt_avalon8_lv6_th_ms,
"Set A3210 lv6 th ms value"),
OPT_WITH_ARG("--avalon8-lv7-th-add",
set_int_0_to_1, opt_show_intval, &opt_avalon8_lv7_th_add,
"Set A3210 lv7 th add value"),
OPT_WITH_ARG("--avalon8-lv7-th-ms",
set_int_0_to_32767, opt_show_intval, &opt_avalon8_lv7_th_ms,
"Set A3210 lv7 th ms value"),
OPT_WITHOUT_ARG("--avalon8-iic-detect",
opt_set_bool, &opt_avalon8_iic_detect,
"Enable Avalon8 detect through iic controller"),
OPT_WITH_ARG("--avalon8-nonce-mask",
set_int_24_to_32, opt_show_intval, &opt_avalon8_nonce_mask,
"Set A3210 nonce mask, range 24-32."),
OPT_WITH_ARG("--avalon8-nonce-check",
set_int_0_to_1, opt_show_intval, &opt_avalon8_nonce_check,
"Set A3210 nonce check, range 0-1."),
OPT_WITH_ARG("--avalon8-roll-enable",
set_int_0_to_1, opt_show_intval, &opt_avalon8_roll_enable,
"Set A3210 roll enable, range 0-1."),
OPT_WITH_ARG("--avalon8-mux-l2h",
set_int_0_to_2, opt_show_intval, &opt_avalon8_mux_l2h,
"Set Avalon8 mux l2h, range 0-2."),
OPT_WITH_ARG("--avalon8-mux-h2l",
set_int_0_to_1, opt_show_intval, &opt_avalon8_mux_h2l,
"Set Avalon8 mux h2l, range 0-1."),
OPT_WITH_ARG("--avalon8-h2ltime0-spd",
set_int_0_to_255, opt_show_intval, &opt_avalon8_h2ltime0_spd,
"Set Avalon8 h2ltime0 spd, range 0-255."),
OPT_WITH_ARG("--avalon8-spdlow",
set_int_0_to_7, opt_show_intval, &opt_avalon8_spdlow,
"Set Avalon8 spdlow, range 0-7."),
OPT_WITH_ARG("--avalon8-spdhigh",
set_int_0_to_7, opt_show_intval, &opt_avalon8_spdhigh,
"Set Avalon8 spdhigh, range 0-7."), |
|
|
|
I just checked BTC.com stats and it reads that this pool only found one block last month, and one other block in February. That's all the blocks that have been found this year. To be fair that was when the difficulty was at its highest so I'm impressed that you guys managed to find some blocks during that time. Given that the halving will happen next month, if that drives up the difficulty (perhaps mining hardware will become cheaper?) it's really going to hurt solo pools' chances of finding a block.
But anyway hope you find another block before the halving.
You are confusing how a solo pool operates with how 'normal' pools work. With a solo pool the total hash rate pointed at it and how many blocks are being found is pretty much meaningless because only the miner that finds a block is paid (+ the pool operator through their fee). All a solo pool does is provide an easy way to mine on your own exclusively for your benefit. The chances of you finding a block all depends on what your individual hash rate is. A 'normal' pool is different in that the total hash rate very much matters because all it takes is one miner finding a block for everyone to get paid though of course the reward will be split among everyone in the pool. The bigger the pool (more hash) the better the odds are that *someone* in it will find a block. |
|
|
|
re: Antminer name, no problem. It is very common for various posts, articles, and videos to mistakenly do the same thing because the authors just don't care about being correct. In my book that raises questions about what else they may get wrong  The other even more common error is calling every crypto coin "Bitcoin". Only BTC is Bitcoin. All others are generally called altcoins and in this part of the Forum, crapcoins... Those are good prices you were quoted, just be sure that it is a reputable dealer you are working with. Personally I don't have any of the M21 series but I do talk with several miners in the pool I use who do have them - overall they are quite happy with them. Given that both MicroBT (Whatsminers) and Canaan have very good products to me it would boil down to what happens if something breaks: Generally the Whatsminer's need to be sent to China for repairs. Canaan's Avalon miners on the other hand are modular with components that are easily replaceable by the user. After sales support from Canaan is excellent meaning once you work with them to diagnose a problem they will quickly send you the replacement part for you to install. |
|
|
|
1st of all, "antminer" refers ONLY to Bitmain's trademark name for their miners. It is not a generic term for all miners. By far the most reliable miners are the Avalon's from Canaan and worst are Bitmain's Antminers. I have had several dozen Avalon's running since 2016 with ZERO hard failures. The only faults were a dead fan on 2 of my oldest 721's. The Whatsminers from microbt are #2. I have 5 of their M10's and all are solid as a rock. Some issues have been reported here but still very few failures. Contrast that to an over 15% failure rate from dead hash boards and dead control boards on the 25 Bitmain s9's I had. Folks in the forum are saying that BM's newer S17 series are even worse... For one example, ref this post about BM's S17'sFrom my perspective, you are correct. Bitmain's overall 7nm units are far from robust or reliable. I have had the best luck with Pro's but they still exhibit a 15% attrition rate on my racks. 15 out of 100 have lost boards, burnt PSU's. Out of 200 S17's we are experiencing 20-25% attrition with many lost boards and plenty of burnt PSU's. |
|
|
|
... Yes reliable, but Canaan's miners are always the first to brick.
Er? 'Reliable' and '1st to brick' are completely opposite unless you are talking about taking them offline due to eff reasons. If that's the case, ja I have a nice pile of 721/741/821's and a few 841's accumulating that are now offline because of their lack of efficiency. But, I'm still running dozens of Avalon miners - 10 remaining 841's (half in low power space heater mode), a couple 921's and the rest A10xx. Aside from losing a fan on 2 of the oldest 721's I've had zero problems with them. I prefer that to the even bigger pile of DEAD s9/T9's I have... |
|
|
|
...
Also, both editions use BOSminer rather than cgminer, which allows Stratum V2 for secure connections to any pool that supports it.
If you decide to use Braiins OS+ with Slushpool, the pool fee is half, so instead of a 2% pool fee you now pay a 1% pool fee.
Since Slushpool looks for BOSminer ID flags then that will certainly make it very easy for Slush to know if their software works as-advertised and finds blocks. When a miner finds a block Slush and the BOS devs will know what it is running. Does this mean that they might finally answer this simple but seemingly intractable question: "Does it find blocks at same rate as 'official' OEM firmware" by providing direct proof that it does? |
|
|
|
|
That is for mining altcoins and does not belong in the BTC areas. Requested that the mods move it to where it belongs.
|
|
|
|
Have you bothered to download the manual for it from Bitmain? Far better than any 'tube vids... Aside from that, be sure that there are no whitespaces in your address or username. When copy/pasting it is very common for a whitespace to be added to the end of what you pasted. As for user and worker name, normally they have to be separated by a dot eg username.workername |
|
|
|
Perhaps folks should simply do a search on what 5G is and how 5G works before leaping onto the Wild Theory & Conspiracies bandwagon...... Hint: 5G sites do not do any pre-processing/sniffing or filtering of data packets. |
|
|
|
I still don't believe that we are going to see bitcoin halved
It is not a matter of believing -- the halving is hard coded into the BTC algorithm and WILL occur every 210,000 blocks or roughly every 4 years. At the current global hash rate the next halving will occur sometime in May this year. While I am usually not a fan of Coindesk, they have a decent explanation of it here. |
|
|
|
2) Is this PPS or PPLNS? It is labeled as score based pplns, but even after disconnecting from the pool for near 24 hours, come back and still have tons of shares. Or is all the math figured out when a block is found? It would seem that if people can disconnect for 24+ hours and still have active shares, it would drastically reduce the payout for active miners. Especially since the rounds are so long. It is neither. Perhaps reading the 1st post where how the pool operates is described would help?  |
|
|
|
|
You have read the various about Antminers and esp. one regarding the S17 to know that all Antminers go through an autotune process when they are powered up right?.... It can take anywhere from several min to around a 1/2hr for them to figure out optimum voltage & speeds before they start hashing on your pools.
|
|
|
|
|
The only possible damage would have been to the PSU with blown input rectifiers or soft-start thermistor. Frankly I am surprised the PO was able to run it at all (did they say it ran?) as the PSU should have shut down/not started at that low voltage. I'd plug it into 240VAC and see if it runs.
|
|
|
|
|
AFAIK no miner is double insulated. Frankly, just make sure you have a solid connection to the power distribution PE ground and that your neutral is solidly bonded to it. Do that and you are good using a normal class-C or D thermal/magnetic breaker.
|
|
|
|
The OP has 99 meirt, please someone send 1 from me I love to rank up people and he deserves it Smiley
Merit given to OP so they are now at 100  |
|
|
|
It is a bad miner all around. 6 months old, when the weather is hot and it starts heating up in the data center it keeps going down, waiting for a reset over and over again. Interesting, what model did you get? Did you even talk to your distributor or Canaan about it? I and many others have the exact opposite results. I *used* to run BM gear and up to the s4 they were great, come s5 on up lots of issues culminating with all 4 T9's and 15 S9's I had each losing multiple boards. Initially repair service from Bitmain and then through Denver-based BitmainWarrenty was decent but quickly went to hell in a hand basket. Switched to Avalons starting with the A721 and have not looked back. Currently running just over 500TH of Avalons ranging from A841's to the A1047's and aside from losing 2 fans on my oldest and now retired 721's ZERO problems. You will find that the few folks here who did report problems were taken care of quickly and in a professional manner either by the distributor or Canaan directly. The miners are modular and easy to troubleshoot, find the problem and Canaan will get replacement parts right out to you. |
|
|
|
|
I'll take 34 if still open
Thanks for the heads up Phil,
Cheers!
|
|
|
|
As Stryfe said - we have asked for proof in the other FW threads as well. No responses at all or deleted. I will say that it is heartening to at least have a response from you even if it is rather negative... The folks behind Braiins certainly do deserve Kudos for it being Open Source complete with the availability of all source code as required per the cgminer license. You are the only aftermarket firmware group do do that Regarding Can you do that with OEM? No, because none of them releases the code like bOS does.
Mostly right but not entirely accurate. Up to Canaan's A10 series their code is freely published in Github repository. From A10 on up - not sure since they have completely revamped their firmware & software but odds are it *is* available. Then again, since Canaan (up to the A10x) has the cgminer More Options field in their GUI it (was) simplicity in itself to tweak their miners to your hearts content which negated any need for aftermarket firmware... Never said that Braiins is only used on Slush (and yes it is banned on Kano), was just saying that with Braiins being part of the Slush family, it should be easy for you folks to check how it performs. My point was that Slush (and other pools) can easily log what FW is in the miners. As they are the ones behind Braiins they should have a vested interested in how it performs and are in the best position to verify it has no problems. I know that Kano periodically checks what FW miners are using because Kanopool (and all other small pools) does not have the hash rate to risk *any* chance of missing a block due to a bug. If the other small pools don't care - well, that's entirely up to them and is just another reason I don't mine elsewhere. For pool operators, when a miner finds a BTC block, query the logs to see if it runs Braiins, if it does - let folks know about it. On the actual miner side - especially large farms - the cgminer API has a block found function: Setup your monitoring software to flag it. If a non-oem miner finds a block - and any large farms should find several in a very short period of time - lets folks know! I would think that large farms should not only be checking their hash rate vs income but also be very interested in the "how many blocks did WE find and which miner did it" metrics. Oh, and yes, the chance of any one single piece of hardware finding a block has always been slim and barring a drop in diff will just keep getting harder. But since 2014 I've found 15 blocks and over the course of 125 miners ranging from S1-S9, an uber rare AMT A1 miner circa 2014, several Avalons from 721-841, and Whatsminer M10's at least 1 from each family has found a block. I have an R4 that has found 2. The only miners I have that have not yet found a block are 2x A941, and 5x A10's. I currently run 25 miners and found Kano's last block with an A841 cluster of 5. Point is that given a large sample of miners running and provided they bother to check, a person/company *will* find blocks with their hardware giving them (and us if they share) data as to what works and what does not work. Again, I have no animosity towards the Braiins devs and do respect you for fulfilling the cgminer license. But as an example, in the Genesis mining kerfuffle obviously shares from them were accepted by Slushpool as normal and yet there was a precipitous and lengthy drop in the farms find rate due to a bug in the proxy software that Genesis was testing. As in despite running over 300PH Genesis suddenly went from several blocks per day to zero for over a month and until other folks started bitching about the pools Luck and their income dropping apparently no one noticed something was wrong somewhere... I and others would just like to see proof that nothing was inadvertently broken. |
|
|
|
maybe it was posted somewhere here? if so, I apologize. but can anyone show proof of anyone using this FW that has found a block?
So far I have not seen hide nor hair of any proof that Braiins - or any other non-OEM firmware -finds BTC blocks. Considering that it is Slush who is behind the FW and no doubt there are a lot of Braiins users on Slush one would think that it would be very very easy for them to post proof it finds BTC blocks... But so far <sound of crickets> |
|
|
|
|
Show Posts
