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

[Neosaan]

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

[1503414420]

1503414420

[1503414420]

1503414420

[1503414420]

1503414420

[1503414420]

1503414420

[os2sam]

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.

[tZKtdvt6]

To Kano,

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

Thank you very much.

[kano]

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]

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.

[txplorer]

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?

[os2sam]

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]

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]

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]

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]

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

[os2sam]

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.

I just tried CGMiner with my Jalapeno and found that it doesn't work as well.  CGMiner says no devices found but cgminer -n shows the Jalapeno as being there.  It has been working fine with 4.7.1 which is what I had been using.

[-ck]

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.

I just tried CGMiner with my Jalapeno and found that it doesn't work as well.  CGMiner says no devices found but cgminer -n shows the Jalapeno as being there.  It has been working fine with 4.7.1 which is what I had been using.

I don't have any bfl hardware any more. Can someone who has one start it with the extra options "-D -T 2>log.txt" and after it's failed at startup stop it and post the output of log.txt here (preferably within code tags).

[-ck]

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.

This is correct. Too many manufacturers have devices with the same communication chips without anything to identify them apart and as new devices come out with the same chip it gets harder and harder to support the older devices. As of late there's no strong reason for people with old hardware to update to the latest version anyway since they're usually just support for new devices. A major rewrite would be required to choose devices by subname and since it's to support older hardware it's hard to justify the effort required. I'm continually adding tweaks for cgminer to try and properly identify them apart but it's an endless battle.

[tZKtdvt6]

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.

I just tried CGMiner with my Jalapeno and found that it doesn't work as well.  CGMiner says no devices found but cgminer -n shows the Jalapeno as being there.  It has been working fine with 4.7.1 which is what I had been using.

I don't have any bfl hardware any more. Can someone who has one start it with the extra options "-D -T 2>log.txt" and after it's failed at startup stop it and post the output of log.txt here (preferably within code tags).

Hello,

I promise doing and doing very well if you can give to me a little explanation of what I must done, I want to say what kind of test must I do, or what command and specifics parameters have I to write, please?

The Jalapeño cost to me near of three hundred dollars or euros, I'm not sure of all, and it arrived more or less six (6) months later of the date of the buy. Then to me is very important to have it connected and working very well as is mandatory, do you know?. The cgminer-4.8.0-linux-x86_64 works very well but I would preffer if it is possible to update to the most recent update of it. I have read the changes in the new version and I have seen some points which could be the cause to the miners don't connect as in the previous version of cgminer.

Thank you very much by your fast answer.

[os2sam]

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.

I just tried CGMiner with my Jalapeno and found that it doesn't work as well.  CGMiner says no devices found but cgminer -n shows the Jalapeno as being there.  It has been working fine with 4.7.1 which is what I had been using.

I don't have any bfl hardware any more. Can someone who has one start it with the extra options "-D -T 2>log.txt" and after it's failed at startup stop it and post the output of log.txt here (preferably within code tags).

The file exceeds the 64,000 character limit of the message so here's a link to it

https://dl.dropboxusercontent.com/u/65145036/log.txt

[-ck]

The file exceeds the 64,000 character limit of the message so here's a link to it

https://dl.dropboxusercontent.com/u/65145036/log.txt

Thanks Sam. I found the problem from your debug. If you're building on linux can you try latest git? If not, can you try the windows binary in temp here:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

[os2sam]

The file exceeds the 64,000 character limit of the message so here's a link to it

https://dl.dropboxusercontent.com/u/65145036/log.txt

Thanks Sam. I found the problem from your debug. If you're building on linux can you try latest git? If not, can you try the windows binary in temp here:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

I dropped in the Windoze binary and the Jalapeno works, but now the Block Erupters don't.  You want a new log.txt?

[-ck]

The file exceeds the 64,000 character limit of the message so here's a link to it

https://dl.dropboxusercontent.com/u/65145036/log.txt

Thanks Sam. I found the problem from your debug. If you're building on linux can you try latest git? If not, can you try the windows binary in temp here:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

I dropped in the Windoze binary and the Jalapeno works, but now the Block Erupters don't.  You want a new log.txt?

That's probably a new battle with AM's broken blockerupter driver.

sigh...

Sure why not give me the log to confirm. Thanks.

[os2sam]

The file exceeds the 64,000 character limit of the message so here's a link to it

https://dl.dropboxusercontent.com/u/65145036/log.txt

Thanks Sam. I found the problem from your debug. If you're building on linux can you try latest git? If not, can you try the windows binary in temp here:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

I dropped in the Windoze binary and the Jalapeno works, but now the Block Erupters don't.  You want a new log.txt?

That's probably a new battle with AM's broken blockerupter driver.

sigh...

Sure why not give me the log to confirm. Thanks.

Here you go.  The original 4.9.0 worked with the BE's.  Please let me know if it is too much effort to run this down.  After reading your post about the new versions not adding anything for the older hardware I'm not sure how much work it's really worth.

https://dl.dropboxusercontent.com/u/65145036/log2.txt

Thanks,
Sam