See the new thread for details 
Topic: OLD: BFGMiner 4.10.0: GBT+Stratum, RPC, Mac/Linux/Win64, Spondoolies SP30 (Read 308659 times)
November 28, 2014, 10:27:19 PM
November 28, 2014, 08:33:24 PM
Is there a way to get the new Antminer U3 to work with BFGminer?
Unfortunately, Bitmain has not been providing samples to work with since the S1 (which they also didn't follow up on).The best route is for more customers to contact them asking for BFGMiner support, so they are aware of the need for quality software support.
In the meantime, perhaps the U3 is cheap enough that someone might be interested in donating one?
November 28, 2014, 07:52:41 PM
Is there a way to get the new Antminer U3 to work with BFGminer?
November 27, 2014, 02:34:30 PM
The speed on zeusminers needs to be alot lower ,the ones i own at between 220 and 248, at 328 they not even start
They instant crash at 300+
They instant crash at 300+
Then you would own zuesminers Thunder X6. I have 9 of them. Ive been trying like hell to get these working on latest bfgminer. Olatest bfgminer will not detect mine. Can you please post you .bat file? Is there anything special you needed to do so bfgminer can see them? Did you recomiple the source and add zeus support?
Thanks in advance
Vegas
Would love it if someone could verify this is the case. Is the initial clock speed too high for newer devices?
I was only able to test up to the 256-chip devices some months ago.
I have both Zeus miner X6 and Zeus miner X3. Multiminer DOES work with Zeusminer X3 as its native speed is 328mhz, however even the latest Multiminer binary (released 4 days ago) does not work with thunder X6. Both the zeusminer thunder X3 and X6 are pretty much identical. They both have 128 chips, they even use the same FTDI driver, the only difference is clock speed. Thunder X3: 328mhz, Thunder X6: 248mhz. I quoted factory clock speeds. Yes, my thunder X6 do crash running latest multiminer, zeus thunder X3 works fine. CONFIRMED!
Have you tried specifying the clock speed with the BFGMiner arguments?
Code:
--set zus:clock=248
You can specify that in MultiMiner in the settings here.
Edit: more info from README.ASIC (thanks to a recent contribution):
Quote
Zeusminers do not support autodetection, so you will need to use --scan to probe
for them:
-S zeusminer:\\.\COM3
You should also configure the driver for your specific device:
--set zeusminer:clock=N Clock frequency (default: 328)
--set zeusminer:chips=N Number of chips per device
Blizzard : 6 Cyclone : 96
Hurricane X2: 48 (2*24) Hurricane X3: 64 (2*32)
Thunder X2: 96 (4*24) Thunder X3: 128 (4*32)
Note: if you set this option incorrectly, the device may underperform and/or
misreport hashrate.
For example:
bfgminer --scrypt -o stratum+tcp://pool:port -u user -p pass -S zeusminer:\\.\COM3 --set zeusminer:clock=328 --set zeusminer:chips=128
for them:
-S zeusminer:\\.\COM3
You should also configure the driver for your specific device:
--set zeusminer:clock=N Clock frequency (default: 328)
--set zeusminer:chips=N Number of chips per device
Blizzard : 6 Cyclone : 96
Hurricane X2: 48 (2*24) Hurricane X3: 64 (2*32)
Thunder X2: 96 (4*24) Thunder X3: 128 (4*32)
Note: if you set this option incorrectly, the device may underperform and/or
misreport hashrate.
For example:
bfgminer --scrypt -o stratum+tcp://pool:port -u user -p pass -S zeusminer:\\.\COM3 --set zeusminer:clock=328 --set zeusminer:chips=128
November 27, 2014, 01:52:50 PM
The speed on zeusminers needs to be alot lower ,the ones i own at between 220 and 248, at 328 they not even start
They instant crash at 300+
They instant crash at 300+
Then you would own zuesminers Thunder X6. I have 9 of them. Ive been trying like hell to get these working on latest bfgminer. Olatest bfgminer will not detect mine. Can you please post you .bat file? Is there anything special you needed to do so bfgminer can see them? Did you recomiple the source and add zeus support?
Thanks in advance
Vegas
Would love it if someone could verify this is the case. Is the initial clock speed too high for newer devices?
I was only able to test up to the 256-chip devices some months ago.
I have both Zeus miner X6 and Zeus miner X3. Multiminer DOES work with Zeusminer X3 as its native speed is 328mhz, however even the latest Multiminer binary (released 4 days ago) does not work with thunder X6. Both the zeusminer thunder X3 and X6 are pretty much identical. They both have 128 chips, they even use the same FTDI driver, the only difference is clock speed. Thunder X3: 328mhz, Thunder X6: 248mhz. I quoted factory clock speeds. Yes, my thunder X6 do crash running latest multiminer, zeus thunder X3 works fine. CONFIRMED!
November 27, 2014, 01:49:11 PM
Zues miner thunder X3 (1st revision) run factory clock @ 328mhz. Speed is 30 Mhs. Zues a few months later created the zeusminer thunder X6 that runs at a clock speed of 248mhz and 20MHs and 1/2 the power draw. Luke what would you charge to include support for zeus miners thunder both X6 and X3 for latest version and all future versions? I will pay as I really want this working. The last mining software that ANYONE developed for zeus was in July 2014, yet there are millions of owners. I can also beta test as I own both the X3 and X6, but I am unable to compile (dont know how), so youll have to compile a binary for each test for windows if you choose to take this on. Also I want to run www.awesomeminer.com and I cant run that as its a front end for bfgminer. Awesome miner, automatically downloads the latest bfgminer automatically, and that does not have zues support built in. HELP US LUKE ! 
Vegas
Vegas
November 27, 2014, 12:48:44 PM
The speed on zeusminers needs to be alot lower ,the ones i own at between 220 and 248, at 328 they not even start
They instant crash at 300+
They instant crash at 300+
Then you would own zuesminers Thunder X6. I have 9 of them. Ive been trying like hell to get these working on latest bfgminer. Olatest bfgminer will not detect mine. Can you please post you .bat file? Is there anything special you needed to do so bfgminer can see them? Did you recomiple the source and add zeus support?
Thanks in advance
Vegas
Would love it if someone could verify this is the case. Is the initial clock speed too high for newer devices?
I was only able to test up to the 256-chip devices some months ago.
November 27, 2014, 12:18:27 PM
The speed on zeusminers needs to be alot lower ,the ones i own at between 220 and 248, at 328 they not even start
They instant crash at 300+
They instant crash at 300+
Then you would own zuesminers Thunder X6. I have 9 of them. Ive been trying like hell to get these working on latest bfgminer. Olatest bfgminer will not detect mine. Can you please post you .bat file? Is there anything special you needed to do so bfgminer can see them? Did you recomiple the source and add zeus support?
Thanks in advance
Vegas
November 25, 2014, 09:55:27 AM
The speed on zeusminers needs to be alot lower ,the ones i own at between 220 and 248, at 328 they not even start
They instant crash at 300+
They instant crash at 300+
hero member
Activity: 560
Merit: 509
I prefer Zakir over Muhammed when mentioning me!
November 25, 2014, 07:31:45 AM
Hello! There is no problem with the miner, the BFG miner is showing correct hashrate but it is showing as dead and thus not giving any work. 
I asked about the restarting because I found these commands:
What all arguments can I use? Any arguments to restart the dead miner?
Running it now! Now too, 1 panel isn't accepting any shares(after resetting the miner).
Correct.
...
I tried Multiminer but it isn't mining for some reason. Lack of set-up maybe.
Thanks! But I like to mine in multipool. I currently mine in multipool.us. I think I want to switch to Ghash.io LTC+Doge .
~~MZ~~
I asked about the restarting because I found these commands:Code:
--cmd-idle Execute a command when a device is allowed to be
idle (rest or wait)
--cmd-sick Execute a command when a device is declared sick
--cmd-dead Execute a command when a device is declared dead
idle (rest or wait)
--cmd-sick
--cmd-dead
What all arguments can I use? Any arguments to restart the dead miner?
Please try 4.10, the latest version available here: https://bitcointalksearch.org/topic/m.6958518 (this thread). Additionally the previous poster indicated you need to unplug/replug the USB cable once the issue has occurred.
Running it now! Now too, 1 panel isn't accepting any shares(after resetting the miner).
MultiMiner has the option to restart miners it detects are behaving poorly, but that will not help if this issue requires re-seating the USB cable.
Correct.
...
I tried Multiminer but it isn't mining for some reason. Lack of set-up maybe.
One last note. If you are constantly switching coins, so you are restarting the gridseeds all the time, you WILL have them going to sleep a lot more often than if you just point them at something and leave them alone.
Thanks! But I like to mine in multipool. I currently mine in multipool.us. I think I want to switch to Ghash.io LTC+Doge .
~~MZ~~
November 24, 2014, 11:14:36 PM
Hello luke. This might not be a issue but it's strange to me. I have 2 zeus thunders running on bfgminer just fine, but there is something that puzzles me. If I set the --set zus:chips=128 your program then reports 1024 chips not 128. I have set it with --set zus:chips=16 and I get much better results in hash rates allways around 28 to 30 mhs. Bfgminer reports 128 chips. I also have gaw furys but it seems everything you set in Bfgminer is times 8.
I dunno if thats a flaw in bfgminer or thats how it's set up. It just seems to work better if you can set the true chips.
IIRC (but this is Nate's area), Zeus design has 8 cores per chip, and BFGMiner shows each core. I dunno if thats a flaw in bfgminer or thats how it's set up. It just seems to work better if you can set the true chips.
November 24, 2014, 11:05:10 PM
Hello luke. This might not be a issue but it's strange to me. I have 2 zeus thunders running on bfgminer just fine, but there is something that puzzles me. If I set the --set zus:chips=128 your program then reports 1024 chips not 128. I have set it with --set zus:chips=16 and I get much better results in hash rates allways around 28 to 30 mhs. Bfgminer reports 128 chips. I also have gaw furys but it seems everything you set in Bfgminer is times 8.
I dunno if thats a flaw in bfgminer or thats how it's set up. It just seems to work better if you can set the true chips.
I dunno if thats a flaw in bfgminer or thats how it's set up. It just seems to work better if you can set the true chips.
November 24, 2014, 04:27:40 PM
Try the most recent BFGMiner - that is version 3.10 in your screenshot.
Tried using 4.8.0 . GSD 0 still doesn't show any hash-rate.
Please try 4.10, the latest version available here: https://bitcointalksearch.org/topic/m.6958518 (this thread). Additionally the previous poster indicated you need to unplug/replug the USB cable once the issue has occurred.
Any possible way to restart miners that are shown as dead in BFG miner? Or any way to prevent killing a miner? And, why is it needed? Thanks!
Know any?~~MZ~~
MultiMiner has the option to restart miners it detects are behaving poorly, but that will not help if this issue requires re-seating the USB cable.
Correct.
And after months of use, the option to restart the poorly behaving miners several times, while trying to restart one that needs a USB reset, will usually get more of the gridseeds to go to sleep. (I have 3 g-blades so 6 blades) Best to plug them straight into the mobo if you have the available ports (USB2 works better than USB3) then start them up and turn the restart option off, and just check them once a day or so...
Sometimes they will go fine for weeks, other times you'll see them dropping after a few hours. When they do that, power EVERYTHING down. The mobo, the PSU feeding the gridseeds, the hub power, everything, then wait 10 seconds, then restart everything. Should run for weeks if you don't screw with anything.
One last note. If you are constantly switching coins, so you are restarting the gridseeds all the time, you WILL have them going to sleep a lot more often than if you just point them at something and leave them alone.
November 24, 2014, 03:52:20 PM
Ok.. that's what I thought. Got it qorking but.. It won't hash any higher then 48gh. Seems to jump all over the place. Any ideas on this?
November 24, 2014, 03:47:50 PM
Try the most recent BFGMiner - that is version 3.10 in your screenshot.
Tried using 4.8.0 . GSD 0 still doesn't show any hash-rate.
Please try 4.10, the latest version available here: https://bitcointalksearch.org/topic/m.6958518 (this thread). Additionally the previous poster indicated you need to unplug/replug the USB cable once the issue has occurred.
Any possible way to restart miners that are shown as dead in BFG miner? Or any way to prevent killing a miner? And, why is it needed? Thanks!
Know any?~~MZ~~
MultiMiner has the option to restart miners it detects are behaving poorly, but that will not help if this issue requires re-seating the USB cable.
hero member
Activity: 560
Merit: 509
I prefer Zakir over Muhammed when mentioning me!
November 24, 2014, 03:33:56 PM
What would be the command line to start BFGMiner 4.10 with the new Antiminer U3?
I think it isn't supported. See https://github.com/luke-jr/bfgminer/issues/580 .
You can use cgminer now:
Code:
cgminer.exe --bmsc-options 115200:0.65 -o pool:port -u user -p password --bmsc-voltage 0800 --bmsc-freq 1306
~~MZ~~
November 24, 2014, 03:29:20 PM
What would be the command line to start BFGMiner 4.10 with the new Antiminer U3?
November 24, 2014, 03:23:13 PM
Try the most recent BFGMiner - that is version 3.10 in your screenshot.
Tried using 4.8.0 . GSD 0 still doesn't show any hash-rate.
Any possible way to restart miners that are shown as dead in BFG miner? Or any way to prevent killing a miner? And, why is it needed? Thanks!
Know any?~~MZ~~
^^ Read my post above.. ^^
hero member
Activity: 560
Merit: 509
I prefer Zakir over Muhammed when mentioning me!
November 24, 2014, 03:16:33 PM
Try the most recent BFGMiner - that is version 3.10 in your screenshot.
Tried using 4.8.0 . GSD 0 still doesn't show any hash-rate.
Any possible way to restart miners that are shown as dead in BFG miner? Or any way to prevent killing a miner? And, why is it needed? Thanks!
Know any?~~MZ~~
November 24, 2014, 02:47:41 PM
Need help! 2 Gridseeds are connected, 2 panels each, so a total of 4 panels which have hash-rate of 2.56 MH/s per panel, so 5.2 MH/s per miner. Both miners are connected and 3 panels is accepting work request. Yesterday, all 4 were working. So anybody know why it isn't working now? Any possible way to check whether it is running but not accepting request or not?
~~MZ~~
~~MZ~~
Try the most recent BFGMiner - that is version 3.10 in your screenshot.
Jump to: