[Minera v0.9.1] Your next mining dashboard - Antminer/CPUminer/CGminer/BFGminer

[tutorialevideo]

the minera temperature on block erupter prisma is true?

[tutorialevideo]

and how to boots the frecvency on the prisma miner? on the bee controller i could get it up to 300 MHZ

[toptek]

Thanks Riley.

The issue I am currently looking to reproduce is the report that ZeusMiner hardware does not work at all. I am leaning towards this being an issue with the default clock being set too high in the driver as discussed in the BFGMiner thread here.

If you are having an issue with hashrate dropping, are you using a multipool? If so this is a known issue with BFGMiner and I'd recommend posting the issue in the BFGMiner thread.

Hi Nate,

I am using a multipool, yes (Clevermining).  Perhaps that's the cause then - I'll post it in the BFGminer thread.

I've found my Blizzard is not detected unless I use --set zeusminer:ignore_golden_nonce=1.  It seems to be detected fine after putting in that flag.

Thanks for following up. That sounds expected with BFGMiner unfortunately. When the Multipool changes blockchains the hashrate in BFGMiner drops.

HM i read some place that's a firm ware bug with zeus miners . --set zeusminer:ignore_golden_nonce=1 it turns some thing off . CGMINer has a setting for it to .



In two days i gonna load in BFGMINer 5.0 into Minera see if the hash rate issue is fixed there is some thing about in it the read me stuff .



Trying to see if my power company is playing with prices or I'd do it now or have tried it by now .

[ntsdm]

hi everyone,
i know this question has been asked before but is there support and what would i need to do for this to work with a  A2 TERMINATOR 86MHs by innosilicon?
 please try to give a clear answer understandable by everyone.

anyone capablle of answering this?

[toptek]

hi everyone,
i know this question has been asked before but is there support and what would i need to do for this to work with a  A2 TERMINATOR 86MHs by innosilicon?
 please try to give a clear answer understandable by everyone.

anyone capablle of answering this?

If i had one I'm sure I would have it run'in with in hours with minera but i don't see  me paying what is it 1, 600$  for some thing that in a few days  might  sell for  800 or less . . i almost bought one the other day i had to give it a lot of thought. bought a few zuesminer in stead they took me hours of searching etc  but got them run'in real nice .


wish i could help  you   . THe best i can  help you is here  try this : http://zoomhash.com/pages/a2-and-mini-a2-software-setup  


The set up in Minera will about the same sorry i can't detail it for you i don't have a A 2 may never , waiting for  the L1 s. .I thought the A2 does more like 100 MH and  the A1 does around 70 to 90  MH.

and yea I'm more a scrypt miner all way have like it more then doing sha256 just fits me . yup more like 150 mh   oc if read this right http://www.innosilicon.com/A2.htm


I guess it depends on B# to .  im sure or hope  mich is working on some thing to supize us all so far its the best in my book . ( minera ) that is .  and only reason I don't have a donation miner set on one of my zeus's is that power drain issue but it look like BFG 5.0 may have fixed it . and its not just with  BFG either you have to play with them a lot they are nice but hard to get just right which makes it even more  fun .

[bradleyjay]

I'm new to Minera and mining in general and have a quick question.

I'm currently using a Gridseed G-Black, which as I understand is based on the GC3355 chips, and uses 40 chip boards (I'm sure someone can correct me if I'm wrong).

So far, the only miner software that seems to work is the CPUMiner that's included with Minera.  When I choose any of the others, I get either an extremely low or zero hashrate or it fails to detect the devices at all.  From my understanding, the DMax CGMiner fork *should* work as it provides Gridseed support, but this seems to be an option that needs to be specified at compile-time.

So my question is, does Minera's included DMax CGMiner fork include Gridseed support or only Zeus support?  Do I need to compile and install my own version of the DMax fork to include Gridseed support?  Also, I don't really have any particular reason for wanting to use CGMiner over CPUMiner.  Like I said I'm new to mining and just wanted to experiment and see which one works best with my device.  If CPU miner is the best choice then I'm fine with that.

Also, my miners seem like they can only use 800MHz frequency.  I was under the impression that the frequency could be changed to tweak performance.

Thanks in advance for any help anyone could provide.

[madmartyk]

I'm using minera for my g-blacks (have 2 hooked up to one pi).  I'm using minera v0.3.5 and it works great.  Tried the updates and had all kinds of issues with hashrates.  DL the 0.3.5 version and you'll have no issues!!

[bradleyjay]

>> I'm using minera for my g-blacks (have 2 hooked up to one pi).  I'm using minera v0.3.5 and it works great.  Tried the updates and had all kinds of issues with hashrates.  DL the 0.3.5 version and you'll have no issues!!

Thanks for the info, I appreciate it.  I'll give that a try for sure.  Which miner program are you using for your G-Blacks?

[madmartyk]

cpuminer, set at the defaults.

[madmartyk]

Here are the hash for my 2 G-Blacks hooked up to an external pi

[mcipseric]

Hi,

I am very new to mining.  I have a rpi b+ and 6 ASCMINER Block Erupter Asic.  
I am running minera and using cpuminer.
It looks like i am getting zero activity.
Below are some of the errors that I am getting.  
Any help would be appreciated.

Thank you,

[2014-12-01 19:48:23] Starting Stratum on stratum+tcp://mint.bitminter.com:3333
[2014-12-01 19:48:23] 0: GC3355 chip mining thread started, in SINGLE mode
[2014-12-01 19:48:23] 0: Open device /dev/ttyUSB1
[2014-12-01 19:48:23] 1: GC3355 chip mining thread started, in SINGLE mode
[2014-12-01 19:48:23] 1: Open device /dev/ttyUSB5
[2014-12-01 19:48:23] Stratum detected new block
[2014-12-01 19:48:23] New Job_id: f616-111 Diff: 16 Work_id: 36874f27
[2014-12-01 19:48:23] 2: GC3355 chip mining thread started, in SINGLE mode
[2014-12-01 19:48:23] 2: Open device /dev/ttyUSB4
[2014-12-01 19:48:23] 3: GC3355 chip mining thread started, in SINGLE mode
[2014-12-01 19:48:23] 3: Open device /dev/ttyUSB3
[2014-12-01 19:48:23] 4: GC3355 chip mining thread started, in SINGLE mode
[2014-12-01 19:48:23] 4: Open device /dev/ttyUSB2
[2014-12-01 19:48:23] 5: GC3355 chip mining thread started, in SINGLE mode
[2014-12-01 19:48:23] 5: Open device /dev/ttyUSB0
[2014-12-01 19:48:24] New Job_id: f617-44 Diff: 16 Work_id: 36874f27
[2014-12-01 19:48:24] 0: Failed reading firmware version
[2014-12-01 19:48:24] 0: Firmware version: 0xffffffff
[2014-12-01 19:48:24] 0: Unknown GC3355 Miner detected (chips=5)
[2014-12-01 19:48:24] 0: Set GC3355 core frequency to 800Mhz
[2014-12-01 19:48:24] 1: Failed reading firmware version
[2014-12-01 19:48:24] 1: Firmware version: 0xffffffff
[2014-12-01 19:48:24] 1: Unknown GC3355 Miner detected (chips=5)
[2014-12-01 19:48:24] 1: Set GC3355 core frequency to 800Mhz
[2014-12-01 19:48:24] 2: Failed reading firmware version
[2014-12-01 19:48:24] 2: Firmware version: 0xffffffff
[2014-12-01 19:48:24] 2: Unknown GC3355 Miner detected (chips=5)
[2014-12-01 19:48:24] 2: Set GC3355 core frequency to 800Mhz
[2014-12-01 19:48:24] 3: Failed reading firmware version
[2014-12-01 19:48:24] 3: Firmware version: 0xffffffff
[2014-12-01 19:48:24] 3: Unknown GC3355 Miner detected (chips=5)
[2014-12-01 19:48:24] 3: Set GC3355 core frequency to 800Mhz
[2014-12-01 19:48:24] 4: Failed reading firmware version
[2014-12-01 19:48:24] 4: Firmware version: 0xffffffff
[2014-12-01 19:48:24] 4: Unknown GC3355 Miner detected (chips=5)
[2014-12-01 19:48:24] 4: Set GC3355 core frequency to 800Mhz
[2014-12-01 19:48:24] 5: Failed reading firmware version
[2014-12-01 19:48:24] 5: Firmware version: 0xffffffff
[2014-12-01 19:48:24] 5: Unknown GC3355 Miner detected (chips=5)
[2014-12-01 19:48:24] 5: Set GC3355 core frequency to 800Mhz
[2014-12-01 19:48:25] 4: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:48:27] 2: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:48:30] 5: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:48:30] 4: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:48:32] 0: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:48:33] 2: Read error: Read 4 bytes, but expected 12 bytes

[2014-12-01 19:14:20.0090] New Job_id: 274e7 Diff: 8 Work_id: 2e8c230d
[2014-12-01 19:14:20.0278] 0: Resetting GC3355 chips
[2014-12-01 19:14:20.0378] 2: Resetting GC3355 chips
[2014-12-01 19:14:20.0478] 1: Resetting GC3355 chips
[2014-12-01 19:14:20.0877] 5: Resetting GC3355 chips
[2014-12-01 19:14:20.0897] 4: Resetting GC3355 chips
[2014-12-01 19:14:20.0905] 3: Resetting GC3355 chips
[2014-12-01 19:14:20.1309] 0: Dispatching new work to GC3355 cores (0x2e8c230d)
[2014-12-01 19:14:20.1409] 2: Dispatching new work to GC3355 cores (0x2e8c230d)
[2014-12-01 19:14:20.1507] 1: Dispatching new work to GC3355 cores (0x2e8c230d)
[2014-12-01 19:14:20.1946] 3: Dispatching new work to GC3355 cores (0x2e8c230d)
[2014-12-01 19:14:20.1969] 4: Dispatching new work to GC3355 cores (0x2e8c230d)
[2014-12-01 19:14:20.1977] 5: Dispatching new work to GC3355 cores (0x2e8c230d)
[2014-12-01 19:14:22.7448] 2: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:14:24.3047] 3: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:14:26.4979] 4: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:14:29.7774] API: Client 127.0.0.1 connected
[2014-12-01 19:14:29.8800] API: Client 127.0.0.1 connected
[2014-12-01 19:14:29.9824] API: Client 127.0.0.1 connected
[2014-12-01 19:14:29.9863] API: GET: stats
[2014-12-01 19:14:30.0609] 2: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:14:30.9720] 3: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:14:32.9613] 4: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:14:50.0074] New Job_id: 274e8 Diff: 8 Work_id: 2e8c230d
[2014-12-01 19:15:02.0552] API: Client 127.0.0.1 connected
[2014-12-01 19:15:02.1577] API: Client 127.0.0.1 connected
[2014-12-01 19:15:02.1617] API: GET: stats
[2014-12-01 19:15:02.6718] API: Client 127.0.0.1 connected
[2014-12-01 19:15:02.7743] API: Client 127.0.0.1 connected
[2014-12-01 19:15:03.4710] API: Client 127.0.0.1 connected
[2014-12-01 19:15:03.5733] API: Client 127.0.0.1 connected
[2014-12-01 19:15:03.6764] API: Client 127.0.0.1 connected
[2014-12-01 19:15:03.6803] API: GET: stats

https://farm9.staticflickr.com/8617/15927632805_2bd509663f_b.jpg

[michelem]

Hi,

I am very new to mining.  I have a rpi b+ and 6 ASCMINER Block Erupter Asic.  
I am running minera and using cpuminer.
It looks like i am getting zero activity.
Below are some of the errors that I am getting.  
Any help would be appreciated.

Thank you,

[2014-12-01 19:48:23] Starting Stratum on stratum+tcp://mint.bitminter.com:3333
[2014-12-01 19:48:23] 0: GC3355 chip mining thread started, in SINGLE mode
[2014-12-01 19:48:23] 0: Open device /dev/ttyUSB1
[2014-12-01 19:48:23] 1: GC3355 chip mining thread started, in SINGLE mode
[2014-12-01 19:48:23] 1: Open device /dev/ttyUSB5
[2014-12-01 19:48:23] Stratum detected new block
[2014-12-01 19:48:23] New Job_id: f616-111 Diff: 16 Work_id: 36874f27
[2014-12-01 19:48:23] 2: GC3355 chip mining thread started, in SINGLE mode
[2014-12-01 19:48:23] 2: Open device /dev/ttyUSB4
[2014-12-01 19:48:23] 3: GC3355 chip mining thread started, in SINGLE mode
[2014-12-01 19:48:23] 3: Open device /dev/ttyUSB3
[2014-12-01 19:48:23] 4: GC3355 chip mining thread started, in SINGLE mode
[2014-12-01 19:48:23] 4: Open device /dev/ttyUSB2
[2014-12-01 19:48:23] 5: GC3355 chip mining thread started, in SINGLE mode
[2014-12-01 19:48:23] 5: Open device /dev/ttyUSB0
[2014-12-01 19:48:24] New Job_id: f617-44 Diff: 16 Work_id: 36874f27
[2014-12-01 19:48:24] 0: Failed reading firmware version
[2014-12-01 19:48:24] 0: Firmware version: 0xffffffff
[2014-12-01 19:48:24] 0: Unknown GC3355 Miner detected (chips=5)
[2014-12-01 19:48:24] 0: Set GC3355 core frequency to 800Mhz
[2014-12-01 19:48:24] 1: Failed reading firmware version
[2014-12-01 19:48:24] 1: Firmware version: 0xffffffff
[2014-12-01 19:48:24] 1: Unknown GC3355 Miner detected (chips=5)
[2014-12-01 19:48:24] 1: Set GC3355 core frequency to 800Mhz
[2014-12-01 19:48:24] 2: Failed reading firmware version
[2014-12-01 19:48:24] 2: Firmware version: 0xffffffff
[2014-12-01 19:48:24] 2: Unknown GC3355 Miner detected (chips=5)
[2014-12-01 19:48:24] 2: Set GC3355 core frequency to 800Mhz
[2014-12-01 19:48:24] 3: Failed reading firmware version
[2014-12-01 19:48:24] 3: Firmware version: 0xffffffff
[2014-12-01 19:48:24] 3: Unknown GC3355 Miner detected (chips=5)
[2014-12-01 19:48:24] 3: Set GC3355 core frequency to 800Mhz
[2014-12-01 19:48:24] 4: Failed reading firmware version
[2014-12-01 19:48:24] 4: Firmware version: 0xffffffff
[2014-12-01 19:48:24] 4: Unknown GC3355 Miner detected (chips=5)
[2014-12-01 19:48:24] 4: Set GC3355 core frequency to 800Mhz
[2014-12-01 19:48:24] 5: Failed reading firmware version
[2014-12-01 19:48:24] 5: Firmware version: 0xffffffff
[2014-12-01 19:48:24] 5: Unknown GC3355 Miner detected (chips=5)
[2014-12-01 19:48:24] 5: Set GC3355 core frequency to 800Mhz
[2014-12-01 19:48:25] 4: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:48:27] 2: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:48:30] 5: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:48:30] 4: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:48:32] 0: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:48:33] 2: Read error: Read 4 bytes, but expected 12 bytes

[2014-12-01 19:14:20.0090] New Job_id: 274e7 Diff: 8 Work_id: 2e8c230d
[2014-12-01 19:14:20.0278] 0: Resetting GC3355 chips
[2014-12-01 19:14:20.0378] 2: Resetting GC3355 chips
[2014-12-01 19:14:20.0478] 1: Resetting GC3355 chips
[2014-12-01 19:14:20.0877] 5: Resetting GC3355 chips
[2014-12-01 19:14:20.0897] 4: Resetting GC3355 chips
[2014-12-01 19:14:20.0905] 3: Resetting GC3355 chips
[2014-12-01 19:14:20.1309] 0: Dispatching new work to GC3355 cores (0x2e8c230d)
[2014-12-01 19:14:20.1409] 2: Dispatching new work to GC3355 cores (0x2e8c230d)
[2014-12-01 19:14:20.1507] 1: Dispatching new work to GC3355 cores (0x2e8c230d)
[2014-12-01 19:14:20.1946] 3: Dispatching new work to GC3355 cores (0x2e8c230d)
[2014-12-01 19:14:20.1969] 4: Dispatching new work to GC3355 cores (0x2e8c230d)
[2014-12-01 19:14:20.1977] 5: Dispatching new work to GC3355 cores (0x2e8c230d)
[2014-12-01 19:14:22.7448] 2: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:14:24.3047] 3: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:14:26.4979] 4: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:14:29.7774] API: Client 127.0.0.1 connected
[2014-12-01 19:14:29.8800] API: Client 127.0.0.1 connected
[2014-12-01 19:14:29.9824] API: Client 127.0.0.1 connected
[2014-12-01 19:14:29.9863] API: GET: stats
[2014-12-01 19:14:30.0609] 2: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:14:30.9720] 3: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:14:32.9613] 4: Read error: Read 4 bytes, but expected 12 bytes
[2014-12-01 19:14:50.0074] New Job_id: 274e8 Diff: 8 Work_id: 2e8c230d
[2014-12-01 19:15:02.0552] API: Client 127.0.0.1 connected
[2014-12-01 19:15:02.1577] API: Client 127.0.0.1 connected
[2014-12-01 19:15:02.1617] API: GET: stats
[2014-12-01 19:15:02.6718] API: Client 127.0.0.1 connected
[2014-12-01 19:15:02.7743] API: Client 127.0.0.1 connected
[2014-12-01 19:15:03.4710] API: Client 127.0.0.1 connected
[2014-12-01 19:15:03.5733] API: Client 127.0.0.1 connected
[2014-12-01 19:15:03.6764] API: Client 127.0.0.1 connected
[2014-12-01 19:15:03.6803] API: GET: stats

Cpuminer is good for gridseed you can't use it for your hardware, please switch to Bfgminer

[michelem]

oh oh oh, Santa Claus is coming!



I'd like to have some guys testing the new Minera I'm going to release before Christmas. Please PM me if you can give a help.

Thanks!

[Xircom]

Jihaaaa...... cant wait.

Im willing to test up against ZEUS ASIC miners and MAT miners.

Xircom

[Xircom]

I hope the possibility to adjust mhz and chip count settings on each USB port is possible in the new version, so multiple miners can be used with the software.

[toptek]

I hope the possibility to adjust mhz and chip count settings on each USB port is possible in the new version, so multiple miners can be used with the software.

you can now with BFG   like this if  this is what you mean.




 -S all --set zeus@/dev/ttyUSB0:clock=328 --set zeus@/dev/ttyUSB0:chips=96 --set zeus@/dev/ttyUSB0:read=200 --set zeus@/dev/ttyUSB1:clock=240 --set zeus@/dev/ttyUSB1:chips=128 --set zeus@/dev/ttyUSB1:read=200 --set zeus@/dev/ttyUSB2:clock=328 --set zeus@/dev/ttyUSB2:chips=128 --set zeus@/dev/ttyUSB2:read=200

etc  and the read is adjustable 200 to 250 safely .

I was using one thunder x3 cyclone and hurrican x3 at one time at the same time with np  but i  would rather use them in there own PI which i do now .

unless you mean with each box per setting  that would be nice .but even BFG 5 still has the power Drain or cap problem or at least i hit it  after ten hours of using BFG 5 my miners either capped at one speed or lost to much hash so I went back to 4.3.1 . now I'm at steadily speeds higher or = to what each miner can do per miner, not over clocked.

[Xircom]

Yes, thats what I would like to see in the Web Gui for both CGminer and BFGminer.
Im running 40 Pi`s and would love to make adjustments on 1 miner and then save the image.

[toptek]

hi everyone,
i know this question has been asked before but is there support and what would i need to do for this to work with a  A2 TERMINATOR 86MHs by innosilicon?
 please try to give a clear answer understandable by everyone.

anyone capablle of answering this?

or this https://bitcointalk.org/index.php?topic=672969.0    .

[Xircom]

I hope the possibility to adjust mhz and chip count settings on each USB port is possible in the new version, so multiple miners can be used with the software.

you can now with BFG   like this if  this is what you mean.




 -S all --set zeus@/dev/ttyUSB0:clock=328 --set zeus@/dev/ttyUSB0:chips=96 --set zeus@/dev/ttyUSB0:read=200 --set zeus@/dev/ttyUSB1:clock=240 --set zeus@/dev/ttyUSB1:chips=128 --set zeus@/dev/ttyUSB1:read=200 --set zeus@/dev/ttyUSB2:clock=328 --set zeus@/dev/ttyUSB2:chips=128 --set zeus@/dev/ttyUSB2:read=200

etc  and the read is adjustable 200 to 250 safely .

I was using one thunder x3 cyclone and hurrican x3 at one time at the same time with np  but i  would rather use them in there own PI which i do now .

unless you mean with each box per setting  that would be nice .but even BFG 5 still has the power Drain or cap problem or at least i hit it  after ten hours of using BFG 5 my miners either capped at one speed or lost to much hash so I went back to 4.3.1 . now I'm at steadily speeds higher or = to what each miner can do per miner, not over clocked.

Yes, this is what I mean... I hate that I have to do all the old school command lines in the miner for each USB port. I would like to switch around miners on the PI´s without having concerns about right miner being on right USB port. Its ok to handle with 1-2-4 PI´s, but with 20 its a hell...

[toptek]

I hope the possibility to adjust mhz and chip count settings on each USB port is possible in the new version, so multiple miners can be used with the software.

you can now with BFG   like this if  this is what you mean.




 -S all --set zeus@/dev/ttyUSB0:clock=328 --set zeus@/dev/ttyUSB0:chips=96 --set zeus@/dev/ttyUSB0:read=200 --set zeus@/dev/ttyUSB1:clock=240 --set zeus@/dev/ttyUSB1:chips=128 --set zeus@/dev/ttyUSB1:read=200 --set zeus@/dev/ttyUSB2:clock=328 --set zeus@/dev/ttyUSB2:chips=128 --set zeus@/dev/ttyUSB2:read=200

etc  and the read is adjustable 200 to 250 safely .

I was using one thunder x3 cyclone and hurrican x3 at one time at the same time with np  but i  would rather use them in there own PI which i do now .

unless you mean with each box per setting  that would be nice .but even BFG 5 still has the power Drain or cap problem or at least i hit it  after ten hours of using BFG 5 my miners either capped at one speed or lost to much hash so I went back to 4.3.1 . now I'm at steadily speeds higher or = to what each miner can do per miner, not over clocked.

Yes, this is what I mean... I hate that I have to do all the old school command lines in the miner for each USB port. I would like to switch around miners on the PI´s without having concerns about right miner being on right USB port. Its ok to handle with 1-2-4 PI´s, but with 20 its a hell...

I'll bet . most i ever want to take it to is 10 miners is my goal .