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

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: NathanB on July 31, 2015, 11:59:38 AM

a question Huh

why does when a miner go zombie does cgminer not always drop the connection to it and search (hotplug)
a new (another) miner.
it will keep the connection to the miner (usb) and just set there doing nothing.

just wondering...

It already resets some devices ... something that you'll find non-USB mining software doesn't do.

But it can't physically pull the miner out and plug it back in.
Physically unplugging it acts like a hardware reset coz the miner itself is not very well designed or made on the cheap.

An example of one that works with zombies is the hashfast hardware ... oh well.

NathanB

newbie

Activity: 12

Merit: 0

a question Huh

why does when a miner go zombie does cgminer not always drop the connection to it and search (hotplug)
a new (another) miner.
it will keep the connection to the miner (usb) and just set there doing nothing.

just wondering...

Hegemon

full member

Activity: 152

Merit: 100

A bit better but:
No device detected even after Zadig.

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

There are no --bmsc-* options in cgminer.

Current cgminer is 4.9.2 so ./cgminer.exe -h will tell you that at the start of the output

As I've said above on this page:
./cgminer.exe -n will tell you what's connected

Also, cgminer doesn't require any settings for the miner for normal running.

Simply try: cgminer.exe -o stratum.*** -u *** -p ***

If you want to change options then read the README for the U3 options:
https://github.com/ckolivas/cgminer/blob/master/README#L338

If want to use some other miner, not master cgminer from us, then you'll need to find who made that fork and ask them.

Hegemon

full member

Activity: 152

Merit: 100

Hello,

Got an U3, trying to make it work but no success yet (windows 7/64) with cgminer 4.9.2

message:

Quote

--bmsc-options: unrecognized option

same with bmsc-freq and --bmsc-voltage

here is my .bat:

Quote

cgminer.exe --bmsc-options 115200:0.5 -o stratum.*** -u *** -p *** --bmsc-freq 0B82 --bmsc-voltage 0800

pause

CP210x_VCP_Windows,Zadig installed

Any idea please ?

with another cgminer, device not found

pekatete

hero member

Activity: 518

Merit: 500

Quote from: pekatete on July 30, 2015, 06:20:22 PM

....

Just a thought ....

All good .... banish the thought.

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: pekatete on July 31, 2015, 06:20:48 AM

...
I was actually thinking more of the styling of the API commands than turning it into an http server ... but as usual you clearly had that covered. Its becoming clearer to me, though, why manufacturers that ship cgminer on their rigs more often than not do not ship the "out of the box" API, despite it having all the required information.

They do ship it as is (mostly), only they have stupid ideas about changing the names of fields and changing the format of fields unnecessarily and breaking compatibility between the different versions.
Bitmain even did that to their own versions on the S1.

It's nothing to do with API interface design changes.

That's the issue with the Bitmain version, they didn't change how the API works or the data format, instead they messed with fields making it no longer backward compatible, rather than simply editing the display scripts to display the raw data differently.
They already do edit the display scripts, but instead of e.g. editing a script to divide by 1000, they modified the cgminer API to do the division by 1000 and renamed the field to something else and deleted the old field name. Clearly they had no idea about design and keeping compatibility when they did that.

I guess the main problem was the fact that Bitmain copied the miner OpenWRT code DIRECTLY from Xiangfu at Avalon and then clearly had little idea what they were doing with that code initially.

pekatete

hero member

Activity: 518

Merit: 500

Quote from: kano on July 31, 2015, 05:28:29 AM

Quote from: pekatete on July 30, 2015, 06:20:22 PM

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 ....

It's not an HTTP server and never will be.

It's designed the way it is on purpose.
A miner's MOST important feature is it's performance when mining.

The API socket is low level and as simple as possible yet contains the information required without burdening the computer by wasting resources that may be scarce and wasting it's time matching up to the other 10 million other random formats that each person prefers.

Tacking on other crap like proxy servers and web based interfaces are design flaws that clearly certain other people have no idea about design and performance ... (not referring to you)

I was actually thinking more of the styling of the API commands than turning it into an http server ... but as usual you clearly had that covered. Its becoming clearer to me, though, why manufacturers that ship cgminer on their rigs more often than not do not ship the "out of the box" API, despite it having all the required information.

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: pekatete on July 30, 2015, 06:20:22 PM

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 ....

It's not an HTTP server and never will be.

It's designed the way it is on purpose.
A miner's MOST important feature is it's performance when mining.

The API socket is low level and as simple as possible yet contains the information required without burdening the computer by wasting resources that may be scarce and wasting it's time matching up to the other 10 million other random formats that each person prefers.

Tacking on other crap like proxy servers and web based interfaces are design flaws that clearly certain other people have no idea about design and performance ... (not referring to you)

pekatete

hero member

Activity: 518

Merit: 500

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 ....

tkalfaoglu

newbie

Activity: 25

Merit: 0

Quote from: tkalfaoglu on July 29, 2015, 05:29:53 AM

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

Great tip; many thanks!
-t

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Buchi-88 on July 29, 2015, 08:15:55 AM

Quote from: hurricandave on July 28, 2015, 09:51:25 PM

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.

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: tkalfaoglu on July 29, 2015, 05:29:53 AM

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.

Buchi-88

legendary

Activity: 3934

Merit: 2634

Quote from: hurricandave on July 28, 2015, 09:51:25 PM

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

tkalfaoglu

newbie

Activity: 25

Merit: 0

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

Quote from: kano on July 28, 2015, 08:05:12 PM

Quote from: tkalfaoglu on July 28, 2015, 05:27:24 PM

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

Polyatomic

sr. member

Activity: 257

Merit: 250

Network diff of 1.2M look.

hurricandave

legendary

Activity: 966

Merit: 1003

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

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: tkalfaoglu on July 28, 2015, 05:27:24 PM

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.

tkalfaoglu

newbie

Activity: 25

Merit: 0

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

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: tkalfaoglu on July 28, 2015, 09:21:08 AM

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.

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