Speaking as not just a seller but also a manufacturer working 11-hour days for the last eight years or so - patience is a virtue. Rockmoney's usually up to his eyeballs dealing with all the various garbage Amazon throws at its sellers in exchange for the benefits of an unfair marketplace that embraces counterfeiting and withholds payouts for weeks at a time and can't always be relied upon to answer emails within a few minutes. But he'll take care of you if you let him.
And if he doesn't, I will.
It's possible your miner is the one he was discussing with me this morning.
Topic: GekkoScience NewPac / Terminus R606 (BM1387) Official Support Thread - page 83. (Read 61906 times)
May 16, 2019, 01:22:09 PM
May 16, 2019, 01:14:49 PM
@DaveF Happy for you. Mine is going back, and depending on how that goes I will probably just have to look at other equipment.
@Rockmoney the seller has not responded to my PM sent here, and calling the phone number listed just says "user busy."
@sidehack Just to rule out the Ubuntu 18.04 industrial computer that works fine with the newpac, but gets the chip errors with the R606, I got out a Dell Windows7 laptop. Installed the latest build and the R606 fails in exactly the same manner. Completely different hardware and different O/S.
Going to give @Rockmoney another couple hours, then just hit the return all button and be done with it.
@Rockmoney the seller has not responded to my PM sent here, and calling the phone number listed just says "user busy."
@sidehack Just to rule out the Ubuntu 18.04 industrial computer that works fine with the newpac, but gets the chip errors with the R606, I got out a Dell Windows7 laptop. Installed the latest build and the R606 fails in exactly the same manner. Completely different hardware and different O/S.
Going to give @Rockmoney another couple hours, then just hit the return all button and be done with it.
May 16, 2019, 07:53:37 AM
Wes0310, according to the device line, cgminer is only detecting 1 chip on that stick. If it's brand-new (just received), it's probably damaged and should be replaced. If it's not new, could be the voltage is set way too low and it's not picking up properly, or the voltage is set too high and it's overheating.
Adjust the voltage up a bit, make sure you have good cooling, and try it again. Sometimes an unplug-replug will take care of that.
gt_addict, I had similar issues with temp sensors not reporting on some advanced-controls prototype sticks last summer but chalked it up to the firmware. This one's code is much more robust, and when I first got temp sensors going I let one run for a week without any hiccups. But something's for sure going on, and the "quick fix" is just disabling that part pending a redesign. I can probably get the same functionality out of the microcontroller's internal temp sensor, though it's not as close to the heatsinks so won't read out the same which is why I didn't want to rely on it. Might have that implemented before Batch 2 starts shipping.
Additionally, I have a couple pods here that, on volt setting 4, could only hit something like 535MHz but were otherwise great. So everything will be tested at Volt 4 but with a second round at Volt 5 if it's only a few percent low. We did a similar adjust-retest for the weaker 2Pacs and nobody complained.
Adjust the voltage up a bit, make sure you have good cooling, and try it again. Sometimes an unplug-replug will take care of that.
gt_addict, I had similar issues with temp sensors not reporting on some advanced-controls prototype sticks last summer but chalked it up to the firmware. This one's code is much more robust, and when I first got temp sensors going I let one run for a week without any hiccups. But something's for sure going on, and the "quick fix" is just disabling that part pending a redesign. I can probably get the same functionality out of the microcontroller's internal temp sensor, though it's not as close to the heatsinks so won't read out the same which is why I didn't want to rely on it. Might have that implemented before Batch 2 starts shipping.
Additionally, I have a couple pods here that, on volt setting 4, could only hit something like 535MHz but were otherwise great. So everything will be tested at Volt 4 but with a second round at Volt 5 if it's only a few percent low. We did a similar adjust-retest for the weaker 2Pacs and nobody complained.
May 16, 2019, 07:15:12 AM
Reading through these oddball problems with temp sensors and blinking lights I was wondering if there could well be a link to it being shipped and the handling of it? As you said you haven’t had any problems with testing but now people are having issues and the only common factor is shipping or possible storage (although these are selling like hotcakes so I doubt its that).
Could it be possible something has become unseated/worked loose?
P.S. sidehack please dont take that as a slur on your workmanship. I love your gear and its robust build quality 👍🏼
Could it be possible something has become unseated/worked loose?
P.S. sidehack please dont take that as a slur on your workmanship. I love your gear and its robust build quality 👍🏼
If you take a look at the Apollo LTC miner discussion you can see jstefanop had some shipping issues with them. They were shipped in a very sold box that was very well padded and people still had miners coming in damaged.
Mine came in yesterday and is hashing away with no issues. Can't get it above 750G, going to play with it more today.
-Dave
May 16, 2019, 04:53:05 AM
Did someone play baseball with it or something?
Reading through these oddball problems with temp sensors and blinking lights I was wondering if there could well be a link to it being shipped and the handling of it? As you said you haven’t had any problems with testing but now people are having issues and the only common factor is shipping or possible storage (although these are selling like hotcakes so I doubt its that).
Could it be possible something has become unseated/worked loose?
P.S. sidehack please dont take that as a slur on your workmanship. I love your gear and its robust build quality 👍🏼
May 16, 2019, 01:17:41 AM
New build (a62385f)...
I can confirm the R606 Terminus Pod Miners are working with this build on Prohashing.com, and with AsicBoost enabled!
Anyway, thanks again vh for the new build, giving users even more, easier options to use these beasts!
Hello, i have a problem with my new pac.
I always get the error missing nonces.
Can you help me ?
I always get the error missing nonces.
Can you help me ?
For starters, the work difficulty of 32.8k for a single NewPac stick is much too high, and would rarely find shares. Have you tried a different mining pool and set your worker difficulty to ~5x expected hashrate in gigahashes? Are you using the latest vh/gekko build of cgminer with the proper syntax?
May 16, 2019, 12:14:53 AM
What hub are you using? e.g. Gekko-science hub is very good for this purpose, due to the way its build. Chinese brand hubs are often causing problems.
What powersupply are you using? single rail 12V is very much advised, or an HP server powersupply.
Are you using cooling? newpac's are very sensitive to temperature. Slight moving of are is enough @ 100 Mhz, higher freq need more intensive cooling.
Also make sure your USB cable is of good quality.
See also previous pages, maybe a solution there.
Can you post your setup? Hardware, OS, HUB, PS, cooling.
My 1st thought is you're having a problem with hub and/or powersupply.
See first page for the above.
What powersupply are you using? single rail 12V is very much advised, or an HP server powersupply.
Are you using cooling? newpac's are very sensitive to temperature. Slight moving of are is enough @ 100 Mhz, higher freq need more intensive cooling.
Also make sure your USB cable is of good quality.
See also previous pages, maybe a solution there.
Can you post your setup? Hardware, OS, HUB, PS, cooling.
My 1st thought is you're having a problem with hub and/or powersupply.
Q. Something doesn't look correct..
Here are some of the more common ways to address issue(s):
Isolate to test only the usb stick
Remove any usb extension cables.
Try a single device without any other accessories drawing power (usb fan, other miners).
Plug into a into different computer.
Check for and git the latest build of cgminer.
Look through the README.txt file for relevant notes.
Handling problems in Windows:
Switch to linux Ubuntu or Raspbian.
Enable High Performance in Power Options Setting.
Confirm the WinUSB driver is attached to the device.
Reboot the computer.
Try one cgminer process per device with "--usb :1".
Search for / post the details to this thread.
Here are some of the more common ways to address issue(s):
Isolate to test only the usb stick
Remove any usb extension cables.
Try a single device without any other accessories drawing power (usb fan, other miners).
Plug into a into different computer.
Check for and git the latest build of cgminer.
Look through the README.txt file for relevant notes.
Handling problems in Windows:
Switch to linux Ubuntu or Raspbian.
Enable High Performance in Power Options Setting.
Confirm the WinUSB driver is attached to the device.
Reboot the computer.
Try one cgminer process per device with "--usb :1".
Search for / post the details to this thread.
See first page for the above.
May 16, 2019, 12:00:33 AM
Hello, i have a problem with my new pac.
I always get the error missing nonces.
Can you help me ?
I always get the error missing nonces.
Can you help me ?
Code:
-------------------------------------------------------------------------------
(5s):344.2K (1m):1.680G (5m):2.649G (15m):1.292G (avg):6.193Gh/s
A:0 R:0 HW:2 WU:86.0/m
Connected to stratum.antpool.com diff 32.8K with stratum as user Wes031.PC
Block: 27bd0ac6... Diff:6.7T Started: [06:56:00.510] Best share: 759
--------------------------------------------------------------------------------
[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
0: GSH 10030315: BM1387:1 100.00MHz������| 344.2K / 6.193Gh/s WU: 86.0/m
--------------------------------------------------------------------------------
[2019-05-16 06:55:59.494] Started cgminer 4.11.1
[2019-05-16 06:55:59.494] Loaded configuration file /root/.cgminer/cgminer.conf
[2019-05-16 06:55:59.494] Probing for an alive pool
[2019-05-16 06:55:59.614] Pool 1 difficulty changed to 32768
[2019-05-16 06:55:59.748] Pool 2 difficulty changed to 32768
[2019-05-16 06:55:59.757] Pool 0 difficulty changed to 32768
[2019-05-16 06:56:00.484] Switching to pool 1 stratum+tcp://stratum.antpool.com:443 - first alive pool
[2019-05-16 06:56:00.510] Network diff set to 6.7T
[2019-05-16 06:56:00.605] Pool 0 stratum+tcp://stratum.antpool.com:443 alive, testing stability
[2019-05-16 06:56:00.606] Switching to pool 0 stratum+tcp://stratum.antpool.com:443
[2019-05-16 06:56:00.631] Stratum from pool 0 requested work restart
[2019-05-16 06:56:00.762] GSH 0: Toggling ASIC nRST to reset
[2019-05-16 06:56:00.856] GSH 0: NewPac Bitcoin Miner (10030315)
[2019-05-16 06:56:01.149] GSH 0: found 2 chip(s)
[2019-05-16 06:56:01.208] GSH 0: setting frequency to 100.00MHz
[2019-05-16 06:56:01.218] GSH 0: open cores @ 100.00MHz
[2019-05-16 06:56:02.432] GSH 0: start work @ 100.00MHz
[2019-05-16 06:57:03.185] GSH 0: missing nonces
[2019-05-16 06:57:03.219] GSH 0: Toggling ASIC nRST to reset
[2019-05-16 06:57:04.637] GSH 0: setting frequency to 100.00MHz
[2019-05-16 06:57:53.073] GSH 0: missing nonces
[2019-05-16 06:57:53.102] GSH 0: Toggling ASIC nRST to reset
[2019-05-16 06:57:54.539] GSH 0: setting frequency to 100.00MHz
[2019-05-16 06:58:43.571] GSH 0: missing nonces
[2019-05-16 06:58:43.618] GSH 0: Toggling ASIC nRST to reset
[2019-05-16 06:58:45.082] GSH 0: setting frequency to 100.00MHz
[2019-05-16 06:59:33.458] GSH 0: missing nonces
[2019-05-16 06:59:33.550] GSH 0: Toggling ASIC nRST to reset
(5s):344.2K (1m):1.680G (5m):2.649G (15m):1.292G (avg):6.193Gh/s
A:0 R:0 HW:2 WU:86.0/m
Connected to stratum.antpool.com diff 32.8K with stratum as user Wes031.PC
Block: 27bd0ac6... Diff:6.7T Started: [06:56:00.510] Best share: 759
--------------------------------------------------------------------------------
[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
0: GSH 10030315: BM1387:1 100.00MHz������| 344.2K / 6.193Gh/s WU: 86.0/m
--------------------------------------------------------------------------------
[2019-05-16 06:55:59.494] Started cgminer 4.11.1
[2019-05-16 06:55:59.494] Loaded configuration file /root/.cgminer/cgminer.conf
[2019-05-16 06:55:59.494] Probing for an alive pool
[2019-05-16 06:55:59.614] Pool 1 difficulty changed to 32768
[2019-05-16 06:55:59.748] Pool 2 difficulty changed to 32768
[2019-05-16 06:55:59.757] Pool 0 difficulty changed to 32768
[2019-05-16 06:56:00.484] Switching to pool 1 stratum+tcp://stratum.antpool.com:443 - first alive pool
[2019-05-16 06:56:00.510] Network diff set to 6.7T
[2019-05-16 06:56:00.605] Pool 0 stratum+tcp://stratum.antpool.com:443 alive, testing stability
[2019-05-16 06:56:00.606] Switching to pool 0 stratum+tcp://stratum.antpool.com:443
[2019-05-16 06:56:00.631] Stratum from pool 0 requested work restart
[2019-05-16 06:56:00.762] GSH 0: Toggling ASIC nRST to reset
[2019-05-16 06:56:00.856] GSH 0: NewPac Bitcoin Miner (10030315)
[2019-05-16 06:56:01.149] GSH 0: found 2 chip(s)
[2019-05-16 06:56:01.208] GSH 0: setting frequency to 100.00MHz
[2019-05-16 06:56:01.218] GSH 0: open cores @ 100.00MHz
[2019-05-16 06:56:02.432] GSH 0: start work @ 100.00MHz
[2019-05-16 06:57:03.185] GSH 0: missing nonces
[2019-05-16 06:57:03.219] GSH 0: Toggling ASIC nRST to reset
[2019-05-16 06:57:04.637] GSH 0: setting frequency to 100.00MHz
[2019-05-16 06:57:53.073] GSH 0: missing nonces
[2019-05-16 06:57:53.102] GSH 0: Toggling ASIC nRST to reset
[2019-05-16 06:57:54.539] GSH 0: setting frequency to 100.00MHz
[2019-05-16 06:58:43.571] GSH 0: missing nonces
[2019-05-16 06:58:43.618] GSH 0: Toggling ASIC nRST to reset
[2019-05-16 06:58:45.082] GSH 0: setting frequency to 100.00MHz
[2019-05-16 06:59:33.458] GSH 0: missing nonces
[2019-05-16 06:59:33.550] GSH 0: Toggling ASIC nRST to reset
May 15, 2019, 10:21:55 PM
kingofhammers - maybe I'm a little biased on account of how much work went into case design and manufacture for those guys, but please just get a not-stupid power supply. Unless you can guarantee the combined housing you make will be appropriately awesome, in which case PICTURES!
cliftonk - keep working with the reseller to diagnose what's going wrong. If you do end up getting a replacement unit, let the reseller know I'd like it shipped straight to me so I can figure out what the heck is going on. I've been thinking about it for a while now and there really are no links between a blinking-LEDs and a zero-chips (those are two almost wholly separate systems). Unless the main regulator died in such a way that it took the volt-setting pot with it, and that's screwing up the I2C bus the temp sensor's also on, which is a series of unlikely failures. There's enough anomalous about that thing that I want to look at it myself.
Also, I have reports of at least four pods with blinking LEDs. The temp sensor was the part of the system I trust the least, and it's also doing the least, so I'll probably just cut it out of the firmware effective immediately and probably not even install it on the next batch.
cliftonk - keep working with the reseller to diagnose what's going wrong. If you do end up getting a replacement unit, let the reseller know I'd like it shipped straight to me so I can figure out what the heck is going on. I've been thinking about it for a while now and there really are no links between a blinking-LEDs and a zero-chips (those are two almost wholly separate systems). Unless the main regulator died in such a way that it took the volt-setting pot with it, and that's screwing up the I2C bus the temp sensor's also on, which is a series of unlikely failures. There's enough anomalous about that thing that I want to look at it myself.
Also, I have reports of at least four pods with blinking LEDs. The temp sensor was the part of the system I trust the least, and it's also doing the least, so I'll probably just cut it out of the firmware effective immediately and probably not even install it on the next batch.
May 15, 2019, 10:06:40 PM
Honestly I don't know what could be causing all those problems. Thought maybe the onboard 5V was wigging out, causing the USB chip to cycle on and off which would explain the disconnects, and also cycle the microcontroller and temp sensor so it keeps starting up to invalid state and blinking. But the timings don't make sense.
It's unlikely to have a bad temp sensor causing the blink. It's at least as unlikely to have a zero-chips-detected issue. It's basically impossible to have both. Did someone play baseball with it or something?
It's unlikely to have a bad temp sensor causing the blink. It's at least as unlikely to have a zero-chips-detected issue. It's basically impossible to have both. Did someone play baseball with it or something?
@sidehack
No the unit arrived today in pristine condition. It was very well packed. Also well protected from static. I have tried the HP PSU and a known good 20 AMP brick with it as well -- no difference -- power supply at least is ruled out
@kingofhammers
I am using an industrial pc running Ubuntu 18.04. The same exact build runs well on the NEWPAC to the same pool on the same computer.
Barring some miraculous revelation tonight, I will just send the unit back for either a replacement, or if none are available, just a refund.
Thanks to all for the attempts at help with this.
May 15, 2019, 09:51:33 PM
Thanks @sidehack .
I do see where @kingofhammers had this issue, however if you look at the paste of cgminer (trying) to run, you will see that I get failures on GSI 0, GSI 1, and GSI 2, -- the unit settles at 0 chips found after resetting all the ASICs and the unit is never hashing.
I did rebuild cgminer using the May 14th build, so it is not the software.
Very frustrated at this point.
I do see where @kingofhammers had this issue, however if you look at the paste of cgminer (trying) to run, you will see that I get failures on GSI 0, GSI 1, and GSI 2, -- the unit settles at 0 chips found after resetting all the ASICs and the unit is never hashing.
I did rebuild cgminer using the May 14th build, so it is not the software.
Very frustrated at this point.
I did get those failures but that seemed as though it could be related to running on the Pi, are you running on a Pi?
The temp tester that @phillipma1975 recommended works like a charm and verified that the temps are stable.
I had never thought that the errors would be related to the temp sensor as they showed up on all units while the temp was only flashing on two of them. Earlier in the thread there is some talk about the weakest chip in the unit and I think that may be the source of the errors. After fooling with the voltage and frequency settings I had them all operating as intended. As the autotune dialed in the frequency for each unit the errors became more and more rare and when a unit would reset it would recover its hash rate in a matter of 45-60 seconds.
They'd still be running if it weren't for the damn power supply. I have these set up in my office and I'm running them off of a bitmain power supply that sounds like a hair dryer. Needless to say, the wife isn't a fan. So, I'm working out a design to remove the boards and place them into a much larger all in one contained unit that I'll put in my garage. It'll give me an excuse to upgrade my home network to a mesh, and I'll be able to extend my wifi into the garage. So, I got that going for me.
May 15, 2019, 09:49:35 PM
Honestly I don't know what could be causing all those problems. Thought maybe the onboard 5V was wigging out, causing the USB chip to cycle on and off which would explain the disconnects, and also cycle the microcontroller and temp sensor so it keeps starting up to invalid state and blinking. But the timings don't make sense.
It's unlikely to have a bad temp sensor causing the blink. It's at least as unlikely to have a zero-chips-detected issue. It's basically impossible to have both. Did someone play baseball with it or something?
It's unlikely to have a bad temp sensor causing the blink. It's at least as unlikely to have a zero-chips-detected issue. It's basically impossible to have both. Did someone play baseball with it or something?
May 15, 2019, 09:21:30 PM
Gosh dangit, another one? See I've run every single one of those pods at least six separate times during different testing steps, including a burn-in test for 24 hours, and have yet to see it happen once.
I'll work on a firmware fix that makes "temp sensor is no good" blinking distinct from and much less obtrusive than "temperature is too high" blinking. And figure out why the heck the temp sensors are failing in these things. Heck I may just get rid of them entirely.
Also when I say "firmware fix" I mean literally a code change for the onboard microcontroller. What makes lights blink is completely independent from cgminer.
By the way, that condition's already been talked about so looking back in the thread a bit will catch you up.
I'll work on a firmware fix that makes "temp sensor is no good" blinking distinct from and much less obtrusive than "temperature is too high" blinking. And figure out why the heck the temp sensors are failing in these things. Heck I may just get rid of them entirely.
Also when I say "firmware fix" I mean literally a code change for the onboard microcontroller. What makes lights blink is completely independent from cgminer.
By the way, that condition's already been talked about so looking back in the thread a bit will catch you up.
Thanks @sidehack .
I do see where @kingofhammers had this issue, however if you look at the paste of cgminer (trying) to run, you will see that I get failures on GSI 0, GSI 1, and GSI 2, -- the unit settles at 0 chips found after resetting all the ASICs and the unit is never hashing.
I did rebuild cgminer using the May 14th build, so it is not the software.
Very frustrated at this point.
May 15, 2019, 09:15:14 PM
That would be great! A lot easier to diagnose then too.
May 15, 2019, 08:54:59 PM
Gosh dangit, another one? See I've run every single one of those pods at least six separate times during different testing steps, including a burn-in test for 24 hours, and have yet to see it happen once.
I'll work on a firmware fix that makes "temp sensor is no good" blinking distinct from and much less obtrusive than "temperature is too high" blinking. And figure out why the heck the temp sensors are failing in these things. Heck I may just get rid of them entirely.
Also when I say "firmware fix" I mean literally a code change for the onboard microcontroller. What makes lights blink is completely independent from cgminer.
By the way, that condition's already been talked about so looking back in the thread a bit will catch you up.
I'll work on a firmware fix that makes "temp sensor is no good" blinking distinct from and much less obtrusive than "temperature is too high" blinking. And figure out why the heck the temp sensors are failing in these things. Heck I may just get rid of them entirely.
Also when I say "firmware fix" I mean literally a code change for the onboard microcontroller. What makes lights blink is completely independent from cgminer.
By the way, that condition's already been talked about so looking back in the thread a bit will catch you up.
May 15, 2019, 07:04:21 PM
You probably need one of the new CGMiner released for the R606 as well.
Unless I hear from support here, I will try to call them tomorrow. Not much point in continuing with the VCore lights blinking and all the chips doing "Toggling ASIC nRST". I had just built cgminer on Sunday, May 12, with a new git clone. I did see where another update was released on May 14th.
May 15, 2019, 06:56:28 PM
Thanks. I suspected as much. Not good! Tried it first with the new HP power supply, then dropped back to a 20AMP 12 volt brick. Same blinking lights with both power supplies. Fan does run. I can see the orange light on the pcb inside the unit.
You probably need one of the new CGMiner released for the R606 as well.
May 15, 2019, 06:53:27 PM
Those lights are supposed to be solid.
Thanks. I suspected as much. Not good! Tried it first with the new HP power supply, then dropped back to a 20AMP 12 volt brick. Same blinking lights with both power supplies. Fan does run. I can see the orange light on the pcb inside the unit.
May 15, 2019, 06:49:54 PM
Thanks. The R606 arrived today. Regarding the VCore lights on the R606, are they supposed to alternate blinking? It is very hard to figure out what the VCore setting actually is since they alternate from one state to the other continuously...
Those lights are supposed to be solid.
May 15, 2019, 06:39:29 PM
Solid green means it's getting power. Blinking white means it's hashing. All of my miners work that way - solid color for general power, flash of white while mining (and blink rate generally proportional to hashing speed).
On the R606, the power light is orange and the white blinks are timed more like 2Pacs.
On the R606, the power light is orange and the white blinks are timed more like 2Pacs.
Thanks. The R606 arrived today. Regarding the VCore lights on the R606, are they supposed to alternate blinking? It is very hard to figure out what the VCore setting actually is since they alternate from one state to the other continuously.
- With the up button clicked eight times all three red LEDs are blinking.
- Clicking down one time results in the top and bottom blinking on then the center on when they are off.
The unit is powered by the HP Power supply bundle with the breakout board and the 6 pin power connection.
I have tried using the R606 build that works perfectly with the newpack on Ubuntu 18.04, but with the R606, cgminer never starts working.
command started with:
Code:
./cgminer -o stratum+tcp://pool.ckpool.org:3333 -u 367KFywb7XdAYUEY13aKXEz1t217Bw2SDE -p x --gekko-r606-freq 400 --gekko-noboost
Code:
cgminer version 4.11.1 - Started: [2019-05-15 19:25:37.498]
--------------------------------------------------------------------------------
(5s):0.000 (1m):0.000 (5m):0.000 (15m):0.000 (avg):0.000h/s
A:0 R:0 HW:0 WU:0.0/m
Connected to pool.ckpool.org diff 10K with stratum as user 367KFywb7XdAYUEY13aKXEz1t217Bw2SDE
Block: 245cba4a... Diff:6.7T Started: [19:25:37.501] Best share: 0
--------------------------------------------------------------------------------
[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
2: GSI 10040057: found 0 chip(s) | OFF
--------------------------------------------------------------------------------
[2019-05-15 19:25:35.984] Started cgminer 4.11.1
[2019-05-15 19:25:35.984] Probing for an alive pool
[2019-05-15 19:25:36.301] Pool 0 difficulty changed to 10000
[2019-05-15 19:25:36.343] Pool 0 message: Authorised, welcome to ckpool.org 367KFywb7XdAYUEY13aKXEz1t21
7Bw2SDE!
[2019-05-15 19:25:37.233] 0: GSI 0 - Toggling ASIC nRST to reset
[2019-05-15 19:25:37.497] 0: GSI 0 - R606 Bitcoin Miner (10040057)
[2019-05-15 19:25:37.501] Network diff set to 6.7T
[2019-05-15 19:25:58.203] GSI 0 failure, disabling!
[2019-05-15 19:26:03.410] 0: GSI 0 - Toggling ASIC nRST to reset
[2019-05-15 19:26:08.675] Hotplug: GekkoScience added GSI 1
[2019-05-15 19:26:29.371] GSI 1 failure, disabling!
[2019-05-15 19:26:34.590] 0: GSI 0 - Toggling ASIC nRST to reset
[2019-05-15 19:26:34.853] Hotplug: GekkoScience added GSI 2
--------------------------------------------------------------------------------
(5s):0.000 (1m):0.000 (5m):0.000 (15m):0.000 (avg):0.000h/s
A:0 R:0 HW:0 WU:0.0/m
Connected to pool.ckpool.org diff 10K with stratum as user 367KFywb7XdAYUEY13aKXEz1t217Bw2SDE
Block: 245cba4a... Diff:6.7T Started: [19:25:37.501] Best share: 0
--------------------------------------------------------------------------------
[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
2: GSI 10040057: found 0 chip(s) | OFF
--------------------------------------------------------------------------------
[2019-05-15 19:25:35.984] Started cgminer 4.11.1
[2019-05-15 19:25:35.984] Probing for an alive pool
[2019-05-15 19:25:36.301] Pool 0 difficulty changed to 10000
[2019-05-15 19:25:36.343] Pool 0 message: Authorised, welcome to ckpool.org 367KFywb7XdAYUEY13aKXEz1t21
7Bw2SDE!
[2019-05-15 19:25:37.233] 0: GSI 0 - Toggling ASIC nRST to reset
[2019-05-15 19:25:37.497] 0: GSI 0 - R606 Bitcoin Miner (10040057)
[2019-05-15 19:25:37.501] Network diff set to 6.7T
[2019-05-15 19:25:58.203] GSI 0 failure, disabling!
[2019-05-15 19:26:03.410] 0: GSI 0 - Toggling ASIC nRST to reset
[2019-05-15 19:26:08.675] Hotplug: GekkoScience added GSI 1
[2019-05-15 19:26:29.371] GSI 1 failure, disabling!
[2019-05-15 19:26:34.590] 0: GSI 0 - Toggling ASIC nRST to reset
[2019-05-15 19:26:34.853] Hotplug: GekkoScience added GSI 2
Jump to: