Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 635. (Read 6590565 times)

1. Turns out, eu1.ethpool.org resolves to several IPs, the miner picks up the first one. The first one does not work (probably due to my location). So, this is a pool problem.
2. This does have to be solved. Watchdog should not be triggered in this case. Miner should differentiate between a mining proxy and a router.

You can run several miner instances. If you, say, have 6 GPUs in your rig, let 5 GPUs mine for rig owner and 1 GPU mine for you.

I don't think this is a problem that needs to be addressed in the miner as it just sounds like you need to fix your internet 

Hi.

I noticed a couple of problems with the miner.

1. ethpool.org IP is not resolved correctly. Looks like eu1.ethpool.org IP is hard-coded or cached somewhere into miner. First connection attempt ALWAYS fails. Then, 20 sec wait, then, successful connect using a failover address. The first IP that miner tries to connect to (91.121.73.83) is not the IP which eu1.ethpool.org actually resolves to at the moment (188.165.235.31). My connections string is ./ethdcrminer64 -epool eu1.ethpool.org:3333 (Ubuntu)

2. I mine thru a typical wired router. When sometimes the router looses ISP connection it, as usual, serves its own error page to all clients. The miner, however, thinks it's a kind of a local proxy and attempts to continue mining. As no more new shares are found (because no more new jobs supplied), the miner thinks it's GPU failure ("Miner thread hangs") and activates the watchdog, instead of simply sitting there and waiting for internet connection to resume. This is not the right type of behavior, IMO.

Thanks!

i want percent of others to mine to my wallet.

Had the same problem with my RX570, also befor kernel update. I flashed only 1 clk level to the RX570, after that they run fine.
With the RX4X0 i had no Problems to set the clk with rocm-smi, they run stabel

Also I am geting GPU failed after 10 min mining

03:16:48:810   19a0   parse packet: 242
03:16:48:814   19a0   ETH: job is the same
03:16:48:818   19a0   new buf size: 0
03:16:53:899   23dc   GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure
03:16:53:927   139c   GPU 3, GpuMiner cu_k1 failed 4, unspecified launch failure
03:16:53:937   19a8   GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure
03:16:53:948   23f4   GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure
03:16:53:957   23e8   GPU 2, GpuMiner cu_k1 failed 4, unspecified launch failure
03:16:53:973   23dc   GPU 0, GpuMiner kx failed 1
03:16:53:979   139c   GPU 3, GpuMiner kx failed 1
03:16:53:996   19a8   GPU 4, GpuMiner kx failed 1
03:16:54:011   23f4   GPU 1, GpuMiner kx failed 1
03:16:54:021   23e8   GPU 2, GpuMiner kx failed 1
03:16:53:978   23dc   Set global fail flag, failed GPU0
03:16:53:995   139c   Set global fail flag, failed GPU3
03:16:54:046   139c   GPU 3 failed
03:16:54:021   23f4   Set global fail flag, failed GPU1
03:16:54:041   23e8   Set global fail flag, failed GPU2
03:16:54:061   23e8   GPU 2 failed
03:16:54:073   1e8c   GPU 2, GpuMiner cu_k1 failed 4, unspecified launch failure
03:16:54:077   19a4   GPU 3, GpuMiner cu_k1 failed 4, unspecified launch failure
03:16:54:009   19a8   Set global fail flag, failed GPU4
03:16:54:092   23dc   GPU 0 failed
03:16:54:103   23d8   GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure
03:16:54:107   23d8   GPU 0, GpuMiner kx failed 1
03:16:54:113   23f4   GPU 1 failed
03:16:54:120   1e8c   GPU 2, GpuMiner kx failed 1
03:16:54:136   19a4   GPU 3, GpuMiner kx failed 1
03:16:54:139   1984   GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure
03:16:54:143   19a8   GPU 4 failed
03:16:54:150   23f0   GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure
03:16:54:171   23f0   GPU 1, GpuMiner kx failed 1
03:16:54:136   1e8c   Set global fail flag, failed GPU2
03:16:54:181   1e8c   GPU 2 failed
03:16:54:188   1984   GPU 4, GpuMiner kx failed 1
03:16:54:113   23d8   Set global fail flag, failed GPU0
03:16:54:209   23d8   GPU 0 failed
03:16:54:139   19a4   Set global fail flag, failed GPU3
03:16:54:205   1984   Set global fail flag, failed GPU4
03:16:54:223   1984   GPU 4 failed
03:16:54:177   23f0   Set global fail flag, failed GPU1
03:16:54:247   23f0   GPU 1 failed
03:16:54:252   19a4   GPU 3 failed
03:16:57:392   19a0   got 243 bytes
03:16:57:404   19a0   buf: {"jsonrpc":"2.0","id":0,"result":["0xb302a12302b6b8007c5d9535343f1f4ffc860069310e3ea98f82bc12aa58dc09","0x0986c6a216293f204351dd4d0b5570e9d5979d65e8389cfbc8ffe0b517d9706c","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}

03:16:57:416   19a0   parse packet: 242
03:16:57:428   19a0   ETH: job changed
03:16:57:439   19a0   new buf size: 0
03:16:57:446   19a0   ETH: 08/30/17-03:16:57 - New job from eth-asia1.nanopool.org:9999
03:16:57:453   19a0   target: 0x00000000dbe6fece (diff: 5000MH), epoch 140(2.09GB)
03:16:57:459   19a0   ETH - Total Speed: 0.000 Mh/s, Total Shares: 39, Rejected: 0, Time: 00:20
03:16:57:467   19a0   ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s
03:16:58:428   19a0   ETH: checking pool connection...
03:16:58:439   19a0   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

Sounds like your psu is being overloaded by that 6th card.

HI GUYS,

 I need help !!!

CLAYMORE V9.8 mining ethereum

I am using ZOTAC GTX 1070 MINI GPU , with Intel pentium G4400 CPU, 4 GB DDR4 ram, 1500 Watt PSU silver edition

WIN 10 Verision 1703 , NVIDIVA Driver verision 385.41

everything works fine for 5 GPU, and basic hashrate 26 Mh/Sec and after MSI afterburner overclocking 30-31Mh/sec

PROBLEM :

when I add the 6th Card..  it runs for 3-5 mins and restarts windows ... it is like loop .

---
I even tried BIOS motherboard H110-D3A Gigabyte enabling 4G encoding.


still, it crashes and restart.

how to fix this issue..

any help... I even checked PCI riser cables .. unpluged and re plugged..

how to make 6th card working without crashing windows

Hi,

I just need to verify something about the amd beta blockchain driver.
I have a rig 8 GPU RX580 Gaming 8 Go (Hynix), in june i got 242 MH/s.
Actually in august i obtain 233 MH/s, in order to solve this drop MH/s, i installed this beta blockchain driver i got 248 MH/s, but i met issue with GPU clock speed frequency alternatively jumping 1000 to 1300 MHz.
Is somebody here met the same issue and find solution to solve this?

Thank you for help.

Why don't you use a percent of your rigs to mine to your wallet?

guys , is it possible to mine with claymore on two wallets? i support a lot of rigs and i want to take percent to my wallet like devfee to claymore. now i only use dual mining to my wallet but i want percent of ethereum.

I'm getting the following error:

============ Starting Miner ===============
dirname: missing operand
Try 'dirname --help' for more information.
/root/xminer.sh: line 40: [: !=: unary operator expected
GO TO GLOBAL OPTIONS or RELOAD RIG if you already configured options and this ris is new added !!!!!


I think I don't know how to chose the kernel after all.. Would you help me out?

what mean this " choose new kernel?
where shell i choose it?

Hi Tytanick,

We need this in beta ASAP. Dag fix for Linux.

New AMD Blockchain optimized drivers availible for linux (finally)

https://www.reddit.com/r/EtherMining/comments/6wsf7o/new_amd_blockchain_optimized_drivers_availible/

And what about the guy who says "I've heard about a mining operation system", when he is the founder. 

I'm curious too...

GREET its work

  You cannot trust the guy who quotes himself on the front page

Try this
http://www.tomshardware.com/faq/id-1904869/disable-ulps-amd-crossfire-setups.html