dev-input-event* device units are not immediately available after install and need rebooting

[lambada]

Just updated from 2.9 to 2.10 (having updated toltec and packages to most recent stable release before doing so) and remux didn't manage to start

toltecctl reenable hit a problem with removing remux initially

[...]
Disabling remux
Failed to disable unit: Unit file remux.service does not exist.
[...]

Which is weird, but seeing as it was trying to disable it before removing it anyway seems harmless.

It then proceeded to reinstall packages seemingly fine, and upon running the systemctl enable --now remux command afterwards, as the output instructs, it failed to start with A dependency job for remux.service failed. See 'journalctl -xe' for details. journalctl seems to indicate it's the dev-input-event0 device

Oct 25 19:29:49 reMarkable systemd[1]: [[0;1;39m[[0;1;31m[[0;1;39mremux.service: Job remux.service/start failed with res
ult 'dependency'.[[0m
Oct 25 19:29:49 reMarkable systemd[1]: [[0;1;39m[[0;1;31m[[0;1;39mdev-input-event0.device: Job dev-input-event0.device/s
tart failed with result 'timeout'.[[0m

For which

Oct 25 19:29:49 reMarkable systemd[1]: [[0;1;31m[[0;1;39m[[0;1;31mTimed out waiting for device /dev/input/event0.[[0m
Oct 25 19:29:49 reMarkable systemd[1]: [[0;1;39m[[0;1;31m[[0;1;39mdev-input-event0.device: Job dev-input-event0.device/s
tart failed with result 'timeout'.[[0m

Trying to recover with opkg remove remux followed by opkg install remux then systemctl enable --now remux resulted in the same situation.

I'm about to see if going nuclear and toltec uninstall and then reinstalling from scratch works; but it's safe to say that there's something funky going on with toltecctl reenable

[lambada]

I unfortunately don't have full log files- it appears that windows cmd doesn't play nicely with journalctl and the like, and it's decided to eat most of the toltecctl reenable output.

[lambada]

toltec uninstall
# confirm reboot
# follow instructions on website to reinstall
exec bash -l  # To get a fresh login shell as per install instructions
opkg install remux
systemctl enable --now remux # As per install output

Resulted in

Created symlink /etc/systemd/system/multi-user.target.wants/remux.service → /lib/systemd/system/remux.service.

A dependency job for remux.service failed. See 'journalctl -xe' for details.

Crud. Maybe it's a remux on 2.10 issue? Same journalctl problem of waiting for device

[lambada]

Switched back to the parition with 2.9 on it, and it's working again.

[Eeems]

@raisjn @matteodelabre This might be the input devices again. Probably a reboot will resolve it, but it's rather annoying that it keeps happening for users.

[lambada]

Interesting idea! I'll switch my partitions back and give a reboot a try after reproduing the failure again. If that is the case a 'trivial' fix might be to get the install message to say to reboot the device in addition to saying to run the systemctl enable --now remux

[lambada]

Switching the partitions back and doing a reboot means the 2.10.1 version works fine. I think a note alongside the one about running systemctl, saying that a reboot is required should make this clear to the end user.

[Eeems]

While a note to do a reboot will probably resolve the issue with remux here, I'd prefer we properly resolve the issue so no reboot is required.