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

[jjiimm_64]

OK,  so maybe I am missing somthing..  but all the rpc requests I see can either start or stop a gpu, get summary of gpu.  but how do you change the clocks? or change the pool??

Code:

The list of requests and replies are:

 Request       Reply Section  Details
 -------       -------------  -------
 version       VERSION        CGMiner=cgminer version
                              API=API version

 summary       SUMMARY        The status summary of the miner
                              e.g. Elapsed=NNN,Found Blocks=N,Getworks=N,...|

 pools         POOLS          The status of each pool
                              e.g. Pool=0,URL=http://pool.com:6311,Status=Alive,...|

 devs          DEVS           Each available CPU and GPU with their details
                              e.g. GPU=0,Accepted=NN,MHS av=NNN,...,Intensity=D|

 gpu|N         GPU            The details of a single GPU number N in the same
                              format and details as for DEVS

 cpu|N         CPU            The details of a single CPU number N in the same
                              format and details as for DEVS

 gpucount      GPUS           Count=N| <- the number of GPUs

 cpucount      CPUS           Count=N| <- the number of CPUs

 gpuenable|N   none           There is no reply section just the STATUS section
                              stating the results of the enable request

 gpudisable|N  none           There is no reply section just the STATUS section
                              stating the results of the disable request

 gpurestart|N  none           There is no reply section just the STATUS section
                              stating the results of the restart request

 quit          none           There is no status section but just a single "BYE|"
                              reply before cgminer quits

I see how to get pool info, but no command to change the pool, or change the fan, or change the clock.? what am i missing?

[1715177386]

1715177386

[Remember remember the 5th of November]

They are yet to be implemented!

[jjiimm_64]

Well, that explains why I couldn't figure it out

[kano]

Well, that explains why I couldn't figure it out

Ignoring the fact that I still haven't even got around to my pool/cgminer changes that I want to do ...
At the moment the issue of CPU code and the Luke-jr changes mean I wont be touching any code until those are decided
(except helping ckolivas remove the CPU code from api.c if/when he does the CPU code removal)
there's also a minor bug in the example code: api-example.c that messes up the JSON (works fine otherwise of course)
The +1 in the send() needs removing - that I'll fix later also.

[bitlane]

• 0.4% more shares with this bugfix
• Code refactor, mostly neutral, but some testers reported better performance and efficiency
• ButterFlyLabs BitForce FPGA support, requires above refactor (will be submitted as a pull request once that gets merged)

Thanks for doing this work. It will take me some time to review these patches as they're fairly large and I'm relatively low on cycles for anything more than a cursory glance at the moment.

Please do not allow Luke-Jr to become associated with CGMiner in any way. Frankly, he is nothing more than a stain on the community as a whole and if his past actions are any indication, you would be opening the door for him to create more havoc in the project than it is worth.

He has indicated that reverse engineering is lawful and an acceptable method of moving forward, so please take this into consideration when reviewing his patches and do everything you possibly can to MAKE THEM YOUR OWN so that his reputation doesn't leave any marks on this great project.

[kwaaak]

Let luke roam free, heathens.

[Diapolo]

• 0.4% more shares with this bugfix
• Code refactor, mostly neutral, but some testers reported better performance and efficiency
• ButterFlyLabs BitForce FPGA support, requires above refactor (will be submitted as a pull request once that gets merged)

Thanks for doing this work. It will take me some time to review these patches as they're fairly large and I'm relatively low on cycles for anything more than a cursory glance at the moment.

Please do not allow Luke-Jr to become associated with CGMiner in any way. Frankly, he is nothing more than a stain on the community as a whole and if his past actions are any indication, you would be opening the door for him to create more havoc in the project than it is worth.

He has indicated that reverse engineering is lawful and an acceptable method of moving forward, so please take this into consideration when reviewing his patches and do everything you possibly can to MAKE THEM YOUR OWN so that his reputation doesn't leave any marks on this great project.

Your avatar SUX, but hey I guess freedom of speech, right ?

Dia

[DeathAndTaxes]

He has indicated that reverse engineering is lawful and an acceptable method of moving forward, so please take this into consideration when reviewing his patches and do everything you possibly can to MAKE THEM YOUR OWN so that his reputation doesn't leave any marks on this great project.

Reverse engineering is lawful.  Granted that right has been severly (and IMHO wrongly) degraded by provisions in DMCA but there is nothing wrong with reverse engineering.

Often when products or protocols are abandoned the ONLY way forward to new sustainable code is via reverse engineering.  Linux simply wouldn't exist without reverse engineering.  Before companies began to support it most drivers were created from reverse engineering.

I left the person of your attack out of the quote and response because it is off-topic but I felt I couldn't leave this perception unchallenged.


Also in a GPL project there is no such thing as MAKE THEM YOUR OWN.  If you want your own fork that makes fart sounds everytime a block is found you can pull it right now.  The license gives you the right and that right can never be taken away.

[bitlane]

He has indicated that reverse engineering is lawful and an acceptable method of moving forward, so please take this into consideration when reviewing his patches and do everything you possibly can to MAKE THEM YOUR OWN so that his reputation doesn't leave any marks on this great project.

Reverse engineering is lawful.  Granted that right has been severly (and IMHO wrongly) degraded by provisions in DMCA but there is nothing wrong with reverse engineering.

Often when products or protocols are abandoned the ONLY way forward to new sustainable code is via reverse engineering.  Linux simply wouldn't exist without reverse engineering.  Before companies began to support it most drivers were created from reverse engineering.

I left the person of your attack out of the quote and response because it is off-topic but I felt I couldn't leave this perception unchallenged.


Also in a GPL project there is no such thing as MAKE THEM YOUR OWN.  If you want your own fork that makes fart sounds everytime a block is found you can pull it right now.  The license gives you the right and that right can never be taken away.

I should have clarified a bit.....so thank you for reminding me to post again.

YES, let him fork his own project and call it DOOSH-JR-MINER, but PLEASE do not allow any of his contributions to make into the master repository.

[DeathAndTaxes]

YES, let him fork his own project and call it DOOSH-JR-MINER, but PLEASE do not allow any of his contributions to make into the master repository.

Why.  I haven't tested them yet but the code looks useful.  The 0.4% improvement code is a rather mundane bug fix.  Should we intentionally keep a bug in cgminer because we don't like the author?  Does that make the community better somehow?

[rjk]

Although most of us do not agree with many of Luke's positions and actions, it is obvious from inspecting his code that he is a capable coder. If you wish to boycott anything that he has touched, then you can stop using Bitcoin - he has committed several fixes/improvements etc to it.

[kano]

Well actually it's up to ckolivas

Though I will say that Luke didn't bother to do the api.c changes in his FPGA pull ... that's slack.

[-ck]

I judge all code by the code's merit. If it's GPL compliant and good code, then even if it's from an axe murderer, I'll take it. I have thought about this long and hard in the past. Read Rusty's take on it:

http://rusty.ozlabs.org/?p=196

[joulesbeef]

people should be wary then, and other developers should double check his work in bitcoin if they already havent.
You cant have people with very suspect morals, writing code that deals with money. Anywhere else dealing with anything like bitcoin, he would have had to go through a background check and send his fingerprints to the fed. Most likely he would have failed said background check during the psychological profile.

[rjk]

people should be wary then, and other developers should double check his work in bitcoin if they already havent.
You cant have people with very suspect morals, writing code that deals with money. Anywhere else dealing with anything like bitcoin, he would have had to go through a background check and send his fingerprints to the fed. Most likely he would have failed said background check during the psychological profile.

dude what
If the code is verified and read through by other competent devleopers, it doesn't matter who wrote it initially. For all we know Satoshi himself could be some evil guy, but because the code is open source, it was verified many times over by other developers to be safe and working.

[DeathAndTaxes]

I judge all code by the code's merit. If it's GPL compliant and good code, then even if it's from an axe murderer, I'll take it. I have thought about this long and hard in the past. Read Rusty's take on it:

http://rusty.ozlabs.org/?p=196

Thanks for the link.

“If you didn’t run code written by assholes, your machine wouldn’t boot”

LOLZ!

[stevegee58]

You're assuming that people with questionable morals/ethics are obvious based on their behavior on message boards.

An aside:  this reminds me of the business with the Reiser file system in Linux, written by the convicted murderer Hans Reiser
Good stuff but not universally adopted partly due to the "ick factor" with the man himself.

[-ck]

You're assuming that people with questionable morals/ethics are obvious based on their behavior on message boards.

An aside:  this reminds me of the business with the Reiser file system in Linux, written by the convicted murderer Hans Reiser
Good stuff but not universally adopted partly due to the "ick factor" with the man himself.

The axe murderer comment was not coincidence, given the history of Hans and linux

In fact his code never got incorporated because it had too many problems. It had nothing to do with him being a murderer. Once he was convicted, though, all the people working on his project slowly all walked away one by one, thus leaving the code to rot.

[jjiimm_64]

Back to the RPC stuff:

being able to switch a pool, or change a gpu engine clock are really the only commands I need. I would gladly pay 5 btc if these two features made it to the trunk.

Jim

[kano]

Back to the RPC stuff:

being able to switch a pool, or change a gpu engine clock are really the only commands I need. I would gladly pay 5 btc if these two features made it to the trunk.

Jim

Well as I replied yesterday
https://bitcointalk.org/index.php?topic=28402.msg689228#msg689228

But yeah - state exactly what you want with those 2 commands and once the CPU changes happen I'll put those 2 on first priority (for 5 BTC