 Show Posts
|
|
Pages: [1] 2 »
|
I have exactly the same problem with the uptime.. 3 of them running on Rpi , each with the USB adapter. Can't have them running for more than 2 days. Quite annoying to come home from work and see them dead every second day , then to heat up the room again and do some spam restart.. By the way. I just noticed on the board , one of the capacitors is not soldered properly , there is one of the small ones soldered instead .. Haven't seen it on the other two. Any idea why ? someone else found that ? -> https://i.imgur.com/RR7FMZU.jpg |
|
|
|
I don't know if you guys thought of this, but i think its better to make the miner stand sideways , rather than leaving it on one of the side. Works for me and stands rock solid. No need to worry about the heat under the board anymore ? :  Just unplugged it to reverse that handles just to be safer. And going back to mine. |
|
|
|
What did you do to fix it?
As i said before. Instead of using AM cgminer from crazy's minera, i compiled another one from github.com/blockerupter. Worked much better for me, filtered some of the errors and seemed to be booting the boards much better than before, i still had to do few restarts and after it boots up everything, i just leave it to do some work. From the beggining i thought it would be something terribly wrong, but it just the miner being stupid and not booting up properly. And also rather than spamming the miner restart button. Its better to keep reopening the cgminer through the terminal, more info, quicker and finding the boards better than through minera for some reason.. So whats up with yours atm.? Still struggling to start it up at all? Or do you get some hashrate going at least? Ops. I actually replied to your post: https://bitcointalk.org/index.php?topic=795477.msg9571067#msg9571067So I tried cgminer 4.7.0 like you suggested and I'm still getting the BET0 errors. I tried re-starting cgminer ~20 times and still the same error. When it starts do you leave it running for a while ? I'm still getting the errors also its spamming cgminer with it , but it stops at some point then it starts accepting shares and the hashrate shows up after that, sometimes its hashing very slow , usually when it boots up more than 500gh/s i leave it , then it slowly starts up all the chips on the boards , but eventually hashes on full power. Do you get any accepted shares at all ? is this what happens chris ? do you wait 10 minutes to see if it improves I recommend this as well, especially from a cold boot. I find they are a bit harder to get started when it's really cold, but once the prisma starts warming up, boards start coming to life. I agree on that , i could not boot it up when i had the miner outside where its colder, was not possible to boot it up at all. But now its inside with open windows and working, i thought that was just my imagination , good to know that i was right. This is interesting. I had my prisma in my workshop where it is currently ~35F. I brought the miner inside to warm up. I ran cgminer 4.7.0 for about 2-5 min each time. maybe that wasn't enough time. With that popped cap, did you have the older shipment or the most recent one? Supposedly the most recent shipment was packaged much better. There were issues with popping caps from the 1st shipment. 35F ?! Put that poor thing inside ! And try it there  |
|
|
|
What did you do to fix it?
As i said before. Instead of using AM cgminer from crazy's minera, i compiled another one from github.com/blockerupter. Worked much better for me, filtered some of the errors and seemed to be booting the boards much better than before, i still had to do few restarts and after it boots up everything, i just leave it to do some work. From the beggining i thought it would be something terribly wrong, but it just the miner being stupid and not booting up properly. And also rather than spamming the miner restart button. Its better to keep reopening the cgminer through the terminal, more info, quicker and finding the boards better than through minera for some reason.. So whats up with yours atm.? Still struggling to start it up at all? Or do you get some hashrate going at least? Ops. I actually replied to your post: https://bitcointalk.org/index.php?topic=795477.msg9571067#msg9571067So I tried cgminer 4.7.0 like you suggested and I'm still getting the BET0 errors. I tried re-starting cgminer ~20 times and still the same error. When it starts do you leave it running for a while ? I'm still getting the errors also its spamming cgminer with it , but it stops at some point then it starts accepting shares and the hashrate shows up after that, sometimes its hashing very slow , usually when it boots up more than 500gh/s i leave it , then it slowly starts up all the chips on the boards , but eventually hashes on full power. Do you get any accepted shares at all ? is this what happens chris ? do you wait 10 minutes to see if it improves I recommend this as well, especially from a cold boot. I find they are a bit harder to get started when it's really cold, but once the prisma starts warming up, boards start coming to life. I agree on that , i could not boot it up when i had the miner outside where its colder, was not possible to boot it up at all. But now its inside with open windows and working, i thought that was just my imagination , good to know that i was right. |
|
|
|
What did you do to fix it?
As i said before. Instead of using AM cgminer from crazy's minera, i compiled another one from github.com/blockerupter. Worked much better for me, filtered some of the errors and seemed to be booting the boards much better than before, i still had to do few restarts and after it boots up everything, i just leave it to do some work. From the beggining i thought it would be something terribly wrong, but it just the miner being stupid and not booting up properly. And also rather than spamming the miner restart button. Its better to keep reopening the cgminer through the terminal, more info, quicker and finding the boards better than through minera for some reason.. So whats up with yours atm.? Still struggling to start it up at all? Or do you get some hashrate going at least? Ops. I actually replied to your post: https://bitcointalk.org/index.php?topic=795477.msg9571067#msg9571067So I tried cgminer 4.7.0 like you suggested and I'm still getting the BET0 errors. I tried re-starting cgminer ~20 times and still the same error. When it starts do you leave it running for a while ? I'm still getting the errors also its spamming cgminer with it , but it stops at some point then it starts accepting shares and the hashrate shows up after that, sometimes its hashing very slow , usually when it boots up more than 500gh/s i leave it , then it slowly starts up all the chips on the boards , but eventually hashes on full power. Do you get any accepted shares at all ? |
|
|
|
What did you do to fix it?
As i said before. Instead of using AM cgminer from crazy's minera, i compiled another one from github.com/blockerupter. Worked much better for me, filtered some of the errors and seemed to be booting the boards much better than before, i still had to do few restarts and after it boots up everything, i just leave it to do some work. From the beggining i thought it would be something terribly wrong, but it just the miner being stupid and not booting up properly. And also rather than spamming the miner restart button. Its better to keep reopening the cgminer through the terminal, more info, quicker and finding the boards better than through minera for some reason.. So whats up with yours atm.? Still struggling to start it up at all? Or do you get some hashrate going at least? |
|
|
|
I can happily say that after 4 days of pain its hashing properly I split the power into two PSU's after all , so i can sleep without being worried.  To CrazyGuy: I might try that Cubian later if my miners arrive, looks like you're getting some extra hashrate with that |
|
|
|
For anyone having the BET0 error problems , for me the best working cgminer is 4.7.0 , compiled on Rpi from git : https://github.com/blockerupter/cgminer . Don't know why , but seems to be working better than the AM one for some reason. Also for the spamming button , better is to open up the minera terminal under the "System" , cd /var/www/minera/minera-bin/src/cgminer or AM or whatever your minera uses. And just start it up with the arguments or json config which is at /var/www/minera/conf/miner_conf.json , then its easier to spam it and see what is actually going on without having to turn on the log all the time , works better for me that way. This way i managed to start it up after few tries again, hashing 1400gh/s this time , 1170W power usage. 6% errors so far. Not sure if its good idea with my 1200W platinum corsair, its close enough.If i keep --bet-clk 23 i was hashing 1200ghs with no errors and 1070W , not sure whats better. Sorry for keeping the spam in the topic , i thought this could be helpfull. If you are running the prisma on 1 PSU then this a very bad idea. PSU really don't like running more than about 80% rated power continuously. You have a very high risk of damaging/destroying your PSU. I thought so , i should probably lower the clocks down a bit. |
|
|
|
For anyone having the BET0 error problems , for me the best working cgminer is 4.7.0 , compiled on Rpi from git : https://github.com/blockerupter/cgminer . Don't know why , but seems to be working better than the AM one for some reason. Also for the spamming button , better is to open up the minera terminal under the "System" , cd /var/www/minera/minera-bin/src/cgminer or AM or whatever your minera uses. And just start it up with the arguments or json config which is at /var/www/minera/conf/miner_conf.json , then its easier to spam it and see what is actually going on without having to turn on the log all the time , works better for me that way. This way i managed to start it up after few tries again, hashing 1400gh/s this time , 1170W power usage. 6% errors so far. Not sure if its good idea with my 1200W platinum corsair, its close enough. If i keep --bet-clk 23 i was hashing 1200ghs with no errors and 1070W , not sure whats better. Sorry for keeping the spam in the topic , i thought this could be helpfull. |
|
|
|
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  If you left debug and log file on, you may have filled up your SD card. I checked the log file through SSH, it didn't have more than 1MB , deleted that and cgminer started right again , now i have to get it running by spamming restart again and hopefully it will last longer. By the way , just came home and the other 2 miners still nowhere to be found :/ i thought they would come today already , but no luck. 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.
Nope I dont have BE controller. Unfortunately i didn't thought of that when i was buying prismas. I was naive enough that the miners would be easy enough to setup with the USB controllers... And they are nowhere to be found in the UK , was thinking about getting one and try it. But no idea where to look for it. I'm quite familiar with setting up the proxy from previous miners , but thank you for the help anyway . |
|
|
|
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 |
|
|
|
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. |
|
|
|
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-buyCan 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 ... |
|
|
|
|
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?
|
|
|
|
Put me down for one unit please Thank you. |
|
|
|
Put me down for one please Thank you. |
|
|
|
Are u getting all x's when u put the cube into overclock? If so, u prob have one bad board. try taking all the boards out and add back one by one in overclock mode until u find the bad board. make sure to shut down before adding each board.
Yep , all X's when its in overclock mode. Ill try them one by one . Thanks for the advice ! EDIT: You were right. Seems like 1 of the 6 boards is faulty as you said. 5/6 are working on high clock , when i plug the 6th one ill get all X's again , i guess i will have to contact someone for replacement then. Thanks a lot for the advice again. At least i know where is the problem now. |
|
|
|
Hello. Just wondering if anyone could possibly know why is my cube shutting off while switching it to high clock. Its connected to 1200w platinum corsair psu. Mining via BFGminer proxy on another machine , connected to btcguild stratum server. Checked the blades if all the screws all tighten up correctly as well. Low settings works perfectly , hashing 32gh/s. As soon as i switch it to high , it just stops mining , have to switch back to low and reboot psu completely to get it mining again afterwards. Soo everything seems correctly set up to me. Any ideas ? Im quite lost here , have no idea what else could be wrong.  |
|
|
|
|
Put me down for 1 as well if its still possible . Thank you.
|
|
|
|
|
