Bitcoin Forum
June 24, 2018, 04:06:19 AM *
News: Latest stable version of Bitcoin Core: 0.16.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 253 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 ... 847 »
  Print  
Author Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.10.0  (Read 5756447 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.
Diapolo
Hero Member
*****
Offline Offline

Activity: 769
Merit: 500



View Profile WWW
July 05, 2012, 06:11:11 AM
 #6041

I have a question related to the --gpu-map option. I'm using RDP to connect and manage my Windows 7 PC remotely.
When I want to start mining, CGMINER tells me ADL and OpenCL devices do not match (which is no problem, when I sit in front of the PC and use it locally).

This is my cgminer.exe -n output:

Quote
[2012-07-05 08:00:24] CL Platform 0 vendor: Advanced Micro Devices, Inc.
 [2012-07-05 08:00:24] CL Platform 0 name: AMD Accelerated Parallel Processing
 [2012-07-05 08:00:24] CL Platform 0 version: OpenCL 1.2 AMD-APP (938.1)
 [2012-07-05 08:00:24] Platform 0 devices: 2
 [2012-07-05 08:00:24]  0       Tahiti
 [2012-07-05 08:00:24]  1       BeaverCreek
 [2012-07-05 08:00:24] Failed to ADL_Adapter_ID_Get. Error -5
 [2012-07-05 08:00:24] Failed to ADL_Adapter_ID_Get. Error -5
 [2012-07-05 08:00:24] Failed to ADL_Adapter_ID_Get. Error -5
 [2012-07-05 08:00:24] Failed to ADL_Adapter_ID_Get. Error -5
 [2012-07-05 08:00:24] Failed to ADL_Adapter_ID_Get. Error -5
 [2012-07-05 08:00:24] Failed to ADL_Adapter_ID_Get. Error -5
 [2012-07-05 08:00:25] Failed to ADL_Adapter_ID_Get. Error -5
 [2012-07-05 08:00:25] ADL found less devices than opencl!
 [2012-07-05 08:00:25] There is possibly more than one display attached to a GPU
 [2012-07-05 08:00:25] Use the gpu map feature to reliably map OpenCL to ADL
 [2012-07-05 08:00:25] WARNING: Number of OpenCL and ADL devices did not match!
 [2012-07-05 08:00:25] Hardware monitoring may NOT match up with devices!
 [2012-07-05 08:00:25] 2 GPU devices max detected

But now I'm unsure about how to map, as the listed devices 0 Tahiti and 1 BeaverCreek are correct (perhaps I should take a look at the output, when locally working on the machine though).

Thanks,
Dia

Liked my former work for Bitcoin Core? Drop me a donation via:
1PwnvixzVAKnAqp8LCV8iuv7ohzX2pbn5x
bitcoin:1PwnvixzVAKnAqp8LCV8iuv7ohzX2pbn5x?label=Diapolo
1529813179
Hero Member
*
Offline Offline

Posts: 1529813179

View Profile Personal Message (Offline)

Ignore
1529813179
Reply with quote  #2

1529813179
Report to moderator
1529813179
Hero Member
*
Offline Offline

Posts: 1529813179

View Profile Personal Message (Offline)

Ignore
1529813179
Reply with quote  #2

1529813179
Report to moderator
1529813179
Hero Member
*
Offline Offline

Posts: 1529813179

View Profile Personal Message (Offline)

Ignore
1529813179
Reply with quote  #2

1529813179
Report to moderator
The World's Betting Exchange

Bet with play money. Win real Bitcoin. 5BTC Prize Fund for World Cup 2018.

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2562
Merit: 1096


Ruu \o/


View Profile WWW
July 05, 2012, 06:41:54 AM
 #6042

I'm getting a "DEAD" signal after a few hours of mining on a card that works just fine if I close and re-open CGminer. I had the same issue with GUIminer where a simple stop/start (button in the program) would get the card going again, so the restart can be automated.

Kinda new to CGminer, so I'm guessing it's something with the code I fiddled with:

Is there a line I'm missing to restart dead cards?
It already tries to restart the cards itself without any options unless you specify --no-restart, but it only does so if it knows it's safe. It almost certainly has tried and failed and you're just lucky that restarting cgminer fixes it. I suggest  clocking less or cooling better if you're routinely killing the driver like that.

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: 2562
Merit: 1096


Ruu \o/


View Profile WWW
July 05, 2012, 06:54:02 AM
 #6043

I have a question related to the --gpu-map option. I'm using RDP to connect and manage my Windows 7 PC remotely.

Quote
[2012-07-05 08:00:24] CL Platform 0 vendor: Advanced Micro Devices, Inc.

 [2012-07-05 08:00:24] Platform 0 devices: 2
 [2012-07-05 08:00:24]  0       Tahiti
 [2012-07-05 08:00:24]  1       BeaverCreek

 [2012-07-05 08:00:25] ADL found less devices than opencl!
CL found 2 devices, so presumably adl is only finding one. Many remote access software thingamajigs only work with the first device. Dunno about losedows... but it's the equivalent of not doing EXPORT DISPLAY on linux.

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

Activity: 560
Merit: 500



View Profile
July 05, 2012, 07:02:35 AM
 #6044

It already tries to restart the cards itself without any options unless you specify --no-restart, but it only does so if it knows it's safe. It almost certainly has tried and failed and you're just lucky that restarting cgminer fixes it. I suggest  clocking less or cooling better if you're routinely killing the driver like that.

Is there a way to make it keep trying to restart the dead card every X seconds?
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2562
Merit: 1096


Ruu \o/


View Profile WWW
July 05, 2012, 07:07:14 AM
 #6045

It already tries to restart the cards itself without any options unless you specify --no-restart, but it only does so if it knows it's safe. It almost certainly has tried and failed and you're just lucky that restarting cgminer fixes it. I suggest  clocking less or cooling better if you're routinely killing the driver like that.

Is there a way to make it keep trying to restart the dead card every X seconds?
It does so every minute already. If however the restart thread is killed by the driver destroying it, it does not try to restart it any further because that is usually when it will crash the entire of cgminer instead, so the safer option is to at least let any remaining devices keep mining. Most cards, when they go DEAD, usually cgminer will keep mining on the rest of the devices, but you have to actually reboot to get the dead one back.

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: 1540
Merit: 1001



View Profile
July 05, 2012, 07:31:41 PM
 #6046

I'm playing with p2pool again.  I have 3 miners pointing to a local pool.  Two are cgminer 2.4.4, one is phoenix 2.0.0.  I get this in the p2pool log every so often for cgminers, not sure about the phoenix miner:

2012-07-05 15:28:18.808000 > Worker q6600 @ 127.0.0.1 submitted share more than once!

p2pool, cgminer, or something else causing this?

M

I mine at Kano's Pool because it pays the best and is completely transparent!  Come join me!
rav3n_pl
Legendary
*
Offline Offline

Activity: 1359
Merit: 1000


Don`t panic! Organize!


View Profile WWW
July 05, 2012, 07:38:10 PM
 #6047

I'm playing with p2pool again.  I have 3 miners pointing to a local pool.  Two are cgminer 2.4.4, one is phoenix 2.0.0.  I get this in the p2pool log every so often for cgminers, not sure about the phoenix miner:

2012-07-05 15:28:18.808000 > Worker q6600 @ 127.0.0.1 submitted share more than once!

p2pool, cgminer, or something else causing this?

M
Try use different login names for each worker.
Looks like different workers find exact same share and send it to p2pool, but it seems very unlikely near to impossible.

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
Some stuff on https://github.com/Rav3nPL/
mdude77
Legendary
*
Offline Offline

Activity: 1540
Merit: 1001



View Profile
July 05, 2012, 08:14:48 PM
 #6048

I'm playing with p2pool again.  I have 3 miners pointing to a local pool.  Two are cgminer 2.4.4, one is phoenix 2.0.0.  I get this in the p2pool log every so often for cgminers, not sure about the phoenix miner:

2012-07-05 15:28:18.808000 > Worker q6600 @ 127.0.0.1 submitted share more than once!

p2pool, cgminer, or something else causing this?

M
Try use different login names for each worker.
Looks like different workers find exact same share and send it to p2pool, but it seems very unlikely near to impossible.

Each worker has it's own name.  miner1, miner2, q6600.

M

I mine at Kano's Pool because it pays the best and is completely transparent!  Come join me!
rav3n_pl
Legendary
*
Offline Offline

Activity: 1359
Merit: 1000


Don`t panic! Organize!


View Profile WWW
July 05, 2012, 08:26:58 PM
 #6049

Code:
elif header_hash in received_header_hashes:
print >>sys.stderr, 'Worker %s @ %s submitted share more than once!' % (request.getUser(), request.getClientIP())
This message is shown, when miner send exact same share that is already in share chain.

What p2pool version? It is very odd....

1Rav3nkMayCijuhzcYemMiPYsvcaiwHni  Bitcoin stuff on my OneDrive
My RPC CoinControl for any coin https://bitcointalk.org/index.php?topic=929954
Some stuff on https://github.com/Rav3nPL/
mdude77
Legendary
*
Offline Offline

Activity: 1540
Merit: 1001



View Profile
July 05, 2012, 08:33:03 PM
 #6050

Code:
elif header_hash in received_header_hashes:
print >>sys.stderr, 'Worker %s @ %s submitted share more than once!' % (request.getUser(), request.getClientIP())
This message is shown, when miner send exact same share that is already in share chain.

What p2pool version? It is very odd....

I confirmed, I'm getting it from all 3 miners, two are cgminer.  So I'm not sure this is a cgminer issue.

And I see it fairly regularly, enough that I can just watch the p2pool interface scroll by and they jump out at me.  My biggest miner sometimes has it 2x in a row.

I'm on p2pool 3.1, the latest as far as I can tell.  Windows version.

Should I cross post in the p2pool forum?
EDIT: posted into p2pool forum.

M

I mine at Kano's Pool because it pays the best and is completely transparent!  Come join me!
Beaflag VonRathburg
Sr. Member
****
Offline Offline

Activity: 443
Merit: 250



View Profile
July 05, 2012, 09:07:19 PM
 #6051

Is there a known issue trying to run 5 or more BFL singles under windows in either 2.4.1 or 2.4.2?  2.3.6 seems to be able to handle 5 singles fine.  But every time I try to run all five under a single instance with 2.4.1 or 2.4.2, I get a crash in libpdcurses.dll.

Faulting application name: cgminer.exe, version: 0.0.0.0, time stamp: 0x4fcad128
Faulting module name: libpdcurses.dll, version: 0.0.0.0, time stamp: 0x4f460f95
Exception code: 0xc0000005
Fault offset: 0x000012fe
Faulting process id: 0xb24
Faulting application start time: 0x01cd419e02e067d8
Faulting application path: C:\Users\miner\Desktop\cgminer-2.4.2-win32\cgminer.exe
Faulting module path: C:\Users\miner\Desktop\cgminer-2.4.2-win32\libpdcurses.dll

I think I saw a thread elsewhere here that said if you increase the size of the command window in windows, it might solve this problem.

Yes, increasing the size of the command window (before starting cgminer) has helped people with similar symptoms.

(EDIT: I've seen you already got it working.)

To set a larger size as a default, hit start->run and type in cmd.exe<enter>; then click the black system icon in the top left corner of the command window that pops up. Choose 'properties'. The important thing here is the 'Layout' tab. Specifically Window Height. Set the Window height to 40 or 50. You can change the font as well to make it fit your monitor better. Click ok. You may then exit the command window. Any command window you open after this will come up with its new size.

There is a difference in how different versions of cgminer behave with Singles. 2.3.6 worked perfectly for me with up to 15 Singles. I since moved to 2.4.1 (and now 2.4.2) and have found that, using the same command line and command window layout size, 15 Singles crashes it. 2.4.1 are happy with 10 Singles, but not 15. 2.3.6 works fine with 15.

I don't know what broke between cgminer 2.3.6 and 2.4.1. It also behaves differently when Singles go offline; 2.3.6 just exited (which was good) but 2.4.1 and 2.4.2 just mark them as 'OFF' and do not exit (bad).

Win 7 x64
9x BFL Singles
10 Port powered USB hub


Issue: Neither 2.4.4 nor 2.3.6 will start more than 6 BFL singles

Troubleshooting:
- Multiple restarts usually resulting in BFL singles receiving different COM numbers than previous reboot
- Powering and unpowering USB hub
- Plugging USB hub into multiple USB 2 ports will cause zero BFL singles to start in cgminer
- Plugging into USB 3 port will allow 6 BFL singles to start in cgminer, but I receive a, "This device can perfom faster when plugged into a USB 2.0 port," message
- Plugging the 3 BFL singles that where not starting in cgminer into another computer directly to the front USB ports. None would start resulting in same COM errors (2.4.3)

At this point I'm trying to figure out if the USB hub, cables from hub --> singles, cgminer, or the singles themselves are the point of error. All singles light up and the fans spin. Any help would be greatly appreciated.

mdude77
Legendary
*
Offline Offline

Activity: 1540
Merit: 1001



View Profile
July 05, 2012, 09:09:00 PM
 #6052

Is there a known issue trying to run 5 or more BFL singles under windows in either 2.4.1 or 2.4.2?  2.3.6 seems to be able to handle 5 singles fine.  But every time I try to run all five under a single instance with 2.4.1 or 2.4.2, I get a crash in libpdcurses.dll.

Faulting application name: cgminer.exe, version: 0.0.0.0, time stamp: 0x4fcad128
Faulting module name: libpdcurses.dll, version: 0.0.0.0, time stamp: 0x4f460f95
Exception code: 0xc0000005
Fault offset: 0x000012fe
Faulting process id: 0xb24
Faulting application start time: 0x01cd419e02e067d8
Faulting application path: C:\Users\miner\Desktop\cgminer-2.4.2-win32\cgminer.exe
Faulting module path: C:\Users\miner\Desktop\cgminer-2.4.2-win32\libpdcurses.dll

I think I saw a thread elsewhere here that said if you increase the size of the command window in windows, it might solve this problem.

Yes, increasing the size of the command window (before starting cgminer) has helped people with similar symptoms.

(EDIT: I've seen you already got it working.)

To set a larger size as a default, hit start->run and type in cmd.exe<enter>; then click the black system icon in the top left corner of the command window that pops up. Choose 'properties'. The important thing here is the 'Layout' tab. Specifically Window Height. Set the Window height to 40 or 50. You can change the font as well to make it fit your monitor better. Click ok. You may then exit the command window. Any command window you open after this will come up with its new size.

There is a difference in how different versions of cgminer behave with Singles. 2.3.6 worked perfectly for me with up to 15 Singles. I since moved to 2.4.1 (and now 2.4.2) and have found that, using the same command line and command window layout size, 15 Singles crashes it. 2.4.1 are happy with 10 Singles, but not 15. 2.3.6 works fine with 15.

I don't know what broke between cgminer 2.3.6 and 2.4.1. It also behaves differently when Singles go offline; 2.3.6 just exited (which was good) but 2.4.1 and 2.4.2 just mark them as 'OFF' and do not exit (bad).

Win 7 x64
9x BFL Singles
10 Port powered USB hub


Issue: Neither 2.4.4 nor 2.3.6 will start more than 6 BFL singles

Troubleshooting:
- Multiple restarts usually resulting in BFL singles receiving different COM numbers than previous reboot
- Powering and unpowering USB hub
- Plugging USB hub into multiple USB 2 ports will cause zero BFL singles to start in cgminer
- Plugging into USB 3 port will allow 6 BFL singles to start in cgminer, but I receive a, "This device can perfom faster when plugged into a USB 2.0 port," message
- Plugging the 3 BFL singles that where not starting in cgminer into another computer directly to the front USB ports. None would start resulting in same COM errors (2.4.3)

At this point I'm trying to figure out if the USB hub, cables from hub --> singles, cgminer, or the singles themselves are the point of error. All singles light up and the fans spin. Any help would be greatly appreciated.

I'm pretty sure I've seen this before.  If you resize the window cgminer runs in, it might fix it.

M

I mine at Kano's Pool because it pays the best and is completely transparent!  Come join me!
kano
Legendary
*
Offline Offline

Activity: 2492
Merit: 1042


Linux since 1997 RedHat 4


View Profile
July 05, 2012, 09:45:02 PM
 #6053

...
Win 7 x64
9x BFL Singles
10 Port powered USB hub


Issue: Neither 2.4.4 nor 2.3.6 will start more than 6 BFL singles
...
At this point I'm trying to figure out if the USB hub, cables from hub --> singles, cgminer, or the singles themselves are the point of error. All singles light up and the fans spin. Any help would be greatly appreciated.
With 2.4.4 it detects 2 specific problems and displays a message:
1) Do not have user privileges required to open %s
2) %s is already in use by another process
If you are not getting either of those messages, then running cgminer also with the -D option it will give you a message why it can't start some of your BFLs

However, I guess the fix might be one of:
1) Try using "\\.\COMn" (not just "COMn") if you aren't already
2) use "bitforce:\\.\COMn" for all the devices (<- this is the most likely fix on Win 7 64bit)

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!
Beaflag VonRathburg
Sr. Member
****
Offline Offline

Activity: 443
Merit: 250



View Profile
July 05, 2012, 09:50:21 PM
 #6054

Is there a known issue trying to run 5 or more BFL singles under windows in either 2.4.1 or 2.4.2?  2.3.6 seems to be able to handle 5 singles fine.  But every time I try to run all five under a single instance with 2.4.1 or 2.4.2, I get a crash in libpdcurses.dll.

Faulting application name: cgminer.exe, version: 0.0.0.0, time stamp: 0x4fcad128
Faulting module name: libpdcurses.dll, version: 0.0.0.0, time stamp: 0x4f460f95
Exception code: 0xc0000005
Fault offset: 0x000012fe
Faulting process id: 0xb24
Faulting application start time: 0x01cd419e02e067d8
Faulting application path: C:\Users\miner\Desktop\cgminer-2.4.2-win32\cgminer.exe
Faulting module path: C:\Users\miner\Desktop\cgminer-2.4.2-win32\libpdcurses.dll

I think I saw a thread elsewhere here that said if you increase the size of the command window in windows, it might solve this problem.

Yes, increasing the size of the command window (before starting cgminer) has helped people with similar symptoms.

(EDIT: I've seen you already got it working.)

To set a larger size as a default, hit start->run and type in cmd.exe<enter>; then click the black system icon in the top left corner of the command window that pops up. Choose 'properties'. The important thing here is the 'Layout' tab. Specifically Window Height. Set the Window height to 40 or 50. You can change the font as well to make it fit your monitor better. Click ok. You may then exit the command window. Any command window you open after this will come up with its new size.

There is a difference in how different versions of cgminer behave with Singles. 2.3.6 worked perfectly for me with up to 15 Singles. I since moved to 2.4.1 (and now 2.4.2) and have found that, using the same command line and command window layout size, 15 Singles crashes it. 2.4.1 are happy with 10 Singles, but not 15. 2.3.6 works fine with 15.

I don't know what broke between cgminer 2.3.6 and 2.4.1. It also behaves differently when Singles go offline; 2.3.6 just exited (which was good) but 2.4.1 and 2.4.2 just mark them as 'OFF' and do not exit (bad).

Win 7 x64
9x BFL Singles
10 Port powered USB hub


Issue: Neither 2.4.4 nor 2.3.6 will start more than 6 BFL singles

Troubleshooting:
- Multiple restarts usually resulting in BFL singles receiving different COM numbers than previous reboot
- Powering and unpowering USB hub
- Plugging USB hub into multiple USB 2 ports will cause zero BFL singles to start in cgminer
- Plugging into USB 3 port will allow 6 BFL singles to start in cgminer, but I receive a, "This device can perfom faster when plugged into a USB 2.0 port," message
- Plugging the 3 BFL singles that where not starting in cgminer into another computer directly to the front USB ports. None would start resulting in same COM errors (2.4.3)

At this point I'm trying to figure out if the USB hub, cables from hub --> singles, cgminer, or the singles themselves are the point of error. All singles light up and the fans spin. Any help would be greatly appreciated.

I'm pretty sure I've seen this before.  If you resize the window cgminer runs in, it might fix it.

M

Window size is already set to 87x56. I've tried increasing it upto 90x80, but it has no effect.

Pictures:



wildemagic
Member
**
Offline Offline

Activity: 112
Merit: 10



View Profile
July 05, 2012, 10:02:14 PM
 #6055

Yay, just compiled my own win32 2.4.4 with icarus support and no ocl adl etc.

Used the instructions here : http://pastebin.com/3pzivj32

Worked first time, happy camper.  Now I can copy the binaries onto my intel integrated devices and not have the usual no-sdk issues.

kind regards

.,-._|\     Offgrid 1.7kW Solar and 3G wireless internet powering my mining rig.
/ .Oz. \
\_,--.x/     [219.5btc of successful trades total] with : rastapool, miernik, flatronw & OneFixt
       o
kano
Legendary
*
Offline Offline

Activity: 2492
Merit: 1042


Linux since 1997 RedHat 4


View Profile
July 05, 2012, 10:12:12 PM
 #6056

Yay, just compiled my own win32 2.4.4 with icarus support and no ocl adl etc.

Used the instructions here : http://pastebin.com/3pzivj32

Worked first time, happy camper.  Now I can copy the binaries onto my intel integrated devices and not have the usual no-sdk issues.

kind regards
Yep those instructions are part of cgminer:
https://github.com/ckolivas/cgminer/blob/master/windows-build.txt

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!
Beaflag VonRathburg
Sr. Member
****
Offline Offline

Activity: 443
Merit: 250



View Profile
July 06, 2012, 12:50:48 AM
 #6057


Win 7 x64
9x BFL Singles
10 Port powered USB hub


Issue: Neither 2.4.4 nor 2.3.6 will start more than 6 BFL singles

Troubleshooting:
- Multiple restarts usually resulting in BFL singles receiving different COM numbers than previous reboot
- Powering and unpowering USB hub
- Plugging USB hub into multiple USB 2 ports will cause zero BFL singles to start in cgminer
- Plugging into USB 3 port will allow 6 BFL singles to start in cgminer, but I receive a, "This device can perfom faster when plugged into a USB 2.0 port," message
- Plugging the 3 BFL singles that where not starting in cgminer into another computer directly to the front USB ports. None would start resulting in same COM errors (2.4.3)

At this point I'm trying to figure out if the USB hub, cables from hub --> singles, cgminer, or the singles themselves are the point of error. All singles light up and the fans spin. Any help would be greatly appreciated.

I'm pretty sure I've seen this before.  If you resize the window cgminer runs in, it might fix it.

M

Window size is already set to 87x56. I've tried increasing it upto 90x80, but it has no effect.

Pictures:




I just went and purchased a 4 port powered USB hub to test out if my 10 port was an issue along with some hardware to reassemble my 10th single. Out of the four singles attached to the new hub zero will start in cgminer. Using multiple rear USB 2/3 ports for the hub has no change. This almost added to the issues as now one of the BFL singles is not being assigned a COM number (Com 38, 39 ,Blank, 41). It should be 40, but that will not work either. With the four port hub added to the system I can now only get 5 singles to start in cgminer. This is pretty much driving me insane.

Beaflag VonRathburg
Sr. Member
****
Offline Offline

Activity: 443
Merit: 250



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

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.

kano
Legendary
*
Offline Offline

Activity: 2492
Merit: 1042


Linux since 1997 RedHat 4


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

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: 2562
Merit: 1096


Ruu \o/


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

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
Pages: « 1 ... 253 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 ... 847 »
  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!