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

[af_newbie]

It's been less than 18 hours since your first post.  I'm sorry our FREE TECH SUPPORT was not quick enough for you.

It wouldn't be free if it would be TECH SUPPORT(ok it would be but you would get a donation as I stetted)... 2 times I needed help and the bug reported first time is still in cgminer... And that time when I was reporting it I was told it not a bug it is is you or your system(but it is not since I found workaround)... This time it was read readme that didn't work... Needed to do something that was not in README...

Don't get upset.  People here are generally helpful.

Some senior members here might treat you like a child because they wrote parts of cgminer and they know "everything" .

Don't take it personally.  Ignore posts that don't help you.

Do your own debugging.  Don't expect things to be spelled out for you.

[Xian01]

Does anyone else have issues using USB flash drives while running CGMiner?
I have a thread here where I tried Alot to fix my USB drivers, turns out that it appears CGMiner was causing them to hang/freeze
https://bitcointalk.org/index.php?topic=267980.0

 On a related note, I have an E-MU Tracker Pre USB that I'm using as my audio device and I notice that I get crackles from time-to-time when it's playing audio with CGMiner driving USB Erupters in the background.

[crazyates]

So for the most part, things seem to be pretty smooth with 3.3.1. I know I haven't had any problems. Any plans for the future of CGMiner, or should I try asking again when CK gets back from vacation?

[-ck]

I'm back and seriously jetlagged with 1000 emails and 500 snail mails to contend with first, but yes some fixes will make their way into a release soon.

[Dunkelheit667]

Does anyone else have issues using USB flash drives while running CGMiner?
I have a thread here where I tried Alot to fix my USB drivers, turns out that it appears CGMiner was causing them to hang/freeze
https://bitcointalk.org/index.php?topic=267980.0

 On a related note, I have an E-MU Tracker Pre USB that I'm using as my audio device and I notice that I get crackles from time-to-time when it's playing audio with CGMiner driving USB Erupters in the background.

In case you're using a mainboard with AMD chipset (from 2008 or 2009, not sure atm), try to find something called 'AMD USB Filter Driver' on the mainboard manufacturers support pages. There was an issue when using USB 1.1 devices causing 'noise' and communication issues. Patches are still available from HP, Lenovo etc. From my experience, these patches are working fine on other brands as well... Just an idea.

[Xian01]

In case you're using a mainboard with AMD chipset (from 2008 or 2009, not sure atm)

 In this case, it's not an AMD issue It's an i7 2600K system I put together on an MSI motherboard. I can live with it; just wanted to report the issue.

[crazyates]

In case you're using a mainboard with AMD chipset (from 2008 or 2009, not sure atm)

 In this case, it's not an AMD issue It's an i7 2600K system I put together on an MSI motherboard. I can live with it; just wanted to report the issue.

Well have you downloaded and run the newest Intel INF Update Utility for your motherboard? Intel MBs still need chipset drivers too, ya know.

[Xian01]

In case you're using a mainboard with AMD chipset (from 2008 or 2009, not sure atm)

In this case, it's not an AMD issue It's an i7 2600K system I put together on an MSI motherboard. I can live with it; just wanted to report the issue.

Well have you downloaded and run the newest Intel INF Update Utility for your motherboard? Intel MBs still need chipset drivers too, ya know.

 All up to date. Lose the snark.

[-ck]

For windows users who have been fighting with the AMUs on the latest version of cgminer, can you try just dropping in this dll in place of the existing one in your cgminer directory? (Or for that matter, anyone using the latest cgminer on windows, see if this changes anything for you). It's the latest version of libusb.

http://ck.kolivas.org/apps/cgminer/temp/libusb-1.0.dll

[-ck]

For windows users who have been fighting with the AMUs on the latest version of cgminer, can you try just dropping in this dll in place of the existing one in your cgminer directory? (Or for that matter, anyone using the latest cgminer on windows, see if this changes anything for you). It's the latest version of libusb.

http://ck.kolivas.org/apps/cgminer/temp/libusb-1.0.dll

And while I'm at it, there are new windows .exes with the latest changes as well in case changing the dll alone isn't enough:
http://ck.kolivas.org/apps/cgminer/temp

[Xian01]

And while I'm at it, there are new windows .exes with the latest changes as well in case changing the dll alone isn't enough:
http://ck.kolivas.org/apps/cgminer/temp

 She's alive ! Happily hashing away with your latest under Windows on an Anker 10 port hub !



EDIT: Additionally, deployed this build to another rig hosting 58 sticks, and sometimes, a few sticks lag at startup and the display never gets updated.

Eg: CGMiner starts up, and displays AMU0 through AMU51. About 30 seconds after it starts up, I see hotplug messages saying devices up to AMU57 have been found, but the display is not updated to reflect the new devices.



 Finally, I notice that bank often switches back and forth between difficulty 8 and 16. Is there a way I can tell CGMiner "Don't ever go higher than Difficulty 8" ?

EDIT2: On my first 10 port hub, I had AMU8 go ZOMBIE with the green light on solid, and would not respond to a hotplug operation. Had to quit and shutdown CGMiner to get it working again. Also, restarting that one 10 port hub only seems to recognize AMU0 through 5 before AMU6-8 get added to the list as hotplug devices later, and again, the list of devices does not get refreshed to display this

[bitcoindaddy]

What is the correct way to specify complex usb command line parameters in the CONFIG file? I have:

--icarus-options 115200:1:1 --icarus-timing 3.0=100 --usb 1:3,2:3,2:4,2:7,2:8,2:9

on the command line.

[crazyates]

New dll and new .exe. Should I be seeing anything different if I'm not using AMUs? Cuz my BFL LS is plenty happy.

[-ck]

New dll and new .exe. Should I be seeing anything different if I'm not using AMUs? Cuz my BFL LS is plenty happy.

Nope, all good. Thanks for feedback.

[-ck]

And while I'm at it, there are new windows .exes with the latest changes as well in case changing the dll alone isn't enough:
http://ck.kolivas.org/apps/cgminer/temp

 She's alive ! Happily hashing away with your latest under Windows on an Anker 10 port hub !


EDIT: Additionally, deployed this build to another rig hosting 58 sticks, and sometimes, a few sticks lag at startup and the display never gets updated.

Eg: CGMiner starts up, and displays AMU0 through AMU51. About 30 seconds after it starts up, I see hotplug messages saying devices up to AMU57 have been found, but the display is not updated to reflect the new devices.


 Finally, I notice that bank often switches back and forth between difficulty 8 and 16. Is there a way I can tell CGMiner "Don't ever go higher than Difficulty 8" ?

EDIT2: On my first 10 port hub, I had AMU8 go ZOMBIE with the green light on solid, and would not respond to a hotplug operation. Had to quit and shutdown CGMiner to get it working again. Also, restarting that one 10 port hub only seems to recognize AMU0 through 5 before AMU6-8 get added to the list as hotplug devices later, and again, the list of devices does not get refreshed to display this

Great thanks for feedback. Unfortunately normal for windows to fail to start every single one of them and occasionally hotplug the remainders due to some being slow to initialise. Normal for hotplugged ones to not show on windows also - a workaround for crashes on resizing windows thanks to buggy pdcurses on windows. Difficulty is set by your pool and cgminer has no control over it, use a pool with a more stable variable diff algorithm.

[os2sam]

(Or for that matter, anyone using the latest cgminer on windows, see if this changes anything for you). It's the latest version of libusb.

http://ck.kolivas.org/apps/cgminer/temp/libusb-1.0.dll

Yep, it changed something for me.

My third instance always crash's now.  I run three instances 5 erupters each.

[-ck]

(Or for that matter, anyone using the latest cgminer on windows, see if this changes anything for you). It's the latest version of libusb.

http://ck.kolivas.org/apps/cgminer/temp/libusb-1.0.dll

Yep, it changed something for me.

My third instance always crash's now.  I run three instances 5 erupters each.

Did you try the dll alone or with the new exe as well?

[os2sam]

(Or for that matter, anyone using the latest cgminer on windows, see if this changes anything for you). It's the latest version of libusb.

http://ck.kolivas.org/apps/cgminer/temp/libusb-1.0.dll

Yep, it changed something for me.

My third instance always crash's now.  I run three instances 5 erupters each.

Did you try the dll alone or with the new exe as well?

dll alone.

[-ck]

(Or for that matter, anyone using the latest cgminer on windows, see if this changes anything for you). It's the latest version of libusb.

http://ck.kolivas.org/apps/cgminer/temp/libusb-1.0.dll

Yep, it changed something for me.

My third instance always crash's now.  I run three instances 5 erupters each.

Did you try the dll alone or with the new exe as well?

dll alone.

Try both then please? Lots of little fixes post 3.3.1 in that exe (in fact close to what 3.3.2 will be, hopefully).

[Xian01]

Normal for hotplugged ones to not show on windows also - a workaround for crashes on resizing windows thanks to buggy pdcurses on windows.

 Could the display toggle coMpact mode be modified to reinit the displayed devices manually ? I noticed it did not