Did you replace the power cables and the USB cable going to the riser as well?  most of my 'riser fails' have been actually due to those 2 cables and the riser is actually fine.

Thank you!  that fix it.

I'm setting up a new rig with Ubuntu 14.04.4 and installed the fglrx drivers and doing driver checks I see my card.  However when I try to list my devices in optiminer I get the following:

$ ./optiminer-zcash --list-devices
./optiminer-zcash: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by ./optiminer-zcash)
./optiminer-zcash: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by ./optiminer-zcash)


Anyone know what I'm missing?  Seems like I should know the answer to this but I'm just struggling.

Correct me if I'm wrong, but wasn't it Wolf's code that Claymore got busted using on one of his miners without giving him credit for it?  If so, Wolf has his reasons.

He's also right about the increase of speed.  A week later and you're making the same amount.  The coins are basically self-regulating when it comes to that.  You just end up paying more for the electricty to make them because the newer faster miner is pushing the cards harder and killing them quicker.   Just like when the price of the coin goes up, the difficulty is right behind it, now suddenly your making less coins per day and for the most part your revenue ends up being a wash in the end.

I'm trying to mine an alt coin in a rig with 380 (4Gb) cards and one 7950 (3Gb) but it keeps crashing when it is switching between normal and dev mining on the 7950.  I'm using:

-allcoins -1 -allpools 1

and instead of crashing 15 minutes into mining, it now lasts and hour and then crashes.

Can someone explain the -allcoins option for me?  in the Readme it says to use "-allcoins 47" to specify room for epoch #47.   Is that for 47 epochs from where it started or what?   how often are the new epochs created. 

Just trying to figure out something else to try and looking for suggestions.   I don't want to run with the -nofee option.

Can someone with Fury cards please tell me what they are getting for wattage?  Thanks!

optiminer - I had a rig totally lock up last night.  The log below show something I've never seen before.  Any idea of what caused it?  Is the 'Concurrent write detected, queuing' a complaint that it can't communicate to flypool or that it can't write to a GPU?

Ubuntu 14.04 with the 15.xx drivers and 6 GPUs.

I've had a GPU lock up before and your watchdog reboots my computer but this time it never even envoked watchdog.  The next entry in the log file is when it was starting back up after I rebooted it.


[2017-03-28 23:18:55.166] [info] Concurrent write detected, queuing.
[2017-03-28 23:18:55.202] [info] Concurrent write detected, queuing.
[2017-03-28 23:18:55.789] [info] Concurrent write detected, queuing.
[2017-03-28 23:18:56.226] [info] [GPU1]  137.0 I/s 262.8 S/s (5s) 137.8 I/s 258.3 S/s (1m) 137.7 I/s 258.8 S/s (1h)
[2017-03-28 23:18:56.528] [info] [GPU3]  112.0 I/s 223.2 S/s (5s) 111.6 I/s 208.2 S/s (1m) 111.5 I/s 209.2 S/s (1h)
[2017-03-28 23:18:56.604] [info] [Total]  689.0 I/s 1300.0 S/s (5s) 686.8 I/s 1279.6 S/s (1m) 686.7 I/s 1289.1 S/s (1h)
[2017-03-28 23:18:56.912] [info] Concurrent write detected, queuing.
[2017-03-28 23:18:57.234] [info] [GPU2]  103.0 I/s 179.2 S/s (5s) 102.7 I/s 190.4 S/s (1m) 102.6 I/s 192.3 S/s (1h)
[2017-03-28 23:18:57.999] [info] [GPU4]  112.0 I/s 209.8 S/s (5s) 111.7 I/s 207.1 S/s (1m) 111.7 I/s 209.9 S/s (1h)
[2017-03-28 23:18:58.436] [info] Concurrent write detected, queuing.
[2017-03-28 23:18:58.611] [info] Concurrent write detected, queuing.
[2017-03-28 23:18:58.696] [info] [GPU5]  111.0 I/s 202.0 S/s (5s) 111.5 I/s 207.4 S/s (1m) 111.6 I/s 209.4 S/s (1h)
[2017-03-28 23:18:59.132] [info] Concurrent write detected, queuing.
[2017-03-28 23:18:59.527] [info] [GPU0]  111.0 I/s 200.2 S/s (5s) 111.6 I/s 207.0 S/s (1m) 111.6 I/s 209.4 S/s (1h)
[2017-03-28 23:18:59.997] [warning] The write deadline expired! Closing connection.
[2017-03-28 23:18:59.997] [error] IO/Error communicating to us1-zcash.flypool.org
[2017-03-28 23:18:59.997] [error] IO/Error communicating to us1-zcash.flypool.org
[2017-03-28 23:18:59.997] [error] IO/Error communicating to us1-zcash.flypool.org
[2017-03-28 23:18:59.997] [error] IO/Error communicating to us1-zcash.flypool.org
[2017-03-28 23:18:59.997] [error] IO/Error communicating to us1-zcash.flypool.org
[2017-03-28 23:18:59.997] [error] IO/Error communicating to us1-zcash.flypool.org
[2017-03-28 23:18:59.997] [error] IO/Error communicating to us1-zcash.flypool.org
[2017-03-28 23:18:59.997] [error] IO/Error communicating to us1-zcash.flypool.org
[2017-03-28 23:18:59.997] [error] IO/Error communicating to us1-zcash.flypool.org
[2017-03-28 23:18:59.997] [error] IO/Error communicating to us1-zcash.flypool.org
[2017-03-28 23:18:59.997] [error] IO/Error communicating to us1-zcash.flypool.org
[2017-03-28 23:18:59.997] [error] IO/Error communicating to us1-zcash.flypool.org
[2017-03-28 23:18:59.997] [error] IO/Error communicating to us1-zcash.flypool.org
[2017-03-28 23:18:59.997] [error] IO/Error communicating to us1-zcash.flypool.org
[2017-03-28 23:18:59.997] [error] IO/Error communicating to us1-zcash.flypool.org
[2017-03-28 23:18:59.997] [error] IO/Error communicating to us1-zcash.flypool.org
[2017-03-28 23:18:59.997] [error] IO/Error communicating to us1-zcash.flypool.org

Can anyone tell me what the wall power is on the R9 Fury card is?

Can someone give me approx what an R9 Fury 4G card would give in hash rate and power consumption?  -Thanks.

You failed to mention Windows vs Linux.  That's my what always irritates me about all these comparisons.  First of all, Optiminer has always said his performs better on Linux and Claymore has said he prefers the Windows side.   So then you get these people that complain that their card isn't doing as well as the other person's card but neither have stated which platform they are on.  If you don't give all the important details of what your results are, don't bother posting them!

But to what you said, you are totally right.  When I make a change I look at my hash rates on the local screen to make sure the cards are doing approx what they should be for 5-10 minutes and then I walk away and I'll spot check the pool results for the next few hours if I'm near the computer and then I don't look at it until the next day to see if my average is going up/down.  I also look at the network difficulty to see if that is going up/down also as that will also show in your average as well.

That's a good one too.   Been thinking about making my rig headless.  Might have to use that myself.

As for logging, zzzzzzzzzz's is a good way to log it.  Another option for you if you want to have it scrolling in a terminal window and also log it at the same time is to use the -l (lowercase L) option.   In the mine.sh file, change the optiminer-zcash line to include the logging option.

./optiminer-zcash -s $POOL -u $USER -p $PASSWORD -l <logfilename> --watchdog-timeout 30 --watchdog-cmd "./watchdog-cmd.sh"

It appears that it rotates the logs periodically and keep the last 10 so that none of the files are too large.  What is really nice about this option is you can see live on the screen what is going on but you can still SSH into your box from another computer and then do a

tail -f <path>/<logfilename>

and it will continuously scroll what is being added to the log live.

Either way you do it, the advantage to logging is that if your rig is having to reboot you can go back in the logs to see why.   A few days ago I had issues with mine rebooting about every 8-12 hours.  A check in the log consistently showed GPU 0 hanging and so I re-worked the power to the riser (it all started after I re-arranged all the cables to improve airflow) and now it's running 48+ hours.

You don't have to use mine.sh but it has the watchdog stuff setup in there automatically.   See it at the end of the line?  That is what makes it start watching over your rig and to restart it if it is having issues.

./optiminer-zcash -s $POOL -u $USER -p $PASSWORD --watchdog-timeout 30 --watchdog-cmd "./watchdog-cmd.sh"

The other advantage to setting it up and using it is that you can have your system set to run that bash script upon startup so it just makes the whole thing automatic.  If you want to manually type it in a terminal window each time, that's fine too.  it just won't startup automatically if your rig is rebooted.

zzzzzzzzzz is right on the permissions.  I forgot that I had to change the permissions for that file.    just do a

chmod 755 mine.sh

In the optiminer folder there is a file called mine.sh    it's just a little bash script to startup your miner.   But in it you need to change the wallet ID and also specify what pool you want it to connect to.  It is about in the middle.  This is what you are looking for:

# Flypool (encrypted connection):
# uses cash address as user
POOL=zstratum+tls://eu1-zcash.flypool.org:3443
USER=t1Yszagk1jBjdyPfs2GxXx1GWcfn6fdTuFJ.worker
PASSWORD=x

# Nicehash:
# uses bitcoin address as user
#POOL=equihash.usa.nicehash.com:3357
#USER=19STEagfLfbb1XdTF9NCf5kmxZHGchSiZj
#PASSWORD=x

# suprnova.cc
#POOL=zec.suprnova.cc:2142
#USER=Weblogin.Worker
#PASSWORD=WorkerPassword

Change that so it has your information.  By default it is setup for Flypool.  If you use something different, comment out the flypool and uncomment the section you want.  Just change the info to match your wallet.  That is all you really have to edit in the file.  And yes, you can use nano, gedit, vi,  any of those or any other favorite text editor.  It's just a text file.    This is the file that actually starts up optiminer and keeps it running.

Setting up watchdog isn't just one simple file.  It's several simple things actually.  Here is what I did.  I'm running Ubuntu 14.04

1). Setup your Linux to auto log in and auto start your 'mine.sh' script.  If you haven't already set your box to auto log in, google that part.  To setup the 'mine.sh' to startup automatically just click on the search and type in 'Startup Applications' and open it.  Create new and for the command put in (including the double quotes)

   "gnome-terminal  -e  "sudo /<full path here>/optiminer-zcash-1.6.0/mine.sh"

2). Because it is using sudo (and so does the shutdown command) you need to set your account to not require a password to run sudo.  Many online tutorials show how to bypass the password for all sudo commands but that is actually a huge security risk.  Instead you only want to open up the ones you really need.  Open a terminal window and do the following:
 
  sudo visudo -f /etc/sudoers       (NEVER use a normal editor to edit this file!)

  Add the following 3 lines in this section (change the <user> and <hostname> to what is used on your computer.  If you don't know what your hostname is type 'hostname' in a terminal window)

# Allow members of group sudo to execute any command
%sudo   ALL=(ALL:ALL) ALL
<user> <hostname> = (root) NOPASSWD: /sbin/shutdown
<user> <hostname> = (root) NOPASSWD: /<full path>/optiminer-zcash-1.6.0/mine.sh
<user> <hostname> = (root) NOPASSWD: /<full path>/optiminer-zcash-1.6.0/optiminer-zcash   (this one might not actually be needed)


3). Setup your mine.sh file that already exists in the optiminer folder if you haven't already done so.

4). In the 'watchdog-cmd.sh' file, simply uncomment the 'sudo /sbin/shutdown -r now' line.

5). Reboot your computer.  When it comes up your optiminer should start working right away in a window.  Open an additional window and type "sudo shutdown -r now"  (without the quotes) and it should reboot the computer without asking for a password.  If it does, you should be all set.

No doubt!  Claymore took forever to get that last version out so I can only assume he really struggled getting what he could out from under the hood.  I tried it out and it was basically what I was getting with optiminer so I moved back because the rate shown is what I get with opti, with claymore you have to deduct his % from what he shows you.  Optiminer works well for me.  I got the watchdog setup so that when I do have a card hanging it just reboots my rig and everything automatically starts right back up where it left off.

Your miner shouldn't control the fan anyway.  That should be controlled as a separate process.  Give me a few days and I'll try and re-write my fan controller so it's a little more robust.  I wrote one that you set a target temp for each card and it will bring the speed up or down to meet that. 

I hate to burst your bubble but news here in the US really doesn't affect the crypto coins very much.  The only news that really makes a differences is what comes out of China.   Look at last week for example.  News from China dropped the market 10% for a day and a half.   Here in the US with all the temper tantrums of anti-Trump (Clinton voters) for the last 3 months the market have continued to climb.  Only time it stumbles is on China's news.  BTC back in September was around $650 USD.  Look at it now.  Even ETH is consistently above $11 USD.  ZEC is on a constant down because of supply and demand.  There is a constant addition to the supply and, let's face it, there are very few applications for it so the demand isn't there (yet).

Not sure what the March 11th reference is to.  What happens on March 11th?  If it's something here in the US, I doubt it will make much difference on crypto.  The US is not the power house it used to be.  China is.

Sounds good.  Thanks!

I'm running Linux with the 15.12 drivers (R9 380 & 380x cards) and the Readme specifies that should be using "fgrlx 15.30.3".   Am I going to notice a difference if I spend the time to upgrade to the newer driver?   changing drivers can be such a pain that I hate to waste the time if I'm not going to really benefit from it.  I already took a big jump going from claymore's 11.1 and (knock on wood) 1.6.0 is running stable.

so is the driver upgrade worth it?

+1

I would have to agree with you on all parts of that statement.