I'll have to see if there is anything enables in the laptop bios. It would be a real bummer if I couldn't shut it off anymore. Ron On Saturday 12 January 2002 16:31, you wrote:
On Saturday 12 January 2002 07:10 am, Ron Joffe wrote:
Well it did it again last night. I had left the machine for about 1/2 hour with everything running (all my apps that is). When I came back to it, the screen had shut down (as it always does even with my power stuff disabled) that could be the monitor though. Anyway, I came back, and moved my mouse which startred the monitor up, but everything was frozen hard.
This time the Caps Lock and Scroll lock were on, but not blinking. So there is something going on inside, If a mouse movement can trigger the monitor to come out of sleep, it doesn't seem like this is a bios, but a software issue, maybee as Jostein had mentioned with X
The list of apps that were running are: Kmail Gkrellm Ymessenger Mozilla (latest & greatest) VMware (2 win2k sessions) xconsole
That's about it. My first choice would be that vmware is causing me grief. Anyone have similar situation?
my symptoms were like yours, blinking caps and scroll lock plus my hard drive light showed constant drive activity, even after logging out, telling the machine to shut down, and all services being terminated.
I haven't got vmware on my machine, So that may not be it. I do run kmail and gkrellm but feel they are unlikely candidates.
I dissabled apm in yast2 (etc/rc.config) and bios yesterday and haven't had the lockup or hard disk always accessing problem yet in the few hours of uptime since. Unfortunately my box does not recognize the power off switch any more so I have to boot into BeOS in order to shut down my machine. (I prefer this to hitting my ups switch)
It does seem that when I did have the problem it would show up within the first 15 minutes of logging into kde
----------------My previous comments follow----------------------
kde 2.2.2 from the SuSE site (dated jan 4, 2002) mantel kernel 2.4.16-21
It's really too soon for me to be blaming kde but that was my only recent upgrade (more than a week). Currently I'm wondering if it might be a power management conflict. Normally I use the on off switch for power management but it seems like I had some unexpected settings in that area.
I'll keep you posted
dh
-- Ron Joffe rjoffe@yahoo.com