BAMT version 0.5 - Easy USB based mining Linux with farm wide management tools

[Red Emerald]

yes sorry cgminer, and no the hash rate is now lower

Is cgminer setting your clocks?

Posting logs and your config would be helpful.

[boozer]

Hey Guys,

Trying to get CGI miner to work, Looks like everything is set up and running, however I noticed that the load it usually around 70-80%. Before I switched to CGI, my load on my GPU would always be 99%. Any ideas?

What cards and intensity are you running in cgminer?  You might try setting a higher intensity to see if that increases GPU load.

[mmartoccia]

Hey guys, looking to further optimize my 5970 rig.  I was completely stable prior to the 0.5 release and now having to reboot my box twice daily to keep the cards from faulting.  I was pulling about 330 MHx2 and was hoping someone else who is using a similar card could share an idea or two on what I could to to push up the limit some.   I've also noticed that my second GPU's Mem is clocking at 1000 Mhz when I've told it to stay at 175.  Am I doing something stupid?

Here's my current configuration:

Code:

gpu0:
  disabled: 0
  # optional command to execute prior to overclocking
  pre_oc_cmd: /etc/init.d/munin-node restart

  #overclocking.. all optional 955/830
  fan_speed: 100
  core_speed_0: 730
  core_speed_1: 730
  core_speed_2: 730
  mem_speed_0: 175
  mem_speed_1: 175
  mem_speed_2: 175
  # core_voltage_0: 1.125
  # core_voltage_1: 1.125
  # core_voltage_2: 1.125000

  # optional command to execute after overclocking
  post_oc_cmd:

  # kernel to use.. currently one of:  phatk phatk2 phatk-bamt04 phatk-svn phatk-1.50 poclbm
  kernel: phatk2
  # phoenix style kernel params.  do not include DEVICE=x
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=13 WORKSIZE=128

  # file containing pool URLs
  pool_file: /etc/bamt/pools
  # default time to allow phoenix to run without finding a share.. exceed this and we move to next pool in poolfile
  pool_timeout: 180

  # monitoring values, used by email alerts and gpumon
  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_fan_lo: 2000
  monitor_reject_hi: 2

gpu1:
  disabled: 0
  # optional command to execute prior to overclocking
  pre_oc_cmd:

  #overclocking.. all optional
  # fan_speed: 80
  core_speed_0: 730
  core_speed_1: 730
  core_speed_2: 730
  mem_speed_0: 175
  mem_speed_1: 175
  mem_speed_2: 175
  # core_voltage_0: 1.088
  # core_voltage_1: 1.088
  # core_voltage_2: 1.088

  # optional command to execute after overclocking
  post_oc_cmd:

  # kernel to use.. currently one of:  phatk phatk2 phatk-bamt04 phatk-svn phatk-1.50 poclbm
  kernel: phatk2
  # phoenix style kernel params.  do not include DEVICE=x
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=13 WORKSIZE=128

  # file containing pool URLs
  pool_file: /etc/bamt/pools
  # default time to allow phoenix to run without finding a share.. exceed this and we move to next pool in poolfile
  pool_timeout: 180

  # monitoring values, used by email alerts and gpumon
  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_fan_lo: 2000
  monitor_reject_hi: 2

[Isokivi]

Hey guys, looking to further optimize my 5970 rig.  I was completely stable prior to the 0.5 release and now having to reboot my box twice daily to keep the cards from faulting.  I was pulling about 330 MHx2 and was hoping someone else who is using a similar card could share an idea or two on what I could to to push up the limit some.   I've also noticed that my second GPU's Mem is clocking at 1000 Mhz when I've told it to stay at 175.  Am I doing something stupid?

Here's my current configuration:

Code:

gpu0:
  disabled: 0
  # optional command to execute prior to overclocking
  pre_oc_cmd: /etc/init.d/munin-node restart

  #overclocking.. all optional 955/830
  fan_speed: 100
  core_speed_0: 730
  core_speed_1: 730
  core_speed_2: 730
  mem_speed_0: 175
  mem_speed_1: 175
  mem_speed_2: 175
  # core_voltage_0: 1.125
  # core_voltage_1: 1.125
  # core_voltage_2: 1.125000

  # optional command to execute after overclocking
  post_oc_cmd:

  # kernel to use.. currently one of:  phatk phatk2 phatk-bamt04 phatk-svn phatk-1.50 poclbm
  kernel: phatk2
  # phoenix style kernel params.  do not include DEVICE=x
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=13 WORKSIZE=128

  # file containing pool URLs
  pool_file: /etc/bamt/pools
  # default time to allow phoenix to run without finding a share.. exceed this and we move to next pool in poolfile
  pool_timeout: 180

  # monitoring values, used by email alerts and gpumon
  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_fan_lo: 2000
  monitor_reject_hi: 2

gpu1:
  disabled: 0
  # optional command to execute prior to overclocking
  pre_oc_cmd:

  #overclocking.. all optional
  # fan_speed: 80
  core_speed_0: 730
  core_speed_1: 730
  core_speed_2: 730
  mem_speed_0: 175
  mem_speed_1: 175
  mem_speed_2: 175
  # core_voltage_0: 1.088
  # core_voltage_1: 1.088
  # core_voltage_2: 1.088

  # optional command to execute after overclocking
  post_oc_cmd:

  # kernel to use.. currently one of:  phatk phatk2 phatk-bamt04 phatk-svn phatk-1.50 poclbm
  kernel: phatk2
  # phoenix style kernel params.  do not include DEVICE=x
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=13 WORKSIZE=128

  # file containing pool URLs
  pool_file: /etc/bamt/pools
  # default time to allow phoenix to run without finding a share.. exceed this and we move to next pool in poolfile
  pool_timeout: 180

  # monitoring values, used by email alerts and gpumon
  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_fan_lo: 2000
  monitor_reject_hi: 2

Im propably the biggest noob who dares give advice here so you might want to wait for confirmation but to me it seems that your feeding stock voltage to a highly underclocked card. It may or may not be the source of your problems, but either way I'd lower the core voltage.

[DeathAndTaxes]

Im propably the biggest noob who dares give advice here so you might want to wait for confirmation but to me it seems that your feeding stock voltage to a highly underclocked card. It may or may not be the source of your problems, but either way I'd lower the core voltage.

Core isn't underclocked.  Stock for 5970 is 725.

[mmartoccia]

Im propably the biggest noob who dares give advice here so you might want to wait for confirmation but to me it seems that your feeding stock voltage to a highly underclocked card. It may or may not be the source of your problems, but either way I'd lower the core voltage.

Core isn't underclocked.  Stock for 5970 is 725.

Thanks guys - here is my corresponding BAMT dashboard:

http://i44.tinypic.com/28t976g.png

[nathanghart]

Im propably the biggest noob who dares give advice here so you might want to wait for confirmation but to me it seems that your feeding stock voltage to a highly underclocked card. It may or may not be the source of your problems, but either way I'd lower the core voltage.

Core isn't underclocked.  Stock for 5970 is 725.

Thanks guys - here is my corresponding BAMT dashboard:

Do a search in this thread for "Mother" you will see why your card is at 725 and 1000.

Also, you may want to reconsider 100% fan...unless you enjoy replacing fans every few months.

Finally, about the comment above....the # in front of a line means that line is ignored so....# core_voltage_2: 1.125000 would not change the core voltage. It would do nothing until the # is removed.

[mmartoccia]

Im propably the biggest noob who dares give advice here so you might want to wait for confirmation but to me it seems that your feeding stock voltage to a highly underclocked card. It may or may not be the source of your problems, but either way I'd lower the core voltage.

Core isn't underclocked.  Stock for 5970 is 725.

Thanks guys - here is my corresponding BAMT dashboard:

http://i44.tinypic.com/28t976g.png

Do a search in this thread for "Mother" you will see why your card is at 725 and 1000.

Also, you may want to reconsider 100% fan...unless you enjoy replacing fans every few months.

Finally, about the comment above....the # in front of a line means that line is ignored so....# core_voltage_2: 1.125000 would not change the core voltage. It would do nothing until the # is removed.

Thanks for the tip Isokivi! I've deleted the file /live/image/BAMT/CONTROL/ACTIVE/noOCx and my Mem is now back to normal 175 Mhz speed.  Other than that, are there some clocks I should try to get my performance up with minimal compromises?

[boozer]

Thanks for the tip Isokivi! I've deleted the file /live/image/BAMT/CONTROL/ACTIVE/noOCx and my Mem is now back to normal 175 Mhz speed.  Other than that, are there some clocks I should try to get my performance up with minimal compromises?

Aggressive way:
I run mine and make sure they are stable at stock gpu speeds with mem underclock for a day or two.  After that I try running at 800 MHz gpu clock.  Out of 6 cards (12 cores) only two cores could not run 800 MHz (they run at 790 and 795 MHz just fine).  My other 9 cores run between 800 and 855 at stock voltage... I have one "magic core" that is stable at 880MHz at stock voltage.  If 800 MHz fails during the next day, i decrease that core(s) by 10 MHz, if it succeeds, I increase by 25 MHz, until they fail, then decrease by 10 MHz until they run stable.  I recommend you do it while you have the ability to reboot the machine to minimize downtime.  You can get pretty close to stable OC's in a few days with the only downtime being a few minutes while you reboot (if/when needed).

Safe way:
Increase clocks by 10 MHz and let run for a day... then repeat.  Takes longer to find stable OC's, but allows for higher uptime, especially if you are not going to be near the rigs.  I did all my rigs the aggressive way, but had to revert to the safe way on one of my rigs as one cards OC was causing others to lock and I would change the OC on the wrong card... isolated issue from what I hear, but the safe way helps eliminate issues like that.

I had stability issues with my mem at 175 on my 5970's, so I run at mem of 190... something to consider... I got all my OC's stable at 310 mem, then ran 190 for about a week... then tried 175 and had issues, so I moved it back to 190... not sure if thats just card specific or what... but I didn't spend much time on it as the difference is negligible at that low of speeds anyways.

Also, earlier in this thread is a post by lodcrappo about OC'ing eating into your profits, you might want to go read that as he has some numbers about how much ROI you get for overclocking and hours of downtime don't make up for a small overclock increase... Its a good thing to read and consider while you are looking for stable clocks.

I run everything with air cooling and no overvolting, so YMMV depending on your setup.

[Joshwaa]

Are 7970's supported in 0.5c?

[nathanghart]

Thanks for the tip Isokivi! I've deleted the file /live/image/BAMT/CONTROL/ACTIVE/noOCx and my Mem is now back to normal 175 Mhz speed.  Other than that, are there some clocks I should try to get my performance up with minimal compromises?

You are thanking him for useless and incorrect advice? According to your posts and config, you were not overvolting or underclocking as he suggested and he told you to change a commented line while leaving it commented....hmph. 

BTW, no offense Isokivi, you did warn him about your knowledge level. I fully support your efforts to try and help him.

[boozer]

Are 7970's supported in 0.5c?

They are not supported "out of the box" in 0.5c, but I got 7970's working by doing the following:

Starting with a fresh install of bamt 0.5b (later versions should work i would assume).

• X does not start on first boot.  Have to manually type startx and it loads desktop.  Desktop says no usable gpus are detected.
  I start a root terminal and change root password.
  
  
• Remove previous version of flgrx (from https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver)
  sudo /usr/share/ati/fglrx-uninstall.sh --force
  coldreboot
  
  
• download new 7970 drivers:
  https://bitcointalk.org/index.php?topic=61987.0
  
  
• chmod +x amd-driver....run file to make it executable
  
  
• execute the driver install file
  /home/user/Downloads/amd-driver....run
  file to install drivers.
  
  
• coldreboot
  
  
• 7900 series detected... start mining with cgminer.

EDIT:  One person I was trying to assist could not get his 7970's to work, even following my method above... However I have done several fresh installs (to verify) and its worked every time for me.  I have 2 rigs running 7970's only.  They each have 3 x 7970's and work just fine for me on BAMT with this method.

[Joshwaa]

Thanks I will try that later!

[jamesg]

Are 7970's supported in 0.5c?

They are not supported "out of the box" in 0.5c, but I got 7970's working by doing the following:

Starting with a fresh install of bamt 0.5b (later versions should work i would assume).

• X does not start on first boot.  Have to manually type startx and it loads desktop.  Desktop says no usable gpus are detected.
  I start a root terminal and change root password.
  
  
• Remove previous version of flgrx (from https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver)
  sudo /usr/share/ati/fglrx-uninstall.sh --force
  coldreboot
  
  
• download new 7970 drivers:
  https://bitcointalk.org/index.php?topic=61987.0
  
  
• chmod +x amd-driver....run file to make it executable
  
  
• execute the driver install file
  /home/user/Downloads/amd-driver....run
  file to install drivers.
  
  
• coldreboot
  
  
• 7900 series detected... start mining with cgminer.

Holyshit! Good to know.

* gigavps starts plotting a purchase of 7970s.......

[Red Emerald]

Hey guys, looking to further optimize my 5970 rig.  I was completely stable prior to the 0.5 release and now having to reboot my box twice daily to keep the cards from faulting.  I was pulling about 330 MHx2 and was hoping someone else who is using a similar card could share an idea or two on what I could to to push up the limit some.   I've also noticed that my second GPU's Mem is clocking at 1000 Mhz when I've told it to stay at 175.  Am I doing something stupid?

Here's my current configuration:

Code:

gpu0:
  disabled: 0
  # optional command to execute prior to overclocking
  pre_oc_cmd: /etc/init.d/munin-node restart

  #overclocking.. all optional 955/830
  fan_speed: 100
  core_speed_0: 730
  core_speed_1: 730
  core_speed_2: 730
  mem_speed_0: 175
  mem_speed_1: 175
  mem_speed_2: 175
  # core_voltage_0: 1.125
  # core_voltage_1: 1.125
  # core_voltage_2: 1.125000

  # optional command to execute after overclocking
  post_oc_cmd:

  # kernel to use.. currently one of:  phatk phatk2 phatk-bamt04 phatk-svn phatk-1.50 poclbm
  kernel: phatk2
  # phoenix style kernel params.  do not include DEVICE=x
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=13 WORKSIZE=128

  # file containing pool URLs
  pool_file: /etc/bamt/pools
  # default time to allow phoenix to run without finding a share.. exceed this and we move to next pool in poolfile
  pool_timeout: 180

  # monitoring values, used by email alerts and gpumon
  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_fan_lo: 2000
  monitor_reject_hi: 2

gpu1:
  disabled: 0
  # optional command to execute prior to overclocking
  pre_oc_cmd:

  #overclocking.. all optional
  # fan_speed: 80
  core_speed_0: 730
  core_speed_1: 730
  core_speed_2: 730
  mem_speed_0: 175
  mem_speed_1: 175
  mem_speed_2: 175
  # core_voltage_0: 1.088
  # core_voltage_1: 1.088
  # core_voltage_2: 1.088

  # optional command to execute after overclocking
  post_oc_cmd:

  # kernel to use.. currently one of:  phatk phatk2 phatk-bamt04 phatk-svn phatk-1.50 poclbm
  kernel: phatk2
  # phoenix style kernel params.  do not include DEVICE=x
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=13 WORKSIZE=128

  # file containing pool URLs
  pool_file: /etc/bamt/pools
  # default time to allow phoenix to run without finding a share.. exceed this and we move to next pool in poolfile
  pool_timeout: 180

  # monitoring values, used by email alerts and gpumon
  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_fan_lo: 2000
  monitor_reject_hi: 2

Im propably the biggest noob who dares give advice here so you might want to wait for confirmation but to me it seems that your feeding stock voltage to a highly underclocked card. It may or may not be the source of your problems, but either way I'd lower the core voltage.

As mentioned multiple times in this thread, do not change profiles 0 and 1 unless you need to.   You can cause instability by OCing the lower profiles. Profile 2 is what is used during mining.

[Joshwaa]

Are 7970's supported in 0.5c?

They are not supported "out of the box" in 0.5c, but I got 7970's working by doing the following:

Starting with a fresh install of bamt 0.5b (later versions should work i would assume).

• X does not start on first boot.  Have to manually type startx and it loads desktop.  Desktop says no usable gpus are detected.
  I start a root terminal and change root password.
  
  
• Remove previous version of flgrx (from https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver)
  sudo /usr/share/ati/fglrx-uninstall.sh --force
  coldreboot
  
  
• download new 7970 drivers:
  https://bitcointalk.org/index.php?topic=61987.0
  
  
• chmod +x amd-driver....run file to make it executable
  
  
• execute the driver install file
  /home/user/Downloads/amd-driver....run
  file to install drivers.
  
  
• coldreboot
  
  
• 7900 series detected... start mining with cgminer.

Holyshit! Good to know.

* gigavps starts plotting a purchase of 7970s.......

No don't wait a week for the 7990's to come out.. much more worth the money. 1.3Ghash per card cost 849.99

Thats why I am selling of a lot of my 5 series and 7970's

[lodcrappo]

Hey guys, looking to further optimize my 5970 rig.  I was completely stable prior to the 0.5 release and now having to reboot my box twice daily to keep the cards from faulting.  I was pulling about 330 MHx2 and was hoping someone else who is using a similar card could share an idea or two on what I could to to push up the limit some.   I've also noticed that my second GPU's Mem is clocking at 1000 Mhz when I've told it to stay at 175.  Am I doing something stupid?

Here's my current configuration:

Code:

gpu0:
  disabled: 0
  # optional command to execute prior to overclocking
  pre_oc_cmd: /etc/init.d/munin-node restart

  #overclocking.. all optional 955/830
  fan_speed: 100
  core_speed_0: 730
  core_speed_1: 730
  core_speed_2: 730
  mem_speed_0: 175
  mem_speed_1: 175
  mem_speed_2: 175
  # core_voltage_0: 1.125
  # core_voltage_1: 1.125
  # core_voltage_2: 1.125000

  # optional command to execute after overclocking
  post_oc_cmd:

  # kernel to use.. currently one of:  phatk phatk2 phatk-bamt04 phatk-svn phatk-1.50 poclbm
  kernel: phatk2
  # phoenix style kernel params.  do not include DEVICE=x
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=13 WORKSIZE=128

  # file containing pool URLs
  pool_file: /etc/bamt/pools
  # default time to allow phoenix to run without finding a share.. exceed this and we move to next pool in poolfile
  pool_timeout: 180

  # monitoring values, used by email alerts and gpumon
  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_fan_lo: 2000
  monitor_reject_hi: 2

gpu1:
  disabled: 0
  # optional command to execute prior to overclocking
  pre_oc_cmd:

  #overclocking.. all optional
  # fan_speed: 80
  core_speed_0: 730
  core_speed_1: 730
  core_speed_2: 730
  mem_speed_0: 175
  mem_speed_1: 175
  mem_speed_2: 175
  # core_voltage_0: 1.088
  # core_voltage_1: 1.088
  # core_voltage_2: 1.088

  # optional command to execute after overclocking
  post_oc_cmd:

  # kernel to use.. currently one of:  phatk phatk2 phatk-bamt04 phatk-svn phatk-1.50 poclbm
  kernel: phatk2
  # phoenix style kernel params.  do not include DEVICE=x
  kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=13 WORKSIZE=128

  # file containing pool URLs
  pool_file: /etc/bamt/pools
  # default time to allow phoenix to run without finding a share.. exceed this and we move to next pool in poolfile
  pool_timeout: 180

  # monitoring values, used by email alerts and gpumon
  monitor_temp_lo: 45
  monitor_temp_hi: 80
  monitor_load_lo: 80
  monitor_hash_lo: 125
  monitor_fan_lo: 2000
  monitor_reject_hi: 2

Im propably the biggest noob who dares give advice here so you might want to wait for confirmation but to me it seems that your feeding stock voltage to a highly underclocked card. It may or may not be the source of your problems, but either way I'd lower the core voltage.

As mentioned multiple times in this thread, do not change profiles 0 and 1 unless you need to.   You can cause instability by OCing the lower profiles. Profile 2 is what is used during mining.

[lodcrappo]

Also, you may want to reconsider 100% fan...unless you enjoy replacing fans every few months.

No.

Running fan at 100% is fine.  Changing its speed a lot can in fact lead to premature failure.  Best to set it at some large value and leave alone.

[rjk]

Also, you may want to reconsider 100% fan...unless you enjoy replacing fans every few months.

No.

Running fan at 100% is fine.  Changing its speed a lot can in fact lead to premature failure.  Best to set it at some large value and leave alone.

My aching and dying fans have told me otherwise in the past.

[lodcrappo]

Also, you may want to reconsider 100% fan...unless you enjoy replacing fans every few months.

No.

Running fan at 100% is fine.  Changing its speed a lot can in fact lead to premature failure.  Best to set it at some large value and leave alone.

My aching and dying fans have told me otherwise in the past.

I suppose you did an exhaustive study with a large control group of fans not set to 100, compared to a large set of samples with fan set to 100?
Because I did..  and found the fans most likely to die were those on "auto" where they varied in speed.  In fact none of the fans set to 100, 85 or 50 had any failures at all.