So, what OS are you using? I'm trying to find a pattern here because I'm hearing other ETH miners have the same issue.
Windows 7 |
|
|
|
Yes I can see the memtweak is off, thanks. However, I'm very surprised about your 1080 being slower than my 1070Ti on epoch 383. I'm getting 24.5Mh/s with PL 90W, CORE 0, MEM +1000. DAG generation time is ~8.8s, without memory tweaks
Because u are compareing two different memory architectures. GDDR5x isnt GDDR5 and vice versa. My results are slower because I used default clocks. I dont want burn my house on this Asus Dragon  When I put MEM + 1000 will get generation time 10s and hashrate about 26.5Mh/s - Epoch 383. But still I will not get results like 33Mh/s with enabled mem tweak. You can nicelly see it on Nicehash graphs when someone order ETC hashrate how it all drops since it have different DAG size like ETH currently. |
|
|
|
Hmm, very curious indeed. I did a benchmark with my 1070Ti with --mt 5 on Linux and didn't notice a hashrate decrease for 383/384 epoch threshold. Could you try benchmarking without --mt?
UPD: What OS are you using? Win 7 by any chance?
How I typed from start. Mem tweak doesnt work anymore. Now you can see its due DAG size - specified EPOCH number. Another fact is Mem tweak just works for GDDR5x memory. Your 1070Ti is just GDDR5. But its there small hashrate drop but not significant like with mem tweak switch. Also look on that generating times for DAG which proove mem tweak is off. (8 secs with mem tweak and 12 secs without him) 20201121 13:45:23 WARN: BENCHMARK MODE (ethash)
20201121 13:45:23 WARN: EPOCH 383
20201121 13:45:23 WARN: GPU #0(000100): ASUS GeForce GTX 1080, intensity set to 20
20201121 13:45:26 GPU #0: generating DAG 3.99 GB for epoch 383 ...
20201121 13:45:38 GPU #0: DAG generated [time: 12377 ms], memory left: 3.58 GB
20201121 13:45:55 GPU #0: using kernel #2
20201121 13:45:56 Total: 21.47 MH/s
20201121 13:45:58 Total: 21.48 MH/s
20201121 13:46:40 WARN: BENCHMARK MODE (ethash)
20201121 13:46:40 WARN: EPOCH 384
20201121 13:46:40 WARN: GPU #0(000100): ASUS GeForce GTX 1080, intensity set to 20
20201121 13:46:43 GPU #0: generating DAG 4.00 GB for epoch 384 ...
20201121 13:46:55 GPU #0: DAG generated [time: 12389 ms], memory left: 3.57 GB
20201121 13:47:13 GPU #0: using kernel #5
20201121 13:47:14 Total: 20.87 MH/s
20201121 13:47:16 Total: 20.88 MH/s
|
|
|
|
I reckon this info is only relevant for 4GB cards where the GPU can't hold the entire DAG. 1080Tis have plenty of memory, so it must be something different. You can do some experiments with "t-rex -a ethash --benchmark --benchmark-epoch NNN" and see how it behaves for different epochs
So christmas gift will get miners - looks like mem tweak works just to 3.99GB DAG size: 20201121 11:30:24 WARN: BENCHMARK MODE (ethash)
20201121 11:30:24 WARN: EPOCH 383
20201121 11:31:10 WARN: GPU #0(000100): ASUS GeForce GTX 1080, intensity set to 20, mtweak 5
20201121 11:31:13 GPU #0: generating DAG 3.99 GB for epoch 383 ...
20201121 11:31:20 GPU #0: DAG generated [time: 8008 ms], memory left: 3.28 GB
20201121 11:31:37 GPU #0: using kernel #2
20201121 11:31:38 Total: 33.39 MH/s
20201121 11:31:40 Total: 33.39 MH/s
20201121 11:32:32 WARN: BENCHMARK MODE (ethash)
20201121 11:32:32 WARN: EPOCH 384
20201121 11:33:02 WARN: GPU #0(000100): ASUS GeForce GTX 1080, intensity set to 20, mtweak 5
20201121 11:33:05 GPU #0: generating DAG 4.00 GB for epoch 384 ...
20201121 11:33:13 GPU #0: DAG generated [time: 7936 ms], memory left: 3.27 GB
20201121 11:33:30 GPU #0: using kernel #5
20201121 11:33:31 Total: 20.89 MH/s
20201121 11:33:33 Total: 20.88 MH/s
20201121 11:34:52 WARN: BENCHMARK MODE (ethash)
20201121 11:34:52 WARN: EPOCH 385
20201121 11:35:22 WARN: GPU #0(000100): ASUS GeForce GTX 1080, intensity set to 20, mtweak 5
20201121 11:35:25 GPU #0: generating DAG 4.01 GB for epoch 385 ...
20201121 11:35:33 GPU #0: DAG generated [time: 7950 ms], memory left: 3.27 GB
20201121 11:35:51 GPU #0: using kernel #5
20201121 11:35:54 Total: 20.72 MH/s
20201121 11:35:56 Total: 20.72 MH/s
20201121 11:37:05 WARN: BENCHMARK MODE (ethash)
20201121 11:37:05 WARN: EPOCH 390
20201121 11:37:36 WARN: GPU #0(000100): ASUS GeForce GTX 1080, intensity set to 20, mtweak 5
20201121 11:37:38 GPU #0: generating DAG 4.05 GB for epoch 390 ...
20201121 11:37:46 GPU #0: DAG generated [time: 8030 ms], memory left: 3.22 GB
20201121 11:38:04 GPU #0: using kernel #5
20201121 11:38:05 Total: 20.66 MH/s
20201121 11:38:07 Total: 20.66 MH/s
20201121 11:38:58 WARN: BENCHMARK MODE (ethash)
20201121 11:38:58 WARN: EPOCH 395
20201121 11:39:29 WARN: GPU #0(000100): ASUS GeForce GTX 1080, intensity set to 20, mtweak 5
20201121 11:39:32 GPU #0: generating DAG 4.09 GB for epoch 395 ...
20201121 11:39:39 GPU #0: DAG generated [time: 8111 ms], memory left: 3.24 GB
20201121 11:39:57 GPU #0: using kernel #5
20201121 11:39:58 Total: 20.40 MH/s
20201121 11:40:00 Total: 20.41 MH/s |
|
|
|
Wow, that difference in hashrate can't be explained by a not functioning memory tweak. "--mt" is only supposed to boost your hashrate by a couple of MH/s per card, there's definitely something else going on. I've seen similar reports elsewhere it's a common problem regardless of what miner is used. I'm not aware of a solution for this issue, unfortunately.
I think its this (Mem tweak was designed for 4GB?) - yeah page aimed on RX 580 but similiar behaviour Im seeing now on nVidia: https://2miners.com/blog/how-to-mine-ethereum-and-ethereum-classic-on-4gb-gpus/ What u think? |
|
|
|
Memtweak doesnt work on ETC anymore with 1080Ti?
It does Are you sure? It causing different epoch. Also on ETC GPU clock is 2100MHz and MCU 40% usage. On ETH GPU clock is 1500MHz MCU 100% usage. Totaly real usage during mining. ETC-mtweak 120201121 07:32:17 Mining at ethash.mine.zergpool.com:9999 20201121 07:32:17 GPU #1: EVGA GTX 1080 Ti - 18.20 MH/s, [T:49C, P:144W, F:55%, E:128kH/W], 2/2 R:0% 20201121 07:32:17 GPU #3: EVGA GTX 1080 Ti - 18.33 MH/s, [T:51C, P:146W, F:55%, E:127kH/W], 2/2 R:0% 20201121 07:32:17 Shares/min: 4.048 (Avr. 1.524), Avr.Power: 286W, Avr.Efficiency: 128kH/W 20201121 07:32:17 Uptime: 2 mins 37 secs | Algo: ethash | T-Rex v0.18.11 ETH-mtweak 120201121 07:33:52 Mining at ethash.mine.zergpool.com:9999 20201121 07:33:52 GPU #1: EVGA GTX 1080 Ti - 42.85 MH/s, [T:46C, P:146W, F:54%, E:330kH/W], 1/1 R:0% 20201121 07:33:52 GPU #3: EVGA GTX 1080 Ti - 42.14 MH/s, [T:47C, P:143W, F:55%, E:329kH/W], 3/3 R:0% 20201121 07:33:52 Shares/min: 23.706 (Avr. 5.614), Avr.Power: 258W, Avr.Efficiency: 329kH/W 20201121 07:33:52 Uptime: 42 secs | Algo: ethash | T-Rex v0.18.11 |
|
|
|
|
Memtweak doesnt work on ETC anymore with 1080Ti?
|
|
|
|
It depends on the liquidity chart. It's possible that Latoken has more premium coins. It depends on when you deposited those coins on Latoken as well, how premium were they? If you purchased reserve it depends on who you bought it from, how premium/fast did those coins convert? The only difference between Latoken and the wallet is the exchange does what's called "liquidity mixing" where for a smoother trading experience a user who buys liquid will have a share in the total liquidity pool for the users at that moment who are also liquid. This prevents a user from accidentally buying sub-premium liquidity because they can't see a users liquidity distribution chart. The reserve however is very specific and it's somewhat random the reserve quality you buy from a reserve seller. Although I suspect most of the reserve is premium because of people who deposited later with a better set of liquid coins. So please I want you to take a look at the send tab and then activate coin select. Then look at all the inputs you can possibly spend. You will notice each input has a liquidity chart. If you click on that chart you can see that each chart is different and the amount of coins distributed is different for each index. You can also see these charts on the block explorer too.  So this is PEG which lock all my funds? Again yours screen is from some testnet or different time of block? So if now others will vote for inflate (I'll round it out every 200 blocks to 4 hours)... Need down 100 indexes to make some coins avaiable. If everyone will contantly vote inflate and wanna get 711 index PEG. 100 indexes x 4 hours = 400 hours. 400/24= 16,6 days of voting? Others agree with these rules? At index 1 its about 100 BAY for liquidity. With current index 811 its 0 BAY  Btw Latoken exchange have already closed trades for BAY already for 4 days. Even support couldnt credit me monthly locked reserved BAY. Lets imagine when will comes some investor with 10 BTC. He will be not even able buy since actual trading situation and if yes he will be not even transfer them to his personal wallet and if yes it will be automatically locked. |
|
|
|
The pegging works by balancing the wallet amounts based on present liquidity and votes, so depending on what the people want and the liquidity of Bitbay forces the coins in reserve to keep price stable. The reason you cannot see the trading on Latoken is because Bitbay is presently under maintenance, don't worry trading will resume soon.
I thought PEG is for whole network. Then why im my personal wallet I see BAY(R) 1059 and BAY(L) just 0.53? When I compare it with Latoken exchange I had almost same reserved BAY value 1016 and for liquidity 10 BAY. That means Latoken exchange have different rules or wallet? |
|
|
|
Hello, can I ask how that PEG works? Latoken/exchanges have different wallet like others people? At Latoken had 1016 BAY Reserved fund I got after some time transfered 10 BAY to liquidity fund. Here is screen from Latoken:  Now lets look to my personal wallet.  Reserved BAY 1059 and avaiable for liquidity just 0.53 BAY? Anyone else is able trade at Latoken exchange? Im getting only empty page when I search for BAY. |
|
|
|
Updated QT wallet to v3 and it stuck on block 2459220, 38 hours ago. Synced from scratch. How fix it?
This may happen as not 100% nodes were updated before hard fork. So you unluckily stuck into abandoned chain looks like. Simplest and quick way: 1. stop qt wallet 2. backup wallet.dat somewere 3. remove all files in datafolder except wallet.dat 4. place bootstrap.dat in datafolder 5. start qt wallet bootstrap file is updated up to Jan 23 - bypassing fork point, so you should be safe after resync. it may take 2-3 hours to load from bootstrap which is much faster then ordinary resync. Usually new exchanges dont want use bootstrap file and want sync from scratch like me. But got same errors like @marecek666 had. |
|
|
|
|
Updated QT wallet to v3 and it stuck on block 2459220, 38 hours ago. Synced from scratch. How fix it?
|
|
|
|
What do you mean by adding BitBay? I know it's a European exchange with several altcoins but there's no CLAM pair.
It have nothing with Bitbay coin. Compare logos of that products. |
|
|
|
Guys, you should update the wallets to the latest version. This is a compulsory update, otherwise you will not be able to use your coins. Also the collateral to make MN is 10000 coins now. Follow the steps: 1. Copy paste the wallet.dat file somewhere safe and then delete the entire Harvest folder. 2. Install the new wallet from the below link for wallets: https://github.com/HarvestMasternodecoin/HarvestCore/releases3. You might see warning messages, click OK and proceed, once the wallet syncs, you can close wallet and then replace the wallet.dat with the old backed up wallet.dat file 4. Restart wallet to see your previous balance. 5. There will be some lost coins as we rolled back the chain to 15th June to get people back on single blockchain instead of the multiple blockchains they were on. Source Code : https://github.com/HarvestMasternodecoin/HarvestCoreOne Click MN Setup : https://github.com/HarvestMasternodecoin/OneClick_MN_Setup[/size] How can transfer coins to new wallet for new collateral cause whole network stuck. Have 24 connections and 7 hours without new block... |
|
|
|
fan control not working 2.3.1nh for Z11 Could you check the latest built again, I'm sure I'm not the only one with a problem. Fan control does not work. It works in automatic mode only. It cannot be set manually. I understand. I will look into this. It is specific to the nicehash version and is the result of an unexpected change from bitmain. They have removed fan control from the user in their latest releases. I will see if o can add that back in. -j Is that fan issue fixed? |
|
|
|
|
@chipless
Are you able make firmware with lower clocks? Is there hidden page minerAdvanced.cgi where you can choose turbo or balance mode but they doesnt do anything. Are you able add here for example clocks? 750MHz 700MHz 650MHz and 600MHz? Of course with volts mods also so miner can choose some value and finally I can replace fans.
Thanks.
|
|
|
|
|
Show Posts
