[OLD] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 #

[spooderman]

Greetings miners!

I've caught up the payout queue.  Then I went and dropped the default minimum payout down to 40 TBC (0.04194304 BTC) and filled it back up with all of the folks who now qualify for payout due to the lowered mininmum.  I will be catching up again shortly.  This will make sure that the pool has less and less of your funds in storage, so, better security, faster payouts, etc.

Happy mining!

-wk


------------------

have the option at eligius pool
to put difficulty at worker
or not?

and if i can how i can do these???

You can set a minimum difficulty in Configurable Options.  

...but it doesn't work...

There's actually no longer an option to set a minimum difficulty in the options page.  This will be superseded by the bfgminer option for --request-diff as soon as I finish testing the latest updates to eloipool to support this.  I was hoping to finish that this weekend, but I did not have sufficient time.

-wk

Thanks very much again sir

[iambaboon]

wizkid, some payment was missing today (in the list but not in the blockchain) - sent PM.

[wizkid057]

wizkid, some payment was missing today (in the list but not in the blockchain) - sent PM.

Happens when we get an orphaned block.  Should already have corrected itself.

-wk

[helmax]

some kncminers have problems with HW here this pool

i use ghash some hours and not have errors and stable

eligius lot of errors and not stable difficult and WU 8700 and cores disable
ghash not cores disable and WU 9400

[kendog77]

some kncminers have problems with HW here this pool

i use ghash some hours and not have errors and stable

eligius lot of errors and not stable difficult and WU 8700 and cores disable
ghash not cores disable and WU 9400

Agreed. I have a November Jupiter that has a lot of hardware errors (~10%) on Eligius, but almost none and a 10% higher hashrate on BtcGuild.

I want to mine on Eligius to support mining pool decentralization, but will not take a 10% hashrate hit to do so.

[robix]

some kncminers have problems with HW here this pool

i use ghash some hours and not have errors and stable

eligius lot of errors and not stable difficult and WU 8700 and cores disable
ghash not cores disable and WU 9400

Agreed. I have a November Jupiter that has a lot of hardware errors (~10%) on Eligius, but almost none and a 10% higher hashrate on BtcGuild.

I want to mine on Eligius to support mining pool decentralization, but will not take a 10% hashrate hit to do so.

Confirm. I also have ~ 8% increased hw error rate and a lower hashrate than on another pool.

Edit: With a Nov KnC Jupiter.

@wizkid. Any idea?

[kendog77]

some kncminers have problems with HW here this pool

i use ghash some hours and not have errors and stable

eligius lot of errors and not stable difficult and WU 8700 and cores disable
ghash not cores disable and WU 9400

Agreed. I have a November Jupiter that has a lot of hardware errors (~10%) on Eligius, but almost none and a 10% higher hashrate on BtcGuild.

I want to mine on Eligius to support mining pool decentralization, but will not take a 10% hashrate hit to do so.

Confirm. I also have ~ 8% increased hw error rate and a lower hashrate than on another pool.

Edit: With a Nov KnC Jupiter.

@wizkid. Any idea?

It would not surprise me if the problem is in cgminer, in which case Knc will need to release an updated firmware to correct the problem. They already did this once.

It looks like the .99 firmware solved problems with October Jupiters and the Eligius pool, but the problems appear to be back with the .99e firmware on November Jupiters.

https://www.kncminer.com/news/news-67

[kendog77]

Actually, after looking at this a bit more, I'm confused because cgminer 3.8.1 is included in the .99e November Jupiter firmware, and that was supposed to correct the problem with the Eligius pool. This must be a new issue that only impacts November Jupiters...

[helmax]

agree because saturn october works +/-
and jupiter november -/-

[wizkid057]

some kncminers have problems with HW here this pool

i use ghash some hours and not have errors and stable

eligius lot of errors and not stable difficult and WU 8700 and cores disable
ghash not cores disable and WU 9400

some kncminers have problems with HW here this pool

i use ghash some hours and not have errors and stable

eligius lot of errors and not stable difficult and WU 8700 and cores disable
ghash not cores disable and WU 9400

Agreed. I have a November Jupiter that has a lot of hardware errors (~10%) on Eligius, but almost none and a 10% higher hashrate on BtcGuild.

I want to mine on Eligius to support mining pool decentralization, but will not take a 10% hashrate hit to do so.

some kncminers have problems with HW here this pool

i use ghash some hours and not have errors and stable

eligius lot of errors and not stable difficult and WU 8700 and cores disable
ghash not cores disable and WU 9400

Agreed. I have a November Jupiter that has a lot of hardware errors (~10%) on Eligius, but almost none and a 10% higher hashrate on BtcGuild.

I want to mine on Eligius to support mining pool decentralization, but will not take a 10% hashrate hit to do so.

Confirm. I also have ~ 8% increased hw error rate and a lower hashrate than on another pool.

Edit: With a Nov KnC Jupiter.

@wizkid. Any idea?

I dont think anyone posting realizes what a hardware error actually is.  It has nothing at all whatsoever to do with the pool...

Edit: (clarity) A "hardware error" occurs when the hardware returns a nonce it believes is a valid difficulty 1 share and when the mining software rechecks it, it isn't.  Again, this has nothing whatsoever to do with the pool.

[kendog77]

some kncminers have problems with HW here this pool

i use ghash some hours and not have errors and stable

eligius lot of errors and not stable difficult and WU 8700 and cores disable
ghash not cores disable and WU 9400

some kncminers have problems with HW here this pool

i use ghash some hours and not have errors and stable

eligius lot of errors and not stable difficult and WU 8700 and cores disable
ghash not cores disable and WU 9400

Agreed. I have a November Jupiter that has a lot of hardware errors (~10%) on Eligius, but almost none and a 10% higher hashrate on BtcGuild.

I want to mine on Eligius to support mining pool decentralization, but will not take a 10% hashrate hit to do so.

some kncminers have problems with HW here this pool

i use ghash some hours and not have errors and stable

eligius lot of errors and not stable difficult and WU 8700 and cores disable
ghash not cores disable and WU 9400

Agreed. I have a November Jupiter that has a lot of hardware errors (~10%) on Eligius, but almost none and a 10% higher hashrate on BtcGuild.

I want to mine on Eligius to support mining pool decentralization, but will not take a 10% hashrate hit to do so.

Confirm. I also have ~ 8% increased hw error rate and a lower hashrate than on another pool.

Edit: With a Nov KnC Jupiter.

@wizkid. Any idea?

I dont think anyone posting realizes what a hardware error actually is.  It has nothing at all whatsoever to do with the pool...

Edit: (clarity) A "hardware error" occurs when the hardware returns a nonce it believes is a valid difficulty 1 share and when the mining software rechecks it, it isn't.  Again, this has nothing whatsoever to do with the pool.

Fair enough, but here is what I know:

- When I connect an October Jupiter to Eligius and BtcGuild, the hashrate reported reported by cgminer and by both pools is almost identical.

- When I connect a November Jupiter to Eligius, cgminer and Eligius report a hashrate ~10% less than what is reported when I connect the same machine to BtcGuild (note that cgminer also reflects the same higher hashrate as BtcGuild when connected to BtcGuild).

I have no idea why this is occurring, but a 10% hashrate hit is substantial enough to switch pools.

[wizkid057]

some kncminers have problems with HW here this pool

i use ghash some hours and not have errors and stable

eligius lot of errors and not stable difficult and WU 8700 and cores disable
ghash not cores disable and WU 9400

some kncminers have problems with HW here this pool

i use ghash some hours and not have errors and stable

eligius lot of errors and not stable difficult and WU 8700 and cores disable
ghash not cores disable and WU 9400

Agreed. I have a November Jupiter that has a lot of hardware errors (~10%) on Eligius, but almost none and a 10% higher hashrate on BtcGuild.

I want to mine on Eligius to support mining pool decentralization, but will not take a 10% hashrate hit to do so.

some kncminers have problems with HW here this pool

i use ghash some hours and not have errors and stable

eligius lot of errors and not stable difficult and WU 8700 and cores disable
ghash not cores disable and WU 9400

Agreed. I have a November Jupiter that has a lot of hardware errors (~10%) on Eligius, but almost none and a 10% higher hashrate on BtcGuild.

I want to mine on Eligius to support mining pool decentralization, but will not take a 10% hashrate hit to do so.

Confirm. I also have ~ 8% increased hw error rate and a lower hashrate than on another pool.

Edit: With a Nov KnC Jupiter.

@wizkid. Any idea?

I dont think anyone posting realizes what a hardware error actually is.  It has nothing at all whatsoever to do with the pool...

Edit: (clarity) A "hardware error" occurs when the hardware returns a nonce it believes is a valid difficulty 1 share and when the mining software rechecks it, it isn't.  Again, this has nothing whatsoever to do with the pool.

Fair enough, but here is what I know:

- When I connect an October Jupiter to Eligius and BtcGuild, the hashrate reported reported by cgminer and by both pools is almost identical.

- When I connect a November Jupiter to Eligius, cgminer and Eligius report a hashrate ~10% less than what is reported when I connect the same machine to BtcGuild (note that cgminer also reflects the same higher hashrate as BtcGuild when connected to BtcGuild).

I have no idea why this is occurring, but a 10% hashrate hit is substantial enough to switch pools.

No idea.  I'd love to actually try testing this a bit if anyone would lend remote access to an affected device, though.

I do feel the need to note that cgminer does *not* report the hash rate as seen by the pool (any pool) (bfgminer does, 3rd hash rate number).

In any case, you would really need a decently long (few days) test against each pool individually to actually see if you are in fact hashing faster/slower on one pool or another using pool-side stats.  What cgminer tells you is irrelevant.

-wk

[wizkid057]

Pool choice can not affect hardware error rate.  It is impossible by definition.

A hardware error is when the *hardware* has an issue. There could potentially be an issue in the mining software that can misreport hardware errors, but that also has nothing to do with the pool.

[kendog77]

Pool choice can not affect hardware error rate.  It is impossible by definition.

A hardware error is when the *hardware* has an issue. There could potentially be an issue in the mining software that can misreport hardware errors, but that also has nothing to do with the pool.

I agree. The problem is likely in cgminer.

[Beave162]

HELP I am trying to mine with bfgminer3.8.0, but it keeps crashing right after I enter the eligius information...

[seriouscoin]

I just notice the hashrate fluctuates alot for the past 2 hrs. Is the server overloaded? maybe network?

The pool's hashrate has grown alot recently, should we worry about the server's load?

[Biffa]

Pool choice can not affect hardware error rate.  It is impossible by definition.

A hardware error is when the *hardware* has an issue. There could potentially be an issue in the mining software that can misreport hardware errors, but that also has nothing to do with the pool.

I think we understand that a hardware error shouldn't be attributable to the pool.

What I would be interested to find out is what difficulty level is being set by VARDIFF on the machines?

My Oct Jupiter (552Gh/s) has a 512 diff, whereas the Nov Jup (654Gh/s) has a 1024 diff. That could have an affect?

I remember cgminer developers talking about the difficulty calculation being relative to the diff, but I could be wrong.

Wiz could you try setting the VARDIFF for >750Gh/s back to 512 see if that helps?

Or those who have moved pools can you check your KnC machines?

It shows in the cgminer status:

Connected to stratum.mining.eligius.st diff 1.02K with stratum as user blablahblah

[kria]

I too have had to take my November Jupiter to another pool. I got over 10% hardware errors and cores enabling/disabling constantly. After my 12hr avg @ Eligius dropped below 600, I switched to BTC Guild and now get 660-690 at the pool with 1.7% hardware errors and no cores goin on and off.

I noticed that my diff @ Eligius alternated between 512 and 1024 while I consistently get 256 @ BTC Guild, if that might have anything to do with it.

[helmax]

is impossible use this pool with jupiter november 10% hw is crazy

@wizkid057 if you want i can make remote for you see

now i am using ghash only  1.3% HW

http://awesomescreenshot.com/0e822tr3dd

pool eligius 10% HW more rejects, less WU and cores disables

http://awesomescreenshot.com/0dd22m3x20

[HellDiverUK]

HW errors are hardware errors, so it's probably a reporting issue.

Didn't I hear about a firmware for the KnC machines that use bfgminer instead of cgminer?