https://bugzilla.kernel.org/show_bug.cgi?id=104011 --- Comment #6 from Robert R. Howell <rhowell@xxxxxxxx> --- I did just test using the bluetoothctl power off / power on sequence. After doing that, pairing DOES in fact work properly with a stock (as far as bluetooth is concerned) 4.2 kernel. The mouse then works well until I reboot. I've tested this both on an ASUS T100 and also on an ASUS G750. I'll need to do more investigating to understand why the adapter was powered on in legacy mode and how I can change that. If you have any suggestions I'd appreciate those. I do run into the following complications after a reboot. The g750 ones are "minor" but may indicate some further patches are needed. The T100 ones are more serious, but those are presumably because I'm currently "manually" using "hciconf hci0 up", which you say will cause problems. The following may be more than you need to know, but in case it is useful, here's more detail on the two machines and their different behavior: On the G750, once I establish a good pairing then reboot, I do NOT need to repeat the bluetoothctl power off / power on sequence again. The bluetooth mouse connection just succeeds automatically after the reboot. However dmesg DOES show that the "SMP security requested but not available" message has been output. After a reboot on the T100 the mouse does NOT work. The bluetoothctl info command claims it is connected, but the mouse does not appear in the xinput device list. Powering the controller off then on then trying to reconnect does not seem to help. I need to start from scratch by removing the pairing then redoing that pairing. On both machines I'm running openSUSE 13.2 KDE with bluez 5.23-1.1 (from the openSUSE distribution) and bluedevil 2.1.1-2.5.1 from openSUSE update. Even before the recent issue with the MX Anywhere 2, getting ANY bluetooth to run on the G750 was a bit of a struggle, mostly involving extracting and installing BCM20702A1 firmware. There were a number of false steps getting to that point so I could have mangled the configuration somehow. Getting bluetooth running on the T100 was even more complicated as it is a relatively new Baytrail tablet with lots of gaps in linux hardware support. Following advice on various forums, I first use brcm_patchram_plus to load an hcd file and set the MAC address. I then use hciattach to connect the bluetooth software to the bcm chip through the Baytrail /dev/ttyS4 port. Finally, I use hciconfig hci0 up to bring up the bluetooth interface. If there is a new alternative to the last one or two commands which will properly initialize SMP, could you let me know? Thanks for the advice. Let me know if there are further tests which would be useful. -- You are receiving this mail because: You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
