GUI mining - updated Dec 3 with 7970 bugfix, also supports Stratum! - page 33.

becoin

legendary

Activity: 3431

Merit: 1233

Quote from: Kiv on June 15, 2011, 12:32:31 PM

What is shown there is a "difficulty 1 hash" being reported, which is analogous to a share being reported in a pool.

Exactly. Which means 'difficulty 1 hash 1' is analogous to 'shares 1 hash 1'... And this is precisely what we see on 'Summary' tab - Accepted 1 (1). There is no point in accepting 'Difficulty 1 (1), of course.

Quote

Just as a small fraction of shares are valid solutions to a block, a small fraction of these hashes are valid solutions to a block.

I don't get this at all.

There is only one valid solution to a block, not many. Whatever small they are, shares are always part of a valid solution to a block. Otherwise, they wouldn't be shares at all, because they would be shares of zero!

This explanation is rather unconvincing, Kiv. Sorry.

Kiv

full member

Activity: 162

Merit: 100

Hi becoin, in this case a block was not actually solved and thus you didn't get the 50 BTC. What is shown there is a "difficulty 1 hash" being reported, which is analogous to a share being reported in a pool. Just as a small fraction of shares are valid solutions to a block, a small fraction of these hashes are valid solutions to a block.

In the case of a block being solved it would show "Blocks: 1" in the miner's tab.

Sorry to get your hopes up on winning the 50 BTC lottery

I am not sure if I should re-word the terminology since I think it's quite confusing, but I don't know what to call it instead.

Quote from: becoin on June 15, 2011, 01:26:02 AM

Quote from: Kiv on June 14, 2011, 09:26:44 PM

A new version of the miner is available

Kiv, thanks for the great work you do for all BTC enthusiasts.

Yesterday, however, something very strange happened. I was using guiminer solo to mine and despite very low hash generation power (about 1.5 Mhash/s) a block was solved and the corresponding single share accepted. But I didn't get the 50 BTC on my bitcoin balance... This has happened somewhere in between blocks 130798-130805. Could you please help explain what went wrong? See below screen shots I made:

---

Thanks for taking the time to have a look at it.

markietalkie

newbie

Activity: 16

Merit: 0

Linuxcoin seriously needs this. Could this be installed via Synaptics in the future?

chaud

newbie

Activity: 17

Merit: 0

Quote from: Kiv on June 14, 2011, 09:26:44 PM

For everyong asking about restarting support: I was thinking of doing it so if there were no accepted shares in X minutes (X being configurable per miner) it would restart the miner.

Yes please, that would be great.

stellan0r

hero member

Activity: 574

Merit: 500

Medical Translations for Bitcoins

Quote from: Kiv on June 14, 2011, 09:26:44 PM

A new version of the miner is available; I've updated the download link on the first post, or you can get it here:

For switching to a backup pool support: just using the -f flag to set priorities as described in the FAQ works just fine for me. I don't particularly want to do something elaborate unless there's a convincing case. If people can't figure out how to use the -f flag then that's actually a documentation bug and I should fix that

Thank you for the Update!
Regarding the -f support, I hope I did understand right that for using phoenix miner I have to use the AGGRESSION= setting instead. But if I do so, if a miner with a high aggression (like 13 or 14) fails because the pool goes down, and my backup miner has aggression <10, that one goes nowhere near 100% hashing power when the "master miner" stops working.

Any ideas? (except switching to opencl miner instead of phoenix Grin

)

becoin

legendary

Activity: 3431

Merit: 1233

Quote from: Kiv on June 14, 2011, 09:26:44 PM

A new version of the miner is available

Kiv, thanks for the great work you do for all BTC enthusiasts.

Yesterday, however, something very strange happened. I was using guiminer solo to mine and despite very low hash generation power (about 1.5 Mhash/s) a block was solved and the corresponding single share accepted. But I didn't get the 50 BTC on my bitcoin balance... This has happened somewhere in between blocks 130798-130805. Could you please help explain what went wrong? See below screen shots I made:

---

Thanks for taking the time to have a look at it.

Kiv

full member

Activity: 162

Merit: 100

A new version of the miner is available; I've updated the download link on the first post, or you can get it here:

guiminer-20110614.exe (self-extracting archive)

Changes:

- Slush's pool moved from mining.bitcoin.cz to api.bitcoin.cz. If any miners on slush's pool cannot connect, you should delete and re-create the worker to make sure it's using the new address.
- Add CPU affinity support, meaning miners can be assigned to a specific CPU core. Users seeing the 100% CPU usage when mining with OpenCL due to buggy drivers can reduce their CPU usage by allowing the miner to only run on a specific core.
- Fix error about missing logo.ico.
- New Italian translation, big thanks to MasterHunterHD for contributing this.

Thanks to all other translators who submitted updated translations to me, I'm afraid I added even more text in this version for you.

For everyone asking about Linux support: for the adventurous you can try running it from source on GitHub. The only thing stopping me now is finding a nice way to install it; it doesn't seem like I can nicely bundle everything together in an EXE like I do on Windows. Maybe I can somehow include it with LinuxCoin (though I don't know what that is right now). Any Linux gurus that could help me out with this would be appreciated

For everyong asking about restarting support: I was thinking of doing it so if there were no accepted shares in X minutes (X being configurable per miner) it would restart the miner.

For switching to a backup pool support: just using the -f flag to set priorities as described in the FAQ works just fine for me. I don't particularly want to do something elaborate unless there's a convincing case. If people can't figure out how to use the -f flag then that's actually a documentation bug and I should fix that

Kiv

full member

Activity: 162

Merit: 100

Thanks for the report, I'll fix this when I get a chance.

Quote from: FuzzyCoins on June 13, 2011, 07:17:10 PM

I notice that when I have multiple pools defined (as backup pools) and when one of the primary pools goes down (GUIMiner reports "Connection problems"), the total hash rate down in the lower right corner retains the last seen hash rate from the pool connection that went down instead of zeroing it out.

Or in other words if I have two miners defined and one is normally running at 200 Mhash/sec and the other runs at 1Mhas/sec (lower priority), my total hash rate is reported as 201Mhash/second as expected.

If the first miner goes down with connection problems and the second minor ramps up to 200 Mhash/sec, the total reported is like 400Mhash/sec. It appears that during "connection problems" GUIMiner still thinks the downed miner is running at full speed.

Edit: 2 typos.

dishwara

legendary

Activity: 1855

Merit: 1016

Quote from: Kiv on June 10, 2011, 08:53:08 PM

Hey everyone, I am putting out a BETA release to try and fix the weird "logo.ico" error a couple people reported. It also has a test version of CPU affinity built in, so if that's a feature you were waiting for you can test that out too for me

The BETA version is here:

GUIMiner BETA 20110610

If this resolves the logo issue and there's no bugs with the affinity, I'll do a full release of it in the next couple days.

I tired the BETA version & it works fine.
The affinity works perfectly.
I am using BETA in 2 systems. one with single miner & another with 3 miner. Both working fine for the past 3-4 hours with out any problem

um0rion

member

Activity: 91

Merit: 10

I get a connection error on one of my cores about once a day, something to restart a miner that gets stuck would be fantastic. Also, Slush added an address to mine at... api.bitcoin.cz.

Any plans to release a new version?

mjsbuddha

sr. member

Activity: 336

Merit: 250

yung lean

Just adding my name to the list of people that desire some sort of fail over support.

FuzzyCoins

newbie

Activity: 29

Merit: 0

I notice that when I have multiple pools defined (as backup pools) and when one of the primary pools goes down (GUIMiner reports "Connection problems"), the total hash rate down in the lower right corner retains the last seen hash rate from the pool connection that went down instead of zeroing it out.

Or in other words if I have two miners defined and one is normally running at 200 Mhash/sec and the other runs at 1Mhas/sec (lower priority), my total hash rate is reported as 201Mhash/second as expected.

If the first miner goes down with connection problems and the second minor ramps up to 200 Mhash/sec, the total reported is like 400Mhash/sec. It appears that during "connection problems" GUIMiner still thinks the downed miner is running at full speed.

Edit: 2 typos.

Nachtwind

hero member

Activity: 700

Merit: 507

Hi, Good work on your program :0)

Have to bump my "problem":

Code:

2011-06-09 22:01:01: Listener für "btc": [09/06/2011 22:01:01] Server gave new work; passing to WorkQueue
2011-06-09 22:01:33: Listener für "btc": [09/06/2011 22:01:33] Server gave new work; passing to WorkQueue
2011-06-09 22:01:34: Listener für "btc": [09/06/2011 22:01:34] Result 0000000030e7a466... accepted
2011-06-09 22:02:06: Listener für "btc": [09/06/2011 22:02:06] Server gave new work; passing to WorkQueue
2011-06-09 22:02:07: Listener für "btc": [09/06/2011 22:02:07] Result 0000000014d660b7... accepted
2011-06-09 22:02:16: Listener für "btc": [09/06/2011 22:02:16] LP: New work pushed
2011-06-09 22:02:16: Listener für "btc": [09/06/2011 22:02:16] Server gave new work; passing to WorkQueue
2011-06-09 22:02:17: Listener für "btc": [09/06/2011 22:02:16] New block (WorkQueue)
2011-06-09 22:02:19: Listener für "btc": [09/06/2011 22:02:19] Server gave new work; passing to WorkQueue
2011-06-09 22:02:48: Listener für "btc": [09/06/2011 22:02:48] Server gave new work; passing to WorkQueue
2011-06-09 22:02:52: Listener für "btc": [09/06/2011 22:02:52] Result 000000009e62c6a7... accepted
2011-06-09 22:03:03: Listener für "btc": [09/06/2011 22:03:03] Result 00000000fe0c49b8... accepted
2011-06-09 22:03:20: Listener für "btc": [09/06/2011 22:03:20] Server gave new work; passing to WorkQueue

Somewhat my console is full with these signs... no matter what i replace or do.. (on cmd it doesnt show up though)

Then i have a small feature to ask for:
Can you do "schedules"? Like having from 1am to 8am running profile a, from 8am to 3pm profile b and so on? I would really love to set my agression settings depending on my sleep/university/work/others automatically...

Coinbuck @ BTCLot

hero member

Activity: 540

Merit: 500

The future begins today

Phoenix and the normal OpenCL miner are consuming 25% of my CPU while mining a CPU !!

becoin

legendary

Activity: 3431

Merit: 1233

Quote from: Dobrodav on June 13, 2011, 11:33:57 AM

For now, most suitable version of bitcoin client for windows is 0.3.20.

I've installed older version 0.3.21 and then tried 0.3.20. Message for problem connecting to bitcoin RPC disappeared. It is showing the correct Mhash/s rate, but it is also showing 'Difficulty 1 hashes: 0'. Isn't it supposed to show the correct difficulty for current block?

Thanks again for help.

short

newbie

Activity: 21

Merit: 0

Quote from: jonnynogood on June 11, 2011, 02:56:29 AM

please make a linux version of this preferably that would work with linuxcoin

I'll copy that. Besides that, great piece of work so far!

People, donate where donation is due!!

cheers,

short

chaud

newbie

Activity: 17

Merit: 0

Quote from: Lightspeed on June 13, 2011, 07:38:06 AM

after 10 minutes of no activity / no connection - play an alarm (make it optional, the length of time configurable and the sound/music play mp3 + wav files with 1 default one included in the app)

Forget the alarm, just kill off the old miner process if it is still around and restart. Phoenix keeps stopping for no reason and I keep losing mining time.

stellan0r

hero member

Activity: 574

Merit: 500

Medical Translations for Bitcoins

Great work Kiv!

I have two questions for you:

Are you working on a version for Linux already, or do you need to get a better poll result for that?

And second, this was already asked for, can you please put a "idle/disconnect worker" feature in it? Say if have 6 different pools set up and I am always running 2 miners/pools on 1 gpu, now one or two of these go down, I want guiminer to auto-switch to the other miners i have set up in either a random or defined order - and maybe a switch back feature, guiminer checks if the miners can reconnect to pool 1 or 2 after X minutes and quit work with miner/pool 3 or 4 and so on. A way you kind of never stop mining for one of your favorite pools!

Would be totally awesome if this feature would be possible and be build in

Dobrodav

sr. member

Activity: 350

Merit: 250

For now, most suitable version of bitcoin client for windows is 0.3.20.

Lightspeed

full member

Activity: 126

Merit: 100

I want:

yes another backup pool request

after 10 minutes of no activity / no connection - play an alarm (make it optional, the length of time configurable and the sound/music play mp3 + wav files with 1 default one included in the app)

bottom right total hashrate, as soon as I hit 1Ghash/sec I want to be able to see another 2 decimal places - can you add this? since there is no total column in MH/s it makes it harder to judge risk/rewards for overclocking/total heat output etc (im too lazy to sit there with a calculator)

Topic: GUI mining - updated Dec 3 with 7970 bugfix, also supports Stratum! - page 33. (Read 3232170 times)