From mboxrd@z Thu Jan  1 00:00:00 1970
From: okamoto@granite.cias.osakafu-u.ac.jp
Message-Id: <200009010117.VAA25825@cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Keyboard woes
Content-Transfer-Encoding: 7bit
Date: Fri,  1 Sep 2000 10:16:31 +0900
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="upas-lrjmzqdzamnesikddliiijircg"
Topicbox-Message-UUID: 01c8f280-eac9-11e9-9e20-41e7f4b1d025

This is a multi-part message in MIME format.
--upas-lrjmzqdzamnesikddliiijircg
Content-Disposition: inline

I've never seen it while running about two months of Release 3.
I have only one display and keyboard for CPU and file server
and another machine.  In most times keyboard is off from the
CPU server...

By the way, thanks for your patch to Alef, now I'm running news
file server written in Alef (by Charles) on Release 3 Plan 9 system.

Yesterday, my release 2 CPU server retired from our office with best 
respects from me.  That file server was turned off the power, and still 
is waiting when I'll meet neccessity of updated release 2 sources.

Kenji


--upas-lrjmzqdzamnesikddliiijircg
Content-Type: message/rfc822
Content-Disposition: inline

Received: from granite.cias.osakafu-u.ac.jp ([192.168.1.3]) by diabase; Thu Aug 31 21:54:31 JST 2000
Received: from elmo.cias.osakafu-u.ac.jp (elmo.cias.osakafu-u.ac.jp [157.16.103.2])
	by granite.cias.osakafu-u.ac.jp (8.9.3/8.9.3) with ESMTP id VAA21531;
	Thu, 31 Aug 2000 21:51:30 +0900
Received: from cse.psu.edu (majordom@claven.cse.psu.edu [130.203.3.50])
	by elmo.cias.osakafu-u.ac.jp (8.9.3/3.7W-00080718) with ESMTP id VAA22630;
	Thu, 31 Aug 2000 21:51:38 +0900 (JST)
Received: from localhost (majordom@localhost)
	by cse.psu.edu (8.8.8/8.8.8) with SMTP id IAA03826;
	Thu, 31 Aug 2000 08:50:18 -0400 (EDT)
Received: by claven.cse.psu.edu (bulk_mailer v1.5); Thu, 31 Aug 2000 08:49:58 -0400
Received: (from majordom@localhost)
	by cse.psu.edu (8.8.8/8.8.8) id IAA03764
	for 9fans-outgoing; Thu, 31 Aug 2000 08:49:47 -0400 (EDT)
X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f
Received: from cackle.proxima.alt.za (cackle.proxima.alt.za [196.30.44.141])
	by cse.psu.edu (8.8.8/8.8.8) with ESMTP id IAA03759
	for <9fans@cse.psu.edu>; Thu, 31 Aug 2000 08:49:27 -0400 (EDT)
Received: (from lucio@localhost)
	by cackle.proxima.alt.za (8.9.3/8.9.1) id OAA02524
	for 9fans@cse.psu.edu; Thu, 31 Aug 2000 14:49:14 +0200 (SAST)
Date: Thu, 31 Aug 2000 14:49:12 +0200
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans mailing list <9fans@cse.psu.edu>
Subject: [9fans] Keyboard woes
Message-ID: <20000831144912.D2399@cackle.proxima.alt.za>
Reply-To: lucio@proxima.alt.za
Mail-Followup-To: 9fans mailing list <9fans@cse.psu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4us
Sender: owner-9fans@cse.psu.edu
Reply-To: 9fans@cse.psu.edu
Precedence: bulk

Has anyone else noticed that their i386 CPU server loses the keyboard
altogether?

I've been sharing the same disk on two totally different motherboards,
and the keyboard eventually (it is not clear when, but presumably
after an interval unused) dies altogether.

It could be something here, naturally, and the fact that the CPU
server is not linked to a network may also be significant: another CPU
server that is actually connected is still perfectly functional.

The main difference is that the CPU server that loses the keyboard is
running entirely off its IDE drive, the other off a 2ed fileserver,
the former starts off with graphics, the latter doesn't.

++L
--upas-lrjmzqdzamnesikddliiijircg--