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

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

Quote from: txplorer on January 04, 2015, 02:13:22 PM

Quote from: os2sam on January 04, 2015, 01:33:47 PM

Quote from: txplorer on January 04, 2015, 01:23:41 PM

Quote from: os2sam on January 04, 2015, 01:12:05 PM

Quote from: txplorer on January 04, 2015, 12:39:23 PM

Having in issue with 4.9.0 on the r-pi. I have 10 Antminer devices (ANU). During initialization, a few of them will initialize as U3 devices (AU3) and repeatedly fail until I disable the USB port and re-enable. After the hot plug logic correctly detects that they are ANU devices and they run perfectly. Is there a way to tell cgminer to use only a single device type (ANU) or identify which device type is plugged into which port and defeat the automatic detection logic?

Try excluding the AU3. I had a similar problem with my BAJ being detected as a BXM until I excluded it in an earlier version of CGMiner.

Sorry, but how do I exclude the AU3? Is that a run-time command line parameter or a configuration parameter prior to the build?

It's a command line parameter. It's in the ASIC Readme, or should be at least.

To disable detection of the false BXM I had to add "--usb BF1:0". I don't know what the driver instance name for your false AU3 is.

The documentation would seem to indicate I can only exclude all Icarus driver devices, not specific types. I tried "--usb AU3:0" and it gave me a message to the effect that there was not driver named AU3.

You can enable/disable any device CGMiner recognizes. I have no idea which one is an AU3 or an ANU since I don't have those miners. But if both of these devices are icarus AKA ICA then I got nuthin.

Here's a list of driver instances from the readme, so it should be one of these.

_________________________________
The second version
--usb BAS:1,BFL:1,MMQ:0,ICA:0,KLN:0
allows you to specify how many devices to choose based on each device
driver cgminer has - the current USB drivers are:
AVA, BAS, BFL, BF1, DRB, HFA, ICA, KLN and MMQ.
_________________________________

txplorer

newbie

Activity: 3

Merit: 0

Quote from: os2sam on January 04, 2015, 01:33:47 PM

Quote from: txplorer on January 04, 2015, 01:23:41 PM

Quote from: os2sam on January 04, 2015, 01:12:05 PM

Quote from: txplorer on January 04, 2015, 12:39:23 PM

Having in issue with 4.9.0 on the r-pi. I have 10 Antminer devices (ANU). During initialization, a few of them will initialize as U3 devices (AU3) and repeatedly fail until I disable the USB port and re-enable. After the hot plug logic correctly detects that they are ANU devices and they run perfectly. Is there a way to tell cgminer to use only a single device type (ANU) or identify which device type is plugged into which port and defeat the automatic detection logic?

Try excluding the AU3. I had a similar problem with my BAJ being detected as a BXM until I excluded it in an earlier version of CGMiner.

Sorry, but how do I exclude the AU3? Is that a run-time command line parameter or a configuration parameter prior to the build?

It's a command line parameter. It's in the ASIC Readme, or should be at least.

To disable detection of the false BXM I had to add "--usb BF1:0". I don't know what the driver instance name for your false AU3 is.

The documentation would seem to indicate I can only exclude all Icarus driver devices, not specific types. I tried "--usb AU3:0" and it gave me a message to the effect that there was not driver named AU3.

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

Quote from: txplorer on January 04, 2015, 01:23:41 PM

Quote from: os2sam on January 04, 2015, 01:12:05 PM

Quote from: txplorer on January 04, 2015, 12:39:23 PM

Having in issue with 4.9.0 on the r-pi. I have 10 Antminer devices (ANU). During initialization, a few of them will initialize as U3 devices (AU3) and repeatedly fail until I disable the USB port and re-enable. After the hot plug logic correctly detects that they are ANU devices and they run perfectly. Is there a way to tell cgminer to use only a single device type (ANU) or identify which device type is plugged into which port and defeat the automatic detection logic?

Try excluding the AU3. I had a similar problem with my BAJ being detected as a BXM until I excluded it in an earlier version of CGMiner.

Sorry, but how do I exclude the AU3? Is that a run-time command line parameter or a configuration parameter prior to the build?

It's a command line parameter. It's in the ASIC Readme, or should be at least.

To disable detection of the false BXM I had to add "--usb BF1:0". I don't know what the driver instance name for your false AU3 is.

txplorer

newbie

Activity: 3

Merit: 0

Quote from: os2sam on January 04, 2015, 01:12:05 PM

Quote from: txplorer on January 04, 2015, 12:39:23 PM

Having in issue with 4.9.0 on the r-pi. I have 10 Antminer devices (ANU). During initialization, a few of them will initialize as U3 devices (AU3) and repeatedly fail until I disable the USB port and re-enable. After the hot plug logic correctly detects that they are ANU devices and they run perfectly. Is there a way to tell cgminer to use only a single device type (ANU) or identify which device type is plugged into which port and defeat the automatic detection logic?

Try excluding the AU3. I had a similar problem with my BAJ being detected as a BXM until I excluded it in an earlier version of CGMiner.

Sorry, but how do I exclude the AU3? Is that a run-time command line parameter or a configuration parameter prior to the build?

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

Quote from: txplorer on January 04, 2015, 12:39:23 PM

Having in issue with 4.9.0 on the r-pi. I have 10 Antminer devices (ANU). During initialization, a few of them will initialize as U3 devices (AU3) and repeatedly fail until I disable the USB port and re-enable. After the hot plug logic correctly detects that they are ANU devices and they run perfectly. Is there a way to tell cgminer to use only a single device type (ANU) or identify which device type is plugged into which port and defeat the automatic detection logic?

Try excluding the AU3. I had a similar problem with my BAJ being detected as a BXM until I excluded it in an earlier version of CGMiner.

txplorer

newbie

Activity: 3

Merit: 0

Having in issue with 4.9.0 on the r-pi. I have 10 Antminer devices (ANU). During initialization, a few of them will initialize as U3 devices (AU3) and repeatedly fail until I disable the USB port and re-enable. After the hot plug logic correctly detects that they are ANU devices and they run perfectly. Is there a way to tell cgminer to use only a single device type (ANU) or identify which device type is plugged into which port and defeat the automatic detection logic?

tZKtdvt6

full member

Activity: 166

Merit: 100

Developer

To kano,

Hello,

result that when I started cgminer-4.9.0-linux-x86_64-built,
I obtained a error message which says to me that libudev.so.1 isn't
found, then I looking for this error to Google and find a solution,
installing libudev1 from synaptic, it has resolve my first problem, but,...
now it start but only with one miner the AMU miner.
(You can see a screenshot of my two miners a bit more up in this web page)
Althought when I start cgminer-4.8.0 the two miners works at the same time
very good. Then I need a bit of your kindly help.

I have tried compiling the cgminer-master, but I obtain the same dilema.

Thank you very much.

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: ?? on ??

Reposting the same question to bump it and PMing will not get you a faster reply but rather suggest to ignore you.

./cgminer -h | head -2
or
java API config

Try that ... so there is some info about what your problem is ............

tZKtdvt6

full member

Activity: 166

Merit: 100

Developer

To Kano,

What do you recomend to make that works good my two miners with the cgminer-4.9.0?

Thank you very much.

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

Quote from: Neosaan on January 03, 2015, 04:46:32 PM

Hello. Dear experts, I need help. have scyipt Asik

Mainline CGMiner does not support scrypt. Post in the Alt Coin forum for help with the proper fork, if there is one.

Neosaan

full member

Activity: 152

Merit: 100

Hello. Dear experts, I need help. have scyipt Asik http://titanminer.com/?product=dragon-miner-litecoin-asic-30mhs-scypt-lketc can not find the version you want Cgminera for his work.
Asik is connected to a computer with vindovs7 installed driver for the serial port = >> Com1 Zadig
Which version cgminera need and what syntax bat needed? Help please, for 3 days ... I am suffering. Tried Cgminer Zeus - he does not see the COM port to which is connected Asik Works only BFGMiner - but his work does not suit me, you need only version CGminer CGminer which saw Asik was 3.1.1 - but this version is not able to work through a proxy, and I need it proxy I beg your help

tZKtdvt6

full member

Activity: 166

Merit: 100

Developer

Here they are, my two SHA-256 miners, I have tried to update to the cgminer-4.9.0, but it was impossible.
With cgminer-4.9.0 I only get that works the AMU unit.

While you can see a very funny screenshot of them running happyly into cgminer-4.8.0

Thank you very much.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: kano on January 02, 2015, 11:51:01 PM

Well, from my post, you should also try using API.class
If it works, then you know the problem is the data being sent.

It was my doing. Sad

It's working now.

I also figured out that the W: needs to be in front of each address, ie,

Code:

W:127.0.0.1,192.168.0.194

makes 127.0.0.1 priv and 192.168.0.194 read only.

Thanks!

M

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: mdude77 on January 02, 2015, 10:05:54 PM

Quote from: kano on January 02, 2015, 09:56:07 PM

"Old" cgminer version on my desktop ... 4.6.1 ... just happens to match.

Using API.class that is supplied with cgminer:

All above looks OK to me ... for me.

So ... the possible problems are:
1) the JSON decoder you compiled into cgminer is a bad choice and you should use the json code supplied with cgminer
2) whatever you are using to send to the cgminer API is changing the data from simply 8 bit ascii to something else
3) the cgminer you are using is not official and they've messed with the API or the json included code
4) ?

I'm using the "stock" cgminer that comes with the Antminer S4 and Spondoolie SP20s. I was hoping if the problem was of the above, I wouldn't have the same problem on both units.. but I do. Sad

I'm pretty sure I'm sending the request correctly as it's the same code that I use to request API data ... aka pools, status, and so forth. And that all works fine.

Guess I'll go to Spondoolies next.

Thanks.

M

Well, from my post, you should also try using API.class
If it works, then you know the problem is the data being sent.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: kano on January 02, 2015, 09:56:07 PM

"Old" cgminer version on my desktop ... 4.6.1 ... just happens to match.

Using API.class that is supplied with cgminer:

All above looks OK to me ... for me.

So ... the possible problems are:
1) the JSON decoder you compiled into cgminer is a bad choice and you should use the json code supplied with cgminer
2) whatever you are using to send to the cgminer API is changing the data from simply 8 bit ascii to something else
3) the cgminer you are using is not official and they've messed with the API or the json included code
4) ?

I'm using the "stock" cgminer that comes with the Antminer S4 and Spondoolie SP20s. I was hoping if the problem was of the above, I wouldn't have the same problem on both units.. but I do. Sad

I'm pretty sure I'm sending the request correctly as it's the same code that I use to request API data ... aka pools, status, and so forth. And that all works fine.

Guess I'll go to Spondoolies next.

Thanks.

M

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

"Old" cgminer version on my desktop ... 4.6.1 ... just happens to match.

Using API.class that is supplied with cgminer:

Code:

# java API version
Attempting to send 'version' to 127.0.0.1:4028
Answer='STATUS=S,When=1420253231,Code=22,Msg=CGMiner versions,Description=cgminer 4.6.1|VERSION,CGMiner=4.6.1,API=3.4|'
[STATUS] =>
(
   [STATUS] => S
   [When] => 1420253231
   [ Code] => 22
   [Msg] => CGMiner versions
   [Description] => cgminer 4.6.1
)
[VERSION] =>
(
   [0] => VERSION
   [CGMiner] => 4.6.1
   [API] => 3.4
)

Code:

# java API "addpool|stratum+tcp://stratum8080.kano.is:8080,Kano,addp"
Attempting to send 'addpool|stratum+tcp://stratum8080.kano.is:8080,Kano,addp' to 127.0.0.1:4028
Answer='STATUS=S,When=1420253142,Code=55,Msg=Added pool 'stratum+tcp://stratum8080.kano.is:8080',Description=cgminer 4.6.1|'
[STATUS] =>
(
   [STATUS] => S
   [When] => 1420253142
   [ Code] => 55
   [Msg] => Added pool 'stratum+tcp://stratum8080.kano.is:8080'
   [Description] => cgminer 4.6.1
)

Code:

# java API '{"command":"addpool","parameter":"stratum+tcp://stratum8080.kano.is:8080,Kano,addp"}'
Attempting to send '{"command":"addpool","parameter":"stratum+tcp://stratum8080.kano.is:8080,Kano,addp"}' to 127.0.0.1:4028
Answer='{"STATUS":[{"STATUS":"S","When":1420253204,"Code":55,"Msg":"Added pool 'stratum+tcp://stratum8080.kano.is:8080'","Description":"cgminer 4.6.1"}],"id":1}'
[{"STATUS":[{"STATUS":"S"] =>
(
   [0] => {"STATUS":[{"STATUS":"S"
   [1] => "When":1420253204
   [2] => "Code":55
   [3] => "Msg":"Added pool 'stratum+tcp://stratum8080.kano.is:8080'"
   [4] => "Description":"cgminer 4.6.1"}]
   [5] => "id":1}
)

All above looks OK to me ... for me.

So ... the possible problems are:
1) the JSON decoder you compiled into cgminer is a bad choice and you should use the json code supplied with cgminer
2) whatever you are using to send to the cgminer API is changing the data from simply 8 bit ascii to something else
3) the cgminer you are using is not official and they've messed with the API or the json included code
4) ?

mdude77

legendary

Activity: 1540

Merit: 1001

I'm having problems with the addpool API command. I'm certain I'm looking over something obvious, but I'm not seeing what it is.

The API docs state this:

Code:

The JSON request format required is '{"command":"CMD","parameter":"PARAM"}'
(though of course parameter is not required for all requests)
where "CMD" is from the "Request" column below and "PARAM" would be e.g.
the ASC/PGA number if required.

An example request in both formats to disable Hotplug:
  hotplug|0
  {"command":"hotplug","parameter":"0"}

When I try sending this:

Code:

{"command":"addpool","parameter":"http://192.168.0.194:3333,test,abc"}

I get this as a response:

Code:

{"STATUS":[{"STATUS":"E","When":1420251376,"Code":23,"Msg":"Invalid JSON","Description":"cgminer 4.6.1"}],"id":1}

When I try sending this:

Code:

"addpool|http://192.168.0.194:3333,test,abc"

I get this as a response:

Code:

{"STATUS":[{"STATUS":"E","When":1420251505,"Code":14,"Msg":"Invalid command","Description":"cgminer 4.6.1"}],"id":1}

(Isn't the response supposed to be in text if the request is in text?)

I've tried this on my S4 with cgminer 4.6.1, and on my SP20 with cgminer 4.7.0, and I get the same result.

Yet if SSH into my S4 and enter:

Code:

cgminer-api "addpool|http://192.168.0.194:3333,test,abc"

It works.

What am I missing?

Thanks.

M

Buchi-88

legendary

Activity: 3990

Merit: 2695

Quote from: -ck on January 01, 2015, 04:50:32 AM

Quote from: Buchi-88 on December 22, 2014, 09:24:01 AM

Hello,

anyone have an idea about this failure?

Quote

cgminer version 4.7.1 - Started: [2014-12-22 12:46:13]
-----------------------------------------------------------------------------------------------
(5s):29.66G (1m):29.07G (5m):29.24G (15m):29.28G (avg):29.27Gh/s
A:60553 R:1918 HW:0 WU:412.8/m | ST: 3 SS: 0 NB: 98 LW: 101434 GF: 7 RF: 0
Connected to multiple pools with block change notify
Block: 712d1003... Diff:2.34M Started: [15:19:58] Best share: 79.9K
-----------------------------------------------------------------------------------------------
USB management Pool management Settings Display options Quit
0: BXM 0 : | 3.725G / 3.624Gh/s WU:51.9/m A:7810 R:217 HW:0
1: BXM 1 : | 3.815G / 3.797Gh/s WU:53.2/m A:8606 R:182 HW:0
2: BXM 2 : | 4.018G / 4.003Gh/s WU:56.0/m A:8544 R:274 HW:0
3: BXM 3 : | 3.715G / 3.700Gh/s WU:51.8/m A:7457 R:292 HW:0
4: BXM 4 : | 3.656G / 3.607Gh/s WU:51.1/m A:7342 R:201 HW:0
6: BXM 6 : | 3.732G / 3.667Gh/s WU:51.9/m A:7733 R:249 HW:0
8: BXM 8 : | 3.932G / 3.883Gh/s WU:54.5/m A:4895 R:226 HW:0
9: BXM 9 : | 3.021G / 2.981Gh/s WU:42.1/m A:2103 R:126 HW:0
-----------------------------------------------------------------------------------------------
[2014-12-22 13:38:14] BXM 5: SPI RX error 0, read 55 of 81
[2014-12-22 13:38:14] BXM 5 failure, disabling!
[2014-12-22 13:38:14] BXM 5: SPI TX error -4, sent 0 of 11
[2014-12-22 13:38:14] BXM 5: SPI TX error -4, sent 0 of 12
[2014-12-22 14:30:46] BXM 7: SPI RX error 0, read 0 of 81
[2014-12-22 14:30:46] BXM 7 failure, disabling!
[2014-12-22 14:30:46] BXM 7: SPI TX error -4, sent 0 of 11
[2014-12-22 14:30:46] BXM 7: SPI TX error -4, sent 0 of 12

regards

Likely you are drawing too much power from your USB hub for that many devices.

THX for your answer, but the USB HUB should be enought power for the miners the have 20A...

Dipo Electronic 19 port USB hubs with 20A

regards

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Buchi-88 on December 22, 2014, 09:24:01 AM

Hello,

anyone have an idea about this failure?

Quote

cgminer version 4.7.1 - Started: [2014-12-22 12:46:13]
-----------------------------------------------------------------------------------------------
(5s):29.66G (1m):29.07G (5m):29.24G (15m):29.28G (avg):29.27Gh/s
A:60553 R:1918 HW:0 WU:412.8/m | ST: 3 SS: 0 NB: 98 LW: 101434 GF: 7 RF: 0
Connected to multiple pools with block change notify
Block: 712d1003... Diff:2.34M Started: [15:19:58] Best share: 79.9K
-----------------------------------------------------------------------------------------------
USB management Pool management Settings Display options Quit
0: BXM 0 : | 3.725G / 3.624Gh/s WU:51.9/m A:7810 R:217 HW:0
1: BXM 1 : | 3.815G / 3.797Gh/s WU:53.2/m A:8606 R:182 HW:0
2: BXM 2 : | 4.018G / 4.003Gh/s WU:56.0/m A:8544 R:274 HW:0
3: BXM 3 : | 3.715G / 3.700Gh/s WU:51.8/m A:7457 R:292 HW:0
4: BXM 4 : | 3.656G / 3.607Gh/s WU:51.1/m A:7342 R:201 HW:0
6: BXM 6 : | 3.732G / 3.667Gh/s WU:51.9/m A:7733 R:249 HW:0
8: BXM 8 : | 3.932G / 3.883Gh/s WU:54.5/m A:4895 R:226 HW:0
9: BXM 9 : | 3.021G / 2.981Gh/s WU:42.1/m A:2103 R:126 HW:0
-----------------------------------------------------------------------------------------------
[2014-12-22 13:38:14] BXM 5: SPI RX error 0, read 55 of 81
[2014-12-22 13:38:14] BXM 5 failure, disabling!
[2014-12-22 13:38:14] BXM 5: SPI TX error -4, sent 0 of 11
[2014-12-22 13:38:14] BXM 5: SPI TX error -4, sent 0 of 12
[2014-12-22 14:30:46] BXM 7: SPI RX error 0, read 0 of 81
[2014-12-22 14:30:46] BXM 7 failure, disabling!
[2014-12-22 14:30:46] BXM 7: SPI TX error -4, sent 0 of 11
[2014-12-22 14:30:46] BXM 7: SPI TX error -4, sent 0 of 12

regards

Likely you are drawing too much power from your USB hub for that many devices.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: helipotte on December 26, 2014, 01:42:22 PM

Is the blockerupter prisma/tube not enabled in the windows binary download? When I run cgminer 4.9.0 it never detects the tube I have connected with a

CP2102 Uart. The option "bet-clk 25" results in "unrecognized option". I complied it myself in Mingw. This way detects it but I get LIBUSB errors the a crash.

This same setup works fine under Linux but due to hardware placement windows is the only option now, or the crappy controller using a proxy. Never have been

able to get this thing to hash under Windows 7 x64.

Yes you are right, I wasn't particularly pleased at the reports from the few people who had tried the driver AM pushed to master cgminer since most people reported it didn't actually work, so I conveniently forgot to include it. Anyway here's a drop-in replacement binary for the windows 4.9.0 version if you still want to try it, just replace the existing exe that comes with 4.9.0:

http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

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