Date: Thu, 21 Mar 1996 10:58:43 -0800 (PST) From: Dave Walton <dwalton@psiint.com> To: "Andrew V. Stesin" <stesin@elvisti.kiev.ua> Cc: hardware@FreeBSD.ORG Subject: Re: Strange lockup problem Message-ID: <Pine.A32.3.91.960321105331.46341A-100000@vv.psiint.com> In-Reply-To: <199603210830.KAA27764@office.elvisti.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 21 Mar 1996, Andrew V. Stesin wrote: > If you still can do telnet to your box (or come into it It's not a matter of 'still'. This particular box is set up to be stand-alone. The network stuff has never been configured. > via modem port), that's a situation I've seen several > times before -- lockup (or better to say synchronization > problem) of onboard kbd controller, or keyboard itself. Any idea what the underlying problem is, and what the cure might be? > Sometimes re-plugging of kbd jack cures it (dangerous!) > or a command kbdcontrol -r fast < /dev/ttyv0 (issued > after coming into the box via telnet). I'll try these, but all they will do is FIX the problem. I need to AVOID it. > # mouse. The only changes were to comment out I386_CPU and I496_CPU, > # change the ident, and add options ATAPI, device wcd0, and device psm0. > # When I enable psm0, the system boots fine, but with the keyboard locked > # up. Disabling psm0 eliminates the problem. > > No idea on this. Since it's the keyboard, I suspect there is some relation between the two problems. This is actually the more important of the two, since it prevents me from running X. Dave ========================================================================== David Walton Unix Programmer PSI INTERNATIONAL, Inc. email: dwalton@psiint.com 190 South Orchard #C200 Fax :(707)451-6484 Vacaville, CA 95688 Phone:(707)451-3503 ==========================================================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.A32.3.91.960321105331.46341A-100000>