timower/rM-docker

Override rm2fb service

Opened this issue · 4 comments

Eeems commented

I would recommend overriding the rm2fb service with some sort of dummy so that packages that install with toltec that depend on it will not error out.

Eeems commented

It might make sense to override it to run rm2fb-forward instead of rm2fb and have it installed by default.

Eeems commented

Another option would be to package rm2fb-forward as a toltec package that provides the display package and install that

Is this about this issue?

# systemctl status rm2fb.service
● rm2fb.service - reMarkable 2 Framebuffer Server
     Loaded: loaded (/lib/systemd/system/rm2fb.service; disabled; vendor preset: disabled)
     Active: inactive (dead)

Oct 09 13:47:07 reMarkable systemd[1]: [[0;1;31m[[0;1;39m[[0;1;31mFailed to start reMarkable 2 Framebuffer Server.[[0m
Oct 09 13:47:10 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server.
Oct 09 13:53:53 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server...
Oct 09 13:53:54 reMarkable xochitl[2568]: STARTING RM2FB
Oct 09 13:53:54 reMarkable xochitl[2568]: Missing address for function 'getInstance'
Oct 09 13:53:54 reMarkable xochitl[2568]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18
Oct 09 13:53:54 reMarkable systemd[1]: [[0;1;39m[[0;1;31m[[0;1;39mrm2fb.service: Main process exited, code=exited, status=255/EXCEPTION[[0m
Oct 09 13:53:54 reMarkable systemd[1]: [[0;1;38;5;185m[[0;1;39m[[0;1;38;5;185mrm2fb.service: Failed with result 'exit-code'.[[0m
Oct 09 13:53:54 reMarkable systemd[1]: [[0;1;31m[[0;1;39m[[0;1;31mFailed to start reMarkable 2 Framebuffer Server.[[0m
Oct 09 13:53:57 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server.

meaning my error cannot be fixed by patching support for

ARG fw_version=3.5.2.1807
?

Eeems commented

No, this is because there is no need for the rm2fb service if using the forwarder. The "issue" you are encountering is because rm2fb doesn't support the OS version you are using.