Just crossed the x5 times my pay threshold, still nada, zilch, zero payout.... c'mon Slush, give us our hard earned coins....  |
|
|
|
Looks like no body get paid on time now.there is any support email for pool service?
According to the FAQ on Slush'e web page, you can email support@bitcoin.cz. There is also a Live Support IRC channel. The pool admins seem to be aware of the problem and they are trying to solve it (based on a quick visit to the IRC channel). Hopefully the coins are not all lost.... |
|
|
|
Does anyone know when the payouts are going to startup again? They said because of high traffic but you would think some would be paid out?
Tried to check on the Live support, it seems that there is some sort of problem, and nobody on Slush is getting paid. They are looking into it. Think positive...  |
|
|
|
GO SLUSH 200% LUCK!!! GO GO GO !!! (Cheerleaders needed, please apply here)
Whats the best bang for 1500 dollars ASIC wise at the moment?
And why (OH WHY?) do I need to wait 360 seconds from logging in to my first post = It really GRINDS MY GEARS!!!
Just a thought, ASIC Cubes don't look to be good value.
Taa
Shshsh..... don't jinx it.... still recovering from some horrible luck.... the dreaded 15 hour block.... and then Slush holds on to our coins..... too early to celebrate.... (welcome aboard anyway...  |
|
|
|
My confirms are almost 25% beyond my payout amount.. haha this is getting interesting..
My confirms are about 4 times my payout threshold.... Perhaps Slush is trying to enforce this high 0.05BTC minimum payout.... bad move in my opinion, unless you want to drive away pool participants, noting that BTC Guild has a 0.01 min pay threshold. |
|
|
|
Well yesterday was a wash with that long block on slush ..then that was resolved..and due to extreme cold in the Midwest USA
charter Inet went poof for like 6 or 7hrs...and then the China announcement and btc down trend..sheesh.....had the day off
decided to stay in..likely a truck shooting around trying to run me down or some such if I go out
did that .00027 or whatever it was block ever get fixed or once confirmed it is a done deal even if maybe in error"
thanks
Searing
Block 21027 did not get fixed for me (it's already lost in the Stats history, below the surface...  |
|
|
|
vardiff not working or my miner got crasy?
I have restarted it and now it sits on diff 3 for 15+ minutes
Same here. Cgminer had some message that it lost connection to the pool, now it sits on diff 3 (which is probably not the right one for a 20GH/sec miner)  |
|
|
|
How often does Slush's pool pay after reaching your payout amount? Just curious.
The FAQ currently says it's now every 15 minutes. That hasn't been my experience, though. I am waiting for a payout and it has been past threshold for at least a couple of hours. It used to be at the top of the hour, but at the moment is seems random. Maybe they are being triggered manually at the moment. All I know is that it isn't consistent right now. I've been many hours over my threshold (which is below the 0.05 value in the FAQ), it is now almost 3 times my threshold but still no payout... Slush has been 'consistently inconsistent' with the payout regime, although it always happens eventually, but the delays are frustrating and unjustified |
|
|
|
|
I noticed that the Confirmed Reward on the main account page is not being updated in a reasonable time (say a couple of minutes) after a block was confirmed (on the Stats page). It's been sitting 'stuck' despite that the next block (21054) was confirmed about an hour ago.
The whole payout process needs to be consistent and timely.
Cheers
|
|
|
|
hi guys, i bought a usb hub for my 2 red fury miners and while running for a few mins they are declared sick then dead... but they are fine when i plug them back into regular usb slots and mine wout the hub. id rather use the hub as the miners block access to other ports. any hints anyone?
cant find similar posts on this here, sorry for repeat post if it was addressed already.
cheers
What sort of hub did you try? You need to have a powered hub with sufficient current capacity for your miners. You'd do better if you avoid connecting fans or other gadgets to ports close to your Red Furies. It should be a USB 2 hub, not USB 3. There is a thread somewhere on this site with a list of 'good' and 'bad' hubs for Block Erupters, which should probably apply also to RF's. Check that you see the devices in Device Manager if you use Windows. Make sure that they are detected with the correct driver assigned if you played with cgminer and bfgminer. My BF/RF's are using a very cheap 10 port USB2 hub with an alternative plug pack that delivers 4A instead of the original. The coexist with a bunch of other USB miners, some using bfgminer and some cgminer. Cheers |
|
|
|
I am more than double over the threshold (0.01) with no payout.... Will leave pool if no answer & payout like defineed in threshold.  Minimum has been .05 for several weeks now, if you are below that you should not be expecting a payout. In my case it does work below .05, but the timing and confirmed level at which payout occurs is 'random' and unrelated to my threshold setting. If we knew what the 'rule' applied is, it would make life easier... (I know that so far everything was paid out accurately, but the timing is an issue too) Cheers |
|
|
|
So is there a heat issue with these boards?
Did you guys overclock, and did any of you use a fan?
Mine were run stock with 2 fans on them. My single Drillbit 8 board runs also with 2 fans. It had no issues running overnight with int:52:2:950 settings (22.6 GH/sec average low R & HW rates, WU:316). The heatsink is warm to the touch, but not too hot. It has been running continuously for about 16 hours since the last config change. Cheers |
|
|
|
My payout finally made it... and to Slush's credit, it accurately tracks all the other data on submitted shares and individual block rewards. But if this inconsistency in payout timing persists, there are other pools (such as BTC Guild). |
|
|
|
i am reporting back
i tried the dead boards now they have been off for 19 hours and the green light did not come on once i connected them the molex connection
Looks like these boards are dead. Can anything be seen in a close inspection (like with a magnifying glass)? Can you verify that power arrives at the pins of the Molex connector on the board? |
|
|
|
My usual complaint.... payouts not happening again.... It's unclear if the 0.05 threshold is applied, my account settings are still on 0.01, but payouts have been happening in a random fashion, way above 0.01 and below 0.05. This is frustrating and annoying. I may 'spit the dummy' and explore elsewhere if this doesn't get sorted... |
|
|
|
I fell asleep and when I woke up I had a second board go dead on me. It doesn't power up anymore. Not sure what to do.
Chad
I guess the only thing that you can do now is to completely disconnect that board, let it cool down (edit: letting the polyswitches reset themselves, if they exist, sounds like a good idea), then try it again (ideally in an isolated environment with its own supply, pc etc.). Do you have reasonable cooling? Good luck |
|
|
|
I've got one board that hashes at full speed, but puts out about 75% hardware errors. I tried another board with the same power/usb cable and it works just fine. I've got three boards up and running on three different computers at the moment. They all seem to be averaging about 21.8 gigahashes at the recommended start settings.
Chad
What are your "starter" settings? My current settings are --drillbit-options int:53:2:850 This produces slightly higher results than 'stock' (int:40:1:850). had some issues with 950, but will continue exploring Trying --drillbit-options int:52:2:950 I am getting 'timing out unresponsive AsicX', the Drillbit 8 board doesn't start. went back to int:53:2:850 and all is fine. Cheers I am seeing the exact same behavior with 1 dillbit 8 board and a raspberry pi, 52:2:850 works fine but [anything]:2:950 causes the ASICs to timeout and then the board becomes unresponsive. With 52:2:850 there are no HW errors, but the hashrate is ~18Gh/s. Could this be a heating issue? If there was a heating issue I'd assume the HW error count would go up, but maybe there is some hidden throttling happening? I'm going to leave it running overnight to see where the speed averages out to by the morning. After more attempts, I managed to 'convince' the Drillbit 8 Board to run at --drillbit-options int:52:2:950 Had the 'timing out unresponsive Asic X' messages, and the board did not hash, so removed the USB cable to the board (while still powered and cgminer running), re-plugged the USB cable and now it got detected 'correctly' and is hashing nicely. I did not touch it since. I now have 2 fans blowing at it from both sides, the heatsink gets warm but not overly hot (can still be touched). Also installed a small heatsink on the 3 MosFets (as I wasn't given the 3 little ones when I got the board). The average hash rate is about 22.5 GH/sec, R:485 HW: 58 WU:315 after about 3.5 hours.  (the image is from an earlier time, but it has been going steady since) Cheers |
|
|
|
I've got one board that hashes at full speed, but puts out about 75% hardware errors. I tried another board with the same power/usb cable and it works just fine. I've got three boards up and running on three different computers at the moment. They all seem to be averaging about 21.8 gigahashes at the recommended start settings.
Chad
What are your "starter" settings? My current settings are --drillbit-options int:53:2:850 This produces slightly higher results than 'stock' (int:40:1:850). had some issues with 950, but will continue exploring Trying --drillbit-options int:52:2:950 I am getting 'timing out unresponsive AsicX', the Drillbit 8 board doesn't start. went back to int:53:2:850 and all is fine. Cheers |
|
|
|
I've got one board that hashes at full speed, but puts out about 75% hardware errors. I tried another board with the same power/usb cable and it works just fine. I've got three boards up and running on three different computers at the moment. They all seem to be averaging about 21.8 gigahashes at the recommended start settings.
Chad
What are your "starter" settings? My current settings are --drillbit-options int:53:2:850 This produces slightly higher results than 'stock' (int:40:1:850). had some issues with 950, but will continue exploring |
|
|
|
So far I'm only able to get my computer to recognize 4 out of my 8 boards, along with 5 USB drillbits.
Even this was a major chore. The best approach for a while was to start up cgminer-drill bit with the int:52:2:950 with just the USB drillbits plugged in. Unfortunately they don't hash as fast without the ext:250:1:950 command. I tried using both the ext and int parameters on the same line but no go.
Then, I would plug in one board and wait for the usb driver to be found, wait a little while and then plug in another board. That got me to 4 boards working but the 5th board caused zombies. I'm pulling power from 2 different computers and a 3rd standalone power supply (I'm short on molex connectors) so I should have enough power.
The whole setup is very sensitive and I've fought for the last 1/2 hour getting back to 4 boards and my 5 usb drillbits working. I'm going to leave it alone for now and try to set the other boards up on another computer.
I managed to separate the Thumb from the Drillbit board by using the --usb :1 entry on the batch file that starts each one of the instances (2 separate directories, each with its own instance of cgminer). I first start the Thumb with its batch file (which has the oc settings, different for the Thumb which accepts 'ext' clock, while the board only uses 'int' clock source). Once the Thumb is running, I connect the Drillbit Board, run its separate instance of cgminer with the selected --drillbit options.... This way they both co-exist on the same (ancient) laptop (together with a bunch of BE's, BF/RF devices). Cheers |
|
|
|
|
Show Posts
