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

[lodcrappo]

Out of curiosity - will BAMT support 5 or 6  HD7970 cards?

it will support whatever the AMD driver supports.  Usually that means 8 gpus total.

[btcnut]

Out of curiosity - will BAMT support 5 or 6  HD7970 cards?

it will support whatever the AMD driver supports.  Usually that means 8 gpus total.

Any idea what this means?

Code:

(process:308): GLib-WARNING **: getpwuid_r(): failed due to unknown user id (0)
startpar: service(s) returned failure: gdm ... failed!

aticonfig --list-adapters showed 0 supported adapters

[lodcrappo]

Out of curiosity - will BAMT support 5 or 6  HD7970 cards?

it will support whatever the AMD driver supports.  Usually that means 8 gpus total.

Any idea what this means?

Code:

(process:308): GLib-WARNING **: getpwuid_r(): failed due to unknown user id (0)
startpar: service(s) returned failure: gdm ... failed!

aticonfig --list-adapters showed 0 supported adapters

it means its time for you to write the image to your key again, and maybe just get a new usb key if things like that keep happening.

[dmcurser]

is there a soft release date for version .6 yet i think im holding off on new usb keys and asking to see about rates as fair as you programing my fram to read on one page until the release.

[Mapuo]

when starting up what does this mean

checkfs.sh failed with warning colored in yellow

Same problem, and bamt fail after 2-3-4 hours. Any ideas?

[lodcrappo]

when starting up what does this mean

checkfs.sh failed with warning colored in yellow

Same problem, and bamt fail after 2-3-4 hours. Any ideas?

"checkfs.sh failed with warning colored in yellow" means nothing important and can be ignored.

bamt fails after a few hours = reduce overclocking.

[lodcrappo]

is there a soft release date for version .6 yet i think im holding off on new usb keys and asking to see about rates as fair as you programing my fram to read on one page until the release.

0.6 has been "done" for a couple weeks now.  However we have bugs that have been very difficult to track down and have delayed the public release.

[Mapuo]

when starting up what does this mean

checkfs.sh failed with warning colored in yellow

Same problem, and bamt fail after 2-3-4 hours. Any ideas?

"checkfs.sh failed with warning colored in yellow" means nothing important and can be ignored.

bamt fails after a few hours = reduce overclocking.

It's the same rig with the same stick, with new BAMT on stick(actualy the same). Previosly work fine, now I reduce overclock with 10-20 mhz, but rig working few hours and fail. The only difrerence is yellow "checkfs.sh is ok with warning" or something like that.

[philips]

I think that checkfs is intentionally disabled for reducing startup time and reduce USB stick wear.

[lodcrappo]

I think that checkfs is intentionally disabled for reducing startup time and reduce USB stick wear.

we have a winner

[lodcrappo]

when starting up what does this mean

checkfs.sh failed with warning colored in yellow

Same problem, and bamt fail after 2-3-4 hours. Any ideas?

"checkfs.sh failed with warning colored in yellow" means nothing important and can be ignored.

bamt fails after a few hours = reduce overclocking.

It's the same rig with the same stick, with new BAMT on stick(actualy the same). Previosly work fine, now I reduce overclock with 10-20 mhz, but rig working few hours and fail. The only difrerence is yellow "checkfs.sh is ok with warning" or something like that.

as I already told you, that warning is unimportant.

sounds like some hardware isn't as happy as it used to be.  things break, it happens.

[Mapuo]

when starting up what does this mean

checkfs.sh failed with warning colored in yellow

Same problem, and bamt fail after 2-3-4 hours. Any ideas?

"checkfs.sh failed with warning colored in yellow" means nothing important and can be ignored.

bamt fails after a few hours = reduce overclocking.

It's the same rig with the same stick, with new BAMT on stick(actualy the same). Previosly work fine, now I reduce overclock with 10-20 mhz, but rig working few hours and fail. The only difrerence is yellow "checkfs.sh is ok with warning" or something like that.

as I already told you, that warning is unimportant.

sounds like some hardware isn't as happy as it used to be.  things break, it happens.

Ok, thanks.

[ibko]

Mapuo Met the same problem a month or two ago. The cause was defective PCIe riser ribbon.

Have somebody an idea how to setup BAMT to use STRATUM proxy?
user:pass@myproxy:8332 doesn't work at all (windows cgminer is ok with that).

[Joshwaa]

I have 3 BAMT rigs all working with stratum. Just change your pool addy to your stratum-proxy ip.  You are running the proxy on a local machine correct? No proxy no worky worky.

[Isokivi]

My rock-solid 5-gpu rig has during the last four days developed an issue and I dont have a clue as to what is causing it or what I should check next. At random intervals I find the rig idling, no mining going on, a simple restart mining does not resolve the issue, whereas a powerdown or coldreboot does. The main pool is up (I've even had the pool op check logs for anythig unusual... nothing there), the two backup pools are up, there has been no interruption in the network connection.

Miner: Phoenix
Bamt version: fully patched 0.5

Other thing's I've checked: the flashdrive running bamt is not full.

Any ideas/suggestions would be greatly appreciated.

[edit]
The only variable that has (somewhat) changed during the period this issue appeared I can think of is that the rig is getting cooler air as it is outdoors and it's fall here.

[bobers]

I use cgminer and receive this message, how can i resolve that?

Code:

[2012-09-20 11:07:37] longpoll failed for http://pool.50btc.com:8331/LP, sleeping for 30s
[2012-09-20 11:07:40] Accepted 00000000.9b5715c1.ba6658e2 GPU 2 thread 2 pool 0
[2012-09-20 11:07:42] Accepted 00000000.ba4183c7.fb206165 GPU 1 thread 1 pool 0
[2012-09-20 11:07:47] Accepted 00000000.163dede0.5bff2af5 GPU 2 thread 2 pool 0
[2012-09-20 11:07:57] Accepted 00000000.a62fe1fa.0e2ca4ea GPU 4 thread 4 pool 0
[2012-09-20 11:08:06] Accepted 00000000.1af2f41f.6e9033f3 GPU 3 thread 3 pool 0
[2012-09-20 11:08:07] Accepted 00000000.4b1dbb66.2da4df47 GPU 2 thread 2 pool 0
[2012-09-20 11:08:07] longpoll failed for http://pool.50btc.com:8331/LP, sleeping for 30s
[2012-09-20 11:08:09] Accepted 00000000.968bbb43.2666cabb GPU 4 thread 4 pool 0
[2012-09-20 11:08:12] Accepted 00000000.f9f289e6.7958d3dc GPU 1 thread 1 pool 0
[2012-09-20 11:08:16] Accepted 00000000.ed611128.67dea56c GPU 3 thread 3 pool 0
[2012-09-20 11:08:19] Accepted 00000000.2ee4a688.ef982e4b GPU 4 thread 4 pool 0
[2012-09-20 11:08:29] Accepted 00000000.fc87f7c7.7d0d7ea8 GPU 2 thread 2 pool 0
[2012-09-20 11:08:32] Accepted 00000000.55b10d1c.f8f4d9eb GPU 2 thread 2 pool 0
[2012-09-20 11:08:36] Accepted 00000000.d9b25a44.4093840d GPU 2 thread 2 pool 0
[2012-09-20 11:08:38] longpoll failed for http://pool.50btc.com:8331/LP, sleeping for 30s

[tnkflx]

lodcrappo,

Your current cgsnoop does not work with bfgminer 2.8.0. It doesn't output "Temperature" anymore via the API if none of your devices can show the temperature...

Here is an ugly hack for cgsnoop Add the following on line 166:

Code:

while ($res =~ m/\|PGA=(\d+),.*?MHS\sav=([\d\.]+).*?Accepted=(\d+),Rejected=(\d+)/g)
{
    $msg .= '|' . $1 . ':{"fan_speed":"0","current_temp_0":"N/A","current_core_clock":"0","current_load":"99","hashrate":' . $2 . ',"shares_invalid":"' . $6 . '","fan_rpm":"0","shares_accepted":"' . $5 . '","pool_url":"cgsnoop/' . $host . '","desc":"FPGA (cgsnoop)","current_mem_clock":"0","current_core_voltage":"0"}';

    if ($verbose)
    {
        print "PGA $1\n";
    }
}

[kano]

... hmm makes me think about my discussions with a certain dev about backward compatibility in the cgminer API and that dev's comments ... that leads to issues like this
Oh well ...

[lodcrappo]

My rock-solid 5-gpu rig has during the last four days developed an issue and I dont have a clue as to what is causing it or what I should check next. At random intervals I find the rig idling, no mining going on, a simple restart mining does not resolve the issue, whereas a powerdown or coldreboot does. The main pool is up (I've even had the pool op check logs for anythig unusual... nothing there), the two backup pools are up, there has been no interruption in the network connection.

Miner: Phoenix
Bamt version: fully patched 0.5

Other thing's I've checked: the flashdrive running bamt is not full.

Any ideas/suggestions would be greatly appreciated.

[edit]
The only variable that has (somewhat) changed during the period this issue appeared I can think of is that the rig is getting cooler air as it is outdoors and it's fall here.

remove gpus one at a time till you figure out which one it is. 

[lodcrappo]

lodcrappo,

Your current cgsnoop does not work with bfgminer 2.8.0. It doesn't output "Temperature" anymore via the API if none of your devices can show the temperature...

Here is an ugly hack for cgsnoop Add the following on line 166:

Code:

while ($res =~ m/\|PGA=(\d+),.*?MHS\sav=([\d\.]+).*?Accepted=(\d+),Rejected=(\d+)/g)
{
    $msg .= '|' . $1 . ':{"fan_speed":"0","current_temp_0":"N/A","current_core_clock":"0","current_load":"99","hashrate":' . $2 . ',"shares_invalid":"' . $6 . '","fan_rpm":"0","shares_accepted":"' . $5 . '","pool_url":"cgsnoop/' . $host . '","desc":"FPGA (cgsnoop)","current_mem_clock":"0","current_core_voltage":"0"}';

    if ($verbose)
    {
        print "PGA $1\n";
    }
}

thanks.  in general, bamt makes no attempt to have compatibility with software/versions other than those it comes with or delivers via fixer/apt.  in this case it is likely that we'll be packaging bfg 2.8.0 in the near future though, so this is good to know.