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

I don't follow; why is that a reason to prefer it? If there is something cgminer does that BFGMiner doesn't, that you find value in, I'd prefer to add it to BFGMiner.

I have been using it since I started mining. 

Why do you prefer cgminer?

Is there any support for the x6500 with cgminer?  I know bfgminer has it but I really prefer cgminer. 

Very likely to all be pulled into ckolivas' git, unless I've messed something up somewhere, it should go in when ckolivas gets back.
https://bitcointalksearch.org/topic/m.1427509
I have a pull request that everything moves into as I work on it while he is away, and I have a list of things I want to get done also.

One of the 2 main reasons behind the USB changes is the upcoming ASIC, coz I'm sure there will be problems with ASIC and serial-USB
the other reason is as I've said a few times in the past to a few people, serial-USB sux - direct USB - using libusb - is way better.
With direct USB the interface is almost as simple as serial-USB (once you understand it) but you optionally have more control over it if you want and you can access anything extra the device allows that serial-USB may not allow.

Once all devices are working through the same library (and working the same on both windows and linux) I was hoping ... as you are suggesting ... that there should be fewer problems.
Thanks for the feedback!

The only one left is Icarus, but I'm not sure when I'll get around to that (it's a different USB device pl2303 - and I'm not expecting any ASIC's to use that - so I'm in no rush to redo that code)
I'm running all my FPGAs on a single cgminer at the moment - 2xIcarus, 1xBFL and 1xMMQ and they are behaving well together.
It's summer here also - so a good test of handling heat problems.

Edit: there is one issue I know of, and that is when a device is lost (by libusb or disappears off the USB bus) that cgminer can crash after it gets a USB error -99 or -6 (which means the device has disappeared) coz it keeps talking to libusb and libusb doesn't like that (and crashes)
I'll add a way to deal with that properly soon - but it should be very rare to happen.

--

And if anyone was interested, in my master git (and the git pull to ckolivas) I've updated miner.php to optionally allow (very simple) password protection - the change is documented in the new API-README with it

Edit: my git: https://github.com/kanoi/cgminer/commits/master

Hi Kano,
I'd like to thank you, I tried your GIT version and it solved my problems with BFL and ZTEX devices connected to the same machine.
Under latest 2.10.4 and many previous versions I have seen many comm errors from BFL devices as well as errors with ZTEXes (when BFLs were removed no such errors appeared) leading to the seqfault in cgminer. I'm guessing the problem was solved by using libusb for BFL?
Currently it runs for 48 hours without any problem. Will be your branch merged completely to the cgminer?

As long as that includes you - I am indeed thankful.

You offered valuable information, pointing me towards solutions, while claiming authorship of the code in question. I simply came here to take you up on that help, where you are more active. How insulting YOU are for essentially inviting questions by posting in the other thread, yet you call me rude for asking them.

You, sir, are an asshole. I can see why members of this community refused to work with you.

Okay thanks

Derp okay I see I was looking at the memory speed. Sometimes you just need to tell you that you are an idiot to see the truth Just to confirm though, I am getting 677.9 Mh/s?

Your GPU's memory is set to 1375 MHz. Your hashrate is the ~675 MH/s.

theres nowhere 1375Mh/s in this screenshot, how did u come up with this...

Ask your miner support team - this thread is for cgminer.
I consider it an insult to post about using my software in another thread that simply copies it and claims it their own and then come here and ask me for support of it.

I have a question about what hash rate I am getting.

http://i.imgur.com/XHViv.png

Does this mean I am getting 1375Mh/s or 677.9Mh/s? Thanks in advance.

Thanks.  I did restart just after posting and it's still running ~10 hours later.  I'll report back ONLY if it fails again within a day or two.  (Sounds like it won't.)

kano: I understand you wrote the RPC API. The API-Readme is quite confusing, how is one to execute the commands listed? there are some example files referenced in the documentation, but they aren't supplied(api-example.php, etc). I think I understand how to format a command, but how to send that command to the software escapes me. I want to be able to use the pgaset command for my MMQ(I hate having it start at 200mhz when I know each chip will easily do 215. Starting at 210 each time would save a lot of waiting for it to clock up)

#define CL_OUT_OF_RESOURCES                         -5

Some driver and/or device problem and the new cgminer version was purely coincidental. Reboot, reinstall drivers etc...

Oops - I should not have removed that bit.  

It's right there in the screen scrape, its that "redacted" pool.