When more than one bluetooth interface is desired and a user connects a USB bluetooth dongle to the Raspberry Pi, the onboard bluetooth interface will fail to be configured after the first reboot and every boot after that. This is due to the btuart script making the erronious assumption that the on-board bluetooth will be configured via UART prior to any USB bluetooth interfaces and thus recieve the interface number: hci0. Currently the btuart script checks whether hci0 is present and exits the script if it exists, without confirming whether it is indeed the onboard chip.
To fix this, the MAC addresses of the available interfaces are compared to the known MAC prefixes of the Raspberry Pi Foundation and if any matches are found, the btuart script exits. Otherwise, the script proceeds and properly configures the onboard bluetooth interface.
When more than one bluetooth interface is desired and a user connects a USB bluetooth dongle to the Raspberry Pi, the onboard bluetooth interface will fail to be configured after the first reboot and every boot after that. This is due to the btuart script making the erronious assumption that the on-board bluetooth will be configured via UART prior to any USB bluetooth interfaces and thus recieve the interface number: hci0. Currently the btuart script checks whether hci0 is present and exits the script if it exists, without confirming whether it is indeed the onboard chip.
To fix this, the MAC addresses of the available interfaces are compared to the known MAC prefixes of the Raspberry Pi Foundation and if any matches are found, the btuart script exits. Otherwise, the script proceeds and properly configures the onboard bluetooth interface.