All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Martin Bretschneider <mailing-lists-mmv@bretschneidernet.de>
Cc: linux-kernel@vger.kernel.org,
	Jan Engelhardt <jengelh@linux01.gwdg.de>,
	linux-usb-devel@lists.sourceforge.net, Greg KH <gregkh@suse.de>,
	Alan Stern <stern@rowland.harvard.edu>,
	Leonid <nouser@lpetrov.net>
Subject: Re: PROBLEM: PS/2 keyboard does not work with 2.6.15
Date: Mon, 9 Jan 2006 01:26:56 -0500	[thread overview]
Message-ID: <200601090126.56831.dtor_core@ameritech.net> (raw)
In-Reply-To: <E1Evi0c-0002mt-00@mars.bretschneidernet.de>

On Sunday 08 January 2006 16:23, Martin Bretschneider wrote:
> Hello,
> 
> Jens Nödler who has got the same motheboard (Gigabyte GA-K8NF-9 with
> nforce4 chipset) can confirm my problem. But he found out that the
> keyboard connected to the ps/2 port does work with kernel 2.6.15 if
> "USB keyboard support" is disabled in the BIOS.
>

Ok, I an getting enough reports to conclude that the new usb-handoff
code does not seem to be working. Let's try CCing USB list and other
parties involved :)

Greg, Alan, any ideas?

-- 
Dmitry

  parent reply	other threads:[~2006-01-09  6:27 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-05 13:58 PROBLEM: PS/2 keyboard does not work with 2.6.15 Martin Bretschneider
2006-01-05 14:37 ` Dmitry Torokhov
2006-01-06  7:21 ` Jan Engelhardt
2006-01-06 16:29 ` Martin Bretschneider
2006-01-06 19:00   ` Jesper Juhl
2006-01-08 21:23 ` Martin Bretschneider
2006-01-08 22:19   ` Dmitry Torokhov
2006-01-09  9:50     ` Martin Bretschneider
2006-01-09  6:26   ` Dmitry Torokhov [this message]
2006-01-09 15:32     ` Alan Stern
2006-01-09 16:50       ` Dmitry Torokhov
2006-01-09 17:23         ` Alan Stern
2006-01-09 17:54           ` Dmitry Torokhov
2006-01-09 20:08             ` Martin Bretschneider
2006-02-04  7:01             ` mahesh
2006-01-10  7:43           ` Vojtech Pavlik
2006-01-10 15:12             ` Alan Stern
2006-01-10 15:28               ` Vojtech Pavlik
2006-01-10 15:37                 ` Dmitry Torokhov
2006-01-11  0:01                   ` Jan Rekorajski
2006-01-11  0:19                     ` Pete Zaitcev
2006-01-11 15:26                     ` Alan Stern
2006-01-11 16:01                       ` Jan Rekorajski
2006-01-11 19:57                         ` Pete Zaitcev
     [not found]                   ` <161717d50601101019k34a901a8x37fb28187a609490@mail.gmail.com>
     [not found]                     ` <d120d5000601101225h32b44f7eobae654056cf0318c@mail.gmail.com>
     [not found]                       ` <161717d50601101419q373cde76y6b374f1ae289ca22@mail.gmail.com>
     [not found]                         ` <d120d5000601101425g576f8fd3kc9de80a4b320c3bf@mail.gmail.com>
2006-01-11  2:45                           ` Dave Neuer
2006-01-09 18:36       ` Martin Bretschneider
2006-01-09 19:09         ` Alan Stern
  -- strict thread matches above, loose matches on Subject: below --
2006-01-09  6:10 Leonid
2006-01-14 14:20 Walt H
2006-01-14 17:09 ` Alan Stern
2006-01-14 19:27   ` Walt H
2006-01-15 15:45     ` Alan Stern

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=200601090126.56831.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=gregkh@suse.de \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=mailing-lists-mmv@bretschneidernet.de \
    --cc=nouser@lpetrov.net \
    --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.