Mining window closing immediately in linuxcoin?

[gigabytecoin]

So I have been troubleshooting this problem with my friend over the phone for the last hour...

He has 4*5830s squeezed onto an MSI 790fx motherboard and fanned apart. Average temps do not go above 80 degrees celcius so he is good there.

The other day we had a scorcher... it hit ~41 celcius almost and one of his rigs turned off/froze/stopped working/whatever.

Now whenever he tries to start a miner through linuxcoin v0.2a (poclbm or phoenix)... his mining window "flashes open, and then immediately shuts".

I have only noticed such behaviour when I forgot to enter a kernel for phoenix, but he assured me that he was typing everything in correctly.

Anybody have any ideas as to what's up before I waste a ton of gas?!

Notes:
 - he can see all of his card temps through aticonfig (and set all of their clocks)
 - he is using sapphire 5830s
 - he is running linuxcoin v0.2a
 - he is freaking out

[1715287591]

1715287591

[1715287591]

1715287591

[Crs]

what psu does he have?
the video card where his lcd is connected might be broken. did he try to remove this card and replace it with another one ?

post the output of:

aticonfig --odgt --adapter=all
aticonfig --odgc --adapter=all
aticonfig --pplib-cmd "get fanspeed 0"
export DISPLAY=:0.1; aticonfig --pplib-cmd "get fanspeed 0"
export DISPLAY=:0.2; aticonfig --pplib-cmd "get fanspeed 0"
export DISPLAY=:0.3; aticonfig --pplib-cmd "get fanspeed 0"

[supa]

linuxcoin has sshd on it, doesn't it?

Is it possible you can get him to do whatever forwarding he needs to do so you can get a shell and double check?

In my experience, the amount of time and gas you spend to go out of your way to help someone is directly inversely proportional to the complexity of the problem....

... that is, if you drive 400 miles, it will turn out they didn't plug in the cat5.

... if you only have to drive 15 minutes, it will be an undiscovered bug in the instruction set of a specific CPU.
 

[Litt]

... if you only have to drive 15 minutes, it will be an undiscovered bug in the instruction set of a specific CPU.
 

This made me chuckle a little.. lol if this actually happened and you had to troubleshoot to find out.