From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] Re: AT Keyboard not present?
Date: Fri, 07 Sep 2001 21:12:10 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805146@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805145@msgid-missing>
I used to have that problem with my BigSur too. I changed
a whole bunch of things all at once when I moved the machine
from the lab to my cube, and the problem went away, so I'm
not sure what the problem was. Here's what I changed:
Upgraded processor from A3 to B3
Upgraded f/w (from ?? to ?? ... I forget versions)
Keyboard was directly connected in the lab,
started using a Belkin OmniCube 4-port KVM
switch to share keyboard between machines.
It's not the same keyboard that was in the lab.
Machine is now faces east instead of north :-)
My cube is at least 10F degrees warmer than the lab.
-Tony
-----Original Message-----
From: Bill Nottingham [mailto:notting@redhat.com]
Sent: Friday, September 07, 2001 1:46 PM
To: KOCHI Takayoshi
Cc: linux-ia64@linuxia64.org
Subject: [Linux-ia64] Re: AT Keyboard not present?
KOCHI Takayoshi (t-kouchi@mvf.biglobe.ne.jp) said:
> It was a BigSur with a PS/2 keyboard and a PS/2 mouse.
> I didn't configure usb driver in the kernel nor load
> as a module.
I've noticed some oddness with the keyboard controller on my BigSur;
for whatever reason, on a cold boot, one keyboard I have needs replugged
for it to work. The same keyboard works fine on other machines.
Bill
_______________________________________________
Linux-IA64 mailing list
Linux-IA64@linuxia64.org
http://lists.linuxia64.org/lists/listinfo/linux-ia64
prev parent reply other threads:[~2001-09-07 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 20:45 [Linux-ia64] Re: AT Keyboard not present? Bill Nottingham
2001-09-07 21:12 ` Luck, Tony [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590698805146@msgid-missing \
--to=tony.luck@intel.com \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.