By the way, I just confirmed that disabling "asus-nb-wmi" allows me to bring hci0 up and use the bluetooth module.
The command sequence is the following:
`sudo rmmod asus-nb-wmi`
`sudo rfkill unblock bluetooth` (this would usually completely disconnect the bluetooth module)
`sudo hciconfig hci0 up`
At this time, you can use Bluez normally. Of course, the side effect of removing "asus-nb-wmi" is that I lose all the "function-keys" (Brightness control, volume control, etc). As soon as I bring this module back up with modprobe, the bluetooth module is disconnected again.
By the way, I just confirmed that disabling "asus-nb-wmi" allows me to bring hci0 up and use the bluetooth module.
The command sequence is the following:
`sudo rmmod asus-nb-wmi`
`sudo rfkill unblock bluetooth` (this would usually completely disconnect the bluetooth module)
`sudo hciconfig hci0 up`
At this time, you can use Bluez normally. Of course, the side effect of removing "asus-nb-wmi" is that I lose all the "function-keys" (Brightness control, volume control, etc). As soon as I bring this module back up with modprobe, the bluetooth module is disconnected again.
I got this information from this comment at ask-Ubuntu: askubuntu. com/a/541546/ 25561
http://
Does this mean that we should file a bug report for asus-nb-wmi module?