From: Brian McGroarty <brian@mcgroarty.net>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB KVM breaks under 2.6.0
Date: Thu, 15 Jan 2004 23:59:41 -0600 [thread overview]
Message-ID: <20040116055941.GB2174@mcgroarty.net> (raw)
In-Reply-To: <20040116005041.GG23253@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
On Thu, Jan 15, 2004 at 04:50:41PM -0800, Greg KH wrote:
> On Wed, Jan 14, 2004 at 12:40:32AM -0600, Brian McGroarty wrote:
> > I have a Belkin Omniview SE 4, a four port KVM, with keyboard and
> > mouse provided to a Linux box via USB.
> >
> > Under 2.4.23, the device works well. The keyboard and mouse are
> > detected.
> >
> > Under 2.6.0 (Debian build), the keyboard is not recognized.
>
> NEVER use the usbkbd driver, unless you _really_ know what you are
> doing. Please read the config help entry for that item.
I had two problems. Once the second problem was resolved, pulling
usbkbd from the picture made operation more consistent between
directly-plugged and KVM-switched keyboards.
For the second problem, the uhci driver changed names from 2.4 to
2.6. If others google(v) for this problem and find this post, you want
the module "uhci_hcd" and not "usb-uhci" when going from 2.4 to 2.6
The original USB loader daemon I was using recognized the change, but
the second I had tried and was still using did not. I've sent notes to
ask Documentation/input/input.txt to be updated, and I've filed a bug
against the second daemon.
Thanks for the help!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-01-16 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 6:40 USB KVM breaks under 2.6.0 Brian McGroarty
2004-01-16 0:50 ` Greg KH
2004-01-16 5:59 ` Brian McGroarty [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=20040116055941.GB2174@mcgroarty.net \
--to=brian@mcgroarty.net \
--cc=greg@kroah.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox