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

[os2sam]

If it works, what should I expect if I need to restart, will I have to do the one at a time thing every time?

You only need to run Zadig to install the WinUSB driver once.  On reboot they should come up to WinUSB every time.  If you need to use a different driver you can run Zadig again and select a different driver.

[pepto]

You only need to run Zadig to install the WinUSB driver once.  On reboot they should come up to WinUSB every time. If you need to use a different driver you can run Zadig again and select a different driver.

Holy Moly, I was good until now. What does it  mean 'if I need to select a different driver'? I have a choice?
I'm windows 7. I need WinUSB. Hopefully you're referring to drivers for linux et al.

[os2sam]

You only need to run Zadig to install the WinUSB driver once.  On reboot they should come up to WinUSB every time. If you need to use a different driver you can run Zadig again and select a different driver.

Holy Moly, I was good until now. What does it  mean 'if I need to select a different driver'? I have a choice?
I'm windows 7. I need WinUSB. Hopefully you're referring to drivers for linux et al.

Sorry!

All I was trying to say was *If* you wanted to use some other driver for *anything* you changed with Zadig you could always change it to something else.

You should never need to change the driver again.  As far as I know.

[mdude77]

mdude77 says "Zadig is needed for 3.1.1.  It will prevent 3.5.0 from working.  Depending on your hardware, you may be able to run 3.5.0 w/o zadig.  Some hardware just isn't recognized by cgminer (I'm about 50/50 with my hardware).

Also, I tried 3.5.0 briefly and ran into errors (didn't have a chance to look closer).  Using 3.4.2 or 3.4.3 right now w/o zadig."

Using without Zadig?
How can this be?

I'm sorry, I misstated.  I meant 3.1.1 needs the USB to UART driver in addition to Zadig (winUSB). 

M

[pepto]

3.1.1 needs the USB to UART driver in addition to Zadig (winUSB). 

You can't have both, even though I do. Each is resident but you have to choose one or the other.
From my view, If devices and printers shows com numbers for all be's, then you have silabs in charge.
If all be's are present with no com numbers, WinUSB is in charge.
Neither selection is working for me.

[mdude77]

3.1.1 needs the USB to UART driver in addition to Zadig (winUSB).  

You can't have both, even though I do. Each is resident but you have to choose one or the other.
From my view, If devices and printers shows com numbers for all be's, then you have silabs in charge.
If all be's are present with no com numbers, WinUSB is in charge.
Neither selection is working for me.

You *can* have both.  Both use WinUSB (put there by Zadig).  However 3.1.1 uses COM ports, so you need Silab to map that USB to a COM port.

For 3.4.3+, you don't want the Silabs there, as cgminer can theoretically use the WinUSB driver directly.

You are correct, if you see COM ports for each of your BEs, you need to be using 3.1.1.  If you see USB entries for BE, you need to be using 3.4.3+.

I've tried cgminer on 4 computers now, all with different motherboards.  Two 3.4.3 sees them just fine.  Two they do not.  One of those two I'm running 3.1.1 with Silabs, the 4th one I haven't tried.

M

[Wipeout2097]

May I suggest a donation mining option for cgminer?

[os2sam]

May I suggest a donation mining option for cgminer?

Because..., it was such a huge success the last time it was tried?

[-ck]

Re: Zadig

Most of the confusion stems from the fact people think of it as a driver when it is not.

Zadig is a tool to associate a driver with a device and it comes prepackaged with the WinUSB driver which is what cgminer uses with all USB devices.

[markm]

I have been running BLT and AMU devices on Fedora Core 17 using cgminer 3.2.0 but even a fresh clone of the github repo, which builds as 3.5.0, does not work for my AMU devices. It detects my BLTs but not the AMUs. I for now I have had to go back to using the old 3.2.0.

(I even tried bfgminer again, but a git pull of that to get its latest code results in one that wont' detect my BLTs as well as not detecting  my AMUs so for me bfgminer is still looking less useful than cgminer because at least the ancient 3.2.0 of cgminer will run my eruptors and lancelots.

I would like to be able to update though. Does anyone know why more-recent versions than 3.2.0 do not work?

-MarkM-

[-ck]

I have been running BLT and AMU devices on Fedora Core 17 using cgminer 3.2.0 but even a fresh clone of the github repo, which builds as 3.5.0, does not work for my AMU devices. It detects my BLTs but not the AMUs. I for now I have had to go back to using the old 3.2.0.

(I even tried bfgminer again, but a git pull of that to get its latest code results in one that wont' detect my BLTs as well as not detecting  my AMUs so for me bfgminer is still looking less useful than cgminer because at least the ancient 3.2.0 of cgminer will run my eruptors and lancelots.

I would like to be able to update though. Does anyone know why more-recent versions than 3.2.0 do not work?

-MarkM-

Bizarre. Nothing in the new code that shouldn't detect what the old code could. Check your permissions and udev rules file and that you built in full support since you're compiling it for yourself.

[markm]

Someone told me how to switch to the 3.5.1 branch since I had only been getting 3.5.0; the 3.5.1 works fine.

-MarkM-

[Taugeran]

Code:

[2013-10-12 23:39:07] USB scan devices: checking for ICA devices
 [2013-10-12 23:39:07] ICA looking for ICA 067b:2303 but found 10c4:ea60 instead
 [2013-10-12 23:39:07] ICA looking for and found AMU 10c4:ea60
 [2013-10-12 23:39:07] USB lock Icarus 20-9
 [2013-10-12 23:39:07] RES: Icarus (20:9) lock=1
 [2013-10-12 23:39:07] USB res lock Icarus 20-9
 [2013-10-12 23:39:07] RES: Icarus (20:9) lock ok=1
 [2013-10-12 23:39:07] USB init, claim ifinfo 0 interface 0 failed, err -3 - AMU device 20:9
 [2013-10-12 23:39:07] USB free AMU
 [2013-10-12 23:39:07] Icarus detect (20:9) failed to initialise (incorrect device?)
 [2013-10-12 23:39:07] USB unlock Icarus 20-9

what does this mean on a mac?

also getting:

Code:

[2013-10-12 23:34:49] USB scan devices: checking for BF1 devices
 [2013-10-12 23:34:49] BF1 looking for and found BF1 03eb:204b
 [2013-10-12 23:34:49] USB lock bitfury 20-7
 [2013-10-12 23:34:49] RES: bitfury (20:7) lock=1
 [2013-10-12 23:34:49] USB res lock bitfury 20-7
 [2013-10-12 23:34:49] RES: bitfury (20:7) lock ok=1
 [2013-10-12 23:34:49] USB init, claim ifinfo 0 interface 1 failed, err -3 - BF1 device 20:7-i1
 [2013-10-12 23:34:49] USB free BF1
 [2013-10-12 23:34:49] bitfury detect (20:7) failed to initialise (incorrect device?)
 [2013-10-12 23:34:49] USB unlock bitfury 20-7
 [2013-10-12 23:34:49] BF1 looking for BF1 03eb:204b but found 05ac:0252 instead
 [2013-10-12 23:34:49] RES: bitfury (20:7) lock=0
 [2013-10-12 23:34:49] BF1 looking for BF1 03eb:204b but found 0424:2513 instead
 [2013-10-12 23:34:49] USB res unlock bitfury 20-7

[-ck]

Someone told me how to switch to the 3.5.1 branch since I had only been getting 3.5.0; the 3.5.1 works fine.

-MarkM-

It still shouldn't have been a problem on the master branch... (which still reads 3.5.0 but is actually the branch under active development).

[-ck]

Code:

 [2013-10-12 23:39:07] USB init, claim ifinfo 0 interface 0 failed, err -3 - AMU device 20:9

what does this mean on a mac?

also getting:

Code:

[2013-10-12 23:34:49] USB init, claim ifinfo 0 interface 1 failed, err -3 - BF1 device 20:7-i1

I wish I knew. -3 is an access permissions problem, whatever the heck that means on osx.

[Taugeran]

Code:

 [2013-10-12 23:39:07] USB init, claim ifinfo 0 interface 0 failed, err -3 - AMU device 20:9

what does this mean on a mac?

also getting:

Code:

[2013-10-12 23:34:49] USB init, claim ifinfo 0 interface 1 failed, err -3 - BF1 device 20:7-i1

I wish I knew. -3 is an access permissions problem, whatever the heck that means on osx.

could it be due  to the kernel usb to serial drivers?

*dont hit me*

[Picmin]

Just built from git on my raspberry pi.
Version is listed as 3.5.0.

Downloaded one of your compiled versions for windows.
Version is 3.5.1.

Did I build from the wrong branch with git clone https://github.com/ckolivas/cgminer?

git clone https://github.com/ckolivas/cgminer --branch 3.5

Oh thanks !

Does the the master branch include someone42 pull requests? i have installed with git clone https://github.com/ckolivas/cgminer on minepeon and the '--bitburner-voltage' parameter doesn't work anymore.
Always set to max : 1100mv on a Bitburner Fury.

[Wipeout2097]

Let's try this again ...

May I suggest a donation mining option for cgminer?

Because..., it was such a huge success the last time it was tried?

[os2sam]

Let's try this again ...

May I suggest a donation mining option for cgminer?

Because..., it was such a huge success the last time it was tried?

My snarky remark wasn't wasn't meant to imply that I thought it was a bad idea.  And if they incorporated it into CGMiner again I would certainly use it.

But, if I remember correctly, it ended up increasing the development workload for ckolivas dramatically more than the revenue it brought in was worth plus it ticked off allot of people.

But maybe it would be a different story now with the increased value of bitcoin and the stratum protocol?

I just would hate to see ckolivas and kano's workload increase with little or no benefit.  But hey who knows.

[-ck]

Actually we've reached a time where almost no one is making a profit mining which won't pass for maybe another year. Is it really time that people would be interested in a donation option?