The MSI 890FXA-GD70 is a common mining board. I just thought I would point out that BAMT hard fails on boot w/ bios version v1.09 or earlier. I am not sure about v1.1A (v1.10) but v1.1B (v1.11) and later work including the latest at the time of writing v1.1D (v1.13).

If you wonder why I wrote the bios versions both ways. The website and post screen use the hex naming system however the actual BIOS configuration screen uses decimal version. BTW easiest way to flash seems to be format a USB stick FAT32 copy the bios file. Boot, launch Bios setup, go to M-flash menu and upgrade.

The MSI 890FXA-GD70 is a common mining board. I just thought I would point out that BAMT hard fails on boot w/ bios version v1.09 or earlier. I am not sure about v1.1A (v1.10) but v1.1B (v1.11) and later work including the latest at the time of writing v1.1D (v1.13).

If you wonder why I wrote the bios versions both ways. The website and post screen use the hex naming system however the actual BIOS configuration screen uses decimal version. BTW easiest way to flash seems to be format a USB stick FAT32 copy the bios file. Boot, launch Bios setup, go to M-flash menu and upgrade.

I think BAMT still has a ways to go to better integrate cgminer as lodcrappo suggested. When I stop mining with a rig in gpumon with shift+d and then try to start again, something weird happens and cgminer will not start back up.

The MSI 890FXA-GD70 is a common mining board. I just thought I would point out that BAMT hard fails on boot w/ bios version v1.09 or earlier. I am not sure about v1.1A (v1.10) but v1.1B (v1.11) and later work including the latest at the time of writing v1.1D (v1.13).

If you wonder why I wrote the bios versions both ways. The website and post screen use the hex naming system however the actual BIOS configuration screen uses decimal version. BTW easiest way to flash seems to be format a USB stick FAT32 copy the bios file. Boot, launch Bios setup, go to M-flash menu and upgrade.

This one has been in the bamt hardware compatibility list for some time, with notes about bios versions. I will add your notes as well.

I think BAMT still has a ways to go to better integrate cgminer as lodcrappo suggested. When I stop mining with a rig in gpumon with shift+d and then try to start again, something weird happens and cgminer will not start back up.

can you be more specific? what about stop/start from command line, are there messages? cgminer takes a while (maybe 2 minutes) to get going, are you waiting for it to be ready?

i can stop and start it OK here on test machine, but resources for testing beyond that are very limited.

I think BAMT still has a ways to go to better integrate cgminer as lodcrappo suggested. When I stop mining with a rig in gpumon with shift+d and then try to start again, something weird happens and cgminer will not start back up.

can you be more specific? what about stop/start from command line, are there messages? cgminer takes a while (maybe 2 minutes) to get going, are you waiting for it to be ready?

i can stop and start it OK here on test machine, but resources for testing beyond that are very limited.

I think I was doing a shift+d then a shift+r instead of shift+s. I think i am just used to hitting shift+r. Didn't try it with the command line.

I think BAMT still has a ways to go to better integrate cgminer as lodcrappo suggested. When I stop mining with a rig in gpumon with shift+d and then try to start again, something weird happens and cgminer will not start back up.

can you be more specific? what about stop/start from command line, are there messages? cgminer takes a while (maybe 2 minutes) to get going, are you waiting for it to be ready?

i can stop and start it OK here on test machine, but resources for testing beyond that are very limited.

I think I was doing a shift+d then a shift+r instead of shift+s. I think i am just used to hitting shift+r. Didn't try it with the command line.

it doesn't matter how you invoke it really. are you saying there is not a problem, or that there is? if there is a problem, i need more information than "something weird".

lodcrappo once I get all my rigs up a big donation is coming your way. I think BAMT + cgminer is really "the solution" for anyone with more than 1 or 2 rigs.

The only troubling thing is I seem to have much higher stale rate ~1% vs 0.1% however the pool I used went down so it may be some back end "junk". Don't want to jump to any conclusions.

The integration between cgminer & BAMT makes the bounty project to add RPC support to cgminer (that I herded together) a solid investment.

A feature request if I may:Since I would imagine most cgminers, use a config file would it be possible to add a "edit cgminer.conf" option to gpumon. It is so convenient to be able to hit c edit bamt.conf and drop back to gpumon but it is kinds spoiled by having to open a new screen launch nano to edit cgminer.conf.

Linux N00b here. With BAMT what is the best option or config file to modify to give a static IP for my rigs?

Thank you.

bamt is designed to be dynamically configured. if you must have a static IP, the best option is to create a reservation in your dhcp server.

That is what I do. You don't really want to be putting IP data into the image because if you use that copy on another rig it is going to get "fun". DHCP reservation makes is "easy". A single image can boot any rig and you always know what IP address that rig will have.

lodcrappo once I get all my rigs up a big donation is coming your way. I think BAMT + cgminer is really "the solution" for anyone with more than 1 or 2 rigs.

The only troubling thing is I seem to have much higher stale rate ~1% vs 0.1% however the pool I used went down so it may be some back end "junk". Don't want to jump to any conclusions.

The integration between cgminer & BAMT makes the bounty project to add RPC support to cgminer (that I herded together) a solid investment.

A feature request if I may:Since I would imagine most cgminers, use a config file would it be possible to add a "edit cgminer.conf" option to gpumon. It is so convenient to be able to hit c edit bamt.conf and drop back to gpumon but it is kinds spoiled by having to open a new screen launch nano to edit cgminer.conf.

it is not a big deal to add a key to open another file in editor. /etc/bamt/cgminer.conf work for everyone?

There seems to be a formatting problem in your bamt.conf file.YAML is picky. The specific complaint about your file is:

Stream does not end with newline character on line 0

here is my config file.

Code:

# Big A Miner Thing configuration# /etc/bamt/bamt.conf## You may be seeing this because you just booted up a new# BAMT system. To start mining:## 1. Adjust values in this file to your liking# 2. Save# 3. Add your pool URL(s) to the file specified per GPU# (if you click File, Open, the default 'pools' file should be right there) # 4. Either open root shell and type '/etc/init.d/mine restart', or power off and on.## From then on, this rig will auto mine at power on, no need# to touch it again.## To make this file quit opening every time you boot up,# remove the line 'show_config_at_boot: 1' below.# # Note: This is a YAML file. Indentation is significant.

# You'll need one gpuX: section per GPU installed. Not sure what's installed,# or the order? Open a root shell and type: aticonfig --list-adapters# # If you need more, copy paste the block and edit the gpu#. Delete blocks# if you don't have that many cards..

gpu0: # remove this or set to 0 to actually use this card.. disabled: 0

# whatever you'd like in the style used with phoenix. Do not use DEVICE= statement. kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=9

# IMPORTANT: pool_file must contain a list of pool URLs.. one at least, more if # you like. You can share the same file for all GPUs, or have one for each. # Miner will start with first URL in file, however if no shares are accepted # for any reason in (pool_timeout) seconds, the miner will move to next URL # in the file. Wraps around to first URL when last one fails.

There seems to be a formatting problem in your bamt.conf file.YAML is picky. The specific complaint about your file is:

Stream does not end with newline character on line 0

Did you open it with any weird (or windows, or mac) editors? I think it's complaining that the newlines aren't right, or even there.. a common symptom of using an editor from one OS to change files from another.

There is a clean config in /opt/bamt/examples that you can use as a base to fix it or replace it.

is it normal to have a card at 99% load in gpumon when that card is not actually mining?

not normal, and i really don't think possible. the card can't just invent it's own card to do. it's probably mining.i have sometimes seen GPUs report 99% load when they have been locked up due to too much overclocking, but usually then they will crash pretty soon after.

utf8 "\xFF" does not map to Unicode at /usr/share/perl5/YAML.pm line 77, <$IN> c hunk 1.Malformed UTF-8 character (unexpected end of string) in substitution (s///) at / usr/share/perl5/YAML/Loader.pm line 35, <$IN> line 1.Malformed UTF-8 character (unexpected end of string) in substitution (s///) at / usr/share/perl5/YAML/Loader.pm line 36, <$IN> line 1.

utf8 "\xFF" does not map to Unicode at /usr/share/perl5/YAML.pm line 77, <$IN> c hunk 1.Malformed UTF-8 character (unexpected end of string) in substitution (s///) at / usr/share/perl5/YAML/Loader.pm line 35, <$IN> line 1.Malformed UTF-8 character (unexpected end of string) in substitution (s///) at / usr/share/perl5/YAML/Loader.pm line 36, <$IN> line 1.

Malformed UTF-8 character (fatal) at /usr/share/perl5/YAML/Loader.pm line 38, <$ IN> line 1.

Rig was running fine last night. This morning it had crashed, rebooted and get this when restarting gpumon. Any ideas?

Its saying you have a weird character in your config file, \xFF to be exact. open up the file and look for anything obvious, otherwise copy the good one from examples over I guess, unless you backup up your config.