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

[mdude77]

I ran into a problem with the USB block erupters.  They work great under 3.4.2 on my main PC, plugged straight into my USB 3.0 ports.  They work great on one of my rigs, plugged into multiple USB 3.0/2.0 hubs.  No configuration, just the WinUSB driver and it "just works".

Not so on my laptop.   3.4.2 (and 3.4.3) do not find the miners.  WinUSB is installed.  It looks the same in device manager on my laptop as it does my PC.  But cgminer doesn't see them.

I'm going to try updating my drivers on the laptop.  They should be up to date, but I'm going to check anyhow.

Any ideas?

M

[1714011293]

1714011293

[1714011293]

1714011293

[1714011293]

1714011293

[1714011293]

1714011293

[Zanatos666]

I ran into a problem with the USB block erupters.  They work great under 3.4.2 on my main PC, plugged straight into my USB 3.0 ports.  They work great on one of my rigs, plugged into multiple USB 3.0/2.0 hubs.  No configuration, just the WinUSB driver and it "just works".

Not so on my laptop.   3.4.2 (and 3.4.3) do not find the miners.  WinUSB is installed.  It looks the same in device manager on my laptop as it does my PC.  But cgminer doesn't see them.

I'm going to try updating my drivers on the laptop.  They should be up to date, but I'm going to check anyhow.

Any ideas?

M

Plugging them directly into the laptop?  If so, probably the reason they arent running.  Laptop ports are notoriously under powered.

[os2sam]

Not so on my laptop.  3.4.2 (and 3.4.3) do not find the miners.  WinUSB is installed.  It looks the same in device manager on my laptop as it does my PC.

What OS is on your laptop?

[mdude77]

Not so on my laptop.  3.4.2 (and 3.4.3) do not find the miners.  WinUSB is installed.  It looks the same in device manager on my laptop as it does my PC.

What OS is on your laptop?

Win7 x64, just like the PCs.

I could see them being underpowered.  But cgminer doesn't see them.  It's not like it sees them and they don't work, it's like they aren't there.

M

[KyrosKrane]

Win7 x64, just like the PCs.

I could see them being underpowered.  But cgminer doesn't see them.  It's not like it sees them and they don't work, it's like they aren't there.

M

I had the same issue. By any chance, is it a very recent PC, with a Z87 chipset? In my case, the conclusion was that my particular chipset or USB port wasn't supported by the libusb that cgminer uses. Windows was seeing the BE fine and loading the right drivers, but they still appeared invisible to cgminer. Ultimately I had to find a different platform to mine on.

[The00Dustin]

Win7 x64, just like the PCs.

I could see them being underpowered.  But cgminer doesn't see them.  It's not like it sees them and they don't work, it's like they aren't there.

M

I had the same issue. By any chance, is it a very recent PC, with a Z87 chipset? In my case, the conclusion was that my particular chipset or USB port wasn't supported by the libusb that cgminer uses. Windows was seeing the BE fine and loading the right drivers, but they still appeared invisible to cgminer. Ultimately I had to find a different platform to mine on.

That's some useful information that the developers can hopefully consider in some future build.  However, if that isn't the case, I think we need to know whether or not there is any indication that the device is visible in the OS and/or powered on since, as a general rule of thumb, I would expect underpowered ports to not power on devices that require more power than is available.  Sure, there may be some mining devices could see enough power to come on, but not enough to mine without errors.  I don't know whether or not there are, but even if there are, I would expect that to be an edge case, not something typical of underpowered USB ports (unless all underpowered USB ports provide the exact same less-than-spec amount of power for some mystical reason [or they are powered to spec and "underpowered" actually means "not overpowered"]).

[mdude77]

Win7 x64, just like the PCs.

I could see them being underpowered.  But cgminer doesn't see them.  It's not like it sees them and they don't work, it's like they aren't there.

M

I had the same issue. By any chance, is it a very recent PC, with a Z87 chipset? In my case, the conclusion was that my particular chipset or USB port wasn't supported by the libusb that cgminer uses. Windows was seeing the BE fine and loading the right drivers, but they still appeared invisible to cgminer. Ultimately I had to find a different platform to mine on.

That's some useful information that the developers can hopefully consider in some future build.  However, if that isn't the case, I think we need to know whether or not there is any indication that the device is visible in the OS and/or powered on since, as a general rule of thumb, I would expect underpowered ports to not power on devices that require more power than is available.  Sure, there may be some mining devices could see enough power to come on, but not enough to mine without errors.  I don't know whether or not there are, but even if there are, I would expect that to be an edge case, not something typical of underpowered USB ports (unless all underpowered USB ports provide the exact same less-than-spec amount of power for some mystical reason [or they are powered to spec and "underpowered" actually means "not overpowered"]).

It's a fairly recent laptop.  It has a 3rd gen i7 processor in it.  Device manager is showing the "Intel 7 series C216 chipset".

Windows knows about the USB device.  It installed the drivers just fine (via Zadig).  It shows in device manager.  But cgminer is none the wiser.

M

[The00Dustin]

New chipsets take time to be supported in *nix (and presumably libusb originates in *nix, translating to Windows).  It's unfortunate, but a reality.  That having been said, the easiest way to confirm a problem is a chipset vs libusb problem would be to try to run the cgminer binaries off of a live distro (presumably the same OS & version in use by the developers).  If cgminer doesn't detect the device there, it's definietly due to the version of libusb included with cgminer.  Also unfortunate, many other libusb versions cause mining problems as seen earlier in this thread, so even if the developer's OS of choice can detect the device on your machine, that doesn't mean cgminer can use it and be stable.  Presumably you would have to hack and compile on your own to be able to have cgminer use a newer libusb whilst not being stable.  Beyond that, all you can do in this scenario is hope that a future version of libusb comes out that is stable for mining, which also requires hoping the developers are trying new libusb versions.  However, the live distro test would at least allow you to know that so you don't waste additional time troubleshooting.

[mdude77]

New chipsets take time to be supported in *nix (and presumably libusb originates in *nix, translating to Windows).  It's unfortunate, but a reality.  That having been said, the easiest way to confirm a problem is a chipset vs libusb problem would be to try to run the cgminer binaries off of a live distro (presumably the same OS & version in use by the developers).  If cgminer doesn't detect the device there, it's definietly due to the version of libusb included with cgminer.  Also unfortunate, many other libusb versions cause mining problems as seen earlier in this thread, so even if the developer's OS of choice can detect the device on your machine, that doesn't mean cgminer can use it and be stable.  Presumably you would have to hack and compile on your own to be able to have cgminer use a newer libusb whilst not being stable.  Beyond that, all you can do in this scenario is hope that a future version of libusb comes out that is stable for mining, which also requires hoping the developers are trying new libusb versions.  However, the live distro test would at least allow you to know that so you don't waste additional time troubleshooting.

Linux and I don't mix well.  Last time I tried it, one of us had to go, and you see who's still here.

I intend to try 3.1.1 which uses COM drivers and see if I can get it working that way.

M

[KyrosKrane]

Was 3.1.1 the last version to support COM functionality?

Oh, and side note: mdude, your sig is out of date.

[The00Dustin]

I intend to try 3.1.1 which uses COM drivers and see if I can get it working that way.

Hopefully that works.  While it doesn't prove that the issue is compatibility between your chipset and libusb, it is an easier way to narrow things down significantly and a potential workaround at the same time.

[Karin]

Unofficial Mac binaries updated to 3.4.3 at http://spaceman.ca/cgminer.

[mdude77]

Was 3.1.1 the last version to support COM functionality?

Oh, and side note: mdude, your sig is out of date.

I think 3.1.1 was the last version to use COM.  I was using it on my mining rigs until very recently.

Thanks for the reminder on my sig, I fixed it.  One neat thing about sigs here is it always shows your current one.

M

[vulgartrendkill]

when using Zadig, do you select the winusb driver or one of the others?

[DrGuns4Hands]

Just compiled from the git running good so far no issues no zombies. I did notice during the configure step that a line popped up showing

./configure: line 11925: -pthread: command not found

seems to be working without it ,but what would i need to get to fix this part.

Raspberry Pi Raspbian Wheezy 7.

[-ck]

Just compiled from the git running good so far no issues no zombies. I did notice during the configure step that a line popped up showing

./configure: line 11925: -pthread: command not found

seems to be working without it ,but what would i need to get to fix this part.

Raspberry Pi Raspbian Wheezy 7.

Nothing, it's a normal part of the libusb check.

[kano]

when using Zadig, do you select the winusb driver or one of the others?

As the screen error message says ... and the README, FPGA-README and ASIC-README says - the WinUSB driver

[The Mafia]

After having a similar issue (moving from 3.1.1 to 3.4.0) and cigminer not seeing devices, I formatted and reinstalled windows and installed the winusb driver only and the devices detected again.

[vulgartrendkill]

when using Zadig, do you select the winusb driver or one of the others?

As the screen error message says ... and the README, FPGA-README and ASIC-README says - the WinUSB driver

Ok, thanks kano, I have done this and still after 30 mins or so 2 of my erupters turn into zombies.  Does this mean that the driver needs to be installed on all the erupters or do I just do it once?

[martinm]

Hello ck,
Hello Kano,

I've a question related to the identification of a device in cgminer and the a hardware device. As I'm currently about to develop a application that creates statistics for every device, it's essential to have a clear mapping between hardware device and the related device in cgminer for that. Previously I thought that the combination of the Device Type (GPU/BAS/AVA/....) and ID provided from cgminer could achieve that task, I had the hope it works as long the devices are connected to the same Port(USB/PCE...). Unfortunately I discovered that's not right. During the run of CGMiner I unplugged an Avalon from the USBPort and reconnected after a short time. After the reconnect the Id changed from AVA0 to AVA1. Now I'm questioning myself, how I can achieve the unique identification of a hardware device by reported data from CGMiner. I hope you can give me some advice!

Thany you very much in advance