Topic: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free) - page 523. (Read 836157 times)

This is just awesome, thank you! 

UPDATE v1074:
- atiflash for linux - for now its only program located at /root/utils/atiflash
If you know putty (ssh) then you can login into rig and flash custom bios remotly.
The flashing from dashboard will be propably implemented in future but not soon.
Right now you can do the flashing only by direct ssh into rigs.

1. Yes it will help -w1 -r1
2. I dont have it now, but i am planning to add this. As now i can add this program to root directory and then you can do the rest via ssh.
But option for flashing from dashboard will be propably possible but later on.

-r 1 does indeed work.

Hello!

Two questions:

1) Two of our rigs were stuck because watchdog detected a problem with one GPUs and needed to restart the mining process, but froze there. Can we use -r 1 to force the rig to restart instead? This way, they will restart the mining process properly. Even on windows, we had that issues, -r 1 would help. I am wondering if the reboot.sh is present in the claymore folder.

2) Would it be possible to have atiflash installed on the image? (maybe it is and I didnt find it) It would be greatly appreciated and it would save us time to flash our cards instead of putting a windows drive in order to do the flashing.

Thanks!!

Yet another alternative:

-gser 2 -eres 1

-gser   this setting can improve stability on multi-GPU systems if miner hangs during startup. It serializes GPUs initalization routines. Use "-gser 1" to serailize some of routines and "-gser 2" to serialize all routines.
   Default value is "0" (no serialization, fast initialization).

-eres   this setting is related to Ethereum mining stability. Every next Ethereum epoch requires a bit more GPU memory, miner can crash during reallocating GPU buffer for new DAG.
   To avoid it, miner reserves a bit larger GPU buffer at startup, so it can process several epochs without buffer reallocation.
   This setting defines how many epochs miner must foresee when it reserves GPU buffer, i.e. how many epochs will be processed without buffer reallocation. Default value is 2.

UPCOMING SRR UPDATE:
I am making new fireware and Tool updates for SRR.
If you are interested and have ideas what can i add or improve, then now its the time to tell me that

https://bitcointalk.org/index.php?topic=1695298.new#new

If still problem after settings per phil's post below, try -lidag
Assuming your GPU has more than 2GB mem

if claymore 8   -ethi 4   should fix it

-ethi 8 is stock

you can try 7 then 6 if it crashes then 5 then 4

you will lose a little hash with 4,5,6,7  settings



my eth  for my pandaminer which has the exact issue as you  due to weak cpu

-epool stratum+tcp://us1.ethpool.org:3333 -ewal 0x3ef297e47404a771139472b93621f82c8a832857.Simple2 -esm 0 -epsw x -allpools 1 -mport -3333 -ethi 4


pandaminer on 4



i get 228mh  no crash
on 7 i get 230 mh crash
pn 8 the stock setting I get 231 same crash as you

Nope, i will start thinking about that not sooner than in 4 months.

2 GB memory in gpus ?

Setting DAG epoch #109 for GPU #1
Create GPU buffer for GPU #1
OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
Setting DAG epoch #109 for GPU #0
Create GPU buffer for GPU #0
OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
Setting DAG epoch #109 for GPU #2
Create GPU buffer for GPU #2
OpenCL error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
ETH: 03/05/17-08:32:13 - New job from pool.bitclouder.co:3333
ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
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
Setting DAG epoch #109 for GPU #4
GPU 4, OpenCL error -38 - cannot write buffer for DAG
Setting DAG epoch #109 for GPU #3
GPU 3, OpenCL error -38 - cannot write buffer for DAG
Setting DAG epoch #109 for GPU #0
GPU 0, OpenCL error -38 - cannot write buffer for DAG
Setting DAG epoch #109 for GPU #1
GPU 1, OpenCL error -38 - cannot write buffer for DAG
Setting DAG epoch #109 for GPU #2
GPU 2, OpenCL error -38 - cannot write buffer for DAG
GPU0 t=17C fan=67%, GPU1 t=18C fan=67%, GPU2 t=18C fan=67%, GPU3 t=30C fan=67%, GPU4 t=20C fan=67%
WATCHDOG: GPU error, you need to restart miner
Binary file (standard input) matches
Close

Hey tytanick, do you plan to support nvidia gpu's anytime soon?

Update v1073
- claymore-zec v12.2 fix memory leak
note. it will start using this after reload

oops my bad on the usr vs user syntax

great mining!

T,

URGENT - Can help recompile Claymore ZEC Miner v12.2. Thanks

v12.2 had a memory leak issue and Claymore fixed it and asked everyone to redownload v12.2.

===
Re: Claymore's ZCash AMD GPU Miner v12.2 (Windows/Linux)
Today at 01:35:02 PM
...

Windows Miner v12.2 has a memory leak 700mb per day, 5gb per week.

yes, this is true. Claymore can you fix this?

Confirmed, fixed. I can re-upload v12.2 or I can include this fix in next update which will be available in a few days.

 12.21 then do the update next week as 12.3

Also please allow -i 8 again on nanos. No reason to disable it!

Memory leak: just redownload v12.2, see note in OP.
-i 8: done, you can use it already.

Claymore - this revised 12.2 is only applicable for Windows version correct ? -- Linux version no impact??

Linux is affected too.
===

Thank you very much for all that information. We learned the hard way to manage rigs with ethOS with SSH connections. We successfully connected to our rigs with that infos.

I just would like to point out that it didnt work for us at first.

nano /mnt/usr/config.txt didnt work, it would open an empty config.txt, but this one worked: nano /mnt/user/config.txt  ==== https://www.dropbox.com/s/y1rnxxc6mp1jwx8/Capture4.PNG?dl=0

We had to look around in the drive to discover that! Our rig is now mining under our wallet address. Maybe it would be a good idea to add these troubleshooting steps in case this happens to someone else.

Cheers!

Cpu mining will be only as an option to mine as fee for me.
There wont be mining for cpus as there is no sense of doing that.

Tytus, any plans on using the CPUs in the rigs as an option for mining? Hard thing to code or easy to do?
Since at most times it makes no sense to mine the same coin / algo as your GPUs.. maybe with a seperate group in the GUI?

I use WINSCP (also from putty suite) in Windows
then go to /mnt/user/
Edit the config.txt
change email (I also add in the first comment R9 or  Rx so i can know what kind of release im editing, and rig identificator for my location)
and just wait like 10 sec, then the rig automagically changes from one panel to the other.
Of course the rig keep doing the same stuff until you reset miner or reboot rig.

I use this way when are trying new configs, so i can move just 1 rig to that email panel and do the tests without affecting the rest, and work flawlessly.

You need to login to the panel of the new email and set the OPTIONS : wallets miner selection.
Just like you did with your first rig, because is a new account.