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

JBT

full member

Activity: 165

Merit: 100

Quote from: vulgartrendkill on September 24, 2013, 05:55:16 AM

Quote

ed. also found if you stop start to many times i get this "Too many values passed to set temp cutoff" a reboot fixes this but is there a quicker way to reset this?

Yeah, I had this issue also. I went into my .conf file and removed all but 1 number in the temp cutoff part saved it as a .conf file and voila, no more error. The USBs do not have temp sensors, so the input is useless.

yup that worked

vulgartrendkill

hero member

Activity: 518

Merit: 500

Quote

ed. also found if you stop start to many times i get this "Too many values passed to set temp cutoff" a reboot fixes this but is there a quicker way to reset this?

Yeah, I had this issue also. I went into my .conf file and removed all but 1 number in the temp cutoff part saved it as a .conf file and voila, no more error. The USBs do not have temp sensors, so the input is useless.

JBT

full member

Activity: 165

Merit: 100

Quote from: Luke-Jr on September 23, 2013, 11:06:50 AM

Quote from: JBT on September 23, 2013, 03:58:58 AM

how difficult is it going the winUSB route?

WinUSB is the wrong driverfor this device, so won't work at all with any standard programs.

Quote from: Mudbankkeith on September 23, 2013, 06:16:57 AM

work division probably would not make a noticeable difference with 12 erupters. If you run 100 erupters then its worth it.

Work division must be correct for it to mine properly.
If it's failing to autodetect, there's likely a hardware problem (power, heat, etc).

found it. not power issue. i ran the 3 problem eruptors on their own and got this message. " ICA 0: Seems too slow to be an Icarus; calibrating with short timing" now all 12 are working

ed. also found if you stop start to many times i get this "Too many values passed to set temp cutoff" a reboot fixes this but is there a quicker way to reset this?

HellDiverUK

hero member

Activity: 1246

Merit: 501

Quote from: vesperwillow on September 23, 2013, 01:31:26 PM

Related: Are there any reccomendations for a good linux build to run BFG solely for getwork proxy ? I use headless ubuntu 12.04 right now but libmicrohttpd-dev is old, and I was hoping to simply install a new distro than trying to duct-tape something together. Willing to do that if necessary though.

Why not, you know, update libmicrohttpd-dev? Huh

It runs OK off Ubuntu 13.04 Server OK for me.

vulgartrendkill

hero member

Activity: 518

Merit: 500

All,

I'm currently using the -T command to make sure my blades and BE work ok (without it BFG crashes out). While in this mode, BFG does not respond to any normal commands.

Is there a way to enable them? I'd like to try out Load Balancing etc.

Thanks

vesperwillow

hero member

Activity: 616

Merit: 500

Related: Are there any reccomendations for a good linux build to run BFG solely for getwork proxy ? I use headless ubuntu 12.04 right now but libmicrohttpd-dev is old, and I was hoping to simply install a new distro than trying to duct-tape something together. Willing to do that if necessary though.

vesperwillow

hero member

Activity: 616

Merit: 500

Quote from: Zanatos666 on September 23, 2013, 12:02:14 PM

What about a firewall on your router (if you are using one)? Would also be an issue with that blocking it, instead of a Windows firewall.

Hardware WAN firewall doesn't affect lan-side equipment, and the devices are all connected between each other with switches anyhow.

Regarding the win32 crashes

I noticed that I was getting the connect-crash bug like some others. I haven't tried the special EXE yet which luke linked, I'll try that later. I didn't have all the failures the other guys did, mine only had one issue loading pdcurses (I believe that was the name).

Things were running fine, I told another blade to connect, and it pooped BFG. I restarted BFG in the same process window and then both connected fine. I exited/restarted BFG and then had them both connect simultaneously, and then tried it again with them connecting one at a time--without issue.

Whatever it is, it seems to be constrained to the process window. Close the window and then try doing it, and it'll happen again but only once per blade.

Other than that, it's running very well. I'm going to do some more cgminer/bfgminer tests to see how I like it. Fast response from luke is always a huge plus.

Zanatos666

sr. member

Activity: 280

Merit: 250

Sometimes man, just sometimes.....

Quote from: vesperwillow on September 23, 2013, 11:24:39 AM

I thought about the port release issue but verified that nothing was using the ports using netstat. The other proxy was on another machine entirely.

No firewall on the computer (makes testing easier)

However, I got it up and running by using another port entirely. Instead of 8332, I chose 8339. Now it's up and running. Going to let it stabalize and report its stats back.

I do find it curious that nothing is trying to use 8332 (or anything close) but that port just won't work. I'll try some other software on the port later and see if it's an issue regardless of software.

What about a firewall on your router (if you are using one)? Would also be an issue with that blocking it, instead of a Windows firewall.

vesperwillow

hero member

Activity: 616

Merit: 500

I thought about the port release issue but verified that nothing was using the ports using netstat. The other proxy was on another machine entirely.

No firewall on the computer (makes testing easier)

However, I got it up and running by using another port entirely. Instead of 8332, I chose 8339. Now it's up and running. Going to let it stabalize and report its stats back.

I do find it curious that nothing is trying to use 8332 (or anything close) but that port just won't work. I'll try some other software on the port later and see if it's an issue regardless of software.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: xyzzy099 on September 23, 2013, 11:17:28 AM

Quote from: vesperwillow on September 23, 2013, 11:03:57 AM

Same port for either proxy, 8332

Also if it matters: BFG is given -u worker.name -p pass and the blade is using worker.name2 same password.

I also tried them both being the same with no luck.

I would think that should work. BFGMiner doesn't care about the username or password the blade is using, as long as each blade has a unique username. Is it possible that the other proxy is not really releasing port 8332? I would think that BFGMiner would complain if it couldn't open the port, but I don't know what else might be wrong here.

Maybe check Windows Firewall?

xyzzy099

legendary

Activity: 1066

Merit: 1098

Quote from: vesperwillow on September 23, 2013, 11:03:57 AM

Same port for either proxy, 8332

Also if it matters: BFG is given -u worker.name -p pass and the blade is using worker.name2 same password.

I also tried them both being the same with no luck.

I would think that should work. BFGMiner doesn't care about the username or password the blade is using, as long as each blade has a unique username. Is it possible that the other proxy is not really releasing port 8332? I would think that BFGMiner would complain if it couldn't open the port, but I don't know what else might be wrong here.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: JBT on September 23, 2013, 03:58:58 AM

how difficult is it going the winUSB route?

WinUSB is the wrong driverfor this device, so won't work at all with any standard programs.

Quote from: Mudbankkeith on September 23, 2013, 06:16:57 AM

work division probably would not make a noticeable difference with 12 erupters. If you run 100 erupters then its worth it.

Work division must be correct for it to mine properly.
If it's failing to autodetect, there's likely a hardware problem (power, heat, etc).

vesperwillow

hero member

Activity: 616

Merit: 500

Same port for either proxy, 8332

Also if it matters: BFG is given -u worker.name -p pass and the blade is using worker.name2 same password.

I also tried them both being the same with no luck.

xyzzy099

legendary

Activity: 1066

Merit: 1098

Quote from: vesperwillow on September 23, 2013, 10:20:19 AM

Trying to use BFG miner as a getwork proxy to see how it compares to other options. Can't get blades to connect.. must be doing something wrong. I read the documentation and all it says is to run with the --http-port option. Here's how I've tried it:

bfgminer -o url:port -u workername -p password --http-port xxxx

this loads up just fine. the blade is setup to point to the system running bfgminer. bfg never sees a connection. if i close bfg and load the other proxy, the blade connects. This is the win32 version.

What am I doing wrong?

Maybe a stupid question, but are the blades set to connect to the port you specified in '--http-port xxxx', or the default port for your other proxy?

vesperwillow

hero member

Activity: 616

Merit: 500

Trying to use BFG miner as a getwork proxy to see how it compares to other options. Can't get blades to connect.. must be doing something wrong. I read the documentation and all it says is to run with the --http-port option. Here's how I've tried it:

bfgminer -o url:port -u workername -p password --http-port xxxx

this loads up just fine. the blade is setup to point to the system running bfgminer. bfg never sees a connection. if i close bfg and load the other proxy, the blade connects. This is the win32 version.

What am I doing wrong?

Taugeran

hero member

Activity: 658

Merit: 500

CCNA: There i fixed the internet.

Quote from: Paladin69 on September 23, 2013, 12:30:17 AM

Quote from: Taugeran on September 22, 2013, 04:25:16 PM

Right click the upper left corner click defaults and change settings. Save close window

Restart. Should be in effect now min width and buffer I recommend is 81 characters

cheers

Thanks man. Can you post an image of your qr code? I wanna send you a tip. Can't seem to log into my blockchain right now, but my phone works.

no need to tip. just being a helpful miner

astutiumRob

full member

Activity: 201

Merit: 100

Quote from: astutiumRob on September 20, 2013, 02:44:37 PM

But it simply wont start with the -S all and without it sees no Block Erupters

Further to this, if I start it with -S /dev/ttyUSB0 -S /dev/ttyUSB1 etc it loads ok (but is always 1 USB short of the actual when doing D - M), just the 'all' that causes it to stop

I'm thinking it's something to do with the BFL kit being in the middle of the USB Hub/Erupter chain - without the hub with eth BFL kit connected the -S all works

HellDiverUK

hero member

Activity: 1246

Merit: 501

Quote from: JBT on September 23, 2013, 05:37:54 AM

so u say the ica timing not needed? mmmm

ed. tried it getting this BES 2: Work division autodetection failed (assuming 2): got 00000000 ?
BES 4: Work division autodetection failed (assuming 2): got 00000000

Never seen that Work Division thing. The ICA timing isn't needed.

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: JBT on September 23, 2013, 05:37:54 AM

Quote from: HellDiverUK on September 23, 2013, 04:50:28 AM

Quote from: JBT on September 23, 2013, 03:53:59 AM

C:\miner\bfgminer321\bfgminer.exe -o pool -u worker1 -p password1 -L log.txt -G -S erupter:all

Fixed.

so u say the ica timing not needed? mmmm

ed. tried it getting this BES 2: Work division autodetection failed (assuming 2): got 00000000 ?
BES 4: Work division autodetection failed (assuming 2): got 00000000

Timings are only needed if you are doing non standard activities.
work division probably would not make a noticeable difference with 12 erupters. If you run 100 erupters then its worth it.

JBT

full member

Activity: 165

Merit: 100

Quote from: HellDiverUK on September 23, 2013, 04:50:28 AM

Quote from: JBT on September 23, 2013, 03:53:59 AM

C:\miner\bfgminer321\bfgminer.exe -o pool -u worker1 -p password1 -L log.txt -G -S erupter:all

Fixed.

so u say the ica timing not needed? mmmm

ed. tried it getting this BES 2: Work division autodetection failed (assuming 2): got 00000000 ?
BES 4: Work division autodetection failed (assuming 2): got 00000000

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