hi all
it seems to be that we become the same problem as last week!!!
at least the 3 last confirmed blocks 278659, 278676 and 278690 gone confirmed in stats. but don't move from unconfirmed reward to confirmed reward
*edit*
lol same time posting i see it on the last 3 blocks dont know if it also before
Hi! Can somebody tell me why blocks #278690 #278676 #278659 #278652 is confirmed but in my account payment for this blocks is still unconfirmed? It happened last week too, something about the payout account getting to low so the whole payment systems halts until BTC is added. Don’t know if that is the case here but that is what happened last week I believe. It was sorted out after about a day. I have only been around here a couple of weeks but so far everything always gets sorted out. then we have to check every reward on this pool?! every time? well I would check any pool because honest mistakes happen. You should always be looking out for yourself and not trusting someone else will do it for you. Just my opinion. The same situation happened a few days ago. It was probably due to limited BTC in the 'hot wallet' used for reward payments, so these were 'frozen' until that was rectified. You may raise a ticket on the support site for Slush (as I did), while I don't doubt the honesty of this pool, it certainly has its share of 'hiccups', which is why it makes sense to closely monitor reward confirmations/payments etc. Cheers |
|
|
|
|
I feel lucky that my 8board has not had so far issue in starting at 950. Since the last f/w update and using the drillbit cgminer 3.8.5 it has been working continuously without any 'glitches'. It has not crashed and no longer has 'hiccups' when the USB KVM is switched. Most of the time it is set to INT:53:2:950. The board is surrounded by 3 12cm fans, all blowing air into it. Running on Win7/64. The latest snapshot after about 20 hours (PC was restarted due to updates).
cgminer version 3.8.5 - Started: [2014-01-05 00:13:47]
--------------------------------------------------------------------------------
(5s):24.01G (avg):22.38Gh/s | A:380644 R:540 HW:12151 WU:312.6/m
ST: 2 SS: 0 NB: 139 LW: 549711 GF: 0 RF: 0
Connected to stratum.bitcoin.cz diff 18 with stratum as user xxxxx
Block: 26caaba0... Diff:1.42G Started: [20:36:29] Best share: 1.28M
--------------------------------------------------------------------------------
[P]ool management [S ]ettings [D ]isplay options [Q ]uit
DRB 0: E8 33.2C (35.9C) | 23.97G/22.38Gh/s | A:380662 R:540 HW:12151 WU:312.6/
m
[2014-01-05 20:36:12] Accepted 0d3e7939 Diff 19/18 DRB 0 pool 0
[2014-01-05 20:36:18] Accepted 020e005f Diff 125/18 DRB 0 pool 0
[2014-01-05 20:36:20] Accepted 0a62449f Diff 25/18 DRB 0 pool 0
(By the way, you can capture the text from a DOS box by right-click inside the box, select 'mark', select the text, then right-click again and paste a copy into a text editor, easier than doing a graphics screen capture).
Cheers
|
|
|
|
I'm pretty sure I got the same boards I sent. I believe I read that TK was keeping them sorted. The Atmel chip popped on one of my boards after I got them back. I believe it has been repaired now, but I'm still waiting on it to be delivered. As far as temperature...I just checked cgminer and the hottest any of my three boards have gone in the last three days is 32.7C. One hasn't gone over 29.0C. It's pretty cold here right now. heh..
Chad
If you have access to a temperature probe you could measure hotspots such as the regulator or the Atmel microcontroller. Do you think it's worth trying cgminer 3.8.5? I assume that your boards are all flashed to the latest f/w. I'm in the same city as Barntech, so it's quite warm here in summer. Cheers I'm running 3.8.5 now with the latest firmware. I also tried the official Windows 3.9.0 version with no luck. I tried running without hubs and with different usb cables. I'm out of ideas. Chad Chad, I'm out of ideas. You may want to try the 'brain trust' on the drillbit system forum and pursue this with Bantech. Good luck. |
|
|
|
I'm pretty sure I got the same boards I sent. I believe I read that TK was keeping them sorted. The Atmel chip popped on one of my boards after I got them back. I believe it has been repaired now, but I'm still waiting on it to be delivered. As far as temperature...I just checked cgminer and the hottest any of my three boards have gone in the last three days is 32.7C. One hasn't gone over 29.0C. It's pretty cold here right now. heh..
Chad
If you have access to a temperature probe you could measure hotspots such as the regulator or the Atmel microcontroller. Do you think it's worth trying cgminer 3.8.5? I assume that your boards are all flashed to the latest f/w. I'm in the same city as Barntech, so it's quite warm here in summer. Cheers |
|
|
|
Mine won't do anything above the stock settings now, but they ran great before the component change. It doesn't matter if I let them mine first or not. If I raise anything above 40:1:850 they go to asic timeout errors now. It's been frustrating because I've lost a lot of hash rate after the boards were repaired and my hardware errors increased by more than 11100%. That's not to say that my hw errors are bad now, but they were practically nonexistent when the boards were first delivered.
Chad
I hope that you manage to fix this with Barntech. Do you have anything to measure voltage or temperature? I guess that a basic check at the linear regulator output and looking for temp hot spots might give you some clues about the reason. Do you know if you received the same board or was it swapped in the repair process? (I had my board swapped). Cheers |
|
|
|
I am running the 8board with the drillbit cgminer 3.8.5 (because I had issues with 3.9.0 when tried it on my mining PC, however it works fine on a standalone PC with just the drillbit8 board). You may want to give 3.8.5 a try.
It looks like we are on to something with the need to change settings before it accepts the final OC value. Another user (Jedimister ?) reported using an automated scheme via cgwatcher to incrementally arrive at the desired OC value (check on the drillbitsystem forum).
Cheers
user cgwatcher to switch to 49:1:850 and then back to 53:2:950 and it seems to work How do you push different clock speeds through cgwatcher while cgminer is running? Can you load different conf files on the fly without restarting the miner? I just noticed under the test tab a box that says submit a command to the miner. Is that how you are doing it? Thanks! Chad I had very limited experience with cgwatcher, I doubt that it can change things 'on-the-fly' without restarting cgminer. It has some sort of a batch scheduler, so you should be able to automatically start with some settings then some time later shift to an OC setting. I think that Fleimeister explained this on the drillbitsystem forums. I am just running an instance of cgminer from a simple batch file. Using drillbit 3.8.5 for the 8board and the general release 3.9.0 for the Thumb (and bfgminer 3.9.0 for the other USB miners). Cheers |
|
|
|
I really doubt it is caused by the Pi. Before the component change my boards ran great on my Pi and three other computers. After the component change none of my boards will hash above default settings on the same computers. I'm hoping to hear back from Barntech about it soon. I think he went on vacation for the holidays. heh..
Chad
I tried the Pi briefly, and it crashed after a few hours, so went back to the Win7 laptop. Since doing the firmware update on the 8board it has been getting consistently to various 950 settings (the pre-mod board struggled to reach 950, had to re-connect USB, recycle power etc.). Since the last f/w update it is running consistently at int:53:2:950, has never had any crashes. Cheers |
|
|
|
been running with 53:2:950 since 00:34 today av 23GH/s 33C
ed. and yet again after a restart :950 does not work.....unresponsive asic
JBT: what OS are you running this on, and how do you invoke cgminer? (I think that you mentioned using cgwatcher - does it make a difference if you use cgminer directly?). Playing yesterday with my drillbit board settings I found that while it consistently starts at 53:2:950, sometimes the resulting hash rate is lower. I found that switching briefly to a different setting (52 or 54) and then to 53 brought the average hash rate back to the region of 22.5 GH/sec (WU=314.8, HW error~ 3-4%). Maybe there are some persistent control settings that need to be over-written? Cheers windows 7, cgminer 3.90, it runs ok on 53:2:850 but asic timeout on anything with :950 in. i tried starting via batch file or cgwatcher same results. power down unplug usb reconnect same thing,. ed. i tried 49:1:850 which outside recommended setting and it doesn't work but right after that 53:2:950 worked again,,,,,going to test this again later I am running the 8board with the drillbit cgminer 3.8.5 (because I had issues with 3.9.0 when tried it on my mining PC, however it works fine on a standalone PC with just the drillbit8 board). You may want to give 3.8.5 a try. It looks like we are on to something with the need to change settings before it accepts the final OC value. Another user (Jedimister ?) reported using an automated scheme via cgwatcher to incrementally arrive at the desired OC value (check on the drillbitsystem forum). Cheers Wasn't me... that was someone else... I'm one of the guys who are stuck at 850 and hashrates/HW best at the default non drillbit-options values. I think I'm limited by my Pi, so hopefully I'll be able to get my BeagleBoardBlack up and running soon with replacement USB cables. Apologies for 'implicating' you. It was actually Flemeister ( http://drillbitsystem.com/forum/index.php?topic=256.msg2391;topicseen#msg2391) Cheers |
|
|
|
been running with 53:2:950 since 00:34 today av 23GH/s 33C
ed. and yet again after a restart :950 does not work.....unresponsive asic
JBT: what OS are you running this on, and how do you invoke cgminer? (I think that you mentioned using cgwatcher - does it make a difference if you use cgminer directly?). Playing yesterday with my drillbit board settings I found that while it consistently starts at 53:2:950, sometimes the resulting hash rate is lower. I found that switching briefly to a different setting (52 or 54) and then to 53 brought the average hash rate back to the region of 22.5 GH/sec (WU=314.8, HW error~ 3-4%). Maybe there are some persistent control settings that need to be over-written? Cheers windows 7, cgminer 3.90, it runs ok on 53:2:850 but asic timeout on anything with :950 in. i tried starting via batch file or cgwatcher same results. power down unplug usb reconnect same thing,. ed. i tried 49:1:850 which outside recommended setting and it doesn't work but right after that 53:2:950 worked again,,,,,going to test this again later I am running the 8board with the drillbit cgminer 3.8.5 (because I had issues with 3.9.0 when tried it on my mining PC, however it works fine on a standalone PC with just the drillbit8 board). You may want to give 3.8.5 a try. It looks like we are on to something with the need to change settings before it accepts the final OC value. Another user (Jedimister ?) reported using an automated scheme via cgwatcher to incrementally arrive at the desired OC value (check on the drillbitsystem forum). Cheers |
|
|
|
My cgminer on PC with 6 boards drops boards after 2 hours. One after the other goes zombie.
I also have 6 boards on a pi and those just completely shut down after 8 hours or so. Have to turn power off and restart manually.
I have just a single drillbit8 board, and in the current configuration (latest 'test' firmware and the drillbit fork cgminer 3.8.5) it has not dropped out yet. It runs in company with another bunch of USB miners (1 Thumb, 3 blue/red Fury units, many BE's). None of these drops out, and the BE's have been running for more than a week at a time without any hiccups. I tried a rasberry pi (with the Minepeon distro from the drillbitsystem forum), it ran but dropped out after a few hours, so I gave up and went back to win7/64 on my old dual core laptop. You may want to explore cooling, power, sw & firmware configuration, running each board on a separate instance of cgminer etc. If you are running the boards on a mini-plane, you might consider running them separately. Use the 'divide and conquer' approach and document every step... Cheers |
|
|
|
been running with 53:2:950 since 00:34 today av 23GH/s 33C
ed. and yet again after a restart :950 does not work.....unresponsive asic
JBT: what OS are you running this on, and how do you invoke cgminer? (I think that you mentioned using cgwatcher - does it make a difference if you use cgminer directly?). Playing yesterday with my drillbit board settings I found that while it consistently starts at 53:2:950, sometimes the resulting hash rate is lower. I found that switching briefly to a different setting (52 or 54) and then to 53 brought the average hash rate back to the region of 22.5 GH/sec (WU=314.8, HW error~ 3-4%). Maybe there are some persistent control settings that need to be over-written? Cheers |
|
|
|
JBT, I get "unresponsive ASIC" errors when my board goes over 35C, I guess some boards are more sensitive than others.
Now running it in the basement where it's a lot cooler. Really helps to have a good fan though.
got two 40x40 fans on the heatsink mounted and a loose 60x60 just blowing on the other side steady at 33C so far. You may try to change the USB cable - see TK's post at http://drillbitsystem.com/forum/index.php?topic=256.30nope still get asic timeouts :950 then i tried 53:2:950 it works, this is all very inconstant Just to investigate the cable effect, I tried the original "multi-color" cable that came with the board, and it worked fine at 53:2:950 At least your are kept busy by the mysteries of your board...  tried another usb cable also got the unresponsive asic issue, so its not the usb cable. tried 54:2:850 works and 52:2:950 did not work. tried 53:2:950 and suddenly that worked. maybe a firmware issue board initialization issue? How do you 'start' your cgminer? If you use a batch file with drillbit options and you also saved your cgminer configuration, be aware that the settings are also saved in the cgminer.conf file. When you change the settings in the batch file that does not alter the cgminer.conf content and the batch file may not override those. I have fallen into this trap in the past, just want to make sure that you did not. I agree that the USB cable does not seem to make a difference in my case. Good luck |
|
|
|
Beastlymac,
I'm thinking of adding a couple more U1's to my order - should I use the same payment address as on my original lot?
Cheers
Yes you can just use the same payment address. Almost One Day LeftPM sent |
|
|
|
|
Beastlymac,
I'm thinking of adding a couple more U1's to my order - should I use the same payment address as on my original lot?
Cheers
|
|
|
|
JBT, I get "unresponsive ASIC" errors when my board goes over 35C, I guess some boards are more sensitive than others.
Now running it in the basement where it's a lot cooler. Really helps to have a good fan though.
got two 40x40 fans on the heatsink mounted and a loose 60x60 just blowing on the other side steady at 33C so far. You may try to change the USB cable - see TK's post at http://drillbitsystem.com/forum/index.php?topic=256.30nope still get asic timeouts :950 then i tried 53:2:950 it works, this is all very inconstant Just to investigate the cable effect, I tried the original "multi-color" cable that came with the board, and it worked fine at 53:2:950 At least your are kept busy by the mysteries of your board... |
|
|
|
|
New payout issue. Last reward payout did not make it to my wallet for over 30 minutes. Checking on the blockchain shows it with "unconfirmed transaction". It rings a bell about some incident in the past where Slush reward payments were 'stuck' because of unpaid transaction fees.
Has anyone else experienced this recently?
Edit: payment made it through after a bit over 2 hours. not sure about the cause.
|
|
|
|
JBT, I get "unresponsive ASIC" errors when my board goes over 35C, I guess some boards are more sensitive than others.
Now running it in the basement where it's a lot cooler. Really helps to have a good fan though.
got two 40x40 fans on the heatsink mounted and a loose 60x60 just blowing on the other side steady at 33C so far. You may try to change the USB cable - see TK's post at http://drillbitsystem.com/forum/index.php?topic=256.30 |
|
|
|
It depends where you live.
I live in Singapore.
Since it is so close i can, yes. THx, is it i need to pay you 0.075 + 0.02 = 0.95 BTC? you need to shift the decimal point.... 0.075 + 0.02 = 0.095 |
|
|
|
|
Just in case you did not notice, network difficulty just jumped to 1.42G (20% increase)
|
|
|
|
Maybe something got corrupted in the cgminer (or related cgwatcher) settings? Perhaps it's worth trying a 'clean instance' of cgminer, first by itself without cgwatcher. You may want to raise this at the DrillbitSystem forum where it may get more exposure/response from fellow drillbit users/developers.
Cheers
already tried it yesterday made no difference, now the strange part been running the whole day on 54:2:850 and tried 52:2:950 again now....... now the bloody thing works?! running 5min 19 -23 GH/s 32C hw 1.15% now at 0.75% What temp should the board be and which temp is high? ed. fan(s) on heat sink a must but fan on otherside recommended JBT, Congrats, persistence pays.... I agree about the cooling, now have 3 fans 'surrounding' the drillbit8 board. My board was previously connected directly to the PC USB2 port, yesterday I tried it through a hub with other devices and it worked fine with int:53:2:950 (has been running now for about 9 hours). Temp reported by cgminer 3.8.5 is 32.1C. I think that this board reached something like 36 C with poorer cooling and some people on the drillbitsystem forum http://drillbitsystem.com/forum/index.php?topic=230.0 show higher temps. In general running it hotter would reduce reliability and possibly trigger some on-chip protection mechanisms. It would be interesting if you find some consistent method to reach the OC settings reliably. Cheers HA! spoke to soon after a 5min router restart cgminer disconnected due to no internet no asic timeouts no hashing so back to 54:2:850 Maybe it's just a dodgy internet connection?! I guess that you need to keep exploring it if you want to get to the bottom/cause.... try the 'divide and conquer' approach, start with the simplest configuration available (single PC, one miner, direct USB connection, just cgminer etc.), change one thing at a time, document your steps so that you can retrace your path.... Good luck |
|
|
|
|
Show Posts
