Shouldn't you have wiped the orderbooks though? The people not paying attention or sleeping will get screwed.
I placed an order, it may get filled, it may stand & wait. How does that screw me? You placed it based on information that's nearly two weeks old. That may be okay with you, but the right thing to do would be to wipe out the order books before resuming trading. |
|
|
|
|
Shouldn't you have wiped the orderbooks though? The people not paying attention or sleeping will get screwed.
|
|
|
|
...and then what? Can't get coins out of the cryptorush. |
|
|
|
True enough about the sd cards, sandisk + proper shutdown and they never seem to corrupt. I've yet to have one flake out on 12 rigs. The wobble thing is a very fair criticism though. Never should've been set up with that silly connector. I just wish the stratum proxy worked as failover (if primary pool fails, go to backup, so on), instead of splitting work. Just chuck chainminer and that proxy and run cgminer. Can anyone confirm cgminer working with V2.2 H-cards? I followed instructions found elsewhere in the forum, compiled from a certain github repo (can't find link right now) with --enable-bab and running cgminer did not hash, just gave spi errors. If I could get cgminer going for my V3 m/V2.2 H rig, I'd be very very happy  All of my hcards are v2 and running cgminer. Just nano driver-bab.c and change this: #define BAB_SPI_SPEED 96000 to this: #define BAB_SPI_SPEED 625000 run make again and you're gold. These options can be passed to cgminer on startup: --bab-options <arg> Set BaB options max:def:min:up:down:hz:delay:trf As mentioned above bfgminer also works with --enable-bfsb, but cgminer autotunes bitfury, uses far less of the rpi's weak cpu, and runs much better imo. I tried that but it seems that hashrate is consistently lower than with chainminer. I've got v2.3 h-cards. The v1.2 h-cards run on average about the same as with chainminer - or so it seems. I should mention that I did not change the SPI SPEED value for the v1.2 h-cards rigs only for the v2.3. Maybe I should let cgminer tune for a longer period of time? Watch the hw error rate. Cgminer is set to 1.0% tuneup and 10.0% tunedown so it wipes out huge numbers of hw errors. The mechanism it uses to do this is the osc so it's tuning chips all the way down to speed 32 over time. This causes power efficiency to improve dramatically over time, but if you don't want it to do that or you want it to do it in moderation then simply pass different values to cgminer at startup via the --bab-options parameter mentioned above. It's extremely flexible and capable of matching chainminer's performance. |
|
|
|
I tried changing the SPI_SPEED on my v1.2 cards, and it just gives me "BaB delay getting work" when it starts up. Change line 1663 in driver-bab.c from "false" to "true". Don't forget to run make again. |
|
|
|
It creates batch files in the directory of the associated mining program.
Could you explain what you just said? Like I have no idea how to comprehend tech language. Not entirely sure how to make it more clear, but I'll give it a shot. When you create a miner in guiminer scrypt, enter your credentials, devices, settings, extra flags etc, and then start mining, guiminer creates a .bat file in the relevant mining program's directory. This is the mechanism that directs the mining program. Perhaps a pic will help? This is the /guiminer-scrypt/cgminer directory on a win7 x64 machine.  |
|
|
|
|
It creates batch files in the directory of the associated mining program.
|
|
|
|
Insurance as we are paying fees!! what do they get used for!  Glad I didn't have much at this pathetic excuse for an exchange. Coinex can gth and take cryptorush with them. |
|
|
|
True enough about the sd cards, sandisk + proper shutdown and they never seem to corrupt. I've yet to have one flake out on 12 rigs. The wobble thing is a very fair criticism though. Never should've been set up with that silly connector. I just wish the stratum proxy worked as failover (if primary pool fails, go to backup, so on), instead of splitting work. Just chuck chainminer and that proxy and run cgminer. Can anyone confirm cgminer working with V2.2 H-cards? I followed instructions found elsewhere in the forum, compiled from a certain github repo (can't find link right now) with --enable-bab and running cgminer did not hash, just gave spi errors. If I could get cgminer going for my V3 m/V2.2 H rig, I'd be very very happy All of my hcards are v2 and running cgminer. Just nano driver-bab.c and change this: #define BAB_SPI_SPEED 96000 to this: #define BAB_SPI_SPEED 625000 run make again and you're gold. These options can be passed to cgminer on startup: --bab-options <arg> Set BaB options max:def:min:up:down:hz:delay:trf As mentioned above bfgminer also works with --enable-bfsb, but cgminer autotunes bitfury, uses far less of the rpi's weak cpu, and runs much better imo. |
|
|
|
|
can you transfer ltc out of cryptorush.in?
|
|
|
|
|
Thanks Stephan, haven't had a parsing error since updating to 0.9.9.2.
|
|
|
|
Well then it's just a couple of scammy companies colluding: http://digitaljournal.com/pr/1819167Deans & Lyons Lawyers Obtain a TRO against HashFast Technologies, "Freezing" its Bitcoin Wallets |
|
|
|
Hey Tommo, I dunno how feasible this is, but perhaps you could reach out to doublec, the op over at mmpool.bitparking.com. The difficulty increases are leaving that terrific btc DGM pool behind. If there was someway you could share hashing power when alts are down it may benefit both your pools. https://bitcointalk.org/index.php?topic=57148.0 |
|
|
|
Interesting... very interesting. I wonder if the same could be applied to BFL. Probably. Then there's cointerra...and amc/vmc. Actually someone should just shut down all the scammy american manufacturers. None of em are worth crap. |
|
|
|
True enough about the sd cards, sandisk + proper shutdown and they never seem to corrupt. I've yet to have one flake out on 12 rigs. The wobble thing is a very fair criticism though. Never should've been set up with that silly connector. I just wish the stratum proxy worked as failover (if primary pool fails, go to backup, so on), instead of splitting work. Just chuck chainminer and that proxy and run cgminer. |
|
|
|
|
see they can easily return my btc
|
|
|
|
|
I could have been more clear.
According to Kano, there was no code to disable or throttle the s1 in an overheat situation prior to the latest cgminer bitmain release(4.2).
Feb 07 firmware had cgminer v3.12 I believe.
|
|
|
|
|
It works with some issues. Icedrill is running sierras.
I'd be able to tell you a whole lot more if I had the sierra I paid for last frickin september.
|
|
|
|
|
Show Posts
