Comment 3 for bug 1506774

There is nothing we can do from bluez side. If the kernel interface we need to do *any* work is not available we can't do anything else but fail. The "bluetooth" module needs to be loaded or the kernel compiled with CONFIG_BT=y rather than CONFIG_BT=m.

Is there any reason not to compile bluetooth support directly into the kernel? Any driver can still be loaded as module but the subsystem should be always available.