[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#451760: marked as done (linux-image-2.6.22-3-amd64: ps2 keyboard plugged into usb adaptor does not work after reconnecting)

Your message dated Fri, 14 Aug 2009 01:09:26 +0200
with message-id <20090813230926.GA14389@galadriel.inutil.org>
and subject line Re: linux-image-2.6.22-3-amd64: ps2 keyboard plugged into usb adaptor does not work after reconnecting
has caused the Debian Bug report #451760,
regarding linux-image-2.6.22-3-amd64: ps2 keyboard plugged into usb adaptor does not work after reconnecting
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
451760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=451760
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.22-3-amd64
Version: 2.6.22-6
Severity: normal

If I boot up my laptop with a PS2 keyboard plugged into a USB->PS/2
mouse+keyboard adaptor, then I have a working keyboard and mouse.

I think it is these lines that correspond to that upon bootup:

usb 3-2: new low speed USB device using uhci_hcd and address 2
usb 3-2: configuration #1 chosen from 1 choice
usbcore: registered new interface driver hiddev
input: Generic USB K/B as /class/input/input1
input: USB HID v1.10 Keyboard [Generic USB K/B] on usb-0000:00:1d.0-2
input: Generic USB K/B as /class/input/input2
input: USB HID v1.10 Mouse [Generic USB K/B] on usb-0000:00:1d.0-2

If I unplug either end of the adaptor (remove the USB plug, or remove
the keyboard and mouse from the adaptor), then I only get the mouse
back.  The keyboard flashes its LEDs indicating it has power, but no
keystrokes get through.

dmesg still shows it is still recognising that the adaptor has a
keyboard and mouse capability:

usb 3-2: USB disconnect, address 3
usb 3-2: new low speed USB device using uhci_hcd and address 4
usb 3-2: configuration #1 chosen from 1 choice
input: Generic USB K/B as /class/input/input13
input: USB HID v1.10 Keyboard [Generic USB K/B] on usb-0000:00:1d.0-2
input: Generic USB K/B as /class/input/input14
input: USB HID v1.10 Mouse [Generic USB K/B] on usb-0000:00:1d.0-2

/dev/input/by-id/usb-13ba_Generic_USB_K.B-*mouse show activity when
the mouse is moved, but usb-13ba_Generic_USB_K.B-event-kbd doesn't
show any activity when the keyboard is used.



This is all both from the console and in X.  If I plug in a real USB
keyboard, it works.  Yes, I have tried multiple PS/2 keyboards.

I have tried rmmodding all usb related stuff I can find -- 
hid usbhid uhci_hcd and modprobing it and usbkbd to no avail.


-- Package-specific info:

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22 (SMP w/2 CPU cores)
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.22-3-amd64 depends on:
ii  e2fsprogs                    1.40.2-1    ext2 file system utilities and lib
ii  initramfs-tools [linux-initr 0.91b       tools for generating an initramfs
ii  module-init-tools            3.3-pre11-4 tools for managing Linux kernel mo

linux-image-2.6.22-3-amd64 recommends no packages.

-- debconf information:
  linux-image-2.6.22-3-amd64/postinst/old-system-map-link-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/preinst/failed-to-move-modules-2.6.22-3-amd64:
  linux-image-2.6.22-3-amd64/prerm/removing-running-kernel-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/postinst/bootloader-error-2.6.22-3-amd64:
  linux-image-2.6.22-3-amd64/postinst/old-initrd-link-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/postinst/bootloader-test-error-2.6.22-3-amd64:
  linux-image-2.6.22-3-amd64/preinst/bootloader-initrd-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/preinst/lilo-initrd-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/preinst/abort-install-2.6.22-3-amd64:
  linux-image-2.6.22-3-amd64/preinst/elilo-initrd-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/preinst/initrd-2.6.22-3-amd64:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.22-3-amd64/postinst/create-kimage-link-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/postinst/depmod-error-initrd-2.6.22-3-amd64: false
  linux-image-2.6.22-3-amd64/prerm/would-invalidate-boot-loader-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/preinst/overwriting-modules-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/postinst/depmod-error-2.6.22-3-amd64: false
  linux-image-2.6.22-3-amd64/preinst/abort-overwrite-2.6.22-3-amd64:
  linux-image-2.6.22-3-amd64/preinst/already-running-this-2.6.22-3-amd64:
  linux-image-2.6.22-3-amd64/preinst/lilo-has-ramdisk:
  linux-image-2.6.22-3-amd64/postinst/old-dir-initrd-link-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/postinst/kimage-is-a-directory:

--- End Message ---
--- Begin Message --- 
On Sat, Dec 27, 2008 at 12:54:12PM +1100, Tim Connors wrote:

> > This is caused by design limitations of the PS/2 port, so it's not
> > surprising that it fails when using PS/2 with a USB adaptor. According
> > to http://en.wikipedia.org/wiki/PS/2_connector:
> >
> > | PS/2 ports are designed to connect the digital I/O lines of the microcontroller
> > | in the external device directly to the digital lines of the microcontroller on
> > | the motherboard. They are not designed to be hot swappable. Hot swapping PS/2
> > | devices usually does not cause damage due to the fact that more modern
> > | microcontrollers tend to have more robust I/O lines built into them which are
> > | harder to damage; however, hot swapping can still potentially cause damage on
> > | older machines, or machines with less robust port implementations.
> >
> > | If they are hotswapped, the devices must be similar enough that the driver
> > | running on the host system recognizes, and can be used with the new device.
> > | Otherwise, the new device will not function properly. While this is seldom
> > | an issue with standard keyboard devices, the host system rarely recognizes
> > | the new device attached to the PS/2 mouse port. In practice most keyboards
> > | can be hotswapped but this should be avoided.
> 
> However, I'm guessing a PS2-USB adaptor was probably designed so that it
> could be plugged into the keyboard, then plugged into the usb port
> providing power to the keyboard and host adaptor within the PS2-USB
> adaptor, and bringing it all up safely.
> 
> Of course, I have no way of proving whether it's the PS2-USB adaptor at
> fault here in not transmitting the keyboard codes onto the USB bus, or
> whether the kernel's USB interface isn't getting the codes sent to it.

I'm closing this bug, since it's very likely caused by the named hardware
limitation.

Cheers,
        Moritz

--- End Message ---
Reply to: