BTW any word on using more than 32 pools??
I wasn't serious... but anything can be done. You really want this?
|
|
|
We were all waiting for ASIC announcement today....
Great....another product that they will fail miserably at delivering in a timely fashion.... Now imagine them holding onto $XX000 dollars for an extra 10 weeks...
|
|
|
Hasn't helped here. Look at this example: The longpoll for the same block from pool 1 (mtred) came 22 seconds after pool 0. [2012-06-16 08:36:23] Accepted 3081346c.7df52c66 GPU 1 pool 1 [2012-06-16 08:36:24] LONGPOLL from pool 0 detected new block [2012-06-16 08:36:24] Accepted bb0486ca.a2f61826 GPU 1 pool 1 [2012-06-16 08:36:24] Accepted 97383d46.18ef510d GPU 1 pool 1 [2012-06-16 08:36:25] Accepted 522a0965.590b8cd5 GPU 3 pool 1 [2012-06-16 08:36:26] Accepted e7d62d63.4dad9f5b GPU 3 pool 1 [2012-06-16 08:36:46] LONGPOLL from pool 1 requested work restart [2012-06-16 08:36:46] Stale share detected, submitting as user requested [2012-06-16 08:36:46] Rejected 4f88da5e.cebd5d8c GPU 1 pool 1 [2012-06-16 08:36:46] Rejected e8af7698.e9cb7a55 GPU 1 pool 1 [2012-06-16 08:36:46] Rejected d5eabcf4.3afa91ce GPU 0 pool 1 [2012-06-16 08:36:46] Rejected 7eda54a1.c6488d05 GPU 0 pool 1 [2012-06-16 08:36:46] Rejected dca7a30a.05a49c40 GPU 3 pool 1 [2012-06-16 08:36:46] Rejected c4bb27a2.1f0e985e GPU 1 pool 1 [2012-06-16 08:36:46] Rejected 8d77b5c5.bbdc4427 GPU 3 pool 1 [2012-06-16 08:36:46] Rejected 8c264688.49911866 GPU 2 pool 1 [2012-06-16 08:36:46] Rejected e6202908.5a500b11 GPU 1 pool 1 [2012-06-16 08:36:46] Rejected 84d3f584.8958e243 GPU 0 pool 1 [2012-06-16 08:36:46] Rejected 4978bc94.4ae7e10d GPU 3 pool 1 [2012-06-16 08:36:47] Rejected fc8c7c53.4ca73617 GPU 0 pool 1 [2012-06-16 08:36:47] Rejected 6f0a6a97.2c9ff043 GPU 0 pool 1 [2012-06-16 08:36:47] Rejected cdb23b55.d619456f GPU 2 pool 1 [2012-06-16 08:36:50] Accepted 4eac1983.1cef3e60 GPU 3 pool 1 [2012-06-16 08:36:54] Accepted 8cec7926.55893b50 GPU 3 pool 1 [2012-06-16 08:36:54] Accepted 3e436c4a.08169b6a GPU 2 pool 1 [2012-06-16 08:36:55] Accepted 5f2da69b.8ebf2d6e GPU 1 pool 1 [2012-06-16 08:36:56] Rejected af974aec.80402f3f GPU 1 pool 1 [2012-06-16 08:36:56] Accepted 486cb950.d697292c GPU 3 pool 1 [2012-06-16 08:36:56] Accepted 660719e3.2b22933c GPU 2 pool 1
There was also nothing accepted for 20 seconds which at a utility of 39 shares/minute there should be ~13 shares. The 15 rejected shares works out to ~23 seconds of lost work.
|
|
|
bitlane acknowledged it might just well be 10 weeks, but the point of his post was how long he has paid for an investment that is not mining. That makes their return on investment time longer much worse. * ckolivas hugs his 7970s
|
|
|
With the latest master, on OpenWRT (TP-Link MR3220) I can't use ztex boards anymore. Haven't got time to properly debug this now so I thought I'd just leave this here in case it is obvious to anyone: [2012-06-14 14:41:10] Popping work to stage thread [2012-06-14 14:41:13] ZTEX 0000000001-1: Share found N0E0 [2012-06-14 14:41:13] Proof: 000000008f655a7694a8933c6eb9b38330a8be710c299dd2a2785220d2832b30 Target: 00000000ffffffffffffffffffffffffffffffffffffffffffffffffffffffff TrgVal? YES (hash < target) [2012-06-14 14:41:13] Pushing submit work to work thread [2012-06-14 14:41:13] ZTEX 0000000001-1: submitted 23c2895c 1 [2012-06-14 14:41:13] Popping work to work thread [2012-06-14 14:41:13] Creating extra submit work thread Bus error
It works great until a share is found, then it dies an immediate and horrible death ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) I was hoping the code for testing if it was a block solve was fixed for openwrt so I removed the commenting out of that test. I guess it was premature and that bug still exists. This is the commit responsible in git: dbe9056df4db4007524af9569edc28c92827b3c4
|
|
|
ckolivas excuse me, where I can download?
phatk110817Caymanbitalignv2w256long4.bin phatk110817Cypressbitalignv2w256long4.bin phatk110817Juniperbitalignv2w256long4.bin
it is not downloaded automatically
They're automatically generated when you run cgminer so you don't need to download them. However if you are after binaries from different SDK versions to what you have installed, you're out of luck as I stopped collecting them because it was getting too much effort to keep them all.
|
|
|
I seem to be getting a heck of a lot more rejects across longpolls lately. There's a deathly pause where no shares are being accepted, then the longpoll hits and a ton of rejects are returned along with it. eg: [2012-06-15 19:56:56] Accepted 474d3cb6.ba57e09a GPU 2 pool 1 [2012-06-15 19:57:03] LONGPOLL from pool 1 detected new block [2012-06-15 19:57:03] Rejected a3a7776a.c2c0c81a GPU 2 pool 1 [2012-06-15 19:57:03] Rejected 5dccdbc1.5ce6dc85 GPU 2 pool 1 [2012-06-15 19:57:03] Rejected de781d20.116097a9 GPU 1 pool 1 [2012-06-15 19:57:03] Rejected 14500521.6ac58d17 GPU 0 pool 1 [2012-06-15 19:57:03] Rejected 06324d16.70e994b1 GPU 1 pool 1 [2012-06-15 19:57:04] Rejected 26a5920b.8961c4bc GPU 0 pool 1 [2012-06-15 19:57:04] Rejected 1ee51bba.9676a3f7 GPU 3 pool 1 [2012-06-15 19:57:06] Accepted 05aac654.90f7fb03 GPU 2 pool 1
I've seen up to twice as many rejects as this too. This machine has 2.75GH on cgminer 2.4.3 edit: here's a monster one: [2012-06-15 21:17:58] LONGPOLL from pool 1 detected new block [2012-06-15 21:17:58] Rejected 077a4ecf.50e39ba5 GPU 2 pool 1 [2012-06-15 21:17:58] Rejected 56324165.ec7de8e2 GPU 0 pool 1 [2012-06-15 21:17:58] Rejected 9d2aa7fc.d23f797f GPU 1 pool 1 [2012-06-15 21:17:58] Rejected 74b0100e.c34e0f49 GPU 2 pool 1 [2012-06-15 21:17:58] Rejected a0519268.132c3f8d GPU 0 pool 1 [2012-06-15 21:17:58] Rejected 75f067a6.964e1a6f GPU 2 pool 1 [2012-06-15 21:17:58] Rejected 95e2c906.27d56c1f GPU 1 pool 1 [2012-06-15 21:17:58] Rejected c808a07d.0c463b4d GPU 1 pool 1 [2012-06-15 21:17:58] Rejected 6cbaaa10.6f668321 GPU 0 pool 1 [2012-06-15 21:17:58] Rejected d9c213f5.59d8669c GPU 2 pool 1 [2012-06-15 21:17:58] Rejected 2fdd68a6.958e8e8a GPU 0 pool 1 [2012-06-15 21:17:58] Rejected e184cc0e.efd0623e GPU 0 pool 1 [2012-06-15 21:17:58] Rejected e2d28c95.a5fe6a22 GPU 0 pool 1 [2012-06-15 21:17:58] Rejected 84e33d33.f6ecc4d7 GPU 3 pool 1 [2012-06-15 21:17:58] Rejected aee3afb1.fa8c347b GPU 1 pool 1 [2012-06-15 21:17:58] Rejected 1d8d471b.eae8b003 GPU 3 pool 1 [2012-06-15 21:17:58] Rejected 51eda82a.32ff74bb GPU 2 pool 1 [2012-06-15 21:17:58] Rejected 795eb39c.81b5f967 GPU 2 pool 1 [2012-06-15 21:17:58] Rejected 38d95929.1639c0cd GPU 3 pool 1 [2012-06-15 21:17:58] Rejected d038c576.e0024be2 GPU 1 pool 1 [2012-06-15 21:18:00] Accepted 661e54c2.34f7804e GPU 1 pool 1 [2012-06-15 21:18:01] Accepted 811e9c36.d9f71791 GPU 0 pool 1 [2012-06-15 21:18:01] Accepted 5e472b8e.3c6faf8c GPU 3 pool 1 [2012-06-15 21:18:02] Rejected c09b5d56.3c8a7a88 GPU 2 pool 1 [2012-06-15 21:18:03] Accepted a5f0834f.faa26cb0 GPU 0 pool 1 [2012-06-15 21:18:04] Rejected 3e35a364.1a58cc24 GPU 3 pool 1 [2012-06-15 21:18:05] Accepted 84ab8f58.0ccc74d6 GPU 3 pool 1 [2012-06-15 21:18:06] Rejected 32b6baa8.30c20107 GPU 1 pool 1 [2012-06-15 21:18:08] Accepted d5fb6e21.1cae1fd4 GPU 1 pool 1
|
|
|
Does CGMINER support multiple backup/fallback pools?
I've noticed that a number of pools will be down or lagging at any given time, so I'm looking to set up 3-5 backup pools to mitigate all this downtime I'm seeing on my miners. Been using GUIminer up to now, but the 1 backup server option still leaves me running idle every now and then.
cgminer supports no more than 32 pools I'm afraid. I can remove that limit in the next version if it's desired...
|
|
|
BFI INT does not work the same way on 7xxx. They automatically do BFI INT without you specifying anything and if you manually patch the kernel with BFI_INT (as mining software does) then the kernel doesn't actually work.
|
|
|
I think you should put in a default Enabled donation rate of .001%, And have it stated blatently that cgminer wishes to ask for a .001% hashed donation, Search the thread: in-cgminer-donation has been tried and wasn't worth the trouble. Awwwww that sucks ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) The donation feature was around for many months and the total hashrate donated averaged about 200MH during that time. It also introduced some bugs of its own which penalised the very people who were donating (until I fixed the bugs). When I suggested it be enabled by default (with the ability to disable it) I got crucified in the forum so I just abandoned the donation feature entirely and hope that people will feel like donating the old fashioned way.
|
|
|
Successfully hitting 1260 would be extraordinary and would require water cooling and probably overvolting.
|
|
|
Effect of poolhoppers is negligible, I'm trying to scare them off ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) How? It's obviously not with your payment scheme since it's pure prop, unless it's not truly that...
|
|
|
New release: Version 2.4.3, June 14 2012
Human readable changelog:
-Mod miner FPGA support. -Fixes for load balance and rotate pool strategies -GPU engine speed changes - will not increase GPU speed if the fanspeed is above the maximum. -Improvements in detecting lagging pools -Lots of other minor fixes -Linux binaries now compiled for Ubuntu 12.04
Full Changelog:
- can_roll and should_roll should have no bearing on the cycle period within the miner_thread so remove it. - Check for strategy being changed to load balance when enabling LPs. - Check that all threads on the device that called get_work are waiting on getwork before considering the pool lagging. - Iterate over each thread belonging to each device in the hashmeter instead of searching for them now that they're a list. - When using rotate pool strategy, ensure we only select from alive enabled pools. - Start longpoll from every pool when load balance strategy is in use. - Add mandatory and block fields to the work struct. Flag any shares that are detected as blocks as mandatory to submit, along with longpoll work from a previously rejecting pool. - Consider the fan optimal if fanspeed is dropping but within the optimal speed window. - Fix typo in some API messages (succeess/success) - api.c MMQ stat bugs - Bugfix: Fix warnings when built without libudev support - Bugfix: slay a variety of warnings - Bugfix: modminer: Fix unsigned/signed comparison and similar warnings - API add ModMinerQuad support - Bugfix: Honour forceauto parameter in serial_detect functions - modminer: Temperature sensor improvements - modminer: Make log messages more consistent in format - Only adjust GPU speed up if the fanspeed is within the normal fanrange and hasn't been turned to maximum speed under overheat conditions. - ModMiner use valid .name - New driver: BTCFPGA ModMiner - Abstract generally useful FPGA code into fpgautils.c - API add stats for pool getworks - miner.php option to hide specific fields from the display - miner.php add version numbers to the summary page - Update debian configs to v2.4.2 - Add API and FPGA READMEs into Makefile to be included in source distribution. - Icarus - fix unit64_t printf warnings
|
|
|
The amd driver seems to have scope for 16 devices but no one has successfully booted more than 8.
|
|
|
Perhaps in my case because they're all running on 16x slots and they're 7970s I hit the limit earlier.
Yeah shouldn't be too big of an issue since it's working for you now. That's a pretty good thought. Must be why some mobos reduce the speed as you add more cards. So the solution is to use only x1 risers to force x1 speeds and avoid x16 negotiations ? I'm pretty sure I've seen people suffer this with x1 as well, but usually when in combination with some higher speed ones, so perhaps with all of them 1x this is true... OR it could be the reason no one has successfully used more than 8 devices?
|
|
|
Try increasing your PCIE latency from 64 to 96 in the bios. Worked for me when I added my last 7970 when nothing else would.
|
|
|
Today i update the driver to 12.6 beta, remove the includet sdk and install the 2.1 sdk. Now the prob is, that cgminer seem to work with ~350mh/s, but there are no shares at all?!? wtf...
2.1 sdk does NOT work with the newer 12.x drivers at all. They are simply incompatible I'm afraid. Um. I use 12.1 driver and my 2.1 SDK works just fine. Try breaking it with 12.4 ![Wink](https://bitcointalk.org/Smileys/default/wink.gif)
|
|
|
Perhaps in my case because they're all running on 16x slots and they're 7970s I hit the limit earlier.
|
|
|
I've seen it reported on numerous occasions that on some motherboards when you get to about 5 GPUs, they won't work unless you increase the PCIE latency from 64 to 96 in the bios. As it turns out I recently added a 4th 7970 to my GD70 motherboard and ran into precisely that issue. Xorg would crash every time I tried to start it with all 4 GPUs. So I went into the bios and tried upping the PCIE latency to 96 and then it worked fine. Anyone know why that is?
|
|
|
|