|
Location?
Pictures also need to have a piece of paper with your user name and date written on it.
We have a TON of scammers here.
|
|
|
|
I run 2 g-blacks right now and they are loud, but are mining beasts. Good power consumption as well.
what software are they running on the controller? Is it a RPi? I bought them cheap without the Rpi in them. Simply plugged a USB cable into the hub inside each one and run them off of a windows box. This is them with 2 blades as well:  Sometimes spikes over 72. |
|
|
|
They run with BFGminer also. The earliest I've used is 4.5.0.
People were having so many problems using bfgminer on the original that I had to stop recommending it in this case. I'm not sure if it was continual user error or what, but you can have a look through the old thread. It's been rocking solid for me for over a month on a mixed batch of the new R-boxes as well as the older ones. No problems at all.  I have them clocked back some because the old r-boxes don't like the higher speeds. |
|
|
|
|
They run with BFGminer also. The earliest I've used is 4.5.0.
bfgminer.exe -S rkm:all --set rkm:clock=unsafe:310 -o stratum+tcp://us-east.multipool.us:8888 -u x -p x
|
|
|
|
|
Anyone know what size the fans are on the G-black?
|
|
|
|
|
I run 2 g-blacks right now and they are loud, but are mining beasts. Good power consumption as well.
|
|
|
|
Can anyone tell me how to use the unsafe:N command?
I have some of the small rockminers running at 290 along with some of the 110 GH units. Due to the 290 clockspeed set they are only hashing around 81 each. When I try to go in and adjust them up to 350 it returns the dangerous clockspeed and use the unsafe:N to force.
Thanks.
--set rkm:clock=unsafe:350 I did that like this in my bat file: bfgminer.exe -S rkm:all --set rkm:clock=unsafe:350 --set rkm:clock=290 It still gives the message to use the unsafe:N command? Wait, I get it now. The unsafe:350 replaces the regular set command. Any way to raise the limit, but still set the default clock to 290? |
|
|
|
Can anyone tell me how to use the unsafe:N command?
I have some of the small rockminers running at 290 along with some of the 110 GH units. Due to the 290 clockspeed set they are only hashing around 81 each. When I try to go in and adjust them up to 350 it returns the dangerous clockspeed and use the unsafe:N to force.
Thanks.
--set rkm:clock=unsafe:350 I did that like this in my bat file: bfgminer.exe -S rkm:all --set rkm:clock=unsafe:350 --set rkm:clock=290 It still gives the message to use the unsafe:N command? |
|
|
|
Can anyone tell me how to use the unsafe:N command?
I have some of the small rockminers running at 290 along with some of the 110 GH units. Due to the 290 clockspeed set they are only hashing around 81 each. When I try to go in and adjust them up to 350 it returns the dangerous clockspeed and use the unsafe:N to force.
Thanks.
--set rkm:clock=unsafe:350 You the man! |
|
|
|
|
Can anyone tell me how to use the unsafe:N command?
I have some of the small rockminers running at 290 along with some of the 110 GH units. Due to the 290 clockspeed set they are only hashing around 81 each. When I try to go in and adjust them up to 350 it returns the dangerous clockspeed and use the unsafe:N to force.
Thanks.
|
|
|
|
Someone has to still have some of these laying around!  |
|
|
|
|
Good luck. I just don't see it selling for that much.
|
|
|
|
Stepped back to 4.5.0 and it has no problems at all.
Try disabling the Coinbase check by appending /#skipcbcheck to the pool URL. Add /#skipcbcheck at the end of the pool URL's like this? stratum+tcp://us-east.multipool.us:8888/#skipcbcheck Exactly. Thanks! I'll have to keep an eye on it. It does it at random times. Crap, now I'm getting a ton of this:  It jumps around all of the different miners. I switched back to 4.5.0 for now. Might try 4.6.0 or 4.7.0 later. 4.8.0 and 4.9.0 give the errors shown for some reason. None of them on 4.5. |
|
|
|
Stepped back to 4.5.0 and it has no problems at all.
Try disabling the Coinbase check by appending /#skipcbcheck to the pool URL. Add /#skipcbcheck at the end of the pool URL's like this? stratum+tcp://us-east.multipool.us:8888/#skipcbcheck Exactly. Thanks! I'll have to keep an eye on it. It does it at random times. Crap, now I'm getting a ton of this: It jumps around all of the different miners. |
|
|
|
Stepped back to 4.5.0 and it has no problems at all.
Try disabling the Coinbase check by appending /#skipcbcheck to the pool URL. Add /#skipcbcheck at the end of the pool URL's like this? stratum+tcp://us-east.multipool.us:8888/#skipcbcheck Exactly. Thanks! I'll have to keep an eye on it. It does it at random times. |
|
|
|
Any idea what I can do to stop this from happening? The pools seem to be up just fine.  Any chance you can run a packet sniffer and see whats going on between the pool and miner? Have a good recommendation for one that will run on windows? Stepped back to 4.5.0 and it has no problems at all. Try disabling the Coinbase check by appending /#skipcbcheck to the pool URL. Add /#skipcbcheck at the end of the pool URL's like this? stratum+tcp://us-east.multipool.us:8888/#skipcbcheck |
|
|
|
Any idea what I can do to stop this from happening? The pools seem to be up just fine. Any chance you can run a packet sniffer and see whats going on between the pool and miner? Have a good recommendation for one that will run on windows? Stepped back to 4.5.0 and it has no problems at all. |
|
|
|
Any idea what I can do to stop this from happening? The pools seem to be up just fine. Any chance you can run a packet sniffer and see whats going on between the pool and miner? Have a good recommendation for one that will run on windows? |
|
|
|
Any idea what I can do to stop this from happening? The pools seem to be up just fine. |
|
|
|
|
Show Posts
