- #USING A MICROSOFT WIRELESS MOUSE 1000 ON A LINUX MACHINE MAC OS#
- #USING A MICROSOFT WIRELESS MOUSE 1000 ON A LINUX MACHINE FULL#
- #USING A MICROSOFT WIRELESS MOUSE 1000 ON A LINUX MACHINE WINDOWS 10#
- #USING A MICROSOFT WIRELESS MOUSE 1000 ON A LINUX MACHINE BLUETOOTH#
#USING A MICROSOFT WIRELESS MOUSE 1000 ON A LINUX MACHINE FULL#
Open Nautilus via terminal with su for full root:Ĥ/. Using regedit (In the result left click to enable administrator rights) go to - HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\BTHPORT\Parameters\keys\computer MAC\device MAC.ģ/. This is helpful in determining the computer and device addresses for use in changing the Windows LinkKey.
#USING A MICROSOFT WIRELESS MOUSE 1000 ON A LINUX MACHINE BLUETOOTH#
Save a copy of the bluetooth keys to a USB stick then print it. This should work in other Debian systems and perhaps for other bluetooth devices.ġ/.
#USING A MICROSOFT WIRELESS MOUSE 1000 ON A LINUX MACHINE WINDOWS 10#
This is an alternative to enable the same bluetooth mouse to work on both Windows 10 and Kubuntu 17.10. There is a long list of suggestions on this topic most are old and are complicated to follow. I think it's safer to work on a copy of the SYSTEM registry file too, just in case something goes wrong.īluetooth Mouse with Windows 10 and K/Ubuntu 17.10 Dual Boot – HP Z5000 Bluetooth Mouse It's probably a bit complex for people who are not comfortable editing config files. (It doesn't seem to work before being logged on either, but that the same, it was happening even with being paired under Linux only. I had to disconnect and reconnect (via the Gnome applet), but I had to do that sometimes anyway. Here, xx xx xx is another 16 bytes, in hexadecimal, represented the link key set up in Windows.įinally, I copied that (and removed the spaces) to replace the value already in /var/lib/bluetooth/AA:11:11:11:11:11/linkkeys. I've then opened it with chntpw (browse registry with ls/ cd help with ?):Ĭd ControlSet002\services\BTHPORT\Parameters\Keys To avoid unwanted modifications of the Windows registry from Linux, I've copied the SYSTEM file somewhere else, from: /path/to/Windows/System32/config/SYSTEM The latest version in the Debian repo (v0.99.6-2 as of writing) worked for me. The version packaged with Lucid v0.99.5 doesn't seem to support registry in 64-bit. (I suppose it might be in another ControlSet in some cases.) Unfortunately, RegEdit says "access is denied" when I get to Keys, even when logged on as administrator. In my case, it was in this registry entry: Pair the device normally, under Windows (this will change the key). Here, xxxx is 16 bytes written continuously in hexadecimal, that's the link key. There should be a file called /var/lib/bluetooth/AA:11:11:11:11:11/linkkeys, which contains a line like this:īB:22:22:22:22:22 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 0 6 Here is what I did:įind the bluetooth address of the PC/dongle (let's say AA:11:11:11:11:11).Find the bluetooth address of the keyboard (let's say BB:22:22:22:22:22).Pair the device normally, under Linux (via the Gnome panel). Hi, I got it to work with mine, by copying the bluetooth link key. You might have been able to find a solution by now.
#USING A MICROSOFT WIRELESS MOUSE 1000 ON A LINUX MACHINE MAC OS#
If you extracted the link key from Mac OS you'll need to reverse the byte order of the key. When you turn on the device, a popup should appear, asking if you want to authorize the connecting bluetooth device. Save, and restart bluetoothd: sudo service bluetooth restart Now check the section and set Trusted=false sudo nano /var/lib/bluetooth/XX:XX:XX:XX:XX:XX/YY:YY:YY:YY:YY:YY/info You should find a file named 'info' there. Go to the subfolder that is named after the device's address. This might trigger anti brute-forcing measures rendering the device unreachable. Otherwise it will try to connect to the device repeatedly with the old (and now invalid) link key. Make sure to have your device turned off when booting linux.