[CLOSED] ASICMiner Prisma 1.4th/s - 1.47 BTC

[Chris_Sabian]

So i have got 1/3 of prismas on Friday so far. But now to be honest i dont want to get the rest . I thought after so many Asic miners was made these would work without much hassle.
But its exactly the opossite . Was much easier to set up 5 gpus litecion mining rig than this crap.
I was trying to make this work for 2 days without any luck. Most of the time i get these stupid "BET0: Unexpected value received" or sync errors.
Boards are connected in the right order with the switches being 100% correct.
I managed to get it running twice on pull power , just randomly , suddenly was running fine. Sometimes it boots up one or two boards , or just few chips, keeping 100ghs - 500ghs hashrate....

I have tried these tricks with switching to RM cgminer and back to AM , no help.
Turning cgminer off , unpluging cable , plugging back and running cgminer , nothing.
Imaged Rpi with original minera , compiled cgminer , same problem.
Tried raspbian with compiled cgminer , no change.
Tried even different computer , with windows, Linux mint and Ubuntu. Still getting the same errors.
Changing all the cables , trying different PSU's , plugging in different Usb slots on the Rpi.
Tried running the boards separately , sometimes they boot up , sometimes they dont , but never on full power.


So i guess there is not much hope to run this crap , unless someone has miraculously manage to get this work?

I've tried exactly the same thing and have had the same no hash results.

Thanks to everyone who has tried to help.

Many many thanks to CrazyGuy who has been amazing in his support  _{even though I used a different group-buy}

[CrazyGuy]

at planetcrypto  what is the watts for that. >>>> if you get 1600gh and I get 1280gh  my way has to be a lot safer since the watts are low.

What follows is a snapshot of our RPi controlled Prisma clocked @ 260.
In my feeble mind 2 things jump out at me versus the image you posted of your RPi controlled Prisma.
1) There is a difference of hashing rate ~300 GH/s.
2) There is a difference of operating temperature of ~70C (158F)

Almost 100% sure that the temp indicated by Minera is the temp of the RPi near one of the vertical connectors on the RPi B+.
The RPi that is controlling ours sits in the incoming air stream and is specifically positioned there to give an indication of incoming air temp.
The RPi that's controlling yours is (by it's own internal measurement) operating some place hot enough to boil water.
If the Rpi is that hot, how hot is the Prisma? and the components contained thereon.
While not having a pic of your configuration, Your Prisma may be operating at or near a thermal failure point. Even in a de-clocked operating mode/state.
Just food for thought.

I agree that the temps are in fact from the RPI. Here is why I think so, anyone please correct me if im wrong. Look at this picture where it says BET0 and BET1. I have both prismas on a single usb to uart adapter into the RPI B+. Here is the pic with the info circled in red https://i.imgur.com/agQ5sob.jpg So the info minera is reporting in my pic of 88.00F is without a doubt the RPI B+...I think

Yes, this is without a doubt the RPI temp. The block erupter driver does not provide an interface for pulling temperatures and I'm not certain if there are even temperature sensors on the Prisma Board.  I beleive the minera developer added temperature display for the RPI as RPIs have been known to reboot at high temps.

[CrazyGuy]

So i have got 1/3 of prismas on Friday so far. But now to be honest i dont want to get the rest . I thought after so many Asic miners was made these would work without much hassle.
But its exactly the opossite . Was much easier to set up 5 gpus litecion mining rig than this crap.
I was trying to make this work for 2 days without any luck. Most of the time i get these stupid "BET0: Unexpected value received" or sync errors.
Boards are connected in the right order with the switches being 100% correct.
I managed to get it running twice on pull power , just randomly , suddenly was running fine. Sometimes it boots up one or two boards , or just few chips, keeping 100ghs - 500ghs hashrate....

I have tried these tricks with switching to RM cgminer and back to AM , no help.
Turning cgminer off , unpluging cable , plugging back and running cgminer , nothing.
Imaged Rpi with original minera , compiled cgminer , same problem.
Tried raspbian with compiled cgminer , no change.
Tried even different computer , with windows, Linux mint and Ubuntu. Still getting the same errors.
Changing all the cables , trying different PSU's , plugging in different Usb slots on the Rpi.
Tried running the boards separately , sometimes they boot up , sometimes they dont , but never on full power.


So i guess there is not much hope to run this crap , unless someone has miraculously manage to get this work?

I've tried exactly the same thing and have had the same no hash results.

Thanks to everyone who has tried to help.

Many many thanks to CrazyGuy who has been amazing in his support  _{even though I used a different group-buy}

Can you both try running with logging enabled and debug enabled? You should get a lot more info, and maybe a hint at what's going on.

[philipma1957]

at planetcrypto  what is the watts for that. >>>> if you get 1600gh and I get 1280gh  my way has to be a lot safer since the watts are low.

What follows is a snapshot of our RPi controlled Prisma clocked @ 260.
In my feeble mind 2 things jump out at me versus the image you posted of your RPi controlled Prisma.
1) There is a difference of hashing rate ~300 GH/s.
2) There is a difference of operating temperature of ~70C (158F)

Almost 100% sure that the temp indicated by Minera is the temp of the RPi near one of the vertical connectors on the RPi B+.
The RPi that is controlling ours sits in the incoming air stream and is specifically positioned there to give an indication of incoming air temp.
The RPi that's controlling yours is (by it's own internal measurement) operating some place hot enough to boil water.
If the Rpi is that hot, how hot is the Prisma? and the components contained thereon.
While not having a pic of your configuration, Your Prisma may be operating at or near a thermal failure point. Even in a de-clocked operating mode/state.
Just food for thought.

I agree that the temps are in fact from the RPI. Here is why I think so, anyone please correct me if im wrong. Look at this picture where it says BET0 and BET1. I have both prismas on a single usb to uart adapter into the RPI B+. Here is the pic with the info circled in red https://i.imgur.com/agQ5sob.jpg So the info minera is reporting in my pic of 88.00F is without a doubt the RPI B+...I think

Yes, this is without a doubt the RPI temp. The block erupter driver does not provide an interface for pulling temperatures and I'm not certain if there are even temperature sensors on the Prisma Board.  I beleive the minera developer added temperature display for the RPI as RPIs have been known to reboot at high temps.

yes rpi's like it cool.  I use 2 fans to keep it cool

[Xtra7973]

Also I asked in this thread earlier if anyone got the prismas running minera to work with mobileminerapp on a cell phone as I had no luck running it. Well once again user error on my part. In the settings in minera where you enter your API key from mobileminer and email address you signed up with thats where I made the mistake. The API key I copy and pasted, so my error was my email address. https://i.imgur.com/GqdpDin.png instead of gmail.com I entered gnail.com and I just kept overlooking the obvious. Now mobile miner works on my cell and I can now check stats, change pools. start, stop and restart the miners from anywhere. Here is a screenshot of it from my cell phone https://i.imgur.com/7GkB19D.jpg If anyone has any problems setting it up just look at the obvious first, as I overlooked it. It's very simple to setup and get going. If anyone needs help with it just ask, I will try to do what I can. Also everyone with the BET0 problems, I just refreshed my setup last night and I had the BET0 and then a BET1 problem. All I did was just hit restart miner under miner in minera, now it did take about 10 trys, but it works, so you dont have to keep changing back and forth from Cgminer (rockminer fork) and Cgminer (asicminer fork) just keep spamming the restart button. It works and seems to be a faster way then doing all those other steps.

[Chris_Sabian]

So i have got 1/3 of prismas on Friday so far. But now to be honest i dont want to get the rest . I thought after so many Asic miners was made these would work without much hassle.
But its exactly the opossite . Was much easier to set up 5 gpus litecion mining rig than this crap.
I was trying to make this work for 2 days without any luck. Most of the time i get these stupid "BET0: Unexpected value received" or sync errors.
Boards are connected in the right order with the switches being 100% correct.
I managed to get it running twice on pull power , just randomly , suddenly was running fine. Sometimes it boots up one or two boards , or just few chips, keeping 100ghs - 500ghs hashrate....

I have tried these tricks with switching to RM cgminer and back to AM , no help.
Turning cgminer off , unpluging cable , plugging back and running cgminer , nothing.
Imaged Rpi with original minera , compiled cgminer , same problem.
Tried raspbian with compiled cgminer , no change.
Tried even different computer , with windows, Linux mint and Ubuntu. Still getting the same errors.
Changing all the cables , trying different PSU's , plugging in different Usb slots on the Rpi.
Tried running the boards separately , sometimes they boot up , sometimes they dont , but never on full power.


So i guess there is not much hope to run this crap , unless someone has miraculously manage to get this work?

I've tried exactly the same thing and have had the same no hash results.

Thanks to everyone who has tried to help.

Many many thanks to CrazyGuy who has been amazing in his support  _{even though I used a different group-buy}

Can you both try running with logging enabled and debug enabled? You should get a lot more info, and maybe a hint at what's going on.

I tried the logging and debug and I keep getting these errors:

 [2014-11-16 05:28:49] BET0: Nonce 00040000 from board 16, asic 13 for work 42
 [2014-11-16 05:28:49] BET0: Nonce Fix Failed

 [2014-11-16 05:29:26] ICA looking for AMU 10c4:ea60 but found 1d6b:0002 instead

 [2014-11-16 05:31:14] blockerupter: Read (0/1)

 [2014-11-16 05:31:14] BET0: Unexpected value 00 received
 [2014-11-16 05:31:14] BET0: BlockErupterRead (amt=0 err=-7 ern=25)

The BET0 error should be fixed with latest update from AM as of yesterday.

I'm thinking that I have bad uart adapter.

[Xtra7973]

yes rpi's like it cool.  I use 2 fans to keep it cool

http://imagizer.imageshack.us/v2/1280x1024q90/674/JhpDkR.jpg
[/quote]

I see you have the rpi B model with a case, I have the B+ no case, my temps were always around 84.00F max usually always around 80.00F, last night I logged into the pi and overclocked the pi's frequency to 450mhz without upping the voltage, just to see if anything changed with the hash rates or to see if the BET0 or the new BET1 errors I was getting on reboot/restart would go away. Since I overclocked it the only thing ive noticed is the slight temp increase to 88.00F and a slight, probably just by chance, lower rejection rate, not enough lower rejection rate to say it solved anything. But I have never seen my pi B+ get anywhere close to some of those temps you had. Do you think with the case on it maybe trapping some heat inside it? In two of your pictures I noticed one said 102.00F and the other said 104.00F. Was that before the fans? I have my pi sitting next to one prisma, right below them on the next shelf down is a window box fan blowing air up to keep the bottom of the prismas cool. Also two fans per prisma, push/pull, and one fan between the prismas blowing air down the middle of them. So I guess I was getting lucky with the placement of the pi as its getting cool from the box fan below it. I just wish we had a way to get the true temps of these prismas while running. I have a laser thermal gun, but the temps are sporadic depending where I point it at. The exhaust fans are around 120F on both units consistently. I am running them right now with no overclock as im worried because of the pictures posted. Better safe than sorry. Does anyone know if there is a way to find the true temps these prismas are running at? Are they even capable of giving us that information?

[philipma1957]

yes rpi's like it cool.  I use 2 fans to keep it cool

I see you have the rpi B model with a case, I have the B+ no case, my temps were always around 84.00F max usually always around 80.00F, last night I logged into the pi and overclocked the pi's frequency to 450mhz without upping the voltage, just to see if anything changed with the hash rates or to see if the BET0 or the new BET1 errors I was getting on reboot/restart would go away. Since I overclocked it the only thing ive noticed is the slight temp increase to 88.00F and a slight, probably just by chance, lower rejection rate, not enough lower rejection rate to say it solved anything. But I have never seen my pi B+ get anywhere close to some of those temps you had. Do you think with the case on it maybe trapping some heat inside it? In two of your pictures I noticed one said 102.00F and the other said 104.00F. Was that before the fans? I have my pi sitting next to one prisma, right below them on the next shelf down is a window box fan blowing air up to keep the bottom of the prismas cool. Also two fans per prisma, push/pull, and one fan between the prismas blowing air down the middle of them. So I guess I was getting lucky with the placement of the pi as its getting cool from the box fan below it. I just wish we had a way to get the true temps of these prismas while running. I have a laser thermal gun, but the temps are sporadic depending where I point it at. The exhaust fans are around 120F on both units consistently. I am running them right now with no overclock as im worried because of the pictures posted. Better safe than sorry. Does anyone know if there is a way to find the true temps these prismas are running at? Are they even capable of giving us that information?
[/quote]

 with garage closed the rpi runs 105-107 f  with garage open it runs  78 to 90 f depending on the clock.

I have added ceramic tiles under the prisma just in case.
I still can't seem to tame the temps with the  door shut.  I have clocked down to freq 190 and door shut I get to  1050 watts from 990 open in just a few hours.


_______________________________________________________________________________ _______________________________________________________________________________ _______________________________________________________________________________ ________________________

On the oc side  with the colder 40f weather  and door open gear is nice. This is freq 260

hash at 1545 gh watts at 1250    using top end evga 1600 p2 psu    so these are kind of as good as it gets for power


in f and c temps are great.

in f


in c



ceramic tiles over a piece of laminate flooring


low watts with door cooling in effect  freq 260 hash 1545 errors 6.96%   1216/1545 = 0.787 at the meter plug



high watts with door cooling in effect freq 260 hash 1545 errors 6.96% 1254/1545 = 0.811 at the meter plug

[aluam]

So i have got 1/3 of prismas on Friday so far. But now to be honest i dont want to get the rest . I thought after so many Asic miners was made these would work without much hassle.
But its exactly the opossite . Was much easier to set up 5 gpus litecion mining rig than this crap.
I was trying to make this work for 2 days without any luck. Most of the time i get these stupid "BET0: Unexpected value received" or sync errors.
Boards are connected in the right order with the switches being 100% correct.
I managed to get it running twice on pull power , just randomly , suddenly was running fine. Sometimes it boots up one or two boards , or just few chips, keeping 100ghs - 500ghs hashrate....

I have tried these tricks with switching to RM cgminer and back to AM , no help.
Turning cgminer off , unpluging cable , plugging back and running cgminer , nothing.
Imaged Rpi with original minera , compiled cgminer , same problem.
Tried raspbian with compiled cgminer , no change.
Tried even different computer , with windows, Linux mint and Ubuntu. Still getting the same errors.
Changing all the cables , trying different PSU's , plugging in different Usb slots on the Rpi.
Tried running the boards separately , sometimes they boot up , sometimes they dont , but never on full power.


So i guess there is not much hope to run this crap , unless someone has miraculously manage to get this work?

I've tried exactly the same thing and have had the same no hash results.

Thanks to everyone who has tried to help.

Many many thanks to CrazyGuy who has been amazing in his support  _{even though I used a different group-buy}

Can you both try running with logging enabled and debug enabled? You should get a lot more info, and maybe a hint at what's going on.

I tried the logging and debug and I keep getting these errors:

 [2014-11-16 05:28:49] BET0: Nonce 00040000 from board 16, asic 13 for work 42
 [2014-11-16 05:28:49] BET0: Nonce Fix Failed

 [2014-11-16 05:29:26] ICA looking for AMU 10c4:ea60 but found 1d6b:0002 instead

 [2014-11-16 05:31:14] blockerupter: Read (0/1)

 [2014-11-16 05:31:14] BET0: Unexpected value 00 received
 [2014-11-16 05:31:14] BET0: BlockErupterRead (amt=0 err=-7 ern=25)

The BET0 error should be fixed with latest update from AM as of yesterday.

I'm thinking that I have bad uart adapter.

I'm having quite similar to yours.
This log is from start of cgminer:

 [2014-11-16 20:15:33] Loaded configuration file /var/www/minera/conf/miner_conf.json
 [2014-11-16 20:15:33] USB scan devices: checking for BET devices
 [2014-11-16 20:15:33] RES: thread starting
 [2014-11-16 20:15:33] BET looking for and found BET 10c4:ea60
 [2014-11-16 20:15:33] USB lock blockerupter 1-5
 [2014-11-16 20:15:33] RES: blockerupter (1:5) lock=1
 [2014-11-16 20:15:33] USB res lock blockerupter 1-5
 [2014-11-16 20:15:33] RES: blockerupter (1:5) lock ok=1
 [2014-11-16 20:15:33] USB init - BET device 1:5 usbver=0110 prod='CP2102 USB to UART Bridge Controller' manuf='Silicon Labs' serial='0001'
 [2014-11-16 20:15:38] BlockErupter missing board: 0, received a6
 [2014-11-16 20:15:38] BlockErupter found Board: 1
 [2014-11-16 20:15:38] BlockErupter found Board: 2
 [2014-11-16 20:15:38] BlockErupter found Board: 3
 [2014-11-16 20:15:38] BET0: BlockErupterRead (amt=0 err=-7 ern=25)
 [2014-11-16 20:15:38] blockerupter: Read (0/1)
 [2014-11-16 20:15:38] BlockErupter missing board: 4, received 00
 [2014-11-16 20:15:38] BET0: BlockErupterRead (amt=0 err=-7 ern=25)
 [2014-11-16 20:15:38] blockerupter: Read (0/1)
 [2014-11-16 20:15:38] BlockErupter missing board: 5, received 00
 [2014-11-16 20:15:38] BET0: BlockErupterRead (amt=0 err=-7 ern=25)
 [2014-11-16 20:15:38] blockerupter: Read (0/1)
 [2014-11-16 20:15:38] BlockErupter missing board: 6, received 00
 [2014-11-16 20:15:38] BET0: BlockErupterRead (amt=0 err=-7 ern=25)
 [2014-11-16 20:15:39] blockerupter: Read (0/1)
 
These are going for another few seconds and then it goes to :


 [2014-11-16 20:15:39] USB: BET0 read1 buffering 12 extra bytes
 [2014-11-16 20:15:39] BET0: Unexpected value 00 received
 [2014-11-16 20:15:39] USB: BET0 read1 buffering 11 extra bytes
 [2014-11-16 20:15:39] BET0: Unexpected value 00 received
 [2014-11-16 20:15:39] USB: BET0 read1 buffering 10 extra bytes
 [2014-11-16 20:15:39] BET0: Unexpected value 00 received
 [2014-11-16 20:15:39] USB: BET0 read1 buffering 9 extra bytes
 [2014-11-16 20:15:39] BET0: Unexpected value 00 received
 [2014-11-16 20:15:39] USB: BET0 read1 buffering 8 extra bytes
 [2014-11-16 20:15:39] BET0: Unexpected value 00 received
 [2014-11-16 20:15:39] USB: BET0 read1 buffering 7 extra bytes
 [2014-11-16 20:15:39] BET0: Unexpected value 00 received
 [2014-11-16 20:15:39] USB: BET0 read1 buffering 6 extra bytes
 [2014-11-16 20:15:39] BET0: Unexpected value 00 received
 [2014-11-16 20:15:39] USB: BET0 read1 buffering 5 extra bytes

I have found this in the middle :

 [2014-11-16 20:15:39] Add BlockErupter with 5/32 Boards
 [2014-11-16 20:15:39] BET0: Set Clock to 120 MHz
 [2014-11-16 20:15:39] BET0: Set Diff Bits to 1
 [2014-11-16 20:15:39] BET0: Set nTime Rolling to 180 seconds

Why its setting clock to 120 mhz ? is its normal ?
I have tried putting --bet-clk 23 option , but never know if its works or not ...

[aluam]

Also I asked in this thread earlier if anyone got the prismas running minera to work with mobileminerapp on a cell phone as I had no luck running it. Well once again user error on my part. In the settings in minera where you enter your API key from mobileminer and email address you signed up with thats where I made the mistake. The API key I copy and pasted, so my error was my email address. https://i.imgur.com/GqdpDin.png instead of gmail.com I entered gnail.com and I just kept overlooking the obvious. Now mobile miner works on my cell and I can now check stats, change pools. start, stop and restart the miners from anywhere. Here is a screenshot of it from my cell phone https://i.imgur.com/7GkB19D.jpg If anyone has any problems setting it up just look at the obvious first, as I overlooked it. It's very simple to setup and get going. If anyone needs help with it just ask, I will try to do what I can. Also everyone with the BET0 problems, I just refreshed my setup last night and I had the BET0 and then a BET1 problem. All I did was just hit restart miner under miner in minera, now it did take about 10 trys, but it works, so you dont have to keep changing back and forth from Cgminer (rockminer fork) and Cgminer (asicminer fork) just keep spamming the restart button. It works and seems to be a faster way then doing all those other steps.

Strange but might be true about the restart button spam , sometimes i get up to 300gh/s , sometimes 500gh/s , but now it got up to incredible 1200 gh/s .. I guess i won't touch it for now and leave it so i can enjoy the hairdryer sound for a while.
Thanks for the advice man.

[Xtra7973]

Also I asked in this thread earlier if anyone got the prismas running minera to work with mobileminerapp on a cell phone as I had no luck running it. Well once again user error on my part. In the settings in minera where you enter your API key from mobileminer and email address you signed up with thats where I made the mistake. The API key I copy and pasted, so my error was my email address. https://i.imgur.com/GqdpDin.png instead of gmail.com I entered gnail.com and I just kept overlooking the obvious. Now mobile miner works on my cell and I can now check stats, change pools. start, stop and restart the miners from anywhere. Here is a screenshot of it from my cell phone https://i.imgur.com/7GkB19D.jpg If anyone has any problems setting it up just look at the obvious first, as I overlooked it. It's very simple to setup and get going. If anyone needs help with it just ask, I will try to do what I can. Also everyone with the BET0 problems, I just refreshed my setup last night and I had the BET0 and then a BET1 problem. All I did was just hit restart miner under miner in minera, now it did take about 10 trys, but it works, so you dont have to keep changing back and forth from Cgminer (rockminer fork) and Cgminer (asicminer fork) just keep spamming the restart button. It works and seems to be a faster way then doing all those other steps.

Strange but might be true about the restart button spam , sometimes i get up to 300gh/s , sometimes 500gh/s , but now it got up to incredible 1200 gh/s .. I guess i won't touch it for now and leave it so i can enjoy the hairdryer sound for a while.
Thanks for the advice man.

Im glad its working for you. I was just so frustrated trying it the other way with all those steps, and to get the same result each time. So I tried it that way, and about the tenth time it worked, hashing away now for a little over 22 hours without problems. I removed any arguments in the Startup extra commands (rc.local) box so im assuming its hashing at 230 and both units are around 1450 GH each with an error rate of about 5% total.

[Xtra7973]

in f and c temps are great.

in f
http://imagizer.imageshack.us/v2/1280x1024q90/538/0qX85c.png

Why does your pool hash rate only show 95.5+ GH/s? I take it thats not the prismas?

[Chris_Sabian]

Tried spamming restarting the miner and not luck.  Keep getting these errors:

[2014-11-16 21:49:12] Pushing work from pool 0 to hash queue
 [2014-11-16 21:49:12] Got work from get queue to get work for thread 0
 [2014-11-16 21:49:12] BET0: Sent work 23 to board 0
 [2014-11-16 21:49:12] USB: BET0 read1 buffering 54 extra bytes
 [2014-11-16 21:49:12] BET0: Nonce 000000ff from board 16, asic 12 for work 22
 [2014-11-16 21:49:12] BET0: Nonce Fix Failed
 [2014-11-16 21:49:13] USB scan devices: checking for BET devices
 [2014-11-16 21:49:13] BET looking for and found BET 10c4:ea60
 [2014-11-16 21:49:13] BET looking for BET 10c4:ea60 but found 0424:ec00 instead
 [2014-11-16 21:49:13] BET looking for BET 10c4:ea60 but found 0424:9512 instead
 [2014-11-16 21:49:13] BET looking for BET 10c4:ea60 but found 1d6b:0002 instead
 [2014-11-16 21:49:13] USB scan devices: checking for ICA devices


When I tried CrazyGuy's build from yesterday, I  can't even see the miner now in Minera.

Maybe 1 or 2 days more of trying to get it to hash then to the market to load this piece of crap.

[philipma1957]

in f and c temps are great.

in f

Why does your pool hash rate only show 95.5+ GH/s? I take it thats not the prismas?

16 x 95.5 = 1528  this version is a little bit older but it seems to be better then the new one.  poolside I am doing 1428


since error rate is 6%

 94 x 1528 = 1436  so   those are close  with rounding etc.

[ManeBjorn]

I just tried this now.  The weird thing is the unit ran until this afternoon then just detects one board or BET0 and does not hash.
Same error.  Just nothing.  I have tried a new PSU and cables.  Always the same thing.
Any ideas anyone?

Run this command to pull the latest and rebuild cgminer-AM

sudo /var/www/minera/./build_miner.sh cgminer-AM


ASICMiner checked in some updates to their fork about 5 hours ago surrounding Block erupter initialization. Worth a shot.

[CrazyGuy]

I just tried this now.  The weird thing is the unit ran until this afternoon then just detects one board or BET0 and does not hash.
Same error.  Just nothing.  I have tried a new PSU and cables.  Always the same thing.
Any ideas anyone?

Run this command to pull the latest and rebuild cgminer-AM

sudo /var/www/minera/./build_miner.sh cgminer-AM


ASICMiner checked in some updates to their fork about 5 hours ago surrounding Block erupter initialization. Worth a shot.

I actually had the same thing once I upgraded. I had to restart cgminer a few times to get it up and running. Might be a better idea to just go back to the last build.

[ManeBjorn]

Noted.
I will try it.
I am at a loss as to why it just stopped to begin with so weird after running so well for so long.

I just tried this now.  The weird thing is the unit ran until this afternoon then just detects one board or BET0 and does not hash.
Same error.  Just nothing.  I have tried a new PSU and cables.  Always the same thing.
Any ideas anyone?

Run this command to pull the latest and rebuild cgminer-AM

sudo /var/www/minera/./build_miner.sh cgminer-AM


ASICMiner checked in some updates to their fork about 5 hours ago surrounding Block erupter initialization. Worth a shot.

I actually had the same thing once I upgraded. I had to restart cgminer a few times to get it up and running. Might be a better idea to just go back to the last build.

[philipma1957]

Noted.
I will try it.
I am at a loss as to why it just stopped to begin with so weird after running so well for so long.

I just tried this now.  The weird thing is the unit ran until this afternoon then just detects one board or BET0 and does not hash.
Same error.  Just nothing.  I have tried a new PSU and cables.  Always the same thing.
Any ideas anyone?

Run this command to pull the latest and rebuild cgminer-AM

sudo /var/www/minera/./build_miner.sh cgminer-AM


ASICMiner checked in some updates to their fork about 5 hours ago surrounding Block erupter initialization. Worth a shot.

I actually had the same thing once I upgraded. I had to restart cgminer a few times to get it up and running. Might be a better idea to just go back to the last build.

many moons ago I had gridseed  build worked for 2-3 months then stopped on wemineltc. still worked on cex.io   a suggestion try 2 or 3 or 4 other pools

[aluam]

Also I asked in this thread earlier if anyone got the prismas running minera to work with mobileminerapp on a cell phone as I had no luck running it. Well once again user error on my part. In the settings in minera where you enter your API key from mobileminer and email address you signed up with thats where I made the mistake. The API key I copy and pasted, so my error was my email address. https://i.imgur.com/GqdpDin.png instead of gmail.com I entered gnail.com and I just kept overlooking the obvious. Now mobile miner works on my cell and I can now check stats, change pools. start, stop and restart the miners from anywhere. Here is a screenshot of it from my cell phone https://i.imgur.com/7GkB19D.jpg If anyone has any problems setting it up just look at the obvious first, as I overlooked it. It's very simple to setup and get going. If anyone needs help with it just ask, I will try to do what I can. Also everyone with the BET0 problems, I just refreshed my setup last night and I had the BET0 and then a BET1 problem. All I did was just hit restart miner under miner in minera, now it did take about 10 trys, but it works, so you dont have to keep changing back and forth from Cgminer (rockminer fork) and Cgminer (asicminer fork) just keep spamming the restart button. It works and seems to be a faster way then doing all those other steps.

Strange but might be true about the restart button spam , sometimes i get up to 300gh/s , sometimes 500gh/s , but now it got up to incredible 1200 gh/s .. I guess i won't touch it for now and leave it so i can enjoy the hairdryer sound for a while.
Thanks for the advice man.

Im glad its working for you. I was just so frustrated trying it the other way with all those steps, and to get the same result each time. So I tried it that way, and about the tenth time it worked, hashing away now for a little over 22 hours without problems. I removed any arguments in the Startup extra commands (rc.local) box so im assuming its hashing at 230 and both units are around 1450 GH each with an error rate of about 5% total.

Was nice to see big numbers for a bit , but it did not last very long , i dont know if it was because the debug was on or any other reason , but it made the cgminer crash after like 30 minutes. Now the Minera is stuck , can't restart cgminer and it wont start even after restarting Rpi. It will need new image on the SD i guess.
Back in the old story. Woohoo.

Tried spamming restarting the miner and not luck.  Keep getting these errors:

[2014-11-16 21:49:12] Pushing work from pool 0 to hash queue
 [2014-11-16 21:49:12] Got work from get queue to get work for thread 0
 [2014-11-16 21:49:12] BET0: Sent work 23 to board 0
 [2014-11-16 21:49:12] USB: BET0 read1 buffering 54 extra bytes
 [2014-11-16 21:49:12] BET0: Nonce 000000ff from board 16, asic 12 for work 22
 [2014-11-16 21:49:12] BET0: Nonce Fix Failed
 [2014-11-16 21:49:13] USB scan devices: checking for BET devices
 [2014-11-16 21:49:13] BET looking for and found BET 10c4:ea60
 [2014-11-16 21:49:13] BET looking for BET 10c4:ea60 but found 0424:ec00 instead
 [2014-11-16 21:49:13] BET looking for BET 10c4:ea60 but found 0424:9512 instead
 [2014-11-16 21:49:13] BET looking for BET 10c4:ea60 but found 1d6b:0002 instead
 [2014-11-16 21:49:13] USB scan devices: checking for ICA devices


When I tried CrazyGuy's build from yesterday, I  can't even see the miner now in Minera.

Maybe 1 or 2 days more of trying to get it to hash then to the market to load this piece of crap.

There is obviously something wrong with the miners, does'nt seem like many people are getting these. I guess people have to be lucky , to get properly working one 

[Xtra7973]

Also I asked in this thread earlier if anyone got the prismas running minera to work with mobileminerapp on a cell phone as I had no luck running it. Well once again user error on my part. In the settings in minera where you enter your API key from mobileminer and email address you signed up with thats where I made the mistake. The API key I copy and pasted, so my error was my email address. https://i.imgur.com/GqdpDin.png instead of gmail.com I entered gnail.com and I just kept overlooking the obvious. Now mobile miner works on my cell and I can now check stats, change pools. start, stop and restart the miners from anywhere. Here is a screenshot of it from my cell phone https://i.imgur.com/7GkB19D.jpg If anyone has any problems setting it up just look at the obvious first, as I overlooked it. It's very simple to setup and get going. If anyone needs help with it just ask, I will try to do what I can. Also everyone with the BET0 problems, I just refreshed my setup last night and I had the BET0 and then a BET1 problem. All I did was just hit restart miner under miner in minera, now it did take about 10 trys, but it works, so you dont have to keep changing back and forth from Cgminer (rockminer fork) and Cgminer (asicminer fork) just keep spamming the restart button. It works and seems to be a faster way then doing all those other steps.

Strange but might be true about the restart button spam , sometimes i get up to 300gh/s , sometimes 500gh/s , but now it got up to incredible 1200 gh/s .. I guess i won't touch it for now and leave it so i can enjoy the hairdryer sound for a while.
Thanks for the advice man.

Im glad its working for you. I was just so frustrated trying it the other way with all those steps, and to get the same result each time. So I tried it that way, and about the tenth time it worked, hashing away now for a little over 22 hours without problems. I removed any arguments in the Startup extra commands (rc.local) box so im assuming its hashing at 230 and both units are around 1450 GH each with an error rate of about 5% total.

Was nice to see big numbers for a bit , but it did not last very long , i dont know if it was because the debug was on or any other reason , but it made the cgminer crash after like 30 minutes. Now the Minera is stuck , can't restart cgminer and it wont start even after restarting Rpi. It will need new image on the SD i guess.
Back in the old story. Woohoo.

Tried spamming restarting the miner and not luck.  Keep getting these errors:

[2014-11-16 21:49:12] Pushing work from pool 0 to hash queue
 [2014-11-16 21:49:12] Got work from get queue to get work for thread 0
 [2014-11-16 21:49:12] BET0: Sent work 23 to board 0
 [2014-11-16 21:49:12] USB: BET0 read1 buffering 54 extra bytes
 [2014-11-16 21:49:12] BET0: Nonce 000000ff from board 16, asic 12 for work 22
 [2014-11-16 21:49:12] BET0: Nonce Fix Failed
 [2014-11-16 21:49:13] USB scan devices: checking for BET devices
 [2014-11-16 21:49:13] BET looking for and found BET 10c4:ea60
 [2014-11-16 21:49:13] BET looking for BET 10c4:ea60 but found 0424:ec00 instead
 [2014-11-16 21:49:13] BET looking for BET 10c4:ea60 but found 0424:9512 instead
 [2014-11-16 21:49:13] BET looking for BET 10c4:ea60 but found 1d6b:0002 instead
 [2014-11-16 21:49:13] USB scan devices: checking for ICA devices


When I tried CrazyGuy's build from yesterday, I  can't even see the miner now in Minera.

Maybe 1 or 2 days more of trying to get it to hash then to the market to load this piece of crap.

There is obviously something wrong with the miners, does'nt seem like many people are getting these. I guess people have to be lucky , to get properly working one 

Would you happen to have a BE controller to use instead of the pi? If so I would try using the BE controller and bfgminer 4.10 as a proxy. I had that setup before I got the USB to UART adapters and to be honest it was rock solid. Running the prismas off of minera and the USB to UART adapters seem to be a little bit more temperamental then just using the BE controller with bfgminer. I tried multiple versions of bfgminer and 4.10 was really solid. If you need any help or guidance setting it up I will do whatever I can with my limited knowledge to help you.