Announcement

Collapse
No announcement yet.

Logitech bluetooth keyboard and mouse disconnect on boot

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Logitech bluetooth keyboard and mouse disconnect on boot

    This is a pretty annoying problem, apparently everytime my system boots, it initializes and disconnects my bluetooth devices and I can't reconnect them until I unplug my dongle for about 30 seconds, and plug it back in, then reconnect the devices. I'm using a Logitech Bluetooth MX5000 keyboard and Bluetooth MX Laser mouse.

    I'm running kernel version 2.6.27-9. I have installed Bluetooth package 4.12-0ubuntu5 installed, as well as kdebluetooth 1:0.2-0ubuntu2, bluez 4.12-0ubuntu5, bluez-cups 4.12-0ubuntu5, osso-gwconnect 1.0.12.debian-1build1, and libbluetooth3 4.12-0ubuntu5.

    I started with this guide: http://tinyurl.com/6msrcx and hcitool scan didn't detect any devices.
    I moved on to this guide: http://tinyurl.com/5gck82 but the config appears to be from an old stack so I went directly to bluez.org http://www.bluez.org/faq/common/ which has the worst faq ever written and apparently no support documents.

    Anyone with experience using this keyboard and mouse combo will definitely know what I am talking about, but I can't find a relevant post anywhere to help me out. Someone please help!

    #2
    Re: Logitech bluetooth keyboard and mouse disconnect on boot

    Though I did find a user with the identical problem in the logitech forums:
    http://forums.logitech.com/logitech/...id=4625#M13093

    Comment


      #3
      Re: Logitech bluetooth keyboard and mouse disconnect on boot

      I found these messages in dmesg:

      [ 69.420025] btusb_intr_complete: hci0 urb ffff88012f41fc00 failed to resubmit (19)
      [ 69.420262] btusb_send_frame: hci0 urb ffff88012f4c3e40 submission failed
      [ 89.529606] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:04.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input6
      [ 89.588628] input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:04.0-1.2
      [ 89.809773] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:04.0/usb2/2-1/2-1.3/2-1.3:1.0/input/input7
      [ 89.890449] input,hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:04.0-1.3

      Comment


        #4
        Re: Logitech bluetooth keyboard and mouse disconnect on boot

        I tried running hid2hci, and I got this message:

        Switching device 046d:c70a to HCI mode was successful
        Switching device 046d:c70e to HCI mode was successful

        It added these lines to dmseg:
        [29247.425529] usb 2-1.1: new full speed USB device using ohci_hcd and address 12
        [29247.555265] usb 2-1.1: configuration #1 chosen from 1 choice
        [29311.180118] usb 2-1: USB disconnect, address 9
        [29311.180124] usb 2-1.1: USB disconnect, address 12
        [29311.181523] btusb_intr_complete: hci0 urb ffff880107cebc00 failed to resubmit (19)
        [29311.184384] btusb_send_frame: hci0 urb ffff880113c7a180 submission failed
        [29311.443155] usb 2-1.2: USB disconnect, address 10
        [29311.520886] usb 2-1.3: USB disconnect, address 11

        However, once I was in HCI mode the devices disconnected and would not reconnect without removing and reconnecting the dongle, so I am assuming this is the same problem as during startup that disconnects the devices. Perhaps it's not setting the dongle into HCI mode? Anyways I'm assuming it's at this point I disconnect and reconnect the keyboard and the following messages are added as the device is reset into HCD mode.

        [29328.559200] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
        [29329.064026] usb 2-1: new full speed USB device using ohci_hcd and address 13
        [29329.286848] usb 2-1: configuration #1 chosen from 1 choice
        [29329.289587] hub 2-1:1.0: USB hub found
        [29329.292181] hub 2-1:1.0: 3 ports detected
        [29329.605139] usb 2-1.2: new full speed USB device using ohci_hcd and address 14
        [29329.730252] usb 2-1.2: configuration #1 chosen from 1 choice
        [29329.752221] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:04.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input8
        [29329.784660] input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:04.0-1.2
        [29329.866139] usb 2-1.3: new full speed USB device using ohci_hcd and address 15
        [29329.991088] usb 2-1.3: configuration #1 chosen from 1 choice
        [29330.009693] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:04.0/usb2/2-1/2-1.3/2-1.3:1.0/input/input9
        [29330.096681] input,hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:04.0-1.3

        I'm assuming that disabling HCI mode in my startup configs will be a sufficient workaround, and hopefully this post was helpful to anyone else who has this problem. If anyone has a better solution, I would appreciate it.

        Comment


          #5
          Re: Logitech bluetooth keyboard and mouse disconnect on boot

          Bug report is here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355497

          Here's my workaround:
          Edited /etc/default/bluetooth:

          HID2HCI_ENABLED=0

          Made the same change in /etc/init.d/bluetooth

          Comment


            #6
            Re: Logitech bluetooth keyboard and mouse disconnect on boot

            Peabody,

            That worked great to get the keyboard going after reboot. Thanks. Now I am having an issue where my number pad does not work. It seems that the keylock key is the one not working. Has anyone else had this issue? Im using 8.10 Intrepid. Thanks.

            Killabee44
            8.10 Intrepid

            Comment


              #7
              Re: Logitech bluetooth keyboard and mouse disconnect on boot

              I found the fix to my numberpad not working (I am using 8.10 intrepid). It was a simple setting.

              System Settings> keyboard and mouse> under NumLock on KDE Startup select "Turn On"


              Also, under System Settings> Regional & Language> Keyboard Layout> Keyboard Model: I selected Logitech Cordless Desktop

              That's it. My keypad works now. I believe it was the "turn on numlock" setting that did it. Why they would have the numlock off by default is beyond me. Anyhow, I hope this helps someone.

              Killabee44
              8.10 Intrepid

              Comment


                #8
                Re: Logitech bluetooth keyboard and mouse disconnect on boot

                I just replaced Ubuntu 8.10 with Kubuntu 8.10. Under the orange version my Logitech mouse and keyboard worked by just adding the devices in the bluetooth control panel. I could not even find one in Kubuntu. The only bluetooth related thing I found was in the Internet section.

                I will try the configuration changes you suggest to get mine working as well.

                What does the kbluetooth under Internet control?

                Comment


                  #9
                  Re: Logitech bluetooth keyboard and mouse disconnect on boot

                  Here is an explanation on what kbluetooth is:

                  http://extragear.kde.org/apps/kdebluetooth/

                  I do not have any bluetooth apps on kubuntu like you mentioned. At this point I'm just glad the damn keyboard works properly.



                  8.10 Intrepid

                  Comment


                    #10
                    Re: Logitech bluetooth keyboard and mouse disconnect on boot

                    Originally posted by Peabody
                    Bug report is here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355497

                    Here's my workaround:
                    Edited /etc/default/bluetooth:

                    HID2HCI_ENABLED=0

                    Made the same change in /etc/init.d/bluetooth
                    Worked perfectly when i did this today.
                    Logitech Dinovo

                    Comment

                    Working...
                    X