From: "linux-os \(Dick Johnson\)" <linux-os@analogic.com>
To: "Jiri Kosina" <jikos@jikos.cz>
Cc: "Linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: USB Keyboard
Date: Thu, 15 Mar 2007 13:49:38 -0400 [thread overview]
Message-ID: <Pine.LNX.4.61.0703151345010.4487@chaos.analogic.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703151835150.12394@twin.jikos.cz>
On Thu, 15 Mar 2007, Jiri Kosina wrote:
> On Thu, 15 Mar 2007, linux-os (Dick Johnson) wrote:
>
>> I have multiple AMD 64-bit servers in several configurations, with
>> several different motherboards, which fail to recognize a USB keyboard
>> when booted from a "stock" Linux kernel. They only work with a RedHat
>> kernel! I have removed all but one CPU from one in an attempt to find
>> the problem.
> [...]
>> linux-2.6.8 linux-2.6.9 linux-2.6.10 linux-2.6.11
>> linux-2.6.11.9 linux-2.6.12 linux-2.6.12.5 linux-2.6.13
>> linux-2.6.13.4 linux-2.6.15.4 linux-2.6.16.24 linux-2.6.16.4
>> linux-2.6.19
>
> Could you please turn on USB debugging (and also maybe HID debugging, but
> usb debug should be more interesting now) and send us the logs?
>
> Thanks,
>
> --
> Jiri Kosina
Ouch! I can't do anything by copy from a screen! There is no way to
get `dmesg` without the keyboard! That's why I sent a request to
linux-kernel, hoping that the problem would sound familiar. All I
can do is boot the system (off a CD-ROM) and then pull the plug
when the keyboad doesn't work!
Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.24 on an i686 machine (5592.71 BogoMips).
New book: http://www.AbominableFirebug.com/
_
\x1a\x04
****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.
next prev parent reply other threads:[~2007-03-15 17:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 17:32 linux-os (Dick Johnson)
2007-03-15 17:36 ` Jiri Kosina
2007-03-15 17:49 ` linux-os (Dick Johnson) [this message]
2007-03-15 17:53 ` Jiri Kosina
2007-03-15 17:59 ` Dmitry Torokhov
2007-03-15 18:18 ` linux-os (Dick Johnson)
2007-03-15 19:07 ` [linux-usb-devel] " Alan Stern
2007-03-15 19:58 ` linux-os (Dick Johnson)
2007-03-15 20:07 ` Dmitry Torokhov
2007-03-15 21:25 ` Alan Stern
2007-03-15 21:40 ` linux-os (Dick Johnson)
2007-03-16 1:54 ` Alan Stern
2007-03-15 21:41 ` linux-os (Dick Johnson)
2007-03-15 21:43 ` Jiri Kosina
2007-03-15 21:49 ` linux-os (Dick Johnson)
2007-03-15 21:54 ` Jiri Kosina
2007-08-15 17:22 linux-os (Dick Johnson)
2007-08-16 9:23 ` Jiri Kosina
2007-08-16 11:33 ` linux-os (Dick Johnson)
2007-08-16 13:00 ` Jiri Kosina
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=Pine.LNX.4.61.0703151345010.4487@chaos.analogic.com \
--to=linux-os@analogic.com \
--cc=jikos@jikos.cz \
--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
all inboxes | Powered by JetHome®