You are not logged in.

Pages: 1

#1 2015-01-10 21:09:22

phw
Member
Registered: 2013-05-27
Posts: 318

Logitech keyboard/mouse stop responsing suddenly

Hi,

I have both an external Logitech keyboard and mouse connected to my laptop, which both have worked flawlessly until a few days back. Now both keyboard and mouse suddenly stop responding during use. They work fine after boot, but may stop at any time while being actively used. When this happens my internal keyboard and touchpad still work. I get no error messages in journalctl unless I try to unplug a device and plug it in again. In this case I see the following:

Jan 10 21:19:43 zoidberg kernel: logitech-djreceiver 0003:046D:C52B.0003: can't reset device, 0000:00:1d.0-1.5/input2, status -32
Jan 10 21:19:43 zoidberg kernel: logitech-djreceiver 0003:046D:C52B.0003: can't reset device, 0000:00:1d.0-1.5/input2, status -32
Jan 10 21:19:43 zoidberg kernel: logitech-djreceiver 0003:046D:C52B.0003: can't reset device, 0000:00:1d.0-1.5/input2, status -32
Jan 10 21:19:43 zoidberg kernel: logitech-djreceiver 0003:046D:C52B.0003: can't reset device, 0000:00:1d.0-1.5/input2, status -32
Jan 10 21:19:43 zoidberg kernel: logitech-djreceiver 0003:046D:C52B.0003: can't reset device, 0000:00:1d.0-1.5/input2, status -32
Jan 10 21:19:43 zoidberg kernel: usb 2-1.5: USB disconnect, device number 3
Jan 10 21:19:43 zoidberg gdm-Xorg-:0[430]: (II) config/udev: removing device Logitech Unifying Device. Wireless PID:4002
Jan 10 21:19:43 zoidberg systemd-udevd[175]: error opening USB device 'descriptors' file
Jan 10 21:19:43 zoidberg gdm-Xorg-:0[430]: (II) evdev: Logitech Unifying Device. Wireless PID:4002: Close

The device does not work again after re-plugging it, though. Only a full reboot recovers this. I first thought it might be related to power management and the devices get suspended but fail to recover, but for both devices I see the following:

[ ~]# cat /sys/devices/pci0000\:00/0000\:00\:1d.0/usb4/4-1/4-1.6/power/level 
on
[ ~]# cat /sys/devices/pci0000\:00/0000\:00\:1d.0/usb4/4-1/4-1.5/power/level 
on

According to http://lwn.net/Articles/253587/ "on" means the device is not allowed to autosuspend. I also have not enabled autosuspend for USB explicitely.

My kernel is the official 3.17.6-1-ARCH. I can't say for sure when the problems started, first noticed it on January 7th or 8th. I have installed regular arch updates since then, but did not notice anything suspicious. I also did not change any system configuration.

Any ideas what I could check?

Offline

#2 2015-01-11 12:54:06

phw
Member
Registered: 2013-05-27
Posts: 318

Re: Logitech keyboard/mouse stop responsing suddenly

Small update, apparently I have different levels of this issue. Sometimes the mouse just disconnects in the middle of usage, but can automatically re-connect. I then see this in the journal:

Jan 11 13:43:37 zoidberg gdm-Xorg-:0[439]: (II) config/udev: removing device Logitech Gaming Mouse G400
Jan 11 13:43:37 zoidberg kernel: usb 2-1.6: USB disconnect, device number 5
Jan 11 13:43:37 zoidberg gdm-Xorg-:0[439]: (II) evdev: Logitech Gaming Mouse G400: Close
Jan 11 13:43:37 zoidberg gdm-Xorg-:0[439]: (II) UnloadModule: "evdev"
Jan 11 13:43:37 zoidberg systemd-udevd[173]: error opening USB device 'descriptors' file
Jan 11 13:43:44 zoidberg kernel: usb 2-1.6: new full-speed USB device number 7 using ehci-pci
Jan 11 13:43:44 zoidberg kernel: input: Logitech Gaming Mouse G400 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/0003:046D:C245.000E/input/input19
Jan 11 13:43:44 zoidberg kernel: hid-generic 0003:046D:C245.000E: input,hidraw1: USB HID v1.10 Mouse [Logitech Gaming Mouse G400] on usb-0000:00:1d.0-1.6/input0
Jan 11 13:43:44 zoidberg kernel: hid-generic 0003:046D:C245.000F: hiddev0,hidraw2: USB HID v1.10 Device [Logitech Gaming Mouse G400] on usb-0000:00:1d.0-1.6/input1
Jan 11 13:43:44 zoidberg mtp-probe[2725]: checking bus 2, device 7: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6"
Jan 11 13:43:44 zoidberg mtp-probe[2725]: bus: 2, device: 7 was not an MTP device
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (II) config/udev: Adding input device Logitech Gaming Mouse G400 (/dev/input/event14)
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (**) Logitech Gaming Mouse G400: Applying InputClass "evdev pointer catchall"
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (II) Using input driver 'evdev' for 'Logitech Gaming Mouse G400'
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (**) Logitech Gaming Mouse G400: always reports core events
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (**) evdev: Logitech Gaming Mouse G400: Device: "/dev/input/event14"
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (--) evdev: Logitech Gaming Mouse G400: Vendor 0x46d Product 0xc245
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (--) evdev: Logitech Gaming Mouse G400: Found 12 mouse buttons
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (--) evdev: Logitech Gaming Mouse G400: Found scroll wheel(s)
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (--) evdev: Logitech Gaming Mouse G400: Found relative axes
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (--) evdev: Logitech Gaming Mouse G400: Found x and y relative axes
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (II) evdev: Logitech Gaming Mouse G400: Configuring as mouse
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (II) evdev: Logitech Gaming Mouse G400: Adding scrollwheel support
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (**) evdev: Logitech Gaming Mouse G400: YAxisMapping: buttons 4 and 5
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (**) evdev: Logitech Gaming Mouse G400: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/0003:046D:C245.000E/input/input19/event14"
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (II) XINPUT: Adding extended input device "Logitech Gaming Mouse G400" (type: MOUSE, id 13)
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (II) evdev: Logitech Gaming Mouse G400: initialized for relative axes.
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (**) Logitech Gaming Mouse G400: (accel) keeping acceleration scheme 1
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (**) Logitech Gaming Mouse G400: (accel) acceleration profile 0
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (**) Logitech Gaming Mouse G400: (accel) acceleration factor: 2.000
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (**) Logitech Gaming Mouse G400: (accel) acceleration threshold: 4
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (II) config/udev: Adding input device Logitech Gaming Mouse G400 (/dev/input/mouse1)
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (II) No input driver specified, ignoring this device.
Jan 11 13:43:44 zoidberg gdm-Xorg-:0[439]: (II) This device may have been added with another device file.

I have also seen this happening in short intervals eventually ending with the behavior I reported above. I have also tried using the mouse on my USB3 instead of USB2 interfaces, but got the same result. Also interesting is that I have so far never seen that automatic disconnect / connect behavior for the keyboard, but once the mouse fails completely the keyboard will do so, too. The keyboard is a wireless device, that's the "Logitech Unifying Device" in my first post. The mouse is wired (Logitech Gaming Mouse G400). I will also try with a different mouse to see whether this is maybe a hardware issue.

Offline

#3 2015-01-11 12:58:46

phw
Member
Registered: 2013-05-27
Posts: 318

Re: Logitech keyboard/mouse stop responsing suddenly

Now I just had this happening again. When both keyboard an mouse failed I see this single ine in my journal:

Jan 11 13:56:55 zoidberg upowerd[511]: (upowerd:511): UPower-Linux-WARNING **: failed to coldplug unifying device: Attempt to read response from device timed out

Offline

#4 2015-01-11 13:06:03

phw
Member
Registered: 2013-05-27
Posts: 318

Re: Logitech keyboard/mouse stop responsing suddenly

Another update:

Once the devices failed and I unplug them I get the following output

Jan 11 13:59:47 zoidberg kernel: logitech-djreceiver 0003:046D:C52B.000C: can't reset device, 0000:00:1d.0-1.5/input2, status -32
Jan 11 13:59:47 zoidberg kernel: logitech-djreceiver 0003:046D:C52B.000C: can't reset device, 0000:00:1d.0-1.5/input2, status -32
Jan 11 13:59:47 zoidberg kernel: usb 2-1.5: USB disconnect, device number 6
Jan 11 13:59:47 zoidberg gdm-Xorg-:0[439]: (II) config/udev: removing device Logitech Unifying Device. Wireless PID:4002
Jan 11 13:59:47 zoidberg systemd-udevd[173]: error opening USB device 'descriptors' file
Jan 11 13:59:47 zoidberg gdm-Xorg-:0[439]: (II) evdev: Logitech Unifying Device. Wireless PID:4002: Close
Jan 11 13:59:47 zoidberg gdm-Xorg-:0[439]: (II) UnloadModule: "evdev"
Jan 11 13:59:55 zoidberg kernel: hid-generic 0003:046D:C245.0012: can't reset device, 0000:00:1d.0-1.6/input0, status -32
Jan 11 13:59:55 zoidberg kernel: hid-generic 0003:046D:C245.0012: can't reset device, 0000:00:1d.0-1.6/input0, status -32
Jan 11 13:59:55 zoidberg kernel: hid-generic 0003:046D:C245.0012: can't reset device, 0000:00:1d.0-1.6/input0, status -32
Jan 11 13:59:55 zoidberg kernel: hid-generic 0003:046D:C245.0012: can't reset device, 0000:00:1d.0-1.6/input0, status -32
Jan 11 13:59:55 zoidberg kernel: hid-generic 0003:046D:C245.0012: can't reset device, 0000:00:1d.0-1.6/input0, status -32
Jan 11 13:59:55 zoidberg kernel: hid-generic 0003:046D:C245.0012: can't reset device, 0000:00:1d.0-1.6/input0, status -32
Jan 11 13:59:55 zoidberg kernel: hid-generic 0003:046D:C245.0012: can't reset device, 0000:00:1d.0-1.6/input0, status -32
Jan 11 13:59:55 zoidberg kernel: hid-generic 0003:046D:C245.0012: can't reset device, 0000:00:1d.0-1.6/input0, status -32
Jan 11 13:59:55 zoidberg kernel: hid-generic 0003:046D:C245.0012: can't reset device, 0000:00:1d.0-1.6/input0, status -32
Jan 11 13:59:55 zoidberg kernel: hid-generic 0003:046D:C245.0012: can't reset device, 0000:00:1d.0-1.6/input0, status -32
Jan 11 13:59:55 zoidberg kernel: hid-generic 0003:046D:C245.0012: can't reset device, 0000:00:1d.0-1.6/input0, status -32
Jan 11 13:59:55 zoidberg kernel: hid-generic 0003:046D:C245.0012: can't reset device, 0000:00:1d.0-1.6/input0, status -32
Jan 11 13:59:55 zoidberg kernel: hid-generic 0003:046D:C245.0012: can't reset device, 0000:00:1d.0-1.6/input0, status -32
Jan 11 13:59:55 zoidberg kernel: usb 2-1.6: USB disconnect, device number 9
Jan 11 13:59:55 zoidberg gdm-Xorg-:0[439]: (II) config/udev: removing device Logitech Gaming Mouse G400
Jan 11 13:59:56 zoidberg gdm-Xorg-:0[439]: (II) evdev: Logitech Gaming Mouse G400: Close
Jan 11 13:59:56 zoidberg gdm-Xorg-:0[439]: (II) UnloadModule: "evdev"
Jan 11 13:59:56 zoidberg systemd-udevd[173]: error opening USB device 'descriptors' file

Replugging them:

Jan 11 14:00:43 zoidberg kernel: usb 2-1.5: new full-speed USB device number 10 using ehci-pci
Jan 11 14:00:43 zoidberg kernel: logitech-djreceiver 0003:046D:C52B.0016: hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.0-1.5/input2
Jan 11 14:00:43 zoidberg mtp-probe[3463]: checking bus 2, device 10: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5"
Jan 11 14:00:43 zoidberg mtp-probe[3463]: bus: 2, device: 10 was not an MTP device
Jan 11 14:00:58 zoidberg kernel: usb 2-1.6: new full-speed USB device number 11 using ehci-pci
Jan 11 14:00:59 zoidberg kernel: input: Logitech Gaming Mouse G400 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/0003:046D:C245.0017/input/input22
Jan 11 14:00:59 zoidberg kernel: hid-generic 0003:046D:C245.0017: input,hidraw2: USB HID v1.10 Mouse [Logitech Gaming Mouse G400] on usb-0000:00:1d.0-1.6/input0
Jan 11 14:00:59 zoidberg kernel: hid-generic 0003:046D:C245.0018: hiddev0,hidraw3: USB HID v1.10 Device [Logitech Gaming Mouse G400] on usb-0000:00:1d.0-1.6/input1
Jan 11 14:00:59 zoidberg mtp-probe[3492]: checking bus 2, device 11: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6"
Jan 11 14:00:59 zoidberg mtp-probe[3492]: bus: 2, device: 11 was not an MTP device
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (II) config/udev: Adding input device Logitech Gaming Mouse G400 (/dev/input/event14)
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (**) Logitech Gaming Mouse G400: Applying InputClass "evdev pointer catchall"
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (II) Using input driver 'evdev' for 'Logitech Gaming Mouse G400'
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (**) Logitech Gaming Mouse G400: always reports core events
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (**) evdev: Logitech Gaming Mouse G400: Device: "/dev/input/event14"
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (--) evdev: Logitech Gaming Mouse G400: Vendor 0x46d Product 0xc245
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (--) evdev: Logitech Gaming Mouse G400: Found 12 mouse buttons
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (--) evdev: Logitech Gaming Mouse G400: Found scroll wheel(s)
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (--) evdev: Logitech Gaming Mouse G400: Found relative axes
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (--) evdev: Logitech Gaming Mouse G400: Found x and y relative axes
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (II) evdev: Logitech Gaming Mouse G400: Configuring as mouse
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (II) evdev: Logitech Gaming Mouse G400: Adding scrollwheel support
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (**) evdev: Logitech Gaming Mouse G400: YAxisMapping: buttons 4 and 5
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (**) evdev: Logitech Gaming Mouse G400: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/0003:046D:C245.0017/input/input22/event14"
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (II) XINPUT: Adding extended input device "Logitech Gaming Mouse G400" (type: MOUSE, id 13)
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (II) evdev: Logitech Gaming Mouse G400: initialized for relative axes.
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (**) Logitech Gaming Mouse G400: (accel) keeping acceleration scheme 1
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (**) Logitech Gaming Mouse G400: (accel) acceleration profile 0
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (**) Logitech Gaming Mouse G400: (accel) acceleration factor: 2.000
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (**) Logitech Gaming Mouse G400: (accel) acceleration threshold: 4
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (II) config/udev: Adding input device Logitech Gaming Mouse G400 (/dev/input/mouse1)
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (II) No input driver specified, ignoring this device.
Jan 11 14:00:59 zoidberg gdm-Xorg-:0[439]: (II) This device may have been added with another device file.

As  I posted originally replugging does not make the devices work, even if the message seems to indicate this sad

Offline

#5 2015-01-11 14:08:08

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,175

Re: Logitech keyboard/mouse stop responsing suddenly

from your posts, i get the feeling the problem is with the wireless reciever.


please post lsusb and lsusb --tree , that will clarify whether the wireless reciever handles both keyboard and mouse.

Last edited by Lone_Wolf (2015-01-11 14:08:22)

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#6 2015-01-11 15:50:45

phw
Member
Registered: 2013-05-27
Posts: 318

Re: Logitech keyboard/mouse stop responsing suddenly

Thanks for the reply. The mouse is not connected via the wireless receiver but directly by USB cable. lsusb:

Bus 002 Device 005: ID 046d:c245 Logitech, Inc. G400 Optical Mouse
Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 1bcf:2c11 Sunplus Innovation Technology Inc. 
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 1058:0748 Western Digital Technologies, Inc. My Passport (WDBKXH, WDBY8L)
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsusb --tree

/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
        |__ Port 5: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 5: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 5: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 6: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 6: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
        |__ Port 1: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
        |__ Port 1: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M

It might be a hardware deffect. I will try both a different mouse and a different wireless receiver (but the same keyboard, I have not other). Unfortunately I have no way to force this to happen and I have to wait. When I work all day I have sometimes experienced this to happen frequently after a couple of minutes, forcing me to reboot several times during one hour. But I was also able to work for 4 hours without any problems at all.

Offline

#7 2015-01-12 12:32:06

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,175

Re: Logitech keyboard/mouse stop responsing suddenly

Understood, looking at lsusb output you got 4 usb hubs in your system.

bus 01 : Sunplus Innovation Technology Inc.  ,  looks like a (integrated?)  webcam  ?
bus 02: wireless receiver (keyboard) & mouse
bus 03: empty
bus 04: external HDD

If you can figure out which physical ports correspond to the bus 03 root hub ,
you could try connecting mouse to bus 03 / wireless reciever to bus 02 to spread load.

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#8 2015-01-12 14:03:07

phw
Member
Registered: 2013-05-27
Posts: 318

Re: Logitech keyboard/mouse stop responsing suddenly

Some update: I have been using a different mouse *and* a different wireless receiver for the whole day today (connected to the same ports), and I had no single crash. So I assume this is a hardware defect. I will switch back separately to my old mouse and old receiver in the next days and see which combination gives me the error again. My bet is on the mouse, as I had exactly the same model purchased at the same time fail a few months back (the behavior was different, though). I will update this thread once I have found the issue, but for now I believe this is hardware and not software related.

Lone_Wolf wrote:

If you can figure out which physical ports correspond to the bus 03 root hub ,
you could try connecting mouse to bus 03 / wireless reciever to bus 02 to spread load.

Interesting suggestion, but I think I already tried that. bus 01 should be the webcam, yes. bus 02 seem to be both USB 2.0 ports the laptop has (and where I have my keyboard and mouse connected). bus 03 and 04 are both USB 3.0 ports, where bus 03 is an always powered port. And exactly that port I have already tried to connect the mouse to, and I had a similar crash sad But I will verify that again.

Offline

Pages: 1

Board footer

Powered by FluxBB