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

[TheRealSteve]

If the issue is largely with reconnects to pools that start out with a too low diff for the device, and for whatever reason there's no minimum vardiff that can be set on the pool interface, see if the pool used accepts the --suggest-diff parameter?  If it's a proxy type service, the end-user doesn't even have to worry about setting that up.

[luthermarcus]

Hey could you add support for S5 like you did for s3?

[Mikestang]

Hey could you add support for S5 like you did for s3?

If you pay for it I bet they'd be happy to. 

[kano]

Hey could you add support for S5 like you did for s3?

Already working on it.

[toptek]

Hey could you add support for S5 like you did for s3?

Already working on it.

nice

I hope you actually fix it , so far you have once you do it . The new bitmain Firmware worked ok for me till today on one of my S5, then  for no good reason the speed started dropping then one of the blades just stopped and displayed

-------- from  zeros and No X es .


 i rebooted it, no go . so i reset it to defaults, no go, finally i was forced to go back to one of the  Firmware modified by Smit1237 with out #xnsub support sense that seems to do strange things to my S5's on some pools . it is working like it should be now with Smit1237 firmware but not with the new released firmware from bitmain . that did work well for a few days then to day for no reason it did , what i just said .

[luthermarcus]

Hey could you add support for S5 like you did for s3?

Already working on it.

nice

I hope you actually fix it , so far you have once you do it . The new bitmain Firmware worked ok for me till today on one of my S5, then  for no good reason the speed started dropping then one of the blades just stopped and displayed

-------- from  zeros and No X es .


 i rebooted it, no go . so i reset it to defaults, no go, finally i was forced to go back to one of the  Firmware modified by Smit1237 with out #xnsub support sense that seems to do strange things to my S5's on some pools . it is working like it should be now with Smit1237 firmware but not with the new released firmware from bitmain . that did work well for a few days then to day for no reason it did , what i just said .

I agree the s5 does work different on each pool. I just want it fixed for p2pool becuase it hash drops from 1200 to 800-900. It works good with some pools and like you say others it displays x for no good reason and starts to act up p2pool being one of them.

[toptek]

Hey could you add support for S5 like you did for s3?

Already working on it.

nice

I hope you actually fix it , so far you have once you do it . The new bitmain Firmware worked ok for me till today on one of my S5, then  for no good reason the speed started dropping then one of the blades just stopped and displayed

-------- from  zeros and No X es .


 i rebooted it, no go . so i reset it to defaults, no go, finally i was forced to go back to one of the  Firmware modified by Smit1237 with out #xnsub support sense that seems to do strange things to my S5's on some pools . it is working like it should be now with Smit1237 firmware but not with the new released firmware from bitmain . that did work well for a few days then to day for no reason it did , what i just said .

I agree the s5 does work different on each pool. I just want it fixed for p2pool becuase it hash drops from 1200 to 800-900. It works good with some pools and like you say others it displays x for no good reason and starts to act up p2pool being one of them.

I notice that to on  p2pool you log on it, then about 10 mins later it caps at 800 or 900 GS on my S5s on my S3 even before the fix had no issue there . Or i would be using it over antpool any day .

[tkalfaoglu]

On a fresh fedora 22 install, I compiled cgminer with -enable-icarus
and plugged in two antiminer U3's.

It "appears" to work because I can see the hashing status of the two devices, but it also dumps lots of errors like this:

ftdi_sio  ttyUSB0: Unable to write latency timer: -71
ftdi_sio  ttyUSB0: Unable to read latency timer: -71
ftdi_sio  ttyUSB0: Unable to write latency timer: -71
and it keeps repeating..

What can I do to fix this?

Thanks, -t

[Buchi-88]

Anyone know about this errors?

cgminer version 4.3.3 - Started: [2015-07-28 18:49:24]
--------------------------------------------------------------------------------
 (5s):12.87G (1m):12.78G (5m):12.56G (15m):11.84G (avg):12.65Gh/s
 A:7496  R:56  HW:0  WU:179.7/m
 Connected to multiple pools with block change notify
 Block: 9135be29...  Diff:1.24M  Started: [19:32:22]  Best share: 8.88K
--------------------------------------------------------------------------------
 USB management Pool management Settings Display options Quit
 0: BXM 0       :                         | 4.393G / 4.402Gh/s WU:61.9/m
 2: BXM 2       :                         | 4.305G / 4.203Gh/s WU:60.6/m
 3: BXM 3       :                         | 4.138G / 3.983Gh/s WU:57.9/m
--------------------------------------------------------------------------------
[2015-07-28 19:21:12] BXM 1: SPI RX error 0, read 0 of 81
 [2015-07-28 19:21:12] BXM 1 failure, disabling!
 [2015-07-28 19:21:12] BXM 1: SPI TX error -4, sent 0 of 11
 [2015-07-28 19:21:12] BXM 1: SPI TX error -4, sent 0 of 12
 [2015-07-28 19:21:18] BXM 0: SPI RX error -7, read 0 of 8
 [2015-07-28 19:21:19] BXM 0: SPI RX error -7, read 0 of 9

Then the miner restart?

[kano]

On a fresh fedora 22 install, I compiled cgminer with -enable-icarus
and plugged in two antiminer U3's.

It "appears" to work because I can see the hashing status of the two devices, but it also dumps lots of errors like this:

ftdi_sio  ttyUSB0: Unable to write latency timer: -71
ftdi_sio  ttyUSB0: Unable to read latency timer: -71
ftdi_sio  ttyUSB0: Unable to write latency timer: -71
and it keeps repeating..

What can I do to fix this?

Thanks, -t

See the first post for where you get the current master cgminer.
I've no idea what you are running or who you got it from.

[tkalfaoglu]

Thank you -- today I downloaded the master, and compiled it. So it is the most recent version.

[kano]

Thank you -- today I downloaded the master, and compiled it. So it is the most recent version.

./cgminer -h | head will show what you are running.
./cgminer -n will list the USB devices.
./cgminer -D --verbose (followed by your other options) will show debug of it running.
... and lastly ... the README says how to setup access to USB devices if you are not using root.

[hurricandave]

Um...I thought 4.9.2 was the most recent? Looks like he compiled 4.3.3?

[Polyatomic]

Network diff of 1.2M look.

[tkalfaoglu]

SOLVED! I just had to add:
    --usb 2:5,2:4
at the end of the command line..

Thank you -- today I downloaded the master, and compiled it. So it is the most recent version.

./cgminer -h | head will show what you are running.
./cgminer -n will list the USB devices.
./cgminer -D --verbose (followed by your other options) will show debug of it running.
... and lastly ... the README says how to setup access to USB devices if you are not using root.

Many thanks.. It seems cgminer finds a third device that it keeps trying to use..

# cgminer -h|head
cgminer 4.9.2
Built with icarus mining support.

# cgminer -n
 [2015-07-29 12:25:41.967] USB all: found 12 devices - listing known devices
.USB dev 0: Bus 2 Device 5 ID: 10c4:ea60
  Manufacturer: 'Silicon Labs'
  Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 1: Bus 2 Device 4 ID: 10c4:ea60
  Manufacturer: 'Silicon Labs'
  Product: 'CP2102 USB to UART Bridge Controller'
.USB dev 2: Bus 8 Device 3 ID: 0403:6001
  Manufacturer: '** err:(-1) LIBUSB_ERROR_IO'
  Product: '** err:(-1) LIBUSB_ERROR_IO'                    
 [2015-07-29 12:25:41.967] 3 known USB devices  

http://www.kalfaoglu.net/tmp/screenshot.png
I guess I need to somehow specify which devices to use.
Many thanks, -turgut

[Buchi-88]

Um...I thought 4.9.2 was the most recent? Looks like he compiled 4.3.3?

Hello and thanks for your answer, but with the 4.9.2 is the same, i have read for the Bitfurys are the 4.3.3 the most recent!?

About the difficult, i mine with the Bitfurys only the "eMark"...

regards

[kano]

SOLVED! I just had to add:
    --usb 2:5,2:4
at the end of the command line..

...

Use: --usb 2:*
If they zombie and revive (or if you pull one out and hotplug it back in) they'll be on the same Bus number (2) but get a new Device number.

[-ck]

Um...I thought 4.9.2 was the most recent? Looks like he compiled 4.3.3?

Hello and thanks for your answer, but with the 4.9.2 is the same, i have read for the Bitfurys are the 4.3.3 the most recent!?

About the difficult, i mine with the Bitfurys only the "eMark"...

regards

Always use the most recent. There is no way 4.3.3 is "the most recent".

You probably just have a failing device. These things have a life expectancy.

[tkalfaoglu]

--usb 2:*
at the end of the command line..[/b]
...

Great tip; many thanks!
-t

[pekatete]

I was working on another project and came across this API Style guide, re implementaion of the cgminer API -  pertinently Collection Resources

Just a thought ....