 Show Posts
|
|
Pages: [1] 2 3 »
|
|
I got the virus mail as well yesterday... Luckily deleted it directly!
|
|
|
|
|
is there a way to tweak the individual modules to run at a similar spread. I have in some of the boxes modules which run 10% less than the fasted module?
Is there something on the modules to adjust?
|
|
|
|
any one had any problems where the coindeska lcd screen is reading out 10024ghs and on the btcguild website it reads out 670ghs or 540ghs or 339ghs, is it the machines or the pool??? most confusing readindgs
I don't have the issue, I've setup 3 workers per desk and they all running at about 340 GH/s in average. |
|
|
|
what a Problem ? how to fix  Settings->Network->Save and Reboot |
|
|
|
Hi,@giorgiomassa,
emergency!!!!
here is a big problem, five hashing units of your product are broken itself..I contact your tech support,Mr/Miss. Christian,maybe he or she was busy and not reply me yesterday...
So, what should I do now? send the broken hash board to you directly?with the RMA code Christian told me before?,at that time,just 2 broken hash modules,but now, up to 5 broken modules..so I use the same RMA code ?
and address is :
to: Bitmine AG
centro la monda 2
6528 Camorino
Switzerland
??
I think I'd better send the broken modules back to you and you can check and fix them or change me a new one?....it's really bad experience in using your products(so many broken modules after using less than 20 days)...it's not as so good as I thought before....I don't know why but they just didn't work itself Suddenly..I didn't touch anything.I use turbo light model and power save light model....
and I check backplane(the red one), cables, PSU...everything is ok? and I power them off completely and power them on again,but still not work..they are not shown on the webinterface at all....
please let someone reply me as soon as possible....
could also be a power supply issue... |
|
|
|
what the hell is this  ?? i get this on some miner:Apr 29 18:24:05 raspberrypi user.warn kernel: [1077388.375790] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:28:48 raspberrypi user.warn kernel: [1077672.145775] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:02 raspberrypi user.warn kernel: [1077685.525716] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:15 raspberrypi user.warn kernel: [1077698.905789] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:28 raspberrypi user.warn kernel: [1077712.318571] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:42 raspberrypi user.warn kernel: [1077725.735686] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:55 raspberrypi user.warn kernel: [1077739.135701] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:35:24 raspberrypi user.warn kernel: [1078067.485718] w1_slave_driver 28-000005cc638d: Read failed CRC check I get these messages as well, but has no noticeable impact on performance... dont know but.... it looks like the errors you would get on a hard drive, up on unpacking a file that has some damage to it... i'm not so technicel to analyse this error -> but 2 minners shut down -> and i have to restart the cgminer by hand.... its not good, i cant sit 24/7 i front of the miner's... grml.... is there an solution ? If i am right... The errors can mean 2 things... 1, you have a bad sector on your disk, on your raspberrypi, disk: w1_slave_driver 28-000005cc638d If this is the case, the solution is normal to run scandisk on your drive, let it block out or sort the bad sectors, re-install any damage data when done (this is for HHD disk only, not SSD disk)... 2, you only have damage files on your raspberrypi, disk: w1_slave_driver 28-000005cc638d If this is the case, the normal solution is to re-install all data to disk to make sure all corrupted files are restored... Both are, for most part, do to the disk get bump/shocks on handling, transport or other moving it around (or age, but its all suppose to be new stuff, so...) (Also heavy magnetic fields can do this, but that's very unlikely) This is no problem on a normal computer, running normal OS (like windows or linux)... But on your miner.... might be a problem, if you did not back up the disk on the raspberrypi device before use (not the miner but your control device or what ever you whona call it), I have no miner OR raspberrypi device so i cant see what software or hardware they provide or what disk partition installations they might have made.... (knowing bitmine.ch's normal work, my guess is their is no partition installation on it and it just a raw OS on a single partition, that means you need new softwae from other location then the disk it selvf, aka; backup/re-instal disks or other medium) Their was a firmware update at some point, you might be lucky to be able to reinstall using that some how... But its also only if i am right in my view of the problem;) but i am 90 % sure that that's is the problem  Also if i am right, it is the raspberrypi's disk their is the problem, NOT the miner, 2 other fixes to this, cut be, to replace the device completely or to run your miner by a computer, not the raspberrypi's device you bought as extra device... I know that its crappy solutions, but unless you have the software to re-install the disk on the raspberrypi device, it can be a big problem doing any thing else about it;) Sorry realy thanks, i will test it... Your welcome... If it helps im just happy about it;P In any case its a read error of some kind, And i have NEVER seen a CRC read error, their was not disk/corruption of data related... (but their is a first time for every thing so i don't say that it is impossible) And even if i think about what else cut make and error like that the only other thing i can come up whit is if its a memory error, (but also a "slave driver" is a normal TAG for a disk, and it looks like a disk name, so i doubt it) But if its a mem problem, then their shut be other signs also, errors on in boot section and so on and you would be fuckt any way... I would still say that my first view of the problem is the most likely And my suggestions are only normal to run in any event of a system failure on any system, so test it out... If it don't help, your only option would be to send it back to bitmine.ch (becurse then its a hardware error on your memory, and you cant fix that yor selvf, or at least you need equipment, tools and a lot of knowledge to do it your selvf) And good luck on getting them to fix it .... LOL But at least test the MINER on a computer before involving bitmine.ch, i would not even trust that they would send you new hardware if you send it back to them.... Still might only be the raspberrypi device, their is a problem even if it is memory problem, which i still doubt A low grade laptop or something shut be more then enorf to run the miner on, so unless you live in a really bad place in the world, it shut not be a problem of finding/borrow one you can test it on before taking more steps Again I get these warnings all the time on all three desks I got here but it doesn't have a real impact on mining so far so I think it is sort of normal behaviour for these devices (or it got to do with the firmware version I'm running 201404251907 which came with the box (and is slightly newer of what is published on Bitmines website)) |
|
|
|
what the hell is this ?? i get this on some miner:Apr 29 18:24:05 raspberrypi user.warn kernel: [1077388.375790] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:28:48 raspberrypi user.warn kernel: [1077672.145775] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:02 raspberrypi user.warn kernel: [1077685.525716] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:15 raspberrypi user.warn kernel: [1077698.905789] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:28 raspberrypi user.warn kernel: [1077712.318571] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:42 raspberrypi user.warn kernel: [1077725.735686] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:55 raspberrypi user.warn kernel: [1077739.135701] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:35:24 raspberrypi user.warn kernel: [1078067.485718] w1_slave_driver 28-000005cc638d: Read failed CRC check I get these messages as well, but has no noticeable impact on performance... dont know but.... it looks like the errors you would get on a hard drive, up on unpacking a file that has some damage to it... i'm not so technicel to analyse this error -> but 2 minners shut down -> and i have to restart the cgminer by hand.... its not good, i cant sit 24/7 i front of the miner's... grml.... is there an solution ? did you change the default miner settings? Are they not running too hot (like > 55C, do they suck in cool air)? ne -> the ambient temp is around 17 - 25C -> the miner runs at 38 - 50 C what are you miner settings at this moment. did you check if the temp. sensors are properly seated between the cooling fins so the temp. readings are reliable (in mine they were sticking out in one of the desks) |
|
|
|
what the hell is this ?? i get this on some miner:Apr 29 18:24:05 raspberrypi user.warn kernel: [1077388.375790] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:28:48 raspberrypi user.warn kernel: [1077672.145775] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:02 raspberrypi user.warn kernel: [1077685.525716] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:15 raspberrypi user.warn kernel: [1077698.905789] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:28 raspberrypi user.warn kernel: [1077712.318571] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:42 raspberrypi user.warn kernel: [1077725.735686] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:55 raspberrypi user.warn kernel: [1077739.135701] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:35:24 raspberrypi user.warn kernel: [1078067.485718] w1_slave_driver 28-000005cc638d: Read failed CRC check I get these messages as well, but has no noticeable impact on performance... dont know but.... it looks like the errors you would get on a hard drive, up on unpacking a file that has some damage to it... i'm not so technicel to analyse this error -> but 2 minners shut down -> and i have to restart the cgminer by hand.... its not good, i cant sit 24/7 i front of the miner's... grml.... is there an solution ? did you change the default miner settings? Are they not running too hot (like > 55C, do they suck in cool air)? |
|
|
|
what the hell is this ?? i get this on some miner:Apr 29 18:24:05 raspberrypi user.warn kernel: [1077388.375790] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:28:48 raspberrypi user.warn kernel: [1077672.145775] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:02 raspberrypi user.warn kernel: [1077685.525716] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:15 raspberrypi user.warn kernel: [1077698.905789] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:28 raspberrypi user.warn kernel: [1077712.318571] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:42 raspberrypi user.warn kernel: [1077725.735686] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:29:55 raspberrypi user.warn kernel: [1077739.135701] w1_slave_driver 28-000005cc638d: Read failed CRC check Apr 29 18:35:24 raspberrypi user.warn kernel: [1078067.485718] w1_slave_driver 28-000005cc638d: Read failed CRC check I get these messages as well, but has no noticeable impact on performance... |
|
|
|
One of my 3 modules is not working properly (hashing at about 50 GHS down from 200) when not working in turbo mode. I think it happens whenever Vcore is set under 0.85V (0.83V is nominal).
Has anyone experienced this? Unfortunately this topic is littered with trolls so it's hard to find useful information. Thanks!
no issue here, I run at 850mV or 860mV using 1000MHz clock and 4000kbps without issues on 3x5 modules so far... |
|
|
|
Not that it will do any good whatsoever, but has anyone been able to get through via phone? I sit on hold burning money 10 mins or more then hang up with no answer. Beyond frustrating. Order #2833 send me my god damn refund, it's been 60 days since requested and approved wtf!
sorry but you will not reach anyone today is holiday in swiss. http://en.wikipedia.org/wiki/Feast_of_the_Ascensionbut you can reach them. i was always able to get through. maybe you have to wait a few minutes or try it multiple times. not that it will help you to get the money back if you reach them. :-) i ve phone at least 20!! times with them. there is no more i can do in a decent way to get my money back. i think it is time to strike a new path. I have called them few times during the day yesterday and today. Also sent them e-mails. No one picked up the phone and no reply which is strange as before I could easily get through and received replies within 24 hours. as stated above, it was a public holiday yesterday... It wasn't on Wednesday... yesterday was Thursday (CET) |
|
|
|
Not that it will do any good whatsoever, but has anyone been able to get through via phone? I sit on hold burning money 10 mins or more then hang up with no answer. Beyond frustrating. Order #2833 send me my god damn refund, it's been 60 days since requested and approved wtf!
sorry but you will not reach anyone today is holiday in swiss. http://en.wikipedia.org/wiki/Feast_of_the_Ascensionbut you can reach them. i was always able to get through. maybe you have to wait a few minutes or try it multiple times. not that it will help you to get the money back if you reach them. :-) i ve phone at least 20!! times with them. there is no more i can do in a decent way to get my money back. i think it is time to strike a new path. I have called them few times during the day yesterday and today. Also sent them e-mails. No one picked up the phone and no reply which is strange as before I could easily get through and received replies within 24 hours. as stated above, it was a public holiday yesterday... |
|
|
|
1000 GH/s desks running now at 900Mhz/850mV/4000Kbps now, seems to be stable with 2 extra fans sucking in 18C outside air and running at approx. 40 - 45C.
Delivering 1150 Gh/s per desk, no substantial increase in hardware errors...
Running 975Mhz/860mV/4000kpbs now at an average of 1190 GH/s at 43-48C |
|
|
|
|
1000 GH/s desks running now at 900Mhz/850mV/4000Kbps now, seems to be stable with 2 extra fans sucking in 18C outside air and running at approx. 40 - 45C.
Delivering 1150 Gh/s per desk, no substantial increase in hardware errors...
|
|
|
|
With the bitcoin rising (now €430/$588) you might want to reconsider requesting a refund and go for the ordered miner.
Why. They still wont profit eaven close to the preorder money people have paid to this compa«4ny. Every Bitmine customer got ripped off. Refund is only option. Delivered miners are bad investments. You can buy 1TH from other vendors much much cheaper. 1TH 1900$ 1.5TH 2500$ when would you receive those??? Ordered and paid Friday morning. Received and hashing today. Paid 1844$ for 1TH URL to product??? |
|
|
|
|
I understood some people experimented with (external) fans? Questions on the result:
1) which fans did you use (brand, URL, price)?
2) how did you connect them (split wires from existing fans???)
3) how effective was the solution (how much temperature drop)?
4) how much noisier is the solution (are the desks with the extra fans noticeable more noisier)?
greetings,
Rob
|
|
|
|
With the bitcoin rising (now €430/$588) you might want to reconsider requesting a refund and go for the ordered miner.
Why. They still wont profit eaven close to the preorder money people have paid to this company. Every Bitmine customer got ripped off. Refund is only option. Delivered miners are bad investments. You can buy 1TH from other vendors much much cheaper. 1TH 1900$ 1.5TH 2500$ when would you receive those??? |
|
|
|
|
With the bitcoin rising (now €430/$588) you might want to reconsider requesting a refund and go for the ordered miner.
Although communication sucks at Bitmine and the assembly quality has room for improvement I still think the product is overall rather nice and the company should deserve a chance to get in a more normalized mode and overcome their growing pains...
|
|
|
|
I think hr means fins from the heatsink? No?
I don't think ocing to 1100+ is a good idea. Some module will produce many hw error. 1080 is ok I guess.
translation error... |
|
|
|
|
Small observation yesterday: One of my three desk miners was running considerably cooler and I suspected this was a bit strange. I opened the box and noticed both the temp sensors (black wire running through the cooling fins of module 1 and 3) was sticking out of the cool fin. I pressed the sensors back between the cooling fins and now the desk is running a temperature in line with the other 2 boxes (so it will stop in time when it is running too hot).
Might be something you want to check on your desks as well...
|
|
|
|
|
