• USB keyboard+mouse can't be hotplugged


    I own the Cordless Desktop Pro 2800 set from Logitech and for the past few months, more and more often it won’t work when plugged in after Linux boots.

    It will work well and fine after I boot the computer, but if I unplug the wireless receiver and plug it back again my laptop won’t detect the set anymore. Doesn’t matter which of the four ports. It won’t work. lsusb won’t find it. If I plug it in before booting Linux, it’ll be detected and work just fine though.

  • Can you post your mkinitcpio setup? It’s in /etc/mkinitcpio.conf
    I’m interested in the HOOKS line.

    EDIT:

    Oh, I had one idea. Connect your usb devices (cordless desktop pro…), boot and open a terminal. Run this:
    sudo mkinitcpio -p linux
    Reboot and check unplug/hotplug again.

    Cheers!

  • @Tamius-Han Follow @karasu 's advice above. Shouldn’t it works well enough, try also to

    1. Exclude the keyboard hook from auto-detection, shrinking and optimization. By placing it before the autodetect hook in the:

      /etc/mkinitcpio.conf
      
    2. Default Antergos = Arch hooks. keyboard hook is included in auto-detection. It is placed after the autodetect one. Problems with USB, Bluetooth, Cordless mice and keyboards may arise. Minimal initrams size, fast load, fast boot.

      HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
      
    3. Modified Antergos = Arch hooks. keyboard hook is excluded from auto-detection. It is placed before the autodetect one. It usually solves problems with USB, Bluetooth, Cordless mice and keyboards. initramfs image will increase in size by some bytes. Boot times are slighthly higher.

      HOOKS="base udev keyboard autodetect modconf block filesystems fsck"
      
    4. Rebuild the initramfs image

      sudo mkinitcpio -p linux
      
    5. Restart your Arch = Antergos

      sudo shutdown -r now
      
  • Nope, neither of the suggestions worked, still no hotplug on my keyboard/mouse set.

    cat /etc/mkinitcpio.conf | grep -v ^# :

    MODULES="nvidia"
    BINARIES=""
    FILES=""
    HOOKS="base udev keyboard autodetect modconf block keymap filesystems fsck"
    

    Prior to @just’s advice, ‘keyboard’ was before ‘keymap’.

    Also — I think I’ve forgot to mention that in the OP — I do have another (but vastly inferior) USB mouse. So far, hotplugging always works on that one. Just not for the kb/mouse set.

    EDIT: I just noticed dmesg is a bit funny.

    [ 1125.239304] usb 3-2: new full-speed USB device number 14 using xhci_hcd
    [ 1125.399464] usb 3-2: device descriptor read/64, error -71
    [ 1125.662959] usb 3-2: device descriptor read/64, error -71
    [ 1125.926432] usb 3-2: new full-speed USB device number 15 using xhci_hcd
    [ 1126.086560] usb 3-2: device descriptor read/64, error -71
    [ 1126.350041] usb 3-2: device descriptor read/64, error -71
    [ 1126.613511] usb 3-2: new full-speed USB device number 16 using xhci_hcd
    [ 1126.613683] usb 3-2: Device not responding to setup address.
    [ 1126.817153] usb 3-2: Device not responding to setup address.
    [ 1127.020383] usb 3-2: device not accepting address 16, error -71
    [ 1127.180534] usb 3-2: new full-speed USB device number 17 using xhci_hcd
    [ 1127.180708] usb 3-2: Device not responding to setup address.
    [ 1127.384148] usb 3-2: Device not responding to setup address.
    [ 1127.587458] usb 3-2: device not accepting address 17, error -71
    [ 1127.587494] usb usb3-port2: unable to enumerate USB device
    

    I’ll see where this goes.

Posts 4Views 1245
Log in to reply