mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Romain Francoise <romain@orebokech.com>
To: Bob Tracy <rct@gherkin.frus.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Ming Lei <tom.leiming@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: 3.5-rcX: USB support without udev?
Date: Sun, 01 Jul 2012 22:34:08 +0200	[thread overview]
Message-ID: <87hatrjk5b.fsf@silenus.orebokech.com> (raw)
In-Reply-To: <20120701201411.GB8603@gherkin.frus.com> (Bob Tracy's message of "Sun, 1 Jul 2012 15:14:11 -0500")

Bob Tracy <rct@gherkin.frus.com> writes:

> Per the syslog entries I included in my initial post on this thread, the
> only difference between the pre- and post- usbfs removal cases seems to
> be whatever is needed for the input subsystem to see the USB keyboard
> and mouse.  I see the USB hubs and attached devices getting detected,
> but whatever "glue" allows the keyboard and mouse to work isn't there,
> and the input subsystem doesn't emit the expected messages at boot time.

FWIW, I have a similar issue on one of my boxes, v3.5-rc doesn't seem to
register the keyboard as an input device at boot time, using an initrd
with udev (175). The USB devices are detected, I can see usbhid getting
loaded, but the keyboard just doesn't work. And on this box the root
filesystem is luks-encrypted, which makes debugging somewhat difficult
without a keyboard.

The same keyboard works with the same kernel image on another box, so I
have no idea what this is about.

  parent reply	other threads:[~2012-07-01 20:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 13:16 Bob Tracy
2012-06-28 13:39 ` Ming Lei
2012-06-29  3:36   ` Bob Tracy
2012-06-30  3:35     ` Greg KH
2012-07-01 20:14       ` Bob Tracy
2012-07-01 20:16         ` Bob Tracy
2012-07-01 20:34         ` Romain Francoise [this message]
2012-07-01 20:58           ` Romain Francoise
2012-07-01 20:41         ` Henrik Rydberg
2012-07-01 23:25           ` Bob Tracy
2012-07-02  0:29             ` Bob Tracy
2012-07-02  5:52               ` Henrik Rydberg
2012-07-02 13:07                 ` Bob Tracy

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=87hatrjk5b.fsf@silenus.orebokech.com \
    --to=romain@orebokech.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rct@gherkin.frus.com \
    --cc=tom.leiming@gmail.com \
    /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

Powered by JetHome