OK - the emergency fix is ready. This finally solves the LP issues on deepbit and elligius. Please redownload.
64-bit:
http://www.gat3way.eu/poc/hashkill-0.2.4-x86_64.tgz
32-bit:
http://www.gat3way.eu/poc/hashkill-0.2.4-x86.tgz
Topic: hashkill - testing bitcoin miner plugin - page 10. (Read 90959 times)
I tried restarting the miner -- didn't help. (BTW, I'm a fellow programmer, so trying to isolate a problem is 2nd nature 
)
Deepbit started reporting a lot of stale shares (and Hashkill started complaining about the Long Polling, as I mentioned) -- when it starts to get over 2% I get nervous about not getting the most from my modest hardware. I'm only getting 20 MH/s more on my 2 cards with Hashkill -- which I love, don't get me wrong -- but if that 3.5% increase results in 2.5, 3, or 4% stale shares -- I have to do something.
You're right, it could be due to something on the Deepbit side -- is there anything the software could do to compensate, or deal with whatever it is? I don't think there's a server/debug log we could look at to see what's happening on the Deepbit side.
I like using Hashkill because I only have to run it once (instead of once per card), it's faster, and it makes me feel like I'm getting something extra for my 64-bit Linux install.
And a 3.5% increase is going to mean more and more as I add capacity. One more card on the way, for now.
)Deepbit started reporting a lot of stale shares (and Hashkill started complaining about the Long Polling, as I mentioned) -- when it starts to get over 2% I get nervous about not getting the most from my modest hardware. I'm only getting 20 MH/s more on my 2 cards with Hashkill -- which I love, don't get me wrong -- but if that 3.5% increase results in 2.5, 3, or 4% stale shares -- I have to do something.
You're right, it could be due to something on the Deepbit side -- is there anything the software could do to compensate, or deal with whatever it is? I don't think there's a server/debug log we could look at to see what's happening on the Deepbit side.
I like using Hashkill because I only have to run it once (instead of once per card), it's faster, and it makes me feel like I'm getting something extra for my 64-bit Linux install.
And a 3.5% increase is going to mean more and more as I add capacity. One more card on the way, for now.
Will have a look. It may also be a problem on the deepbit.net's side. Did it continue to throw that error or it stopped? Did restarting the miner fix that?
I am going to commit some fixes to the LP code today, fixing the eligius LP issue. Will have a look again at that.
BTW did you have a look at the speed as reported by deepbit?
I am going to commit some fixes to the LP code today, fixing the eligius LP issue. Will have a look again at that.
BTW did you have a look at the speed as reported by deepbit?
The error is happening again, Gat3way.
I just got 1% stales I noticed, and I looked at my terminal output and it's giving the "error" Long polling failure, will retry in 20s!
The error happened here: _bitcoin.c:232
hashkill-gpu -G 2 -D -p bitcoin XXXX:XXXX:deepbit.net:8332
I checked the MD5, and it checked out to be the latest version.
Hopefully you can fix it -- thanks!
Matthew
I just got 1% stales I noticed, and I looked at my terminal output and it's giving the "error" Long polling failure, will retry in 20s!
The error happened here: _bitcoin.c:232
hashkill-gpu -G 2 -D -p bitcoin XXXX:XXXX:deepbit.net:8332
I checked the MD5, and it checked out to be the latest version.
Hopefully you can fix it -- thanks!
Matthew
Thanx.
that is sad(
that is sad(
Hi!
Will there be a version for WINDOWS users?
Will there be a version for WINDOWS users?
Seems No & can't
http://forum.bitcoin.org/index.php?topic=12053
Hi!
Will there be a version for WINDOWS users?
Will there be a version for WINDOWS users?
.... did you fix it? I'm not sure if I should be waiting for you to post a new download link or try the old download link and hope it's the new version?
Ah, just tried. Dammit, they use relative URLs for that. OK, gotta fix that sorry.
I have the newest version.
Can someone quickly test against mining.eligius.st port 8337 or 80 ?
The beginning output says Long Polling was detected, but I get the warning about long polling failing every 20 seconds.
If you have downloaded prior versions, please make sure you are using the new version. Do:
For the 32-bit one it should return:
cda0feb360a2e81c5c93fbcfac86c6e6
And for the 64-bit one it should be:
855ec7e26d10b12845820dfbed1d9175
If those checksums don't match, please make sure:
* You don't have a browser caching issue with the download. Or if you have used wget, make sure you don't have it downloaded already so that the new download would be renamed to hashkill-....tgz.1
* You run the install.sh script with root privileges so that it is able to overwrite the old binary
Quote
md5sum /usr/bin/hashkill-gpu
For the 32-bit one it should return:
cda0feb360a2e81c5c93fbcfac86c6e6
And for the 64-bit one it should be:
855ec7e26d10b12845820dfbed1d9175
If those checksums don't match, please make sure:
* You don't have a browser caching issue with the download. Or if you have used wget, make sure you don't have it downloaded already so that the new download would be renamed to hashkill-....tgz.1
* You run the install.sh script with root privileges so that it is able to overwrite the old binary
Random question -
The last time I tried this, it kept complaining about long polling failure while using eligius.st
Update -
I just tried it again and it constantly complains of long polling on eligius.
I'm also getting nearly 20% stale/invalid...
The last time I tried this, it kept complaining about long polling failure while using eligius.st
Update -
I just tried it again and it constantly complains of long polling on eligius.
I'm also getting nearly 20% stale/invalid...
how does this compare with the phatk kernel?
I'm currently getting 302mh/s with 5830 976/300 on Win7
Would hashkill be able to beat that...I guess i could setup a linux machine to find out
Would it + stream sdk work thru a VM? (vmware etc...)
I'm currently getting 302mh/s with 5830 976/300 on Win7
Would hashkill be able to beat that...I guess i could setup a linux machine to find out
Would it + stream sdk work thru a VM? (vmware etc...)
@gat3way
when you get a chance check out the error with btcguild's long polling?
when you get a chance check out the error with btcguild's long polling?
Well, it's still worth using -D. Default speeds (without -D) should not change and using -D with the latest version tends to be slower than before...but still faster than without -D. -G2 is the default one on AMD cards. I guess -G3 or -G4 would not bring you much (but your CPU usage and power consumption would be up using them)
Has anything changed with the parameters? You said that multiple GPU setups should use -G 2 -D
But now you're saying that -D has been "de-fanged" and doesn't do much -- is it worth using at all?
Matthew
But now you're saying that -D has been "de-fanged" and doesn't do much -- is it worth using at all?
Matthew
Generally it is, but right now it's not a good measure. Any new LP notification would reset current getwork and cause a new one to be issued per thread and by default we use 2 threads/GPU. When using a pool that supports long polling, efficiency is likely getting slowly down with time. I have to take that into account when calculating the "efficiency" percentage. I guess you can ignore that. Just have a look at deepbit's pool reported speed. It should be either somewhat higher or lower than the speed reported by hashkill. If it is constantly below the speed reported by hashkill (as reported before) then we have a problem.
P.S your speed as reported by the pool would likely drop on a new block notification. That's because the current getwork is being reset and you've got to wait until it's fed with a new one. Depending on your network latency (I am using a wireless connection that is not very fast and stable) you may even see some tens of Mhash/s drop. It should quickly compensate for this though.
P.S your speed as reported by the pool would likely drop on a new block notification. That's because the current getwork is being reset and you've got to wait until it's fed with a new one. Depending on your network latency (I am using a wireless connection that is not very fast and stable) you may even see some tens of Mhash/s drop. It should quickly compensate for this though.
I created a new worker on deepbit.net, so I can see what they report as far as % stale shares.
What is the "eff" column mean?
Is that how efficiently I'm finding shares? In other words, how lucky I am?
I've seen it above 100% before. Right now it's at 87%.
What is the "eff" column mean?
Is that how efficiently I'm finding shares? In other words, how lucky I am?
I've seen it above 100% before. Right now it's at 87%.
Stales would be greatly decreased with that release at the cost of some little performance loss (but your pool should support long polling). You can also check against the speed reported by the pool.
Anyway, hashkill still lacks CPU verification prior to sending. So if you are overclocking your cards too much, it is possible that you are sending invalid shares (false positives) and hashkill would count them as "stale". That's another feature I would like to implement, some miners warn you about your hardware running unstable. Unfortunately, hashkill does not do that at present.
Anyway, hashkill still lacks CPU verification prior to sending. So if you are overclocking your cards too much, it is possible that you are sending invalid shares (false positives) and hashkill would count them as "stale". That's another feature I would like to implement, some miners warn you about your hardware running unstable. Unfortunately, hashkill does not do that at present.
Sounds good -- thanks!
I have some good figures to compare to -- I was running Poclbm for about 5 hours today; My rate stales was almost exactly 0.7% on each of the 2 cards.
I'll look at it around 9:00 tonight and see if I'm getting less stales. That would be great!
Matthew
I have some good figures to compare to -- I was running Poclbm for about 5 hours today; My rate stales was almost exactly 0.7% on each of the 2 cards.
I'll look at it around 9:00 tonight and see if I'm getting less stales. That would be great!
Matthew
Jump to: