On Wed, 2019-01-02 at 15:21 +0000, Ian Campbell wrote:
> On Wed, 2019-01-02 at 15:14 +0000, Ian Campbell wrote:
> > > But after booting the buster kernel qcontrol could setup
> > > successfully:
> >
> > I wonder if it is the reboot itself, and not necessarily the switch
> > to
> > the buster kernel which is the bandaid here, i.e. if rebooting back
> > into the stretch kernel would work too.
>
> In fact I also wonder if:
> udevadm control --reload-rules && dpkg --configure -a
>
> would do the trick, indicating that the reload is what is missing.
Probably not, according to [0] which mentions that udev monitors the
directory and does so automatically (which is what I expected).
That mail does mention `udevadm trigger` to apply new rules to existing
devices though -- that does sound like it might apply here, so I wonder
if:
udevadm trigger -s platform -y gpio_keys && dpkg --configure -a
Does what is required... I have a strong feeling it will and so it
should be done from the qcontrol postinst.
Ian.
[0] https://lists.debian.org/debian-devel/2018/06/msg00047.html
