It would appear that the latest version of cgminer still has no provision for mining different devices as different usernames and I need to run multiple copies of cgminer to accomplish this. Is this understanding accurate?
That's correct. 
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 422. (Read 5805998 times)
December 14, 2012, 03:33:35 AM
December 14, 2012, 03:31:53 AM
Performance for me exactly like 2.9.x versions.
Which is good because that's what it's supposed to be. Performance with current hardware (i.e. no asics) should have maximised with stratum support already. The changes in 2.10 are for the future. December 14, 2012, 03:30:00 AM
I tried the debugging-Version of cgminer.exe which ended with this Access Violation:
I guess this won't help you very much?
Quote
cgminer.exe caused an Access Violation at location 65722074 Reading from location 65722074.
Registers:
eax=00000000 ebx=0028fa58 ecx=74e92e09 edx=00000000 esi=00000002 edi=00000000
eip=65722074 esp=0028fa24 ebp=0028faa4 iopl=0 nv up ei pl nz na po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
Call stack:
65722074
07F32A67
74FD1A2C kernel32.dll:74FD1A2C WaitForMultipleObjectsEx
74FD4220 kernel32.dll:74FD4220 WaitForMultipleObjects
6248320B pthreadGC2.dll:6248320B pthreadCancelableTimedWait
Registers:
eax=00000000 ebx=0028fa58 ecx=74e92e09 edx=00000000 esi=00000002 edi=00000000
eip=65722074 esp=0028fa24 ebp=0028faa4 iopl=0 nv up ei pl nz na po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
Call stack:
65722074
07F32A67
74FD1A2C kernel32.dll:74FD1A2C WaitForMultipleObjectsEx
74FD4220 kernel32.dll:74FD4220 WaitForMultipleObjects
6248320B pthreadGC2.dll:6248320B pthreadCancelableTimedWait
I guess this won't help you very much?
I went back to Version 2.8.7 and it works like a charm on stratum...
December 14, 2012, 01:20:08 AM
Performance for me exactly like 2.9.x versions.
December 13, 2012, 09:19:28 PM
I've just made cgminer 2.10.0 at Raspberry Pi to drive my Cairnsmore CM1.
Looks like it performs a bit better than the same version on Win7 at i7-2600K.
normal, its linux Looks like it performs a bit better than the same version on Win7 at i7-2600K.
December 13, 2012, 06:19:20 PM
api.mining.cz doesn't exist. use api.bitcoin.cz instead. Or, preferably, "stratum+tcp://stratum.bitcoin.cz:3333"
Sorry, I had a brain error when typing that, but I am indeed using http://api.bitcoin.cz:8332 (which auto-upgrades to Stratum anyway)
I'll switch to the using the stratum+tcp URL if that's prefered.
roy
December 13, 2012, 05:59:00 PM
Just had 2.10.0 fail to failover on me. My configured pools are:
stratum+tcp://us1.eclipsemc.com:3333
stratum+tcp://us2.eclipsemc.com:3333
stratum+tcp://eustratum.ozco.in:3333
http://api.mining.cz:8332
stratum+tcp://us1.eclipsemc.com:3333
stratum+tcp://us2.eclipsemc.com:3333
stratum+tcp://eustratum.ozco.in:3333
http://api.mining.cz:8332
api.mining.cz doesn't exist. use api.bitcoin.cz instead. Or, preferably, "stratum+tcp://stratum.bitcoin.cz:3333"
December 13, 2012, 05:12:22 PM
I've just made cgminer 2.10.0 at Raspberry Pi to drive my Cairnsmore CM1.
Looks like it performs a bit better than the same version on Win7 at i7-2600K.
Looks like it performs a bit better than the same version on Win7 at i7-2600K.
December 13, 2012, 04:23:52 PM
Still seeing backup pools that use stratum+tcp URLs detected as down by cgminer (2.9.6)
e.g. neither of these seem to work right as backup pools :
stratum+tcp://us3.eclipsemc.com:3333
stratum+tcp://eustratum.ozco.in:3333
However specifying them as http (even though they're not) seems to work:
http://us3.eclipsemc.com:3333
http://eustratum.ozco.in:3333
(Note I only see this problem for backup pools - specifying stratum+tcp for my first pool seems to work fine)
roy
Yeah, not ideal, is it? Just get rid of *any* prefix and let cgminer figure it out. eg eustratum.ozco.in:3333e.g. neither of these seem to work right as backup pools :
stratum+tcp://us3.eclipsemc.com:3333
stratum+tcp://eustratum.ozco.in:3333
However specifying them as http (even though they're not) seems to work:
http://us3.eclipsemc.com:3333
http://eustratum.ozco.in:3333
(Note I only see this problem for backup pools - specifying stratum+tcp for my first pool seems to work fine)
roy
I think Con answered this here, unless there is something different
Yes, this appears to be something different, although it could well be related. The original problem with stratum+tcp:// URLs was fixed.
December 13, 2012, 04:19:10 PM
Still seeing backup pools that use stratum+tcp URLs detected as down by cgminer (2.9.6)
e.g. neither of these seem to work right as backup pools :
stratum+tcp://us3.eclipsemc.com:3333
stratum+tcp://eustratum.ozco.in:3333
However specifying them as http (even though they're not) seems to work:
http://us3.eclipsemc.com:3333
http://eustratum.ozco.in:3333
(Note I only see this problem for backup pools - specifying stratum+tcp for my first pool seems to work fine)
roy
Yeah, not ideal, is it? Just get rid of *any* prefix and let cgminer figure it out. eg eustratum.ozco.in:3333e.g. neither of these seem to work right as backup pools :
stratum+tcp://us3.eclipsemc.com:3333
stratum+tcp://eustratum.ozco.in:3333
However specifying them as http (even though they're not) seems to work:
http://us3.eclipsemc.com:3333
http://eustratum.ozco.in:3333
(Note I only see this problem for backup pools - specifying stratum+tcp for my first pool seems to work fine)
roy
I think Con answered this here, unless there is something different
December 13, 2012, 04:13:35 PM
This code doesn't seem to be working for me in the config file. It sticks to mining on pool 0 even though there are 5 connected. I'm running the program directly from the cgminer-fpgaonly.exe file.
Any ideas why?
Code:
"balance" : true,
Any ideas why?
My issue is resolved with the latest version. Working how it should now. I'm very pleased.
December 13, 2012, 03:26:19 PM
Same thing happened to me on 2.9.6 I think it was. Eclipse US1 server was never marked dead. No idea why.
EDIT US1 marked dead for me currently
EDIT2: Clear as mud I had this problem a while ago. Not today. I could look back and find it. But I didn't as the 2.10.0 que is a redo and likely isn't functionally the same as before as it is serial rather then parallell asynchronus.
EDIT US1 marked dead for me currently
EDIT2: Clear as mud I had this problem a while ago. Not today. I could look back and find it. But I didn't as the 2.10.0 que is a redo and likely isn't functionally the same as before as it is serial rather then parallell asynchronus.
December 13, 2012, 03:05:43 PM
Just had 2.10.0 fail to failover on me. My configured pools are:
stratum+tcp://us1.eclipsemc.com:3333
stratum+tcp://us2.eclipsemc.com:3333
stratum+tcp://eustratum.ozco.in:3333
http://api.mining.cz:8332
us1.eclipsemc.com appears to have gone down (for stratum at least) and cgminer displayed the following:
Lost 19 shares due to stratum disconnect on pool 0
Pool 0 stratum+tcp://us1.eclipsemc.com:3333 not responding
Pool 0 stratum share submission failure
....and then nothing more (and no failover). The top of the screen still showed
Connected to us1.eclipsemc.com with stratum as user ...
And the pool management screen showed all four pools as dead.
Restarting cgminer, it now shows only pool 0 dead, pools 1-3 alive, and is happily mining on pool 1.
roy
stratum+tcp://us1.eclipsemc.com:3333
stratum+tcp://us2.eclipsemc.com:3333
stratum+tcp://eustratum.ozco.in:3333
http://api.mining.cz:8332
us1.eclipsemc.com appears to have gone down (for stratum at least) and cgminer displayed the following:
Lost 19 shares due to stratum disconnect on pool 0
Pool 0 stratum+tcp://us1.eclipsemc.com:3333 not responding
Pool 0 stratum share submission failure
....and then nothing more (and no failover). The top of the screen still showed
Connected to us1.eclipsemc.com with stratum as user ...
And the pool management screen showed all four pools as dead.
Restarting cgminer, it now shows only pool 0 dead, pools 1-3 alive, and is happily mining on pool 1.
roy
December 13, 2012, 12:55:52 PM
What kind of computer had a bootloader like that?
i first ran across it in win 8 and thought it was MS. but tried installing linux on my 3 miners with win 7 and it also blocked me. now i think it is the bootloader program.
Security setting in BIOS?
bios is blocking the usb boot.
December 13, 2012, 12:54:45 PM
What kind of computer had a bootloader like that?
i first ran across it in win 8 and thought it was MS. but tried installing linux on my 3 miners with win 7 and it also blocked me. now i think it is the bootloader program.
Security setting in BIOS?
December 13, 2012, 12:51:49 PM
I'm saw the same thing today, simultaneous crash on all rigs upon Stratum detection of a new block.
Thought it was Windo'hs Update at first, but that's disabled on rigs that still crashed.
Putting half the farm on 2.9.6 and half on 2.9.7-1 until it's sorted.
Yeah I noticed the same. All of mine crashed at the same time upon detection of a new block.Thought it was Windo'hs Update at first, but that's disabled on rigs that still crashed.
Putting half the farm on 2.9.6 and half on 2.9.7-1 until it's sorted.
BTW, thanks ckolivas for the debugger. I'll be sure to give that a go in case any of my rigs crash again.
* ckolivas keeps wishing people would stop using the windows version knowing he may as well wish the sky weren't blue.
i first ran across it in win 8 and thought it was MS. but tried installing linux on my 3 miners with win 7 and it also blocked me. now i think it is the bootloader program.
December 13, 2012, 12:18:22 PM
I'm saw the same thing today, simultaneous crash on all rigs upon Stratum detection of a new block.
Thought it was Windo'hs Update at first, but that's disabled on rigs that still crashed.
Putting half the farm on 2.9.6 and half on 2.9.7-1 until it's sorted.
Yeah I noticed the same. All of mine crashed at the same time upon detection of a new block.Thought it was Windo'hs Update at first, but that's disabled on rigs that still crashed.
Putting half the farm on 2.9.6 and half on 2.9.7-1 until it's sorted.
BTW, thanks ckolivas for the debugger. I'll be sure to give that a go in case any of my rigs crash again.
* ckolivas keeps wishing people would stop using the windows version knowing he may as well wish the sky weren't blue.
December 13, 2012, 11:56:48 AM
It would appear that the latest version of cgminer still has no provision for mining different devices as different usernames and I need to run multiple copies of cgminer to accomplish this. Is this understanding accurate?
You could use the balance setting to evening send shares to all pools in your list.
Actually, my interest is to have the pool tell me when one of my miners is not producing.
Currently (unless I run 2 instances of cgminer) when one of my devices stops, I get no notification.
But thanks for the suggestion
December 13, 2012, 11:48:36 AM
I'd report a bug, and in the meantime use the version that works.
December 13, 2012, 11:33:00 AM
I'm saw the same thing today, simultaneous crash on all rigs upon Stratum detection of a new block.
Thought it was Windo'hs Update at first, but that's disabled on rigs that still crashed.
Putting half the farm on 2.9.6 and half on 2.9.7-1 until it's sorted.
Thought it was Windo'hs Update at first, but that's disabled on rigs that still crashed.
Putting half the farm on 2.9.6 and half on 2.9.7-1 until it's sorted.
Yeah I noticed the same. All of mine crashed at the same time upon detection of a new block.
BTW, thanks ckolivas for the debugger. I'll be sure to give that a go in case any of my rigs crash again.
* ckolivas keeps wishing people would stop using the windows version knowing he may as well wish the sky weren't blue.
except that, guess what? my bootloader locks me out of installing linux!
Jump to: