From: Valdis.Kletnieks@vt.edu
To: Jiri Kosina <jkosina@suse.cz>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@suse.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-input@vger.kernel.org
Subject: Re: Wonkiness with keyboard adapter - not sure if it's in USB or input systems
Date: Tue, 26 Apr 2011 20:17:51 -0400 [thread overview]
Message-ID: <6382.1303863471@localhost> (raw)
In-Reply-To: Your message of "Tue, 26 Apr 2011 23:29:42 +0200." <alpine.LNX.2.00.1104262319240.12035@pobox.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1949 bytes --]
On Tue, 26 Apr 2011 23:29:42 +0200, Jiri Kosina said:
> On Tue, 26 Apr 2011, Valdis.Kletnieks@vt.edu wrote:
>
> > > > Bus 001 Device 006: ID 0e8f:0020 GreenAsia Inc. USB to PS/2 Adapter
> >
> > > Have you tried testing the adapter by plugging it in after the system
> > > is running?
> >
> > It works fine at the Grub screen.
> >
> > It *doesn't* work for the kernel when it initially starts up, even though a few
> > seconds ago the hardware worked just fine.
> >
> > It *does* work after I've unplugged/replugged it - I've tested both the USB
> > side and the PS2 side, in either case it starts working.
> It seems like the BIOS handover of the USB input device doesn't work
> properly.
>
> The way things usually work in such situations -- BIOS is able to
> understand USB input devices in a very basic mode (hidp) and translate the
> events into PS/2-looking events, so that things like grub (which don't
> understand USB HID) are able to see keyboard events -- BIOS presents those
> as PS/2 devices.
>
> Once kernel is booted, it takes over devices in this 'legacy' mode from
> BIOS, and initializes them properly as USB input devices.
>
> Seems like this process is broken on your system. Could you please try to
> disable legacy USB emulation in your BIOS, and see if the problem
> persists? (it will make USB keyboard unavailable in grub).
Possible datapoint - the USB handoff can't be *totally* broken on the laptop,
because it handled another Microsoft Natural keyboard with a USB on it just
fine, so it's something specific to the GreenAsia adapter.
I disabled legacy USB emulation, and as expected, the keyboard wasn't available
to grub. It was *also* unavailable to the initrd until I did the 'disc/reconnect' thing,
at which point it started working. (Sorry, don't have the dmesg from that
one, can get it tomorrow (Wed) morning if you want. And any advice on
additional debugging I can turn on to help would be accepted too).
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-04-27 0:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 15:47 Wonkiness with keyboard adapter - not sure if it's in USB or input systems Valdis.Kletnieks
2011-04-26 18:55 ` Alan Stern
2011-04-26 18:55 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1104261453300.2035-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2011-04-26 19:12 ` Valdis.Kletnieks-PjAqaU27lzQ
2011-04-26 19:12 ` Valdis.Kletnieks
2011-04-26 21:29 ` Jiri Kosina
2011-04-27 0:17 ` Valdis.Kletnieks [this message]
2011-04-27 17:23 ` Alan Stern
2011-04-27 17:23 ` Alan Stern
2011-04-27 17:27 ` Dr. David Alan Gilbert
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=6382.1303863471@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@suse.de \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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.