a lot of errors new jupiter november anyone have this problem
Device Hardware%=10.0331
What pool are you running on?
how to see this advanced status Screen?
Me too - how do I get to see this ??
Topic: Swedish ASIC miner company kncminer.com - page 861. (Read 3050078 times)
a lot of errors new jupiter november anyone have this problem
Device Hardware%=10.0331
What pool are you running on?
how to see this advanced status Screen?
Me too - how do I get to see this ??
@robix you have many hw on eligius?
maybe is pool because my saturn start today give some errors
I have two Jups (one Oct and one Nov) on Eligius. Oct rig runs fine, I think. Nov rig has the HW error issue. maybe is pool because my saturn start today give some errors
@robix you have many hw on eligius?
maybe is pool because my saturn start today give some errors
maybe is pool because my saturn start today give some errors
a lot of errors new jupiter november anyone have this problem
Device Hardware%=10.0331
What pool are you running on?
how to see this advanced status Screen?
Me too - how do I get to see this ??
@robix eligius pool
Interesting. I'm on Eligius too. Before I was on Slush for some time and I think the HW errors were significantly lower (3 or 4% if I recall correctly). Hmm, perhaps I try it again later and move back to Slush for a try. 
a lot of errors new jupiter november anyone have this problem
Device Hardware%=10.0331
What pool are you running on?
how to see this advanced status Screen?
@robix eligius pool
what is the best worker diff
for november jupiter
512 or 1024?
for november jupiter
512 or 1024?
test both values and report back.
i've used 512 for all the pools that do not have vardiff in place.
On eligius the highest diff set by the pool for my jup was 2048.
what is the best worker diff
for november jupiter
512 or 1024?
for november jupiter
512 or 1024?
a lot of errors new jupiter november anyone have this problem
Device Hardware%=10.0331
What pool are you running on?
a lot of errors new jupiter november anyone have this problem
4 Hours till the next difficulty increase 
Bitcoin Difficulty: 707,408,283
Estimated Next Difficulty: 907,096,226 (+28.23%)
Adjust time: After 33 Blocks, About 4.1 hours
Hashrate(?): 6,796,629 GH/s
Bitcoin Difficulty: 707,408,283
Estimated Next Difficulty: 907,096,226 (+28.23%)
Adjust time: After 33 Blocks, About 4.1 hours
Hashrate(?): 6,796,629 GH/s
So received my Nov Jupiter.
Can't connect to machine by either SSH or webpage. It is assigned an IP address just can't connect. Even ping gets no response but not sure if the BBB is setup to respond to ping.
If I disconnect all 4 ASIC boards I can connect to the host and access web gui with no issues.
Reconnect the ASIC boards, can't connect.
Tried connecting just one ASIC board with same results.
Tried two different power supplies with the same results.
Anyone had anything like this or am I just SOL?
Can't connect to machine by either SSH or webpage. It is assigned an IP address just can't connect. Even ping gets no response but not sure if the BBB is setup to respond to ping.
If I disconnect all 4 ASIC boards I can connect to the host and access web gui with no issues.
Reconnect the ASIC boards, can't connect.
Tried connecting just one ASIC board with same results.
Tried two different power supplies with the same results.
Anyone had anything like this or am I just SOL?
Maybe silly question but you didn't flash 0.99-tune onto it did you?
If not...
I'd get the RMA email done right away, you can always cancel it if you fix it, but at least get the ball rolling as it can take a day or two, then I'd go on the IRC channel and ask hno what he thinks
I didn't flash anything, it never worked from the first power on. I did try reflashing the Nov 0.99e firmware but no change. The one thing that makes the convinces it is just a bad controller is it does not save any setting after a reboot or power loss. For example enable ssh, able to ssh in (w/ no ASICs connected), reboot, not able to ssh in, check gui and enable ssh is unchecked.
I went ahead an put in an RMA but I have a bad feeling KNC is going to make me ship the entire damn this back rather than just ship a new controller.
This is exactly what mine does. I even booted it off a sd card and same issue when I plug a module in. You end up shipping your whole unit back?
Figured I'd follow up on my original post about my extended Jupiter (4+2 upgrade modules)
KNC authorized an RMA, and shipped my order back the same day they received it. The boards I got looked completely new, along with the control board. UPS delayed the shipment by 2 days (on an overnight AM delivery), but that's not on KNC.
Some things that I would like to see KNC do in the future:
Provide shipping labels.
Cross ship defective items. Take market value BTC to hold until defective parts come in. Those few days are huge.
Compensate for lost hashing power. Either offer customers direct BTC compensation for lost time, or include some sort of module/credit freebie.
Early morning delivery times instead of evening saver. A 10 AM delivery is much better than 6 PM.
Provide faster updates (I had to email them to receive the tracking number they shipped out) This includes better communication about orders going out and R&D.
I'm happily hashing around 841 on Putty right now. KnC might not be perfect, the delays sucked - but would you rather have preordered with Hashfast or BFL? Anyone else? Time will ultimately tell who was the best investment. Right now, today, I am very happy that I preordered with KNC and not anyone else.
That said, I've got a nice chunk of Neptunes on order. Here's to them spearheading the next generation.
KNC authorized an RMA, and shipped my order back the same day they received it. The boards I got looked completely new, along with the control board. UPS delayed the shipment by 2 days (on an overnight AM delivery), but that's not on KNC.
Some things that I would like to see KNC do in the future:
Provide shipping labels.
Cross ship defective items. Take market value BTC to hold until defective parts come in. Those few days are huge.
Compensate for lost hashing power. Either offer customers direct BTC compensation for lost time, or include some sort of module/credit freebie.
Early morning delivery times instead of evening saver. A 10 AM delivery is much better than 6 PM.
Provide faster updates (I had to email them to receive the tracking number they shipped out) This includes better communication about orders going out and R&D.
I'm happily hashing around 841 on Putty right now. KnC might not be perfect, the delays sucked - but would you rather have preordered with Hashfast or BFL? Anyone else? Time will ultimately tell who was the best investment. Right now, today, I am very happy that I preordered with KNC and not anyone else.
That said, I've got a nice chunk of Neptunes on order. Here's to them spearheading the next generation.
To follow up on my original post here, after some hashing time 2 of the ASIC boards have developed die 0 issues. I can revive one of them by constantly pumping voltage into it, but the other one I can't do anything to get it up and running. KNC offered the standard warranty service, although this time they are offering to cover the shipping.
I wonder if KNC will do anything above and beyond the normal, it is unfortunate and disheartening to have so many issues, even on seemingly new boards they shipped out.
Turn it off, open it up and check that all cables are completely plugged in. Try swapping ports and cables between pairs of ASICs, see if the problem follows the move or the port. Various methods to determine if the problem is the asic, controller board, or the cable between them.
I will try that soon.Do you have a flaky power supply?
You really should be able to find a supply that can deliver 12V -- 12.2V -- 11.8V might be an issue.
You really should be able to find a supply that can deliver 12V -- 12.2V -- 11.8V might be an issue.
I believe the PSU is fine, the 2 boards that are working perfectly are both being supplied with 11.8 or 11.9 volts.
I will try using a different power supply to power the non-functional boards.
Is there anything I can do to get these cores to work? On board 3 none of the cores work, and on board 2 about 24 out of the 192 cores seem to stay off.
I just got the miner today and when I initially started it up the hashrate climbed up to about 660/670, but later i checked and noticed it was running at about 480GH/s.
I just got the miner today and when I initially started it up the hashrate climbed up to about 660/670, but later i checked and noticed it was running at about 480GH/s.
Do you have a flaky power supply?
You really should be able to find a supply that can deliver 12V -- 12.2V -- 11.8V might be an issue.
I have a seasonic plat. and it says 11.8v on mine but it works fine...I'd like to think seasonic isn't a flaky psu
but mine is a oct. unit...feel sorry for everyone that is having problems with nov. units...you'd think the extra time/wait for these units they'd all arrive perfect...or most of them...good luck to you all 
and happy diff. raise day!!! err..wait Is there anything I can do to get these cores to work? On board 3 none of the cores work, and on board 2 about 24 out of the 192 cores seem to stay off.
I just got the miner today and when I initially started it up the hashrate climbed up to about 660/670, but later i checked and noticed it was running at about 480GH/s.
I just got the miner today and when I initially started it up the hashrate climbed up to about 660/670, but later i checked and noticed it was running at about 480GH/s.
Turn it off, open it up and check that all cables are completely plugged in. Try swapping ports and cables between pairs of ASICs, see if the problem follows the move or the port. Various methods to determine if the problem is the asic, controller board, or the cable between them.
Is there anything I can do to get these cores to work? On board 3 none of the cores work, and on board 2 about 24 out of the 192 cores seem to stay off.
I just got the miner today and when I initially started it up the hashrate climbed up to about 660/670, but later i checked and noticed it was running at about 480GH/s.
I just got the miner today and when I initially started it up the hashrate climbed up to about 660/670, but later i checked and noticed it was running at about 480GH/s.
Do you have a flaky power supply?
You really should be able to find a supply that can deliver 12V -- 12.2V -- 11.8V might be an issue.
I wonder if there's more duds for this batch of KNC, or if it's just more folks talking about it? Seems like a lot more than the first batch.
Hope this isn't a foresight for the Neptunes.
Hope this isn't a foresight for the Neptunes.
Is there anything I can do to get these cores to work? On board 3 none of the cores work, and on board 2 about 24 out of the 192 cores seem to stay off.
I just got the miner today and when I initially started it up the hashrate climbed up to about 660/670, but later i checked and noticed it was running at about 480GH/s.
I just got the miner today and when I initially started it up the hashrate climbed up to about 660/670, but later i checked and noticed it was running at about 480GH/s.
Jump to: