From owner-freebsd-stable Wed May 7 05:49:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA20461 for stable-outgoing; Wed, 7 May 1997 05:49:41 -0700 (PDT) Received: from clio.rice.edu (clio.rice.edu [128.42.105.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA20456 for ; Wed, 7 May 1997 05:49:39 -0700 (PDT) Received: by clio.rice.edu (AIX 3.2/UCB 5.64/4.03) id AA13097; Wed, 7 May 1997 07:36:10 -0500 Date: Wed, 7 May 1997 07:36:10 -0500 From: keyser@clio.rice.edu (Kevin Keyser) Message-Id: <9705071236.AA13097@clio.rice.edu> To: tsprad@mail.metronet.com Subject: Re: frozen virtual terminals on Dell system Cc: freebsd-stable@FreeBSD.ORG Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > (not coincident with any other event I can think of) the system stops > > responding to all keyboard input, just as if the keyboard had been > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > unplugged. > ^^^^^^^^^ > Have you eliminated exactly that? I have a wonderful little IBM keyboard that > I was using with a mini-DIN to normal-DIN adapter plus an extension cable, and > I got the same symptoms quite often. The connections all seemed fine when I > checked them, but if I disconnected and reconnected it, it would immediately > start working fine again. Just a flakey connector, I guess. > > Doesn't hurt to check the really stupid stuff. > > Ted Spradley tsprad@metronet.com +1-972-484-5356 > Brisco: "...the more I learn the less I know." > Bowler: "At the rate we're learning things we won't know nothing in no time." In fact I did check this and it was not the problem. Even tried a different keyboard. Also, things work fine (relatively speaking) when booted into Win95. This makes me think the hardware is OK and I must have some config problem, IRQ conflict (though I don't see one), etc. Kevin Keyser keyser@clio.rice.edu