From owner-freebsd-questions Wed Jan 8 16:55:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA14646 for questions-outgoing; Wed, 8 Jan 1997 16:55:22 -0800 (PST) Received: from darwin.tti.net (darwin.tti.net [206.14.71.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA14641 for ; Wed, 8 Jan 1997 16:55:20 -0800 (PST) Received: from megawati.tti.net (megawati.tti.net [206.14.71.23]) by darwin.tti.net (8.6.11/8.6.9) with SMTP id QAA24662 for ; Wed, 8 Jan 1997 16:57:24 -0800 Message-Id: <199701090057.QAA24662@darwin.tti.net> Comments: Authenticated sender is From: "Jeffry Komala" Organization: Talking Technology, Inc. To: freebsd-questions@freebsd.org Date: Wed, 8 Jan 1997 16:57:07 PST MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: persistent console crash on 2.1.5R Priority: normal X-mailer: Pegasus Mail for Windows (v2.42a) Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a 2.1.5R box that has been operational for a few months. The problem is, after a random period of time after I rebooted the machine, the console would crash and the keyboard locked-up. The console behaved as if there is no signal from the video card (low power/sleep mode) while the keyboard simply locked-up. Yet, everything else was still running as if nothing happened. This behavior persisted when I rebooted the machine a few more times. Last night, I replaced the PCI VGA card with a monochrome card and it also trashed the console with garbage character after 20-15 minutes. The keyboard is still functional though. System has Pentium-100 with Triton chipsets, 64MB RAM, Adaptec 2940, IBM 2GB SCSI-3, Intel EtherExpress Pro 100B. This system used to have 2.1R in it and it ran just fine, never crashed the console and/or locked-up the keyboard before. The only piece of hardware I changed when I upgraded to 2.1.5R are the ethernet card and the hard drive. I used to have an Accton combo (NE2000 compatible). I also did a fresh installation of 2.1.5R and then tar the /home and some other essential files. So, it came as clean as it can be. Does anyone has experienced a similar problem or have any idea to fix this? TIA. Please CC your reply to jk@tti.net. Thanks. -jeff-