This seems a lot like a user space race. bluez is trying to do stuff with the driver before the firmware is loaded. Is there a way to construct the udev rule such that bluez doesn't get started until after the firmware load is done ?
This seems a lot like a user space race. bluez is trying to do stuff with the driver before the firmware is loaded. Is there a way to construct the udev rule such that bluez doesn't get started until after the firmware load is done ?