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

lodcrappo

hero member

Activity: 616

Merit: 506

Quote from: matthewh3 on February 24, 2012, 09:05:51 PM

Is this distro easy to use for a 'BitForce SHA256 Single' set up,

untested, but should work with cgminer mode. not as easy as most setups are.

Quote from: matthewh3 on February 24, 2012, 09:05:51 PM

also can it easily merge mine BTC, NMC and LTC on P2Pool,

p2pool requires a local wallet afaik. that is absolutely not supported on bamt, due to running on USB.

Quote from: matthewh3 on February 24, 2012, 09:05:51 PM

plus can I use the Ubuntu 'Startup Disk Creator' to put it on USB? Thanks.

Maybe, but you are on your own unless you use the recommended tools.

matthewh3

legendary

Activity: 1372

Merit: 1003

Is this distro easy to use for a 'BitForce SHA256 Single' set up, also can it easily merge mine BTC, NMC and LTC on P2Pool, plus can I use the Ubuntu 'Startup Disk Creator' to put it on USB? Thanks.

lodcrappo

hero member

Activity: 616

Merit: 506

Somebody who is having trouble with overclocking, please install fix1a and add the debug_oc option to GPU with trouble.
I can't recreate here, so need the info it provides.

Adds debugging option for GPU O/c

To enable debugging, add:

debug_oc: 1

to any GPU section in bamt.conf.

You will then see additional information whenever the O/C routine runs,
for instance when doing: mine restart

BitMinerN8

hero member

Activity: 626

Merit: 500

Mining since May 2011.

Quote from: lodcrappo on February 24, 2012, 06:41:02 PM

Quote from: BitMinerN8 on February 24, 2012, 06:38:49 PM

Quote from: lodcrappo on February 24, 2012, 06:04:05 PM

Quote from: Isokivi on February 24, 2012, 05:31:42 PM

Im back to square one: the usb-stick problem is gone.

bamt.conf wont apply overclocking, the values set are known stable clocks for this particular card. The card in question is a 5870, core voltage 1.16 core clock 970.
My workaround to this is to stop mining and run:
atitweak --set-core-voltage=1.16
atitweak --set engine-clock=970
And then restart mining.

Would you mind doing this to confirm bamt is understanding your config:

while mining, in a root shell or from ssh, type:

pcontrol

press d
press f
press enter

you will see a screen like this:

Make sure the O/C info (shaded purple in shot above, but won't be in real life) matches what you set in bamt.conf

use up down arrow to check all your GPUs

let me know

On my test rig I run pcontrol, hit d and then f and it bombs out like this.

Code:

 BAMT                                                                    miner1Exception in thread Thread-1:
 Display   GPUs   Pools   CoTraceback (most recent call last):
                                                                File "/usr/lib/python2.6/threading.py", linCurrent Pool: pit.deepbit.net
                                                          self.run()
  Hash: 305.334 Mh/s         Pools File: /etc/bamt/pools              File "/opt/bamt/pcontrolADLT.py", liPool Strategy: priority failover
   A/R: 98/0                     Kernel: phatk2f.scr.addstr(top + x,rt, ("%" + s   Rej: 0.00% "s") % " ") Kernel Params: BFI_INT VECTORS FASTLOOP=false AGG..
  Stat: got              error: addstr() returned ERR
   Que: 0/0
  Dlay: 164ms                                                            miner1
   Eff: 33.3%

pcontrol is still very alpha, not intended for normal use at all.

try making window bigger, sometimes it gets confused.

Something else that is strange, I can't use the atitweek tool:

Code:

root@miner1:~# atitweak --set-engine-clock=970
Setting performance level 0 on adapter 0: engine clock 970MHz
Setting performance level 1 on adapter 0: engine clock 970MHz
Setting performance level 2 on adapter 0: engine clock 970MHz
ADL_Overdrive5_ODPerformanceLevels_Set failed.
root@miner1:~# atitweak --set-memory-clock=300
Setting performance level 0 on adapter 0: memory clock 300MHz
Setting performance level 1 on adapter 0: memory clock 300MHz
Setting performance level 2 on adapter 0: memory clock 300MHz
ADL_Overdrive5_ODPerformanceLevels_Set failed.

lodcrappo

hero member

Activity: 616

Merit: 506

Quote from: BitMinerN8 on February 24, 2012, 06:38:49 PM

Quote from: lodcrappo on February 24, 2012, 06:04:05 PM

Quote from: Isokivi on February 24, 2012, 05:31:42 PM

Im back to square one: the usb-stick problem is gone.

bamt.conf wont apply overclocking, the values set are known stable clocks for this particular card. The card in question is a 5870, core voltage 1.16 core clock 970.
My workaround to this is to stop mining and run:
atitweak --set-core-voltage=1.16
atitweak --set engine-clock=970
And then restart mining.

Would you mind doing this to confirm bamt is understanding your config:

while mining, in a root shell or from ssh, type:

pcontrol

press d
press f
press enter

you will see a screen like this:

Make sure the O/C info (shaded purple in shot above, but won't be in real life) matches what you set in bamt.conf

use up down arrow to check all your GPUs

let me know

On my test rig I run pcontrol, hit d and then f and it bombs out like this.

Code:

 BAMT                                                                    miner1Exception in thread Thread-1:
 Display   GPUs   Pools   CoTraceback (most recent call last):
                                                                File "/usr/lib/python2.6/threading.py", linCurrent Pool: pit.deepbit.net
                                                          self.run()
  Hash: 305.334 Mh/s         Pools File: /etc/bamt/pools              File "/opt/bamt/pcontrolADLT.py", liPool Strategy: priority failover
   A/R: 98/0                     Kernel: phatk2f.scr.addstr(top + x,rt, ("%" + s   Rej: 0.00% "s") % " ") Kernel Params: BFI_INT VECTORS FASTLOOP=false AGG..
  Stat: got              error: addstr() returned ERR
   Que: 0/0
  Dlay: 164ms                                                            miner1
   Eff: 33.3%

pcontrol is still very alpha, not intended for normal use at all.

try making window bigger, sometimes it gets confused.

BitMinerN8

hero member

Activity: 626

Merit: 500

Mining since May 2011.

Quote from: lodcrappo on February 24, 2012, 06:04:05 PM

Quote from: Isokivi on February 24, 2012, 05:31:42 PM

Im back to square one: the usb-stick problem is gone.

bamt.conf wont apply overclocking, the values set are known stable clocks for this particular card. The card in question is a 5870, core voltage 1.16 core clock 970.
My workaround to this is to stop mining and run:
atitweak --set-core-voltage=1.16
atitweak --set engine-clock=970
And then restart mining.

Would you mind doing this to confirm bamt is understanding your config:

while mining, in a root shell or from ssh, type:

pcontrol

press d
press f
press enter

you will see a screen like this:

Make sure the O/C info (shaded purple in shot above, but won't be in real life) matches what you set in bamt.conf

use up down arrow to check all your GPUs

let me know

On my test rig I run pcontrol, hit d and then f and it bombs out like this.

Code:

 BAMT                                                                    miner1Exception in thread Thread-1:
 Display   GPUs   Pools   CoTraceback (most recent call last):
                                                                File "/usr/lib/python2.6/threading.py", linCurrent Pool: pit.deepbit.net
                                                          self.run()
  Hash: 305.334 Mh/s         Pools File: /etc/bamt/pools              File "/opt/bamt/pcontrolADLT.py", liPool Strategy: priority failover
   A/R: 98/0                     Kernel: phatk2f.scr.addstr(top + x,rt, ("%" + s   Rej: 0.00% "s") % " ") Kernel Params: BFI_INT VECTORS FASTLOOP=false AGG..
  Stat: got              error: addstr() returned ERR
   Que: 0/0
  Dlay: 164ms                                                            miner1
   Eff: 33.3%

lodcrappo

hero member

Activity: 616

Merit: 506

Quote from: Isokivi on February 24, 2012, 05:31:42 PM

Im back to square one: the usb-stick problem is gone.

bamt.conf wont apply overclocking, the values set are known stable clocks for this particular card. The card in question is a 5870, core voltage 1.16 core clock 970.
My workaround to this is to stop mining and run:
atitweak --set-core-voltage=1.16
atitweak --set engine-clock=970
And then restart mining.

Would you mind doing this to confirm bamt is understanding your config:

while mining, in a root shell or from ssh, type:

pcontrol

press d
press f
press enter

you will see a screen like this:

Make sure the O/C info (shaded purple in shot above, but won't be in real life) matches what you set in bamt.conf

use up down arrow to check all your GPUs

let me know

lodcrappo

hero member

Activity: 616

Merit: 506

Quote from: cuz0882 on February 24, 2012, 08:26:56 AM

I just tried this out for the first time tonight, the hash rate is really low though. Is there a guide to get cgminer running with it? I'm assuming the mining software is the reason for hash rate.. It's only giving 330 hash's per gpu. (5970's with 850 clocks)

Phoenix will give you at least the same and usually a better hashrate, better stales, and more shares accepted per minute (the only stat that actually matters) than cgminer. Not to mention its much more stable.

The only reason to use cgminer is if you must have autofan or you must have it's pool management, and are willing to give up phoenix's advantages in return for those.

Soon, phoenix will have those things also, either in phoenix 2 or from BAMT's own modifications in pcontrol. We actually have autofan and autogpu implemented for phoenix, but I'm holding off to see where phoenix 2 will end up. one way or the other, eventually phoenix will become the only miner needed in bamt.

As for your low rates, there may be a bug with overclocking. I am looking into it.

lodcrappo

hero member

Activity: 616

Merit: 506

All the o/c settings in bamt.conf do is construct the atitweak command for you. If it works with atitweak manually, it should work when bamt runs atitweak for you.
I will look into it.

gnar1ta$

donator

Activity: 798

Merit: 500

Quote from: Isokivi on February 24, 2012, 05:31:42 PM

Im back to square one: the usb-stick problem is gone.

bamt.conf wont apply overclocking, the values set are known stable clocks for this particular card. The card in question is a 5870, core voltage 1.16 core clock 970.
My workaround to this is to stop mining and run:
atitweak --set-core-voltage=1.16
atitweak --set engine-clock=970
And then restart mining.

If that works just add it to bamt.conf as a post oc command for the gpu and comment out the rest.

Code:

post_oc_cmd: /usr/local/bin/atitweak -e 970 -v 1.16 -A <#>

I never use the oc and fan commands just did it all that way. You can add -f and -m also. It will set all profile levels so make sure they are sane clocks.

Isokivi

hero member

Activity: 910

Merit: 1000

Items flashing here available at btctrinkets.com

Im back to square one: the usb-stick problem is gone.

bamt.conf wont apply overclocking, the values set are known stable clocks for this particular card. The card in question is a 5870, core voltage 1.16 core clock 970.
My workaround to this is to stop mining and run:
atitweak --set-core-voltage=1.16
atitweak --set engine-clock=970
And then restart mining.

BitMinerN8

hero member

Activity: 626

Merit: 500

Mining since May 2011.

Quote from: Isokivi on February 24, 2012, 05:09:16 PM

Quote from: BitMinerN8 on February 24, 2012, 05:03:43 PM

Quote from: Isokivi on February 24, 2012, 04:57:22 PM

And now it would appear that coldreboot killed my usb-stick.

Unplug and re-insert. See if that helps. I have that happen sometimes on a few rigs.

Did that using a different usb port, that did not resolve it.

I fixed one that would not come back by putting in a windows system, did a full format (not quick) and then restored the image on it again. It's been working for weeks after that. YMMV

Isokivi

hero member

Activity: 910

Merit: 1000

Items flashing here available at btctrinkets.com

Quote from: BitMinerN8 on February 24, 2012, 05:03:43 PM

Quote from: Isokivi on February 24, 2012, 04:57:22 PM

And now it would appear that coldreboot killed my usb-stick.

Unplug and re-insert. See if that helps. I have that happen sometimes on a few rigs.

Did that using a different usb port, that did not resolve it.

BitMinerN8

hero member

Activity: 626

Merit: 500

Mining since May 2011.

Quote from: Isokivi on February 24, 2012, 04:57:22 PM

And now it would appear that coldreboot killed my usb-stick.

Unplug and re-insert. See if that helps. I have that happen sometimes on a few rigs.

Isokivi

hero member

Activity: 910

Merit: 1000

Items flashing here available at btctrinkets.com

And now it would appear that coldreboot killed my usb-stick.
edit: Rewriting bamt to the stick atm
edit2: manages to boot up, stick is not dead.

Isokivi

hero member

Activity: 910

Merit: 1000

Items flashing here available at btctrinkets.com

Quote from: gnar1ta$ on February 24, 2012, 04:35:19 PM

Quote from: BitMinerN8 on February 24, 2012, 04:08:00 PM

Quote from: Isokivi on February 24, 2012, 03:35:05 PM

Trying to set this up on rig#1

Problems so far: I cant get any overclocking in with bamt.conf. I was able to do some overclocking with AMDOverdrive Ctrl, but Im nowhere near what this particular card can do, it wont let me push the core clock past 900Mhz. I have set up all (3) the core_speeds at 970Mhz, tried only setting one dosent seem to make any difference.

Other than that everything looks fine.

I have been having issues too. What does it say on your http://YourMinerIP/ compared to what you set in bamt.conf? On my (3) 5850 GPU test rig that was doing 1120 Mhash/s under 0.4 is doing around 860 Mhash/s on 0.5 no matter what I put in for the 3 core_speed_X or mem_speed_X, it's like stock speeds only.

I'm going to try another single 5850 GPU rig now.

Have you checked that oc hasn't been disabled by mother? Not running .5 yet but I'd think this would be included https://bitcointalksearch.org/topic/m.755770

Nope the file mother creates is not there.

BitMinerN8

hero member

Activity: 626

Merit: 500

Mining since May 2011.

Quote from: gnar1ta$ on February 24, 2012, 04:35:19 PM

Quote from: BitMinerN8 on February 24, 2012, 04:08:00 PM

Quote from: Isokivi on February 24, 2012, 03:35:05 PM

Trying to set this up on rig#1

Problems so far: I cant get any overclocking in with bamt.conf. I was able to do some overclocking with AMDOverdrive Ctrl, but Im nowhere near what this particular card can do, it wont let me push the core clock past 900Mhz. I have set up all (3) the core_speeds at 970Mhz, tried only setting one dosent seem to make any difference.

Other than that everything looks fine.

I have been having issues too. What does it say on your http://YourMinerIP/ compared to what you set in bamt.conf? On my (3) 5850 GPU test rig that was doing 1120 Mhash/s under 0.4 is doing around 860 Mhash/s on 0.5 no matter what I put in for the 3 core_speed_X or mem_speed_X, it's like stock speeds only.

I'm going to try another single 5850 GPU rig now.

Have you checked that oc hasn't been disabled by mother? Not running .5 yet but I'd think this would be included https://bitcointalksearch.org/topic/m.755770

I confirmed the ACTIVE folder is empty.

On my single GPU 5850 on 0.5 i'm getting 305 Mhash/s.
On munin status page it shows Core 765 Mhz - Memory 1000 Mhz - Power 1.088v

Code:

gpu0:
  core_speed_0: 300
  core_speed_1: 800
  core_speed_2: 955
  
  mem_speed_0: 300
  mem_speed_1: 300
  mem_speed_2: 300

  core_voltage_0: 1.125
  core_voltage_1: 1.125
  core_voltage_2: 1.125000

On the same single GPU 5850 on 0.4 i'm getting 402 Mhash/s.
On munin status page it shows Core 970 Mhz - Memory 300 Mhz - Power 1.088v

Code:

gpu0:
  core_speed: 970
  mem_speed: 300
  fan_speed: 85
  kernel: phatk2

gnar1ta$

donator

Activity: 798

Merit: 500

Quote from: BitMinerN8 on February 24, 2012, 04:08:00 PM

Quote from: Isokivi on February 24, 2012, 03:35:05 PM

Trying to set this up on rig#1

Problems so far: I cant get any overclocking in with bamt.conf. I was able to do some overclocking with AMDOverdrive Ctrl, but Im nowhere near what this particular card can do, it wont let me push the core clock past 900Mhz. I have set up all (3) the core_speeds at 970Mhz, tried only setting one dosent seem to make any difference.

Other than that everything looks fine.

I have been having issues too. What does it say on your http://YourMinerIP/ compared to what you set in bamt.conf? On my (3) 5850 GPU test rig that was doing 1120 Mhash/s under 0.4 is doing around 860 Mhash/s on 0.5 no matter what I put in for the 3 core_speed_X or mem_speed_X, it's like stock speeds only.

I'm going to try another single 5850 GPU rig now.

Have you checked that oc hasn't been disabled by mother? Not running .5 yet but I'd think this would be included https://bitcointalksearch.org/topic/m.755770

Isokivi

hero member

Activity: 910

Merit: 1000

Items flashing here available at btctrinkets.com

I found a workaround to the problem, but it's not pretty:
in root terminal: atitweak --set-core-voltage 1,16
(thats the card's stock voltage)
and: atitweak --set-engine-clock=970

Hashing away at normal rate now.

I'd still like to find out why I can only control the fanspeed from bamt.conf

BitMinerN8

hero member

Activity: 626

Merit: 500

Mining since May 2011.

Quote from: Isokivi on February 24, 2012, 03:35:05 PM

Trying to set this up on rig#1

Problems so far: I cant get any overclocking in with bamt.conf. I was able to do some overclocking with AMDOverdrive Ctrl, but Im nowhere near what this particular card can do, it wont let me push the core clock past 900Mhz. I have set up all (3) the core_speeds at 970Mhz, tried only setting one dosent seem to make any difference.

Other than that everything looks fine.

I have been having issues too. What does it say on your http://YourMinerIP/ compared to what you set in bamt.conf? On my (3) 5850 GPU test rig that was doing 1120 Mhash/s under 0.4 is doing around 860 Mhash/s on 0.5 no matter what I put in for the 3 core_speed_X or mem_speed_X, it's like stock speeds only.

I'm going to try another single 5850 GPU rig now.

Topic: BAMT version 0.5 - Easy USB based mining Linux with farm wide management tools - page 78. (Read 324169 times)