Swedish ASIC miner company kncminer.com

[Phoenix1969]

Hi all,

I was so excited to set up my Mercury today.

Got the PSU all hooked up, took two boots but then it was up and running.
Thought things were going so well I should go ahead and upgrade to the latest version, since I was instructed to do so IN ALL CAPS.

Well, firmware revision 0.97 isn't making me love this machine.  It is "hashing" at 0.1 Gh/sec...

I get a CGMiner status on the web GUI "Running (Connect to CGMiner API failed)"

I did nothing but flash to the latest firmware.  What gives?  Anyone else have problems with 0.97?
Any ideas on how to fix it?

Thank you,

_theJestre

All you had to do was clear your browser cache, and restart the browser.

[thejestre]

Not sure, I don't think I've seen that. I forgot to mention I had to run the EnableCores.bin after downgrading from .97 to .96 as it also disabled all cores on all dies and they didn't re-enable on downgrade.

Run the EnableCores.bin like uploading firmware?  Thanks so much for the info.

[thejestre]

Hi all,

I was so excited to set up my Mercury today.

Got the PSU all hooked up, took two boots but then it was up and running.
Thought things were going so well I should go ahead and upgrade to the latest version, since I was instructed to do so IN ALL CAPS.

Well, firmware revision 0.97 isn't making me love this machine.  It is "hashing" at 0.1 Gh/sec...

I get a CGMiner status on the web GUI "Running (Connect to CGMiner API failed)"

I did nothing but flash to the latest firmware.  What gives?  Anyone else have problems with 0.97?
Any ideas on how to fix it?

Thank you,

_theJestre

All you had to do was clear your browser cache, and restart the browser.

Dude, please...

I used a completely different browser just to be sure.

EDIT: punctuation.

[KnCMiningOp]

Not sure, I don't think I've seen that. I forgot to mention I had to run the EnableCores.bin after downgrading from .97 to .96 as it also disabled all cores on all dies and they didn't re-enable on downgrade.

Run the EnableCores.bin like uploading firmware?  Thanks so much for the info.

No problem and yes if it's still not hashing then reboot.

[KnCMiningOp]

Hi all,

I was so excited to set up my Mercury today.

Got the PSU all hooked up, took two boots but then it was up and running.
Thought things were going so well I should go ahead and upgrade to the latest version, since I was instructed to do so IN ALL CAPS.

Well, firmware revision 0.97 isn't making me love this machine.  It is "hashing" at 0.1 Gh/sec...

I get a CGMiner status on the web GUI "Running (Connect to CGMiner API failed)"

I did nothing but flash to the latest firmware.  What gives?  Anyone else have problems with 0.97?
Any ideas on how to fix it?

Thank you,

_theJestre

All you had to do was clear your browser cache, and restart the browser.

Dude, please...

I used a completely different browser just to be sure...

I had the same thing when I upgraded to .97 I too tried another browser.

[Phoenix1969]

Almost wishing i had a bad board to play with.  Mine are running so so...  once there are warm they error rates drop to about 7-9%  and usually hashes about 550-554   SO i don't want to go and make things worse.   Though if i had a board that i was sending back to RMA  i couldn't help my self but try and heat it up .   tomorrow i might check and see if a little more pressure dose help mine at all..  if so i might just grind off a little on the spacers.

I found a few screws that attach the heat sink to the board to be a tad loose and was able to get get a half to a full twist on them.

I already know mine are down tight.  I took mine apart the first day i had it...  witch is why Im thinking about grinding a little off the spacer to make it a bit more tight.    but first ill test tomorrow if any more pressure helps.   Would go ahead and try tonight.  But i had a couple drinks earlier....    And well drinking and tinkering with a 7k machine don't go to well together in my books lol.    Wait tell im nice and fresh tomorrow.

Haha right! Even when I'm 100% sober I feel nervous doing anything, to apply pressure on the heat sink took me almost 1.5 days to do.

@Phoenix1969 Glad to hear you found a "bug"

yeah!... I was able to get a pair of angle pliers in there and get a twist or two on it... good stuff.
I then checked all the others...
most of which took at least half a turn to get tight.

[KnCMiningOp]

Almost wishing i had a bad board to play with.  Mine are running so so...  once there are warm they error rates drop to about 7-9%  and usually hashes about 550-554   SO i don't want to go and make things worse.   Though if i had a board that i was sending back to RMA  i couldn't help my self but try and heat it up .   tomorrow i might check and see if a little more pressure dose help mine at all..  if so i might just grind off a little on the spacers.

I found a few screws that attach the heat sink to the board to be a tad loose and was able to get get a half to a full twist on them.

I already know mine are down tight.  I took mine apart the first day i had it...  witch is why Im thinking about grinding a little off the spacer to make it a bit more tight.    but first ill test tomorrow if any more pressure helps.   Would go ahead and try tonight.  But i had a couple drinks earlier....    And well drinking and tinkering with a 7k machine don't go to well together in my books lol.    Wait tell im nice and fresh tomorrow.

Haha right! Even when I'm 100% sober I feel nervous doing anything, to apply pressure on the heat sink took me almost 1.5 days to do.

@Phoenix1969 Glad to hear you found a "bug"

yeah!... I was able to get a pair of angle pliers in there and get a twist or two on it... good stuff.
I then checked all the others...
most of which took at least half a turn to get tight.

Any change in performance or temp?

[thejestre]

Well I still am getting the "Running (Connect to CGMiner API failed)" error from the web GUI.
Yes, I have cleared the cash on the browser, AND used a different browser.

More importantly I can tell it isn't doing anything because the pool isn't getting much work.

Looks like 0.96 isn't up to prime time for my Mercury.  Going back to 0.95 because at least that was hashing something.  Unless there is something else to do to get 0.96 to work?

Thanks,

_theJestre

[KnCMiningOp]

Well I still am getting the "Running (Connect to CGMiner API failed)" error from the web GUI.
Yes, I have cleared the cash on the browser, AND used a different browser.

More importantly I can tell it isn't doing anything because the pool isn't getting much work.

Looks like 0.96 isn't up to prime time for my Mercury.  Going back to 0.95 because at least that was hashing something.  Unless there is something else to do to get 0.96 to work?

Thanks,

_theJestre

Not that I know of. People have had bad luck with .96 too, I haven't. You did check the box in the mining page that say enable CGMiner API right?

[Phoenix1969]

actually, yes...the hot one came down 10c
Now they are ALL 3 offically over-spec!.. 279,283,284...BAM

[thejestre]

Well I still am getting the "Running (Connect to CGMiner API failed)" error from the web GUI.
Yes, I have cleared the cash on the browser, AND used a different browser.

More importantly I can tell it isn't doing anything because the pool isn't getting much work.

Looks like 0.96 isn't up to prime time for my Mercury.  Going back to 0.95 because at least that was hashing something.  Unless there is something else to do to get 0.96 to work?

Thanks,

_theJestre

Not that I know of. People have had bad luck with .96 too, I haven't. You did check the box in the mining page that say enable CGMiner API right?

Indeed I did, thanks.

I was also letting it run for a long time and it didn't report a single share to my pool for over 7 minutes, so there is some kind of problem beyond just the web GUI not displaying CGIminer info.  I don't feel like SSH'ing to the thing tonight to muck about [and also haven't really read up on what I need to avoid doing so as to not void the warranty] so I've just flashed back to 0.95 which it came with.  So far I'm getting a report of ~80 Ghash/sec @ 42.0 C so I think I'll go relax and let it run overnight.  At least it won't just be sitting there doing nothing.

I haven't tried the 0.961 yet, maybe will see if that works tomorrow.

Thanks again,

_theJestre

[Phoenix1969]

Ill bet you find the credentials are entered wrong, or something like that
was it running before?, or u just got it?

[edgar]

the crossbar screws seem to want to disintegrate despite needing a slight tightening.

most needed at least a 1/4 turn - no noticeable improvements yet

[Searing]

Almost wishing i had a bad board to play with.  Mine are running so so...  once there are warm they error rates drop to about 7-9%  and usually hashes about 550-554   SO i don't want to go and make things worse.   Though if i had a board that i was sending back to RMA  i couldn't help my self but try and heat it up .   tomorrow i might check and see if a little more pressure dose help mine at all..  if so i might just grind off a little on the spacers.

I found a few screws that attach the heat sink to the board to be a tad loose and was able to get get a half to a full twist on them.

I already know mine are down tight.  I took mine apart the first day i had it...  witch is why Im thinking about grinding a little off the spacer to make it a bit more tight.    but first ill test tomorrow if any more pressure helps.   Would go ahead and try tonight.  But i had a couple drinks earlier....    And well drinking and tinkering with a 7k machine don't go to well together in my books lol.    Wait tell im nice and fresh tomorrow.

Haha right! Even when I'm 100% sober I feel nervous doing anything, to apply pressure on the heat sink took me almost 1.5 days to do.

@Phoenix1969 Glad to hear you found a "bug"

mine is now running 565gh after 6 days up...5% error rate on .95...only thing I need is to find the thread on how to put in 2nd pool manually because not on .95....my core temps are 27c 31c 34c and 42c ...and I have once in a great while a core enable and unenable itself (maybe 1x ever 4hrs or so I'd guess)

so I HAVE TOUCHED NOTHING ..in fact I walk by the beastie and I look downward and away less it get p/o'd at me and make it go CLUNK!

I will however have to look at the screws above to see if they are tight the next time it is powered off of which I plan for it to be NEVER if possible

anyway if anyone trips over the trick to get a 2nd pool in on .95 ..still looking for the link..pm me or post it here....if power goes out I have lots to check out
but until then GO BABY GO!

off to check the unit in the bsmt.....(must avert eyes...i'm not worthy)

Searing

[Phoenix1969]

nice...Id be scared to touch it too, thats great!
on the 2nd pool, I think you can just use putty to do it in cgminer, just remember to save to /config/cgminer.conf, and not the root/default directory. your default pool is pool 0, the backup is 1...

BTW... error rates, 1%, 3%, 3%. wow.

[sickpig]

nice...Id be scared to touch it too, thats great!
on the 2nd pool, I think you can just use putty to do it in cgminer, just remember to save to /config/cgminer.conf, and not the root/default directory. your default pool is pool 0, the backup is 1...

BTW... error rates, 1%, 3%, 3%. wow.

Dumb questions:

1) Did you apply all those hw tricks withe the machine switched on?
2) a part from makes VRM clicks and check the heatsink screws thre's something else to do?

Unreleated to this just wanna share that BB sys load lowered to 1.5 from 1.9 when using bfgminer instead of cgminer (bfgminer compiled fro source doeas not include  dynamic cores enable/disable mechanism committed on the 25)

[ElGabo]

Hi

Now after 24 hours my jup is going with 552ghs rock solid but I figured out something interesting.

If all my vrm output above 0.7 V the pool shows great 550-560Ghs, if just only 1 or 2 vrm output goes down under 0.7 V (for example 0.687V) the pool hashrate dorps down to 510-540. In cgminer still 552.

Any ideas?

[FeedbackLoop]

Hi

Now after 24 hours my jup is going with 552ghs rock solid but I figured out something interesting.

If all my vrm output above 0.7 V the pool shows great 550-560Ghs, if just only 1 or 2 vrm output goes down under 0.7 V (for example 0.687V) the pool hashrate dorps down to 510-540. In cgminer still 552.

Any ideas?

KNC's cgminer includes hardware errors in the reported hashing rate. Something not done by the other versions of cgminer. From the maker:
https://asktom.cf/index.php?topic=319533.0

Please compute your hashing rate from cgminer using:
2^32 * Accepted / Elapsed


What are your temps and HW in both circumstances?

[ElGabo]

Hi Feedbackloop!

Here is a picture. Everything is just the same. Only the vrm output changing nothing else. No hashrate drop, nothing. Ecerything is just fine...

[ElGabo]

Hi

Now after 24 hours my jup is going with 552ghs rock solid but I figured out something interesting.

If all my vrm output above 0.7 V the pool shows great 550-560Ghs, if just only 1 or 2 vrm output goes down under 0.7 V (for example 0.687V) the pool hashrate dorps down to 510-540. In cgminer still 552.

Any ideas?

KNC's cgminer includes hardware errors in the reported hashing rate. Something not done by the other versions of cgminer. From the maker:
https://asktom.cf/index.php?topic=319533.0

Please compute your hashing rate from cgminer using:
2^32 * Accepted / Elapsed


What are your temps and HW in both circumstances?

Now I understand I think.

IF Hw counts in the hasrate, when the output drops a bit, maybe the hw rate goes up a bit and the real hasrate goes down.

It would be great if we could control the output of the DC-s.... (And maybe the clock)