Hi Thomas, > > this is a really old dongle. > Don't know exactly, about 4 years I guess. It's from the first DiNovo > Media Desktop (neither Laser nor 2.0). > > > Check hciconfig hci0 revision (as root) if > > it is either a BlueCore01 or BlueCore02. > | thomas@Majestix:~$ sudo hciconfig hci0 revision > | hci0: Type: USB > | BD Address: 00:07:61:19:49:79 ACL MTU: 192:8 SCO MTU: 64:8 > | Build 846 > | Chip version: BlueCore02-External > | Max key size: 56 bit > | SCO mapping: HCI > > > No idea why the Default Link Policy commands is not implemented here. > > That is really strange. > Isn't there some other way to get smooth communication with my MX900? > After all, the Bluetooth Travel Mouse works fine with the exact same > dongle after just reconnecting it. not really. It is tricky and I am not willing to go back to the per connection link policy setup, because that interferes with how with setup Bluetooth 2.1 devices. Problem is that this particular firmware is a custom build for Logitech (or beta firmware) as it looks like. Also you have other problems with not having AFH enabled when you have WiFi around. I think that I do have the exact same mouse and keyboard at home somewhere. But not supporting Default Link Policy is just pure stupid. Regards Marcel -- 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
