OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[kano]

Never mind

# ./cgminer -D -T --verbose
 [2013-05-31 15:02:15] Started cgminer 3.2.0
 [2013-05-31 15:02:15] All devices disabled, cannot mine!
#

That means you didn't compile in any USB devices ...

[1714228482]

1714228482

[1714228482]

1714228482

[1714228482]

1714228482

[1714228482]

1714228482

[fydel]

pastebin (don't paste here) the output of the end of 'dmesg' when you plug the AMU in
also 2 cgminer outputs:
1) cgminer -n
2) cgminer -D -T -verbose ... your options ... 2> debug.log
and let that run for about 30 seconds - and pastebin it or upload the log somewhere

I don't have a powered hub, I guess I better get one to see what's happening myself
(tried to get one last week and oddly none of the shops I went to had one ... except one that was crap)

One other thing to try is to leave it unplugged for about a minute then see if that fixes it
I had mine go into a weird state not being recognised after using different OSs and being left unplugged for a while fixed it for me
The error I got when this happened in the debug log was an error 4 setting the baud
I might try see if that is reproduceable - the error and the unplug fix, and if so, when it happens print a message to do that.

Here you go: http://pastebin.com/tRWSfvNV

I hope it helps. I would be happy to provide more info, if needed.

Leaving it unplugged for a minute had no effect.

[Xian01]

Having issues getting 3.2.0 working with Zadig/WinUSB on Windows 7 64 bit. Uninstalled the SiLabs driver, installed the WinUSB driver from Zadig, and all my devices show up under the "Universal Serial Bus devices" as "CP2101 USB to UART Bridge Controller" and not in "Ports (COM & LPT)" as COM devices

 Will try more later tonight.

[ewitte]

That means you didn't compile in any USB devices ...

I don't have any usb devices   Not for another 2-3 months.

[Dunkelheit667]

pastebin (don't paste here) the output of the end of 'dmesg' when you plug the AMU in
also 2 cgminer outputs:
1) cgminer -n
2) cgminer -D -T -verbose ... your options ... 2> debug.log
and let that run for about 30 seconds - and pastebin it or upload the log somewhere

I don't have a powered hub, I guess I better get one to see what's happening myself
(tried to get one last week and oddly none of the shops I went to had one ... except one that was crap)

One other thing to try is to leave it unplugged for about a minute then see if that fixes it
I had mine go into a weird state not being recognised after using different OSs and being left unplugged for a while fixed it for me
The error I got when this happened in the debug log was an error 4 setting the baud
I might try see if that is reproduceable - the error and the unplug fix, and if so, when it happens print a message to do that.

Here you go: http://pastebin.com/tRWSfvNV

I hope it helps. I would be happy to provide more info, if needed.

Leaving it unplugged for a minute had no effect.

Thank you kano and fydel!

Some additional data: http://pastebin.com/2W2wte3z Note: rpi -> usb hub -> 1 AMU

Regarding the hub: just connected a single AMU directly to the rpi (usb hub disconnected, rpi power cycled) and have had the same issue. Guess the powered usb hub is not the cause.

[kano]

pastebin (don't paste here) the output of the end of 'dmesg' when you plug the AMU in
also 2 cgminer outputs:
1) cgminer -n
2) cgminer -D -T -verbose ... your options ... 2> debug.log
and let that run for about 30 seconds - and pastebin it or upload the log somewhere

I don't have a powered hub, I guess I better get one to see what's happening myself
(tried to get one last week and oddly none of the shops I went to had one ... except one that was crap)

One other thing to try is to leave it unplugged for about a minute then see if that fixes it
I had mine go into a weird state not being recognised after using different OSs and being left unplugged for a while fixed it for me
The error I got when this happened in the debug log was an error 4 setting the baud
I might try see if that is reproduceable - the error and the unplug fix, and if so, when it happens print a message to do that.

Here you go: http://pastebin.com/tRWSfvNV

I hope it helps. I would be happy to provide more info, if needed.

Leaving it unplugged for a minute had no effect.

Hmm yep you are getting the same error in there that I have got twice (once on windows and once on linux)
and I managed to clear it somehow ...

Code:

 [2013-05-31 22:13:28] AMU: cgid 0 SetBaud got err 4

Now to work out how I cleared it ...

[kano]

pastebin (don't paste here) the output of the end of 'dmesg' when you plug the AMU in
also 2 cgminer outputs:
1) cgminer -n
2) cgminer -D -T -verbose ... your options ... 2> debug.log
and let that run for about 30 seconds - and pastebin it or upload the log somewhere

I don't have a powered hub, I guess I better get one to see what's happening myself
(tried to get one last week and oddly none of the shops I went to had one ... except one that was crap)

One other thing to try is to leave it unplugged for about a minute then see if that fixes it
I had mine go into a weird state not being recognised after using different OSs and being left unplugged for a while fixed it for me
The error I got when this happened in the debug log was an error 4 setting the baud
I might try see if that is reproduceable - the error and the unplug fix, and if so, when it happens print a message to do that.

Here you go: http://pastebin.com/tRWSfvNV

I hope it helps. I would be happy to provide more info, if needed.

Leaving it unplugged for a minute had no effect.

Thank you kano and fydel!

Some additional data: http://pastebin.com/2W2wte3z Note: rpi -> usb hub -> 1 AMU

Regarding the hub: just connected a single AMU directly to the rpi (usb hub disconnected, rpi power cycled) and have had the same issue. Guess the powered usb hub is not the cause.

Same eror there also

Code:

 [2013-05-31 22:26:51] AMU: cgid 0 SetBaud got err 4

Yep trying to sort out what causes it (and what fixes it) ...

[ewitte]

ok better

# ./cgminer --benchmark
 cgminer version 3.2.0 - Started: [2013-05-31 16:33:39]
--------------------------------------------------------------------------------
 (5s):0.000 (avg):0.000h/s | A:0  R:0  HW:0  U:0.0/m  WU:0.0/m
 ST: 2  SS: 0  NB: 0  LW: 0  GF: 1  RF: 0
 Connected to (null) diff 0 without LP as user Benchmark
 Block: (null)...  Diff:  Started:   Best share: 0
--------------------------------------------------------------------------------
 [P]ool management ettings [D]isplay options [Q]uit
--------------------------------------------------------------------------------

 [2013-05-31 16:33:39] Started cgminer 3.2.0
 [2013-05-31 16:33:39] No devices detected!
 [2013-05-31 16:33:39] Waiting for USB hotplug devices or press q to quit
 [2013-05-31 16:33:39] Pool 0 not providing work fast enough

[Littleshop]

I am getting crashed with signal 11 on startup on multiple versions of cgminer on one machine.  What did I do wrong.  A search here only leads to bad memory but machine has good memory.

[-ck]

Something I noticed that last version didn't do.

This version is frequently changing difficulty. Is this suppose to happen? Scrypt mining for litecoin.

Code:

Pool 0 difficulty changed to

 Accepted f3c31b0a Diff 208/128 GPU 0
 Pool 0 difficulty changed to 64.000000
 Accepted 81bdd518 Diff 157/128 GPU 1
 Accepted f732d5b3 Diff 67/64 GPU 1

cgminer's just reporting what your pool is doing. If it changes difficulty often it's not a very stable algorithm they're using to determine your dynamic difficulty. It's harmless, just noisy.

[bitpop]

P2pool changes every few seconds

[gyverlb]

P2pool changes every few seconds

Yes, but it's quite stable: it only changes noticeably when you add/remove hashrate.

Avoiding making tiny difficulty adjustment when hashrate is stable wouldn't hurt though.

[kano]

I'm getting errors in os x 10.8.3. Any ideas how to fix it?

./configure --enable-scrypt --enable-icarus PKG_CONFIG_PATH=/usr/local/opt/curl/lib/pkgconfig CFLAGS="-g -O2 -Wall"
sudo make install

"
<..>
usbutils.c:2576: error: redefinition of ‘union semun’
usbutils.c: In function ‘resource_unlock’:
usbutils.c:2878: warning: implicit declaration of function ‘semtimedop’
make[1]: *** [cgminer-usbutils.o] Error 1
make: *** [install-recursive] Error 1
"
Thank you!

Oh, yeah we fixed that in IRC about an hour ago and I pushed it to the master branch
I've seen it before, but no one has stayed around in IRC to help me fix it (I don't have OSX)
Thanks to NetRaider in IRC for helping with this.
https://github.com/ckolivas/cgminer/commit/8c1366113c22ea4e8a5340c154c6328bbf6dfee8

[Fallout]

Have you seen this? Possible optimization of the scrypt kernel

https://forum.litecoin.net/index.php/topic,4082.0/topicseen.html

[mdude77]

I'm not able to get 3.2.0 to work with my USB block erupters either.  It never finds the device.  Like others that have reported the problem, I'm using a USB 3.0 hub.  It's the only one I could find that could reliable power 7 devices.

M

EDIT: And it was a hassle getting it to work again with 3.1.1.  Reinstalling the USB to COM drivers didn't fix it, as it put them on the next 7 ports (according to device manager), and cgminer couldn't see them there.  On a hunch I manually changed them back to the right ports (3 - 9), uninstalled and reinstalled the USB to COM drivers again, then everything started working again.

[-ck]

Have you seen this? Possible optimization of the scrypt kernel

https://forum.litecoin.net/index.php/topic,4082.0/topicseen.html

All those changes are of dubious utility and likely to lead to identical binary kernels being generated.

[-ck]

I'm not able to get 3.2.0 to work with my USB block erupters either.  It never finds the device.  Like others that have reported the problem, I'm using a USB 3.0 hub.  It's the only one I could find that could reliable power 7 devices.

M

EDIT: And it was a hassle getting it to work again with 3.1.1.  Reinstalling the USB to COM drivers didn't fix it, as it put them on the next 7 ports (according to device manager), and cgminer couldn't see them there.  On a hunch I manually changed them back to the right ports (3 - 9), uninstalled and reinstalled the USB to COM drivers again, then everything started working again.

Looks like we have a lot of work to do... for windows yet again. With heavy development, the unforeseen problems are likely to be ever present.

[PCMiner]

If you have stable GPU miners on on older versions (3.0.0 or 3.1.1 for example) is there any performance increase inherent to 3.2 that is worth the upgrade?  I see the majority of changes are for ASIC people.

[-ck]

If you have stable GPU miners on on older versions (3.0.0 or 3.1.1 for example) is there any performance increase inherent to 3.2 that is worth the upgrade?  I see the majority of changes are for ASIC people.

No. There are stratum changes which might help you if you have problems, but otherwise no.

[dermo]

Can't find the changelog