We've got a handful of PC's in a small office running Linux. We switched from MDK91 to SUSE93 over the past few months. One of the machines tends to lock up if left unattended too long. System never had these problems under MDK91. Sometimes (not every day), the monitor will display a message indicating that there is no signal from the computer (freq out of range). We get the same message when the monitor is on, but disconnected from the computer. Please note that the message does *not* come from SUSE, it comes from inside the monitor. Anyway; whenever this message is on the monitor, the system will not "wake up" when we move the mouse or click a key on keyboard. However; the case does still have power. We are forced to power cycle to reboot system to get it working again. From the behavior I would possibly think of a hardware or possibly heat

On Monday 13 March 2006 1:31 pm, Frank Bax wrote: problem. Another possible issue is with powersave. Try turning the power save daemon off and manually turn off the monitor for a couple of days and see if the system locks up. -- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

On 13/03/06 12:31, Frank Bax wrote:

We've got a handful of PC's in a small office running Linux. We switched from MDK91 to SUSE93 over the past few months. One of the machines tends to lock up if left unattended too long. System never had these problems under MDK91. Sometimes (not every day), the monitor will display a message indicating that there is no signal from the computer (freq out of range). We get the same message when the monitor is on, but disconnected from the computer. Please note that the message does *not* come from SUSE, it comes from inside the monitor. Anyway; whenever this message is on the monitor, the system will not "wake up" when we move the mouse or click a key on keyboard. However; the case does still have power. We are forced to power cycle to reboot system to get it working again.

The system does not lock up every morning (after being idle overnight). Sometimes it is usable in the morning, but is locked up after lunch (after being idle a few hours). I realise that this type of random symptom can be hard to diagnose, but any ideas why the system does not wake up?

Does this system by any chance have a Via chipset and an AMD processor? I was running an old system that locked up all the time when I had both memory slots populated (size did not matter), but rarely did with one slot left empty. A great bother, since system limit was 2x128MB. There are references in the SuSE database to this being a conflict of some sort between the Via chipset and AMD Athlons, but a) mine was an ancient K6-2, and b) the problem only surfaced once I installed 9.3 (aka. began using 2.6 kernel). SuSE may be right, but the problem may also be in the 2.6 via module(s). Both problem and solution were confirmed off-list by another list member; both of us swapped out the mainboards to finally resolve the issue.