2014-11-20 20:34 GMT+01:00 Dan Williams <d...@redhat.com>: > On Thu, 2014-11-20 at 14:56 +0100, Michael Biebl wrote: >> I had some rather "interesting" experience with the rfkill service as well. >> See [1]. Basically, running rfkill on one device, made the other device go >> away. > > That's normal behavior in the case of a platform rfkill device and a > device-specific rfkill device. The platform rfkill functionality can > sometimes (often?) cut power to the device through BIOS and GPIOs, and > it will drop off the USB or PCI bus. But the device itself can also > expose rfkill functionality through it's own drivers, that doesn't cause > it to drop off the bus. This is your case with the USB-based Bluetooth > device and the BIOS-based platform killswitch. > > Since the routing of all these rfkills is highly model specific, there > is no way to know that the platform rfkill has an affect on any other > device in a generic way. That would have to be hardcoded into the > kernel and would be pretty awful to maintain.
Thanks for the detailed explanation. Any suggestion how we can address that in systemd-rfkill or its service file? It's kinda ugly if you get a failed service because of that and having the system state be reported as "degraded". -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
