From owner-freebsd-questions Wed Jan 8 20:10:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA24405 for questions-outgoing; Wed, 8 Jan 1997 20:10:08 -0800 (PST) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA24400 for ; Wed, 8 Jan 1997 20:10:06 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.2/8.6.12) with SMTP id UAA08243; Wed, 8 Jan 1997 20:09:25 -0800 (PST) Date: Wed, 8 Jan 1997 20:09:25 -0800 (PST) From: Doug White X-Sender: dwhite@localhost Reply-To: dwhite@resnet.uoregon.edu To: Jeffry Komala cc: freebsd-questions@freebsd.org Subject: Re: persistent console crash on 2.1.5R In-Reply-To: <199701090057.QAA24662@darwin.tti.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 8 Jan 1997, Jeffry Komala wrote: > > 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). Have you tried pulling the Ethernet card? Bad NE2000's are known to do strange things... Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major