Eh? I think he was referring to my post? Or not? Yes, he was. I'm messing with you because he thinks I run around after his friend. Don't worry
|
|
|
I fired up a Xubuntu VM & the "temporary" branch wallet compiled fine (daemon only). It's currently downloading the blockchain with 2 connections. So far so good
|
|
|
What are the odds of their site popping up when BTC starts falling?.......
|
|
|
It's coming. Hang in there. Be strong. Any....minute....now....
|
|
|
Edit: If the results are OK in the morning I'll do a reboot to make sure the settings keep - if they do then it's all good & I'll update my other S5's I believe it will not. In which case, I may tweak this firmware instead If I do, I'll make 4.9.0 the default. Yeah, I ended up reverting back to my previous setup after all. The lower loads were nice but not nice enough to offset the lower hash rate I never tested to see if the settings were kept after a reboot though. @ Meuh6879: I've never seen 25 second latency spikes before......something wrong there buddy, connection issues perhaps?
|
|
|
Well, it's been a strange day today. Got neg'd by dogie then verbally attacked & insulted by this Carlton Banks guy while wishing the best to a new p2pool node: +1 for p2pool, the more the merrier Wow, what a lying POS. To all that it may concern: this is the same sock-puppet master who tried to destroy p2pool by bullying it's developer off the project. Recommendation is not to listen to one single word that comes out of it's slimy mouth. What on earth are you talking about Feel free to come over to the p2pool thread & explain how you came to this conclusion, as I don't want to derail OP's thread. ...does anyone know what he's going on about? I know he reads this thread, so here's my last conversation with forrestv from a few weeks ago for him to read: Click image or read it here: https://github.com/p2pool/p2pool/issues/270Hardly "bullying the developer" ......I've done nothing but support & promote p2pool since day one.....I'm confused......what's with the p2pool haters? Edit: BTW, here's what I got with the new Bitcoin Core client: ....nice
|
|
|
But why is the hash rate rising on the algorithms that aren't merge mined? Qubit, Skein, and Myr-Groestl are not merge mined.
Probably because miners who were straight mining the gpu algos have moved over due to the rising gpu difficulty merge mining has caused?
|
|
|
+1 for p2pool, the more the merrier Wow, what a lying POS. To all that it may concern: this is the same sock-puppet master who tried to destroy p2pool by bullying it's developer off the project. Recommendation is not to listen to one single word that comes out of it's slimy mouth. What on earth are you talking about Feel free to come over to the p2pool thread & explain how you came to this conclusion, as I don't want to derail OP's thread.
|
|
|
Thanks you very much. The node list worked for me for now but the synchronization is pretty slow. it needs its time. Could you provide a list of working nodes, please? The wallet synchronization stucks at the moment.
Here's a couple that my wallet are connected to: 91.108.68.164:55889 109.73.173.119:55889 You're welcome. First sync might be a little slow, but once it's done you'll be flying!
|
|
|
work for me
Hmmmm......that's strange, it worked for me the last time I used it a few weeks ago Anyways, good luck with your node(s)
|
|
|
Your link to p2pool.co is down
link p2pool.co is not a node pool but a node scanner Correct, they also used to run a node - but it closed. Now the node scanner is not working either - or is it just me?
|
|
|
REMEMBER Set backup pool preferably an p2pool node for example p2pool.co Your link to p2pool.co is down, so better not use that as a backup. It was an XT node btw - so that's 1 - 0 to the Core team! +1 for p2pool, the more the merrier
|
|
|
**sigh** Every time I come to this or most other hardware threads to see if there are any updates/answers I am bombarded with dog poo - it's tiring. Six ugly posts on the last page alone - it's really no surprise that the yap-yapping chiwawa has so many enemies on this forum. I should have kept him on my ignore list when he tried trolling the p2pool thread. Fixed now though: Nice trust rating btw......... That still requires the other party to pick it up when they refuse or avoid it in the first place.
Why don't you roll up at their doorstep with one of your fake ID's (not a shitty council one though) & hand it to them personally like you tried with your TAX friend pekatete? I'm sure they will take you seriously........ : Dogie, or should I say Adam AllCock: I'm sure I speak for many other readers of this thread when I say that I sincerely don't give a shit about whatever your beef is with Spondoolies. However, if you feel you have been scammed/hard done by/mislead or whatever by Spondoolies I suggest you open a scam thread in the appropriate section & make your case there like everyone else does & forum rules require. That way you can continue your vitriolic, imbecilic & cry baby "waffle" & we can all ignore it in peace. Everyone here already knows that Bitmain got rid of you because of your terrible attitude towards their customers & forum members in general, change the record FFS. The fact that Spondoolies are not deleting your putrid posts here tells me that you are not only wrong, but that they want everyone to see that you are wrong. Your behavior is appalling & embarrassing only to yourself. The worst thing about it is that you can actually be helpful to forum members when you want to be (or when there's money involved), you seem to go from one extreme to the other - schizophrenic almost. Be nice, follow the forum rules, stop talking FUD & STFU.
|
|
|
Edit: Just flashed it & queue is set at 8192 Searching for the parameters now to change it............ Edit 1: OK, changed the queue setting to 1 for testing. BEWARE: This firmware does not submit stale shares - I noticed the "no-submit-stale" parameter in the /etc/init.d/cgminer.sh file (line 69), so I deleted it as it is my understanding that the default cgminer setting will submit stales - very important for p2pool......I'll monitor it & report back later. Bummer. I'm pretty sure that not submitting stale shares is true for the default Bitmain firmware as well, though. Be aware that the bitmain fork also intercepts stale work and drops it inside their driver code - before the main cgminer engine gets to see it and decide based on the command line options. ... as can be seen in their fork here: https://github.com/bitmaintech/cgminer/blob/master/driver-bitmain.c#L1274Bloody hell. Why bitmain, why? Right, so what I need to do is replace the bitmain bork binary with the ck one at http://ck.kolivas.org/apps/cgminer/antminer/s5/ & drop it in /config/ in order to make it permanent after reboots - amiright? If so, I might need a little help with the commands on this one...... (linux amateur I am)
|
|
|
Edit: Just flashed it & queue is set at 8192 Searching for the parameters now to change it............ Edit 1: OK, changed the queue setting to 1 for testing. BEWARE: This firmware does not submit stale shares - I noticed the "no-submit-stale" parameter in the /etc/init.d/cgminer.sh file (line 69), so I deleted it as it is my understanding that the default cgminer setting will submit stales - very important for p2pool......I'll monitor it & report back later. Bummer. I'm pretty sure that not submitting stale shares is true for the default Bitmain firmware as well, though. Yes, it is After running a couple of hours I noticed the load was much lower with the smit firmware (down from ~2.6 to ~0.7!), making the GUI much more responsive, but the hash rate was very slightly lower. I changed the queue setting of 1 to 0 for a while & my DOA rate has reduced nicely (not that it was high anyway) with hardly any spikes - so I'm going to run it overnight & check it again in the morning. Very happy with the lower load readings though. Edit: If the results are OK in the morning I'll do a reboot to make sure the settings keep - if they do then it's all good & I'll update my other S5's
|
|
|
The basic problem is there is no way to appeal against files that are flagged as malware. All the official channels for review have no scope for you to argue that case.
Yup, Google are a law unto themselves. But it's strange that it's not a blanket ban, which is usually the case. I get the feeling there's more to this than meets the eye....... I don't know what to suggest - apart from a mass of email complaints from all cgminer users......now that would be something
|
|
|
That's strange, I can access your site no problem with Waterfox - which is a 64bit version of Firefox, & my AV (Comodo) has never flagged cgminer..... Google being evil again Yeah I'm not sure which versions of firefox are affected. On one PC it's fine but on another here (newer version) it comes up with the malicious warning. Try searching for cgminer in google as well and see if the site even shows up now. Your github page shows up top on all my search engines, but not your website http://ck.kolivas.org/apps/cgminer/And you're right, google are showing numerous dodgy sites for your software - unbelievable! Edit: Apparently, these guys handle suspected malware sites for google & a few other search engines: https://www.stopbadware.org/request-reviewGive them a go
|
|
|
That's strange, I can access your site no problem with Waterfox - which is a 64bit version of Firefox, & my AV (Comodo) has never flagged cgminer..... Google being evil again
|
|
|
Interesting. Can anyone tell me what nicehash have done to improve the bitmain firmware?
This firmware was not developed by Nicehash. It was developed by smit1237. Nicehash is just distributing it. There are a lot of changes. The cgminer version isn't the default broken Bitmain one, but instead a cgminer 4.8.0 that still submits stale shares. It might have a different default queue and expiry setting too, but I'm not sure about that. In my testing, it gives about 5% higher hashrate than the one S5s ship with on p2pool. The smit1237 firmware also allows you to upload custom cgminer binaries to /config/, where they will persist across reboots and will be used instead of the cgminer in (IIRC) /usr/local/bin/. OK, that sounds more like it. I might give it a go on one of my S5's & have a look-see what the queue & other settings are then, thanks for that info jtoomim Edit: Just flashed it & queue is set at 8192 Searching for the parameters now to change it............ Edit 1: OK, changed the queue setting to 1 for testing. BEWARE: This firmware does not submit stale shares - I noticed the "no-submit-stale" parameter in the /etc/init.d/cgminer.sh file (line 69), so I deleted it as it is my understanding that the default cgminer setting will submit stales - very important for p2pool......I'll monitor it & report back later.
|
|
|
|