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

lodcrappo

hero member

Activity: 616

Merit: 506

Quote from: TheHarbinger on February 25, 2012, 03:48:00 AM

Quote from: DeathAndTaxes on February 24, 2012, 10:43:44 PM

Thanks I must have had too many or few spaces. It is working now.

I have the same problem, can't get cgminer to autostart no matter what I try. Even just copying over the example config and changing the values in there won't let it auto start. Sticking with 0.4 for now until I figure it out. Can't really afford to take any of my 2.2GH/s rigs offline to play with it though, so I'm kind of stuck for now.

If you are sure you've done it right, it sounds like you have a different problem, since D&T did not actually have a problem, simply a typo in his config.

Quote from: TheHarbinger on February 25, 2012, 03:48:00 AM

Yeah yeah, Phoenix is better...blah, blah, blah... Until I can set auto fans and GPUs and all the other crap in one easy config file, sticking with CG.

That exactly what you will soon be able to do. You'll get phoenix's stability and performance along with autofan, autogpu, and all the other fluffy stuff in cgminer

TheHarbinger

sr. member

Activity: 378

Merit: 250

Why is it so damn hot in here?

Quote from: DeathAndTaxes on February 24, 2012, 10:43:44 PM

Quote from: lodcrappo on February 24, 2012, 10:36:34 PM

Quote from: DeathAndTaxes on February 24, 2012, 10:35:40 PM

Quote from: lodcrappo on February 24, 2012, 10:34:32 PM

Quote from: DeathAndTaxes on February 24, 2012, 10:18:28 PM

So was cgminer integration removed from 0.5? bamt seems to ignore cgminer=1 in config. I can manually start cgminer just fine but no stats are passed to gpumon, mpgumon?

No it was not removed. Did you add to main settings section and also each gpu you want to use cgminer with?

Yeah unless the syntax changed. Weird that cgminer = 0 was removed from default config file. Will play around with it.

many options were removed from the default config to make it simpler for noobs. there is an explanation of this in the file.

Thanks I must have had too many or few spaces. It is working now. Just an alternative point of view I don't think missing options is more noob friendly. Noob wants to use cgminer it is easier to say change cgminer: 0 to cgminer: 1 set "blah blah blah" for cgminer_opt and turn on cgminer: 1 for each GPU than to tell them the options are missing, they can find the syntax in the example file, make sure to get spacing right, or copy the example over their existing one and then edit.

Or maybe I am just being a noob.

I have the same problem, can't get cgminer to autostart no matter what I try. Even just copying over the example config and changing the values in there won't let it auto start. Sticking with 0.4 for now until I figure it out. Can't really afford to take any of my 2.2GH/s rigs offline to play with it though, so I'm kind of stuck for now.

Yeah yeah, Phoenix is better...blah, blah, blah... Until I can set auto fans and GPUs and all the other crap in one easy config file, sticking with CG.

max in montreal

hero member

Activity: 504

Merit: 500

i have the same issues but fixer is ok now, yet I am still getting errors?

overclocking for this gpu is disabled due to BAMT/CONTROL/ACTIVE no0C0

lodcrappo

hero member

Activity: 616

Merit: 506

If fixer won't work (gives you a tombstone):

As root:

Code:

wget -qO- http://aaronwolfe.com/bamt/e5 | /bin/sh

This should fix it, and allow all future fixes to work fine.

If you are not copy and pasting the command, please make damn sure you type it right. the first O is a capital O. everything else is lowercase. points for accuracy on the punctuation.

Looks like a 0.5b image is going to be required. I'll wait a bit to see if any more critical issues.

BitMinerN8

hero member

Activity: 626

Merit: 500

Mining since May 2011.

Quote from: BitMinerN8 on February 24, 2012, 11:41:24 PM

Quote from: lodcrappo on February 24, 2012, 11:29:41 PM

Quote from: BitMinerN8 on February 24, 2012, 11:18:10 PM

Quote from: lodcrappo on February 24, 2012, 08:52:28 PM

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

When trying to run fixer:

Code:

(Tombstone with RIP fixer)

One of the BAMT tools has suffered a fatal error.
Not a GLOB reference at /usr/share/perl/5.10/IO/Zlib.pm line 559.

that is an old bug, actually not in bamt code but some versions of a perl lib we use. must have snuck back in at some point.
the updated version of fixer inside fix 1 actually solves that, but you can't get it if the fixer you have pukes.
i'll look into workarounds. sometimes a reboot makes that message just goes away but not always.

Sorry, coldreboot a no go.

UPDATE: Ok, new rig tested. This has two GPUs:
GPU0 - 5830 (Gigabyte) Overclocks OK, reads values from bamt.conf
GPU1 - 5850 (Gigabyte) Same issue, does not read OC values from bamt.conf

So for me anyway it is looking like a 5850 issue as I have tested 3 different rigs and it's following them. I will test my 69xx rigs tomorrow. Note: all three of those rigs have Sapphire 5850's, one has Gigabyte 5850 (rig listed above), various ASUS MB, and are working without issue on 0.4 (I.E. OC values read from bamt.conf for both GPUs)

BitMinerN8

hero member

Activity: 626

Merit: 500

Mining since May 2011.

Quote from: lodcrappo on February 24, 2012, 11:29:41 PM

Quote from: BitMinerN8 on February 24, 2012, 11:18:10 PM

Quote from: lodcrappo on February 24, 2012, 08:52:28 PM

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

When trying to run fixer:

Code:

(Tombstone with RIP fixer)

One of the BAMT tools has suffered a fatal error.
Not a GLOB reference at /usr/share/perl/5.10/IO/Zlib.pm line 559.

that is an old bug, actually not in bamt code but some versions of a perl lib we use. must have snuck back in at some point.
the updated version of fixer inside fix 1 actually solves that, but you can't get it if the fixer you have pukes.
i'll look into workarounds. sometimes a reboot makes that message just goes away but not always.

Sorry, coldreboot a no go.

lodcrappo

hero member

Activity: 616

Merit: 506

Quote from: BitMinerN8 on February 24, 2012, 11:18:10 PM

Quote from: lodcrappo on February 24, 2012, 08:52:28 PM

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

When trying to run fixer:

Code:

(Tombstone with RIP fixer)

One of the BAMT tools has suffered a fatal error.
Not a GLOB reference at /usr/share/perl/5.10/IO/Zlib.pm line 559.

that is an old bug, actually not in bamt code but some versions of a perl lib we use. must have snuck back in at some point.
the updated version of fixer inside fix 1 actually solves that, but you can't get it if the fixer you have pukes.
i'll look into workarounds. sometimes a reboot makes that message just goes away but not always.

BitMinerN8

hero member

Activity: 626

Merit: 500

Mining since May 2011.

Quote from: lodcrappo on February 24, 2012, 08:52:28 PM

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

When trying to run fixer:

Code:

(Tombstone with RIP fixer)

One of the BAMT tools has suffered a fatal error.
Not a GLOB reference at /usr/share/perl/5.10/IO/Zlib.pm line 559.

lodcrappo

hero member

Activity: 616

Merit: 506

Quote from: DeathAndTaxes on February 24, 2012, 10:43:44 PM

Quote from: lodcrappo on February 24, 2012, 10:36:34 PM

Quote from: DeathAndTaxes on February 24, 2012, 10:35:40 PM

Quote from: lodcrappo on February 24, 2012, 10:34:32 PM

Quote from: DeathAndTaxes on February 24, 2012, 10:18:28 PM

So was cgminer integration removed from 0.5? bamt seems to ignore cgminer=1 in config. I can manually start cgminer just fine but no stats are passed to gpumon, mpgumon?

No it was not removed. Did you add to main settings section and also each gpu you want to use cgminer with?

Yeah unless the syntax changed. Weird that cgminer = 0 was removed from default config file. Will play around with it.

many options were removed from the default config to make it simpler for noobs. there is an explanation of this in the file.

Thanks I must have had too many or few spaces. It is working now. Just an alternative point of view I don't think missing options is more noob friendly. Noob wants to use cgminer it is easier to say change cgminer: 0 to cgminer: 1 set "blah blah blah" for cgminer_opt and turn on cgminer: 1 for each GPU than to tell them the options are missing, they can find the syntax in the example file, make sure to get spacing right, or copy the example over their existing one and then edit.

Or maybe I am just being a noob.

noobs are strongly encouraged to use phoenix. as phoenix and/or bamt's phoenix extensions add all the features of cgminer (which is happening very quickly), there will be little reason for typical users to worry about this. I will leave cgminer support in since some people have donated towards having it there, but i don't think there will be any reason for it otherwise.

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

Quote from: lodcrappo on February 24, 2012, 10:36:34 PM

Quote from: DeathAndTaxes on February 24, 2012, 10:35:40 PM

Quote from: lodcrappo on February 24, 2012, 10:34:32 PM

Quote from: DeathAndTaxes on February 24, 2012, 10:18:28 PM

So was cgminer integration removed from 0.5? bamt seems to ignore cgminer=1 in config. I can manually start cgminer just fine but no stats are passed to gpumon, mpgumon?

No it was not removed. Did you add to main settings section and also each gpu you want to use cgminer with?

Yeah unless the syntax changed. Weird that cgminer = 0 was removed from default config file. Will play around with it.

many options were removed from the default config to make it simpler for noobs. there is an explanation of this in the file.

Thanks I must have had too many or few spaces. It is working now. Just an alternative point of view I don't think missing options is more noob friendly. Noob wants to use cgminer it is easier to say change cgminer: 0 to cgminer: 1 set "blah blah blah" for cgminer_opt and turn on cgminer: 1 for each GPU than to tell them the options are missing, they can find the syntax in the example file, make sure to get spacing right, or copy the example over their existing one and then edit.

Or maybe I am just being a noob.

lodcrappo

hero member

Activity: 616

Merit: 506

Quote from: DeathAndTaxes on February 24, 2012, 10:35:40 PM

Quote from: lodcrappo on February 24, 2012, 10:34:32 PM

Quote from: DeathAndTaxes on February 24, 2012, 10:18:28 PM

So was cgminer integration removed from 0.5? bamt seems to ignore cgminer=1 in config. I can manually start cgminer just fine but no stats are passed to gpumon, mpgumon?

No it was not removed. Did you add to main settings section and also each gpu you want to use cgminer with?

Yeah unless the syntax changed. Weird that cgminer = 0 was removed from default config file. Will play around with it.

many options were removed from the default config to make it simpler for noobs. there is an explanation of this in the file.

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

Quote from: lodcrappo on February 24, 2012, 10:34:32 PM

Quote from: DeathAndTaxes on February 24, 2012, 10:18:28 PM

So was cgminer integration removed from 0.5? bamt seems to ignore cgminer=1 in config. I can manually start cgminer just fine but no stats are passed to gpumon, mpgumon?

No it was not removed. Did you add to main settings section and also each gpu you want to use cgminer with?

Yeah unless the syntax changed. Weird that cgminer: 0 was removed from default config file. Will play around with it.

lodcrappo

hero member

Activity: 616

Merit: 506

Quote from: DeathAndTaxes on February 24, 2012, 10:18:28 PM

So was cgminer integration removed from 0.5? bamt seems to ignore cgminer=1 in config. I can manually start cgminer just fine but no stats are passed to gpumon, mpgumon?

No it was not removed. Did you add to main settings section and also each gpu you want to use cgminer with?

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

So was cgminer integration removed from 0.5? bamt seems to ignore cgminer=1 in config. I can manually start cgminer just fine but no stats are passed to gpumon, mpgumon?

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

Quote from: gnar1ta$ on February 24, 2012, 09:31:41 PM

Quote from: lodcrappo on February 24, 2012, 09:26:13 PM

OK, so I guess the best answer is that BAMT rigs are fine as client miners for p2pool, but the p2pool software itself cannot be run on bamt?
Sorry not familiar with it.

Yes. Even if you use -a option in p2pool you will still have to run the pool software with a lot of writes, and the full block chains of all *coind's and all the writes that come with them. Not ideal for USB drives.

This. The p2pool "server" requires p2pool daemon running and bitcoind daemon running 24/7 creating a never ending storm of disk I/O. BAMT doesn't support that, shouldn't support that and it would be idiotic to even try.

That being said one can put p2pool on another machine and point 1, 2, 20, 200 BAMT rigs at the p2pool instance. BAMT works fine in that manner.

gnar1ta$

donator

Activity: 798

Merit: 500

Quote from: lodcrappo on February 24, 2012, 09:26:13 PM

OK, so I guess the best answer is that BAMT rigs are fine as client miners for p2pool, but the p2pool software itself cannot be run on bamt?
Sorry not familiar with it.

Yes. Even if you use -a option in p2pool you will still have to run the pool software with a lot of writes, and the full block chains of all *coind's and all the writes that come with them. Not ideal for USB drives.

lodcrappo

hero member

Activity: 616

Merit: 506

Quote from: gnar1ta$ on February 24, 2012, 09:23:55 PM

p2pool doesn't require a local wallet. You just need to point your miner to a machine running p2pool and any *coind's you wish to mine. That machine should absolutley not be a BAMT machine. I have 3 BAMT rigs merged mining on p2pool with cgminer. The non BAMT machine is the one I have to spend the most time on. Tongue

OK, so I guess the best answer is that BAMT rigs are fine as client miners for p2pool, but the p2pool software itself cannot be run on bamt?
Sorry not familiar with it.

gnar1ta$

donator

Activity: 798

Merit: 500

p2pool doesn't require a local wallet. You just need to point your miner to a machine running p2pool and any *coind's you wish to mine. That machine should absolutley not be a BAMT machine. I have 3 BAMT rigs merged mining on p2pool with cgminer. The non BAMT machine is the one I have to spend the most time on. Tongue

lodcrappo

hero member

Activity: 616

Merit: 506

Quote from: m3ta on February 24, 2012, 09:16:34 PM

Quote from: lodcrappo on February 24, 2012, 09:10:44 PM

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

P2pool has a "-a" option to specify a wallet address on its startup, that can obviously be located somewhere else.

I guess here is the best way to say it:

If p2pool can work like every other pool, then it is supported.
If not, it is not currently supported.
If there is some safe, reasonable way to run p2pool on BAMT that requires some changes, let me know what they are and I will consider making them.

m3ta

sr. member

Activity: 435

Merit: 250

Quote from: lodcrappo on February 24, 2012, 09:10:44 PM

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

P2pool has a "-a" option to specify a wallet address on its startup, that can obviously be located somewhere else.

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