@jondecker: Well I overclock my cards separately using atitweak because it's a 5770 and 5830 so they have different clocks.
The status screen shows <
It's just happened again now and I can still see the temperatures so aticonfig must still be working.
When I look at the miner screen instances all I see is
"Exporting: /opt/AMD-APP-SDK-v2.4-lnx64/lib/x86_64
LAUNCH: python /opt/miners/phoenix//phoenix.py -v -u http://btcrig:btcrig@localhost:8337/ device=0 worksize=256 vectors aggression=10 bfi_int fastloop=false -k phatk"
Also another thing I noticed is if phoenix fails to connect it will just stop trying after a couple of attempts:
e.g. "Exporting: /opt/AMD-APP-SDK-v2.4-lnx64/lib/x86_64
LAUNCH: python /opt/miners/phoenix//phoenix.py -v -u http://btcrig:btcrig@localhost:8337/ device=0 worksize=256 vectors aggression=10 bfi_int fastloop=false -k phatk
[10/08/2011 22:45:12] Phoenix r111 starting...
[10/08/2011 22:45:22] Failed to connect, retrying...
[10/08/2011 22:45:32] Failed to connect, retrying..."
Even though the server is up and running as I'm mining it on my other PC. It's been sat like that for 25 minutes without attempting to reconnect again now and smartcoin doesn't attempt to restart them either.
If I restart them manually they connect fine.
What distro are you running smartcoin on? When the miner instance screen shows blank, is it like that when it starts, or after its already been running and then hangs? (Does smartcoin ever work properly, if even just for a little bit? If/when it is working, do the miner instance screens look normal?)
Regarding phoenix connection issues, there isn't much I can do about phoenix issues, though it appears to me that lockup detection should happen in this instance. Also, i have gotten reports of r 111 and r112 of phoenix having these types of problems (I run phoenix r107 and never have issues like you are describing, perhaps you could verify?)
Linuxcoin 0.2-final.
I run it 16 hours a day and it only happens a couple of times a week.
It's always after a few hours or so.
When it works it looks normal.
I guess it's just locking up.
Do you recommend just setting the lockup script to restart the machine or set my clocks lower? Since it doesn't happen that often.
Ah, I'm using 1.5 but i'll try those, thanks.
I would recommend both actually - lower your clocks a little bit (2-3 mhz or so) and setup a nice lockup.sh script which reboots the machine and notifies you.
A good example is my own machine. I kept backing off my overclock by 1mhz until it was stable. Just the other day, for the first time in 0ver 40 days it finally detected a lockup and rebooted. Thats not enough of a concern for me to reduce clocks more, as I consider that pretty stable - but the lockup.sh script rebooting is a good thing, as otherwise I would have suffered some downtime until I checked on it (I'm known to not check on mine for several days at a time).