Page 5 of 6 FirstFirst ... 3456 LastLast
Results 41 to 50 of 60

Thread: Bluetooth mouse stops to work after random time Ubuntu 13.04 on laptop

  1. #41
    Join Date
    Mar 2010
    Location
    India
    Beans
    8,149
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Bluetooth mouse stops to work after random time Ubuntu 13.04 on laptop

    Quote Originally Posted by macmus View Post
    one more interesting thing:

    It seems each open/close of lid .. binds it to next input device... i have already input 27!!!
    .....
    Is there a way how to clean this register of input devices?
    That is normal for removable devices. I think it is the kernel's own way of keeping records, we better not mess with that.
    (Try plugging-unplugging a usb device in the same port and monitor "dmesg". It's device id will increment in the same way each time, but it doesn't make it less stable)

    Quote Originally Posted by macmus View Post
    how to unload and reload all of the drivers ?
    I have never done such a trick
    Before explaining that, let me make it clear that this is an approach totally based on guess and assumptions.

    Now, for example, to unload only the "bluetooth" module, we need to unload all the modules that are using it -
    [Note : Text after a '#' are comments, I've put them just to explain things.
    Code:
    # Change to Root so you don't have to use "sudo" each time -
    sudo su
    
    # Stop the Bluetooth service so no drivers remain in use by it
    service bluetooth stop
    
    # Now remove the drivers
    modprobe -rv btusb # Should make bt icon disappear
    modprobe -rv bnep # This is the driver I suspect the most, but resetting others as well just because I'm paranoid..
    modprobe -rv hidp
    modprobe -rv rfcomm # This should also remove the "bluetooth" with it. If not, remove it manually -
    modprobe -rv bluetooth # Shouldn't be needed. Post back if it gives errors.
    
    # Reload the drivers in reverse sequence
    modprobe -v bluetooth # Not needed if it was removed automatically
    modprobe -v rfcomm
    modprobe -v hidp
    modprobe -v bnep
    modprobe -v btusb # The BT systray icon should return with this
    
    # Now restart the bluetooth service
    service bluetooth start
    
    # Exit root
    exit
    I am not sure whether the above should be done before or after resetting the hub (unbind - bind ehci), because I never needed the above at all. I'm also not sure whether or not it is going to help, especially after reading the evdev module part. So try both ways, and most important - keep the fingers as well as toes crossed !
    Varun
    Help others by marking threads as [SOLVED], if they are. (See how)
    Wireless Script | Use Code Tags

  2. #42
    Join Date
    Aug 2007
    Beans
    67

    Re: Bluetooth mouse stops to work after random time Ubuntu 13.04 on laptop

    Ok i used your script, but no good news
    Did not help at all.

    Code:
    root@HP-EliteBook:/home/lech/scripts# cat bluereset 
    #!/bin/bash
    
    echo -n "0000:00:1d.0" | sudo tee /sys/bus/pci/drivers/ehci-pci/unbind
    echo -n "0000:00:1d.0" | sudo tee /sys/bus/pci/drivers/ehci-pci/bind
    # Stop the Bluetooth service so no drivers remain in use by it
    service bluetooth stop
    
    # Now remove the drivers
    modprobe -rv btusb # Should make bt icon disappear
    modprobe -rv bnep # This is the driver I suspect the most, but resetting others as well just because I'm paranoid..
    modprobe -rv hidp
    modprobe -rv rfcomm # This should also remove the "bluetooth" with it. If not, remove it manually -
    modprobe -rv bluetooth # Shouldn't be needed. Post back if it gives errors.
    
    # Reload the drivers in reverse sequence
    modprobe -v bluetooth # Not needed if it was removed automatically
    modprobe -v rfcomm
    modprobe -v hidp
    modprobe -v bnep
    modprobe -v btusb # The BT systray icon should return with this
    
    # Now restart the bluetooth service
    service bluetooth start
    
    # Exit root
    echo -n "0000:00:1d.0" | sudo tee /sys/bus/pci/drivers/ehci-pci/unbind
    echo -n "0000:00:1d.0" | sudo tee /sys/bus/pci/drivers/ehci-pci/bind
    #exit
    and the result in dmesg:

    Code:
    [25426.998401] hid-generic 0005:046D:B006.001D: unknown main item tag 0x0
    [25426.998521] input: Dell BT Travel Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/bluetooth/hci0/hci0:12/input35
    [25426.998965] hid-generic 0005:046D:B006.001D: input,hidraw3: BLUETOOTH HID v1.24 Mouse [Dell BT Travel Mouse] on b8:76:3f:db:05:2f
    [25528.754857] hub 2-1:1.0: port 6 disabled by hub (EMI?), re-enabling...
    [25528.841691] usb 2-1.6: reset full-speed USB device number 3 using ehci-pci
    [25528.934977] btusb 2-1.6:1.0: no reset_resume for driver btusb?
    [25528.934985] btusb 2-1.6:1.1: no reset_resume for driver btusb?
    [25528.934996] usb 2-1.6: USB disconnect, device number 3
    [25529.169048] usb 2-1.6: new full-speed USB device number 5 using ehci-pci
    [25529.264854] usb 2-1.6: New USB device found, idVendor=0a5c, idProduct=21e1
    [25529.264862] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [25529.264866] usb 2-1.6: Product: BCM20702A0
    [25529.264869] usb 2-1.6: Manufacturer: Broadcom Corp
    [25529.264872] usb 2-1.6: SerialNumber: B8763FDB052F
    [25534.417021] Bluetooth: hci0 corrupted ACL packet
    [25534.417045] Bluetooth: hci0 ACL packet for unknown connection handle 12
    [25543.895707] ehci-pci 0000:00:1d.0: remove, state 4
    [25543.895715] usb usb2: USB disconnect, device number 1
    [25543.895716] usb 2-1: USB disconnect, device number 2
    [25543.895718] usb 2-1.6: USB disconnect, device number 5
    [25543.915185] ehci-pci 0000:00:1d.0: USB bus 2 deregistered
    [25543.923802] ehci-pci 0000:00:1d.0: setting latency timer to 64
    [25543.923809] ehci-pci 0000:00:1d.0: EHCI Host Controller
    [25543.923816] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
    [25543.923834] ehci-pci 0000:00:1d.0: debug port 2
    [25543.927742] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
    [25543.927755] ehci-pci 0000:00:1d.0: irq 16, io mem 0xd4738000
    [25543.937227] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
    [25543.937291] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
    [25543.937293] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [25543.937294] usb usb2: Product: EHCI Host Controller
    [25543.937295] usb usb2: Manufacturer: Linux 3.8.0-26-generic ehci_hcd
    [25543.937297] usb usb2: SerialNumber: 0000:00:1d.0
    [25543.937403] hub 2-0:1.0: USB hub found
    [25543.937406] hub 2-0:1.0: 3 ports detected
    [25543.973177] usbcore: deregistering interface driver btusb
    [25544.001251] NET: Unregistered protocol family 31
    [25544.015872] Bluetooth: Core ver 2.16
    [25544.015908] NET: Registered protocol family 31
    [25544.015913] Bluetooth: HCI device and connection manager initialized
    [25544.015926] Bluetooth: HCI socket layer initialized
    [25544.015931] Bluetooth: L2CAP socket layer initialized
    [25544.015944] Bluetooth: SCO socket layer initialized
    [25544.025477] Bluetooth: RFCOMM TTY layer initialized
    [25544.025488] Bluetooth: RFCOMM socket layer initialized
    [25544.025490] Bluetooth: RFCOMM ver 1.11
    [25544.030116] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
    [25544.030134] Bluetooth: HIDP socket layer initialized
    [25544.034544] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [25544.034551] Bluetooth: BNEP filters: protocol multicast
    [25544.034567] Bluetooth: BNEP socket layer initialized
    [25544.038015] usbcore: registered new interface driver btusb
    [25544.052385] init: patchram main process (9070) terminated with status 5
    [25544.062393] ehci-pci 0000:00:1d.0: remove, state 1
    [25544.062400] usb usb2: USB disconnect, device number 1
    [25544.066428] ehci-pci 0000:00:1d.0: USB bus 2 deregistered
    [25544.074032] ehci-pci 0000:00:1d.0: setting latency timer to 64
    [25544.074039] ehci-pci 0000:00:1d.0: EHCI Host Controller
    [25544.074044] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
    [25544.074060] ehci-pci 0000:00:1d.0: debug port 2
    [25544.077941] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
    [25544.077950] ehci-pci 0000:00:1d.0: irq 16, io mem 0xd4738000
    [25544.088944] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
    [25544.088985] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
    [25544.088990] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [25544.088994] usb usb2: Product: EHCI Host Controller
    [25544.088997] usb usb2: Manufacturer: Linux 3.8.0-26-generic ehci_hcd
    [25544.089000] usb usb2: SerialNumber: 0000:00:1d.0
    [25544.089225] hub 2-0:1.0: USB hub found
    [25544.089232] hub 2-0:1.0: 3 ports detected
    [25544.400362] usb 2-1: new high-speed USB device number 2 using ehci-pci
    [25544.532432] usb 2-1: New USB device found, idVendor=8087, idProduct=0024
    [25544.532440] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    [25544.532714] hub 2-1:1.0: USB hub found
    [25544.532786] hub 2-1:1.0: 8 ports detected
    [25544.803650] usb 2-1.6: new full-speed USB device number 3 using ehci-pci
    [25544.899222] usb 2-1.6: New USB device found, idVendor=0a5c, idProduct=21e1
    [25544.899230] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [25544.899234] usb 2-1.6: Product: BCM20702A0
    [25544.899237] usb 2-1.6: Manufacturer: Broadcom Corp
    [25544.899240] usb 2-1.6: SerialNumber: B8763FDB052F
    [25547.312679] Bluetooth: hci0 corrupted ACL packet

    as you can see restart happens and hci currpted ACL packets shows up again

  3. #43
    Join Date
    Aug 2007
    Beans
    67

    Re: Bluetooth mouse stops to work after random time Ubuntu 13.04 on laptop

    for me it would be rather now a quation how to make it back in devices list after mouse reinialize itselfe.

    I'm reading now about EMI at this would be more like HW issue with mouse itselfe.
    However linux should reattach it automaticly ,but it does not ..

    this issue is comming back thruout history of linux e.g

    http://forums.fedoraforum.org/archiv.../t-244660.html
    http://forums.m-audio.com/archive/in...p/t-16441.html

    or even recent :

    https://bbs.archlinux.org/viewtopic.php?id=163730

    have not found yet if anyone solve it ...

    it all the cases you can see however that bluetooth device is added shortly after, in case of ubuntu this does not happen....!!!
    Last edited by macmus; July 10th, 2013 at 05:42 AM.

  4. #44
    Join Date
    Aug 2007
    Beans
    67

    Re: Bluetooth mouse stops to work after random time Ubuntu 13.04 on laptop

    Quote Originally Posted by varunendra View Post
    especially after reading the evdev module part. So try both ways, and most important - keep the fingers as well as toes crossed !
    this part is interesting for me:

    Code:
    [  799.457] (II) config/udev: Adding input device Dell BT Travel Mouse (/dev/input/mouse2)
    [  7799.457] (II) No input driver specified, ignoring this device.
    [  7799.457] (II) This device may have been added with another device file.
    [  7799.457] (II) config/udev: Adding input device Dell BT Travel Mouse (/dev/input/event16)
    [  7799.457] (**) Dell BT Travel Mouse: Applying InputClass "evdev pointer catchall"
    why ?

  5. #45
    Join Date
    Aug 2007
    Beans
    67

    Re: Bluetooth mouse stops to work after random time Ubuntu 13.04 on laptop

    i'm continuing my investigation:

    when i move my mouse with blueooth dump i can see:

    Code:
    > ACL data: handle 12 flags 0x02 dlen 12
        L2CAP(d): cid 0x0041 len 8 [psm 0]
          A1 02 00 01 10 00 00 00 
    > ACL data: handle 12 flags 0x02 dlen 12
        L2CAP(d): cid 0x0041 len 8 [psm 0]
          A1 02 00 01 00 00 00 00 
    > ACL data: handle 12 flags 0x02 dlen 12
        L2CAP(d): cid 0x0041 len 8 [psm 0]
          A1 02 00 00 10 00 00 00
    which means handle 12 is a usual receiver.

    when mouse stop working in dmesg I can see:

    Code:
    [29613.906151] Bluetooth: hci0 corrupted ACL packet
    [29613.906173] Bluetooth: hci0 ACL packet for unknown connection handle 12

  6. #46
    Join Date
    Aug 2007
    Beans
    67

    Re: Bluetooth mouse stops to work after random time Ubuntu 13.04 on laptop

    ok few more findings! i think i may found a cause of this but I will need some expert from udev to help me debug it:

    when everthing works we can see (shortly after opening laptop, after coming from suspend)

    Code:
    :  Bus=02 Lev=02 Prnt=02 Port=05 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
    D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
    P:  Vendor=0a5c ProdID=21e1 Rev=01.12
    S:  Manufacturer=Broadcom Corp
    S:  Product=BCM20702A0
    S:  SerialNumber=B8763FDB052F
    C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
    I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
    I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
    I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
    I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)
    
    [30171.941852] usb 1-1.3: reset high-speed USB device number 3 using ehci-pci
    [30172.045501] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    [30172.053486] ata6: SATA link down (SStatus 0 SControl 300)
    [30172.061493] ata5: SATA link down (SStatus 0 SControl 300)
    [30172.105549] usb 2-1.6: reset full-speed USB device number 3 using ehci-pci
    [30172.178762] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
    [30172.181677] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
    [30172.181697] ata2.00: configured for UDMA/100
    [30172.199240] btusb 2-1.6:1.0: no reset_resume for driver btusb?
    [30172.199243] btusb 2-1.6:1.1: no reset_resume for driver btusb?
    [30172.269233] usb 1-1.2: reset full-speed USB device number 6 using ehci-pci
    [30172.391071] psmouse serio1: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10 00 64
    [30173.143630] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
    [30173.666488] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [30173.668074] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
    [30173.669983] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
    [30173.670182] ata1.00: configured for UDMA/133
    Code:
    lech@HP-EliteBook:~$ usb-devices  | grep  Dev#=
    T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 3
    T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 6
    T:  Bus=01 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#=  6 Spd=12  MxCh= 0
    T:  Bus=01 Lev=02 Prnt=02 Port=02 Cnt=02 Dev#=  3 Spd=480 MxCh= 0
    T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 3
    T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 8
    T:  Bus=02 Lev=02 Prnt=02 Port=05 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
    T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 4
    T:  Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 4
    the first 3 is my web cammera:
    Code:
    T:  Bus=01 Lev=02 Prnt=02 Port=02 Cnt=02 Dev#=  3 Spd=480 MxCh= 0
    D:  Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
    P:  Vendor=04f2 ProdID=b2ef Rev=51.72
    S:  Manufacturer=Chicony Electronics Co., Ltd.
    S:  Product=HP HD Webcam [Fixed]
    S:  SerialNumber=SN0001
    C:  #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
    I:  If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
    I:  If#= 1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo
    the other 3 is bluetooth mouse
    bus input
    Code:
    I: Bus=0005 Vendor=046d Product=b006 Version=0124
    N: Name="Dell BT Travel Mouse"
    P: Phys=b8:76:3f:db:05:2f
    S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/bluetooth/hci0/hci0:12/input37
    U: Uniq=00:1f:20:50:01:b4
    H: Handlers=mouse3 event6 
    B: PROP=0
    B: EV=17
    B: KEY=ff0000 0 0 0 0
    B: REL=143
    B: MSC=10
    when its stop working it resets device number 3 and reinisalize the usb chipset BCM20702A0 on as device 5 which causes bluetooth not working.
    That is why my dump got disconencted and because all events seems to be addressed old handler still!

    Code:
    [29607.386090] usb 2-1.6: reset full-speed USB device number 3 using ehci-pci
    [29607.479544] btusb 2-1.6:1.0: no reset_resume for driver btusb?
    [29607.479552] btusb 2-1.6:1.1: no reset_resume for driver btusb?
    [29607.479563] usb 2-1.6: USB disconnect, device number 3
    [29607.693517] usb 2-1.6: new full-speed USB device number 5 using ehci-pci
    [29607.789069] usb 2-1.6: New USB device found, idVendor=0a5c, idProduct=21e1
    [29607.789072] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [29607.789074] usb 2-1.6: Product: BCM20702A0
    [29607.789076] usb 2-1.6: Manufacturer: Broadcom Corp
    [29607.789077] usb 2-1.6: SerialNumber: B8763FDB052F
    [29613.906151] Bluetooth: hci0 corrupted ACL packet
    bluetooth chipset moved to Dev #5
    Code:
    T:  Bus=02 Lev=02 Prnt=02 Port=05 Cnt=01 Dev#=  5 Spd=12  MxCh= 0
    D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
    P:  Vendor=0a5c ProdID=21e1 Rev=01.12
    S:  Manufacturer=Broadcom Corp
    S:  Product=BCM20702A0
    S:  SerialNumber=B8763FDB052F
    C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
    I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
    I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
    I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
    I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)
    Code:
    root@HP-EliteBook:/home/lech/scripts# usb-devices | grep Dev
    T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 3
    T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 6
    T:  Bus=01 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#=  6 Spd=12  MxCh= 0
    T:  Bus=01 Lev=02 Prnt=02 Port=02 Cnt=02 Dev#=  3 Spd=480 MxCh= 0
    T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 3
    T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 8
    T:  Bus=02 Lev=02 Prnt=02 Port=05 Cnt=01 Dev#=  5 Spd=12  MxCh= 0
    T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 4
    T:  Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 4
    when I close/open lid is again become Dev 3 and mouse starts responding again (and we go to begning of this post )

    I see couple ofthings here:

    1. EMI is cased because WebCamera and Bluetooth chipset is defined as some Device #3
    2. Bluetooth stops responding becasue new device is diffrent then old one after reasiging

    Solution: ( I have no idea how to do it!! )

    1. Make WebCamera diffrent ID then Bluetooth and check if it causes EMI
    2. Remove Camera and check it it casues EMI. (it's build in so i don't know how to do it )
    3. Move Bluetooth to diffrent ID and check if after bluetooth will work!
    4. Make Bluetooth go back to Dev #3 to check if mouse work again.

    HELP i am so close now
    Last edited by macmus; July 10th, 2013 at 07:31 AM.

  7. #47
    Join Date
    Mar 2010
    Location
    India
    Beans
    8,149
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Bluetooth mouse stops to work after random time Ubuntu 13.04 on laptop

    Wow ! I'm getting dizzy
    You made me do quite some experimenting before posting..
    Quote Originally Posted by macmus View Post
    Ok i used your script, but no good news
    [/code]
    I wasn't expecting that you'll quickly turn it into a script. Although everything as per dmesg is happening as expected, I think we should give some time to certain operations. I'd suggest to insert "sleep 6" in-between 'unbind-bind' commands both times, after "service bt stop", after unloading the last module, and after "service bt start". Although sleep time 2 to 4 seconds should be sufficient, we are desperate here and don't want to take chance (given all the clues you dug up, this may seem futile, but, we ARE desperate !).

    Quote Originally Posted by macmus View Post
    this part is interesting for me:

    Code:
    [  799.457] (II) config/udev: Adding input device Dell BT Travel Mouse (/dev/input/mouse2)
    [  7799.457] (II) No input driver specified, ignoring this device.
    [  7799.457] (II) This device may have been added with another device file.
    [  7799.457] (II) config/udev: Adding input device Dell BT Travel Mouse (/dev/input/event16)
    [  7799.457] (**) Dell BT Travel Mouse: Applying InputClass "evdev pointer catchall"
    why ?
    I noticed that earlier. To me it seems like a routine 'check, probe & move on' type device probing event, where finally the device gets correctly identified and associated with the correct driver 'evdev'.

    Quote Originally Posted by macmus View Post
    Code:
    [29613.906151] Bluetooth: hci0 corrupted ACL packet
    [29613.906173] Bluetooth: hci0 ACL packet for unknown connection handle 12
    This is typically an indication/symptom of bt connection failure, but I don't think it tells anything more than that.

    Quote Originally Posted by macmus View Post
    the first 3 is my web cammera:
    ....
    the other 3 is bluetooth mouse
    Nope! The other 3 is your internal bluetooth adapter, not the mouse (see usb-devices).

    Quote Originally Posted by macmus View Post
    when its stop working it resets device number 3 and reinisalize the usb chipset BCM20702A0 on as device 5 which causes bluetooth not working.
    That is why my dump got disconencted and because all events seems to be addressed old handler still!

    Code:
    [29607.386090] usb 2-1.6: reset full-speed USB device number 3 using ehci-pci
    [29607.479544] btusb 2-1.6:1.0: no reset_resume for driver btusb?
    [29607.479552] btusb 2-1.6:1.1: no reset_resume for driver btusb?
    [29607.479563] usb 2-1.6: USB disconnect, device number 3
    [29607.693517] usb 2-1.6: new full-speed USB device number 5 using ehci-pci
    [29607.789069] usb 2-1.6: New USB device found, idVendor=0a5c, idProduct=21e1
    [29607.789072] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [29607.789074] usb 2-1.6: Product: BCM20702A0
    [29607.789076] usb 2-1.6: Manufacturer: Broadcom Corp
    [29607.789077] usb 2-1.6: SerialNumber: B8763FDB052F
    [29613.906151] Bluetooth: hci0 corrupted ACL packet
    bluetooth chipset moved to Dev #5
    That behaviour is same as removing a usb device from a port, then plugging it back. Its device no. will change, but it doesn't mean it won't work properly. Your bt adapter is just like a usb device, only connected internally. I'm quite positive that once you do the hub reset, the device id should get reset (to 3) too.

    As per the dmesg part above, it seems like the bt adapter was reset properly and should work properly afterwards. The corrupt ACL packet may be an indication that either the adapter itself, or the device sending those packets (mouse??) is not yet reset properly. If you have another bt device, like a mobile phone, you may experiment with its connection to see whether it works after the new dev id is assigned to the adapter. If it does, it would mean that the adapter is being reset properly. Keep in mind that once a bluetooth connection is interrupted, it needs to be re-established and that may require that the external device is reset too (implying a power reset on devices like mouse where you have no other way to re-initiate a connection).

    Quote Originally Posted by macmus View Post
    when I close/open lid is again become Dev 3 and mouse starts responding again (and we go to begning of this post )

    I see couple ofthings here:

    1. EMI is cased because WebCamera and Bluetooth chipset is defined as some Device #3
    2. Bluetooth stops responding becasue new device is diffrent then old one after reasiging
    On a sleep-wake cycle, the usb devices are put to sleep and reset again, something like we are doing with our unbind-bind cycle. Obviously a sleep-wake cycle does a lot more than that and some part of it is helping the case. But I'm quite sure it is not the device id that is causing trouble. Furthermore -

    1. Not only the device no, but the bus no. is also taken into consideration, and no two devices can have same device no in that perspective (at lease one of the no. or bus will be different)

    2. Nope. The new dev no. (remember - it is the internal bt adapter, not the mouse) is a result of the device reset, not the cause of the problem (unless it fails to properly reset).

    However, despite these misunderstandings, I'm interested in your solution part -

    Quote Originally Posted by macmus View Post
    Solution: ( I have no idea how to do it!! )

    1. Make WebCamera diffrent ID then Bluetooth and check if it causes EMI
    2. Remove Camera and check it it casues EMI. (it's build in so i don't know how to do it )
    3. Move Bluetooth to diffrent ID and check if after bluetooth will work!
    4. Make Bluetooth go back to Dev #3 to check if mouse work again.
    1. Try (I'm picking IDs from your outputs, but you still may have to correct addresses like you had to with 'ehci_hcd')-
    Code:
    echo -n "1-1.3:1.0" | sudo tee /sys/bus/usb/drivers/uvcvideo/unbind
    echo -n "1-1.3:1.0" | sudo tee /sys/bus/usb/drivers/uvcvideo/bind
    Keep a gap of at least 4 seconds between both, then check usb-devices to see if the dev no. changed.

    2. Don't use the 'bind' command in above. Simple as that

    3. Do the same as 1 above, with bt driver (btusb) and the adapter's ID -
    Code:
    echo -n "2-1.6:1.0" | sudo tee /sys/bus/usb/drivers/btusb/unbind
    echo -n "2-1.6:1.0" | sudo tee /sys/bus/usb/drivers/btusb/bind
    4 second gap as above, then check usb-devices.

    4. Do the usual unbind-bind cycle that we have been doing (with the hub). Check usb-devices and I'm sure you'll get your wish. Not with the mouse functionality though, only with the dev no.

    Let me know if you have success with any of them.
    Varun
    Help others by marking threads as [SOLVED], if they are. (See how)
    Wireless Script | Use Code Tags

  8. #48
    Join Date
    Aug 2007
    Beans
    67

    Re: Bluetooth mouse stops to work after random time Ubuntu 13.04 on laptop

    Quote Originally Posted by varunendra View Post

    1. Try (I'm picking IDs from your outputs, but you still may have to correct addresses like you had to with 'ehci_hcd')-
    Code:
    echo -n "1-1.3:1.0" | sudo tee /sys/bus/usb/drivers/uvcvideo/unbind
    echo -n "1-1.3:1.0" | sudo tee /sys/bus/usb/drivers/uvcvideo/bind
    Keep a gap of at least 4 seconds between both, then check usb-devices to see if the dev no. changed.
    when I do unbind something is unbinding but that isn't WebCamera. It simply does not disapears from device list.
    When i do bind WebCamera does not change its device ID

  9. #49
    Join Date
    Mar 2010
    Location
    India
    Beans
    8,149
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Bluetooth mouse stops to work after random time Ubuntu 13.04 on laptop

    I picked up that ID from post #5 -
    S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input14
    Before you try the above command, check "cat /proc/but/input/devices" to see if the camera is listed and is on the same bus/port, then you may also check "ls /sys/bus/usb/drivers/uvcvideo/" to confirm that "1-1.3:1.0" exists there. (I wrote all of the above behaviours after testing on my lappy here).
    Last edited by varunendra; July 10th, 2013 at 05:52 PM.
    Varun
    Help others by marking threads as [SOLVED], if they are. (See how)
    Wireless Script | Use Code Tags

  10. #50
    Join Date
    Aug 2007
    Beans
    67

    Re: Bluetooth mouse stops to work after random time Ubuntu 13.04 on laptop

    this is what is see there

    Code:
    I: Bus=0003 Vendor=04f2 Product=b2ef Version=5172
    N: Name="HP HD Webcam [Fixed]"
    P: Phys=usb-0000:00:1a.0-1.3/button
    S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input17
    U: Uniq=
    H: Handlers=kbd event17 
    B: PROP=0
    B: EV=3
    B: KEY=100000 0 0 0
    Code:
    lech@HP-EliteBook:~$ ls /sys/bus/usb/drivers/uvcvideo
    1-1.3:1.0  1-1.3:1.1  bind  module  new_id  remove_id  uevent  unbind
    it seems what you wrote is correct?

Page 5 of 6 FirstFirst ... 3456 LastLast

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
  •