Show Posts
|
Pages: [1] 2 3 »
|
No updates...Well it was an interesting start. Too bad to see a nice project like this not be updated ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) We dont really need claymore anyways...there are other options. but more options equal better options Can you please comment about new futures? I need some feedback about the new futures.
|
|
|
is development on this miner stopped?
Development continue. I will announce new version soon.
|
|
|
any update soon?
I'm working for new update, I will announce soon. You're doing better with keeping your IP hard(er) to get at - nice work. Might want to use C instead of Go so you can put in some anti-debugging traps, too. Also... in your "Optimized 4 threads" OpenCL... I know this won't make a huge difference, but it still makes me sad: bool update_share = thread_id == ((a >> 3) % THREADS);
Were that interpreted how you wrote it (verbatim), you would be eating... 4 clocks for the shift, and an untold number of clocks for the modulo, as AMD GCN doesn't even have modulo implemented - it's emulated. In reality, it's going to optimize that to an AND, making it look more like this: bool update_share = thread_id == ((a >> 3) & (THREADS - 1))
Okay, that's 8 clocks - two full-rate instructions. Unless you use a local worksize that's not a power of two, and in that case, god help you. But we can do better. First, for AMD - you're using LDS. Any worksize above wavefront size (64 work-items) is going to make those barriers take a LOT longer. Reason being, an AMD GCN CU (Compute Unit) only executes wavefronts. Larger work groupings are cut into wavefront-sized pieces and executed that way. If you use an LDS barrier with a worksize of 64 (wavefront size) - big deal, the whole wavefront is handled by that CU, and as such, the barriers can actually be omitted! And they are, by the AMD OCL compiler, in that case. When you make your group larger - suddenly you need to sync with other execution units: this is going to make you very sad. So - at least for AMD - I would keep it to 64 work-items/local group. Now - we know the value of THREADS - the kernel says it's a 4-way - so... get you one of these... #pragma OPENCL EXTENSION cl_amd_media_ops2 : enable
... and suddenly you have access to the amd_bfe builtin, which is purpose-built for what you wanna do! It gives you direct access to the v_alignbit_b32 instruction. And this gives us: bool update_share = thread_id == amd_bfe(a, 3U, 2U);
Shaving at LEAST four ticks off the best the compiler would likely come up with (and I am being generous.) As it's looped, this magnifies the effect of the optimization, although it's still not much. Now you have the operation done in a single full-rate instruction, though - which IS an improvement. WOW! tons of job like for me. @Wolf thanks your mention. I'll keep up these and will be share results here.
|
|
|
any update soon?
I'm working for new update, I will announce soon.
|
|
|
I found an issue with cloud service if i don't use a key or didn't have interest in using it some parameters do not work, like for example -M for device selection.
Could you please send full command line, I can test it.
|
|
|
Power usage is still pretty high. No watchdog, yet...
Did you try intensity parameter?
|
|
|
request to add feature to notify when significant hash rate drop for a worker(ideally configurable). ie. a worker usually do 180mh/s, if drops by more than X%(configurable) it sends a notification. do not need to notify immediately(configurable). but if below the threshold for more than Y(configurable) minutes then notify.
added to checklist, will add to cloud service.
|
|
|
Ok so I'm seeing about 0.5 to 1% better hashrate reporting pool side. Would be nice to have a worker automatic restart if a gpu goes down for some reason, and a warning, or automatic intensity drop for that gpu.
I added to checklist, this can be add to cloud service.
|
|
|
Can i use different pools for failover Like this -> eminer -S eu1.ethermine.org:4444,eth-eu1.nanopool.org:9999
BTW i like to use your miner , keep working !
Thanks
Yes it's possible, you can use if the pools support same username and password scheme.
|
|
|
I am reporting a LOT of crashing on Linux. Ubuntu 16.4 I have tried many different settings but the AMD cards crash every 30 mins or so. I wish I had a better understanding of the -kernel switch that no one will explain. 3 of the cards are 390's and I am thinking maybe they don't work well on -kernel 3. Also the fan speed switch does not seem to change the fan speeds on Linux.
So maybe someone can answer these 2 questions -
1) Explain differences between -k 1,2,3 2)is the -kernel switch able to use commas to set different kernels for different cards? -kernel 2,2,3,3,3 ANSWERED BY ME. YES IT WORKS LIKE EXAMPLE
Thanks for any help
1- Each kernel has different thread count 2- Yes you should set best kernel for your device like your parameter. I also advice intensity parameter, you should benchmark your device with best intensity like this; eminer -B <deviceid> -intensity <number> also you can choose kernel with this parameters. If your device crashing probably intensity high for your device.
|
|
|
Any thoughts to adding clock and memory speeds for AMD? -cclock 1100 -mclock 1500 Very useful for Linux rigs thks
Thanks for your advice, I added to my checklist, I will add next release.
|
|
|
Hi guys I am a a bit of a nub so please bear with me. I have the following rig setup for mining eth+dcr but i keep getting the error in the subject line. my setup is as follows:
Windows 10 64 bit 16GB ram ADM FX(tm)8350 eight core RX Vega 64 8GB Page file on e:\ min 1340 max 16400
running claymore dual miner 10 my batch file is as follows:
setx GPU_FORCE_64BIT_PTR 0 setx GPU_MAX_HEAP_SIZE 100 setx GPU_USE_SYNC_OBJECTS 1 setx GPU_MAX_ALLOC_PERCENT 100 setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool eth-us.dwarfpool.com:8008 -ewal xxxxxx.1 -epsw x -dpool stratum+tcp://yiimp.eu:3252 -dwal xxxxxx -dpsw x
any and all help would be extremely appreciated i tussled with this for a few hours last night and come up stumped. is it possibly because i have the page on the e:\ and claymore on the c:\ or is there something wrong in my batch file
Try another miner, https://github.com/ethash/eminer-release I just curious the problem solve or not.
|
|
|
You... left... the OCL in the binary... and it's not even packed! That... was kind of a let down.
OCL build on runtime like good idea for new chipsets so the miner can support all OCL based devices.
|
|
|
how to connect to: clona.ru (solo pool). I do not know how to edit the bat file so that I can connect to clona.ru please help me. TYVM
You can look example .bat file from https://github.com/ethash/eminer-release
|
|
|
Looks like your 480 crashed, like high overclock problem.
I know, I mean if a card stopped, Eminer should warn me -- not continue to average with 0MH/s I see, added to my checklist.
|
|
|
also just want to check if we can delete workers from the cloud dashboard?
i did not use the -N to specify the worker name so the dashboard has multiple instance of the random 5 char string showing up.
- cloud key no random, its recoverable. - your old workers will be delete automatically within 24 hours.
|
|
|
I have a problem. My RX480 crashed, but Eminer thinking it's still alive, so I got this: ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2F1ApdphY.jpg&t=665&c=ofWscdm1Yeh9nA) Please fix it. Thanks. ( In the state, miner can't be restarted, so I only need to know what correct happens and stop) Win10/AMD DAG fix driver/Eminer 0.6.1 RC2/ASUS RX480 4G dual Looks like your 480 crashed, like high overclock problem.
|
|
|
Why is there still no transparency on when the Dev Fee is being mined?
Claymore does this and you should too.
It's already logging, you can see devfee start and stop messages on console, I think, its clearly transparency
|
|
|
really like so far ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) )) is there a way that you make the cloud monitoring local on ones network? edit: when running on my AMD rig i get this msg: WARN [09-20|00:04:13] AMD (ADL) hardware monitor library couldn't initialize
? Miner has local monitoring, you can view the local dashboard from http://localhost:8550What is your OS? If you using Linux, ignore the message, eminer has alternative solution on Linux for AMD devices.
|
|
|
after 2 hours running eminer v0.6.1-RC2, windows 10, cloud service, received error:
ERROR[09-19|22:29:36] Couldn't send stats to cloud service error="Not verified"
local eminer still working with no problem
Thanks for your report, problem has been solved. Can you check again?
|
|
|
|