Hi, What graphics card is in the Thinkpad? Have you checked the /var/log/XFree86.0.log for any errors? Look for messages fronted by (EE). Jostein
===== Original Message From Ron Joffe <rjoffe@yahoo.com> ===== Humm, nope I have not set a bios boot up password. Any other ideas?
Thanks,
Ron
On Friday 11 January 2002 03:13, you wrote:
I just had my Suse 7.3 running on a IBM T20 thinkpad lock up on me. I didn't have that much going on, but the strange part was that as soon as the system froze, bot the scroll lock and caps lock button started blinking. They continued blinking until I did a hard reset. Very strange
Nothing in the messages or warn logs. Any ideas of where else to look?
I don't know about that Thinkpad, but guys in my office eventually figured out that when an IBM Intel server locks up with the LEDs blinking, it means that the BIOS security/screensaver thingy has kicked in. If you type (blindly, there's no feedback) the BIOS power-on password, it snaps back into life.
-- Ron Joffe rjoffe@yahoo.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
The thinkpad T20 has a savage ix8 (I belive). I couldn't find any errors in the Xfree86 log. any other ideas? Thanks, Ron On Friday 11 January 2002 08:26, you wrote:
Hi,
What graphics card is in the Thinkpad? Have you checked the /var/log/XFree86.0.log for any errors? Look for messages fronted by (EE).
Jostein
===== Original Message From Ron Joffe <rjoffe@yahoo.com> ===== Humm, nope I have not set a bios boot up password. Any other ideas?
Thanks,
Ron
On Friday 11 January 2002 03:13, you wrote:
I just had my Suse 7.3 running on a IBM T20 thinkpad lock up on me. I didn't have that much going on, but the strange part was that as soon as the system froze, bot the scroll lock and caps lock button started blinking. They continued blinking until I did a hard reset. Very strange
Nothing in the messages or warn logs. Any ideas of where else to look?
I don't know about that Thinkpad, but guys in my office eventually figured out that when an IBM Intel server locks up with the LEDs blinking, it means that the BIOS security/screensaver thingy has kicked in. If you type (blindly, there's no feedback) the BIOS power-on password, it snaps back into life.
-- Ron Joffe rjoffe@yahoo.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- Ron Joffe rjoffe@yahoo.com
On Friday 11 January 2002 03:13, you wrote:
I just had my Suse 7.3 running on a IBM T20 thinkpad lock up on me. I didn't have that much going on, but the strange part was that as soon as the system froze, bot the scroll lock and caps lock button started blinking. They continued blinking until I did a hard reset. Very strange
I've been experiencing a similar problem for the last week or so but on a desktop w/ first generation athlon processor. Sometimes -as you described- 2 keyboard lights flash and the machine stops accepting all keyboard/mouse input, I have to hard reset. Currently my hard drive light is on (constant) even though I'm really not doing anything. This starts a few minutes after I start the machine, at first I thought it was something like updatedb but that doesn't seem to be it. I'm going to investigate my cabling this weekend. The only other thing I can see could be causing this is the most recent kde upgrade. best of luck to both of us dh
David, What version of kde did you upgrade to? I also recently upgraded to kde2.2.2 Ron On Friday 11 January 2002 10:32, you wrote:
On Friday 11 January 2002 03:13, you wrote:
I just had my Suse 7.3 running on a IBM T20 thinkpad lock up on me. I didn't have that much going on, but the strange part was that as soon as the system froze, bot the scroll lock and caps lock button started blinking. They continued blinking until I did a hard reset. Very strange
I've been experiencing a similar problem for the last week or so but on a desktop w/ first generation athlon processor.
Sometimes -as you described- 2 keyboard lights flash and the machine stops accepting all keyboard/mouse input, I have to hard reset.
Currently my hard drive light is on (constant) even though I'm really not doing anything. This starts a few minutes after I start the machine, at first I thought it was something like updatedb but that doesn't seem to be it.
I'm going to investigate my cabling this weekend. The only other thing I can see could be causing this is the most recent kde upgrade.
best of luck to both of us
dh
-- Ron Joffe rjoffe@yahoo.com
On Friday 11 January 2002 07:43 am, Ron Joffe wrote:
David,
What version of kde did you upgrade to? I also recently upgraded to kde2.2.2
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
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? Thanks, Ron On Friday 11 January 2002 20:10, you wrote:
On Friday 11 January 2002 07:43 am, Ron Joffe wrote:
David,
What version of kde did you upgrade to? I also recently upgraded to kde2.2.2
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
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
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
On Sunday 13 January 2002 08:48 am, Ron Joffe wrote:
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 --------------SNIP----------------------------------------
Well unfortunately for me it appears not to be a bios/apm problem after all. Got the lockup last night and tried some troubleshooting. I now know without a doubt that I cannot run SuSEconfig (and therefore many yast related maintenance functions) without my machine either locking up -w/ the flashing keyboard lights or in some cases totally resetting itself. This occured even when running at init 1 (single user mode). Once while in single user and once at a normal login I was able to view the output of SuSEconfig and noticed alot of gobbledygook (looked like a binary file viewed in a text editor) just before the lockup/reset. The last line printed before locking up is something about "susewm". I haven't been this frustrated since my Amiga gave up the ghost. I wouldn't want to be trying to convince a nyone how good SuSE/Linux is today, I'm just totally at a loss. One other possible avenue is that I installed the kde experimental rpm's (never was able to login to kde3 though). I dont know why this would mess things up when runnung a single user console. Best of luck dh
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If I remember, this is the Stinkpad? I have an A22p and have had this flashing lights once or twice. I also run VMware. But the only hard lockups besides that were a) before I added disableapic,and b) when I have an AdaptecSCSI PCMCIA in (1460 or 1480) and it went into suspend. Even though I set apm to deal with scsi card (shut it down first) I still get that, so cannot leave my SCSI in except when I use it. On Saturday, 12 January 2002 9:10, you 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?
Thanks,
Ron
On Friday 11 January 2002 20:10, you wrote:
On Friday 11 January 2002 07:43 am, Ron Joffe wrote:
David,
What version of kde did you upgrade to? I also recently upgraded to kde2.2.2
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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org
iD8DBQE8aZnnnQ18+PFcZJsRAs/CAJ99XrWZhapr/TS7r7htvHaXfI5eDQCZAQ4j tzdvs76y0/xjcG1VWUndBqc= =eBfj -----END PGP SIGNATURE-----
participants (4)
-
Carl A. Cook -
David Herman -
Jostein Berntsen -
Ron Joffe