Does the installation stop at that point, or does it get to the final message: "install rtk_btusb success!"
The particular messages that you've listed simply mean that the system is not currently running/have installed the bluetooth drivers that you are about to replace/install. They are not "failure" messages in that if they are shown it does not mean that the new Edimax bluetooth driver is unable to be installed. It simply means that the new driver is not replacing an existing/already in use driver.
If you are not getting to the final message above, can you please post the full set of messages you see when you type "sudo make install -s"? It's highly likely that any "real" issue with the install is actually somewhat higher up in the output messages (i.e. during the "make" part rather than during the "install" part).
Edit: I think your update came in while I was replying. What I think happened is that it probably did work yesterday, you just didn't have the device drivers already in use. Having installed it the first time, the next time you tried it would have been able to replace the drivers you had actually installed the first time. Very glad to hear it is working for you. :)
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
branchandroot
Re: Problem
Date: 2017-06-14 07:44 am (UTC)"install rtk_btusb success!"
The particular messages that you've listed simply mean that the system is not currently running/have installed the bluetooth drivers that you are about to replace/install. They are not "failure" messages in that if they are shown it does not mean that the new Edimax bluetooth driver is unable to be installed. It simply means that the new driver is not replacing an existing/already in use driver.
If you are not getting to the final message above, can you please post the full set of messages you see when you type "sudo make install -s"? It's highly likely that any "real" issue with the install is actually somewhat higher up in the output messages (i.e. during the "make" part rather than during the "install" part).
Edit: I think your update came in while I was replying. What I think happened is that it probably did work yesterday, you just didn't have the device drivers already in use. Having installed it the first time, the next time you tried it would have been able to replace the drivers you had actually installed the first time. Very glad to hear it is working for you. :)