Hide Forgot
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1 Xenta Wireless 2.4G mouse looses connection after a few minutes. The mouse works fine for a short time and then stops responding. When I connect a wired USB mouse that works fine. If I connect both then the wireless mouse works fine. Reproducible: Always Steps to Reproduce: 1. Connect Wireless mouse to USB port. 2. Use mouse for a few minuets Actual Results: Mouse stops working after a short time. Expected Results: Mouse should be working all the time.
Created attachment 529501 [details] Output of dmesg and lsusb Contains the output of dmesg and lsusb and lsusb -v
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Looking at https://fedoraproject.org/wiki/Xorg/Input_Triage_Algorithm, I see these information necessary. Please attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log*; check with grep Backtrace /var/log/Xorg* which logs might be the most interesting ones, send us at least Xorg.0.log) * output of the evtest command run like extest /dev/input/event<number> (number of the event file could be found in /var/log/Xorg.0.log for the particular device), and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 529563 [details] Xorg log file Xorg log file with mouse information in. 2.4G Receiver for mouse information.
Mouse recognise as three sperate devices usb 6-1: new low speed USB device number 4 using uhci_hcd [32546.570741] usb 6-1: New USB device found, idVendor=1d57, idProduct=32da [32546.570751] usb 6-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [32546.570757] usb 6-1: Product: 2.4G Receiver [32546.595404] input: 2.4G Receiver as /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.0/input/input19 [32546.597563] generic-usb 0003:1D57:32DA.0007: input,hidraw3: USB HID v1.10 Keyboard [2.4G Receiver] on usb-0000:00:1d.0-1/input0 [32546.611289] input: 2.4G Receiver as /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.1/input/input20 [32546.611640] generic-usb 0003:1D57:32DA.0008: input,hidraw4: USB HID v1.10 Mouse [2.4G Receiver] on usb-0000:00:1d.0-1/input1 [32546.639057] input: 2.4G Receiver as /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.2/input/input21 [32546.639381] generic-usb 0003:1D57:32DA.0009: input,hidraw5: USB HID v1.10 Device [2.4G Receiver] on usb-0000:00:1d.0-1/input2 Which device do I use for evtest
Created attachment 529565 [details] Var log messages file var log messages file
(In reply to comment #4) > Which device do I use for evtest just run evtest with no arguments and try all the ones in the list that look appropriate.
Created attachment 529768 [details] evtest output for mouse Tried with all three devices and got an output from device input 7. /dev/input/event0: Lid Switch /dev/input/event1: Power Button /dev/input/event10: Logitech USB Multimedia Keyboard /dev/input/event11: Logitech USB Multimedia Keyboard /dev/input/event12: Video Bus /dev/input/event13: TPPS/2 IBM TrackPoint /dev/input/event14: ThinkPad Extra Buttons /dev/input/event15: HDA Intel Mic /dev/input/event16: HDA Intel Headphone /dev/input/event17: HDA ATI HDMI HDMI/DP /dev/input/event18: Integrated Camera /dev/input/event2: Sleep Button /dev/input/event3: Power Button /dev/input/event4: AT Translated Set 2 keyboard /dev/input/event5: SynPS/2 Synaptics TouchPad /dev/input/event6: 2.4G Receiver /dev/input/event7: 2.4G Receiver /dev/input/event8: 2.4G Receiver
Any news on this. Is there anymore information I can provide. It has been a month since last post and F16 has been released. Is it worth me doing a resh install of F16 and seeing if that helps.
(In reply to comment #7) > Tried with all three devices and got an output from device input 7. does this mean you got output on device 7 even while it wasn't working in X? Can you run evtest in the background and wait for it to stop moving and then monitor the evtest output? does evtest still show events after the mouse has stopped working?
Hi after your last comment I tried the mouse again. Since then it has been working fine. Up until today. Where it has died after usage times vary. I ran evtest on /dev/input/event7 output was available only when the mouse was working. As soon as the mouse stopped I received no output from evtest. I have attached the last set of values that were output from evtest before the mouse died. See file evtest-mouse-dead.txt
Created attachment 540385 [details] evtest output before mouse died
Hi This is now happening more often is there anything else I can do to help diagnose the problem.
If evtest doesn't show anything when the mouse stops moving, the most likely cause is a hardware issue. There's also the option of a kernel bug but I think that's rather unlikely. Have you tried this device on any other non-linux machine? Either way, it's not an evdev or X bug.
Hi I have been using the device happily today at work on a Windows XP machine with no problems. The mouse is recognise as two different hardware components and installed as a standard HID component. At least I know the mouse works. Thanks for the help with this most strange.
I have since upgraded to F16. Although the problem still persists.
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
I have just updated my machine to 3.3.0-4.fc16.x86_64 and within 2minuetes the Mouse lost its connection again. output from dmesg showing connection and disconnection of mouse. [ 215.953092] usb 6-2: new low-speed USB device number 3 using uhci_hcd [ 216.113405] usb 6-2: New USB device found, idVendor=1d57, idProduct=32da [ 216.113415] usb 6-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 216.113422] usb 6-2: Product: 2.4G Receiver [ 216.130372] input: 2.4G Receiver as /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0/input/input16 [ 216.130849] generic-usb 0003:1D57:32DA.0004: input,hidraw0: USB HID v1.10 Keyboard [2.4G Receiver] on usb-0000:00:1d.0-2/input0 [ 216.146167] input: 2.4G Receiver as /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.1/input/input17 [ 216.146765] generic-usb 0003:1D57:32DA.0005: input,hidraw3: USB HID v1.10 Mouse [2.4G Receiver] on usb-0000:00:1d.0-2/input1 [ 216.173662] input: 2.4G Receiver as /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.2/input/input18 [ 216.174185] generic-usb 0003:1D57:32DA.0006: input,hidraw4: USB HID v1.10 Device [2.4G Receiver] on usb-0000:00:1d.0-2/input2 [ 231.188972] SELinux: initialized (dev proc, type proc), uses genfs_contexts [ 336.954419] usb 6-2: USB disconnect, device number 3 [ 338.679309] usb 6-2: new low-speed USB device number 4 using uhci_hcd [ 338.839200] usb 6-2: New USB device found, idVendor=1d57, idProduct=32da [ 338.839210] usb 6-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 338.839217] usb 6-2: Product: 2.4G Receiver [ 338.857260] input: 2.4G Receiver as /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0/input/input19 [ 338.857778] generic-usb 0003:1D57:32DA.0007: input,hidraw0: USB HID v1.10 Keyboard [2.4G Receiver] on usb-0000:00:1d.0-2/input0 [ 338.873146] input: 2.4G Receiver as /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.1/input/input20 [ 338.873748] generic-usb 0003:1D57:32DA.0008: input,hidraw3: USB HID v1.10 Mouse [2.4G Receiver] on usb-0000:00:1d.0-2/input1 [ 338.900686] input: 2.4G Receiver as /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.2/input/input21 [ 338.901174] generic-usb 0003:1D57:32DA.0009: input,hidraw4: USB HID v1.10 Device [2.4G Receiver] on usb-0000:00:1d.0-2/input2 [ 407.454202] usb 6-2: USB disconnect, device number 4
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.
I've come across another issue with a Xenia device. This time it's another device and ID, but since it's the same manufacturer with hardware suffering from the same symptoms it seems like I should put this here and re-open this old bug. I got a presenter remote for my presentations. It was a cheap one off ebay. It works flawless on Windows without any additional software and it should act as a normal keyboard. Of one key (the window switch key) I get a keycode, but the other keys report nothing at all. I've tried with evtest and showkey, even from a fresh xorg session, but it did not help. It's a bit odd that there's also a mouse listed, but I guess this is their most generic receiver. There is nothing from the OS at all when pressing keys, not even an error to work with. I'm on 3.17.8-200.fc20.x86_64 LSUSB: Bus 001 Device 007: ID 1d57:83ed Xenta Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x1d57 Xenta idProduct 0x83ed bcdDevice 11.10 iManufacturer 1 RF 2.4G iProduct 1 RF 2.4G iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 59 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 78 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 108 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Device Status: 0x0000 (Bus Powered) DMESG: [12383.573257] input: RF 2.4G RF 2.4G as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:1D57:83ED.0007/input/input21 [12383.573687] hid-generic 0003:1D57:83ED.0007: input,hidraw2: USB HID v1.10 Keyboard [RF 2.4G RF 2.4G ] on usb-0000:00:1a.0-1.3/input0 [12383.577497] input: RF 2.4G RF 2.4G as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:1D57:83ED.0008/input/input22 [12383.578229] hid-generic 0003:1D57:83ED.0008: input,hidraw3: USB HID v1.10 Mouse [RF 2.4G RF 2.4G ] on usb-0000:00:1a.0-1.3/input1
Please open a new bug.