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
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 546. (Read 5805728 times)
July 05, 2012, 02:31:41 PM
July 05, 2012, 02:07:14 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?
July 05, 2012, 02:02:35 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?
July 05, 2012, 01:54:02 AM
I have a question related to the --gpu-map option. I'm using RDP to connect and manage my Windows 7 PC remotely.
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. 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!
[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!
July 05, 2012, 01:41:54 AM
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. 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?
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.
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:
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
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
[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
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?
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?
July 03, 2012, 08:11:26 PM
pack dat shi up
July 03, 2012, 02:48:09 PM
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:
EDIT: removed 1 board, restarted. 1 random dead again.
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.
July 03, 2012, 10:14:55 AM
Binary! Binary! Binary!
July 03, 2012, 09:34:23 AM
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?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.
July 02, 2012, 08:42:06 PM
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.
I think the update makes it adjust fan speeds much slower than previous versions.
July 02, 2012, 08:41:19 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. 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
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
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
July 02, 2012, 07:19:17 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?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.
July 02, 2012, 07:17:52 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?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.
July 02, 2012, 05:36:22 PM
YAY! 3.5 more MHash from my PowerColor 5870!!
How ? What settings ? Kernel ?
Did you change anything ? Total MH/s ?
July 02, 2012, 05:03:49 PM
YAY! 3.5 more MHash from my PowerColor 5870!!
July 02, 2012, 01:29:41 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?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.
July 02, 2012, 12:56:12 PM
May want to take a look at the windows binary.
Getting 1.5Mh/s on my 5870s with the new 2.4.4.
Getting 1.5Mh/s on my 5870s with the new 2.4.4.
I haven't checked my intensity level but I have the same thing on my 6770m (a 5000 series card technically with add-in 6000-series features).
My 6950 and 6450 are enjoying an additional 10 and 4 MH/s... Interesting ratio...
Jump to: