Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 163. (Read 5805527 times)

I see   . I was dreaming for nanofury to work on Pi with cgminer

Since the topic of other drivers is coming up more and more often, let me clarify/reiterate the situation regarding mainline cgminer driver support and new devices. If a regular contributor was to come along and prove themselves by extensive repeated quality code contribution to cgminer, I would be happy to include them amongst the official devs for cgminer and add them to the people with git push access to cgminer which currently numbers only the two of us.

If Kano and/or I have been offered new hardware, or offered support to develop drivers for hardware, we will develop and include the code in cgminer and actively maintain and develop it. With various manufacturers we have been engaged on this level at wildly different stages in development. Some very early in hardware development (like cointerra and hashfast), some just before distribution of the product (like BFLSC and bi*fury devices), some after the fact when manufacturer code and hardware has been out for a while (like kncminer and much later for avalon). These examples by no means include everyone. Our involvement in the driver has been proportional to the duration of our involvement.

If someone wishes to develop their own driver and are happy to maintain it for cgminer, they are welcome to submit a pull request for their code to the cgminer git tree - Note that it will not be instantly accepted but usually it's simply a matter of making their code consistent with cgminer and Kano and/or I will provide comments about what changes need to be made for the code to be included. While I can keep the code building satisfactorily with changes to cgminer, the onus will then fall upon the person who pushed the original code to maintain it and keep it up to date since neither Kano nor I can test changes to the driver without actually having the hardware ourselves. If down the track the original maintainer has not been keeping up to date with cgminer, and users report that the driver has stopped working, the original driver author will be contacted for fixes. If no fixes are forthcoming, the driver will then be removed from cgminer (this happened in the case of the ztex driver). With the very rapid pace of development of code in cgminer lately, this can happen all too easily. Historically this sort of code does not stand the test of time.

If there are drivers out there based on forked earlier cgminer code that we have never heard about, and the original author makes no attempt to get the code incorporated into cgminer, that code cannot be meaningfully incorporated into cgminer even if we're made aware of its existence for the same reason we cannot maintain code for hardware we don't have.

https://github.com/drillbitsystems/cgminer/releases/latest

That's a link to a forked version of 3.8.1 that Drillbit came up with, that might help to speed things up a bit.

Yes, the firmware parameters are not compatible so you'd either have to try changing settings and saving them (not sure if this is enough), or resetting settings to default and setting your machine up from scratch (including the whole network setup part).

I recently tried to flash my 2nd Gen 3-card Avalon with the latest CGMiner firmware, but after restarting the box it doesn't seem to start hashing. I finally just reverted back to the August firmware and restarted the box. Everything started hashing immediately again.

Did something change in the latest version that requires the configuration parameters to change or something? Perhaps is the November firmware not intended for the 2nd gen avalon?

Any pointers greatly appreciated!

They have been re-plugging very smoothly for the last few releases, but not so for these "cluster zombies" under 3.8.4 (one cluster of several zombies on each machine, at different times) - each seemed to need a hub replug, but with just the two samples I might not be reporting it precisely enough. No other anomalies for a while though, and no dynamic AMU reallocations since the clusters.

Thanks. Yes that's the typical windows fail I've been trying to work around: When there's some kind of usb communication lag it affects everything on the bus. To be clear, when you get zombies, do they eventually re-hotplug for you? They do not for JMC

Similar results here - 2 Win7 machines, each got zombies from time to time. In fact, each got a cluster of them at different times - haven't seen that behavior in a while. Both machines are fine with 3.8.4 at the moment.

 

I for one was not sorry to read this, and fully support your decision. TY for all you do, and for taking a stance.

Be nice.  It's free.  And it's still the best around. 

M

No problem. Just curious. Keep up the good work!

Each use:
--usb BAS:1

Haven't got one yet - I'll probably be visiting him soon
So I've no idea what's required to make them work.

Any chance of getting the Drillbit thumbs integrated? For some reason when I run 2 instances of cgminer, 1 for my BE's and 1 for DB thumbs, my laptop will crash. Not an issue with the laptop, it has been running for over a month with cgminer for the BE's and stratum proxy. 

Done

Help plz, if I have a laptop connected to several bfl asics, how do I open one window of cgminer for each?

ckolivas,

Would you please update KNC version of cgminer to 3.8.4.

Thank you

Happy to oblige as always.  Test ran for just under 2 hours before a zombie (AMU16) appeared.  Did the usual thing with debug, then stopped the test.

Logfile here:
  https://dl.dropboxusercontent.com/u/44240170/logfile-3.8.4.txt

README FAQ answers that.

I dont know if anyone reported this, but I left my computer on all night like i've been doing for weeks mining, then I woke up and I saw Malwaresbyte reporting cgminer-nogpu.exe as a trojan, specifically "Trojan.Bitminer". Im CPU mining with 3.7.2 so I was using cgminer.exe. Anyway, I disconnected and ran a complete scan, I detected Trojan.Winload on Winload-Loader-v2.2.1.zip which I guess is a false positive from Daz's Windows activator for Win7, and that's about it.
To be sure, I downloaded again http://ck.kolivas.org/apps/cgminer/3.7/cgminer-3.7.2-windows.7z scanned it and found again "Trojan.Bitminer" on cgminer-nogpu.exe.

Im asuming Malwarebytes has included that exe as a trojan because people has been installing it around to secretly mine with other people's computers. False positive?