Page 3 of 3 FirstFirst 123
Results 21 to 27 of 27

Thread: Wireless mouse not recognized at startup or reboot...

  1. #21
    Join Date
    Jan 2012
    Beans
    69

    Re: Wireless mouse not recognized at startup or reboot...

    Quote Originally Posted by misterblobby View Post
    I have a Logitech M305 wireless mouse, but have never had a problem. I'm currently using 12.04 with all updates installed.

    The touchpad used to drop out quite regularly ion 11.10, but never the mouse.

    What does all that mean? I don't know, but someone might.
    The issue in question only appears to apply to Logitech Darkfield technology mice - the Anywhere MX and Performance MX. Having continued my experiment with Grub, I haven't had a single instance where the mouse wasn't recognized as long as I didn't let Grub time out.

  2. #22
    Join Date
    Feb 2007
    Location
    Rome, Italy
    Beans
    2,184

    Re: Wireless mouse not recognized at startup or reboot...

    Quote Originally Posted by SemiExpert View Post
    The issue in question only appears to apply to Logitech Darkfield technology mice - the Anywhere MX and Performance MX. Having continued my experiment with Grub, I haven't had a single instance where the mouse wasn't recognized as long as I didn't let Grub time out.
    I have a hidden grub, without time out, and at every reboot mouse is not recognized.
    I've to unplug and plug again the MX recevicer.

    when it doesn't work there is only a entry in dmesg about the logitech mouse:

    Code:
    [   18.968583] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.0-2/input2
    instead removing and inserting again I get two entries:

    Code:
    [  106.130243] logitech-djreceiver 0003:046D:C52B.0006: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.0-2/input2
    [  106.139727] logitech-djdevice 0003:046D:C52B.0007: input,hidraw1: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:101a] on usb-0000:00:1d.0-2:1

  3. #23
    Join Date
    Mar 2010
    Location
    Southern NH, USA
    Beans
    160
    Distro
    Ubuntu 12.10 Quantal Quetzal

    Re: Wireless mouse not recognized at startup or reboot...

    Quote Originally Posted by SemiExpert View Post
    .... Having continued my experiment with Grub, I haven't had a single instance where the mouse wasn't recognized as long as I didn't let Grub time out.
    @SemiExpert,
    Does your keyboard use the same wireless receiver (is your keyboard even wireless)? I could see early HID traffic prior to kernel load putting the receiver into a known state and that having an impact on whether the mouse is probed properly. Does keyboard activity prior to grub have the same effect?

    @Lucazade,
    Is your mouse ever recognized at boot? If you do use the keyboard prior to kernel load, is the mouse recognized?

    Can someone put 'sudo lsusb -v output' for both working and non-working conditions? Don't paste, just attach.

  4. #24
    Join Date
    Dec 2009
    Location
    Vermont
    Beans
    853
    Distro
    Ubuntu

    Re: Wireless mouse not recognized at startup or reboot...

    You folks should be copying some of these posts to the bug report. From what I can tell (so far) the devs at Ubuntu could give a rat's butt about this problem; but they might take it a little more seriously if information like this narrows down the cause (and is shown to be a more widespread problem than it currently appears at the bug report).
    Linux: You reap what you tweak.

  5. #25
    Join Date
    Feb 2007
    Location
    Rome, Italy
    Beans
    2,184

    Re: Wireless mouse not recognized at startup or reboot...

    @NHclimber

    lsusb output attached.
    I'll post them also in the bug report... btw the mouse is recognized at boot rarely, I usually have to plug the receiver again.
    Attached Files Attached Files

  6. #26
    Join Date
    Mar 2010
    Location
    Southern NH, USA
    Beans
    160
    Distro
    Ubuntu 12.10 Quantal Quetzal

    Re: Wireless mouse not recognized at startup or reboot...

    Please don't do this unless you're 100% comfortable messing with your boot parameters and know how to repair a broken ram image from an alternate boot.

    It might help to see kernel logs with debug HID output to narrow down the problem. This will turn on debug output for the hid subsystem.
    Code:
    echo "options hid debug=1" | sudo tee /etc/modprobe.d/hid.conf
    sudo update-initramfs -u
    Then reboot.

    Please note that HID reports will output to the syslog and this could flood your logs if left on. After rebooting, turn off the debug HID output with:
    Code:
    echo "0" | sudo tee /sys/module/hid/parameters/debug
    Use these to reset back to how it was (debug HID output disabled) upon the next reboot:
    Code:
    sudo rm /etc/modprobe.d/hid.conf
    sudo update-initramfs -u
    Then attach or paste *ONLY* the fragment of syslog that begins
    Code:
    /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: Logitech-DJ:logi_dj_init
    A working probe of devices paired to the receiver looks like this (for keyboard and mouse)
    Code:
    Apr 16 12:17:51 thor kernel: [   18.383757] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: Logitech-DJ:logi_dj_init
    Apr 16 12:17:51 thor kernel: [   18.383772] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_probe called for ifnum 0
    Apr 16 12:17:51 thor kernel: [   18.383774] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_probe: ignoring ifnum 0
    Apr 16 12:17:51 thor kernel: [   18.383784] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_probe called for ifnum 1
    Apr 16 12:17:51 thor kernel: [   18.383786] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_probe: ignoring ifnum 1
    Apr 16 12:17:51 thor kernel: [   18.383793] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_probe called for ifnum 2
    Apr 16 12:17:51 thor kernel: [   18.386301] /build/buildd/linux-3.2.0/drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0110 wIndex=0x0002 wLength=7
    Apr 16 12:17:51 thor kernel: [   18.386983] /build/buildd/linux-3.2.0/drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0111 wIndex=0x0002 wLength=20
    Apr 16 12:17:51 thor kernel: [   18.387980] /build/buildd/linux-3.2.0/drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0120 wIndex=0x0002 wLength=15
    Apr 16 12:17:51 thor kernel: [   18.388983] /build/buildd/linux-3.2.0/drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0121 wIndex=0x0002 wLength=32
    Apr 16 12:17:51 thor kernel: [   18.390191] logitech-djreceiver 0003:046D:C52B.0004: hiddev0,hidraw3: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.2-2/input2
    Apr 16 12:17:51 thor kernel: [   18.392987] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15
    Apr 16 12:17:51 thor kernel: [   18.393056] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: delayedwork_callback
    Apr 16 12:17:51 thor kernel: [   18.393150] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_ll_parse
    Apr 16 12:17:51 thor kernel: [   18.393152] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_ll_parse: sending a kbd descriptor, reports_supported: 1a
    Apr 16 12:17:51 thor kernel: [   18.393321] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_ll_parse: sending a multimedia report descriptor: 1a
    Apr 16 12:17:51 thor kernel: [   18.393400] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_ll_parse: sending a power keys report descriptor: 1a
    Apr 16 12:17:51 thor kernel: [   18.393488] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_ll_start
    Apr 16 12:17:51 thor kernel: [   18.393643] input: Logitech Unifying Device. Wireless PID:2010 as /devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.2/0003:046D:C52B.0004/input/input4
    Apr 16 12:17:51 thor kernel: [   18.393651] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_ll_open:usb-0000:00:1d.2-2:1
    Apr 16 12:17:51 thor kernel: [   18.393792] logitech-djdevice 0003:046D:C52B.0007: input,hidraw4: USB HID v1.11 Keyboard [Logitech Unifying Device. Wireless PID:2010] on usb-0000:00:1d.2-2:1
    Apr 16 12:17:51 thor kernel: [   18.394983] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15
    Apr 16 12:17:51 thor kernel: [   18.395000] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: delayedwork_callback
    Apr 16 12:17:51 thor kernel: [   18.395066] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_ll_parse
    Apr 16 12:17:51 thor kernel: [   18.395069] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_ll_parse: sending a mouse descriptor, reports_supported: 4
    Apr 16 12:17:51 thor kernel: [   18.395243] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_ll_start
    Apr 16 12:17:51 thor kernel: [   18.395311] input: Logitech Unifying Device. Wireless PID:101b as /devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.2/0003:046D:C52B.0004/input/input5
    Apr 16 12:17:51 thor kernel: [   18.395445] logitech-djdevice 0003:046D:C52B.0008: input,hidraw5: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:101b] on usb-0000:00:1d.2-2:2
    Apr 16 12:17:51 thor kernel: [   18.396987] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15
    Apr 16 12:17:51 thor kernel: [   18.397007] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: delayedwork_callback
    Apr 16 12:17:51 thor kernel: [   18.397011] /build/buildd/linux-3.2.0/drivers/hid/hid-logitech-dj.c: logi_dj_recv_add_djhid_device: device list is empty

  7. #27
    Join Date
    Jan 2012
    Beans
    69

    Re: Wireless mouse not recognized at startup or reboot...

    The saga continues and periodically my mouse isn't recognized even if I have selected manually from the Grub menu. I've even had to unplug and replug twice in one instance. I'm wondering if this is really a Grub issue, a generic Kernel issue or an Ubuntu 12.04 specific issue?

Page 3 of 3 FirstFirst 123

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •