toltec-dev
3.22 Support
Due to the current state of rm2fb support in the community. We will not be supporting every OS release after 3.3.2. Instead, we will be adding 3.5.2 and 3.8.2 support. When timower's rm2fb is updated to support newer OS versions, we will work on only supporting those versions.
Hi,
as fas as I comprehend, the issue is displaying apps on OS release > 3.4. But how is the state for non-UI packages?
Would it be possible to install wireguard und webinterface-wifi on the latest OS versions?
Cheers
Hi,
as fas as I comprehend, the issue is displaying apps on OS release > 3.4. But how is the state for non-UI packages? Would it be possible to install
wireguardundwebinterface-wifion the latest OS versions?Cheers
Wireguard was removed from toltec for the OS 3.x repositories: https://github.com/toltec-dev/toltec/releases/tag/2024-W21
As for webinterface-wifi, you would likely be able to follow it's manual install instructions to run it on 3.4.
Oh, that's too bad regarding wireguard 😲
So generally speaking that's a "no"? Non-GUI apps don't work any better than GUI-applications?
Oh, that's too bad regarding wireguard 😲
linux-stracciatella contains the wireguard module.
So generally speaking that's a "no"? Non-GUI apps don't work any better than GUI-applications?
That was not a "no". That was a "you can manually install stuff if you want, and it may work". Toltec does not support anything past 3.4, and as such we don't test it, and heavily recommend against using it on a newer version.
Is the current last version (3.14.1.10) on reMarkable Paper Pro supported?
Is the current last version (3.14.1.10) on reMarkable Paper Pro supported?
Please refer to the website for what versions are currently supported by toltec: https://toltec-dev.org/
does this help at all? https://www.reddit.com/r/RemarkableTablet/comments/1h7jg6w/terminal_on_the_remarkable_paper_pro/
I'm not knowledged about technical aspect of this issue but FWIW I'd like to bring 2 repos into your attention in case they may contribute to this issue:
- https://github.com/asivery/qtfb
- https://github.com/asivery/rmpp-qtfb-shim
@asivery seems to do framework level studies on recent versions of RM.
I'm sorry if this comment is a noise.
We are aware of these repositories. The changes in #860 will still be required to allow splitting display providers on different OS versions that we support, and #929 would need to be addressed to support the rMPP
Is the plan still to provide 3.5.2 and 3.8.2 support, or has that been leapfrogged to something even newer?
The linked PR tracks progress. Please don't ask if there has been an update. This project is run by volunteers that all have their own lives. If there was an update, it will either be on the PR, or this ticket would be closed and there would be a release.
Due to how stale this all is, next efforts will be for 3.18 support. There are rm2fb solutions in the works for 3.18 that we can take advantage of as indicated above. Targeting 3.18 also allows us to start adding rMPP support.
@Eeems I just got my RPP! It's on v 3.20.0.87. Can you point me to how to downgrade, if needed, to run VNSEE. Or point me to simple instructions led way to install fuller Linux, so I could light web browse, use as second display for MacBook/iPad. I suppose if I'm VNSee, I don't need to browse from RPP. ALSO, is landscape supported? Many thanks!
If you have the time/skills to help test some of the open PRs in our build process, that would be helpful:
- https://github.com/toltec-dev/toolchain/pull/41
- https://github.com/toltec-dev/build/pull/58
After those are tested and merged, we can start the work to start integrating the rMPP into the install process, package builds, etc. We also need a generic rm2fb replacement for the rMPP for toltec to work, as qtfb doesn't match the featureset toltec is built around, so a lot of the tooling like launcherctl will not work in it's current form.
How are things looking for RM/RM2 3.18 support? Currently on 3.11.2.5 (RM2) and not sure I want to go through the manual downgrade process (https://github.com/Jayy001/codexctl/issues/95#issuecomment-2305529048) if this is around the corner. If there are blockers, is there anything I can do to help?
How are things looking for RM/RM2 3.18 support? Currently on 3.11.2.5 (RM2) and not sure I want to go through the manual downgrade process (https://github.com/Jayy001/codexctl/issues/95#issuecomment-2305529048) if this is around the corner. If there are blockers, is there anything I can do to help?
See my previous message.
Blocking architecture changes have been completed. Next steps will be to create a new PR that starts doing the following:
- [x] Split out repos for 3.22 support.
- [x] Split out rMPP and rMPPM specific repos.
- [x] Make all rmall packages that are not truly architecture independent into specific rM1 and rM2 builds only.
- [x] Update bootstrap script to handle install on 3.22, rMPP, and rMPPM
- [ ] Sort out how to handle decryption on bootup without xochitl running
- [x] Take the changes from #860 for splitting out display providers on different OS versions.
- rM2 will use timower's rm2fb implementation
- rMPP/rMPPM will not have a display server yet, future work will be required to add support, as well as port more of the packages.
- [x] Tag PR with experimental to start doing testing.
- [ ] Test upgrade process from 3.3.2.1666.
- [ ] Test install process on 3.22.