Smartcoin Linux mining administration. [MULTI-MACHINE SUPPORT NOW IN!] - page 23.

jondecker76

full member

Activity: 238

Merit: 100

Update r393(experimental) available

Nothing too big, but I did some cleanup of the failover profiles display which makes it much easier to differentiate boundaries between profiles (especially on profiles with multiple workers)

jondecker76

full member

Activity: 238

Merit: 100

linkme:

Quote from: linkme on July 11, 2011, 05:27:28 AM

in previous versions i read you had to edit various files to get the display to line up etc. i have not tried smartcoin yet due to this fact.

I'm thinking you have SmartCoin confused with another project possibly, as there have never been files to edit (its database driven) and your descriptions so far don't sound like smartcoin at all. Either way, smartcoin is incredibly stable (my miner, and smartcoin development machine hasn't been rebooted in I can't remember how long) and getting easier to use by the day, so give it a try. I'll do what I can to help you out if there are any problems

jondecker76

full member

Activity: 238

Merit: 100

Kennel:
I have smartcoin start at boot like this on Ubuntu desktop edition:
1) Autologin enabled for my user
2) Preferences->startup applications (make entry to start 'smartcoin'

I haven't tried this, but in your script, try: (instead of exec /usr/bin/smartcoin)

Code:

su your_user -c smartcoin

i.e. my line would look like:

Code:

su jondecker76 -c smartcoin

Fletch

full member

Activity: 168

Merit: 100

I'll have a steak sandwich and a... steak sandwich

What would be the best way to have smartcoin launch on startup in Ubuntu? I imagine adding a service to /etc/init/ is the way to go, but I'm not having a lot of success. I created a script /etc/init/smartcoin.conf with the following contents:

description "Start Smartcoin"
start on runlevel [2345]
stop on runlevel [!2345]
kill timeout 30
script
LOGINUSER=miner
sleep 30
exec /usr/bin/smartcoin
end script

I based it on the examples in the Ubuntu headless mining guide: http://forum.bitcoin.org/index.php?topic=9239.0

Any idea why that doesn't work? It doesn't appear to write anything to the syslog either, so I have no idea why it doesn't work.

linkme

sr. member

Activity: 324

Merit: 250

in previous versions i read you had to edit various files to get the display to line up etc. i have not tried smartcoin yet due to this fact.

jondecker76

full member

Activity: 238

Merit: 100

linkme:
Smartcoin has never had any limit on the number of mining cards. Can you elaborate?

linkme

sr. member

Activity: 324

Merit: 250

does smartcoin support 7 mining cards out of the box yet ? or is it still default to 4 max ?

jondecker76

full member

Activity: 238

Merit: 100

Quote

This is a bit confusing during install (on Ubuntu 64 bit):

Please make sure the path below is correct, and change if necessary:
/home/miner/AMD-APP-SDK-v2.4-lnx64/lib/x86_64
/home/miner/AMD-APP-SDK-v2.4-lnx64/lib/x86

As you can see, the suggested line contains _64 at the end, but the line that you get to edit doesn't. Should I change it to _64 or not?

Edit: Also, the installer asks for en email address to which notifications are sent, but does Smartcoin actually send any notifications? If so, in which script is that done?

Yes, you need to add the _64 on 64 bit installs. I have never personally installed a 64 bit miner, and was not aware that the AMD SDK for 64 bit machines also have the 32 bit libraries. I will fix this in the near future.

The email address is a new setting but is not currently used. It will be used in the near future, however.

Quote

Why not use lockfile-progs instead, at least the package in debian is cleaner

Thanks, I will check it out- maybe it will fit the bill. Also, I had thought about making my own lockfile routines that use the atomic mkdir command. It is a good method that is pretty much 100% compatible with any distro, and requires no dependencies. I'm just not sure if A) the directory is actually created on the disk (perhaps its just cached?), and B) If so, how will it affect users running off of USB drives.
In the end, I'm beginning to kick myself for moving away from MySQL!

plantucha

newbie

Activity: 56

Merit: 0

Quote from: Rob P. on July 10, 2011, 06:53:29 PM

Quote from: plantucha on July 10, 2011, 05:46:47 PM

Quote

On my 6970's 950/300 if I set my worksize to 256 my Mhash/s goes down. I have to run at 128.

how do you underclock 950/300?

1) Are you running Catalyst 11.6? If not, then you can't over/under clock outside of the BIOS ranges without flashing.
2) Did you enable over/underclocking with:

Code:

aticonfig --od-enable --adapter=all

3) What is the output of:

Code:

aticonfig --odgc --adapter=all

1: a) yes 11.6.
b) Flashing? where I can get alternative BIOS?

2: yes

3:

Code:

 aticonfig --odgc --adapter=all

Adapter 0 - AMD Radeon HD 6700 Series
                            Core (MHz)    Memory (MHz)
           Current Clocks :    900           1050
             Current Peak :    900           1050
  Configurable Peak Range : [775-1000]     [1050-1250]
                 GPU load :    99%

Adapter 1 - AMD Radeon HD 6700 Series
                            Core (MHz)    Memory (MHz)
           Current Clocks :    900           1050
             Current Peak :    900           1050
  Configurable Peak Range : [775-1000]     [1050-1250]
                 GPU load :    99%

Adapter 2 - AMD Radeon HD 6700 Series
                            Core (MHz)    Memory (MHz)
           Current Clocks :    900           1050
             Current Peak :    900           1050
  Configurable Peak Range : [775-1000]     [1050-1250]
                 GPU load :    99%

Adapter 3 - AMD Radeon HD 6700 Series
                            Core (MHz)    Memory (MHz)
           Current Clocks :    900           1050
             Current Peak :    900           1050
  Configurable Peak Range : [775-1000]     [1050-1250]
                 GPU load :    99%

Rob P.

member

Activity: 84

Merit: 10

Quote from: plantucha on July 10, 2011, 05:46:47 PM

Quote

On my 6970's 950/300 if I set my worksize to 256 my Mhash/s goes down. I have to run at 128.

how do you underclock 950/300?

1) Are you running Catalyst 11.6? If not, then you can't over/under clock outside of the BIOS ranges without flashing.
2) Did you enable over/underclocking with:

Code:

aticonfig --od-enable --adapter=all

3) What is the output of:

Code:

aticonfig --odgc --adapter=all

plantucha

newbie

Activity: 56

Merit: 0

Quote

On my 6970's 950/300 if I set my worksize to 256 my Mhash/s goes down. I have to run at 128.

how do you underclock 950/300?

in my case:

Code:

aticonfig --od-setclocks=900,300 --adapter=all

ERROR - Set clocks failed for Adapter 0 - AMD Radeon HD 6700 Series
        Please check that input values were valid
ERROR - Set clocks failed for Adapter 1 - AMD Radeon HD 6700 Series
        Please check that input values were valid
ERROR - Set clocks failed for Adapter 2 - AMD Radeon HD 6700 Series
        Please check that input values were valid
ERROR - Set clocks failed for Adapter 3 - AMD Radeon HD 6700 Series
        Please check that input values were valid

Code:

 aticonfig --od-setclocks=900,1050 --adapter=all

Adapter 0 - AMD Radeon HD 6700 Series
            New Core Peak   : 900
            New Memory Peak : 1050

Adapter 1 - AMD Radeon HD 6700 Series
            New Core Peak   : 900
            New Memory Peak : 1050

Adapter 2 - AMD Radeon HD 6700 Series
            New Core Peak   : 900
            New Memory Peak : 1050

Adapter 3 - AMD Radeon HD 6700 Series
            New Core Peak   : 900
            New Memory Peak : 1050

plantucha

newbie

Activity: 56

Merit: 0

Quote

The worksize will affect performance depending on your memory clock generally speaking a worksize of 256 will be best with a memory clock around 300Mhz. I actually run that way because you don't need your GPU memory for much while hashing and this keeps the power consumption and heat lower.

Quote

On my 6970's 950/300 if I set my worksize to 256 my Mhash/s goes down. I have to run at 128.

GPU ATI 6790

900/1050 best worksize is 64.

it is about 1,5 Mhash/s better than 128
and 4 Mhash/s better than 256
worksize 32 is hashrate 50% down

Rob P.

member

Activity: 84

Merit: 10

Quote from: jaebird on July 10, 2011, 12:54:53 PM

I just updated... actually reinstalled! I noticed a few dependencies missing from LinuxCoin 0.2.1b

1. locate (sudo apt-get install locate)
2. lockfile (sudo apt-get install procmail, however it installs stuff you don't need as well)

@jondecker76:

Why not use lockfile-progs instead, at least the package in debian is cleaner

Thanks,
jae

I agree. Installing procmail is a big PITA because under Ubuntu, it will also install Postfix, causing the user to have to select a type of mail server.

Rob P.

member

Activity: 84

Merit: 10

Quote from: Fletch on July 10, 2011, 03:39:04 PM

This is a bit confusing during install (on Ubuntu 64 bit):

Please make sure the path below is correct, and change if necessary:
/home/miner/AMD-APP-SDK-v2.4-lnx64/lib/x86_64
/home/miner/AMD-APP-SDK-v2.4-lnx64/lib/x86

As you can see, the suggested line contains _64 at the end, but the line that you get to edit doesn't. Should I change it to _64 or not?

Edit: Also, the installer asks for en email address to which notifications are sent, but does Smartcoin actually send any notifications? If so, in which script is that done?

On a 64-bit system it finds both the 32-bit and 64-bit versions. Just delete the one you don't want to use. It's a continuous line, so backspace to the first line then set it appropriately.

Fletch

full member

Activity: 168

Merit: 100

I'll have a steak sandwich and a... steak sandwich

This is a bit confusing during install (on Ubuntu 64 bit):

Please make sure the path below is correct, and change if necessary:
/home/miner/AMD-APP-SDK-v2.4-lnx64/lib/x86_64
/home/miner/AMD-APP-SDK-v2.4-lnx64/lib/x86

As you can see, the suggested line contains _64 at the end, but the line that you get to edit doesn't. Should I change it to _64 or not?

Edit: Also, the installer asks for en email address to which notifications are sent, but does Smartcoin actually send any notifications? If so, in which script is that done?

jondecker76

full member

Activity: 238

Merit: 100

I've been having some Failover fun today, and thought i would share my results...

Normally, most people will create manual profiles in which each profile will run one instance per card to a specific pool, then assign a failover order to them. This is definitely the standard usage case, and it works great!

Just to play around today, I made 3 profiles:
TripleMineMe! (one instance on each card to my Triplemine worker)
X8SME! (once instance on each card to my X8S worker)
X8Sx2 + TripleMinex1 (one instance each on GPU[0] and GPU[1] to my X8S worker, and one instance on GPU[2] to my triplemine worker)

I then updated my failover order to:
X8Sx2 + TripleMinex1
X8SME!
TripleMineMe!
...
...
All my other profiles

Now when I run failover profile, I send hashes from 2 cards to X8S and hashes from 1 card to Triplemine. If a failover is detected (I.e. ANY of the instances are listed as DOWN)
Then it fails over to try X8S. Since the first profile had both X8S and Triplemine, then this will either run, or failover to the triplemine profile.

Basically, what a failover profile like this means is
"Hash to both X8S and Triplemine. If one of them fails, send all the hashes to the other one, but give X8S priority"
or, for the programmers out there:

Code:

if(x8s_is_up && triplemine_is_up) {
  hash_to_both
elseif(x8s_is_up)
  hash_to_x8s
else
  hash_to_triplemine
}

Just wanted to make sure people were aware that the failover and profile systems are a little more flexible and powerful than it may initially appear, and it can be fun to set up failovers like this

epg

member

Activity: 63

Merit: 10

Quote from: jondecker76 on July 10, 2011, 01:20:39 PM

Yes, I do have plans for checking for lockups like this, and in fact I've been doing some tests on the best way to do it.

On a side note, overclocking just 1-2mhz less might be enough to stop the problem all together

I had this same problem with my 5830 cards as well (stuck at 99%, not hashing). My solution was as you suggested, by pushing back the overclock until the cards were stable and didn't hang anymore.

jondecker76

full member

Activity: 238

Merit: 100

Yes, I do have plans for checking for lockups like this, and in fact I've been doing some tests on the best way to do it.

On a side note, overclocking just 1-2mhz less might be enough to stop the problem all together

jaebird

member

Activity: 79

Merit: 10

Quote from: jondecker76 on July 10, 2011, 01:01:24 PM

jaebird -

I'm still up in the air about the best lockfile method to use for now. One reason is, that I am strongly reconsidering the move to sqlite3. I'm starting to hit the point where speed limitations are going to become very apparent. I'm afraid that once multi-machine support is in, someone with 4+ machines will choke things up at the sqlite bottleneck. So the lockfile may become irrelevant if the move back to MySQL happens

I understand, using a DB like MySQL or PostgreSQL also gives access to read-only views for other types of info display aka www

On another note: sometimes my 5830's just lock up, there is no update to the status line and aticonfig still shows 99% usage. In cases like this i usually need to do a reboot to get them back. I'm wondering if you are planning on adding this type of failure detection?

Thanks,
Jae

jondecker76

full member

Activity: 238

Merit: 100

jaebird -

I'm still up in the air about the best lockfile method to use for now. One reason is, that I am strongly reconsidering the move to sqlite3. I'm starting to hit the point where speed limitations are going to become very apparent. I'm afraid that once multi-machine support is in, someone with 4+ machines will choke things up at the sqlite bottleneck. So the lockfile may become irrelevant if the move back to MySQL happens

Topic: Smartcoin Linux mining administration. [MULTI-MACHINE SUPPORT NOW IN!] - page 23. (Read 105029 times)