Control: tags -1 + moreinfo
Hi On Thu, 25 Feb 2016 23:23:31 +0100 Josua Mayer <josua.maye...@gmail.com> wrote: > Package: systemd > Version: 215-17+deb8u3 > Severity: normal > > Dear Maintainers, > > I noticed that rfkill state for both wifi and bluetooth is not restored > on reboots on Hummingboard and Cubox-i. > > 1) Let me focus on wifi first: > The behaviour I see is: > it always starts up soft-blocked no matter if I unblocked it before > rebooting, or not. > In /var/lib/systemd/rfkill a state-file is created which shows 1 if wifi > was blocked before last reboot, and 0 if it was unblocked. > > So I conclude that saving the state works fine. > So I investigated the status of systemd-rfkill@rfkill0.service, and > found that its reported to have exited without error. > > --> I guess that systemd tries to restore therfkill state too early, > that is before the actual rfkill device / wifi device is properly > initialized. (is this #809323 ?) > > There is still a ghost around here, as I got the state restored properly > at least once now, without changing *anything* at all. > > 2) Bluetooth: > There is no state-file created in /var/lib/systemd/rfkill for the > bluetooth device. > But I should add that this specific bluetooth chip requires manualy > loading firmware from userspace, and only then it comes up. Is this problem still reproducible with recent version of systemd? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
