 Show Posts
|
|
Pages: [1] 2 3 4 5 6 7 »
|
Source and released version does not match? |
|
|
|
If started with Vegas miner does not create cached compiled kernels. Each start it compiles kernels again. Only zero-sized file with name '687F' is created. Start of the log looks like this. GPU0: 687F:C3 [gfx901] [8176 MB][Intensity 110.0][W: 8][T: 2][K: 1][BUS: 19]
GPU1: 687F:C1 [gfx901] [8176 MB][Intensity 110.0][W: 8][T: 2][K: 1][BUS: 3]
GPU2: 687F:C1 [gfx901] [8176 MB][Intensity 110.0][W: 8][T: 2][K: 1][BUS: 10]
GPU3: 687F:C3 [gfx901] [8176 MB][Intensity 110.0][W: 8][T: 2][K: 1][BUS: 7]
GPU4: 687F:C1 [gfx901] [8176 MB][Intensity 110.0][W: 8][T: 2][K: 1][BUS: 16]
GPU5: 687F:C1 [gfx901] [8176 MB][Intensity 110.0][W: 8][T: 2][K: 1][BUS: 13]
---------------------------------------------------------
SRBMiner Cryptonight AMD GPU miner 1.5.3
DevFee 1 minute every 2 hours (~ 0.85%)
Press 's' to get some stats
Press 'h' to get some hashrate
Give it a few minutes to reach maximum hashrate
---------------------------------------------------------
Total pools: 1
Please wait...
Cryptonight ArtoCash mode enabled
[2018-05-13 16:14:07] Heating up system, please wait...
[2018-05-13 16:14:07] Compiling kernel for DEVICE BUS ID 19 ...
[2018-05-13 16:14:21] Compiling kernel for DEVICE BUS ID 19 ...
|
|
|
|
|
Pools show different difficulty of top block. Network forked?
|
|
|
|
Attention miners. An unexpected Hardfork occurred on this pool due to updated software being used. https://pool.ombre.io/As we fix the issues we encourage you to mine using the other available pools, as this new chain will not be supported or endorsed by Ombre. We apologize for any inconveniences you maybe have incurred due to this Hardfork. Current git syncs to pool.ombre.io. |
|
|
|
How about Stellite, Turtle, Bitcoal , Dero, Edollar and a dozen other tradable CN coins? Most of them just started and are more profitable to mine. Each week there's a new one coming out, keeping the original cryptonight algorithm. I hope it's gonna be like you say, otherwise all small miners with will get smashed like bugs.
Оther coins have <60Mh combined. TRTL, EDL, DERO probably fork too ( https://medium.com/@turtlecoin/take-your-baikal-and-shove-it-up-your-asic-b05c96187790, https://twitter.com/EdollarCash/status/973233457902989312, https://bitcointalk.org/index.php?topic=2525508.msg32350727#msg32350727). Bitcoal has only ~0.3Mh. I think most cryptonight coins with active developers will follow XMR (if fork succeed). |
|
|
|
Why does anyone talk about Monero only ? There are tens of cryptonight coins, much more profitable than monero, mineable with these Asics. Yes, Monero will fork, but no one forbids people to mine other coins and buy monero afterwards. And yes, other coins will be destroyed by so many powerful miners flooding the market, and most of those miners will ROI (not talking about those who paid the ridiculous price for the first batch). It will take time for these miners to become obsolete, as it's gonna take a lot of time for other CN coins to switch algo. Again, the planet doesn't revolve around Monero, wake up people.
But i still find it funny how all companies released a cryptonight miner at the same time. As if it was a single company under different names, controlling the miner's market.
XMR have 950Mh (700 Mh of which is estimated to be asics), ETN have 320Mh, GFT+IPBC+SUMO have <150Mh combined, other coins have <60Mh combined. If XMR and ETN forks then first batch of bitmain will have estimated payback period around 8 months at best. If GFT, IPBS, SUMO forks it will be 2 years at best. |
|
|
|
https://sum.dreampool.info/ forked? Wallet sychronization is stuck @ block 100036, even re-syncing using the provided (in op) .conf file and another daemon (stock forknote) - does not help. forknoted+bitsum.conf looks fine to me, http://sum.dreampool.info seems to be on longest good chain. bitsumd (compiled from current git) does not sync past 100036, but forknoted+bitsum.conf syncs fine to height 100564. According to bitsum.conf at height 100000 zawy difficulty control algo was implemented. Although git for bitsumd contains commit which implement zawy difficulty control algo it looks like compiled bitsumd works differently from forknoted+bitsum.conf. |
|
|
|
how to contact the dev ?
i was mining on dcy.crypto-coins.club, they say was sent my payment
Already answered. Some pools (including 151.80.136.118 = dcy.crypto-coins.club) did not update to version 2.1.2 and was mining fork. 2.1.2 wallet synchronizes with dinastycoin.com/democats.org chain. cryptopia.co.nz wallet is in maintenance mode and updating to 2.1.2. |
|
|
|
We changed some parameters on the official dinastycoin pool (poolmining1.dinastycoin.com)
payment time now each 1 hour (before 2 hours)
maximum transaction amount 2000DCY (before 1000DCY)
pool fee 0.8% (before 0.5%)
Maximum miners paid any time 150 (before 50)
we will see in the next days if all will be good with transactions to increase again the maximum values that will be paid to 5000DCY
good mining
Could you also fix vardiff behaviour? Current one often gives stable share difficulty ~3000000 (too big) for vega rigs with 11.5Kh/s hashrate. |
|
|
|
|
alpha.ultranote.org rejects all shares from my rigs with message 'Over Limit'.
Could devs explain?
|
|
|
|
Somewhere, there must be a pool with almost 50% or more of the hashrate which finds the majority of the blocks and which runs those attacks.
32Mh/s on http://prohash.net/etn right now. 1 connected miner. |
|
|
|
Compiled it myself from the src for Ubuntu 16.04, now it works. So your Linux download version won´t definitely run with Ubuntu 16.04
You just need to provide one good seed node. |
|
|
|
Same here. Is there a delay or something is wrong? Pool shows transfrers was made. Local wallet shows no incoming transfers even in blocks with age>500. Probably something is wrong. |
|
|
|
Preach it!
Meh, don't like long prayers. |
|
|
|
You are asking to much.  This is obviously not only for me but for the community as well. Major part of community here is 'endless horde of noobs who done nothing but want profits'. Sorry I don't give a f!!k about such community and consider expression 'for the community' a swearing.  |
|
|
|
How would you go about optimizing the straps?
You are asking to much. Don't have gtx's now to test if it work. |
|
|
|
I may have found a way to sign the rom.
But I can't find the location of the straps + there is the problem of fixing the checksum.
I think you need to find and parse three tables in case of nvidia: 'memory type' table which lists memory types supported by bios, 'timings' table which lists all timings without memory clocks and memory type and 'map' table which maps memory clocks+memory type to 'timing' id. 'timings' table starts at offset 0x2e40a from bios start, 'timings' are '0c1910048902312411040588ec180022328061d3e270b2a60b86000200bc34000039020a06000000a65514040a01f06c1333330300000000000000000a00008000000000'
'152d1c078cc2312411060788ac180022328061d3e270b2a60b86000100bc34000039050806000000a85514068a01f06c1333330300000000000000000a00008000000000'
'388a4c1293c2b42000071288ec280022328082d5e270b2a60f86000200bc340000390d1006000000a0441a90ca0491901444440300000000000000000a00008000000000'
'42a55a1595c2e52000081588ec300022320083d5e270b2a60f86000200bc340000390f1206000000a2441e93cf0491901444440300000000000000000a00008000000000'
'4ec16a1997c2162900091988ec380022328083d5e270b2a60f86000200bc34000039121506000000a5442496920591901444440300000000000000000a00008000000000'
'58dc781c99822729000a1c88ec400023320084d5e270b2a60f86000200bc34000039141706000000a7442899540691901444440300000000000000000a00008000000000'
'122d16078802222411040788aa180022328061d3d270b2a60b86000100bc34000039020a06000000444414054a01f06c1333330300000000000000000a00008000000000'
'338a401391c2e42800071488aa280022328082d5d270b2a60f86000100bc34000039050a060000004444140d4a0391901444440300000000000000000a00008000000000'
'3da54c1794c2252900081888aa300022320083d5d270b2a60f86000100bc34000039060a060000004444140fca0391901444440300000000000000000a00008000000000'
'47c1581b96c2662900091c88aa380022328083d5d270b2a60f86000100bc34000039070a06000000444414128a0491901444440300000000000000000a00008000000000'
'50dc641e97828729000b2088aa400023320084d5d270b2a60f86000100bc34000039080a06000000444414140a0591901444440300000000000000000a00008000000000'
'0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000a00008000000000'
'0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000a00008000000000'
'0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000a00008000000000'
'0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000a00008000000000'
'0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000a00008000000000'
'0c1910048902312411040588ec180022328061d3d270b2a60b86000200bc34000039020a06000000a65514040a01f06c1333330300000000000000000a00008000000000'
Clock ranges (not sure which multiplier should be used) used are: 0-540, 541-1299, 1300-2800, 2801-3300, 3301-3700, 3701-4500. Timing ids for different memoty types are (ordered by clock): type0 - 0,1,2,3,4,5, type1 - 16,6,7,8,9,10, type2/3 - 0,1,1,2,3,none. Type 0 is Samsung GDDR5, type 1,2,3 is Micron GDDR5. |
|
|
|
|
