OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 227.

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: PulsarAV on September 11, 2013, 05:28:40 PM

How do I tell cgminer to ignore a specific USB device?
...

I haven't added any ignore rules into --usb yet that will work for that.
In your case you can't ignore the ICA driver either coz you have other ICA devices
ICA are: ICA, AMU, BLT, LLT and CMR

At the moment, to get it to ignore that one you would have to edit usbutils.c
A quick hack would be change the "ICA" find_dev to ignore it.
067b:2303 is the chip used in the original Icarus boards (I still have one)
So if you change say

Code:

  .idVendor = 0x067b,
  .idProduct = 0x2303,
  .kernel = 0,

to

Code:

  .idVendor = 0x067b,
  .idProduct = 0x2303,
  .iProduct = "Never Match Me",
  .kernel = 0,

it will never match any device with that chip in it.

By the way, the original Icarus has
iManufacturer 'Prolific Technology Inc. '
iProduct 'USB-Serial Controller D'

What does your device have?
You get that info with cgminer -n

PulsarAV

newbie

Activity: 12

Merit: 0

How do I tell cgminer to ignore a specific USB device?

cgminer is recognizing a non ASIC miner device and continually attempts to initialize it.

Here's what cgminer -n sees:

Code:

C:\Temp\cgminer-3.3.1-windows>cgminer.exe -n
 [2013-09-11 17:19:20] CL Platform 0 vendor: Advanced Micro Devices, Inc.
 [2013-09-11 17:19:20] CL Platform 0 name: AMD Accelerated Parallel Processing
 [2013-09-11 17:19:20] CL Platform 0 version: OpenCL 1.2 AMD-APP (1124.2)
 [2013-09-11 17:19:20] Platform 0 devices: 1
 [2013-09-11 17:19:20]  0       Capeverde
 [2013-09-11 17:19:20] GPU 0 AMD Radeon HD 7700 Series hardware monitoring enabled
 [2013-09-11 17:19:20] 1 GPU devices max detected
 [2013-09-11 17:19:21] USB all: found 23 devices - listing known devices
.USB dev 0: Bus 6 Device 1 ID: 067b:2303  <<<<<<<<<<<<<<<<<< This device is *NOT* a miner >>>>>>>>>>>
  ** dev 0: Failed to open, err -12
.USB dev 1: Bus 7 Device 2 ID: 10c4:ea60
  Manufacturer: 'Silicon Labs'
  Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 2: Bus 7 Device 3 ID: 10c4:ea60
  Manufacturer: 'Silicon Labs'
  Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 3: Bus 7 Device 4 ID: 10c4:ea60
  Manufacturer: 'Silicon Labs'
  Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 4: Bus 7 Device 6 ID: 10c4:ea60
  Manufacturer: 'Silicon Labs'
  Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 5: Bus 7 Device 7 ID: 10c4:ea60
  Manufacturer: 'Silicon Labs'
  Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 6: Bus 7 Device 8 ID: 10c4:ea60
  Manufacturer: 'Silicon Labs'
  Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 7: Bus 7 Device 10 ID: 10c4:ea60
  Manufacturer: 'Silicon Labs'
  Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 8: Bus 7 Device 11 ID: 10c4:ea60
  Manufacturer: 'Silicon Labs'
  Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 9: Bus 7 Device 12 ID: 10c4:ea60
  Manufacturer: 'Silicon Labs'
  Product: 'CP2102 USB to UART Bridge Controller'
 [2013-09-11 17:19:21] 10 known USB devices

Here's the output while running:

Code:

[2013-09-11 17:25:48] Started cgminer 3.3.1
[2013-09-11 17:25:48] USB init, open device failed, err -12, you need to install a WinUSB driver for - ICA device 6:1
[2013-09-11 17:25:48] Icarus detect (6:1) failed to initialise (incorrect device?)
[2013-09-11 17:25:49] Probing for an alive pool
[2013-09-11 17:25:50] Network diff set to 86.9M
[2013-09-11 17:25:51] Accepted e601b578 Diff 1/1 AMU 3
[2013-09-11 17:25:53] Accepted e458846a Diff 1/1 AMU 5
[2013-09-11 17:25:53] Accepted 348930bd Diff 4/1 AMU 2
[2013-09-11 17:25:56] USB init, open device failed, err -12, you need to install a WinUSB driver for - ICA device 6:1
[2013-09-11 17:25:56] Icarus detect (6:1) failed to initialise (incorrect device?)
[2013-09-11 17:25:56] Accepted e4a9be91 Diff 1/1 AMU 5
[2013-09-11 17:25:59] Accepted b164beda Diff 1/1 AMU 2
[2013-09-11 17:26:00] Hotplug: Icarus added AMU 6
[2013-09-11 17:26:00] Hotplug: Icarus added AMU 7
[2013-09-11 17:26:00] Hotplug: Icarus added AMU 8
[2013-09-11 17:26:01] Accepted 60b080ff Diff 2/1 AMU 0
[2013-09-11 17:26:01] Accepted 8d5fd0cf Diff 1/1 AMU 7
[2013-09-11 17:26:02] Accepted 478a7d7f Diff 3/1 AMU 0
[2013-09-11 17:26:05] USB init, open device failed, err -12, you need to install a WinUSB driver for - ICA device 6:1
[2013-09-11 17:26:05] Icarus detect (6:1) failed to initialise (incorrect device?)
[2013-09-11 17:26:09] Accepted 8e86fb63 Diff 1/1 AMU 6
[2013-09-11 17:26:09] Accepted fecd3d9a Diff 1/1 AMU 2
[2013-09-11 17:26:10] Accepted 1f30b92a Diff 8/1 AMU 1
[2013-09-11 17:26:11] USB init, open device failed, err -12, you need to install a WinUSB driver for - ICA device 6:1
[2013-09-11 17:26:11] Icarus detect (6:1) failed to initialise (incorrect device?)

Any assistance is appreciated.

Thanks!

~PulsarAV~

spacebob

newbie

Activity: 13

Merit: 0

Quote from: kano on September 11, 2013, 10:23:07 AM

Yeah your kernel crashed on you.
99.9999% likely an SD card problem.
Get a new SD and also make sure it is Class 10.
(and always make sure you shut it own properly, don't just switch it off)

The one I have now is a SanDisk 16GB Class 10. Perhaps I just got a junk one...

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Yeah your kernel crashed on you.
99.9999% likely an SD card problem.
Get a new SD and also make sure it is Class 10.
(and always make sure you shut it own properly, don't just switch it off)

spacebob

newbie

Activity: 13

Merit: 0

Quote from: -ck on September 10, 2013, 05:04:03 PM

No idea then sorry. Perhaps your Pi is coincidentally failing or as you say, some upgraded other package is responsible.

I was able t get a screen cap of the error when the system locks up

http://i.imgur.com/7sSZPU2.jpg

I'm not sure what this error means but I'm leaning towards that there was some kind of disk access error. Perhaps the SD card on my Pi is corrupted?

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: tk1337 on September 11, 2013, 12:03:00 AM

actually, odd, I was going to dump the output of the api call to a file, decided to change the parameter to an INT (1) instead of a BOOL (true) and now I'm getting back correct data...

that gives me enough of a lead to where I can figure it out (or at least get the correct data to show), thanks for the responses.

There are two Accept numbers in cgminer.
It only displays one on the screen.
A: is "Difficulty Accepted" = as per the README: "A: The total difficulty of Accepted shares"
The API has both "Difficulty Accepted" and "Accepted"
"Accepted" is the number of shares accepted ... the old ineffectual value.
Make sure you're not looking at the wrong one.

daemondazz

sr. member

Activity: 448

Merit: 250

Quote from: -ck on September 09, 2013, 08:44:51 PM

Quote from: Trongersoll on September 09, 2013, 08:34:29 PM

yeah when to upgrade is always a tough call.

Strictly speaking, I move to the latest Ubuntu 3 months after it is released, and 2 releases are usually binary compatible, which means they get a year of binary compatibility before I move on. 13.04 came out in April and 13.10 is due out in a month (as per the .04 .10 nomenclature).

No disagreeing with you, but it would be nice if the LTS releases were supported, at least while they are the latest LTS release (Not that rebuilding is hard... but still)

Askit2

hero member

Activity: 981

Merit: 500

DIV - Your "Virtual Life" Secured and Decentralize

Quote from: spacebob on September 10, 2013, 08:43:49 AM

Quote from: -ck on September 10, 2013, 08:31:44 AM

Quote from: spacebob on September 10, 2013, 08:23:33 AM

So I got a kinda weird issue.

I started mining on my Raspberry Pi (O/S: Raspian) with 5 Block Eruptors on a DLink DUB-7 on August 19th using cgminer 3.3.4 and followed the included instructions on how to compile the libusb libraries myself. It worked great and it ran non-stop for a few weeks. The other day I decided to update cgminer to 3.4.2. After mining for about 20 minutes the Pi seemed to locked up. My SSH session died and I couldn't ping the Pi anymore. I figured it was just a fluke so I restarted the Pi but, again, after mining for about 20 minutes the Pi locks up.

I figured that this must have just been an issue with the newest version of cgminer so I went back to 3.3.4 with no luck. 3.3.4 now causes the Pi to lock up as well. I thought that maybe the Pi was overheating so I tried doing something else intensive; watching a 1080p movie over my LAN for 2hrs+ but it worked great and never locked up. I also tried mining just with 1 miner but the Pi still locked up.

Perhaps there is an issue with the newest packages for the Pi? How can I provide some more detailed info to see what is going on? Anything else I can try to resolve the issue?

If going back to the previous version doesn't resolve the issue, how can the new version be responsible?

I'm not saying the newest version is responsible for the issue. I was just describing what I've tried so far.

Quote

Perhaps there is an issue with the newest packages for the Pi

What I meant by this is maybe updating my Pi's firmware and packages are causing the issue.

When this happened to me I wasn't using that specific CGMiner but it would lock up Raspbian and I would have no recourse but to hard power cycle it. Eventually it happened so often I investigated. I tried new SD card as it kept corrupting mine. I tried newer versions of CGMiner. I finally upgraded Raspbian and tried using the over clocking and low and behold it wouldn't boot properly.

I don't know that this is your problem but for me I spent 30$ on SD cards (good ones) and a 15$ cable and new power supply fixed it. So if it was me I would double check that your power isn't getting saggy and causing errors. Mine worked for 4 months or so Flawlessly before I had problems.

tk1337

sr. member

Activity: 266

Merit: 250

actually, odd, I was going to dump the output of the api call to a file, decided to change the parameter to an INT (1) instead of a BOOL (true) and now I'm getting back correct data...

that gives me enough of a lead to where I can figure it out (or at least get the correct data to show), thanks for the responses.

tk1337

sr. member

Activity: 266

Merit: 250

Quote from: Krak on September 10, 2013, 11:54:35 PM

Quote from: tk1337 on September 10, 2013, 11:17:35 PM

It appears that the API is reporting a different number of accepted shares than what is being shown on the output. Not sure if this is intentional for some reason or if this is an already known issue (sorry, not going through 600+ pages). Small example: CGMiner Output screen says 8105 accepted shares, the API returns 6786 for said device (1319 difference, seems to be across the board for each device).

Please let me know if you would like me to supply the data from the API vs. data on the output.

Maybe you're using a pool with variable difficulty and you're at a hashrate that keeps you bouncing around between difficulty 1 and 2 shares?

I would assume CGMiner's API would report the same data as what it's showing to the user on the output screen. Otherwise either the output screen or the API would be incorrect at all times.

Krak

hero member

Activity: 591

Merit: 500

Quote from: tk1337 on September 10, 2013, 11:17:35 PM

It appears that the API is reporting a different number of accepted shares than what is being shown on the output. Not sure if this is intentional for some reason or if this is an already known issue (sorry, not going through 600+ pages). Small example: CGMiner Output screen says 8105 accepted shares, the API returns 6786 for said device (1319 difference, seems to be across the board for each device).

Please let me know if you would like me to supply the data from the API vs. data on the output.

Maybe you're using a pool with variable difficulty and you're at a hashrate that keeps you bouncing around between difficulty 1 and 2 shares?

tk1337

sr. member

Activity: 266

Merit: 250

Quote from: kano on September 10, 2013, 11:28:35 PM

Quote from: tk1337 on September 10, 2013, 11:17:35 PM

It appears that the API is reporting a different number of accepted shares than what is being shown on the output. Not sure if this is intentional for some reason or if this is an already known issue (sorry, not going through 600+ pages). Small example: CGMiner Output screen says 8105 accepted shares, the API returns 6786 for said device (1319 difference, seems to be across the board for each device).

Please let me know if you would like me to supply the data from the API vs. data on the output.

Nope, I don't see it on any of my 4 instances.
You'll need to provide more info.
Also ... try java API summary and java API devs and compare those outputs to the screen.

CGMiner API summary reports a total accepted as 47634, CGMiner output shows the total as 57407, a difference of 9773 divide that by the number of devices (7), looking at a difference of around 1396 per device.

I'm falling asleep here, but I'll post screenshots & data to back up this tomorrow morning.

Edit: This is on linux (MinePeon distro) with ASIC USB Erupters only, however others are reporting an error with BFL devices as well on the same distro, I wrote a stand alone call (separate from MinePeon's WebUI) to see if there was any difference in what the WebUI was getting from CGMiner API versus what the WebUI was showing. Turns out, there is no difference in the WebUI on MinePeon's side, but it appears the difference is coming from CGMiner's API, as at the time of the call the numbers are off from what what the output screen is displaying.

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: tk1337 on September 10, 2013, 11:17:35 PM

It appears that the API is reporting a different number of accepted shares than what is being shown on the output. Not sure if this is intentional for some reason or if this is an already known issue (sorry, not going through 600+ pages). Small example: CGMiner Output screen says 8105 accepted shares, the API returns 6786 for said device (1319 difference, seems to be across the board for each device).

Please let me know if you would like me to supply the data from the API vs. data on the output.

Nope, I don't see it on any of my 4 instances.
You'll need to provide more info.
Also ... try java API summary and java API devs and compare those outputs to the screen.

tk1337

sr. member

Activity: 266

Merit: 250

It appears that the API is reporting a different number of accepted shares than what is being shown on the output. Not sure if this is intentional for some reason or if this is an already known issue (sorry, not going through 600+ pages). Small example: CGMiner Output screen says 8105 accepted shares, the API returns 6786 for said device (1319 difference, seems to be across the board for each device).

Please let me know if you would like me to supply the data from the API vs. data on the output.

nwoolls

hero member

Activity: 840

Merit: 1002

vulgartrendkill

hero member

Activity: 518

Merit: 500

hey there folks,

i`m having the TIMEOUT warning on 2 of my block erupters. I`ve had a search of this thread and I can only find reference to it in relation to Linux. As i`m running a window 7 pc, are there any steps i can take to rectify the error? I`ve read about the libusb file being correct in cgminer 3.4.2 and that this file may be the issue. do I have to place this file else where to work?

Thanks guys

johnyj

legendary

Activity: 1988

Merit: 1012

Beyond Imagination

After I installed the latest libudev-dev package, the linux froze at the beginning of start up, two leds on keyboard just flashes and no response from keyboard/mouse. I can never enter the system anymore, even with ssh

The prompt at frozen point is:

/init: line 318: can't open /root/dev/console: no such file (only part of the text were displayed, see below)

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: spacebob on September 10, 2013, 08:43:49 AM

Quote from: -ck on September 10, 2013, 08:31:44 AM

Quote from: spacebob on September 10, 2013, 08:23:33 AM

So I got a kinda weird issue.

I started mining on my Raspberry Pi (O/S: Raspian) with 5 Block Eruptors on a DLink DUB-7 on August 19th using cgminer 3.3.4 and followed the included instructions on how to compile the libusb libraries myself. It worked great and it ran non-stop for a few weeks. The other day I decided to update cgminer to 3.4.2. After mining for about 20 minutes the Pi seemed to locked up. My SSH session died and I couldn't ping the Pi anymore. I figured it was just a fluke so I restarted the Pi but, again, after mining for about 20 minutes the Pi locks up.

I figured that this must have just been an issue with the newest version of cgminer so I went back to 3.3.4 with no luck. 3.3.4 now causes the Pi to lock up as well. I thought that maybe the Pi was overheating so I tried doing something else intensive; watching a 1080p movie over my LAN for 2hrs+ but it worked great and never locked up. I also tried mining just with 1 miner but the Pi still locked up.

Perhaps there is an issue with the newest packages for the Pi? How can I provide some more detailed info to see what is going on? Anything else I can try to resolve the issue?

If going back to the previous version doesn't resolve the issue, how can the new version be responsible?

I'm not saying the newest version is responsible for the issue. I was just describing what I've tried so far.

Quote

Perhaps there is an issue with the newest packages for the Pi

What I meant by this is maybe updating my Pi's firmware and packages are causing the issue.

No idea then sorry. Perhaps your Pi is coincidentally failing or as you say, some upgraded other package is responsible.

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

Quote from: -ck on September 09, 2013, 07:43:00 PM

Quote from: PatMan on September 09, 2013, 10:55:08 AM

SOLVED! (sort of, eventually)

Conclusion:

Nvidia should stick to GFX chipsets.

Xubuntu 13.04 performed poorly compared to 12.04 (I reinstalled 12.04)

I need to learn more Grin

Thanks for investigating. Having coded parts of kernels that report CPU usage, I should point out that the CPU usage is not as clear as you may think, so while it appears that 13.04 is worse than 12.04 (37 vs 33% you said), it may be a measuring artefact difference, whereas 12% vs 33% is more likely to be significant.

You're welcome! And thanks for the reply. Yeah, I've been really happy with 12.04 - the thinking behind trying 13.04 was that maybe the drivers for my usb controllers had been updated and/or improved in the newer version, but if they had it didn't seem to cure the problem, the opposite in fact. I liked the new desktop look though..... Cheesy

Another thing that put me off a little was that the installation no longer fitted on a CD, not that it makes much difference since as soon as I install an OS I immediately set about uninstalling everything that isn't needed for mining anyway - gimp, Thunderbird, gstreamer etc. I run the OS on a small 40GB ssd & keep all the wallet data (5 different coins ATM) on a separate, larger & faster ssd in an effort to decrease latency.
It still strikes me as a little funny that the expensive super duper nvidia chipset was outclassed & outperformed by a £8 amazon cheap n' cheerful add-on card.... Cheesy

As you say, it's a case of horses for courses, I'll be sticking with 12.04 for the time being, but if I decide on upgrading the mobo to a non-nvidia chipset type I might try 13.04 again.

spacebob

newbie

Activity: 13

Merit: 0

Quote from: -ck on September 10, 2013, 08:31:44 AM

Quote from: spacebob on September 10, 2013, 08:23:33 AM

So I got a kinda weird issue.

I started mining on my Raspberry Pi (O/S: Raspian) with 5 Block Eruptors on a DLink DUB-7 on August 19th using cgminer 3.3.4 and followed the included instructions on how to compile the libusb libraries myself. It worked great and it ran non-stop for a few weeks. The other day I decided to update cgminer to 3.4.2. After mining for about 20 minutes the Pi seemed to locked up. My SSH session died and I couldn't ping the Pi anymore. I figured it was just a fluke so I restarted the Pi but, again, after mining for about 20 minutes the Pi locks up.

I figured that this must have just been an issue with the newest version of cgminer so I went back to 3.3.4 with no luck. 3.3.4 now causes the Pi to lock up as well. I thought that maybe the Pi was overheating so I tried doing something else intensive; watching a 1080p movie over my LAN for 2hrs+ but it worked great and never locked up. I also tried mining just with 1 miner but the Pi still locked up.

Perhaps there is an issue with the newest packages for the Pi? How can I provide some more detailed info to see what is going on? Anything else I can try to resolve the issue?

If going back to the previous version doesn't resolve the issue, how can the new version be responsible?

I'm not saying the newest version is responsible for the issue. I was just describing what I've tried so far.

Quote

Perhaps there is an issue with the newest packages for the Pi

What I meant by this is maybe updating my Pi's firmware and packages are causing the issue.

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