rM2 version 3.20 installation #47
timower
started this conversation in
Show and tell
Replies: 2 comments 9 replies
-
|
Hello, thank you for your work! What happens when Toltec just gives when trying to reenable? I've downgraded to 3.3.2.1066 to install Toltec and upgraded to 3.20 again... |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
I tried following this guide. I have been running 3.8 with rm2fb for a while. My Remarkable 2 is now stuck at "reMarkable Paper tablet is starting". I can't connect via SSH. I guess I have to get a pogopin adapter now. The fault is all mine, I should have looked into remarkable2-recovery beforehand. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've been using 3.20 for a while, and it's been quite stable. So I thought I'd write down some installation notes, based on #32 so others can try as well.
Warning
As with any modification there are risks of boot loops. Make sure you have remarkable2-recovery working before trying!
Installation
I'm assuming you're already on 3.20, if not install it using codexctl.
0. Manual test
First you should verify that the rm2fb server works, and that xochitl can use it. For this download the
install.tar.gzpackage from the v0.1.3 release.Then transfer
opt/bin/rm2fb_server,opt/lib/librm2fb_client.soandopt/bin/yaft(or any other app to test. To the device, I'm assuming all the binaries are in/home/root:Now, in another terminal, start xochitl using the rm2fb client:
Exit xochitl (either by pressing power off in the UI, or Ctrl-C in the terminal).
Now try yaft, to make sure other apps also work correctly:
If everything worked, exit yaft (type exit on the reMarkable), and kill the rm2fb server by pressing Ctrl-C.
1. Making sure
/homeis mountedImportant
Data encryption is not supported, make sure it's disabled before continuing.
Newer xochitl versions support disk encryption, so
/homeis not mounted on startup, but only after entering the pin in xochitl. This won't work with toltec or the modifications we're going to do.Modify
/etc/fstaband comment out the line that starts with/dev/unknown, and add a new line that mounts/dev/mmcblk2p4on/home:/dev/mmcblk2p1 /var/lib/uboot/ vfat defaults,nofail 0 2 # /dev/unknown /home ext4 defaults,nofail,noauto,x-systemd.after=xochitl.service,x-systemd.device-timeout=0 0 3 /dev/mmcblk2p4 /home ext4 defaults,nofail 0 3Now reboot and make sure everything is still working. Check
systemctl --failedto make sure there are no failed units.2. Re-enable or install toltec
Warning
Toltec on anything 3.3+ is not officially supported. Packages will break, and the toltec maintainers won't offer support.
Install toltec in the usual method, or re-enable an existing install. Make sure to disable any package that could cause issues (older rm2fb servers, anything that installs services, ...).
Also use the testing channel, as that has an updated wget that works correctly on 3.20:
3. Install the ipks
First stop xochitl again:
> systemctl stop xochitlDownload the rm2display.ipk (and any other apps you want) from the v0.1.3 release.
Install them using opkg:
> opkg install rm2display.ipk yaft.ipk rocket.ipkNow you can test the rm2fb server:
> systemctl start rocketIf everything worked correctly, the rocket launch screen should show up.
Stop rocket, and make sure xochitl also still works:
Verify that the LD_PRELOAD was set correctly by checking
journalctl:You can now disable xochitl and enable rocket so it starts on boot:
Next steps
I've only verified that xochitl, rocket, yaft, tilem and koreader work. I've not verified any other launchers, or packages from toltec.
The system changed significantly (move from Qt5 to Qt6) so expect many toltec packages to break.
Beta Was this translation helpful? Give feedback.
All reactions