 Show Posts
|
|
Pages: « 1 2 3 [4] 5 »
|
did i miss the post that explains why miners aren't identified in v3 like they are in v2? for example NFY/ANY are now AMU.
Only AntMiner U1 naming was changed from ANT to AMU ( Ant Miner U1). This change has no affect on other devices. OIC... the last run i did of v3 earlier today my nfy did not appear. will check again. Thanks! |
|
|
|
|
did i miss the post that explains why miners aren't identified in v3 like they are in v2? for example NFY/ANY are now AMU.
|
|
|
|
Greetings. I too have an antminer that is throwing a high rate of errors and I'm having problems with downclocking a single antminer. When I run the device list, I see all of them listed as \\.\COM(NUM). of course this doesn't help when you have more than one as you don't know which is which. but i deduced it was COM54. when I run bfgminer with the --set-device for that path, it seems a random antminer will be downclocked. never seems to be the same one nor the problem antminer.
The U1 may support sending it an identify command so that its LED lights up. I'll have to look into it. On my side I was able to identify the com port by removing all except one. Then, run the command, so I know which it is. It seems Windows assign a port to a specific usb port. Thanks for the reply. As I mentioned, I was able to find out the COM number for the one that was causing all the errors and it was by doing the exact same thing. Unfortunately, when I ran the command specified to downclock the misbehaving antminer, one antminer would be downclocked and one would still be throwing errors. haven't had time to go through the entire process again to see if it's the exact same one or a different one throwing the errors. just an annoyance for me, and i don't fault the programmers for this, is that it seems the detection of the devices is random so for example, COM5 may be ANT0 when you run it one time, but another time COM5 may be ANT5. seems to be no rhyme or reason. |
|
|
|
Is it possible to overclock antminers separately with different oc? I have one antminer I would like to oc to 0881 and the other one to 0981?
One of my antminer has 14% HW and the other one 0% HW with 0981 oc.
Yes you can. First run bfgminer with -d? -S antminer:all to list the devices and their paths: bfgminer -d? -S antminer:all [2014-01-12 13:16:59] Started bfgminer 3.9.0
[2014-01-12 13:17:00] Devices detected:
[2014-01-12 13:17:00] Device (driver=antminer; procs=1; path=/dev/cu.SLAB_USBtoUART)
1 devices listed Then use the path displayed (above) in the --set-device argument: bfgminer -S antminer:all --set-device antminer@/dev/cu.SLAB_USBtoUART:clock=x0881 Greetings. I too have an antminer that is throwing a high rate of errors and I'm having problems with downclocking a single antminer. When I run the device list, I see all of them listed as \\.\COM(NUM). of course this doesn't help when you have more than one as you don't know which is which. but i deduced it was COM54. when I run bfgminer with the --set-device for that path, it seems a random antminer will be downclocked. never seems to be the same one nor the problem antminer. any suggestions? |
|
|
|
again, forgive my ignorance. but i want to set multiple device settings on the conf file but only one is getting loaded. "set-device":["NFY:osc6_bits=53"], "set-device":["antminer:freq=0981"] how exactly should this be configured in the conf file? thanks in advance. you all are great!  Try "set-device":["NFY:osc6_bits=53", "antminer:freq=0981"] ahh, got it. didn't know how they would be separated. once again, this thread rules. works like a charm! |
|
|
|
again, forgive my ignorance. but i want to set multiple device settings on the conf file but only one is getting loaded. "set-device":["NFY:osc6_bits=53"], "set-device":["antminer:freq=0981"] how exactly should this be configured in the conf file? thanks in advance. you all are great! |
|
|
|
forgive my ignorance about this.
using the new build with antminer and overclocking support, i'm seeing a very high rate of hardware errors related to my nanofury. what steps would i need to take to reduce them?
NFY 0: | 2.38/ 2.37/ 2.32Gh/s | A: 326 R:0+2(.78%) HW:287/4.0%
I wouldn't necessarily call HW of 4% "very high" especially for a Bitfury device. Usually Bitfury devices are fine with HW errors in the 10% or less range. ahh, ok. it was just higher than what i've seen before as i've been running it for a while. thank you! |
|
|
|
|
forgive my ignorance about this.
using the new build with antminer and overclocking support, i'm seeing a very high rate of hardware errors related to my nanofury. what steps would i need to take to reduce them?
NFY 0: | 2.38/ 2.37/ 2.32Gh/s | A: 326 R:0+2(.78%) HW:287/4.0%
|
|
|
|
On windows when bfgminer is started I get the message : NO DEVICES FOUND: Press 'M' and '+' to add My commandline: bfgminer.exe -S antminer:all -o stratum+tcp://stratum.bitcoin.cz:3333 -u stevenf.xxxxx -p xxxx --set-device antminer:freq=0881 I did install the CP210xVCP driver for windowsand I used the Zadig tool thingy, or is this not needed? The Zadig is not needed. just the VCP driver and you should be good to go. |
|
|
|
If anyone feels like testing out the latest AntMiner U1 code, it now supports both over-clocking and running side-by-side with Block Erupters. git clone -b feature\/antminer-u1-support https://github.com/nwoolls/bfgminer.git bfgminer-npw
cd bfgminer-npw
./autogen.sh
./configure
make Make sure you see a driver-antminer.c before compiling and a driver-antminer.o after. Probing is done similarly to the Block Erupter: bfgminer -S antminer:all -S erupter:all And you can overclock using --set-device: bfgminer --set-device antminer:freq=4F02 Windows binaries: https://www.dropbox.com/s/z29x4n6ng510joi/bfgminer-npw-antminer.7zTested on Windows, OS X, and Raspberry Pi (using MinePeon) It Works For Me™  amazing! trying it now. thank you! EDIT: all antminer, nanofury, and BE running on same instance. never thought i'd see the day. thank you! just have to wait and see if the BE get up to speed. this is great. |
|
|
|
Any chance of a Windows binary with ANT support? Screenshot is very nice and all, but I'm loathed to run cg (with all the zdiag and WinUSB bollocks fecking up the USB drivers) to get these things working.  If it breaks I didn't do it  Note that, like the Bitmaintech cgminer build, this won't play nice with Block Erupters for now (unless you manually specify the driver for each devices with -S antminer and -S erupter). oh damn! thanks. will give it a go! EDIT: seemed to have detected all the BE as ANT... thanks though. |
|
|
|
|
can't wait, oh wait, for ant u1 support. not to be too overbearing, might there be an ETA?
|
|
|
|
|
Offer 0.26btc shipped to California.
|
|
|
|
|
Offer 0.45btc shipped to California.
|
|
|
|
|
Offer 0.25btc for all of them.
|
|
|
|
|
Not sure if keys are region specific but it was sent to my NA account.
Asking 0.15btc.
|
|
|
|
|
Giving it a try! Thanks!
PRpwC43mE8AYcuJokVxU69TYfQULGEZYqR
|
|
|
|
|
