linux-kernel - Re: no USB keyboard in 3.5-rc1 and later

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20120630033626.GB4792@kroah.com>
Date:	Fri, 29 Jun 2012 23:36:26 -0400
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Bob Tracy <rct@...rkin.frus.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: no USB keyboard in 3.5-rc1 and later

On Thu, Jun 28, 2012 at 01:04:56AM -0500, Bob Tracy wrote:
> On Tue, Jun 26, 2012 at 08:30:31PM -0500, Bob Tracy wrote:
> > Here's hoping it's something simple.  Attached USB devices fail to
> > initialize/work for kernel version 3.5-rc1 and later (up through
> > 3.5-rc4).  From what I can tell from the dmesg output (attached),
> > there used to be an "input" or "generic-usb" message that appeared
> > for each device following detection -- showing the sysfs path to the
> > device.
> 
> The answer *was* simple: the deprecated usbfs under /proc went bye-bye
> starting with 3.5-rc1.  I'm still using a static "/dev" (no "udev").
> Hence, no device nodes under "/dev/bus/usb".

If you are using a static /dev/ then you should just create these nodes
statically and you should be fine, right?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/