All of lore.kernel.org
 help / color / mirror / Atom feed
* no USB keyboard in 3.5-rc1 and later
@ 2012-06-27  1:30 Bob Tracy
  2012-06-28  6:04 ` Bob Tracy
  0 siblings, 1 reply; 3+ messages in thread
From: Bob Tracy @ 2012-06-27  1:30 UTC (permalink / raw)
  To: linux-kernel

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.

For the dmesg output excerpted below, I've left out the USB hub
detection/initialization messages.  The system *does* have a USB 3.0 hub
with nothing currently attached to it, just in case the presence of 3.0
hardware is an issue.

The relevant 3.4 boot time messages look like this:

(...)
usb 1-1.1: new low-speed USB device number 3 using ehci_hcd
usb 1-1.1: New USB device found, idVendor=413c, idProduct=2107
usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.1: Product: Dell USB Entry Keyboard
usb 1-1.1: Manufacturer: DELL
input: DELL Dell USB Entry Keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/input/input3
generic-usb 0003:413C:2107.0001: input,hidraw0: USB HID v1.10 Keyboard [DELL Dell USB Entry Keyboard] on usb-0000:00:1a.0-1.1/input0
usb 1-1.2: new low-speed USB device number 4 using ehci_hcd
usb 1-1.2: New USB device found, idVendor=045e, idProduct=0039
usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.2: Product: Microsoft IntelliMouse<C2><AE> Optical
usb 1-1.2: Manufacturer: Microsoft
input: Microsoft Microsoft IntelliMouse<C2><AE> Optical as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input4
generic-usb 0003:045E:0039.0002: input,hidraw1: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse<C2><AE> Optical] on usb-0000:00:1a.0-1.2/input0
uhci_hcd: USB Universal Host Controller Interface driver
usb 1-1.6: new low-speed USB device number 5 using ehci_hcd
usb 1-1.6: New USB device found, idVendor=051d, idProduct=0002
usb 1-1.6: New USB device strings: Mfr=3, Product=1, SerialNumber=2
usb 1-1.6: Product: Back-UPS NS 1250 FW:7.g1 .D USB FW:g1 
usb 1-1.6: Manufacturer: American Power Conversion
usb 1-1.6: SerialNumber: JB0643005571  
generic-usb 0003:051D:0002.0003: hiddev0,hidraw2: USB HID v1.10 Device [American Power Conversion Back-UPS NS 1250 FW:7.g1 .D USB FW:g1 ] on usb-0000:00:1a.0-1.6/input0


The 3.5-rc4 messages look like this:

(...)
usb 1-1.1: new low-speed USB device number 3 using ehci_hcd
usb 1-1.1: New USB device found, idVendor=413c, idProduct=2107
usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.1: Product: Dell USB Entry Keyboard
usb 1-1.1: Manufacturer: DELL
usb 1-1.2: new low-speed USB device number 4 using ehci_hcd
usb 1-1.2: New USB device found, idVendor=045e, idProduct=0039
usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.2: Product: Microsoft IntelliMouse<C2><AE> Optical
usb 1-1.2: Manufacturer: Microsoft
uhci_hcd: USB Universal Host Controller Interface driver
usb 1-1.6: new low-speed USB device number 5 using ehci_hcd
usb 1-1.6: New USB device found, idVendor=051d, idProduct=0002
usb 1-1.6: New USB device strings: Mfr=3, Product=1, SerialNumber=2
usb 1-1.6: Product: Back-UPS NS 1250 FW:7.g1 .D USB FW:g1 
usb 1-1.6: Manufacturer: American Power Conversion
usb 1-1.6: SerialNumber: JB0643005571  

Thanks in advance for any assistance in figuring out what's going on
here.

--Bob

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: no USB keyboard in 3.5-rc1 and later
  2012-06-27  1:30 no USB keyboard in 3.5-rc1 and later Bob Tracy
@ 2012-06-28  6:04 ` Bob Tracy
  2012-06-30  3:36   ` Greg KH
  0 siblings, 1 reply; 3+ messages in thread
From: Bob Tracy @ 2012-06-28  6:04 UTC (permalink / raw)
  To: linux-kernel

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".

--Bob

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: no USB keyboard in 3.5-rc1 and later
  2012-06-28  6:04 ` Bob Tracy
@ 2012-06-30  3:36   ` Greg KH
  0 siblings, 0 replies; 3+ messages in thread
From: Greg KH @ 2012-06-30  3:36 UTC (permalink / raw)
  To: Bob Tracy; +Cc: linux-kernel

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2012-06-30  3:36 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-06-27  1:30 no USB keyboard in 3.5-rc1 and later Bob Tracy
2012-06-28  6:04 ` Bob Tracy
2012-06-30  3:36   ` Greg KH

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.