I've just updated my strapmod utility to handle R9 straps: ~/github/strapread$ ./strapmod.py 7771332000000000EF516A3790550F1232179A05006AE40022AA1C0874021420CA89C0A8020000C01510232859283315
R9 strap detected
Old, new RRD: 0 , 5
Old, new FAW: A , 0
Old, new 32AW: 7 , 0
Old, new ACTRD: 15 , 0x10
7771332000000000EF516A3790550F1232179A05006AE40022AA1C0874021420CA89C0A8020000C01510232859283315
7771332000000000EF515A3790550F1232179A050060040022AA1C0874021420CA89C0A8020000C01010232859283315
Does this work using the lazy fools' tool? On a semi-related note...is Debian stable a good distro to start using linux? Not for doing anything fancy...but just web browsing and email and maybe some mining and folding and more importantly getting familiar with the OS. |
|
|
|
There's been HBM mentioned earlier before in this topic....
I got my hands on my first card with HBM (Sap Fury Nitro).
It's behaviour is f@ckin magic! Totally different from GDDR5.
I got ideas from modded Nano and Fury X roms from the OCN thread and copied 400 timings to 500&600.
But nothing changed even a bit, although I copied the straps to both 00 & 01 tables! The hashrates remained exactly the same.
I discovered there is a much more complex mechanism that determines timings dynamically.
Clearly there are frequency ranges about ~20MHz wide, where the timings change gradualy.
I found a sweet spot where I get above 33mh with stock timing, but there is much more I think.
And also there is a strong connection between GPU&HBM freqs, the performance gain is not linear.
And what is with that 100MHz first strap? (There are straps for 100, 400, 500, 600)
So many questions...so much pain..!?
Get on it! I wanna be ready for Vega  |
|
|
|
I have been watching this thread with anticipation of jumping into the RX480 world.
Last week tried to order a bunch of MSI RX480 X Gaming 8GB. Both Jet and B&H Photo said were in stock. Just got an email from both saying manufacturer shortage. They each cancelled the order. Sounds to me like Vega release might be imminent.
Sorry, I know it's off topic, sort of.
Vega release IS imminent (May or June). Also the 500 series Polaris rebrands which will be the direct replacement are due this month. |
|
|
|
|
The devfee always begins x minutes after you start mining (I think x=15...at least it did for the ZEC miner) and then every hour after that. Just don't stop or close the miner and it will only happen once per hour like it's supposed to.
|
|
|
|
Uhh that's the reason I was asking. Where can I find a list of nodes and their addresses? I am trying to solo mine but many of the blocks come in 2 or 3 at a time so I think I need more peers so blocks get propogated faster. |
|
|
|
So far I haven't found anything. Scoured the OP, block explorers, network stats, and github for this info. Problem seems to be getting worse as now I'm getting 2 and 3 blocks at a time more frequently than before, and occasionally 4 blocks before any get imported now. Seems if I do manage to mine any it will just be an orphan.
have you tried the UBQ slack? we have a channel just for miners and i think most people interact wit the community in the slack...I think youll get some quicker feedback and help if you join.. http://slack.ubiqsmart.com/good luck Ehh I don't have slack currently but it looks like I might have to get it. It's the only way to get info for certain other coins too apparently. Was hoping it was just publicly available already. Coincidentally though I just mined 2 blocks and neither of them were orphans so that's good...but I may have just gotten lucky and still have a higher orphan rate than I should over the longer term. As you can see the time between block imports is pretty inconsistent with several minutes in between sometimes and then getting 2 or 3 at once. I0403 15:14:12.197818 core/blockchain.go:1097] imported 1 blocks, 0 txs ( 0.000 Mg) in 13.000ms ( 0.000 Mg/s). #64578 [94e61b1a.]
I0403 15:14:12.199818 miner/worker.go:496] commit new work on block 64579 with 1 txs & 0 uncles. Took 1ms
I0403 15:17:10.549019 miner/unconfirmed.go:83] ?? mined potential block #64579 [8b8e92a2.], waiting for 5 blocks to confirm
I0403 15:17:10.552020 miner/worker.go:496] commit new work on block 64580 with 2 txs & 0 uncles. Took 3.0002ms
I0403 15:19:13.639060 core/blockchain.go:1097] imported 1 blocks, 2 txs ( 0.042 Mg) in 16.000ms ( 2.625 Mg/s). #64580 [7a49d917.]
I0403 15:19:13.644060 miner/worker.go:496] commit new work on block 64581 with 1 txs & 0 uncles. Took 3.0002ms
I0403 15:20:33.206611 core/blockchain.go:1097] imported 2 blocks, 1 txs ( 0.021 Mg) in 16.000ms ( 1.312 Mg/s). #64582 [ad97cd6c. / 136a04f2.]
I0403 15:20:33.208611 miner/worker.go:496] commit new work on block 64583 with 1 txs & 0 uncles. Took 1.0001ms
I0403 15:23:11.178646 core/blockchain.go:1097] imported 1 blocks, 1 txs ( 0.021 Mg) in 14.000ms ( 1.500 Mg/s). #64583 [8812dcad.]
I0403 15:23:11.181646 miner/worker.go:496] commit new work on block 64584 with 2 txs & 0 uncles. Took 2.0001ms
I0403 15:23:14.906859 core/blockchain.go:1097] imported 1 blocks, 2 txs ( 0.042 Mg) in 26.001ms ( 1.615 Mg/s). #64584 [5920a81c.]
I0403 15:23:14.909860 miner/worker.go:496] commit new work on block 64585 with 1 txs & 0 uncles. Took 2.0001ms
I0403 15:23:14.910860 miner/unconfirmed.go:105] ?? mined block #64579 [8b8e92a2.] reached canonical chain
I0403 15:26:11.158940 core/blockchain.go:1097] imported 1 blocks, 1 txs ( 0.021 Mg) in 17.000ms ( 1.235 Mg/s). #64585 [a3959a8c.]
I0403 15:26:11.162941 miner/worker.go:496] commit new work on block 64586 with 2 txs & 0 uncles. Took 2.0001ms
I0403 15:28:54.123262 core/blockchain.go:1097] imported 1 blocks, 2 txs ( 0.042 Mg) in 26.001ms ( 1.615 Mg/s). #64586 [ca44ee76.]
I0403 15:28:54.127262 miner/worker.go:496] commit new work on block 64587 with 1 txs & 0 uncles. Took 1.0001ms
I0403 15:29:08.312073 core/blockchain.go:1097] imported 1 blocks, 1 txs ( 0.021 Mg) in 14.000ms ( 1.500 Mg/s). #64587 [14430b2e.]
I0403 15:29:08.316073 miner/worker.go:496] commit new work on block 64588 with 1 txs & 0 uncles. Took 1ms
I0403 15:37:48.961853 core/blockchain.go:1097] imported 1 blocks, 1 txs ( 0.021 Mg) in 25.001ms ( 0.840 Mg/s). #64588 [4ed21581.]
I0403 15:37:48.968853 miner/worker.go:496] commit new work on block 64589 with 4 txs & 0 uncles. Took 4.0002ms
I0403 15:39:40.364224 core/blockchain.go:1097] imported 1 blocks, 2 txs ( 0.043 Mg) in 27.001ms ( 1.608 Mg/s). #64589 [9a9f18b1.]
I0403 15:39:40.368225 miner/worker.go:496] commit new work on block 64590 with 2 txs & 0 uncles. Took 2.0002ms
I0403 15:39:40.619239 core/blockchain.go:1097] imported 1 blocks, 2 txs ( 0.043 Mg) in 17.001ms ( 2.554 Mg/s). #64589 [ae22d66a.]
I0403 15:39:40.622239 miner/worker.go:496] commit new work on block 64590 with 2 txs & 1 uncles. Took 1.0001ms
I0403 15:39:58.194244 core/blockchain.go:1097] imported 1 blocks, 2 txs ( 0.073 Mg) in 29.001ms ( 2.506 Mg/s). #64590 [dfbeca51.]
I0403 15:39:58.197244 miner/worker.go:496] commit new work on block 64591 with 1 txs & 0 uncles. Took 1ms
I0403 15:43:26.007130 core/blockchain.go:1097] imported 1 blocks, 1 txs ( 0.021 Mg) in 15.000ms ( 1.400 Mg/s). #64591 [b7266e0c.]
I0403 15:43:26.010131 miner/worker.go:496] commit new work on block 64592 with 1 txs & 0 uncles. Took 1ms
I0403 15:46:45.470539 core/blockchain.go:1097] imported 2 blocks, 3 txs ( 0.071 Mg) in 21.001ms ( 3.373 Mg/s). #64593 [d8acbc71. / 4953b496.]
I0403 15:46:45.473539 miner/worker.go:496] commit new work on block 64594 with 0 txs & 0 uncles. Took 1.0001ms
I0403 15:47:01.599462 core/blockchain.go:1097] imported 1 blocks, 0 txs ( 0.000 Mg) in 13.000ms ( 0.000 Mg/s). #64594 [43edba75.]
I0403 15:47:01.605462 miner/worker.go:496] commit new work on block 64595 with 2 txs & 0 uncles. Took 2.0001ms
I0403 15:48:05.522118 core/blockchain.go:1097] imported 1 blocks, 1 txs ( 0.021 Mg) in 14.000ms ( 1.500 Mg/s). #64595 [1356d06c.]
I0403 15:48:05.526118 miner/worker.go:496] commit new work on block 64596 with 1 txs & 0 uncles. Took 1ms
I0403 15:51:03.365290 core/blockchain.go:1097] imported 1 blocks, 1 txs ( 0.021 Mg) in 15.000ms ( 1.400 Mg/s). #64596 [8fdb85bb.]
I0403 15:51:03.370290 miner/worker.go:496] commit new work on block 64597 with 2 txs & 0 uncles. Took 2.0001ms
I0403 15:53:40.995306 core/blockchain.go:1097] imported 1 blocks, 2 txs ( 0.042 Mg) in 16.000ms ( 2.625 Mg/s). #64597 [93d60d94.]
I0403 15:53:40.999306 miner/worker.go:496] commit new work on block 64598 with 1 txs & 0 uncles. Took 2.0001ms
I0403 15:53:59.468362 core/blockchain.go:1097] imported 1 blocks, 1 txs ( 0.021 Mg) in 15.000ms ( 1.400 Mg/s). #64598 [39209c45.]
I0403 15:53:59.471363 miner/worker.go:496] commit new work on block 64599 with 1 txs & 0 uncles. Took 1.0001ms
I0403 15:55:08.680321 core/blockchain.go:1097] imported 2 blocks, 1 txs ( 0.021 Mg) in 15.000ms ( 1.400 Mg/s). #64600 [dc11b14a. / cbb7b7b3.]
I0403 15:55:08.684321 miner/worker.go:496] commit new work on block 64601 with 1 txs & 0 uncles. Took 2.0001ms
I0403 15:55:14.213638 core/blockchain.go:1097] imported 1 blocks, 1 txs ( 0.021 Mg) in 15.000ms ( 1.400 Mg/s). #64601 [c36db155.]
I0403 15:55:14.216638 miner/worker.go:496] commit new work on block 64602 with 0 txs & 0 uncles. Took 1ms
I0403 16:00:17.275972 miner/unconfirmed.go:83] ?? mined potential block #64602 [db3dbcbc.], waiting for 5 blocks to confirm
I0403 16:00:17.280972 miner/worker.go:496] commit new work on block 64603 with 3 txs & 0 uncles. Took 5.0003ms
I0403 16:02:44.398387 core/blockchain.go:1097] imported 3 blocks, 4 txs ( 0.084 Mg) in 33.001ms ( 2.545 Mg/s). #64605 [8286f5e5. / d83096d0.]
I0403 16:02:44.401387 miner/worker.go:496] commit new work on block 64606 with 0 txs & 0 uncles. Took 1ms
I0403 16:03:31.678091 core/blockchain.go:1097] imported 1 blocks, 1 txs ( 0.021 Mg) in 14.000ms ( 1.500 Mg/s). #64606 [e8d96db4.]
I0403 16:03:31.681091 miner/worker.go:496] commit new work on block 64607 with 1 txs & 0 uncles. Took 1.0001ms
I0403 16:05:01.175210 core/blockchain.go:1097] imported 2 blocks, 1 txs ( 0.021 Mg) in 21.001ms ( 1.000 Mg/s). #64608 [290bbaa8. / 263f381c.]
I0403 16:05:01.180210 miner/worker.go:496] commit new work on block 64609 with 1 txs & 0 uncles. Took 2.0001ms
I0403 16:05:01.182210 miner/unconfirmed.go:105] ?? mined block #64602 [db3dbcbc.] reached canonical chain |
|
|
|
|
Cool. I think something like that will be needed for this to catch on. With the bar set so high to get the DX running with just one BTC pair (110GB or more of free space, time/bandwidth to d/l the blockchains, reconfiguring of the wallets, etc.) people are going to at least want to know it is going to be worth the time and effort to do so first.
I do see the potential however with the of hacks and closures of traditional exchanges that go on (Bitfenix, Mintpal, Cryptsy, etc.)...not to mention the DDoS attacks that go on with Polo at the most critical high volume/high price movement moments when you really need your orders to execute.
Still, though, if the success of Blocknet relies on the failing of other exchanges it may never catch on. It will need to have the same level of ease of use. Having a quick easy way of checking the order book seems like low hanging fruit for a step in that direction.
|
|
|
|
|
Ok thanks for your inputs!
|
|
|
|
|
Wait I'm confused...so you DO have to run a node for each coin you want to trade? If so then that brings me back to my first question. Is there a site where someone can go just to check the DX's orderbook without running all the nodes? Like, does the blocknet team or a community member have a system that IS running a full DX with all the nodes (or at least the most popular ones like BTC, ETH, and XMR) and sending the info to a public website? (Even if it's just the orderbook in simple text form with no transaction history)
|
|
|
|
|
Ok cool so I don't have to run a BTC node to see the order book then? I will check it out later in that case.
|
|
|
|
|
So every single model of 470 4GB is guaranteed to have Samsung memory?
|
|
|
|
|
Just flash back to stock BIOS before you send it.
Can anyone tell me if there are any specific models of 470 4GB cards that are guaranteed to have Samsung mem? Thought I read somewhere that all MSI Armors that have an 8-pin PEG connector do and any recent Sapphire Nitro OCs. Not sure if that info is accurate though or if there are any other models. I'm hoping to maybe offload my Hawaii cards and get some 470s. Gonna have a 2nd rig soon with an 850W PSU and I'd love to be able to run 3 or 4 cards in it (I can't even run 3 Hawaiis without being at or above max output).
|
|
|
|
|
Claymore any plans to add UBQ to the list of devfee pools?
Also, anyone know dafuq is Musicoin? Came right out of nowhere with 170GH network hash rate...more than 3x what Expanse has.
EDIT: I guess I should add that I know about the -allcoins and -allpools flags but I'm just wondering cuz it would save time wasted switching DAG epochs.
|
|
|
|
|
So far I haven't found anything. Scoured the OP, block explorers, network stats, and github for this info. Problem seems to be getting worse as now I'm getting 2 and 3 blocks at a time more frequently than before, and occasionally 4 blocks before any get imported now. Seems if I do manage to mine any it will just be an orphan.
|
|
|
|
|
I might want to try the DX but before I go to the trouble of clearing 110GB to run a full Bitcoin node I'd like to look at the order books. Is there a link where I can check that out? I don't care if the info comes from a centralized server as long as it's accurate.
|
|
|
|
Where can I find a list of nodes and their addresses? I am trying to solo mine but many of the blocks come in 2 or 3 at a time so I think I need more peers so blocks get propogated faster. I0403 08:41:15.724321 core/blockchain.go:1097] imported 1 blocks, 0 txs ( 0.000 Mg) in 26.001ms ( 0.000 Mg/s). #64296 [cf276be0.]
I0403 08:41:15.729321 miner/worker.go:496] commit new work on block 64297 with 3 txs & 0 uncles. Took 3.0002ms
I0403 08:41:46.195064 core/blockchain.go:1097] imported 2 blocks, 3 txs ( 0.063 Mg) in 20.001ms ( 3.150 Mg/s). #64298 [968f945f. / 53cf260b.]
I0403 08:41:46.199064 miner/worker.go:496] commit new work on block 64299 with 2 txs & 0 uncles. Took 3.0002ms
I0403 08:45:36.199219 core/blockchain.go:1097] imported 2 blocks, 2 txs ( 0.043 Mg) in 27.001ms ( 1.608 Mg/s). #64300 [6bbae163. / f8fa4bc1.]
I0403 08:45:36.203220 miner/worker.go:496] commit new work on block 64301 with 6 txs & 0 uncles. Took 3.0002ms
I0403 08:46:09.707136 core/blockchain.go:1097] imported 1 blocks, 6 txs ( 0.126 Mg) in 22.001ms ( 5.727 Mg/s). #64301 [7849205f.]
I0403 08:46:09.710136 miner/worker.go:496] commit new work on block 64302 with 0 txs & 0 uncles. Took 2.0001ms
I0403 08:48:43.944958 core/blockchain.go:1097] imported 1 blocks, 0 txs ( 0.000 Mg) in 13.000ms ( 0.000 Mg/s). #64302 [096d98ce.]
I0403 08:48:43.947958 miner/worker.go:496] commit new work on block 64303 with 1 txs & 0 uncles. Took 2.0001ms
I0403 08:48:43.993961 core/blockchain.go:1097] imported 1 blocks, 1 txs ( 0.021 Mg) in 15.000ms ( 1.400 Mg/s). #64303 [2c06fff5.]
I0403 08:48:43.995961 miner/worker.go:496] commit new work on block 64304 with 0 txs & 0 uncles. Took 1ms
I0403 08:53:28.313223 core/blockchain.go:1097] imported 1 blocks, 0 txs ( 0.000 Mg) in 15.000ms ( 0.000 Mg/s). #64304 [c25c57e5.]
I0403 08:53:28.319223 miner/worker.go:496] commit new work on block 64305 with 6 txs & 0 uncles. Took 4.0002ms
I0403 08:53:28.426229 core/blockchain.go:1097] imported 3 blocks, 5 txs ( 0.105 Mg) in 22.001ms ( 4.772 Mg/s). #64307 [6f10889a. / a228e5c0.]
I0403 08:53:28.429229 miner/worker.go:496] commit new work on block 64308 with 1 txs & 0 uncles. Took 1.0001ms
I0403 08:53:33.894542 core/blockchain.go:1097] imported 1 blocks, 3 txs ( 0.063 Mg) in 28.001ms ( 2.250 Mg/s). #64308 [dc5ee1fc.]
I0403 08:53:33.897542 miner/worker.go:496] commit new work on block 64309 with 0 txs & 0 uncles. Took 1.0001ms
I0403 08:54:00.774079 core/blockchain.go:1097] imported 1 blocks, 0 txs ( 0.000 Mg) in 14.000ms ( 0.000 Mg/s). #64309 [8f271b4a.]
I0403 08:54:00.779080 miner/worker.go:496] commit new work on block 64310 with 1 txs & 0 uncles. Took 4.0002ms
I0403 08:55:04.747739 core/blockchain.go:1097] imported 2 blocks, 1 txs ( 0.021 Mg) in 20.001ms ( 1.050 Mg/s). #64311 [0c7b5105. / 5afdd97c.]
I0403 08:55:04.749739 miner/worker.go:496] commit new work on block 64312 with 1 txs & 0 uncles. Took 1ms |
|
|
|
If it's the tightest one that will run stable at that speed, yes. For Polaris BIOS modding 101 try this forum thread: http://www.overclock.net/t/1604567/polaris-bios-editing-rx480-rx470-rx460It's probably better to leave this thread for nerdralph, Wolf0, and the others for their technical discussions. I'm going to take my own advice too and revert to lurking now  EDIT: Ahhh I'm not well-versed in Polaris BIOS modding but if it's anything like Hawaii, the 2000 field applies to mem clocks between 1875 and 2000. You would want to apply to the 2125 field (if there even is one) for clocks between 2000 and 2125. yes the 2000 field (40 0D 03) applies to any clocks above 1751. Anyhow all that info can be found in the link. |
|
|
|
total newb question. when i first started playing with straps the common standard mod was to take the 1500 strap and apply it to 1625, 1750, and 2000. when you take and edit the 1625 strap, do you apply it to only 1625, to 1625, 1750, and 2000, or do you apply it to all of them, 1500, 1625, 1750, and 2000?
That should depend on what mem clock you can achieve. You basically want the tightest timings that will still work at the highest mem clock. If your mem can do 2100 and the 1500 strap will only let you get to 1900...well you might want to use the 1625 strap instead. As always trial and error and performance/stability testing will find out what works best for your hardware. Every card is different. You only really need to apply a strap to the one frequency you will actually be using. Applying it to multiple ones will just give you some lower clocks to fall back on if a higher clock fails. |
|
|
|
For the lazy fools out there, I whipped up a cgi version of my strap mod utility. http://doreymills.ca/cgi-bin/strapmod?555000000000000022CC1C00AD515A3EC0570E142D4A64080048C700030114207A8900A003000000150E2A3186272E16
This tool is working great for me so far on 2 different gpus (one samsung and one hynix). Will this most likely be stable for most gpu mem chips (new non ref cards with different hynix/samsung chips?) Nice! I will try that out and report back. Just waiting for some replacement fans and thermal pads to arrive first. VRMs are getting too hot on the BFR card in its current state. EDIT: Just tried inputting Stilt's AFR and BBBG timings for shits and giggles and it did spit out something different. Does this mean it actually made them better? The tool is for Polaris straps only. I'd have to modify it to support R9 cards. Heh I thought so but thought I'd try it anyway just to see what happened. (btw nothing happened..same performance and stability as Stilt's original strap) It's probably not worth spending time on R9 cards at this point. I'm sure most people have switched to RX cards by now for the efficiency...and anyway everything will probably be HBM before too long after Vega and Volta become the norm. |
|
|
|
For the lazy fools out there, I whipped up a cgi version of my strap mod utility. http://doreymills.ca/cgi-bin/strapmod?555000000000000022CC1C00AD515A3EC0570E142D4A64080048C700030114207A8900A003000000150E2A3186272E16
This tool is working great for me so far on 2 different gpus (one samsung and one hynix). Will this most likely be stable for most gpu mem chips (new non ref cards with different hynix/samsung chips?) Nice! I will try that out and report back. Just waiting for some replacement fans and thermal pads to arrive first. VRMs are getting too hot on the BFR card in its current state. EDIT: Just tried inputting Stilt's AFR and BBBG timings for shits and giggles and it did spit out something different. Does this mean it actually made them better? Old, new RRD: 0 , 5
Old, new ACTRD: 12 , 0x10
Old, new FAW: B , 0
Old, new 32AW: 0 , 0
77713320000000000839472A50550C0B242045040046C40022BB1C005C0B14204A8900A00000012 0120C211E51192613
77713320000000000839472A50555C0B242045040046C40022B00C005C0B14204A8900A00000012 0100C211E51192613 Old, new RRD: 0 , 5
Old, new ACTRD: 11 , 0x10
Old, new FAW: A , 0
Old, new 32AW: 64 , 0
77713320000000004ABD472A60550F0F231D87030046C40022AA1C085C0B14204A8900A00000012 0110D20234A1D2411
77713320000000004ABD472A60555F0F231D87030046C40022A00C005C0B14204A8900A00000012 0100D20234A1D2411 I guess I'll find out soon enough! EDIT2: Yeah agree with cryptominer420's post below. If I switch back to ETH or ZEC and this is gonna make the magical internet moneys flow in faster then I'd be all for sending some % of the extra income back to the people making it possible. I'm just not sure what amount should go to who. Perhaps you guys could get together and agree upon a split, and make a smart contract donation address that splits the donations accordingly. |
|
|
|
|
Show Posts
