What is good invalid rate for eth mining? Sometimes i have almost 10% invalids per round 
0% is good
Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 1260. (Read 6590565 times)
June 27, 2016, 01:57:58 PM
0% is good
June 27, 2016, 01:37:33 PM
What is good invalid rate for eth mining? Sometimes i have almost 10% invalids per round
June 27, 2016, 11:43:59 AM
anyone got any lines on who is taking pre-orders for the AMD RX 480s yet?
B&H but the prices are outrageous...
Check it out:
http://www.bhphotovideo.com/c/product/1261505-REG/index.html
http://www.bhphotovideo.com/c/product/1261970-REG/msi_radeon_rx_480_8g_rdn_rx_480_gddr5.html
$10 over retail, but I don't like the July delivery date!!
I don't think $284 is $10 over retail...
2nd link says $239, I'm actually hoping for a gigabyte version
Ok, those are two links to two different products
June 27, 2016, 11:33:15 AM
anyone got any lines on who is taking pre-orders for the AMD RX 480s yet?
B&H but the prices are outrageous...
Check it out:
http://www.bhphotovideo.com/c/product/1261505-REG/index.html
http://www.bhphotovideo.com/c/product/1261970-REG/msi_radeon_rx_480_8g_rdn_rx_480_gddr5.html
$10 over retail, but I don't like the July delivery date!!
I don't think $284 is $10 over retail...
2nd link says $239, I'm actually hoping for a gigabyte version
June 27, 2016, 11:29:16 AM
anyone got any lines on who is taking pre-orders for the AMD RX 480s yet?
B&H but the prices are outrageous...
Check it out:
http://www.bhphotovideo.com/c/product/1261505-REG/index.html
http://www.bhphotovideo.com/c/product/1261970-REG/msi_radeon_rx_480_8g_rdn_rx_480_gddr5.html
$10 over retail, but I don't like the July delivery date!!
I don't think $284 is $10 over retail...
June 27, 2016, 11:23:50 AM
anyone got any lines on who is taking pre-orders for the AMD RX 480s yet?
B&H but the prices are outrageous...
Check it out:
http://www.bhphotovideo.com/c/product/1261505-REG/index.html
http://www.bhphotovideo.com/c/product/1261970-REG/msi_radeon_rx_480_8g_rdn_rx_480_gddr5.html
$10 over retail, but I don't like the July delivery date!!
June 27, 2016, 11:21:10 AM
And strictly speaking, they're right. Any fork breaks the main idea of blockchain, making Ethereum NOT that declared on their main page.
The worst thing is that so called hacker may be wrong in general, but strictly complied with the terms of TheDAO contract. Any fork means that a 3rd-party changes the rules of the game on the fly in favor of someone just because some business made something wrong and lost some investments. Any investment is a risk, and they should learn the lesson, fix it and move on. Instead, due to conflict of interests being in both Ethereum foundation and TheDAO curators, they decided to prove the world that they are right to break own rules just because they lost some money due to own fault. Be that a smaller project that failed, no one would ever thought about any forks. But this one just "too big to fail", and that's sad.
No any polls and votes should be treated as the network consensus - they just mean that people trust to the founders without own investigation. If one said 'theft', they do not do own judgement. And just led by a false goal. Killing the whole Ethereum thing as a result.
The worst thing is that so called hacker may be wrong in general, but strictly complied with the terms of TheDAO contract. Any fork means that a 3rd-party changes the rules of the game on the fly in favor of someone just because some business made something wrong and lost some investments. Any investment is a risk, and they should learn the lesson, fix it and move on. Instead, due to conflict of interests being in both Ethereum foundation and TheDAO curators, they decided to prove the world that they are right to break own rules just because they lost some money due to own fault. Be that a smaller project that failed, no one would ever thought about any forks. But this one just "too big to fail", and that's sad.
No any polls and votes should be treated as the network consensus - they just mean that people trust to the founders without own investigation. If one said 'theft', they do not do own judgement. And just led by a false goal. Killing the whole Ethereum thing as a result.
June 27, 2016, 11:17:32 AM
anyone got any lines on who is taking pre-orders for the AMD RX 480s yet?
B&H but the prices are outrageous...
Check it out:
http://www.bhphotovideo.com/c/product/1261505-REG/index.html
http://www.bhphotovideo.com/c/product/1261970-REG/msi_radeon_rx_480_8g_rdn_rx_480_gddr5.html
June 27, 2016, 11:14:14 AM
Hi, Claymore,
Hi, guys,
Can you please help me. I've noticed that the miner is getting stuck several times in the past few days.
So I have carefully read "red lines" and it says error 10004.
The miner restarts after this error. But few minutes later same error - miner restarts again and get stuck on "POOl/SOLO...." text.
What is this error? And where is the problem, i.e. what should I do to fix it?
Thank you.
Hi, guys,
Can you please help me. I've noticed that the miner is getting stuck several times in the past few days.
So I have carefully read "red lines" and it says error 10004.
The miner restarts after this error. But few minutes later same error - miner restarts again and get stuck on "POOl/SOLO...." text.
What is this error? And where is the problem, i.e. what should I do to fix it?
Thank you.
It's uncommon error, something is wrong with winsock. You can PM me the log.
June 27, 2016, 11:11:47 AM
anyone got any lines on who is taking pre-orders for the AMD RX 480s yet?
June 27, 2016, 11:08:11 AM
June 27, 2016, 08:31:18 AM
Hi, Claymore,
Hi, guys,
Can you please help me. I've noticed that the miner is getting stuck several times in the past few days.
So I have carefully read "red lines" and it says error 10004.
The miner restarts after this error. But few minutes later same error - miner restarts again and get stuck on "POOl/SOLO...." text.
What is this error? And where is the problem, i.e. what should I do to fix it?
Thank you.
Hi, guys,
Can you please help me. I've noticed that the miner is getting stuck several times in the past few days.
So I have carefully read "red lines" and it says error 10004.
The miner restarts after this error. But few minutes later same error - miner restarts again and get stuck on "POOl/SOLO...." text.
What is this error? And where is the problem, i.e. what should I do to fix it?
Thank you.
June 27, 2016, 08:16:57 AM
If u wish to vote for soft-fork then mine on a pool that is running soft-fork supported geth 1.4.8. Coinotron is running this version of geth, however they have also opened an alternate port that allows you to vote against soft-fork. I read around that some other pools are running the softfork version of geth also, you should investigate if ur pool is doing so or change appropriately.
June 27, 2016, 07:53:54 AM
2 Claymore
What about https://github.com/ethereum/go-ethereum/releases/tag/v1.4.8
Should you update your miner? As your miner has great % of ether mining, is running unupdates miners is voting anti-soft-fork may cause problems 0-o
What about https://github.com/ethereum/go-ethereum/releases/tag/v1.4.8
Should you update your miner? As your miner has great % of ether mining, is running unupdates miners is voting anti-soft-fork may cause problems 0-o
https://bitcointalksearch.org/topic/m.15356732
June 27, 2016, 07:50:57 AM
2 Claymore
What about https://github.com/ethereum/go-ethereum/releases/tag/v1.4.8
Should you update your miner? As your miner has great % of ether mining, is running unupdates miners is voting anti-soft-fork may cause problems 0-o
What about https://github.com/ethereum/go-ethereum/releases/tag/v1.4.8
Should you update your miner? As your miner has great % of ether mining, is running unupdates miners is voting anti-soft-fork may cause problems 0-o
June 27, 2016, 04:41:57 AM
Also I can definitely confirm that the memory leak is directly related to the telemetry. I stopped the monitoring and found no memory leaks using the same top output. As soon as I started the monitor again, the leak resumed.
More info found, I'll PM it to you.
More info found, I'll PM it to you.
June 27, 2016, 04:37:53 AM
That might be the memory leak since I reported you about that already. Now I still use 4.5 after 7 hours of total rejects @ Dwarf with 4.6 for both rigs. I can run the debug version but do not like an idea of having another few hours of rejects 
Unfortunately I can't help with memory leak debug for closed source software.
Unfortunately I can't help with memory leak debug for closed source software.
It's not a memory leak. I'd like to see the log with rejects. Anyway, I'll send you a debug version soon.
No, no. These are two different issues.
Rejects I saw with 4.6 right after release when switched from 4.5 in a hope to get fixed the telemetry problems. It run without logs since there was no issues with rejects until 4.6. So I cannot show those logs.
Now I run 4.5 again that has no such issues. But the memory leak is obvious and easily observed. If you run the program 'top', you'll see that the miner process consumes around 1M per second of virtual memory. Probably that is the reason why telemetry got dropped. You close the socket after every request and probably something leaks. I expected to open the control connection once and then just send requests and get replies over the same socket.
Please check the 'top' output on Linux and I am sure you will fix that leak easily.
June 27, 2016, 04:19:27 AM
I get a lot of PMs, usually I answer all, but can miss some, sorry. I will PM you debug version today, it looks like resources leak instead of time overflow, but I cannot debug/handle such thing in Linux properly, it's not my primary OS.
That might be the memory leak since I reported you about that already. Now I still use 4.5 after 7 hours of total rejects @ Dwarf with 4.6 for both rigs. I can run the debug version but do not like an idea of having another few hours of rejects Unfortunately I can't help with memory leak debug for closed source software.
It's not a memory leak. I'd like to see the log with rejects. Anyway, I'll send you a debug version soon.
June 27, 2016, 04:03:29 AM
I get a lot of PMs, usually I answer all, but can miss some, sorry. I will PM you debug version today, it looks like resources leak instead of time overflow, but I cannot debug/handle such thing in Linux properly, it's not my primary OS.
That might be the memory leak since I reported you about that already. Now I still use 4.5 after 7 hours of total rejects @ Dwarf with 4.6 for both rigs. I can run the debug version but do not like an idea of having another few hours of rejects Unfortunately I can't help with memory leak debug for closed source software.
June 27, 2016, 03:59:13 AM
v4.6:
- bug fixes.
- bug fixes.
Can you confirm if it has any stability improvements on Linux regarding statistics socket? 4.4 had issues, 4.5 didn't have as I thought but there was a report of them here. Today I also found the issue of loosing socket by 4.5 on Linux. What about 4.6, were any changes done for it?
Since you twice ignored this question, I assume the answer is "No changes, Linux 4.6 telemetry still is unstable".
Due to reject issues with 4.6 and some pools I set back to 4.5. After running two rigs for ~45 hours both at the same time and same uptime had lost telemetry sockets, still running fine for mining. I am sending you links to both full logs in PM.
Quote
Error: no response
Last seen: 2016-06-25 06:40:45
Error: no response
Last seen: 2016-06-25 06:42:01
Last seen: 2016-06-25 06:40:45
Error: no response
Last seen: 2016-06-25 06:42:01
Any chances to have stable telemetry on Linux? Or should I finally write an own process monitor and restart miner when telemetry is lost?
I still cannot reproduce this issue. PM me, I can send you a debug version with more detailed log, it seems it's the only way to fix this problem.
Now I repeated the case. Again, both rigs started at the same time stopped responding at the same time. That is common, the uptime - it is around 45 hours. I think some timer overflows with that period.
I get a lot of PMs, usually I answer all, but can miss some, sorry. I will PM you debug version today, it looks like resources leak instead of time overflow, but I cannot debug/handle such thing in Linux properly, it's not my primary OS.
Jump to: