Yeah, that looks good to me.  Aggression 14 does seem a bit high, tho.

overvolting in linux is more limited than windows.  probably just cannot be done.

however, by using correct settings you will probably find it isn't necessary.

11 is a reasonable aggression.  14 is pretty crazy.  plus you were messing with profiles 0 and 1.
I think you have much more stability now, without needing to screw around the voltage.

Well that sucks. Was hoping I could hit a crazy clock like 1040 and get 340MH/s if I up'd the voltage.

Pretty good point. 320 instead of 340 isn't much of a difference. I have two cards, so I am missing out on a total 40 MH/s. Not a big deal. But when you have 20-30 cards, or a large mining farm, it's a fairly considerable amount of money you are missing out on.

I'm having an odd memory underclocking issue.

I have a 6990 where I have flashed the BIOS to allow for a 150MHz memory clock.  With cgminer 2.3.1-2 on Ubuntu x64 I can set the memory clocks to 150MHz and there are no issues.  Also can use it just fine with atitweak and phoenix miner.

With BAMT, if I put in the profile (P2) that memory should be 150MHz, it freaks out.  On one machine it just halts.  On another machine it ignores it and runs the memory at 1250MHz.  It also ran at 150Mhz for a little while then went to 1250MHz.

I suspect something is conflicting with something else within BAMT.  Any ideas?

Different network card?

Mine are onboard.

And did you integrate all BAMT tools? I like BAMT for the web interface...

Btw, which OS did you take?

Go to http://192.168.11.1 enter username and password.
Click Internet...then choose route
add route to 192.168.1.0 (and 255.255.255.0 if subnet mask is needed) and select 192.168.1.1 as the next hop and leave the metric as default.

Something like that depending on your router should give your clients access to/ from the remote subnet.

Tracert is a command line tool you can run from windows to see the path your request is making. Its done like this from the command line:

tracert 192.168.1.1

It will tell you all the hops from the client your are running to the destination and the response from the routers at each hop. You can use that to see where the path is ending or looping for debugging a routing issue.

That's excellent info, thanks!
I'll try it and report back.