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

[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

[-ck]

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

The whole display thing was never meant for so many devices since it's from an era of GPU mining. I keep rewriting it over and over again yet windows just likes crashing if you get too fancy with pdcurses. I keep meaning to rewrite it to just delete all the windows and start new ones but too many other things to do all taking my attention...

[Xian01]

The whole display thing was never meant for so many devices since it's from an era of GPU mining. I keep rewriting it over and over again yet windows just likes crashing if you get too fancy with pdcurses. I keep meaning to rewrite it to just delete all the windows and start new ones but too many other things to do all taking my attention...

I haven't written any significant code in over 10 years. I think it's time to dust off my bike and oil up the chains... Have been looking for something to rip me away from DOTA2...

Cheers.

[kano]

The whole display thing was never meant for so many devices since it's from an era of GPU mining. I keep rewriting it over and over again yet windows just likes crashing if you get too fancy with pdcurses. I keep meaning to rewrite it to just delete all the windows and start new ones but too many other things to do all taking my attention...

I haven't written any significant code in over 10 years. I think it's time to dust off my bike and oil up the chains... Have been looking for something to rip me away from DOTA2...

Cheers.

When you look at the code, in windows I set it to always open one bigger than required at start so there is one spare spot for a hotplug
... in case you were wondering why it does that

[crazyates]

The whole display thing was never meant for so many devices since it's from an era of GPU mining. I keep rewriting it over and over again yet windows just likes crashing if you get too fancy with pdcurses. I keep meaning to rewrite it to just delete all the windows and start new ones but too many other things to do all taking my attention...

I haven't written any significant code in over 10 years. I think it's time to dust off my bike and oil up the chains... Have been looking for something to rip me away from DOTA2...

Cheers.

When you look at the code, in windows I set it to always open one bigger than required at start so there is one spare spot for a hotplug
... in case you were wondering why it does that

Actually I was wondering why it did that. Thanks!

For the redesign, could we have it simplified and condensed into a single device type per line? For example, say you've got 3 Little Singles, 4 Jalapenos, and 14 AMUs. Rather than 21 separate lines, could we have 3 lines, saying how many of each type, and then important stats: average temp, highest temp, lowest hashrate, average hashrate, total hashrate (for that device type), reject %, etc. Similar to how you can view detailed info about a GPU, can't you also get into a submenu option that gives detailed info for each device type, listing each separate device of that type in the format it is today? I don't know if that's too fancy to work properly, but it's just a thought about how to organize the mass of information a lil cleaner.

But who am I to tell you guys what to do. I'm not a coder, and I have great respect for your work.

Actually, now that I think about it, I haven't sent you guys a donation in a while. I should do that, since you've been very helpful.

[-ck]

That all sounds like a great idea and pretty much what I had in mind. However we're just too busy working on new (and old) drivers for now.

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

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

I tried both the new dll and exe and all 3 instances of erupters did start.  But I had erupters falling off and coming back up continuously.  Ozco is bouncing up and down and it seems to keep trying bring it back up.  I went back to stock 3.3.1 and it failed over to a backup pool and is running stable again.

Also I noticed that the U: went away.  I like contrasting the U: and WU: with the variable difficulty to make sure they are in line.  I wouldn't like it if U: went away.  It doesn't seem that it would make a difference in window realestate.
Sam