Bitcoin Forum
August 20, 2017, 08:11:18 AM *
News: Latest stable version of Bitcoin Core: 0.14.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 [304] 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 ... 836 »
  Print  
Author Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.10.0  (Read 5377775 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
Beaflag VonRathburg
Sr. Member
****
Offline Offline

Activity: 472



View Profile
July 06, 2012, 02:26:42 AM
 #6061

Figured it out:

Win 7 would say it was downloading the BFL driver, but it wasn't actually doing something correct with it. I installed the BFL driver and all of the devices received COM numbers. Using -S COM# would only get six devices running in cgminer. I did some searching and found:

Thanks for your help. They each work individually. I just cant get them all to run.

-S "\\.\COM3" -S "\\.\COM4" -S "\\.\COM5"


Regards,
BF Labs Inc.

With all of the COM numbers put in all 10 devices were found and are now currently hashing.

There are several different types of Bitcoin clients. Server-assisted clients like blockchain.info rely on centralized servers to do their network verification for them. Although the server can't steal the client's bitcoins directly, it can easily execute double-spending-style attacks against the client.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1503216678
Hero Member
*
Offline Offline

Posts: 1503216678

View Profile Personal Message (Offline)

Ignore
1503216678
Reply with quote  #2

1503216678
Report to moderator
kano
Legendary
*
Offline Offline

Activity: 2184


Linux since 1997 RedHat 4


View Profile
July 06, 2012, 08:16:27 AM
 #6062

lulz ...
https://bitcointalk.org/index.php?topic=28402.msg1011546#msg1011546

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2254


Ruu \o/


View Profile WWW
July 06, 2012, 10:41:48 AM
 #6063

New Version: 2.5.0 - 6th July 2012

New version number signifying the updated BFL hardware support. Non-bfl miners have only bugfixes since 2.4.4.

Human readable changelog:

- Bitforce minirig support - including support for use on p2pool through use of the --bfl-range option, provided you have a new enough minirig that supports the nonce-range feature. By default this feature is disabled because it costs ~1% in hashrate, but given the massive loss of hashes you would otherwise have mining on p2pool, this is worth using. Other miners should leave it disabled.
- Huge update to other bitforce device. I've merged all of p_shep's changes into this code (thanks!). These can reenable devices, time out gracefully and mark them sick/overheated and so on.
- I've also created my own workaround for the biggest problem with existing bitforce devices - the can now abort work as soon as a longpoll hits which means literally half as much work on average wasted across longpoll than previously, and a much lower reject rate. Note these devices are still inefficient across longpoll since they don't even have the support the minirig devices have - and they never will according to bfl. This means you should never mine with them on p2pool.
- Fixed the dynamic GPU intensity behaviour which was getting stuck at -10 on faster GPUs.
- Updated API code with lots of changes under the hood courtesy of Kano, and updated miner.php.

Full changelog:

- Fix --benchmark not working since the dynamic addition of pools and pool
stats.
- Make disabling BFL nonce range support a warning since it has to be explicitly
enabled on the command line now.
- miner.php allow renaming table headers
- Make bitforce nonce range support a command line option --bfl-range since
enabling it decrease hashrate by 1%.
- Add sanity checking to make sure we don't make sleep_ms less than 0 in
bitforce.
- The fastest minirig devices need a significantly smaller starting sleep time.
- Use a much shorter initial sleep time to account for faster devices and nonce
range working, and increase it if nonce range fails to work.
- Use nmsleep instead of usleep in bitforce.
- Provide a ms based sleep function that uses nanosleep to avoid the inaccuracy
of usleep on SMP systems.
- delay_time_ms is always set so need not be initialised in bitforce.
- Increase bitforce timeout to 10 seconds.
- Add more hysteresis and poll ~5 times to allow for timer delays in bitforce
devices.
- miner.php allow alternating line colours (off by default)
- Display the actual duration of wait when it is greater than the cutoff.
- Set nonce to maximum once we determine nonce range support is broken.
- Initial wait time is always known so no need to zero it beforehand in
bitforce.
- No point counting wait time until the work is actually sent to bitforce
devices.
- Use string comparison functions instead of explicit comparisons.
- Account for wait_ms time when nonce_range is in use on BFL.
- Split nonces up into 1/5 chunks when nonce range is supported.
- limit clear buffer iterations.
- Ad fd check to clear buffer.
- miner.php remove incorrect 'DATE' error message
- miner.php allow summary header in custom pages
- Disable nonce range support in BFL when broken support is detected.
- Restart_wait is only called with a ms value so incorporate that into the
function.
- Only try to adjust dev width when curses is built in.
- miner.php define custom sum fields as a simple array
- Fix off-by-one error in nonce increment in bfl.
- Use BE when setting nonce in bitforce nonce range work.
- Enable nonce range in the normal init sequence for bfl.
- Queue extra work at 2/3 differently depending on whether we're using nonce
range or not.
- Initially enable support for nonce range support on bfl, splitting nonces up
into 3/4 size and only disable it if it fails on work submit.
- Attempt to detect nonce range support in BFL by sending work requring its
support.
- Limit retrying on busy for up to BITFORCE_TIMEOUT_MS
- Attempt to initialise while bitforce device returns BUSY.
- Extend length of string that can be passed to BFL devices.
- Fix signedness warning.
- Adjust device width column to be consistent.
- Use cgpu-> not gpus[] in watchdog thread.
- Add api stats (sleep time)
- Timing tweaks Added long and short timeouts, short for detecting throttling,
long to give up totally. Reset sleep time when device re-initialised Still check
results after timeout Back up a larger time if result on first poll.
- Add API Notify counter 'Comms Error'
- Style police on api.c
- Do all logging outside of the bitforce mutex locking to avoid deadlocks.
- Remove applog call from bfwrite to prevent grabbing nested mutexes.
- Bitforce style changes.
- Minor style changes.
- Remove needless roundl define.
- Made JSON error message verbose.
- Fine-tune timing adjustment. Also remove old work_restart timing.
- Check for gpu return times of >= 0, not just 0, to fix intensity dropping to
-10.
- Restart is zeroed in the mining thread so no need to do it inside the bitforce
code.
- More improvements to comms. BFL return nothing when throttling, so should not
be considered an error. Instead repeat with a longer delay.
- Polling every 10ms there's not much point checking the pthread_cond_timedwait
as it just adds overhead. Simply check the value of work_restart in the bfl main
polling loop.
- Use a pthread conditional that is broadcast whenever work restarts are
required. Create a generic wait function waiting a specified time on that
conditional that returns if the condition is met or a specified time passed to
it has elapsed. Use this to do smarter polling in bitforce to abort work, queue
more work, and check for results to minimise time spent working needlessly.
- Add busy time to wait time.
- api.c put version up to 1.14
- Add tiny delay after writing to BFL Change BFL errors to something more human
readable Send work busy re-tries after 10ms delay

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2254


Ruu \o/


View Profile WWW
July 06, 2012, 10:48:12 AM
 #6064

Alas, it's not like I actually own a minirig, but some generous donating and temporary remote access allowed me to work on the code for it. Note that this was a laptop connected to 2 minirigs, each with 17 devices in it. The silicon quality apparently varies from device to device which is why they're 2 speeds in this example. Note that this machine was generating 50Ghash, with an efficiency over 9000  Wink and the CPU usage was recording 1%.


Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
mdude77
Legendary
*
Offline Offline

Activity: 1400


View Profile
July 06, 2012, 11:37:10 AM
 #6065

Alas, it's not like I actually own a minirig, but some generous donating and temporary remote access allowed me to work on the code for it. Note that this was a laptop connected to 2 minirigs, each with 17 devices in it. The silicon quality apparently varies from device to device which is why they're 2 speeds in this example. Note that this machine was generating 50Ghash, with an efficiency over 9000  Wink and the CPU usage was recording 1%.


<sigh>

M
jamesg
VIP
Legendary
*
Offline Offline

Activity: 1358


AKA: gigavps


View Profile
July 06, 2012, 11:59:31 AM
 #6066

Alas, it's not like I actually own a minirig, but some generous donating and temporary remote access allowed me to work on the code for it. Note that this was a laptop connected to 2 minirigs, each with 17 devices in it. The silicon quality apparently varies from device to device which is why they're 2 speeds in this example. Note that this machine was generating 50Ghash, with an efficiency over 9000  Wink and the CPU usage was recording 1%.

Thanks for this work Con. You are the best in the business. I have cgminer 2.5.0 running on 14 singles and 3 mini rigs without issue.
dave3
Sr. Member
****
Offline Offline

Activity: 346


View Profile
July 06, 2012, 12:19:35 PM
 #6067

Thanks!

I compiled 2.5.0 for windows and I'm running it for a pair of BFL Singles.  So far so good.

I did try a test by pulling the plug on the Singles to see if they'd recover after being plugged back in, but no luck on that, yet.

Code:
[2012-07-06 19:38:09] Accepted a8d83928.6635d436 BFL 0 pool 0
[2012-07-06 19:38:11] Accepted ea99b76e.33143e03 BFL 1 pool 0
[2012-07-06 19:38:24] BFL0: took 15015ms - longer than 10000ms
[2012-07-06 19:38:24] BFL0: Error: Send work reports: ░?kLA
[2012-07-06 19:38:25] BFL1: took 15015ms - longer than 10000ms
[2012-07-06 19:38:26] Pool 0 not providing work fast enough
[2012-07-06 19:38:29] BFL0: Comms error
[2012-07-06 19:38:29] BFL0: Error: Send work reports: ╚?╒î┴v£öy|■   ╓┬└v?IA
[2012-07-06 19:38:34] BFL0: Comms error
[2012-07-06 19:38:34] BFL0: Error: Send work reports: ╚?╒î┴v£öy|■   ╓┬└v?IA

--------------------

2012-07-06 19:40:07] BFL1: Comms error
2012-07-06 19:40:07] BFL1: Error: Send work reports: ╚?╒î┴v£öy|^P
2012-07-06 19:40:07] BFL0: Idle for more than 60 seconds, declaring SICK!
2012-07-06 19:40:07] BFL0: Attempting to restart
2012-07-06 19:40:07] BFL0: Re-initalizing
2012-07-06 19:40:07] BFL0: Comms error
2012-07-06 19:40:12] BFL1: Comms error
2012-07-06 19:40:12] BFL1: Error: Send work reports: ╚?╒î┴v£öy|■   ╓┬└v?IA
2012-07-06 19:40:12] BFL0: Comms error
2012-07-06 19:40:17] BFL1: Comms error
2012-07-06 19:40:17] BFL1: Error: Send work reports: ╚?╒î┴v£öy|■   ╓┬└v?IA

--------------------

[2012-07-06 19:49:21] BFL1: Re-initalizing
[2012-07-06 19:50:10] BFL0: Re-initalizing
[2012-07-06 19:50:59] BFL0: Not responded for more than 10 minutes, declaring DEAD!
[2012-07-06 19:50:59] BFL1: Re-initalizing
[2012-07-06 19:52:01] BFL0: Re-initalizing

I added some exit(1)'s after some of those error messages in driver-bitforce.c as a hack so it can stop & restart.  Maybe not applicable for most people, though.
Vorksholk
Legendary
*
Offline Offline

Activity: 1554



View Profile WWW
July 06, 2012, 01:50:22 PM
 #6068

Anyone else having a problem of cgminer saying their BFL is over the heat threshold when it's only at 45C and stopping work on it? Sad

Fold Proteins, earn cryptos! CureCoin.
https://bitcointalk.org/index.php?topic=603757.0
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2254


Ruu \o/


View Profile WWW
July 06, 2012, 01:52:38 PM
 #6069

Anyone else having a problem of cgminer saying their BFL is over the heat threshold when it's only at 45C and stopping work on it? Sad
Check your configuration file or command line doesn't have temperature parameters for GPU(s), and that zero is being used for the BFL.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
P_Shep
Legendary
*
Offline Offline

Activity: 1036


View Profile WWW
July 06, 2012, 03:46:05 PM
 #6070

Anyone else having a problem of cgminer saying their BFL is over the heat threshold when it's only at 45C and stopping work on it? Sad
Check your configuration file or command line doesn't have temperature parameters for GPU(s), and that zero is being used for the BFL.

I found this too. My config file had 95 set for my two GPUs, then nothing more specified. by default, it should set any remaining devices to 95, but it didn't. I'm thinking it set it to 0. Anyway, I removed the conf. line and it worked fine.
P_Shep
Legendary
*
Offline Offline

Activity: 1036


View Profile WWW
July 06, 2012, 03:51:19 PM
 #6071

Thanks!

I compiled 2.5.0 for windows and I'm running it for a pair of BFL Singles.  So far so good.

I did try a test by pulling the plug on the Singles to see if they'd recover after being plugged back in, but no luck on that, yet.

Code:
[2012-07-06 19:38:09] Accepted a8d83928.6635d436 BFL 0 pool 0
[2012-07-06 19:38:11] Accepted ea99b76e.33143e03 BFL 1 pool 0
[2012-07-06 19:38:24] BFL0: took 15015ms - longer than 10000ms
[2012-07-06 19:38:24] BFL0: Error: Send work reports: ░?kLA
[2012-07-06 19:38:25] BFL1: took 15015ms - longer than 10000ms
[2012-07-06 19:38:26] Pool 0 not providing work fast enough
[2012-07-06 19:38:29] BFL0: Comms error
[2012-07-06 19:38:29] BFL0: Error: Send work reports: ╚?╒î┴v£öy|■   ╓┬└v?IA
[2012-07-06 19:38:34] BFL0: Comms error
[2012-07-06 19:38:34] BFL0: Error: Send work reports: ╚?╒î┴v£öy|■   ╓┬└v?IA

--------------------

2012-07-06 19:40:07] BFL1: Comms error
2012-07-06 19:40:07] BFL1: Error: Send work reports: ╚?╒î┴v£öy|^P
2012-07-06 19:40:07] BFL0: Idle for more than 60 seconds, declaring SICK!
2012-07-06 19:40:07] BFL0: Attempting to restart
2012-07-06 19:40:07] BFL0: Re-initalizing
2012-07-06 19:40:07] BFL0: Comms error
2012-07-06 19:40:12] BFL1: Comms error
2012-07-06 19:40:12] BFL1: Error: Send work reports: ╚?╒î┴v£öy|■   ╓┬└v?IA
2012-07-06 19:40:12] BFL0: Comms error
2012-07-06 19:40:17] BFL1: Comms error
2012-07-06 19:40:17] BFL1: Error: Send work reports: ╚?╒î┴v£öy|■   ╓┬└v?IA

--------------------

[2012-07-06 19:49:21] BFL1: Re-initalizing
[2012-07-06 19:50:10] BFL0: Re-initalizing
[2012-07-06 19:50:59] BFL0: Not responded for more than 10 minutes, declaring DEAD!
[2012-07-06 19:50:59] BFL1: Re-initalizing
[2012-07-06 19:52:01] BFL0: Re-initalizing

I added some exit(1)'s after some of those error messages in driver-bitforce.c as a hack so it can stop & restart.  Maybe not applicable for most people, though.


When you unplug a device then plug it back in it enumerates to a different port. Cgminer doesn't scan ports (yet) so it can't work out where it's gone.

Edit:
One thing you could try... in bitforce_init, remove the clear_buffer and add a sleep(5) between the BFclose and BFopen. See if that does anything
kano
Legendary
*
Offline Offline

Activity: 2184


Linux since 1997 RedHat 4


View Profile
July 06, 2012, 03:52:35 PM
 #6072

... and anyone looking for an Xubuntu 11.04 compile of 2.5.0
-> cgminer-2.5.0a at the top of https://github.com/kanoi/cgminer/downloads
(I'm running this executable at the moment on both my rigs)

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
dave3
Sr. Member
****
Offline Offline

Activity: 346


View Profile
July 06, 2012, 03:59:15 PM
 #6073

When you unplug a device then plug it back in it enumerates to a different port. Cgminer doesn't scan ports (yet) so it can't work out where it's gone.

For what it's worth, I'm pulling the plug on the power (the laptop that's running cgminer keeps running on batteries).  When I restart cgminer, it's still using the same serial ports (specified on the command line with -S).
P_Shep
Legendary
*
Offline Offline

Activity: 1036


View Profile WWW
July 06, 2012, 04:18:29 PM
 #6074

When you unplug a device then plug it back in it enumerates to a different port. Cgminer doesn't scan ports (yet) so it can't work out where it's gone.

For what it's worth, I'm pulling the plug on the power (the laptop that's running cgminer keeps running on batteries).  When I restart cgminer, it's still using the same serial ports (specified on the command line with -S).


In that case I'm thinking windows isn't closing / reopening the port properly.

Edit:
Yeah, a quick look suggests that a wait between closing and reopening may help.
The00Dustin
Hero Member
*****
Offline Offline

Activity: 806


View Profile
July 06, 2012, 04:32:57 PM
 #6075

When you unplug a device then plug it back in it enumerates to a different port. Cgminer doesn't scan ports (yet) so it can't work out where it's gone.

For what it's worth, I'm pulling the plug on the power (the laptop that's running cgminer keeps running on batteries).  When I restart cgminer, it's still using the same serial ports (specified on the command line with -S).


In that case I'm thinking windows isn't closing / reopening the port properly.

Edit:
Yeah, a quick look suggests that a wait between closing and reopening may help.
I'm confused as to why the port would change.  My experience with various removable serial ports (USB and otherwise, spanning at least 4 or 5 different device drivers) in Windows is that the enumerate the same consistently so long as they are plugged in the exact same port.  IOW, as long as any hubs are connected/initialized in the same order (so that the USB ports are still addressed the same) and the same singles are connected to the same USB ports, the same serial port numbers should be used.  Unless something is different about the controller BFL uses, the serial port numbers shouldn't change (Windows would need to think the same controller was plugged into a different port or a different controller was plugged into the same port when that hadn't happened).  I could see a mini-rig having a problem with address consistency if the chained hubs get detected in a different order, but I've never seen that happen with built-in ports or single hubs on a desktop or laptop.  Am I missing something?
P_Shep
Legendary
*
Offline Offline

Activity: 1036


View Profile WWW
July 06, 2012, 04:42:17 PM
 #6076

It does in Linux, and that's what I'm mainly using Smiley
The00Dustin
Hero Member
*****
Offline Offline

Activity: 806


View Profile
July 06, 2012, 04:47:39 PM
 #6077

It does in Linux, and that's what I'm mainly using Smiley
Fair enough.  For some reason, I was thinking you were specifically discussing Windows.  Either I crossed this conversation with another one in the same thread or I confused the -S designations for Windows vs Linux (I don't own any BFL product to help keep this straight in my head, and I was only trying to help).
BitMinerN8
Hero Member
*****
Offline Offline

Activity: 626


Mining since May 2011.


View Profile
July 06, 2012, 04:49:06 PM
 #6078

Just upgraded to cgminer 2.5.0 on BAMT 0.5, so far so good with 5 BFLs, 1 GPU.
farfie
Jr. Member
*
Offline Offline

Activity: 58



View Profile
July 06, 2012, 05:38:07 PM
 #6079

I'd like to chime in and say that after upgrading to CGminer 2.5.0, I'm getting an increased number when dividing DW by Q while solo mining. Doing this USED to get me ~ .003 - .006 in BFGminer 2.4.4. Now I'm getting above .01 on 2 different machines, both running Win 7x64. To be honest I'm not even sure doing this math means anything while solo mining, but it's what I've been doing to try and see how much work has been useless, and I can't see it being a good thing. Running 11 singles with a couple odd gpu's in 2 different cmd prompts across 2 machines.

Do these numbers actually mean nothing when solo mining or..? I figured I'd post this just in case. Maybe it was for naught Smiley
P_Shep
Legendary
*
Offline Offline

Activity: 1036


View Profile WWW
July 06, 2012, 05:44:04 PM
 #6080

I'd like to chime in and say that after upgrading to CGminer 2.5.0, I'm getting an increased number when dividing DW by Q while solo mining. Doing this USED to get me ~ .003 - .006 in BFGminer 2.4.4. Now I'm getting above .01 on 2 different machines, both running Win 7x64. To be honest I'm not even sure doing this math means anything while solo mining, but it's what I've been doing to try and see how much work has been useless, and I can't see it being a good thing. Running 11 singles with a couple odd gpu's in 2 different cmd prompts across 2 machines.

Do these numbers actually mean nothing when solo mining or..? I figured I'd post this just in case. Maybe it was for naught Smiley

I don't think it means anything.
AFAIK, DW is work requests that have been discarded for whatever reason. Work that has not be started, just retrieved from the server then thrown away.

I typically get 10-15% discards.
Pages: « 1 ... 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 [304] 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 ... 836 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!