OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 544.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: Beaflag VonRathburg on July 05, 2012, 04:07:19 PM

Quote from: Epoch on June 03, 2012, 11:10:30 AM

Quote from: mdude77 on June 03, 2012, 10:53:49 AM

Quote from: rkozola on June 03, 2012, 10:42:40 AM

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; 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

Beaflag VonRathburg

sr. member

Activity: 472

Merit: 250

Quote from: Epoch on June 03, 2012, 11:10:30 AM

Quote from: mdude77 on June 03, 2012, 10:53:49 AM

Quote from: rkozola on June 03, 2012, 10:42:40 AM

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; 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

Activity: 1540

Merit: 1001

Quote from: rav3n_pl on July 05, 2012, 03:26:58 PM

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

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

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....

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: rav3n_pl on July 05, 2012, 02:38:10 PM

Quote from: mdude77 on July 05, 2012, 02:31:41 PM

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

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Quote from: mdude77 on July 05, 2012, 02:31:41 PM

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.

mdude77

legendary

Activity: 1540

Merit: 1001

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

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Fuzzy on July 05, 2012, 02:02:35 AM

Quote from: -ck on July 05, 2012, 01:41:54 AM

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.

Fuzzy

hero member

Activity: 560

Merit: 500

Quote from: -ck on July 05, 2012, 01:41:54 AM

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

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Diapolo on July 05, 2012, 01:11:11 AM

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.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Fuzzy on July 04, 2012, 08:50:04 PM

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.

Diapolo

hero member

Activity: 772

Merit: 500

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

Fuzzy

hero member

Activity: 560

Merit: 500

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:

Code:

{
"pools" : [

],

"intensity" : "9,9,9,9",
"temp-cutoff" : "95,95,95,95",

"expiry" : "120",
"gpu-threads" : "2",
"log" : "5",
"queue" : "1",
"retry-pause" : "5",
"scan-time" : "60",
"temp-hysteresis" : "3",

"kernel-path" : "/usr/local/bin"
}

Is there a line I'm missing to restart dead cards?

kentrolla

hero member

Activity: 1652

Merit: 569

Catalog Websites

pack dat shi up

punin

hero member

Activity: 560

Merit: 500

I've had strange issues with a cluster of 18 ztex boards connected through 2 separate powered hubs run by cgminer 2.4.2 and 2.4.4 on a Raspberry Pi. 1 random board dies (and gets a LED on). After 10 minutes cgminer pronounced it dead. I must stress that there's seems to be no logic in what board fails. It's completely erratic (4 different boards now after each restart of cgminer). Any clues?

EDIT: And now segfault:

Code:

 [2012-07-03 22:18:27] ZTEX 04A32Exxxx-1: Failed readHashData with err -1
 [2012-07-03 22:18:27] ZTEX 04A32Exxxx-1: Failed to read hash data with err -1, retrying
 [2012-07-03 22:18:27] ZTEX 04A32Exxxx-1: Failed readHashData with err -4
 [2012-07-03 22:18:27] ZTEX 04A32Exxxx-1: Disabling!
 [2012-07-03 22:18:27] ZTEX 04A32Exxxx-1: Failed to read hash data with err -4, giving upSegmentation fault

EDIT: removed 1 board, restarted. 1 random dead again.

ChanceCoats123

hero member

Activity: 682

Merit: 500

Binary! Binary! Binary!

TheHarbinger

sr. member

Activity: 378

Merit: 250

Why is it so damn hot in here?

Quote from: TheHarbinger on July 02, 2012, 07:17:52 PM

Quote from: TheHarbinger on July 02, 2012, 01:29:41 PM

Quote from: -ck on July 02, 2012, 08:56:14 AM

Quote from: -ck on July 01, 2012, 05:37:58 PM

Darn. Guess I broke instead of fixed dynamic. I'll have to investigate again soon...

I've committed a change to the git tree which should fix it. Can anyone who has the problem and builds from git confirm please?

~~Negative, not fixed. Fresh pull from git and built on a Win7 x64 system. Same behavior.~~

Edit: Did a new pull and tried it again. This time it works, I must have borked something up the first time. Going to let it run a bit and see how it does.

Edit #2: Has been running now for 3 hours. Seems to be stable. Will update again in the morning (12 hours). But so far it looks like a good candidate for a binary.

Edit #3: Coming up on 20 hours of running stable. I would say go ahead and pack it CKolivas. Only thing you might want to look at is I'm showing about 400% efficiency and a reject rate of 0.007%, so clearly something is wrong. Grin

GernMiester

sr. member

Activity: 285

Merit: 250

Stable here with BFL's and 3 GPU's. Seesm to get a few more Mh/s but the fans dont seems to slow back down as fast as they used to.
I think the update makes it adjust fan speeds much slower than previous versions.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: wildemagic on July 02, 2012, 07:22:56 PM

Stable here too on 4 x icarus with 2.4.4.

Still cant decide between 2.4.4 and 2.4.3.

Any advantages between the two versions? anything changed for icarus?

I use a proxy pool so I cant really tell if stales are better or worse since the pool swings between high rejects and low depending on where the hashes are going.

kind regards

Apart from broken dynamic intensity, 2.4.4 should be better across the board.

wildemagic

member

Activity: 112

Merit: 10

Stable here too on 4 x icarus with 2.4.4.

Still cant decide between 2.4.4 and 2.4.3.

Any advantages between the two versions? anything changed for icarus?

I use a proxy pool so I cant really tell if stales are better or worse since the pool swings between high rejects and low depending on where the hashes are going.

kind regards

Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 544. (Read 5806088 times)