Pages:
Author

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

legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
...
I now have OpenWrt up and running in VirtualBox but have ground to a halt and can't find any helpful instructions  Huh  I didn't realise how much of the S1 interface was literally just OpenWrt so it looks very familiar!
One of my replies to people who have asked in PM:
...
Cross compile.
Same process as avalon.
See their details for how to do it ... or OpenWRT that document how to cross compile also.
I've not documented it and I wont be - too much effort and there are those 2 sources already.

The cgminer feed that I change each time:
https://github.com/kanoi/cgminer-openwrt-packages
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Say I wanted to make sure I don't contribute to malicious pool activity, namely an attempt of the pool operator to withhold blocks for whatever reason, and I do so by verifying that once I found a block, the block is indeed broadcasted by the operator within a short timeframe, or otherwise, if this is not the case, I switch to another pool. It's easy to use a local or an external node to watch for the appeance of new blocks, but I was wondering what would be the best way to get the information about new blocks out of CGMiner? I could redirect the debug output and identify "found block" statements and then use the RPC-API to switch pools, but is this the best way?
You'd read API-README that tells you all the info you can get out of the API ...
Including the block count ...
newbie
Activity: 13
Merit: 0
Hi, I've read through a good chunk of this thread and wanted some guidance or at least to clarify some things.

I am running S1s and S2s and have only recently come across this thread.  I have had a little look at the CGMiner source code, most of which is beyond me at the moment but I haven't delved that deeply yet.

First question, there is mention that Bitmain's S1 (and S2) drivers have a few flaws and kano recommends using his (for the S1 so far anyway).  If I load kano's latest version of CGMiner onto my S1s is that issue addressed and can be forgotten about?

Secondly I would really like to compile a version of CGMiner from the source and load it onto one of my S1s, even if it is just a copy of an existing version.  Can this be compiled on anything (e.g. Windoze 7) or does it need to be compiled on Ubuntu to then run on the S1?  Once I have a machine that is set up to compile CGMiner successfully so it can be loaded onto an S1, I want to delve deeper into the workings of CGMiner (not that there will probably much benefit to that, it is more out of interest).  I have MinGW etc. on my system and there appear to be a couple of issues building CGMiner on it but haven't really looked into that yet as there is little point if I can't then run it on the S1.

Any help would be greatly appreciated.

as I understand it Kano's patch makes more of a difference in regards to p2pool mining and you need to build it on the same flavour of Linux. in this case openwrt and there are guides if you just search build cgminer on openwrt
Thanks norgan.  That's what I understood with the driver.  Didn't know it had to be openwrt so I shall have a search for that as there are loads of guides about for other operating systems but needed to know if they were any good to me.

If all you care about is the end result, you can just install kano's binary: https://github.com/kanoi/cgminer-binaries/tree/master/AntS1.  Runnning this on six S1s and it is rock solid.
I already have it running on one of my S1s and will probably update the rest in the next day or so.

I want to know how to build cgminer for myself though.  Partly out of interest and partly as I want to have a mess around with the code - if I mess up then I can always reload kano's version or hit the reset button  Smiley

I now have OpenWrt up and running in VirtualBox but have ground to a halt and can't find any helpful instructions  Huh  I didn't realise how much of the S1 interface was literally just OpenWrt so it looks very familiar!
member
Activity: 89
Merit: 10
Hi, I've read through a good chunk of this thread and wanted some guidance or at least to clarify some things.

I am running S1s and S2s and have only recently come across this thread.  I have had a little look at the CGMiner source code, most of which is beyond me at the moment but I haven't delved that deeply yet.

First question, there is mention that Bitmain's S1 (and S2) drivers have a few flaws and kano recommends using his (for the S1 so far anyway).  If I load kano's latest version of CGMiner onto my S1s is that issue addressed and can be forgotten about?

Secondly I would really like to compile a version of CGMiner from the source and load it onto one of my S1s, even if it is just a copy of an existing version.  Can this be compiled on anything (e.g. Windoze 7) or does it need to be compiled on Ubuntu to then run on the S1?  Once I have a machine that is set up to compile CGMiner successfully so it can be loaded onto an S1, I want to delve deeper into the workings of CGMiner (not that there will probably much benefit to that, it is more out of interest).  I have MinGW etc. on my system and there appear to be a couple of issues building CGMiner on it but haven't really looked into that yet as there is little point if I can't then run it on the S1.

Any help would be greatly appreciated.

as I understand it Kano's patch makes more of a difference in regards to p2pool mining and you need to build it on the same flavour of Linux. in this case openwrt and there are guides if you just search build cgminer on openwrt
Thanks norgan.  That's what I understood with the driver.  Didn't know it had to be openwrt so I shall have a search for that as there are loads of guides about for other operating systems but needed to know if they were any good to me.

If all you care about is the end result, you can just install kano's binary: https://github.com/kanoi/cgminer-binaries/tree/master/AntS1.  Runnning this on six S1s and it is rock solid.
sr. member
Activity: 308
Merit: 250
Decentralize your hashing - p2pool - Norgz Pool
newbie
Activity: 13
Merit: 0
Hi, I've read through a good chunk of this thread and wanted some guidance or at least to clarify some things.

I am running S1s and S2s and have only recently come across this thread.  I have had a little look at the CGMiner source code, most of which is beyond me at the moment but I haven't delved that deeply yet.

First question, there is mention that Bitmain's S1 (and S2) drivers have a few flaws and kano recommends using his (for the S1 so far anyway).  If I load kano's latest version of CGMiner onto my S1s is that issue addressed and can be forgotten about?

Secondly I would really like to compile a version of CGMiner from the source and load it onto one of my S1s, even if it is just a copy of an existing version.  Can this be compiled on anything (e.g. Windoze 7) or does it need to be compiled on Ubuntu to then run on the S1?  Once I have a machine that is set up to compile CGMiner successfully so it can be loaded onto an S1, I want to delve deeper into the workings of CGMiner (not that there will probably much benefit to that, it is more out of interest).  I have MinGW etc. on my system and there appear to be a couple of issues building CGMiner on it but haven't really looked into that yet as there is little point if I can't then run it on the S1.

Any help would be greatly appreciated.

as I understand it Kano's patch makes more of a difference in regards to p2pool mining and you need to build it on the same flavour of Linux. in this case openwrt and there are guides if you just search build cgminer on openwrt
Thanks norgan.  That's what I understood with the driver.  Didn't know it had to be openwrt so I shall have a search for that as there are loads of guides about for other operating systems but needed to know if they were any good to me.
sr. member
Activity: 308
Merit: 250
Decentralize your hashing - p2pool - Norgz Pool
Hi, I've read through a good chunk of this thread and wanted some guidance or at least to clarify some things.

I am running S1s and S2s and have only recently come across this thread.  I have had a little look at the CGMiner source code, most of which is beyond me at the moment but I haven't delved that deeply yet.

First question, there is mention that Bitmain's S1 (and S2) drivers have a few flaws and kano recommends using his (for the S1 so far anyway).  If I load kano's latest version of CGMiner onto my S1s is that issue addressed and can be forgotten about?

Secondly I would really like to compile a version of CGMiner from the source and load it onto one of my S1s, even if it is just a copy of an existing version.  Can this be compiled on anything (e.g. Windoze 7) or does it need to be compiled on Ubuntu to then run on the S1?  Once I have a machine that is set up to compile CGMiner successfully so it can be loaded onto an S1, I want to delve deeper into the workings of CGMiner (not that there will probably much benefit to that, it is more out of interest).  I have MinGW etc. on my system and there appear to be a couple of issues building CGMiner on it but haven't really looked into that yet as there is little point if I can't then run it on the S1.

Any help would be greatly appreciated.

as I understand it Kano's patch makes more of a difference in regards to p2pool mining and you need to build it (cgminer, not necessarily kano's driver as it's prebuilt for the S1) on the same flavour of Linux. in this case openwrt and there are guides if you just search build cgminer on openwrt
newbie
Activity: 13
Merit: 0
Hi, I've read through a good chunk of this thread and wanted some guidance or at least to clarify some things.

I am running S1s and S2s and have only recently come across this thread.  I have had a little look at the CGMiner source code, most of which is beyond me at the moment but I haven't delved that deeply yet.

First question, there is mention that Bitmain's S1 (and S2) drivers have a few flaws and kano recommends using his (for the S1 so far anyway).  If I load kano's latest version of CGMiner onto my S1s is that issue addressed and can be forgotten about?

Secondly I would really like to compile a version of CGMiner from the source and load it onto one of my S1s, even if it is just a copy of an existing version.  Can this be compiled on anything (e.g. Windoze 7) or does it need to be compiled on Ubuntu to then run on the S1?  Once I have a machine that is set up to compile CGMiner successfully so it can be loaded onto an S1, I want to delve deeper into the workings of CGMiner (not that there will probably much benefit to that, it is more out of interest).  I have MinGW etc. on my system and there appear to be a couple of issues building CGMiner on it but haven't really looked into that yet as there is little point if I can't then run it on the S1.

Any help would be greatly appreciated.
newbie
Activity: 36
Merit: 0
Hi,
Apparently Avalon3 is supposed to be accessible using Avalon2
I however get the following
Avalon2 Detect: Failed to open /dev/ttyUSB0

this error is the same as if the miner is not connected however the miner is connected to a hub at that address (everything is connected to USB0)
legendary
Activity: 826
Merit: 1000
Having an error since Version 4.4.0 at saving the config:

https://dl.dropboxusercontent.com/u/67023860/Screenshot%202014-06-22%2014.18.50.png

Config file is created, but empty!

Windows 7 64bit
legendary
Activity: 3990
Merit: 2695
New release: Version 4.4.1, 21st June 2014

Catching a flight in a few hours but couldn't stand the thought I might be able to fix some bugs, so this is an attempt to rectify a couple of known issues.


Human readable changelog:

- Failover stopped working on some recent releases when a pool was down for an extended period it would never fail back even though the pool was alive. This is an attempt to rectify that code.
- An attempt to rectify the problem with Antminer U* devices not working for some people.
- Finally stop calling the Icarus devices FPGA via the API - I'm quite sure no one is still running an actual Icarus FPGA any more, they're all just ASICs that used the original Icarus protocol (I wish they didn't since the protocol was designed for much slower devices).


Full changelog:

- Move icarus driver to being seen as an asic
- Clear usb reads on each pass through icarus detect to hopefully prevent false
positives for detecting rboxes
- Clean up pool failure and failover code for stratum


Thanks for the Fix, but my problem https://bitcointalksearch.org/topic/m.7420495 is still present!

I have start the cgminer in "debug" modus where can i find the debug file?

regards
newbie
Activity: 23
Merit: 0
Hi
Can anyone help me here:

a1 28nm module

Cgminer:

Utility showing half the speed of all the rest of the other modules.

Running at about 20-30% hardware error

Was missing a capacitor. I have soldered one back on.

What should I be looking for? Would this maybe be poor quality of capacitor?

Or should I be looking at something else completely? What does the utility show/measure between?

Thanks in advance
member
Activity: 89
Merit: 10
New release: Version 4.4.1, 21st June 2014
- An attempt to rectify the problem with Antminer U* devices not working for some people.

Also seems to work for my Antminer U2s on Win 7/32.  Nice work and fast!  Safe travels.
hero member
Activity: 539
Merit: 500
New release: Version 4.4.1, 21st June 2014
- An attempt to rectify the problem with Antminer U* devices not working for some people.

Solved it for me.  Great work as usual, thanks.  Enjoy your trip.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
New release: Version 4.4.1, 21st June 2014

Catching a flight in a few hours but couldn't stand the thought I might be able to fix some bugs, so this is an attempt to rectify a couple of known issues.


Human readable changelog:

- Failover stopped working on some recent releases when a pool was down for an extended period it would never fail back even though the pool was alive. This is an attempt to rectify that code.
- An attempt to rectify the problem with Antminer U* devices not working for some people.
- Finally stop calling the Icarus devices FPGA via the API - I'm quite sure no one is still running an actual Icarus FPGA any more, they're all just ASICs that used the original Icarus protocol (I wish they didn't since the protocol was designed for much slower devices).


Full changelog:

- Move icarus driver to being seen as an asic
- Clear usb reads on each pass through icarus detect to hopefully prevent false
positives for detecting rboxes
- Clean up pool failure and failover code for stratum
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Well it only gets detected as a serial USB device, you say an older version supported serial? do you know which built it was since perharps i will give that build ago.

End of day i got a miner sitting here doing nothing complete waste of money guy i got it from not responding and the TP-link flash bricks the router. So another £35 wasted on that piece of crap.
No sorry I was mixed up myself  Embarrassed. The avalon2 driver was written and is maintained and supported by Xiangfu and I don't really know much about it. Hopefully he can help you here if he sees your message.
newbie
Activity: 25
Merit: 0
I cant even find the basic commands to view usb device lists to see if its now visable.

The "-n" argument displays all usb devices available and exits.  It is in the readme.

something im doing wrong since worked on verison i used before, on the lastest install from sources on front page of this thread it didnt work.

Fresh start today on a fresh install now ive got a clear head.

Any advice some anyone please??

I have got cgminer 4.3.5 or 4.4.0 installed on another sd card. When i have cgminer running it says it can see the device as a serial usb connection since the miner is an avalon2 but it wont enable? Have i missed a command? i did compile with --enable-avalon2.

Sorry to ask so many questions Raspberry PI and cgminer are new to me and trying to learn.

*EDIT if i use sudo ./cgminer -n it details usb device.

When running cgminer it says 0 usb devices perharps i have not enabled the right option? but i have used avalon2 and its the single blade style 100ghs

You can do the old, ls /dev/ttyUSB* and start cgminer with ./cgminer -S /dev/ttyUSB0 --avalon2-voltage 10000 --avalon2-freq 1500 --avalon2-fan 90 -o YOUR_POOL:PORT
I'm not sure what the problem is with your avalon2 but one thing I am sure of is there is  no -S command in the mainline cgminer for any ASICs and hasn't been for a year. That was only for old serial based devices and all mainline cgminer uses direct USB only (cgminer forks are likely different but any drivers merged into mainline cgminer have to use direct USB).

Well it only gets detected as a serial USB device, you say an older version supported serial? do you know which built it was since perharps i will give that build ago.

End of day i got a miner sitting here doing nothing complete waste of money guy i got it from not responding and the TP-link flash bricks the router. So another £35 wasted on that piece of crap.
legendary
Activity: 3990
Merit: 2695
Good day,

i have an existing problem with my configuration:

8 x Antminer U2 +
8 x BFx2 Bitfury

as soon as I both operate (. / configure - enable-bitfury - enable-icarus) remains Cgminer hang over again, and "watchdog" restarts the Raspberry new!

Once I only BFx2 Bitfury (. / Configure - enable-bitfury) used, runs the Cgminer 24/7.
Code:
 0: BXM 0       :                         | 3.810G / 3.751Gh/s WU:52.9/m
 1: BXM 1       :                         | 2.394G / 3.187Gh/s WU:44.6/m
 2: BXM 2       :                         | 3.136G / 3.167Gh/s WU:44.6/m
 3: BXM 3       :                         | 2.990G / 3.006Gh/s WU:42.1/m
 4: BXM 4       :                         | 3.767G / 3.819Gh/s WU:53.7/m
 5: BXM 5       :                         | 3.894G / 3.919Gh/s WU:55.0/m
 6: BXM 6       :                         | 3.952G / 3.932Gh/s WU:55.5/m
 7: BXM 7       :                         | 3.804G / 3.867Gh/s WU:54.4/m
--------------------------------------------------------------------------------
 [2014-06-12 23:19:41] Zero length string passed to valid_hex from in util.c ini
tiate_stratum():2609
 [2014-06-12 23:19:41] Zero length string passed to valid_hex from in util.c ini
tiate_stratum():2609


Exactly the same is in the use of Antminer (. / Configure - enable-icarus)?

The problem is only with the simultaneous use, is it possibly there is a compatibility issue between the two drivers?

I had raised the issue before, but still wanted to thoroughly test!

On the Pi is the newest Kernel installed.

regards


Hello,

So after several tests I have to correct my results, the Bitfury driver is working perfect, instabilities with trailers from Cgminer (Pi hangs and the watchdog restarts), problems only with the Antminer U2+!?

Is it possible that the new Antminer Design V1.2 + U2 (Icarus Driver) is to blame with increased voltage?

The Antminer U2 + just is not stable, tested with 4.2.x, 4.3.x and 4.4.0??

regards
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
hero member
Activity: 539
Merit: 500
What operating system are you guys on that are having trouble with U1s and 4.4.0?

13.10 Saucy x86 - randomly zombie out and replug until cgminer crashes.  

Normally I wouldn't have upped unless a device change came, but I was upgrading from 12.04 and compiled fresh git before seeing the above posts about problems.  As soon as 4.3.5 was built, back to normal.
Pages:
Jump to: