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

[Luke-Jr]

When I go above version 2.10.5 with my singles I just get the following. Both the newer versions seem to do it, never had any issues upgrading before.

you need to install the windows USB drivers.  read the FPGA-Readme.txt included in the cgminer folder.

driver is at http://sourceforge.net/projects/libwdi/files/zadig/

when you grab the driver, note that XP uses a different driver than vista/7.

Note that doing this will break all applications using the standard driver...

IIRC that driver was specific for the usb controller chip in BFL singles. which nothing else I have uses, and I sure have my share of usb crap.

so, who cares?

PS as always, feel free to correct me if Im wrong.

BFL doesn't have a special driver, it uses the standard FTDI driver installed automatically when you plug it in.

[1714292936]

1714292936

[1714292936]

1714292936

[1714292936]

1714292936

[1714292936]

1714292936

[1714292936]

1714292936

[kano]

When I go above version 2.10.5 with my singles I just get the following. Both the newer versions seem to do it, never had any issues upgrading before.

you need to install the windows USB drivers.  read the FPGA-Readme.txt included in the cgminer folder.

driver is at http://sourceforge.net/projects/libwdi/files/zadig/

when you grab the driver, note that XP uses a different driver than vista/7.

Note that doing this will break all applications using the standard driver...

No it will just break your piece of shit - go away.

[vapourminer]

you need to install the windows USB drivers.  read the FPGA-Readme.txt included in the cgminer folder.

driver is at http://sourceforge.net/projects/libwdi/files/zadig/

when you grab the driver, note that XP uses a different driver than vista/7.

Note that doing this will break all applications using the standard driver...

IIRC that driver was specific for the usb controller chip in BFL singles. which nothing else I have uses, and I sure have my share of usb crap.

so, who cares?

PS as always, feel free to correct me if Im wrong.

BFL doesn't have a special driver, it uses the standard FTDI driver installed automatically when you plug it in.

I dont remember it installing automatically, I needed to goto bfls driver page and follow the link for that driver. at least for my xp machine that the singles hanging off of.

[slush]

BFL doesn't have a special driver, it uses the standard FTDI driver installed automatically when you plug it in.

I dont remember it installing automatically, I needed to goto bfls driver page and follow the link for that driver. at least for my xp machine that the singles hanging off of.

I can confirm for Windows7, I had to install drivers for BFL as well.

[Luke-Jr]

Note that doing this will break all applications using the standard driver...

BFL doesn't have a special driver, it uses the standard FTDI driver installed automatically when you plug it in.

actually the FTDI drivers isnt a "standard" usb driver, which is why it needs to be installed for many, if not most windows users.

from their driver page (the one BFL links to): http://www.ftdichip.com/Drivers/VCP.htm

Virtual COM port (VCP) drivers cause the USB device to appear as an additional COM port available to the PC.  Application software can access the USB device in the same way as it would access a standard COM port.

if anything, seems that driver would break stuff, as it treats the that specific usb chip as serial device, not usb device. if anything else used that chip in a standard usb way, it would break.

It is a serial device. Windows is supposed to automatically install it from Windows Update when you plug it in - why that didn't work for you, I don't know.

[vapourminer]

It is a serial device. Windows is supposed to automatically install it from Windows Update when you plug it in - why that didn't work for you, I don't know.

seems Im not the only one it doesnt install automatically for but anyway..

youre right it is a serial device. actually I had deleted that post once I read further but you replied to it before I deleted it.

as I mentioned the zadig driver can be installed along side the FTDI driver so I cant see the problem using it.

[-ck]

Be wary of FUD 

[nitrox]

Be wary of FUD 

what is "FUD" ?

[mdude77]

Be wary of FUD 

what is "FUD" ?

https://en.wikipedia.org/wiki/Fear,_uncertainty_and_doubt

M

[kano]

Be wary of FUD  

what is "FUD" ?

https://bitcointalk.org/index.php?action=profile;u=3318

Edit: well ... that at least gives the summary ...

[nitrox]

thanks 

[n4l3hp]

Using XP, I had to download and install manually the FTDI driver. With Win7, after plugging the single in, windows prompted to search the driver over the internet (windows update) and all I had to do was click "NEXT" button.

[kano]

I have a system that utilizes both gpus and fpgas and I want to run one cgminer instance for gpus and another for fpgas.  Starting in 2.11.0 with the new usb subsystem, I am unable to start an instance of cgminer for just the gpus.  Whenever I try to start the instance for gpus only, cgminer displays "MTX: BitForce USB failed to get cgminer-usb..." and exits.  Is there any way to disable the usb detection like how "-S noauto" used to work?

--hotplug 0

tried that and still had the same problem

Update
I've put the code in a pull for USB device selection:
https://github.com/ckolivas/cgminer/pull/403

This is v0.1 ... and as per the README changes:

Code:

Cgminer will automatically find all of your BFL ASIC, BitForce FPGAs,
ModMiner FPGAs or Ztex FPGAs
The --usb option can restrict how many BFL ASIC, BitForce FPGAs or
ModMiner FPGAs it finds:

  --usb 1:2,1:3,1:4,1:*
or
  --usb BAS:1,BFL:1,MMQ:0
or
  --usb :10

You can only use one of the above 3

The first version
  --usb 1:2,1:3,1:4,1:*
allows you to select which devices to mine on with a list of USB
 bus_number:device_address
All other USB devices will be ignored
Hotplug will also only look at the devices matching the list specified and
find nothing new if they are all in use
You can specify just the USB bus_number to find all devices like 1:*
which means any devices on USB bus_number 1
This is useful if you unplug a device then plug it back in the same port,
it usually reappears with the same bus_number but a different device_address

You can see the list of USB devices on linux with 'sudo lsusb'
Cgminer will list the USB devices with the '--usb-dump 0' option
The '--usb-dump N' option with a value of N greater than 0 will dump a lot
of details about each USB device

The second version
  --usb BAS:1,BFL:1,MMQ:0
allows you to specify how many devices to choose based on each device
driver cgminer has - there are currently 3 USB drivers: BAS, BFL & MMQ
N.B. you can only specify which device driver to limit, not the type of
each device, e.g. with BAS:n you can limit how many BFL ASIC devices will
be checked, but you cannot limit the number of each type of BFL ASIC
Also note that the MMQ count is the number of MMQ backplanes you have
not the number of MMQ FPGAs

The third version
  --usb :10
means only use a maximum of 10 devices of any supported USB devices
Once cgminer has 10 devices it will not configure any more and hotplug will
not scan for any more
If one of the 10 devices stops working, hotplug - if enabled, as is default
- will scan normally again until it has 10 devices

Edit: oh and in case it wasn't obvious ... to optimally not use any USB devices you'd use --usb :0 --hotplug 0

This of course has no affect on the Icarus driver since it is (still) serial-USB not direct USB

[TechCF]

CGminer now crashes every time i start it, witrh 2.11.2 

The 2 usual reasons for this are: Mixed versions of different driver files installed, and virus software interfering.

Thanks for the updates!

Regarding the crash upon start (with no correct .bin file) read: http://devgurus.amd.com/thread/160032

I had the same issue with a 6950 card on my clean windows (7/8) install with 13.1/2 drivers. Mismatched amdocl64.dll and opencl.dll in system32/syswow64 and the AMD APP\bin\x86/x64 folder is the trouble (need to use the AMD APP files).

Clean install with 12.8 works, or overwrite the windows files (take ownership,then change the file rights, then overwrite).

[-ck]

I am tentatively elevating the status of 2.11.2 to stable.

It is worth reminding people that on windows+fpgas you will need to install a winusb driver as it says in the fpga readme compared to running versions of cgminer <2.11 which used the old serial interface.

It is also worth mentioning that stability seems to be compromised when built with an older version of libcurl.

[PatMan]

Hi ckolivas,

While bitcoin was down I used the opportunity to upgrade my rigs to Xubuntu 12.04 LTS 64bit. I noticed your binary is for 12.10 - is it OK to run on 12.04 do you know? Or will it give me stability issues? Cheers muchly.

[-ck]

Hi ckolivas,

While bitcoin was down I used the opportunity to upgrade my rigs to Xubuntu 12.04 LTS 64bit. I noticed your binary is for 12.10 - is it OK to run on 12.04 do you know? Or will it give me stability issues? Cheers muchly.

It works on 12.04 as well. I can't attest to its stability as such though.

[juhakall]

I am tentatively elevating the status of 2.11.2 to stable.

It is worth reminding people that on windows+fpgas you will need to install a winusb driver as it says in the fpga readme compared to running versions of cgminer <2.11 which used the old serial interface.

It is also worth mentioning that stability seems to be compromised when built with an older version of libcurl.

What is the first safe version to use?

[-ck]

It's only a postulated cause for instability, but probably >=7.25 which have the keepalive features.

[RedLine888]

Hi guys! Please help me with my problem. The matter is that I run 2.11.2 CGminer as always (.bin files are deleted for miner to autodetect best config) then the cmd window appears and Error: The program has stopped working.

With old .bin files it works. W8x84, Catalyst 13.2 b7 with built-in SDK

Thanx