 Show Posts
|
|
Pages: [1] 2 3 »
|
|
Das klingt interessant. Das heißt, wenn man die Coins unmittelbar nach BTC und wieder retour tauscht, würde trotz dem Mining Steuerfreiheit auf den restlichen ETH-Kursgewinn (Behaltedauer mind. 12M) herrschen?
Gibt es in Wien einen empfehlenswerten Steuerberater?
|
|
|
|
|
ich meinte, dass die cryptos (zb eth) zuerst gemined wurden, und nachher auf BTC getauscht wurden. Gilt für diese BTCs nach dem Tausch dann auch das eine Jahr, oder sind diese steuerlich "anders"?
|
|
|
|
|
gilt das mit dem 1J auch, wenn die cryptos gemined und dann erst auf BTC getauscht wurden?
|
|
|
|
|
Gibt es hierzu Neuigkeiten?
|
|
|
|
1. I use same code for all my recent miners: ZEC, ETH, CN. So this problem is not related to this miner only.
2. This problem is related to buggy drivers. Miner sets fan speed but drivers sets some different speed. Then miner reads current fan speed and drivers report wrong speed. Therefore miner calculates wrong new speed, drivers set it wrong again, it increases error in speeds even more and so on.
As far as I remember, I saw at least two reports that this problem is solved in some drivers version. Need to find these messages. Also I will check it on latest drivers, if AMD still has this problem may be I can find some new workaround.
You can try to set static fan speed, for example, "-tt -50". And see what speed was set.
1. I didn't have tested all of them, but I have the same problem with your EthMiner. 2. In the log it's showing GPU0 and GPU6 and the stats are showing GPU0 und GPU1. I've read about problems with the enumeration of the devices in the faq. Do I need to set the value for the 1st and 7th GPU (-tt 75,00,00,00,00,00,70) or only for the 1st and 2nd (-tt 75,70) and you're mapping it internally from 2 to 6? I've tried to set -tt -50 but there was no effect (it's cooler because I've started it with -li 1): GPU0 t=66C fan=46%, GPU1 t=65C fan=27% I'm using the 16.12.2.2-Jan3 driver. I've also tested sgminer with "--temp-target 77 --auto-fan" with the same machine,card & driver and there it's working fine after some "learning"-time: GPU 0: 74.0C 2449RPM GPU 1: 74.0C 1308RPM |
|
|
|
Hello claymore, something seems to be wrong with the -tt parameter. I'm using a 380 and a 470 in the same machine. I'm trying to set fan-speeds with -tt 77,70 to avoid the 100% fan-bug of the 470, but it's not working. I've tried: NsGpuCNMiner.exe -li 1 -a 2 -tt 75 NsGpuCNMiner.exe -li 1 -a 2 -tt 75,70 but the temperatures of the second card is always too high. It seems that you're trying to set it, but it doesn't work: 10:46:39:850 360 GPU0 t=75C fan=55%, GPU1 t=78C fan=17%
10:46:40:707 3fe4 GPU 1: HashCnt = 864, time = 2034 ms, hashrate = 424 h/s
10:46:40:960 5d58 GPU 0: HashCnt = 1024, time = 2162 ms, hashrate = 473 h/s
10:46:41:166 5930 GPU 0 temp = 75, old fan speed = 55, new fan speed = 68
10:46:41:175 5930 GPU 6 temp = 78, old fan speed = 17, new fan speed = 25
10:46:42:920 3c74 GPU 1: HashCnt = 864, time = 2158 ms, hashrate = 400 h/s
10:46:43:143 32f4 GPU 0: HashCnt = 1024, time = 2122 ms, hashrate = 482 h/s
10:46:44:190 5930 GPU 0 temp = 75, old fan speed = 55, new fan speed = 68
10:46:44:223 5930 GPU 6 temp = 77, old fan speed = 17, new fan speed = 25
10:46:44:870 360 GPU0 t=75C fan=55%, GPU1 t=78C fan=17%
10:46:47:235 5930 GPU 0 temp = 75, old fan speed = 55, new fan speed = 68
10:46:47:312 5930 GPU 6 temp = 78, old fan speed = 17, new fan speed = 25
|
|
|
|
Yeah alot of us have that problem with the lowdifficultyshare. It gets fixed for me after 15 min when the miner reconnect with the pool (dwarfpool). Not sure if a pool issue or a miner issue. Dwarf is doing some changes with their site, maybe their ports too.
okay, I'm seeing some of these lowdifficultyshares also with 9.6, but with 9.7 there are a lot more - can you confirm that 9.6 is doing it's work better? |
|
|
|
9.7 isn't working very well - i'm getting a lot of "low difficulty share"s and rejects with very high response times? 2 completely different machines: 2x 380 and 2x 470 everything is working fine with 9.6 ... 15:01:15:083 db8 GPU 1: HashCnt = 1024, time = 1831 ms, hashrate = 559 h/s
15:01:15:099 db8 Round
15:01:16:647 23bc GPU 0: HashCnt = 1024, time = 1887 ms, hashrate = 542 h/s
15:01:16:647 23bc Round
15:01:16:787 2b20 got 78 bytes
15:01:16:787 2b20 buf: {"id":4,"jsonrpc":"2.0","error":{"code":-1,"message":"Low difficulty share"}}
15:01:16:787 2b20 parse packet: 76
15:01:16:787 2b20 Share rejected (2047 ms)!
15:01:16:787 2b20 {"id":4,"jsonrpc":"2.0","error":{"code":-1,"message":"Lowdifficultyshare"}}
15:01:16:787 2b20 new buf size: 0
15:01:16:881 2b20 got 78 bytes
15:01:16:881 2b20 buf: {"id":4,"jsonrpc":"2.0","error":{"code":-1,"message":"Low difficulty share"}}
15:01:16:881 2b20 parse packet: 76
15:01:16:881 2b20 Share rejected (2141 ms)!
15:01:16:881 2b20 {"id":4,"jsonrpc":"2.0","error":{"code":-1,"message":"Lowdifficultyshare"}}
01:45:23:961 6b14 GPU 0: HashCnt = 1024, time = 1849 ms, hashrate = 553 h/s
01:45:23:987 6b14 Round
01:45:24:143 16a4 GPU 1: HashCnt = 864, time = 1615 ms, hashrate = 534 h/s
01:45:24:165 16a4 Round
01:45:25:806 6144 GPU 1: HashCnt = 864, time = 1617 ms, hashrate = 534 h/s
01:45:25:823 6144 Round
01:45:25:875 4104 GPU 0: HashCnt = 1024, time = 1860 ms, hashrate = 550 h/s
01:45:25:894 4104 Round
01:45:26:593 417c got 78 bytes
01:45:26:601 417c buf: {"id":4,"jsonrpc":"2.0","error":{"code":-1,"message":"Low difficulty share"}}
01:45:26:609 417c parse packet: 76
01:45:26:618 417c Share rejected (4102 ms)!
01:45:26:628 417c {"id":4,"jsonrpc":"2.0","error":{"code":-1,"message":"Lowdifficultyshare"}}
01:45:26:638 417c new buf size: 0
01:45:26:906 417c got 78 bytes
01:45:26:930 417c buf: {"id":4,"jsonrpc":"2.0","error":{"code":-1,"message":"Low difficulty share"}}
01:45:26:938 417c parse packet: 76
01:45:26:948 417c Share rejected (4430 ms)!
01:45:26:959 417c {"id":4,"jsonrpc":"2.0","error":{"code":-1,"message":"Lowdifficultyshare"}}
01:45:26:968 417c new buf size: 0
01:45:27:694 16a4 GPU 1: HashCnt = 864, time = 1842 ms, hashrate = 469 h/s
01:45:27:713 16a4 Round
01:45:27:844 6b14 GPU 0: HashCnt = 1024, time = 1922 ms, hashrate = 532 h/s
01:45:27:863 6b14 Dev round
01:45:29:363 6144 GPU 1: HashCnt = 864, time = 1625 ms, hashrate = 531 h/s
01:45:29:380 6144 Round
01:45:29:736 4104 GPU 0: HashCnt = 1024, time = 1845 ms, hashrate = 555 h/s
01:45:29:757 4104 Round
01:45:31:021 16a4 GPU 1: HashCnt = 864, time = 1615 ms, hashrate = 534 h/s |
|
|
|
|
The version 7.0 shows temp&fan-speed only for one of my two RX470 :-/
|
|
|
|
|
The new wallet is showing 1.2.3 and 1.2.5 as up2date ... Why?
|
|
|
|
I am trying to change servers. I am updated to 1.2.6. When I try to change I get this error: {"errorDescription":"recipient account does not have public key","errorCode":8,"requestProcessingTime":10}. I am trying to change to pool.burstcoin.biz. Any ideas? Thanks.
Which burst-id did you enter in the first checkbox? Sounds like a typo or that you have entered "pool.burstcoin.biz". You need to enter the burst-id of this pool (BURST-xxxx... ) |
|
|
|
The new wallet seems to be broken? Everything worked fine at the beginning, but after 2 days of runtime I'm on my own fork. Now I'm trying to resync the blockchain from the beginning :-( The block-view in the wallet is showing an unordered list of blocks:  |
|
|
|
|
Something wrong with the dev v2 pool? Currently on 259368 but my wallet shows 259390 :-(
|
|
|
|
|
I wasn't here since a longe time -> are there any important news about burst?
|
|
|
|
Mmmm... I was thinking to try mining with raspberry pi b+ to save electricity, and I don't it is possible now after reading you post above. I think that the reason why I did not see anyone mine burstcoin with raspberry pi yet...
Why don't you try, likr a proof-of-concept....?  It would be quite interesting to know how a raspberry would do, especially as we call BURST "enegy-friendly". I'm already planning a test  I'll keep ya posted. If crowetic already planned to start the raspberry test, and since I do not have a raspberry on hand yet, then I will wait for your proof-of-concept, I think that a raspberry pi has to low cpu-capacities for calculating those hashes. Maybe it'll work for <1TB, but not more. You also need a lot of cpu-power for the USB-Port (data transfer). |
|
|
|
Burst 1.2.1Download: https://mega.co.nz/#!TsgWkDyQ!lyJz_bEf29FyaC6DdRgqjM2NV8AkaSUC1gPtIWwHx08sha256: feda672f8bc5eabb31e56ebf78dc26d43a3422d24de22de277e59fc72a20fd19 All users should update as soon as possible. Fixed some AT bugs which could cause the blockchain to get stuck. Also changed a check during block generation which was causing some things to get skipped as duplicates when the thing they conflicted with wasn't passing validation. This should help with the problems some users have been having with reward assignments recently. I've updated my wallets. Would be great if you update the run.bat files so that every current java version is recognized (8u25 is currently not recognized correctly, but working after editing the run.bat file). |
|
|
|
http://burstcoin.mku.name:8080 feature update: - showing MA21 instead of MA50
- MA21 and MA7 are now displayed in the chart in area-style
- blockreward is displayed in the chart now
- MA7 is displayed in the sum-tables
- calculation is now done up to today and not the last day with transactions/blocks
|
|
|
|
Any idea how I can modify this batch file so it can restart shut down and restart every 2 hours? Right now it auto starts when it fails but I want a timer on it. Thanks @echo off
cls
:start
C:\Windows\SysWOW64\java -Xmx1024m -cp pocminer_pool.jar;lib/*;lib/akka/*;lib/jetty/* pocminer_pool.POCMiner mine http://127.0.0.1:8125 http://178.62.39.204:8121
goto start
You can start another batch file, which kills the miner-process and waits for 48 hours |
|
|
|
|
