OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 65.

IYFTech

hero member

Activity: 686

Merit: 500

WANTED: Active dev to fix & re-write p2pool in C

Quote from: HellDiverUK on January 13, 2014, 12:08:25 PM

Quote from: IYFTech on January 13, 2014, 12:04:07 PM

Greetings,

I'm running a cube using the bfgminer proxy but the longpoll is showing as inactive & I'm only getting 67% efficiency as well as 34% rejects - can you tell me the command to enable longpolling as I can't find it in the readme......thanks anyone.

Peace. Grin

I had this discussion with Luke-Jr about a month ago. There is no Longpoll support, but he said he'd look in to adding it.

I found that running bfgminer on Linux helped a lot - I'm getting a solid 38GH out of my Cube connected to bfgminer on a Celeron 847 PC running Debian Wheezy.
When I point the Cube to the Pi running MinePeon and bfgminer, the Pi's CPU is running flat out and efficiency goes to crap. It runs OK on the BeagleBone Black running Debian, too (dual 1GHz ARMv7). The same Celeron machine running a stripped down Windows 7 install is also inefficient.

Well bugger me sideways, that's several hours wasted then, thanks HelldiverUK. I'm running Xubuntu 12.04 but was unable to get slush's proxy working with my cube & p2pool for some reason, it just wouldn't connect, but works fine on other pools - any pointers or ideas my man?

Peace.

HellDiverUK

hero member

Activity: 1246

Merit: 501

Quote from: IYFTech on January 13, 2014, 12:04:07 PM

Greetings,

I'm running a cube using the bfgminer proxy but the longpoll is showing as inactive & I'm only getting 67% efficiency as well as 34% rejects - can you tell me the command to enable longpolling as I can't find it in the readme......thanks anyone.

Peace. Grin

I had this discussion with Luke-Jr about a month ago. There is no Longpoll support, but he said he'd look in to adding it.

I found that running bfgminer on Linux helped a lot - I'm getting a solid 38GH out of my Cube connected to bfgminer on a Celeron 847 PC running Debian Wheezy.
When I point the Cube to the Pi running MinePeon and bfgminer, the Pi's CPU is running flat out and efficiency goes to crap. It runs OK on the BeagleBone Black running Debian, too (dual 1GHz ARMv7). The same Celeron machine running a stripped down Windows 7 install is also inefficient.

IYFTech

hero member

Activity: 686

Merit: 500

WANTED: Active dev to fix & re-write p2pool in C

Greetings,

I'm running a cube using the bfgminer proxy but the longpoll is showing as inactive & I'm only getting 67% efficiency as well as 34% rejects - can you tell me the command to enable longpolling as I can't find it in the readme......thanks anyone.

Peace. Grin

dbcmaster

newbie

Activity: 27

Merit: 0

Quote from: nwoolls on January 13, 2014, 08:46:22 AM

Quote from: dbcmaster on January 13, 2014, 08:45:24 AM

Running the new antminer version of bfgminer with the antminer overclocked and two usb block erupters. Look at the Hardware Error Rate:

They're all less than 1%. You are doing good.

Yup ... should have looked before I posted. I overlooked the "/" for some reason.

<<<< STUPID NOOB MOVES ALL DAY LONG

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: dbcmaster on January 13, 2014, 08:45:24 AM

Running the new antminer version of bfgminer with the antminer overclocked and two usb block erupters. Look at the Hardware Error Rate:

They're all less than 1%. You are doing good.

dbcmaster

newbie

Activity: 27

Merit: 0

Running the new antminer version of bfgminer with the antminer overclocked and two usb block erupters. Look at the Hardware Error Rate:

https://dl.dropboxusercontent.com/u/15558107/Pictures/bfgminer_antminer_HW.png

On bfgminer 3.9.0, I was only receiving errors on the antminer because it didn't realize what it was. The ASIC Block Erupters never really threw an error.

twib2

sr. member

Activity: 280

Merit: 250

Helperizer

Hi nwoolls,

I've got the newest version of your 3.9.0 build for the antminers, and I do all the steps for linux - autogen.sh, configure, make, and antminer shows up on the -h switch. However, even though my ants work with the bitmain cgminer 3.8.5, and with fractalbc's cgminer 3.9.0, I can't get your bfgminer to recognize them. bfgminer -d? -S antminer:all shows no devices, yet they're there just fine in lsusb, and of course for the two cgminers. I don't notice any errors during compilation, configure shows it as enabled for the antminer, and I'm using the correct binary - even called it by the full path just to be sure.

FWIW, this machine is Edubuntu 13.10, 64 bit version.

Any idea what could be going wrong?
Thanks,
- Tye

dbcmaster

newbie

Activity: 27

Merit: 0

So, if I download the bfgminer-npw-antminer from the link posted previously ... I just have to run that by itself for now correct?

In other words, I can't drop those files into the 3.9.0 directory.

cool77

newbie

Activity: 13

Merit: 0

Quote from: nwoolls on January 12, 2014, 01:17:24 PM

Quote from: cool77 on January 12, 2014, 12:51:07 PM

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:

Code:

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:

Code:

bfgminer -S antminer:all --set-device antminer@/dev/cu.SLAB_USBtoUART:clock=x0881

You know, you are really good and fast! Thank you very much, it works perfectly.

Cheers

Cool77

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: nwoolls on January 12, 2014, 02:11:42 PM

Quote from: Mudbankkeith on January 12, 2014, 01:25:21 PM

I have just tried this update.
My hash speed has gone up from 2.05 to .............................2.05
If I go any higher I have massive HW errors

From what I understand, depending on the unit you can't over-clock it higher without giving it more power.

One of the forum pages has some more info on changing the power resistors, to improve the overclocking.
I will stick at this level for now, 2.05Gh at the 5 second interval and 1.98Gh average at the pool.
Not bad at all for the price and power consumption. 1.28watts/Gh on 11 sticks.
Blue/RedFury are showing at 1.23watts/Gh but cost 3 or 4 times more to buy.
(starting to become a power tart)

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: Mudbankkeith on January 12, 2014, 01:25:21 PM

I have just tried this update.
My hash speed has gone up from 2.05 to .............................2.05
If I go any higher I have massive HW errors

From what I understand, depending on the unit you can't over-clock it higher without giving it more power.

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: nwoolls on January 12, 2014, 12:11:00 PM

Quote from: HiGer on January 12, 2014, 07:21:22 AM

I am using this (https://www.dropbox.com/s/z29x4n6ng510joi/bfgminer-npw-antminer.7z) in Win7x64 with the parameter "--set-device antminer:freq=0981" It starts up ok, finds the antminer but reports that
"AMU 0: Applying rule antminer:freq=0981: Unknown option:freq" and then starts hashing at the standard speed. Why? Supposedly overclocking is working? Am I doing something wrong?

Full start parameter is "bfgminer.exe -S antminer:all -o pooladdress:port -u XXX -p XXX --set-device antminer:freq=0981"

The format is now:

Code:

--set-device antminer:clock=x0981

I have just tried this update.
My hash speed has gone up from 2.05 to .............................2.05
If I go any higher I have massive HW errors

HiGer

newbie

Activity: 6

Merit: 0

Quote from: nwoolls on January 12, 2014, 12:11:00 PM

The format is now:

Code:

--set-device antminer:clock=x0981

Thank you!

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: cool77 on January 12, 2014, 12:51:07 PM

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:

Code:

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:

Code:

bfgminer -S antminer:all --set-device antminer@/dev/cu.SLAB_USBtoUART:clock=x0881

cool77

newbie

Activity: 13

Merit: 0

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.

Thanks!

cool77

newbie

Activity: 13

Merit: 0

Quote from: nwoolls on January 12, 2014, 12:11:00 PM

Quote from: HiGer on January 12, 2014, 07:21:22 AM

I am using this (https://www.dropbox.com/s/z29x4n6ng510joi/bfgminer-npw-antminer.7z) in Win7x64 with the parameter "--set-device antminer:freq=0981" It starts up ok, finds the antminer but reports that
"AMU 0: Applying rule antminer:freq=0981: Unknown option:freq" and then starts hashing at the standard speed. Why? Supposedly overclocking is working? Am I doing something wrong?

Full start parameter is "bfgminer.exe -S antminer:all -o pooladdress:port -u XXX -p XXX --set-device antminer:freq=0981"

The format is now:

Code:

--set-device antminer:clock=x0981

Wonderfull!

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: HiGer on January 12, 2014, 07:21:22 AM

I am using this (https://www.dropbox.com/s/z29x4n6ng510joi/bfgminer-npw-antminer.7z) in Win7x64 with the parameter "--set-device antminer:freq=0981" It starts up ok, finds the antminer but reports that
"AMU 0: Applying rule antminer:freq=0981: Unknown option:freq" and then starts hashing at the standard speed. Why? Supposedly overclocking is working? Am I doing something wrong?

Full start parameter is "bfgminer.exe -S antminer:all -o pooladdress:port -u XXX -p XXX --set-device antminer:freq=0981"

The format is now:

Code:

--set-device antminer:clock=x0981

cool77

newbie

Activity: 13

Merit: 0

Quote from: HiGer on January 12, 2014, 08:40:10 AM

Quote from: Mudbankkeith on January 12, 2014, 08:19:02 AM

Make sure you have the latest version of antminer.7z
I think there have been 3 now.

Mine says it was changed on Jan 12th 2014, 7:46PM. Thats the latest one, isn't it?

Using the parameters in the way you did yields the same result: "Unknown option:freq"

I'm in the same boat. Unknown option:freq.

I've tried both Jan 9th 01:32:18 and Jan 12th ‏‎01:45:59 bfgminer

With Jan 9th version, it does not give an error but running w/o OC.
With Jan 12th version, it gives the error.

I have win7 x64 using 2 X antminer.

Command line : C:\Bfgminer\bfgminer.exe -S antminer:all -o stratum.bitcoin.cz:3333 -u User -p Pass --set-device antminer:freq=0981

Cheers!

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: HiGer on January 12, 2014, 08:40:10 AM

Quote from: Mudbankkeith on January 12, 2014, 08:19:02 AM

Make sure you have the latest version of antminer.7z
I think there have been 3 now.

Mine says it was changed on Jan 12th 2014, 7:46PM. Thats the latest one, isn't it?

Using the parameters in the way you did yields the same result: "Unknown option:freq"

The version I am using is dated the 9th

HiGer

newbie

Activity: 6

Merit: 0

Quote from: Mudbankkeith on January 12, 2014, 08:19:02 AM

Make sure you have the latest version of antminer.7z
I think there have been 3 now.

Mine says it was changed on Jan 12th 2014, 7:46PM. Thats the latest one, isn't it?

Using the parameters in the way you did yields the same result: "Unknown option:freq"

Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 65. (Read 1193208 times)