search

ddvk / remarkable2-framebuffer

remarkable2 framebuffer reversing
MIT License
270 stars 22 forks source link

opkg install display failed #105

Closed glyh closed 1 year ago

glyh commented 1 year ago

Here's the error message:

Package display (1:0.0.20-1) installed in root is up to date.
Configuring display.
Job for rm2fb.service failed because the control process exited with error code.
See "systemctl status rm2fb.service" and "journalctl -xe" for details.
Collected errors:
 * pkg_run_script: package "display" postinst script returned status 1.
 * opkg_configure: display.postinst returned 1.

systemctl status rm2fb.service

● rm2fb.service - reMarkable 2 Framebuffer Server
     Loaded: loaded (/lib/systemd/system/rm2fb.service; enabled; vendor preset: disabled)
     Active: activating (auto-restart) (Result: exit-code) since Tue 2022-09-06 00:04:48 UTC; 2s ago
    Process: 349 ExecStart=/usr/bin/xochitl [[0;1;31m(code=exited, status=255/EXCEPTION)[[0m
   Main PID: 349 (code=exited, status=255/EXCEPTION)

journalctl -xe

logs ``` -- Logs begin at Sun 2022-09-04 23:13:07 UTC, end at Tue 2022-09-06 00:07:38 UTC. -- Sep 06 00:01:56 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:01:56 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 4487 and the job result is failed. Sep 06 00:01:58 reMarkable xochitl[230]: 00:01:58.508 rm.wifi Scanning: false Sep 06 00:02:04 reMarkable xochitl[230]: 00:02:04.589 rm.wifi Scanning: true Sep 06 00:02:08 reMarkable xochitl[230]: 00:02:08.501 rm.wifi Scanning: false Sep 06 00:02:14 reMarkable xochitl[230]: 00:02:14.589 rm.wifi Scanning: true Sep 06 00:02:18 reMarkable xochitl[230]: 00:02:18.502 rm.wifi Scanning: false Sep 06 00:02:24 reMarkable xochitl[230]: 00:02:24.590 rm.wifi Scanning: true Sep 06 00:02:28 reMarkable xochitl[230]: 00:02:28.431 rm.wifi Scanning: false Sep 06 00:02:34 reMarkable xochitl[230]: 00:02:34.590 rm.wifi Scanning: true Sep 06 00:02:38 reMarkable xochitl[230]: 00:02:38.501 rm.wifi Scanning: false Sep 06 00:02:44 reMarkable xochitl[230]: 00:02:44.590 rm.wifi Scanning: true Sep 06 00:02:46 reMarkable systemd[1]: Reloading. Sep 06 00:02:46 reMarkable systemd[1]: /etc/systemd/system.conf.d/10-qt-env.conf:1: Assignment outside of section. Ignoring. Sep 06 00:02:46 reMarkable systemd[1]: sync.service: Service has a D-Bus service name specified, but is not of type dbus. Ignoring. Sep 06 00:02:47 reMarkable systemd[1]: Reloading. Sep 06 00:02:47 reMarkable systemd[1]: /etc/systemd/system.conf.d/10-qt-env.conf:1: Assignment outside of section. Ignoring. Sep 06 00:02:47 reMarkable systemd[1]: sync.service: Service has a D-Bus service name specified, but is not of type dbus. Ignoring. Sep 06 00:02:48 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 4561. Sep 06 00:02:48 reMarkable xochitl[4154]: STARTING RM2FB Sep 06 00:02:48 reMarkable xochitl[4154]: Missing address for function 'getInstance' Sep 06 00:02:48 reMarkable xochitl[4154]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:02:48 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:02:48 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:02:48 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 4561 and the job result is failed. Sep 06 00:02:48 reMarkable xochitl[230]: 00:02:48.436 rm.wifi Scanning: false Sep 06 00:02:53 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 1. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:02:53 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 4635 and the job result is done. Sep 06 00:02:53 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 4635. Sep 06 00:02:53 reMarkable xochitl[4155]: STARTING RM2FB Sep 06 00:02:53 reMarkable xochitl[4155]: Missing address for function 'getInstance' Sep 06 00:02:53 reMarkable xochitl[4155]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:02:53 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:02:53 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:02:53 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 4635 and the job result is failed. Sep 06 00:02:54 reMarkable xochitl[230]: 00:02:54.590 rm.wifi Scanning: true Sep 06 00:02:58 reMarkable xochitl[230]: 00:02:58.441 rm.wifi Scanning: false Sep 06 00:02:58 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 2. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:02:58 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 4709 and the job result is done. Sep 06 00:02:58 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 4709. Sep 06 00:02:58 reMarkable xochitl[4156]: STARTING RM2FB Sep 06 00:02:58 reMarkable xochitl[4156]: Missing address for function 'getInstance' Sep 06 00:02:58 reMarkable xochitl[4156]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:02:58 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:02:58 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:02:58 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 4709 and the job result is failed. Sep 06 00:03:03 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 3. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:03:03 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 4783 and the job result is done. Sep 06 00:03:03 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 4783. Sep 06 00:03:04 reMarkable xochitl[4157]: STARTING RM2FB Sep 06 00:03:04 reMarkable xochitl[4157]: Missing address for function 'getInstance' Sep 06 00:03:04 reMarkable xochitl[4157]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:03:04 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:03:04 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:03:04 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 4783 and the job result is failed. Sep 06 00:03:04 reMarkable xochitl[230]: 00:03:04.590 rm.wifi Scanning: true Sep 06 00:03:08 reMarkable xochitl[230]: 00:03:08.457 rm.wifi Scanning: false Sep 06 00:03:09 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 4. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:03:09 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 4857 and the job result is done. Sep 06 00:03:09 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 4857. Sep 06 00:03:09 reMarkable xochitl[4158]: STARTING RM2FB Sep 06 00:03:09 reMarkable xochitl[4158]: Missing address for function 'getInstance' Sep 06 00:03:09 reMarkable xochitl[4158]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:03:09 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:03:09 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:03:09 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 4857 and the job result is failed. Sep 06 00:03:14 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 5. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:03:14 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 4931 and the job result is done. Sep 06 00:03:14 reMarkable systemd[1]: rm2fb.service: Start request repeated too quickly. Sep 06 00:03:14 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:03:14 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 4931 and the job result is failed. Sep 06 00:03:14 reMarkable xochitl[230]: 00:03:14.590 rm.wifi Scanning: true Sep 06 00:03:18 reMarkable xochitl[230]: 00:03:18.496 rm.wifi Scanning: false Sep 06 00:03:19 reMarkable xochitl[230]: 00:03:19.297 default qrc:/qml/device/view/settings/General.qml:14:5: Unable to assign [undefined] to bool (qrc:/qml/device/view/settings/General.qml:14) Sep 06 00:03:21 reMarkable systemd[1]: Stopped target Multi-User System. -- Subject: A stop job for unit multi-user.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit multi-user.target has finished. -- -- The job identifier is 5017 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopped target Login Prompts. -- Subject: A stop job for unit getty.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit getty.target has finished. -- -- The job identifier is 5098 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopped target Remote Encrypted Volumes. -- Subject: A stop job for unit remote-cryptsetup.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit remote-cryptsetup.target has finished. -- -- The job identifier is 5093 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopped target Remote File Systems. -- Subject: A stop job for unit remote-fs.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit remote-fs.target has finished. -- -- The job identifier is 5049 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopped target System Time Synchronized. -- Subject: A stop job for unit time-sync.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit time-sync.target has finished. -- -- The job identifier is 5097 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopped target System Time Set. -- Subject: A stop job for unit time-set.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit time-set.target has finished. -- -- The job identifier is 5034 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopped target Timers. -- Subject: A stop job for unit timers.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit timers.target has finished. -- -- The job identifier is 5071 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: systemd-tmpfiles-clean.timer: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-tmpfiles-clean.timer has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped Daily Cleanup of Temporary Directories. -- Subject: A stop job for unit systemd-tmpfiles-clean.timer has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-tmpfiles-clean.timer has finished. -- -- The job identifier is 5062 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopped target Hardware activated USB gadget. -- Subject: A stop job for unit usb-gadget.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit usb-gadget.target has finished. -- -- The job identifier is 5055 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: systemd-rfkill.socket: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-rfkill.socket has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch. -- Subject: A stop job for unit systemd-rfkill.socket has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-rfkill.socket has finished. -- -- The job identifier is 5026 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Unmounting /var/lib/uboot... -- Subject: A stop job for unit var-lib-uboot.mount has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit var-lib-uboot.mount has begun execution. -- -- The job identifier is 5043. Sep 06 00:03:21 reMarkable systemd[1]: Stopping reMarkable crash uploader... -- Subject: A stop job for unit crashuploader.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit crashuploader.service has begun execution. -- -- The job identifier is 5010. Sep 06 00:03:21 reMarkable systemd[1]: Stopping D-Bus System Message Bus... -- Subject: A stop job for unit dbus.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit dbus.service has begun execution. -- -- The job identifier is 5036. Sep 06 00:03:21 reMarkable dropbear[2870]: Exit (root): Terminated by signal Sep 06 00:03:21 reMarkable wpa_supplicant[257]: wlan0: CTRL-EVENT-DISCONNECTED bssid=ee:4f:0d:07:8c:bf reason=3 locally_generated=1 Sep 06 00:03:21 reMarkable systemd[1]: Stopping SSH Per-Connection Server... -- Subject: A stop job for unit dropbear@28-10.11.99.1:22-10.11.99.4:39200.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit dropbear@28-10.11.99.1:22-10.11.99.4:39200.service has begun execution. -- -- The job identifier is 5054. Sep 06 00:03:21 reMarkable dhcpcd[231]: wlan0: carrier lost Sep 06 00:03:21 reMarkable wpa_supplicant[257]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/1 Sep 06 00:03:21 reMarkable systemd[1]: Stopping Getty on tty1... -- Subject: A stop job for unit getty@tty1.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit getty@tty1.service has begun execution. -- -- The job identifier is 5031. Sep 06 00:03:21 reMarkable xochitl[230]: Shutting down... Sep 06 00:03:21 reMarkable systemd[1]: Stopping A simple mDNS responder... -- Subject: A stop job for unit qmdns-responder.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit qmdns-responder.service has begun execution. -- -- The job identifier is 5053. Sep 06 00:03:21 reMarkable systemd[1]: Stopping Serial Getty on ttymxc0... -- Subject: A stop job for unit serial-getty@ttymxc0.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit serial-getty@ttymxc0.service has begun execution. -- -- The job identifier is 5014. Sep 06 00:03:21 reMarkable systemd[1]: Stopping reMarkable Document Sync... -- Subject: A stop job for unit sync.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit sync.service has begun execution. -- -- The job identifier is 5012. Sep 06 00:03:21 reMarkable systemd[1]: Stopping Login Service... -- Subject: A stop job for unit systemd-logind.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-logind.service has begun execution. -- -- The job identifier is 5045. Sep 06 00:03:21 reMarkable systemd[1]: Stopping Load/Save Random Seed... -- Subject: A stop job for unit systemd-random-seed.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-random-seed.service has begun execution. -- -- The job identifier is 5090. Sep 06 00:03:21 reMarkable systemd-networkd[141]: wlan0: Lost carrier Sep 06 00:03:21 reMarkable systemd[1]: Stopping Update Engine... -- Subject: A stop job for unit update-engine.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit update-engine.service has begun execution. -- -- The job identifier is 5047. Sep 06 00:03:21 reMarkable wpa_supplicant[257]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0 Sep 06 00:03:21 reMarkable systemd[1]: wacom_flash.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit wacom_flash.service has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped Pseudo service that ensures that Wacom firmware is up-to-date. -- Subject: A stop job for unit wacom_flash.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit wacom_flash.service has finished. -- -- The job identifier is 5056 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopping reMarkable main application... -- Subject: A stop job for unit xochitl.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit xochitl.service has begun execution. -- -- The job identifier is 5037. Sep 06 00:03:21 reMarkable systemd[1]: dbus.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit dbus.service has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped D-Bus System Message Bus. -- Subject: A stop job for unit dbus.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit dbus.service has finished. -- -- The job identifier is 5036 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: getty@tty1.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit getty@tty1.service has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable wpa_supplicant[257]: wlan0: CTRL-EVENT-TERMINATING Sep 06 00:03:21 reMarkable systemd[1]: Stopped Getty on tty1. -- Subject: A stop job for unit getty@tty1.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit getty@tty1.service has finished. -- -- The job identifier is 5031 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: serial-getty@ttymxc0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit serial-getty@ttymxc0.service has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped Serial Getty on ttymxc0. -- Subject: A stop job for unit serial-getty@ttymxc0.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit serial-getty@ttymxc0.service has finished. -- -- The job identifier is 5014 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: sync.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit sync.service has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped reMarkable Document Sync. -- Subject: A stop job for unit sync.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit sync.service has finished. -- -- The job identifier is 5012 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: update-engine.service: Main process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit update-engine.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Sep 06 00:03:21 reMarkable systemd[1]: update-engine.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit update-engine.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:03:21 reMarkable systemd[1]: Stopped Update Engine. -- Subject: A stop job for unit update-engine.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit update-engine.service has finished. -- -- The job identifier is 5047 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: systemd-logind.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-logind.service has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped Login Service. -- Subject: A stop job for unit systemd-logind.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-logind.service has finished. -- -- The job identifier is 5045 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: crashuploader.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit crashuploader.service has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped reMarkable crash uploader. -- Subject: A stop job for unit crashuploader.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit crashuploader.service has finished. -- -- The job identifier is 5010 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: wpa_supplicant.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit wpa_supplicant.service has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped WPA supplicant. -- Subject: A stop job for unit wpa_supplicant.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit wpa_supplicant.service has finished. -- -- The job identifier is 5046 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: qmdns-responder.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit qmdns-responder.service has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped A simple mDNS responder. -- Subject: A stop job for unit qmdns-responder.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit qmdns-responder.service has finished. -- -- The job identifier is 5053 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: dropbear@28-10.11.99.1:22-10.11.99.4:39200.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit dropbear@28-10.11.99.1:22-10.11.99.4:39200.service has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped SSH Per-Connection Server. -- Subject: A stop job for unit dropbear@28-10.11.99.1:22-10.11.99.4:39200.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit dropbear@28-10.11.99.1:22-10.11.99.4:39200.service has finished. -- -- The job identifier is 5054 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: var-lib-uboot.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit var-lib-uboot.mount has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Unmounted /var/lib/uboot. -- Subject: A stop job for unit var-lib-uboot.mount has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit var-lib-uboot.mount has finished. -- -- The job identifier is 5043 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: systemd-random-seed.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-random-seed.service has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped Load/Save Random Seed. -- Subject: A stop job for unit systemd-random-seed.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-random-seed.service has finished. -- -- The job identifier is 5090 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Removed slice system-dropbear.slice. -- Subject: A stop job for unit system-dropbear.slice has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit system-dropbear.slice has finished. -- -- The job identifier is 5092 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Removed slice system-getty.slice. -- Subject: A stop job for unit system-getty.slice has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit system-getty.slice has finished. -- -- The job identifier is 5030 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Removed slice system-serial\x2dgetty.slice. -- Subject: A stop job for unit system-serial\x2dgetty.slice has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit system-serial\x2dgetty.slice has finished. -- -- The job identifier is 5013 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopped target Network is Online. -- Subject: A stop job for unit network-online.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit network-online.target has finished. -- -- The job identifier is 5103 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopped target Network. -- Subject: A stop job for unit network.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit network.target has finished. -- -- The job identifier is 5088 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopping ifplugd on usb0... -- Subject: A stop job for unit busybox-ifplugd@usb0.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit busybox-ifplugd@usb0.service has begun execution. -- -- The job identifier is 5024. Sep 06 00:03:21 reMarkable systemd[1]: Stopping udhcpd on usb0... -- Subject: A stop job for unit busybox-udhcpd@usb0.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit busybox-udhcpd@usb0.service has begun execution. -- -- The job identifier is 5023. Sep 06 00:03:21 reMarkable systemd[1]: Stopping dhcpcd on all interfaces... -- Subject: A stop job for unit dhcpcd.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit dhcpcd.service has begun execution. -- -- The job identifier is 5061. Sep 06 00:03:21 reMarkable systemd[1]: systemd-fsck@dev-mmcblk2p1.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-fsck@dev-mmcblk2p1.service has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped File System Check on /dev/mmcblk2p1. -- Subject: A stop job for unit systemd-fsck@dev-mmcblk2p1.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-fsck@dev-mmcblk2p1.service has finished. -- -- The job identifier is 5042 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: systemd-networkd-wait-online.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-networkd-wait-online.service has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped Wait for Network to be Configured. -- Subject: A stop job for unit systemd-networkd-wait-online.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-networkd-wait-online.service has finished. -- -- The job identifier is 5025 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: busybox-udhcpd@usb0.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit busybox-udhcpd@usb0.service has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped udhcpd on usb0. -- Subject: A stop job for unit busybox-udhcpd@usb0.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit busybox-udhcpd@usb0.service has finished. -- -- The job identifier is 5023 and the job result is done. Sep 06 00:03:21 reMarkable dhcpcd[4180]: sending signal TERM to pid 231 Sep 06 00:03:21 reMarkable dhcpcd[4180]: waiting for pid 231 to exit Sep 06 00:03:21 reMarkable dhcpcd[4180]: sending signal TERM to pid 231 Sep 06 00:03:21 reMarkable dhcpcd[4180]: waiting for pid 231 to exit Sep 06 00:03:21 reMarkable systemd[1]: Removed slice system-busybox\x2dudhcpd.slice. -- Subject: A stop job for unit system-busybox\x2dudhcpd.slice has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit system-busybox\x2dudhcpd.slice has finished. -- -- The job identifier is 5035 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: busybox-ifplugd@usb0.service: Main process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit busybox-ifplugd@usb0.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Sep 06 00:03:21 reMarkable ifplugd(usb0)[174]: exiting Sep 06 00:03:21 reMarkable systemd[1]: busybox-ifplugd@usb0.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit busybox-ifplugd@usb0.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:03:21 reMarkable systemd[1]: Stopped ifplugd on usb0. -- Subject: A stop job for unit busybox-ifplugd@usb0.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit busybox-ifplugd@usb0.service has finished. -- -- The job identifier is 5024 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Removed slice system-busybox\x2difplugd.slice. -- Subject: A stop job for unit system-busybox\x2difplugd.slice has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit system-busybox\x2difplugd.slice has finished. -- -- The job identifier is 5084 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopping Network Service... -- Subject: A stop job for unit systemd-networkd.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-networkd.service has begun execution. -- -- The job identifier is 5022. Sep 06 00:03:21 reMarkable dhcpcd[231]: wlan0: deleting route to 172.20.10.0/28 Sep 06 00:03:21 reMarkable dhcpcd[231]: wlan0: deleting default route via 172.20.10.1 Sep 06 00:03:21 reMarkable systemd[1]: systemd-networkd.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-networkd.service has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped Network Service. -- Subject: A stop job for unit systemd-networkd.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-networkd.service has finished. -- -- The job identifier is 5022 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Requested transaction contradicts existing jobs: Transaction for systemd-networkd.service/start is destructive (systemd-reboot.service has 'start' job queued, but 'stop' is included in transaction). Sep 06 00:03:21 reMarkable systemd[1]: systemd-networkd.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction for systemd-networkd.service/start is destructive (systemd-reboot.service has 'start' job queued, but 'stop' is included in transaction). Sep 06 00:03:21 reMarkable systemd[1]: systemd-networkd.socket: Failed with result 'resources'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-networkd.socket has entered the 'failed' state with result 'resources'. Sep 06 00:03:21 reMarkable dhcpcd[231]: received SIGTERM, stopping Sep 06 00:03:21 reMarkable dhcpcd[231]: wlan0: removing interface Sep 06 00:03:21 reMarkable dhcpcd[231]: dhcpcd exited Sep 06 00:03:21 reMarkable systemd[1]: dhcpcd.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit dhcpcd.service has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped dhcpcd on all interfaces. -- Subject: A stop job for unit dhcpcd.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit dhcpcd.service has finished. -- -- The job identifier is 5061 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: xochitl.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit xochitl.service has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped reMarkable main application. -- Subject: A stop job for unit xochitl.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit xochitl.service has finished. -- -- The job identifier is 5037 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopped target Basic System. -- Subject: A stop job for unit basic.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit basic.target has finished. -- -- The job identifier is 5015 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopped target Paths. -- Subject: A stop job for unit paths.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit paths.target has finished. -- -- The job identifier is 5027 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopped target Slices. -- Subject: A stop job for unit slices.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit slices.target has finished. -- -- The job identifier is 5080 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Removed slice User and Session Slice. -- Subject: A stop job for unit user.slice has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit user.slice has finished. -- -- The job identifier is 5086 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopped target Sockets. -- Subject: A stop job for unit sockets.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit sockets.target has finished. -- -- The job identifier is 5074 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: dbus.socket: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit dbus.socket has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Closed D-Bus System Message Bus Socket. -- Subject: A stop job for unit dbus.socket has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit dbus.socket has finished. -- -- The job identifier is 5044 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: dropbear.socket: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit dropbear.socket has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Closed dropbear.socket. -- Subject: A stop job for unit dropbear.socket has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit dropbear.socket has finished. -- -- The job identifier is 5058 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopped target System Initialization. -- Subject: A stop job for unit sysinit.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit sysinit.target has finished. -- -- The job identifier is 5059 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopped target Local Encrypted Volumes. -- Subject: A stop job for unit cryptsetup.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit cryptsetup.target has finished. -- -- The job identifier is 5033 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: systemd-ask-password-console.path: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-ask-password-console.path has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch. -- Subject: A stop job for unit systemd-ask-password-console.path has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-ask-password-console.path has finished. -- -- The job identifier is 5087 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: systemd-ask-password-wall.path: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-ask-password-wall.path has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped Forward Password Requests to Wall Directory Watch. -- Subject: A stop job for unit systemd-ask-password-wall.path has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-ask-password-wall.path has finished. -- -- The job identifier is 5101 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Starting Show reboot image... -- Subject: A start job for unit remarkable-reboot.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit remarkable-reboot.service has begun execution. -- -- The job identifier is 5120. Sep 06 00:03:21 reMarkable systemd[1]: systemd-sysctl.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-sysctl.service has successfully entered the 'dead' state. Sep 06 00:03:21 reMarkable systemd[1]: Stopped Apply Kernel Variables. -- Subject: A stop job for unit systemd-sysctl.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-sysctl.service has finished. -- -- The job identifier is 5085 and the job result is done. Sep 06 00:03:21 reMarkable systemd[1]: Stopping Network Time Synchronization... -- Subject: A stop job for unit systemd-timesyncd.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-timesyncd.service has begun execution. -- -- The job identifier is 5032. Sep 06 00:03:22 reMarkable systemd[1]: systemd-timesyncd.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-timesyncd.service has successfully entered the 'dead' state. Sep 06 00:03:22 reMarkable systemd[1]: Stopped Network Time Synchronization. -- Subject: A stop job for unit systemd-timesyncd.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-timesyncd.service has finished. -- -- The job identifier is 5032 and the job result is done. Sep 06 00:03:22 reMarkable systemd[1]: systemd-tmpfiles-setup.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-tmpfiles-setup.service has successfully entered the 'dead' state. Sep 06 00:03:22 reMarkable systemd[1]: Stopped Create Volatile Files and Directories. -- Subject: A stop job for unit systemd-tmpfiles-setup.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-tmpfiles-setup.service has finished. -- -- The job identifier is 5082 and the job result is done. Sep 06 00:03:22 reMarkable systemd[1]: Stopped target Local File Systems. -- Subject: A stop job for unit local-fs.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit local-fs.target has finished. -- -- The job identifier is 5078 and the job result is done. Sep 06 00:03:22 reMarkable systemd[1]: Unmounting Bind mount /home/root/.entware over /opt... -- Subject: A stop job for unit opt.mount has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit opt.mount has begun execution. -- -- The job identifier is 5041. Sep 06 00:03:22 reMarkable systemd[1]: Unmounting Temporary Directory (/tmp)... -- Subject: A stop job for unit tmp.mount has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit tmp.mount has begun execution. -- -- The job identifier is 5111. Sep 06 00:03:22 reMarkable systemd[1]: Unmounting /var/volatile... -- Subject: A stop job for unit var-volatile.mount has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit var-volatile.mount has begun execution. -- -- The job identifier is 5106. Sep 06 00:03:22 reMarkable remarkable-shutdown[4200]: REMARKABLE_SHUTDOWN_STATE= "" Sep 06 00:03:22 reMarkable remarkable-shutdown[4200]: REMARKABLE_SHUTDOWN_UPDATE_SCREEN= "" Sep 06 00:03:22 reMarkable systemd[1]: opt.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit opt.mount has successfully entered the 'dead' state. Sep 06 00:03:22 reMarkable systemd[1]: Unmounted Bind mount /home/root/.entware over /opt. -- Subject: A stop job for unit opt.mount has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit opt.mount has finished. -- -- The job identifier is 5041 and the job result is done. Sep 06 00:03:22 reMarkable remarkable-shutdown[4200]: EPD platform plugin loaded! Sep 06 00:03:22 reMarkable systemd[1]: tmp.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit tmp.mount has successfully entered the 'dead' state. Sep 06 00:03:22 reMarkable systemd[1]: Unmounted Temporary Directory (/tmp). -- Subject: A stop job for unit tmp.mount has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit tmp.mount has finished. -- -- The job identifier is 5111 and the job result is done. Sep 06 00:03:22 reMarkable systemd[1]: var-volatile.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit var-volatile.mount has successfully entered the 'dead' state. Sep 06 00:03:22 reMarkable systemd[1]: Unmounted /var/volatile. -- Subject: A stop job for unit var-volatile.mount has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit var-volatile.mount has finished. -- -- The job identifier is 5106 and the job result is done. Sep 06 00:03:22 reMarkable systemd[1]: Stopped target Swap. -- Subject: A stop job for unit swap.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit swap.target has finished. -- -- The job identifier is 5104 and the job result is done. Sep 06 00:03:22 reMarkable remarkable-shutdown[4200]: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Sep 06 00:03:22 reMarkable systemd[1]: Unmounting /home... -- Subject: A stop job for unit home.mount has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit home.mount has begun execution. -- -- The job identifier is 5040. Sep 06 00:03:22 reMarkable remarkable-shutdown[4200]: qt.qpa.input: evdevtouch: Using device discovery Sep 06 00:03:22 reMarkable remarkable-shutdown[4200]: qt.qpa.input: evdevtouch: Adding device at /dev/input/event2 Sep 06 00:03:22 reMarkable remarkable-shutdown[4200]: qt.qpa.input: evdevtouch: Using device /dev/input/event2 Sep 06 00:03:22 reMarkable remarkable-shutdown[4200]: qt.qpa.input: evdevtouch: /dev/input/event2: Protocol type B (multi), filtered=no Sep 06 00:03:22 reMarkable remarkable-shutdown[4200]: qt.qpa.input: evdevtouch: /dev/input/event2: min X: 0 max X: 1403 Sep 06 00:03:22 reMarkable remarkable-shutdown[4200]: qt.qpa.input: evdevtouch: /dev/input/event2: min Y: 0 max Y: 1871 Sep 06 00:03:22 reMarkable remarkable-shutdown[4200]: qt.qpa.input: evdevtouch: /dev/input/event2: min pressure: 0 max pressure: 0 Sep 06 00:03:22 reMarkable remarkable-shutdown[4200]: qt.qpa.input: evdevtouch: /dev/input/event2: device name: pt_mt Sep 06 00:03:22 reMarkable systemd[1]: home.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit home.mount has successfully entered the 'dead' state. Sep 06 00:03:22 reMarkable systemd[1]: Unmounted /home. -- Subject: A stop job for unit home.mount has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit home.mount has finished. -- -- The job identifier is 5040 and the job result is done. Sep 06 00:03:22 reMarkable systemd[1]: Reached target Unmount All Filesystems. -- Subject: A start job for unit umount.target has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit umount.target has finished successfully. -- -- The job identifier is 5105. Sep 06 00:03:22 reMarkable systemd[1]: systemd-fsck@dev-mmcblk2p4.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-fsck@dev-mmcblk2p4.service has successfully entered the 'dead' state. Sep 06 00:03:22 reMarkable systemd[1]: Stopped File System Check on /dev/mmcblk2p4. -- Subject: A stop job for unit systemd-fsck@dev-mmcblk2p4.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-fsck@dev-mmcblk2p4.service has finished. -- -- The job identifier is 5039 and the job result is done. Sep 06 00:03:22 reMarkable systemd[1]: Removed slice system-systemd\x2dfsck.slice. -- Subject: A stop job for unit system-systemd\x2dfsck.slice has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit system-systemd\x2dfsck.slice has finished. -- -- The job identifier is 5038 and the job result is done. Sep 06 00:03:22 reMarkable systemd[1]: Stopped target Local File Systems (Pre). -- Subject: A stop job for unit local-fs-pre.target has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit local-fs-pre.target has finished. -- -- The job identifier is 5077 and the job result is done. Sep 06 00:03:22 reMarkable systemd[1]: systemd-remount-fs.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-remount-fs.service has successfully entered the 'dead' state. Sep 06 00:03:22 reMarkable systemd[1]: Stopped Remount Root and Kernel File Systems. -- Subject: A stop job for unit systemd-remount-fs.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-remount-fs.service has finished. -- -- The job identifier is 5068 and the job result is done. Sep 06 00:03:22 reMarkable systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-tmpfiles-setup-dev.service has successfully entered the 'dead' state. Sep 06 00:03:22 reMarkable systemd[1]: Stopped Create Static Device Nodes in /dev. -- Subject: A stop job for unit systemd-tmpfiles-setup-dev.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-tmpfiles-setup-dev.service has finished. -- -- The job identifier is 5091 and the job result is done. Sep 06 00:03:23 reMarkable remarkable-shutdown[4200]: SWTCON initialized \o/ Sep 06 00:03:23 reMarkable remarkable-shutdown[4200]: Creating painter Sep 06 00:03:23 reMarkable remarkable-shutdown[4200]: Battery left: 97 Sep 06 00:03:23 reMarkable remarkable-shutdown[4200]: Sending update Sep 06 00:03:24 reMarkable remarkable-shutdown[4200]: Epaper integration dying Sep 06 00:03:24 reMarkable remarkable-shutdown[4200]: Epaper integration dead Sep 06 00:03:24 reMarkable remarkable-shutdown[4200]: Error decoding barcode: EUFE7RDF1X1V011ZKAT -1.27! Sep 06 00:03:24 reMarkable remarkable-shutdown[4200]: Waveform file with correct FPL_LOT and TFT_VID not found, using fallback: /usr/share/remarkable/320_R355_AF0A11_ED103TC2U2_VB3300-KCD_TC.wbf Sep 06 00:03:24 reMarkable remarkable-shutdown[4200]: Reading waveforms from /usr/share/remarkable/320_R355_AF0A11_ED103TC2U2_VB3300-KCD_TC.wbf Sep 06 00:03:24 reMarkable remarkable-shutdown[4200]: Running INIT (87 phases) Sep 06 00:03:24 reMarkable systemd[1]: Started Show reboot image. -- Subject: A start job for unit remarkable-reboot.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit remarkable-reboot.service has finished successfully. -- -- The job identifier is 5120. Sep 06 00:03:24 reMarkable systemd[1]: Reached target Shutdown. -- Subject: A start job for unit shutdown.target has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit shutdown.target has finished successfully. -- -- The job identifier is 5008. Sep 06 00:03:24 reMarkable systemd[1]: Reached target Final Step. -- Subject: A start job for unit final.target has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit final.target has finished successfully. -- -- The job identifier is 5007. Sep 06 00:03:24 reMarkable systemd[1]: systemd-reboot.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-reboot.service has successfully entered the 'dead' state. Sep 06 00:03:24 reMarkable systemd[1]: Started Reboot. -- Subject: A start job for unit systemd-reboot.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-reboot.service has finished successfully. -- -- The job identifier is 5006. Sep 06 00:03:24 reMarkable systemd[1]: Reached target Reboot. -- Subject: A start job for unit reboot.target has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit reboot.target has finished successfully. -- -- The job identifier is 5005. Sep 06 00:03:24 reMarkable systemd[1]: Shutting down. Sep 06 00:03:24 reMarkable systemd[1]: Hardware watchdog 'imx2+ watchdog', version 0 Sep 06 00:03:24 reMarkable systemd[1]: Set hardware watchdog to 10min. Sep 06 00:03:24 reMarkable kernel: watchdog: watchdog0: watchdog did not stop! Sep 06 00:03:24 reMarkable systemd-shutdown[1]: Syncing filesystems and block devices. Sep 06 00:03:24 reMarkable systemd-shutdown[1]: Sending SIGTERM to remaining processes... Sep 06 00:03:24 reMarkable haveged[132]: haveged: Stopping due to signal 15 Sep 06 00:03:24 reMarkable haveged[132]: haveged starting up Sep 06 00:03:24 reMarkable systemd-journald[133]: Journal stopped -- Subject: The journal has been stopped -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The system journal process has shut down and closed all currently -- active journal files. -- Reboot -- Sep 06 00:03:41 reMarkable kernel: Booting Linux on physical CPU 0x0 Sep 06 00:03:41 reMarkable kernel: Linux version 5.4.70-v1.2.2-rm11x (oe-user@oe-host) (gcc version 9.3.0 (GCC)) #1 SMP PREEMPT Thu Aug 25 12:39:03 UTC 2022 Sep 06 00:03:41 reMarkable kernel: CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d Sep 06 00:03:41 reMarkable kernel: CPU: div instructions available: patching division code Sep 06 00:03:41 reMarkable kernel: CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache Sep 06 00:03:41 reMarkable kernel: OF: fdt: Machine model: reMarkable 2.0 Sep 06 00:03:41 reMarkable kernel: Memory policy: Data cache writealloc Sep 06 00:03:41 reMarkable kernel: Reserved memory: created CMA memory pool at 0xa9c00000, size 320 MiB Sep 06 00:03:41 reMarkable kernel: OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool Sep 06 00:03:41 reMarkable kernel: On node 0 totalpages: 262144 Sep 06 00:03:41 reMarkable kernel: Normal zone: 2048 pages used for memmap Sep 06 00:03:41 reMarkable kernel: Normal zone: 0 pages reserved Sep 06 00:03:41 reMarkable kernel: Normal zone: 262144 pages, LIFO batch:63 Sep 06 00:03:41 reMarkable kernel: Reserving 32MB of memory at 2560MB for crashkernel (System RAM: 1024MB) Sep 06 00:03:41 reMarkable kernel: percpu: Embedded 15 pages/cpu s31180 r8192 d22068 u61440 Sep 06 00:03:41 reMarkable kernel: pcpu-alloc: s31180 r8192 d22068 u61440 alloc=15*4096 Sep 06 00:03:41 reMarkable kernel: pcpu-alloc: [0] 0 [0] 1 Sep 06 00:03:41 reMarkable kernel: Built 1 zonelists, mobility grouping on. Total pages: 260096 Sep 06 00:03:41 reMarkable kernel: Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk2p3 rootwait rootfstype=ext4 rw quiet panic=20 systemd.crash_reboot systemd.show_status=0 loglevel=0 crashkernel=32M Sep 06 00:03:41 reMarkable kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear) Sep 06 00:03:41 reMarkable kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear) Sep 06 00:03:41 reMarkable kernel: mem auto-init: stack:off, heap alloc:off, heap free:off Sep 06 00:03:41 reMarkable kernel: Memory: 666196K/1048576K available (7168K kernel code, 371K rwdata, 2384K rodata, 1024K init, 384K bss, 54700K reserved, 327680K cma-reserved) Sep 06 00:03:41 reMarkable kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 Sep 06 00:03:41 reMarkable kernel: rcu: Preemptible hierarchical RCU implementation. Sep 06 00:03:41 reMarkable kernel: rcu: RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. Sep 06 00:03:41 reMarkable kernel: Tasks RCU enabled. Sep 06 00:03:41 reMarkable kernel: rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. Sep 06 00:03:41 reMarkable kernel: rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 Sep 06 00:03:41 reMarkable kernel: NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 Sep 06 00:03:41 reMarkable kernel: random: get_random_bytes called from start_kernel+0x2b4/0x3fc with crng_init=0 Sep 06 00:03:41 reMarkable kernel: arch_timer: cp15 timer(s) running at 8.00MHz (phys). Sep 06 00:03:41 reMarkable kernel: clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns Sep 06 00:03:41 reMarkable kernel: sched_clock: 56 bits at 8MHz, resolution 125ns, wraps every 2199023255500ns Sep 06 00:03:41 reMarkable kernel: Switching to timer-based delay loop, resolution 125ns Sep 06 00:03:41 reMarkable kernel: Ignoring duplicate/late registration of read_current_timer delay Sep 06 00:03:41 reMarkable kernel: clocksource: mxc_timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 637086815595 ns Sep 06 00:03:41 reMarkable kernel: arch_timer: multiple nodes in dt, skipping Sep 06 00:03:41 reMarkable kernel: Console: colour dummy device 80x30 Sep 06 00:03:41 reMarkable kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 16.00 BogoMIPS (lpj=80000) Sep 06 00:03:41 reMarkable kernel: pid_max: default: 32768 minimum: 301 Sep 06 00:03:41 reMarkable kernel: Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) Sep 06 00:03:41 reMarkable kernel: Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) Sep 06 00:03:41 reMarkable kernel: CPU: Testing write buffer coherency: ok Sep 06 00:03:41 reMarkable kernel: CPU0: update cpu_capacity 1024 Sep 06 00:03:41 reMarkable kernel: CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 Sep 06 00:03:41 reMarkable kernel: Setting up static identity map for 0x80100000 - 0x80100060 Sep 06 00:03:41 reMarkable kernel: rcu: Hierarchical SRCU implementation. Sep 06 00:03:41 reMarkable kernel: smp: Bringing up secondary CPUs ... Sep 06 00:03:41 reMarkable kernel: CPU1: update cpu_capacity 1024 Sep 06 00:03:41 reMarkable kernel: CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 Sep 06 00:03:41 reMarkable kernel: smp: Brought up 1 node, 2 CPUs Sep 06 00:03:41 reMarkable kernel: SMP: Total of 2 processors activated (32.00 BogoMIPS). Sep 06 00:03:41 reMarkable kernel: CPU: All CPU(s) started in SVC mode. Sep 06 00:03:41 reMarkable kernel: devtmpfs: initialized Sep 06 00:03:41 reMarkable kernel: Duplicate name in lcdif@30730000, renamed to "display#1" Sep 06 00:03:41 reMarkable kernel: VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5 Sep 06 00:03:41 reMarkable kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns Sep 06 00:03:41 reMarkable kernel: futex hash table entries: 512 (order: 3, 32768 bytes, linear) Sep 06 00:03:41 reMarkable kernel: pinctrl core: initialized pinctrl subsystem Sep 06 00:03:41 reMarkable kernel: NET: Registered protocol family 16 Sep 06 00:03:41 reMarkable kernel: DMA: preallocated 256 KiB pool for atomic coherent allocations Sep 06 00:03:41 reMarkable kernel: cpuidle: using governor menu Sep 06 00:03:41 reMarkable kernel: vdd1p0d: supplied by regulator-dummy Sep 06 00:03:41 reMarkable kernel: vdd1p0d: Bringing 0uV into 800000-800000uV Sep 06 00:03:41 reMarkable kernel: vdd1p2: supplied by regulator-dummy Sep 06 00:03:41 reMarkable kernel: DDR type is LPDDR3! Sep 06 00:03:41 reMarkable kernel: No ATAGs? Sep 06 00:03:41 reMarkable kernel: imx7d-pinctrl 302c0000.iomuxc-lpsr: initialized IMX pinctrl driver Sep 06 00:03:41 reMarkable kernel: imx7d-pinctrl 30330000.iomuxc: initialized IMX pinctrl driver Sep 06 00:03:41 reMarkable kernel: usbcore: registered new interface driver usbfs Sep 06 00:03:41 reMarkable kernel: usbcore: registered new interface driver hub Sep 06 00:03:41 reMarkable kernel: usbcore: registered new device driver usb Sep 06 00:03:41 reMarkable kernel: usb_phy_generic usbphynop1: usbphynop1 supply vcc not found, using dummy regulator Sep 06 00:03:41 reMarkable kernel: usb_phy_generic usbphynop3: usbphynop3 supply vcc not found, using dummy regulator Sep 06 00:03:41 reMarkable kernel: usb_phy_generic usbphynop2: usbphynop2 supply vcc not found, using dummy regulator Sep 06 00:03:41 reMarkable kernel: i2c i2c-0: IMX I2C adapter registered Sep 06 00:03:41 reMarkable kernel: bd7181x 1-004b: BD7181x: Device ID=0x41 Sep 06 00:03:41 reMarkable kernel: bd7181x->chip_irq=236 Sep 06 00:03:41 reMarkable kernel: random: fast init done Sep 06 00:03:41 reMarkable kernel: i2c i2c-1: IMX I2C adapter registered Sep 06 00:03:41 reMarkable kernel: i2c i2c-2: IMX I2C adapter registered Sep 06 00:03:41 reMarkable kernel: i2c i2c-3: IMX I2C adapter registered Sep 06 00:03:41 reMarkable kernel: pps_core: LinuxPPS API ver. 1 registered Sep 06 00:03:41 reMarkable kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti Sep 06 00:03:41 reMarkable kernel: PTP clock support registered Sep 06 00:03:41 reMarkable kernel: MIPI CSI2 driver module loaded Sep 06 00:03:41 reMarkable kernel: clocksource: Switched to clocksource arch_sys_counter Sep 06 00:03:41 reMarkable kernel: VFS: Disk quotas dquot_6.6.0 Sep 06 00:03:41 reMarkable kernel: VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Sep 06 00:03:41 reMarkable kernel: thermal_sys: Registered thermal governor 'step_wise' Sep 06 00:03:41 reMarkable kernel: thermal_sys: Registered thermal governor 'user_space' Sep 06 00:03:41 reMarkable kernel: NET: Registered protocol family 2 Sep 06 00:03:41 reMarkable kernel: tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear) Sep 06 00:03:41 reMarkable kernel: TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear) Sep 06 00:03:41 reMarkable kernel: TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear) Sep 06 00:03:41 reMarkable kernel: TCP: Hash tables configured (established 8192 bind 8192) Sep 06 00:03:41 reMarkable kernel: UDP hash table entries: 512 (order: 2, 16384 bytes, linear) Sep 06 00:03:41 reMarkable kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear) Sep 06 00:03:41 reMarkable kernel: NET: Registered protocol family 1 Sep 06 00:03:41 reMarkable kernel: RPC: Registered named UNIX socket transport module. Sep 06 00:03:41 reMarkable kernel: RPC: Registered udp transport module. Sep 06 00:03:41 reMarkable kernel: RPC: Registered tcp transport module. Sep 06 00:03:41 reMarkable kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Sep 06 00:03:41 reMarkable kernel: Bus freq driver module loaded Sep 06 00:03:41 reMarkable kernel: Initialise system trusted keyrings Sep 06 00:03:41 reMarkable kernel: workingset: timestamp_bits=30 max_order=18 bucket_order=0 Sep 06 00:03:41 reMarkable kernel: NFS: Registering the id_resolver key type Sep 06 00:03:41 reMarkable kernel: Key type id_resolver registered Sep 06 00:03:41 reMarkable kernel: Key type id_legacy registered Sep 06 00:03:41 reMarkable kernel: fuse: init (API version 7.31) Sep 06 00:03:41 reMarkable kernel: Key type asymmetric registered Sep 06 00:03:41 reMarkable kernel: Asymmetric key parser 'x509' registered Sep 06 00:03:41 reMarkable kernel: io scheduler mq-deadline registered Sep 06 00:03:41 reMarkable kernel: io scheduler kyber registered Sep 06 00:03:41 reMarkable kernel: mxsfb 30730000.lcdif: lcd-supply not ready, deferring Sep 06 00:03:41 reMarkable kernel: 30860000.serial: ttymxc0 at MMIO 0x30860000 (irq = 46, base_baud = 1500000) is a IMX Sep 06 00:03:41 reMarkable kernel: printk: console [ttymxc0] enabled Sep 06 00:03:41 reMarkable kernel: 30a80000.serial: ttymxc5 at MMIO 0x30a80000 (irq = 51, base_baud = 1500000) is a IMX Sep 06 00:03:41 reMarkable kernel: loop: module loaded Sep 06 00:03:41 reMarkable kernel: rm_otg_control otgcontrol1: rm_otgcontrol_probe: Defering probe due to charger driver not beingloaded/available yet Sep 06 00:03:41 reMarkable kernel: max77818 1-0066: device ID: 0x23, REV: 0x3 Sep 06 00:03:41 reMarkable kernel: sy7636a 3-0062: Power good GPIO registered (gpio# 181) Sep 06 00:03:41 reMarkable kernel: libphy: Fixed MDIO Bus: probed Sep 06 00:03:41 reMarkable kernel: usbcore: registered new interface driver kaweth Sep 06 00:03:41 reMarkable kernel: pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver Sep 06 00:03:41 reMarkable kernel: usbcore: registered new interface driver pegasus Sep 06 00:03:41 reMarkable kernel: usbcore: registered new interface driver rtl8150 Sep 06 00:03:41 reMarkable kernel: usbcore: registered new interface driver r8152 Sep 06 00:03:41 reMarkable kernel: usbcore: registered new interface driver asix Sep 06 00:03:41 reMarkable kernel: usbcore: registered new interface driver ax88179_178a Sep 06 00:03:41 reMarkable kernel: usbcore: registered new interface driver cdc_ether Sep 06 00:03:41 reMarkable kernel: usbcore: registered new interface driver net1080 Sep 06 00:03:41 reMarkable kernel: usbcore: registered new interface driver cdc_subset Sep 06 00:03:41 reMarkable kernel: usbcore: registered new interface driver zaurus Sep 06 00:03:41 reMarkable kernel: usbcore: registered new interface driver cdc_ncm Sep 06 00:03:41 reMarkable kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Sep 06 00:03:41 reMarkable kernel: ehci-mxc: Freescale On-Chip EHCI Host driver Sep 06 00:03:41 reMarkable kernel: usbcore: registered new interface driver usb_ehset_test Sep 06 00:03:41 reMarkable kernel: imx_usb 30b10000.usb: No over current polarity defined Sep 06 00:03:41 reMarkable kernel: imx_usb 30b10000.usb: 30b10000.usb supply vbus not found, using dummy regulator Sep 06 00:03:41 reMarkable kernel: imx_usb 30b20000.usb: No over current polarity defined Sep 06 00:03:41 reMarkable kernel: imx_usb 30b20000.usb: 30b20000.usb supply vbus not found, using dummy regulator Sep 06 00:03:41 reMarkable kernel: usbmisc_imx 30b20200.usbmisc: vbus is error Sep 06 00:03:41 reMarkable kernel: usbmisc_imx 30b20200.usbmisc: Error occurs during detection: -22 Sep 06 00:03:41 reMarkable kernel: using random self ethernet address Sep 06 00:03:41 reMarkable kernel: using random host ethernet address Sep 06 00:03:41 reMarkable kernel: usb0: HOST MAC d2:c7:5d:b9:b2:b2 Sep 06 00:03:41 reMarkable kernel: usb0: MAC 02:82:7b:e4:f5:07 Sep 06 00:03:41 reMarkable kernel: using random self ethernet address Sep 06 00:03:41 reMarkable kernel: using random host ethernet address Sep 06 00:03:41 reMarkable kernel: g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 Sep 06 00:03:41 reMarkable kernel: g_ether gadget: g_ether ready Sep 06 00:03:41 reMarkable kernel: input: 30370000.snvs:snvs-powerkey as /devices/soc0/soc/30000000.aips-bus/30370000.snvs/30370000.snvs:snvs-powerkey/input/input0 Sep 06 00:03:41 reMarkable kernel: input: Wacom I2C Digitizer as /devices/soc0/soc/30800000.aips-bus/30a20000.i2c/i2c-0/0-0009/input/input1 Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] pt_init: Request RST GPIO 13 Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] pt_init: Request IRQ GPIO 14 Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] pt_probe: PARADE No HW detect function pointer Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] pt_xres: 20ms HARD RESET on gpio=13 Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] pt_hw_hard_reset: executed HARD reset Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [1] pt_hid_output_validate_app_response: APP output response, wrong report_id Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [1] _pt_request_active_pip_protocol: pip_version Not Detected Sep 06 00:03:41 reMarkable kernel: g_ether gadget: high-speed config #1: CDC Ethernet (ECM) Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] _pt_poll_for_fw_exit_boot_mode: PIP 1.7 no support for ext STATUS, sleep 1001 Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] pt_enum_with_dut_: Exit FW BOOT Mode after 1001ms Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] pt_enum_with_dut_: HW Version: 1600.FFFF.FF Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] pt_enum_with_dut_: Completed Enumeration rc=0 On Attempt 1 Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] pt_probe: cd->startup_status=0x0002 status=0x01FD Sep 06 00:03:41 reMarkable kernel: input: pt_mt as /devices/soc0/soc/30800000.aips-bus/30a40000.i2c/i2c-2/2-0024/input/input2 Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] pt_pip1_send_output_and_wait_: HID output cmd execution timed out (1000ms) Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] pt_pip_resume_scanning_: Resume Scan PIP cmd failed. rc = -62 Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] pt_probe: TTDL Core Probe Completed Successfully Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] _pt_pip2_update_bl_status: ATM - Reset BL Status to 0 Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] upgrade_firmware_from_builtin: Enabling firmware class loader built-in Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] upgrade_firmware_from_builtin: Request FW file tt_fw.bin Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] upgrade_firmware_from_builtin: Fail request FW tt_fw.bin load Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] upgrade_firmware_from_builtin: Request FW file 1600_tt_fw.bin Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] upgrade_firmware_from_builtin: Fail request FW 1600_tt_fw.bin load Sep 06 00:03:41 reMarkable kernel: pt_loader_init: Parade FW Loader Driver (Version TTDL.04.11.977092) rc=0 Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] pt_parse_cmcp_threshold_builtin: Failed loading cmcp threshold file, attempting legacy file Sep 06 00:03:41 reMarkable kernel: pt_i2c_adapter 2-0024: [2] pt_parse_cmcp_threshold_builtin: Fail request cmcp threshold class file load Sep 06 00:03:41 reMarkable kernel: pt_device_access_init: Parade TTSP Device Access Driver (Built TTDL.04.11.977092) rc = 0 Sep 06 00:03:41 reMarkable kernel: snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc0 Sep 06 00:03:41 reMarkable kernel: i2c /dev entries driver Sep 06 00:03:41 reMarkable kernel: max77818-fuelgauge max77818-fuelgauge: DMA mask not set Sep 06 00:03:42 reMarkable kernel: power_supply max77818_battery: Not all required supplies found, defer probe Sep 06 00:03:42 reMarkable kernel: max77818-fuelgauge max77818-fuelgauge: failed to register supply: -517 Sep 06 00:03:42 reMarkable kernel: max77818-charger max77818-charger: DMA mask not set Sep 06 00:03:42 reMarkable kernel: max77818-charger max77818-charger: failed to unlock: -6 Sep 06 00:03:42 reMarkable kernel: max77818-charger max77818-charger: failed to init charger: 0 Sep 06 00:03:42 reMarkable kernel: imx2-wdt 30280000.wdog: timeout 60 sec (nowayout=0) Sep 06 00:03:42 reMarkable kernel: sdhci: Secure Digital Host Controller Interface driver Sep 06 00:03:42 reMarkable kernel: sdhci: Copyright(c) Pierre Ossman Sep 06 00:03:42 reMarkable kernel: sdhci-pltfm: SDHCI platform and OF driver helper Sep 06 00:03:42 reMarkable kernel: sdhci-esdhc-imx 30b50000.usdhc: allocated mmc-pwrseq Sep 06 00:03:42 reMarkable kernel: mmc1: SDHCI controller on 30b50000.usdhc [30b50000.usdhc] using ADMA Sep 06 00:03:42 reMarkable kernel: mmc2: SDHCI controller on 30b60000.usdhc [30b60000.usdhc] using ADMA Sep 06 00:03:42 reMarkable kernel: usbcore: registered new interface driver usbhid Sep 06 00:03:42 reMarkable kernel: usbhid: USB HID core driver Sep 06 00:03:42 reMarkable kernel: NET: Registered protocol family 26 Sep 06 00:03:42 reMarkable kernel: NET: Registered protocol family 10 Sep 06 00:03:42 reMarkable kernel: Segment Routing with IPv6 Sep 06 00:03:42 reMarkable kernel: sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver Sep 06 00:03:42 reMarkable kernel: NET: Registered protocol family 17 Sep 06 00:03:42 reMarkable kernel: Key type dns_resolver registered Sep 06 00:03:42 reMarkable kernel: imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 3 mkt segment 0 supported-hw 0x8 0x1 Sep 06 00:03:42 reMarkable kernel: mmc1: queuing unknown CIS tuple 0x80 (2 bytes) Sep 06 00:03:42 reMarkable kernel: Registering SWP/SWPB emulation handler Sep 06 00:03:42 reMarkable kernel: registered taskstats version 1 Sep 06 00:03:42 reMarkable kernel: Loading compiled-in X.509 certificates Sep 06 00:03:42 reMarkable kernel: mmc1: queuing unknown CIS tuple 0x80 (3 bytes) Sep 06 00:03:42 reMarkable kernel: mmc1: queuing unknown CIS tuple 0x80 (3 bytes) Sep 06 00:03:42 reMarkable kernel: mmc1: queuing unknown CIS tuple 0x80 (7 bytes) Sep 06 00:03:42 reMarkable kernel: mmc1: queuing unknown CIS tuple 0x81 (9 bytes) Sep 06 00:03:42 reMarkable kernel: mmc1: queuing unknown CIS tuple 0x8e (8 bytes) Sep 06 00:03:42 reMarkable kernel: EPD_VCOM: supplied by vcom Sep 06 00:03:42 reMarkable kernel: mmc1: new ultra high speed DDR50 SDIO card at address 0001 Sep 06 00:03:42 reMarkable kernel: mmc2: new HS400 MMC card at address 0001 Sep 06 00:03:42 reMarkable kernel: mmcblk2: mmc2:0001 FN62BB 7.28 GiB Sep 06 00:03:42 reMarkable kernel: mmcblk2boot0: mmc2:0001 FN62BB partition 1 4.00 MiB Sep 06 00:03:42 reMarkable kernel: mmcblk2boot1: mmc2:0001 FN62BB partition 2 4.00 MiB Sep 06 00:03:42 reMarkable kernel: mmcblk2rpmb: mmc2:0001 FN62BB partition 3 512 KiB, chardev (247:0) Sep 06 00:03:42 reMarkable kernel: mmcblk2: p1 p2 p3 p4 Sep 06 00:03:42 reMarkable kernel: mxsfb 30730000.lcdif: Driver set to prevent frying pan mode Sep 06 00:03:42 reMarkable kernel: mxsfb 30730000.lcdif: initialized Sep 06 00:03:42 reMarkable kernel: rm_otg_control otgcontrol1: rm_otgcontrol_probe: Defering probe due to charger driver not beingloaded/available yet Sep 06 00:03:42 reMarkable kernel: imx_usb 30b10000.usb: No over current polarity defined Sep 06 00:03:42 reMarkable kernel: imx_usb 30b10000.usb: 30b10000.usb supply vbus not found, using dummy regulator Sep 06 00:03:42 reMarkable kernel: power_supply max77818_battery: max77818_battery: Found supply : max77818-charger Sep 06 00:03:42 reMarkable kernel: imx_thermal tempmon: Commercial CPU temperature grade - max:95C critical:90C passive:85C Sep 06 00:03:42 reMarkable kernel: max77818-charger max77818-charger: set MODE bits to 0x5 Sep 06 00:03:42 reMarkable kernel: rm_otg_control otgcontrol1: Loaded successfully ! Sep 06 00:03:42 reMarkable kernel: imx_usb 30b10000.usb: No over current polarity defined Sep 06 00:03:42 reMarkable kernel: imx_usb 30b10000.usb: 30b10000.usb supply vbus not found, using dummy regulator Sep 06 00:03:42 reMarkable kernel: snvs_rtc 30370000.snvs:snvs-rtc-lp: setting system clock to 2022-09-06T00:03:40 UTC (1662422620) Sep 06 00:03:42 reMarkable kernel: EXT4-fs (mmcblk2p3): mounted filesystem with ordered data mode. Opts: (null) Sep 06 00:03:42 reMarkable kernel: ext4 filesystem being mounted at /root supports timestamps until 2038 (0x7fffffff) Sep 06 00:03:42 reMarkable kernel: VFS: Mounted root (ext4 filesystem) on device 179:3. Sep 06 00:03:42 reMarkable kernel: devtmpfs: mounted Sep 06 00:03:42 reMarkable kernel: Freeing unused kernel memory: 1024K Sep 06 00:03:42 reMarkable kernel: Run /sbin/init as init process Sep 06 00:03:42 reMarkable systemd[1]: /etc/systemd/system.conf.d/10-qt-env.conf:1: Assignment outside of section. Ignoring. Sep 06 00:03:42 reMarkable systemd[1]: systemd 244.5+ running in system mode. (-PAM -AUDIT -SELINUX -IMA -APPARMOR -SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN -PCRE2 default-hierarchy=hybrid) Sep 06 00:03:42 reMarkable systemd[1]: Detected architecture arm. Sep 06 00:03:42 reMarkable systemd[1]: Set hostname to . Sep 06 00:03:42 reMarkable systemd[1]: sync.service: Service has a D-Bus service name specified, but is not of type dbus. Ignoring. Sep 06 00:03:42 reMarkable kernel: random: systemd: uninitialized urandom read (16 bytes read) Sep 06 00:03:42 reMarkable systemd[1]: system-busybox\x2difplugd.slice: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling. Sep 06 00:03:42 reMarkable systemd[1]: (This warning is only shown for the first unit using IP firewalling.) Sep 06 00:03:42 reMarkable systemd[1]: Created slice system-busybox\x2difplugd.slice. Sep 06 00:03:42 reMarkable kernel: random: systemd: uninitialized urandom read (16 bytes read) Sep 06 00:03:42 reMarkable systemd[1]: Created slice system-getty.slice. Sep 06 00:03:42 reMarkable kernel: random: systemd: uninitialized urandom read (16 bytes read) Sep 06 00:03:42 reMarkable systemd[1]: Created slice system-serial\x2dgetty.slice. Sep 06 00:03:42 reMarkable systemd[1]: Created slice system-systemd\x2dfsck.slice. Sep 06 00:03:42 reMarkable systemd[1]: Created slice User and Session Slice. Sep 06 00:03:42 reMarkable systemd[1]: Started Dispatch Password Requests to Console Directory Watch. Sep 06 00:03:42 reMarkable systemd[1]: Started Forward Password Requests to Wall Directory Watch. Sep 06 00:03:42 reMarkable systemd[1]: Reached target Local Encrypted Volumes. Sep 06 00:03:42 reMarkable systemd[1]: Reached target Paths. Sep 06 00:03:42 reMarkable systemd[1]: Reached target Remote Encrypted Volumes. Sep 06 00:03:42 reMarkable systemd[1]: Reached target Remote File Systems. Sep 06 00:03:42 reMarkable systemd[1]: Reached target Slices. Sep 06 00:03:42 reMarkable systemd[1]: Reached target Swap. Sep 06 00:03:42 reMarkable systemd[1]: Listening on initctl Compatibility Named Pipe. Sep 06 00:03:42 reMarkable systemd[1]: Condition check resulted in Journal Audit Socket being skipped. Sep 06 00:03:42 reMarkable systemd[1]: Listening on Journal Socket (/dev/log). Sep 06 00:03:42 reMarkable systemd[1]: Listening on Journal Socket. Sep 06 00:03:42 reMarkable systemd[1]: Listening on Network Service Netlink Socket. Sep 06 00:03:42 reMarkable systemd[1]: Listening on udev Control Socket. Sep 06 00:03:42 reMarkable systemd[1]: Listening on udev Kernel Socket. Sep 06 00:03:42 reMarkable systemd[1]: Condition check resulted in Huge Pages File System being skipped. Sep 06 00:03:42 reMarkable systemd[1]: Condition check resulted in POSIX Message Queue File System being skipped. Sep 06 00:03:42 reMarkable systemd[1]: Mounting Kernel Debug File System... Sep 06 00:03:42 reMarkable systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway. Sep 06 00:03:42 reMarkable systemd[1]: Mounting Temporary Directory (/tmp)... Sep 06 00:03:42 reMarkable systemd[1]: Condition check resulted in Create list of static device nodes for the current kernel being skipped. Sep 06 00:03:42 reMarkable systemd[1]: Condition check resulted in File System Check on Root Device being skipped. Sep 06 00:03:42 reMarkable systemd[1]: Condition check resulted in Load Kernel Modules being skipped. Sep 06 00:03:42 reMarkable systemd[1]: Mounting FUSE Control File System... Sep 06 00:03:42 reMarkable systemd[1]: Mounting Kernel Configuration File System... Sep 06 00:03:42 reMarkable systemd[1]: Starting Remount Root and Kernel File Systems... Sep 06 00:03:42 reMarkable systemd[1]: Starting Apply Kernel Variables... Sep 06 00:03:42 reMarkable systemd[1]: Starting udev Coldplug all Devices... Sep 06 00:03:42 reMarkable systemd[1]: Mounted Kernel Debug File System. Sep 06 00:03:42 reMarkable systemd[1]: Mounted Temporary Directory (/tmp). Sep 06 00:03:42 reMarkable systemd[1]: Mounted FUSE Control File System. Sep 06 00:03:42 reMarkable systemd[1]: Mounted Kernel Configuration File System. Sep 06 00:03:42 reMarkable kernel: EXT4-fs (mmcblk2p3): re-mounted. Opts: (null) Sep 06 00:03:42 reMarkable kernel: ext4 filesystem being remounted at / supports timestamps until 2038 (0x7fffffff) Sep 06 00:03:42 reMarkable systemd[1]: Started Remount Root and Kernel File Systems. Sep 06 00:03:42 reMarkable systemd[1]: Condition check resulted in First Boot Wizard being skipped. Sep 06 00:03:42 reMarkable systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Sep 06 00:03:42 reMarkable systemd[1]: Condition check resulted in Create System Users being skipped. Sep 06 00:03:42 reMarkable systemd[1]: Starting Create Static Device Nodes in /dev... Sep 06 00:03:42 reMarkable systemd[1]: Started Apply Kernel Variables. Sep 06 00:03:43 reMarkable systemd[1]: Started Create Static Device Nodes in /dev. Sep 06 00:03:43 reMarkable systemd[1]: Reached target Local File Systems (Pre). Sep 06 00:03:43 reMarkable systemd[1]: Mounting /var/volatile... Sep 06 00:03:43 reMarkable systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm. Sep 06 00:03:43 reMarkable systemd[1]: Starting Journal Service... Sep 06 00:03:43 reMarkable systemd[1]: Starting udev Kernel Device Manager... Sep 06 00:03:43 reMarkable systemd[133]: haveged.service: PrivateNetwork=yes is configured, but the kernel does not support network namespaces, ignoring. Sep 06 00:03:43 reMarkable systemd[1]: Mounted /var/volatile. Sep 06 00:03:43 reMarkable systemd[1]: Condition check resulted in Bind mount volatile /var/cache being skipped. Sep 06 00:03:43 reMarkable systemd[1]: Condition check resulted in Bind mount volatile /var/lib being skipped. Sep 06 00:03:43 reMarkable systemd[1]: Starting Load/Save Random Seed... Sep 06 00:03:43 reMarkable systemd[1]: Condition check resulted in Bind mount volatile /var/spool being skipped. Sep 06 00:03:43 reMarkable systemd[1]: Condition check resulted in Bind mount volatile /srv being skipped. Sep 06 00:03:43 reMarkable systemd[135]: systemd-udevd.service: ProtectHostname=yes is configured, but the kernel does not support UTS namespaces, ignoring namespace setup. Sep 06 00:03:43 reMarkable systemd[1]: Started udev Kernel Device Manager. Sep 06 00:03:43 reMarkable systemd[1]: Starting Network Service... Sep 06 00:03:43 reMarkable systemd[1]: Started Network Service. Sep 06 00:03:43 reMarkable systemd[1]: Starting Wait for Network to be Configured... Sep 06 00:03:43 reMarkable systemd-journald[134]: Journal started -- Subject: The journal has been started -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The system journal process has started up, opened the journal -- files for writing and is now ready to process requests. Sep 06 00:03:43 reMarkable systemd-journald[134]: Runtime Journal (/run/log/journal/6751c30d92f5406095abb08659c7d7ba) is 6.0M, max 48.5M, 42.5M free. -- Subject: Disk space used by the journal -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Runtime Journal (/run/log/journal/6751c30d92f5406095abb08659c7d7ba) is currently using 6.0M. -- Maximum allowed usage is set to 48.5M. -- Leaving at least 24.2M free (of currently available 479.4M of disk space). -- Enforced usage limit is thus 48.5M, of which 42.5M are still available. -- -- The limits controlling how much disk space is used by the journal may -- be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, -- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in -- /etc/systemd/journald.conf. See journald.conf(5) for details. Sep 06 00:03:43 reMarkable systemd-sysctl[124]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Sep 06 00:03:41 reMarkable systemd-random-seed[136]: Kernel entropy pool is not initialized yet, waiting until it is. Sep 06 00:03:43 reMarkable systemd[1]: Started Journal Service. Sep 06 00:03:41 reMarkable systemd-networkd[138]: Enumeration completed Sep 06 00:03:43 reMarkable systemd[1]: Starting Flush Journal to Persistent Storage... -- Subject: A start job for unit systemd-journal-flush.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-journal-flush.service has begun execution. -- -- The job identifier is 20. Sep 06 00:03:43 reMarkable haveged[133]: haveged: command socket is listening at fd 3 Sep 06 00:03:43 reMarkable haveged[133]: haveged: ver: 1.9.13; arch: generic; vend: ; build: (gcc 9.3.0 CTV); collect: 128K Sep 06 00:03:43 reMarkable haveged[133]: haveged: cpu: (VC); data: 16K (D); inst: 16K (D); idx: 11/40; sz: 14660/63044 Sep 06 00:03:43 reMarkable haveged[133]: haveged: tot tests(BA8): A:1/1 B:1/1 continuous tests(B): last entropy estimate 8.00106 Sep 06 00:03:43 reMarkable haveged[133]: haveged: fills: 0, generated: 0 Sep 06 00:03:43 reMarkable systemd-journald[134]: Time spent on flushing to /var is 37.063ms for 326 entries. Sep 06 00:03:43 reMarkable systemd-journald[134]: System Journal (/var/log/journal/6751c30d92f5406095abb08659c7d7ba) is 10.0M, max 10.0M, 0B free. -- Subject: Disk space used by the journal -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- System Journal (/var/log/journal/6751c30d92f5406095abb08659c7d7ba) is currently using 10.0M. -- Maximum allowed usage is set to 10.0M. -- Leaving at least 20.0M free (of currently available 21.2M of disk space). -- Enforced usage limit is thus 10.0M, of which 0B are still available. -- -- The limits controlling how much disk space is used by the journal may -- be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, -- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in -- /etc/systemd/journald.conf. See journald.conf(5) for details. Sep 06 00:03:43 reMarkable kernel: random: crng init done Sep 06 00:03:43 reMarkable kernel: random: 7 urandom warning(s) missed due to ratelimiting Sep 06 00:03:43 reMarkable systemd[1]: Started Load/Save Random Seed. -- Subject: A start job for unit systemd-random-seed.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-random-seed.service has finished successfully. -- -- The job identifier is 30. Sep 06 00:03:43 reMarkable systemd[1]: Started Flush Journal to Persistent Storage. -- Subject: A start job for unit systemd-journal-flush.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-journal-flush.service has finished successfully. -- -- The job identifier is 20. Sep 06 00:03:43 reMarkable systemd[1]: Started udev Coldplug all Devices. -- Subject: A start job for unit systemd-udev-trigger.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-udev-trigger.service has finished successfully. -- -- The job identifier is 14. Sep 06 00:03:43 reMarkable systemd-udevd[144]: Using default interface naming scheme 'v243'. Sep 06 00:03:43 reMarkable systemd-udevd[144]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Sep 06 00:03:43 reMarkable systemd-networkd[138]: usb0: IPv6 successfully enabled Sep 06 00:03:43 reMarkable systemd-networkd[138]: usb0: Link UP Sep 06 00:03:43 reMarkable systemd-networkd[138]: usb0: Gained carrier Sep 06 00:03:43 reMarkable kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database Sep 06 00:03:43 reMarkable kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Sep 06 00:03:43 reMarkable kernel: brcmfmac: unknown parameter 'parameter' ignored Sep 06 00:03:43 reMarkable systemd[1]: Found device /sys/subsystem/net/devices/usb0. -- Subject: A start job for unit sys-subsystem-net-devices-usb0.device has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit sys-subsystem-net-devices-usb0.device has finished successfully. -- -- The job identifier is 80. Sep 06 00:03:43 reMarkable systemd-udevd[139]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Sep 06 00:03:43 reMarkable systemd-udevd[144]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Sep 06 00:03:43 reMarkable kernel: mmc1: queuing unknown CIS tuple 0x80 (2 bytes) Sep 06 00:03:43 reMarkable kernel: mmc1: queuing unknown CIS tuple 0x80 (3 bytes) Sep 06 00:03:43 reMarkable kernel: mmc1: queuing unknown CIS tuple 0x80 (3 bytes) Sep 06 00:03:43 reMarkable kernel: mmc1: queuing unknown CIS tuple 0x80 (7 bytes) Sep 06 00:03:43 reMarkable kernel: mmc1: queuing unknown CIS tuple 0x81 (9 bytes) Sep 06 00:03:43 reMarkable kernel: mmc1: queuing unknown CIS tuple 0x8e (8 bytes) Sep 06 00:03:43 reMarkable systemd[1]: Found device /dev/mmcblk2p1. -- Subject: A start job for unit dev-mmcblk2p1.device has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit dev-mmcblk2p1.device has finished successfully. -- -- The job identifier is 50. Sep 06 00:03:43 reMarkable kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43012-sdio for chip BCM43012/2 Sep 06 00:03:43 reMarkable systemd[1]: Found device /dev/mmcblk2p4. -- Subject: A start job for unit dev-mmcblk2p4.device has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit dev-mmcblk2p4.device has finished successfully. -- -- The job identifier is 40. Sep 06 00:03:43 reMarkable systemd-vconsole-setup[165]: KD_FONT_OP_GET failed while trying to get the font metadata: Function not implemented Sep 06 00:03:43 reMarkable systemd-vconsole-setup[165]: Fonts will not be copied to remaining consoles Sep 06 00:03:44 reMarkable systemd[1]: Reached target Hardware activated USB gadget. -- Subject: A start job for unit usb-gadget.target has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit usb-gadget.target has finished successfully. -- -- The job identifier is 106. Sep 06 00:03:44 reMarkable systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. -- Subject: A start job for unit systemd-rfkill.socket has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-rfkill.socket has finished successfully. -- -- The job identifier is 110. Sep 06 00:03:44 reMarkable systemd[1]: Starting File System Check on /dev/mmcblk2p1... -- Subject: A start job for unit systemd-fsck@dev-mmcblk2p1.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-fsck@dev-mmcblk2p1.service has begun execution. -- -- The job identifier is 49. Sep 06 00:03:44 reMarkable systemd[1]: Starting File System Check on /dev/mmcblk2p4... -- Subject: A start job for unit systemd-fsck@dev-mmcblk2p4.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-fsck@dev-mmcblk2p4.service has begun execution. -- -- The job identifier is 38. Sep 06 00:03:44 reMarkable systemd-fsck[170]: fsck.fat 4.1 (2017-01-24) Sep 06 00:03:44 reMarkable systemd-fsck[170]: /dev/mmcblk2p1: 8 files, 82/10211 clusters Sep 06 00:03:44 reMarkable systemd[1]: Started File System Check on /dev/mmcblk2p1. -- Subject: A start job for unit systemd-fsck@dev-mmcblk2p1.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-fsck@dev-mmcblk2p1.service has finished successfully. -- -- The job identifier is 49. Sep 06 00:03:44 reMarkable systemd[1]: Mounting /var/lib/uboot... -- Subject: A start job for unit var-lib-uboot.mount has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit var-lib-uboot.mount has begun execution. -- -- The job identifier is 48. Sep 06 00:03:44 reMarkable systemd-fsck[171]: home: clean, 2482/441504 files, 199229/1765120 blocks Sep 06 00:03:44 reMarkable systemd[1]: Started File System Check on /dev/mmcblk2p4. -- Subject: A start job for unit systemd-fsck@dev-mmcblk2p4.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-fsck@dev-mmcblk2p4.service has finished successfully. -- -- The job identifier is 38. Sep 06 00:03:44 reMarkable systemd[1]: home.mount: Directory /home to mount over is not empty, mounting anyway. -- Subject: Mount point is not empty -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The directory /home is specified as the mount point (second field in -- /etc/fstab or Where= field in systemd unit file) and is not empty. -- This does not interfere with mounting, but the pre-exisiting files in -- this directory become inaccessible. To see those over-mounted files, -- please manually mount the underlying file system to a secondary -- location. Sep 06 00:03:44 reMarkable systemd[1]: Mounting /home... -- Subject: A start job for unit home.mount has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit home.mount has begun execution. -- -- The job identifier is 37. Sep 06 00:03:44 reMarkable kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43012-sdio for chip BCM43012/2 Sep 06 00:03:44 reMarkable systemd[1]: Mounted /var/lib/uboot. -- Subject: A start job for unit var-lib-uboot.mount has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit var-lib-uboot.mount has finished successfully. -- -- The job identifier is 48. Sep 06 00:03:44 reMarkable kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43012/2 wl0: Apr 28 2021 15:42:47 version 18.35.389.66 (20cf392@SYNA) (wlan=r836194) FWID 01-fe2cf44 Sep 06 00:03:44 reMarkable kernel: EXT4-fs (mmcblk2p4): mounted filesystem with ordered data mode. Opts: (null) Sep 06 00:03:44 reMarkable systemd[1]: Mounted /home. -- Subject: A start job for unit home.mount has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit home.mount has finished successfully. -- -- The job identifier is 37. Sep 06 00:03:44 reMarkable systemd[1]: Mounting Bind mount /home/root/.entware over /opt... -- Subject: A start job for unit opt.mount has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit opt.mount has begun execution. -- -- The job identifier is 42. Sep 06 00:03:44 reMarkable systemd[1]: Starting Load/Save RF Kill Switch Status... -- Subject: A start job for unit systemd-rfkill.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-rfkill.service has begun execution. -- -- The job identifier is 131. Sep 06 00:03:44 reMarkable systemd[1]: Started Load/Save RF Kill Switch Status. -- Subject: A start job for unit systemd-rfkill.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-rfkill.service has finished successfully. -- -- The job identifier is 131. Sep 06 00:03:44 reMarkable systemd[1]: Mounted Bind mount /home/root/.entware over /opt. -- Subject: A start job for unit opt.mount has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit opt.mount has finished successfully. -- -- The job identifier is 42. Sep 06 00:03:44 reMarkable systemd[1]: Reached target Local File Systems. -- Subject: A start job for unit local-fs.target has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit local-fs.target has finished successfully. -- -- The job identifier is 36. Sep 06 00:03:44 reMarkable systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped. -- Subject: A start job for unit systemd-machine-id-commit.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-machine-id-commit.service has finished successfully. -- -- The job identifier is 35. Sep 06 00:03:44 reMarkable systemd[1]: Starting Create Volatile Files and Directories... -- Subject: A start job for unit systemd-tmpfiles-setup.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-tmpfiles-setup.service has begun execution. -- -- The job identifier is 60. Sep 06 00:03:44 reMarkable systemd[1]: Started Create Volatile Files and Directories. -- Subject: A start job for unit systemd-tmpfiles-setup.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-tmpfiles-setup.service has finished successfully. -- -- The job identifier is 60. Sep 06 00:03:44 reMarkable systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped. -- Subject: A start job for unit systemd-journal-catalog-update.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-journal-catalog-update.service has finished successfully. -- -- The job identifier is 62. Sep 06 00:03:44 reMarkable systemd[1]: Starting Network Time Synchronization... -- Subject: A start job for unit systemd-timesyncd.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-timesyncd.service has begun execution. -- -- The job identifier is 25. Sep 06 00:03:44 reMarkable systemd[1]: Condition check resulted in Update is Completed being skipped. -- Subject: A start job for unit systemd-update-done.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-update-done.service has finished successfully. -- -- The job identifier is 15. Sep 06 00:03:44 reMarkable systemd[1]: Starting Update UTMP about System Boot/Shutdown... -- Subject: A start job for unit systemd-update-utmp.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-update-utmp.service has begun execution. -- -- The job identifier is 105. Sep 06 00:03:44 reMarkable systemd-udevd[146]: Using default interface naming scheme 'v243'. Sep 06 00:03:44 reMarkable systemd-udevd[146]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Sep 06 00:03:44 reMarkable systemd[1]: Started Update UTMP about System Boot/Shutdown. -- Subject: A start job for unit systemd-update-utmp.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-update-utmp.service has finished successfully. -- -- The job identifier is 105. Sep 06 00:03:44 reMarkable systemd[180]: systemd-timesyncd.service: ProtectHostname=yes is configured, but the kernel does not support UTS namespaces, ignoring namespace setup. Sep 06 00:03:44 reMarkable systemd[1]: Started Network Time Synchronization. -- Subject: A start job for unit systemd-timesyncd.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-timesyncd.service has finished successfully. -- -- The job identifier is 25. Sep 06 00:03:44 reMarkable systemd[1]: Reached target System Initialization. -- Subject: A start job for unit sysinit.target has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit sysinit.target has finished successfully. -- -- The job identifier is 6. Sep 06 00:03:44 reMarkable systemd[1]: Started Daily Cleanup of Temporary Directories. -- Subject: A start job for unit systemd-tmpfiles-clean.timer has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-tmpfiles-clean.timer has finished successfully. -- -- The job identifier is 65. Sep 06 00:03:44 reMarkable systemd[1]: Reached target System Time Set. -- Subject: A start job for unit time-set.target has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit time-set.target has finished successfully. -- -- The job identifier is 29. Sep 06 00:03:44 reMarkable systemd[1]: Reached target System Time Synchronized. -- Subject: A start job for unit time-sync.target has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit time-sync.target has finished successfully. -- -- The job identifier is 28. Sep 06 00:03:44 reMarkable systemd[1]: Reached target Timers. -- Subject: A start job for unit timers.target has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit timers.target has finished successfully. -- -- The job identifier is 64. Sep 06 00:03:44 reMarkable systemd[1]: Listening on D-Bus System Message Bus Socket. -- Subject: A start job for unit dbus.socket has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit dbus.socket has finished successfully. -- -- The job identifier is 69. Sep 06 00:03:44 reMarkable systemd[1]: Listening on dropbear.socket. -- Subject: A start job for unit dropbear.socket has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit dropbear.socket has finished successfully. -- -- The job identifier is 71. Sep 06 00:03:44 reMarkable systemd[1]: Reached target Sockets. -- Subject: A start job for unit sockets.target has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit sockets.target has finished successfully. -- -- The job identifier is 68. Sep 06 00:03:44 reMarkable systemd[1]: Reached target Basic System. -- Subject: A start job for unit basic.target has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit basic.target has finished successfully. -- -- The job identifier is 2. Sep 06 00:03:44 reMarkable systemd[1]: Started ifplugd on usb0. -- Subject: A start job for unit busybox-ifplugd@usb0.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit busybox-ifplugd@usb0.service has finished successfully. -- -- The job identifier is 76. Sep 06 00:03:44 reMarkable systemd[1]: Started reMarkable crash uploader. -- Subject: A start job for unit crashuploader.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit crashuploader.service has finished successfully. -- -- The job identifier is 99. Sep 06 00:03:44 reMarkable systemd[1]: Started D-Bus System Message Bus. -- Subject: A start job for unit dbus.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit dbus.service has finished successfully. -- -- The job identifier is 96. Sep 06 00:03:44 reMarkable systemd[1]: Starting dhcpcd on all interfaces... -- Subject: A start job for unit dhcpcd.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit dhcpcd.service has begun execution. -- -- The job identifier is 100. Sep 06 00:03:44 reMarkable systemd[1]: Started Getty on tty1. -- Subject: A start job for unit getty@tty1.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit getty@tty1.service has finished successfully. -- -- The job identifier is 82. Sep 06 00:03:44 reMarkable systemd[1]: Starting Prepare for kdump... -- Subject: A start job for unit kdump-prep.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit kdump-prep.service has begun execution. -- -- The job identifier is 92. Sep 06 00:03:44 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 94. Sep 06 00:03:44 reMarkable systemd[1]: Started Serial Getty on ttymxc0. -- Subject: A start job for unit serial-getty@ttymxc0.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit serial-getty@ttymxc0.service has finished successfully. -- -- The job identifier is 86. Sep 06 00:03:44 reMarkable systemd[1]: Reached target Login Prompts. -- Subject: A start job for unit getty.target has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit getty.target has finished successfully. -- -- The job identifier is 81. Sep 06 00:03:44 reMarkable crashuploader[186]: Device serial number: RM110-229-91629 Sep 06 00:03:44 reMarkable systemd[1]: Started reMarkable Document Sync. -- Subject: A start job for unit sync.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit sync.service has finished successfully. -- -- The job identifier is 91. Sep 06 00:03:44 reMarkable crashuploader[186]: Watching "/home/root/" Sep 06 00:03:44 reMarkable dhcpcd[188]: dev: loaded udev Sep 06 00:03:44 reMarkable crashuploader[186]: All files uploaded Sep 06 00:03:44 reMarkable crashuploader[186]: All files uploaded Sep 06 00:03:44 reMarkable dhcpcd[188]: dev: loaded udev Sep 06 00:03:44 reMarkable systemd[1]: Starting Login Service... -- Subject: A start job for unit systemd-logind.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-logind.service has begun execution. -- -- The job identifier is 89. Sep 06 00:03:44 reMarkable systemd[1]: Starting Update Engine... -- Subject: A start job for unit update-engine.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit update-engine.service has begun execution. -- -- The job identifier is 74. Sep 06 00:03:44 reMarkable systemd[1]: Starting Pseudo service that ensures that Wacom firmware is up-to-date... -- Subject: A start job for unit wacom_flash.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit wacom_flash.service has begun execution. -- -- The job identifier is 98. Sep 06 00:03:44 reMarkable dbus-daemon[187]: dbus[187]: Unknown username "core" in message bus configuration file Sep 06 00:03:44 reMarkable dbus-daemon[187]: dbus[187]: Unknown username "core" in message bus configuration file Sep 06 00:03:44 reMarkable dhcpcd[188]: forked to background, child pid 205 Sep 06 00:03:44 reMarkable dhcpcd[188]: forked to background, child pid 205 Sep 06 00:03:44 reMarkable systemd[1]: Started dhcpcd on all interfaces. -- Subject: A start job for unit dhcpcd.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit dhcpcd.service has finished successfully. -- -- The job identifier is 100. Sep 06 00:03:44 reMarkable systemd[1]: kdump-prep.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit kdump-prep.service has successfully entered the 'dead' state. Sep 06 00:03:44 reMarkable systemd[1]: Started Prepare for kdump. -- Subject: A start job for unit kdump-prep.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit kdump-prep.service has finished successfully. -- -- The job identifier is 92. Sep 06 00:03:44 reMarkable update_engine[200]: I20220906 00:03:44.787657 200 main.cc:97] reMarkable Update Engine starting Sep 06 00:03:44 reMarkable update_engine[200]: I20220906 00:03:44.811564 200 update_check_scheduler.cc:82] Next update check in 2m33s Sep 06 00:03:44 reMarkable systemd[1]: Started Update Engine. -- Subject: A start job for unit update-engine.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit update-engine.service has finished successfully. -- -- The job identifier is 74. Sep 06 00:03:44 reMarkable systemd[1]: Created slice system-busybox\x2dudhcpd.slice. -- Subject: A start job for unit system-busybox\x2dudhcpd.slice has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit system-busybox\x2dudhcpd.slice has finished successfully. -- -- The job identifier is 140. Sep 06 00:03:44 reMarkable systemd[1]: Started udhcpd on usb0. -- Subject: A start job for unit busybox-udhcpd@usb0.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit busybox-udhcpd@usb0.service has finished successfully. -- -- The job identifier is 139. Sep 06 00:03:44 reMarkable systemd[1]: Reached target Network. -- Subject: A start job for unit network.target has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit network.target has finished successfully. -- -- The job identifier is 78. Sep 06 00:03:44 reMarkable systemd[1]: Starting Load dump capture kernel... -- Subject: A start job for unit kdump.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit kdump.service has begun execution. -- -- The job identifier is 93. Sep 06 00:03:44 reMarkable sync[195]: Lock in temp location Sep 06 00:03:44 reMarkable kexec[220]: syscall kexec_file_load not available. Sep 06 00:03:44 reMarkable sync[195]: Installing crash handler Sep 06 00:03:44 reMarkable sync[195]: installed crash handler Sep 06 00:03:44 reMarkable sync[195]: Running service... Sep 06 00:03:44 reMarkable systemd[198]: systemd-logind.service: ProtectHostname=yes is configured, but the kernel does not support UTS namespaces, ignoring namespace setup. Sep 06 00:03:44 reMarkable wacom_flash.sh[202]: Firmware is up-to-date (0x1231) Sep 06 00:03:44 reMarkable systemd[1]: Started Pseudo service that ensures that Wacom firmware is up-to-date. -- Subject: A start job for unit wacom_flash.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit wacom_flash.service has finished successfully. -- -- The job identifier is 98. Sep 06 00:03:44 reMarkable systemd-networkd[138]: usb0: Gained IPv6LL Sep 06 00:03:44 reMarkable systemd[1]: kdump.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit kdump.service has successfully entered the 'dead' state. Sep 06 00:03:44 reMarkable systemd[1]: Started Load dump capture kernel. -- Subject: A start job for unit kdump.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit kdump.service has finished successfully. -- -- The job identifier is 93. Sep 06 00:03:45 reMarkable xochitl[192]: STARTING RM2FB Sep 06 00:03:45 reMarkable xochitl[192]: Missing address for function 'getInstance' Sep 06 00:03:45 reMarkable xochitl[192]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:03:45 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:03:45 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:03:45 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 94 and the job result is failed. Sep 06 00:03:45 reMarkable systemd[1]: Started reMarkable main application. -- Subject: A start job for unit xochitl.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit xochitl.service has finished successfully. -- -- The job identifier is 97. Sep 06 00:03:45 reMarkable xochitl[234]: Sourcing /opt/etc/xochitl.env.d/rm2fb-preload.env Sep 06 00:03:45 reMarkable xochitl[234]: rm2fb server is not running: starting without rm2fb client Sep 06 00:03:45 reMarkable systemd-networkd[138]: wlan0: Link UP Sep 06 00:03:45 reMarkable systemd-timesyncd[180]: Network configuration changed, trying to establish connection. Sep 06 00:03:45 reMarkable dhcpcd[205]: wlan0: waiting for carrier Sep 06 00:03:45 reMarkable dhcpcd[205]: wlan0: carrier acquired Sep 06 00:03:45 reMarkable systemd[229]: systemd-logind.service: ProtectHostname=yes is configured, but the kernel does not support UTS namespaces, ignoring namespace setup. Sep 06 00:03:45 reMarkable dhcpcd[205]: DUID 00:01:00:01:2a:a5:27:a5:70:f7:54:58:1b:a4 Sep 06 00:03:45 reMarkable dhcpcd[205]: wlan0: IAID 54:58:1b:a4 Sep 06 00:03:45 reMarkable dhcpcd[205]: wlan0: carrier lost Sep 06 00:03:45 reMarkable systemd-logind[229]: Watching system buttons on /dev/input/event0 (30370000.snvs:snvs-powerkey) Sep 06 00:03:45 reMarkable xochitl[234]: 00:03:45.190 default QSocketNotifier: Can only be used with threads started with QThread Sep 06 00:03:45 reMarkable xochitl[234]: 00:03:45.194 default 2022-08-25T12:38:57Z heads/releases/lanford 54ab0acaff (int main(int, char**) /usr/src/debug/xochitl/override+gitAUTOINC+54ab0acaff-r0/git/src/main.cpp:166) Sep 06 00:03:45 reMarkable xochitl[234]: Registering exit handlers Sep 06 00:03:45 reMarkable xochitl[234]: 00:03:45.194 default we're running on an epaper device (int main(int, char**) /usr/src/debug/xochitl/override+gitAUTOINC+54ab0acaff-r0/git/src/main.cpp:173) Sep 06 00:03:45 reMarkable systemd-logind[229]: New seat seat0. -- Subject: A new seat seat0 is now available -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat -- -- A new seat seat0 has been configured and is now available. Sep 06 00:03:45 reMarkable systemd[1]: Started Login Service. -- Subject: A start job for unit systemd-logind.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-logind.service has finished successfully. -- -- The job identifier is 89. Sep 06 00:03:45 reMarkable xochitl[234]: Reading waveforms from /usr/share/remarkable/320_R404_AF9911_ED103TC2U2_VB3300-KCD_TC.wbf Sep 06 00:03:46 reMarkable xochitl[234]: 00:03:46.861 default EPD platform plugin loaded! Sep 06 00:03:46 reMarkable xochitl[234]: 00:03:46.863 default QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Sep 06 00:03:46 reMarkable xochitl[234]: 00:03:46.878 qt.qpa.input evdevtouch: Using device discovery Sep 06 00:03:46 reMarkable xochitl[234]: 00:03:46.884 qt.qpa.input evdevtouch: Adding device at /dev/input/event2 Sep 06 00:03:46 reMarkable xochitl[234]: 00:03:46.884 qt.qpa.input evdevtouch: Using device /dev/input/event2 Sep 06 00:03:46 reMarkable xochitl[234]: 00:03:46.885 qt.qpa.input evdevtouch: /dev/input/event2: Protocol type B (multi), filtered=no Sep 06 00:03:46 reMarkable xochitl[234]: 00:03:46.886 default Lock in temp location (static void DocumentFiles::storeLockFilesInTemp(bool) /usr/src/debug/xochitl/override+gitAUTOINC+54ab0acaff-r0/git/src/worker/include/worker/documentfiles.h:193) Sep 06 00:03:46 reMarkable xochitl[234]: 00:03:46.886 qt.qpa.input evdevtouch: /dev/input/event2: min X: 0 max X: 1403 Sep 06 00:03:46 reMarkable xochitl[234]: 00:03:46.887 qt.qpa.input evdevtouch: /dev/input/event2: min Y: 0 max Y: 1871 Sep 06 00:03:46 reMarkable xochitl[234]: 00:03:46.887 qt.qpa.input evdevtouch: /dev/input/event2: min pressure: 0 max pressure: 0 Sep 06 00:03:46 reMarkable xochitl[234]: 00:03:46.887 qt.qpa.input evdevtouch: /dev/input/event2: device name: pt_mt Sep 06 00:03:46 reMarkable usermod[245]: change user 'root' password Sep 06 00:03:47 reMarkable xochitl[234]: 00:03:47.072 rm.wifi Invalid supplicant received Sep 06 00:03:47 reMarkable dbus-daemon[187]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' requested by ':1.6' (uid=0 pid=234 comm="/usr/bin/xochitl --system ") Sep 06 00:03:47 reMarkable systemd[1]: Starting WPA supplicant... -- Subject: A start job for unit wpa_supplicant.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit wpa_supplicant.service has begun execution. -- -- The job identifier is 218. Sep 06 00:03:47 reMarkable dbus-daemon[187]: [system] Successfully activated service 'fi.w1.wpa_supplicant1' Sep 06 00:03:47 reMarkable systemd[1]: Started WPA supplicant. -- Subject: A start job for unit wpa_supplicant.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit wpa_supplicant.service has finished successfully. -- -- The job identifier is 218. Sep 06 00:03:47 reMarkable wpa_supplicant[253]: Successfully initialized wpa_supplicant Sep 06 00:03:47 reMarkable xochitl[234]: 00:03:47.472 default HttpListener: Listening on port 80 Sep 06 00:03:47 reMarkable xochitl[234]: Installing crash handler Sep 06 00:03:47 reMarkable xochitl[234]: installed crash handler Sep 06 00:03:49 reMarkable systemd[1]: systemd-rfkill.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-rfkill.service has successfully entered the 'dead' state. Sep 06 00:03:50 reMarkable xochitl[234]: 00:03:50.007 default Creating window Sep 06 00:03:50 reMarkable xochitl[234]: 00:03:50.086 qt.qpa.input evdevtouch: Updating QInputDeviceManager device count: 1 touch devices, 0 pending handler(s) Sep 06 00:03:50 reMarkable xochitl[234]: 00:03:50.195 rm.library Found deleted entry in library! "23bcd45d-80d4-4175-8bfd-3a54c956883d" Sep 06 00:03:50 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 1. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:03:50 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 294 and the job result is done. Sep 06 00:03:50 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 294. Sep 06 00:03:50 reMarkable xochitl[261]: STARTING RM2FB Sep 06 00:03:50 reMarkable xochitl[261]: Missing address for function 'getInstance' Sep 06 00:03:50 reMarkable xochitl[261]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:03:50 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:03:50 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:03:50 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 294 and the job result is failed. Sep 06 00:03:50 reMarkable xochitl[234]: 00:03:50.408 rm.library Found deleted entry in library! "457febea-f7c7-402a-8b0c-bd7b9c099746" Sep 06 00:03:50 reMarkable xochitl[234]: 00:03:50.550 rm.library Found deleted entry in library! "5ba2c589-5d57-4ecf-b3a0-e5f016a1bd56" Sep 06 00:03:50 reMarkable xochitl[234]: 00:03:50.954 rm.library Found deleted entry in library! "df90cb64-e8fe-46b3-968d-98fc8f1925e6" Sep 06 00:03:50 reMarkable xochitl[234]: 00:03:50.967 rm.library Found deleted entry in library! "e76d32f4-ae58-4088-bc42-159c7c27e90e" Sep 06 00:03:51 reMarkable xochitl[234]: 00:03:51.071 rm.wifi No interface to scan Sep 06 00:03:51 reMarkable xochitl[234]: 00:03:51.895 rm.network.document.sync Ignoring sync; not online Sep 06 00:03:51 reMarkable xochitl[234]: 00:03:51.969 rm.wifi wpa_supplicant came back, trying to reconnect Sep 06 00:03:52 reMarkable xochitl[234]: 00:03:52.413 rm.wifi Scanning: true Sep 06 00:03:54 reMarkable wpa_supplicant[253]: wlan0: Trying to associate with SSID 'International House' Sep 06 00:03:54 reMarkable xochitl[234]: 00:03:54.912 rm.wifi Scanning: false Sep 06 00:03:55 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 2. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:03:55 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 368 and the job result is done. Sep 06 00:03:55 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 368. Sep 06 00:03:55 reMarkable xochitl[262]: STARTING RM2FB Sep 06 00:03:55 reMarkable xochitl[262]: Missing address for function 'getInstance' Sep 06 00:03:55 reMarkable xochitl[262]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:03:55 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:03:55 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:03:55 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 368 and the job result is failed. Sep 06 00:03:56 reMarkable systemd-timesyncd[180]: Network configuration changed, trying to establish connection. Sep 06 00:03:56 reMarkable systemd[1]: Started Wait for Network to be Configured. -- Subject: A start job for unit systemd-networkd-wait-online.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-networkd-wait-online.service has finished successfully. -- -- The job identifier is 103. Sep 06 00:03:56 reMarkable systemd[1]: Reached target Network is Online. -- Subject: A start job for unit network-online.target has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit network-online.target has finished successfully. -- -- The job identifier is 102. Sep 06 00:03:57 reMarkable systemd[1]: Started A simple mDNS responder. -- Subject: A start job for unit qmdns-responder.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit qmdns-responder.service has finished successfully. -- -- The job identifier is 101. Sep 06 00:03:57 reMarkable systemd[1]: Reached target Multi-User System. -- Subject: A start job for unit multi-user.target has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit multi-user.target has finished successfully. -- -- The job identifier is 1. Sep 06 00:03:57 reMarkable systemd[1]: Starting Update UTMP about System Runlevel Changes... -- Subject: A start job for unit systemd-update-utmp-runlevel.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-update-utmp-runlevel.service has begun execution. -- -- The job identifier is 104. Sep 06 00:03:57 reMarkable systemd[1]: systemd-update-utmp-runlevel.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-update-utmp-runlevel.service has successfully entered the 'dead' state. Sep 06 00:03:57 reMarkable systemd[1]: Started Update UTMP about System Runlevel Changes. -- Subject: A start job for unit systemd-update-utmp-runlevel.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-update-utmp-runlevel.service has finished successfully. -- -- The job identifier is 104. Sep 06 00:03:57 reMarkable systemd[1]: Startup finished in 6.268s (kernel) + 16.443s (userspace) = 22.712s. -- Subject: System start-up is now complete -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- All system services necessary queued for starting at boot have been -- started. Note that this does not mean that the machine is now idle as services -- might still be busy with completing start-up. -- -- Kernel start-up required 6268752 microseconds. -- -- Initial RAM disk start-up required INITRD_USEC microseconds. -- -- Userspace start-up required 16443498 microseconds. Sep 06 00:03:57 reMarkable wpa_supplicant[253]: wlan0: Associated with 00:fe:c8:2e:60:c1 Sep 06 00:03:57 reMarkable wpa_supplicant[253]: wlan0: CTRL-EVENT-CONNECTED - Connection to 00:fe:c8:2e:60:c1 completed [id=1 id_str=] Sep 06 00:03:57 reMarkable wpa_supplicant[253]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Sep 06 00:03:57 reMarkable systemd-timesyncd[180]: Network configuration changed, trying to establish connection. Sep 06 00:03:57 reMarkable xochitl[234]: 00:03:57.790 rm.wifi wlan0: Link is up Sep 06 00:03:57 reMarkable kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Sep 06 00:03:57 reMarkable dhcpcd[205]: wlan0: carrier acquired Sep 06 00:03:57 reMarkable systemd-networkd[138]: wlan0: Gained carrier Sep 06 00:03:57 reMarkable dhcpcd[205]: wlan0: connected to Access Point `International House' Sep 06 00:03:57 reMarkable qmdns-responder[263]: reinitializing sockets Sep 06 00:03:57 reMarkable systemd-networkd[138]: wlan0: Connected WiFi access point: International House (00:fe:c8:2e:60:c1) Sep 06 00:03:57 reMarkable systemd-timesyncd[180]: Network configuration changed, trying to establish connection. Sep 06 00:03:57 reMarkable wpa_supplicant[253]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US Sep 06 00:03:57 reMarkable qmdns-responder[263]: reinitializing sockets Sep 06 00:03:57 reMarkable dhcpcd[205]: wlan0: IAID 54:58:1b:a4 Sep 06 00:03:58 reMarkable dhcpcd[205]: wlan0: rebinding lease of 10.1.14.190 Sep 06 00:03:58 reMarkable dhcpcd[205]: wlan0: probing address 10.1.14.190/16 Sep 06 00:03:59 reMarkable systemd-networkd[138]: wlan0: Gained IPv6LL Sep 06 00:03:59 reMarkable systemd-timesyncd[180]: Network configuration changed, trying to establish connection. Sep 06 00:03:59 reMarkable xochitl[234]: 00:03:59.129 rm.wifi wlan0: Address added: fe80::72f7:54ff:fe58:1ba4 Sep 06 00:04:00 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 3. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:04:00 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 442 and the job result is done. Sep 06 00:04:00 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 442. Sep 06 00:04:01 reMarkable xochitl[267]: STARTING RM2FB Sep 06 00:04:01 reMarkable xochitl[267]: Missing address for function 'getInstance' Sep 06 00:04:01 reMarkable xochitl[267]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:04:01 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:04:01 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:04:01 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 442 and the job result is failed. Sep 06 00:04:01 reMarkable xochitl[234]: 00:04:01.336 rm.updates Request finished. Was dispatched at: 2022-09-06T00:03:47.473 Sep 06 00:04:01 reMarkable xochitl[234]: 00:04:01.337 rm.updates Network error: QNetworkReply::OperationCanceledError Payload: "" Sep 06 00:04:01 reMarkable xochitl[234]: 00:04:01.337 rm.telemetry Sep 06 00:04:03 reMarkable dhcpcd[205]: wlan0: leased 10.1.14.190 for 6133 seconds Sep 06 00:04:03 reMarkable systemd-timesyncd[180]: Network configuration changed, trying to establish connection. Sep 06 00:04:03 reMarkable xochitl[234]: 00:04:03.465 rm.wifi wlan0: Address added: 10.1.14.190 Sep 06 00:04:03 reMarkable dhcpcd[205]: wlan0: adding route to 10.1.0.0/16 Sep 06 00:04:03 reMarkable dhcpcd[205]: wlan0: adding default route via 10.1.0.1 Sep 06 00:04:03 reMarkable xochitl[234]: 00:04:03.473 rm.wifi Got gateway: 10.1.0.1 Sep 06 00:04:03 reMarkable xochitl[234]: 00:04:03.483 rm.wifi We probably have Internet Sep 06 00:04:06 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 4. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:04:06 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 516 and the job result is done. Sep 06 00:04:06 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 516. Sep 06 00:04:06 reMarkable xochitl[289]: STARTING RM2FB Sep 06 00:04:06 reMarkable xochitl[289]: Missing address for function 'getInstance' Sep 06 00:04:06 reMarkable xochitl[289]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:04:06 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:04:06 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:04:06 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 516 and the job result is failed. Sep 06 00:04:10 reMarkable kernel: SDOE: disabling Sep 06 00:04:10 reMarkable kernel: EPD_VCOM: disabling Sep 06 00:04:11 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 5. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:04:11 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 590 and the job result is done. Sep 06 00:04:11 reMarkable systemd[1]: rm2fb.service: Start request repeated too quickly. Sep 06 00:04:11 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:04:11 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 590 and the job result is failed. Sep 06 00:04:29 reMarkable xochitl[234]: 00:04:29.366 rm.telemetry Sep 06 00:04:30 reMarkable update_engine[200]: I20220906 00:04:30.336494 200 update_attempter.cc:533] Not updating boot flags, we don't know the state of the application. Sep 06 00:04:32 reMarkable systemd[1]: Created slice system-dropbear.slice. -- Subject: A start job for unit system-dropbear.slice has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit system-dropbear.slice has finished successfully. -- -- The job identifier is 665. Sep 06 00:04:32 reMarkable systemd[1]: Condition check resulted in SSH Key Generation being skipped. -- Subject: A start job for unit dropbearkey.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit dropbearkey.service has finished successfully. -- -- The job identifier is 739. Sep 06 00:04:32 reMarkable systemd[1]: Started SSH Per-Connection Server (10.11.99.2:54066). -- Subject: A start job for unit dropbear@0-10.11.99.1:22-10.11.99.2:54066.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit dropbear@0-10.11.99.1:22-10.11.99.2:54066.service has finished successfully. -- -- The job identifier is 664. Sep 06 00:04:32 reMarkable dropbear[298]: Child connection from ::ffff:10.11.99.2:54066 Sep 06 00:04:33 reMarkable dropbear[298]: Pubkey auth succeeded for 'root' with key sha1!! e1:f7:99:5e:f4:74:bc:a8:6e:29:ae:46:9f:92:f8:80:b5:f9:25:80 from ::ffff:10.11.99.2:54066 Sep 06 00:04:33 reMarkable crashuploader[186]: All files uploaded Sep 06 00:04:33 reMarkable crashuploader[186]: All files uploaded Sep 06 00:04:36 reMarkable systemd[1]: Reloading. Sep 06 00:04:36 reMarkable systemd[1]: /etc/systemd/system.conf.d/10-qt-env.conf:1: Assignment outside of section. Ignoring. Sep 06 00:04:36 reMarkable systemd[1]: sync.service: Service has a D-Bus service name specified, but is not of type dbus. Ignoring. Sep 06 00:04:37 reMarkable systemd[1]: Reloading. Sep 06 00:04:37 reMarkable systemd[1]: /etc/systemd/system.conf.d/10-qt-env.conf:1: Assignment outside of section. Ignoring. Sep 06 00:04:37 reMarkable systemd[1]: sync.service: Service has a D-Bus service name specified, but is not of type dbus. Ignoring. Sep 06 00:04:37 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 740. Sep 06 00:04:38 reMarkable xochitl[347]: STARTING RM2FB Sep 06 00:04:38 reMarkable xochitl[347]: Missing address for function 'getInstance' Sep 06 00:04:38 reMarkable xochitl[347]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:04:38 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:04:38 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:04:38 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 740 and the job result is failed. Sep 06 00:04:43 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 1. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:04:43 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 814 and the job result is done. Sep 06 00:04:43 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 814. Sep 06 00:04:43 reMarkable xochitl[348]: STARTING RM2FB Sep 06 00:04:43 reMarkable xochitl[348]: Missing address for function 'getInstance' Sep 06 00:04:43 reMarkable xochitl[348]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:04:43 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:04:43 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:04:43 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 814 and the job result is failed. Sep 06 00:04:48 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 2. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:04:48 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 888 and the job result is done. Sep 06 00:04:48 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 888. Sep 06 00:04:48 reMarkable xochitl[349]: STARTING RM2FB Sep 06 00:04:48 reMarkable xochitl[349]: Missing address for function 'getInstance' Sep 06 00:04:48 reMarkable xochitl[349]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:04:48 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:04:48 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:04:48 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 888 and the job result is failed. Sep 06 00:04:53 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 3. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:04:53 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 962 and the job result is done. Sep 06 00:04:53 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 962. Sep 06 00:04:53 reMarkable xochitl[352]: STARTING RM2FB Sep 06 00:04:53 reMarkable xochitl[352]: Missing address for function 'getInstance' Sep 06 00:04:53 reMarkable xochitl[352]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:04:53 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:04:53 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:04:53 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 962 and the job result is failed. Sep 06 00:04:53 reMarkable systemd-timesyncd[180]: Initial synchronization to time server 216.239.35.4:123 (time2.google.com). Sep 06 00:04:58 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 4. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:04:58 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 1036 and the job result is done. Sep 06 00:04:58 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 1036. Sep 06 00:04:58 reMarkable xochitl[354]: STARTING RM2FB Sep 06 00:04:58 reMarkable xochitl[354]: Missing address for function 'getInstance' Sep 06 00:04:58 reMarkable xochitl[354]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:04:58 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:04:58 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:04:58 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 1036 and the job result is failed. Sep 06 00:05:03 reMarkable xochitl[234]: 00:05:03.581 rm.telemetry Too Many Requests Sep 06 00:05:03 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 5. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:05:03 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 1110 and the job result is done. Sep 06 00:05:03 reMarkable systemd[1]: rm2fb.service: Start request repeated too quickly. Sep 06 00:05:03 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:05:03 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 1110 and the job result is failed. Sep 06 00:05:41 reMarkable systemd[1]: Reloading. Sep 06 00:05:41 reMarkable systemd[1]: /etc/systemd/system.conf.d/10-qt-env.conf:1: Assignment outside of section. Ignoring. Sep 06 00:05:42 reMarkable systemd[1]: sync.service: Service has a D-Bus service name specified, but is not of type dbus. Ignoring. Sep 06 00:05:42 reMarkable systemd[1]: Reloading. Sep 06 00:05:42 reMarkable systemd[1]: /etc/systemd/system.conf.d/10-qt-env.conf:1: Assignment outside of section. Ignoring. Sep 06 00:05:43 reMarkable systemd[1]: sync.service: Service has a D-Bus service name specified, but is not of type dbus. Ignoring. Sep 06 00:05:43 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 1184. Sep 06 00:05:43 reMarkable xochitl[402]: STARTING RM2FB Sep 06 00:05:43 reMarkable xochitl[402]: Missing address for function 'getInstance' Sep 06 00:05:43 reMarkable xochitl[402]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:05:43 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:05:43 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:05:43 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 1184 and the job result is failed. Sep 06 00:05:48 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 1. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:05:48 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 1258 and the job result is done. Sep 06 00:05:48 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 1258. Sep 06 00:05:48 reMarkable xochitl[405]: STARTING RM2FB Sep 06 00:05:48 reMarkable xochitl[405]: Missing address for function 'getInstance' Sep 06 00:05:48 reMarkable xochitl[405]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:05:48 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:05:48 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:05:48 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 1258 and the job result is failed. Sep 06 00:05:54 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 2. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:05:54 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 1332 and the job result is done. Sep 06 00:05:54 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 1332. Sep 06 00:05:54 reMarkable xochitl[406]: STARTING RM2FB Sep 06 00:05:54 reMarkable xochitl[406]: Missing address for function 'getInstance' Sep 06 00:05:54 reMarkable xochitl[406]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:05:54 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:05:54 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:05:54 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 1332 and the job result is failed. Sep 06 00:05:59 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 3. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:05:59 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 1406 and the job result is done. Sep 06 00:05:59 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 1406. Sep 06 00:05:59 reMarkable xochitl[407]: STARTING RM2FB Sep 06 00:05:59 reMarkable xochitl[407]: Missing address for function 'getInstance' Sep 06 00:05:59 reMarkable xochitl[407]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:05:59 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:05:59 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:05:59 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 1406 and the job result is failed. Sep 06 00:06:04 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 4. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:06:04 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 1480 and the job result is done. Sep 06 00:06:04 reMarkable systemd[1]: Starting reMarkable 2 Framebuffer Server... -- Subject: A start job for unit rm2fb.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has begun execution. -- -- The job identifier is 1480. Sep 06 00:06:04 reMarkable xochitl[408]: STARTING RM2FB Sep 06 00:06:04 reMarkable xochitl[408]: Missing address for function 'getInstance' Sep 06 00:06:04 reMarkable xochitl[408]: PLEASE SEE https://github.com/ddvk/remarkable2-framebuffer/issues/18 Sep 06 00:06:04 reMarkable systemd[1]: rm2fb.service: Main process exited, code=exited, status=255/EXCEPTION -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- An ExecStart= process belonging to unit rm2fb.service has exited. -- -- The process' exit code is 'exited' and its exit status is 255. Sep 06 00:06:04 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:06:04 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 1480 and the job result is failed. Sep 06 00:06:09 reMarkable systemd[1]: rm2fb.service: Scheduled restart job, restart counter is at 5. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit rm2fb.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Sep 06 00:06:09 reMarkable systemd[1]: Stopped reMarkable 2 Framebuffer Server. -- Subject: A stop job for unit rm2fb.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit rm2fb.service has finished. -- -- The job identifier is 1554 and the job result is done. Sep 06 00:06:09 reMarkable systemd[1]: rm2fb.service: Start request repeated too quickly. Sep 06 00:06:09 reMarkable systemd[1]: rm2fb.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit rm2fb.service has entered the 'failed' state with result 'exit-code'. Sep 06 00:06:09 reMarkable systemd[1]: Failed to start reMarkable 2 Framebuffer Server. -- Subject: A start job for unit rm2fb.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit rm2fb.service has finished with a failure. -- -- The job identifier is 1554 and the job result is failed. Sep 06 00:06:18 reMarkable update_engine[200]: I20220906 00:06:18.026813 200 prefs.cc:54] certificate-report-to-send-update not present in /var/lib/update_engine/prefs Sep 06 00:06:18 reMarkable update_engine[200]: I20220906 00:06:18.027024 200 prefs.cc:54] certificate-report-to-send-download not present in /var/lib/update_engine/prefs Sep 06 00:06:18 reMarkable update_engine[200]: I20220906 00:06:18.033447 200 omaha_request_params.cc:75] Current group set to Prod Sep 06 00:06:18 reMarkable update_engine[200]: I20220906 00:06:18.034142 200 update_attempter.cc:533] Not updating boot flags, we don't know the state of the application. Sep 06 00:06:18 reMarkable update_engine[200]: I20220906 00:06:18.034209 200 update_attempter.cc:710] Scheduling an action processor start. Sep 06 00:06:18 reMarkable update_engine[200]: I20220906 00:06:18.034333 200 action_processor.cc:41] ActionProcessor::StartProcessing: OmahaRequestAction Sep 06 00:06:18 reMarkable update_engine[200]: I20220906 00:06:18.036974 200 omaha_request_action.cc:280] Posting an Omaha request to https://updates.cloud.remarkable.engineering/service/update2 Sep 06 00:06:18 reMarkable update_engine[200]: I20220906 00:06:18.037077 200 omaha_request_action.cc:281] Request: Sep 06 00:06:18 reMarkable update_engine[200]: Sep 06 00:06:18 reMarkable update_engine[200]: Sep 06 00:06:18 reMarkable update_engine[200]: Sep 06 00:06:18 reMarkable update_engine[200]: Sep 06 00:06:18 reMarkable update_engine[200]: Sep 06 00:06:18 reMarkable update_engine[200]: Sep 06 00:06:18 reMarkable update_engine[200]: Sep 06 00:06:18 reMarkable update_engine[200]: Sep 06 00:06:18 reMarkable update_engine[200]: I20220906 00:06:18.037185 200 libcurl_http_fetcher.cc:50] Starting/Resuming transfer Sep 06 00:06:18 reMarkable update_engine[200]: I20220906 00:06:18.045647 200 libcurl_http_fetcher.cc:176] Setting up curl options for HTTPS Sep 06 00:06:18 reMarkable update_engine[200]: I20220906 00:06:18.046383 200 libcurl_http_fetcher.cc:466] Setting up timeout source: 1 seconds. Sep 06 00:06:19 reMarkable update_engine[200]: I20220906 00:06:19.001062 200 libcurl_http_fetcher.cc:261] HTTP response code: 200 Sep 06 00:06:19 reMarkable update_engine[200]: I20220906 00:06:19.001616 200 libcurl_http_fetcher.cc:323] Transfer completed (200), 309 bytes downloaded Sep 06 00:06:19 reMarkable update_engine[200]: I20220906 00:06:19.001708 200 omaha_request_action.cc:670] Omaha request response: Sep 06 00:06:19 reMarkable update_engine[200]: Sep 06 00:06:19 reMarkable update_engine[200]: Sep 06 00:06:19 reMarkable update_engine[200]: Sep 06 00:06:19 reMarkable update_engine[200]: Sep 06 00:06:19 reMarkable update_engine[200]: Sep 06 00:06:19 reMarkable update_engine[200]: Sep 06 00:06:19 reMarkable update_engine[200]: Sep 06 00:06:19 reMarkable update_engine[200]: Sep 06 00:06:19 reMarkable update_engine[200]: I20220906 00:06:19.009773 200 omaha_request_action.cc:444] No update. Sep 06 00:06:19 reMarkable update_engine[200]: I20220906 00:06:19.009929 200 action_processor.cc:99] ActionProcessor::ActionComplete: finished OmahaRequestAction, starting OmahaResponseHandlerAction Sep 06 00:06:19 reMarkable update_engine[200]: I20220906 00:06:19.009976 200 omaha_response_handler_action.cc:38] There are no updates. Aborting. Sep 06 00:06:19 reMarkable update_engine[200]: I20220906 00:06:19.010015 200 action_processor.cc:81] ActionProcessor::ActionComplete: OmahaResponseHandlerAction action failed. Aborting processing. Sep 06 00:06:19 reMarkable update_engine[200]: I20220906 00:06:19.010047 200 action_processor.cc:87] ActionProcessor::ActionComplete: finished last action of type OmahaResponseHandlerAction Sep 06 00:06:19 reMarkable update_engine[200]: I20220906 00:06:19.010078 200 update_attempter.cc:313] Processing Done. Sep 06 00:06:19 reMarkable update_engine[200]: I20220906 00:06:19.010152 200 update_attempter.cc:351] No update. Sep 06 00:06:19 reMarkable update_engine[200]: I20220906 00:06:19.010228 200 update_check_scheduler.cc:82] Next update check in 41m25s Sep 06 00:06:39 reMarkable xochitl[234]: 00:06:39.119 rm.telemetry Too Many Requests Sep 06 00:07:12 reMarkable xochitl[234]: 00:07:12.060 rm.telemetry Too Many Requests Sep 06 00:07:38 reMarkable crashuploader[186]: All files uploaded Sep 06 00:07:38 reMarkable crashuploader[186]: All files uploaded ```
matteodelabre commented 1 year ago

As mentioned in the logs, please see https://github.com/ddvk/remarkable2-framebuffer/issues/18.