Support for system software version 2.6

[pks40]

Apparently, the binaries need to be recompiled to work with the new reMarkable software version 2.6, since some shared libraries were updated to new versions in this update. (At least libcrypto.so was updated; I’m not sure about others.)

(Perhaps this is also an issue for nix-remarkable, but since I don’t really understand the build system, I’m not sure about this.)

[bordaigorl]

@pl-semiotics any news about this?
I haven't got the update yet (and would not want to update until this is fixed as I use rmview daily for work) so I cannot test workarounds...
For RM1, would compiling the server linking those libraries statically help?
Maybe not efficient but would allow for the same executable to work on all versions?
What about RM2, I think there's some patching involved and there things might be less obvious?

@pks40 would be nice to have a list of the updated libraries...(are you on RM1 or RM2?)

[bbolker]

Got the update, would be eager to test on both RM1 and RM2 if the instructions for applying patches/workarounds/updates are sufficiently easy for me to follow ...

Should I start by following the build instructions on the front page of this repo and then figuring out how to combine them with rmview (which is the only way in which I use the software)?

[wmkoolen]

Dear all,

The following works for me.

1. while still on firmware 2.5, copy /usr/lib/libcrypto.so.1.0.2 from the remarkable to somewhere safe.
2. upgrade to 2.6. This will introduce /usr/lib/libcrypto.so.1.1 and remove /usr/lib/libcrypto.so.1.0.2
3. copy the stored libcrypto.so.1.0.2 from step 1 back onto the remarkable (as /usr/lib/libcrypto.so.1.0.2)

Now rM-vnc-server-standalone lauches and works, and hence so does rmview.
This holds both on firmware versions 2.6.1.71 and 2.6.2.75.

[juanfcocontreras]

Hello @wmkoolen ,

Thanks for the information. Could you upload libcrypto.so.1.0.2? I've already upgraded my Remarkable, so I have no option to get this file anymore.

Thanks in advance!

[bordaigorl]

@juanfcocontreras Here it is (from RM1):
libcrypto.so.1.0.2.zip

@wmkoolen Thank you so much for reporting this!

If anybody could post the library from RM2-pre2.6 @bbolker may test it out for us

[bordaigorl]

Here is libcrypto for RM2 (courtesy of Mattéo Delabre)
libcrypto.so.1.0.2.zip
@bbolker could you test it for us?
Just unzip it and copy it over with (assuming connection via USB)

scp /path/of/uncompressed/libcrypto.so.1.0.2 root@10.11.99.1:/usr/lib/

Then start rmview and check if it works.

[juanfcocontreras]

Here is libcrypto for RM2 (courtesy of Mattéo Delabre)
libcrypto.so.1.0.2.zip
@bbolker could you test it for us?
Just unzip it and copy it over with (assuming connection via USB)

scp /path/of/uncompressed/libcrypto.so.1.0.2 root@10.11.99.1:/usr/lib/

Then start rmview and check if it works.

It's working here in my RM2.

Thank you so much!

[bordaigorl]

@juanfcocontreras could you maybe check if the file I posted for RM1 works on RM2 too?

[juanfcocontreras]

@juanfcocontreras could you maybe check if the file I posted for RM1 works on RM2 too?

Sure, and it's working too!

[pks40]

Thanks a lot to all of you for working this out! It’s great that only one library has to be included ...

[bbolker]

posted file works for me on RM2, hurrah.

[pl-semiotics]

Hi all, I apologize for the delay on this issue---I don't have 2.6, and I don't know where an updated sdk might be, so it's nontrivial to build a version that natively links against the new library. I'm hoping that an updated sdk gets released at some point, but if not I will look at hacking something together once I have the update. Unfortunately the rM for some reason doesn't have the normal libX.so.<major> symlink and SONAME for crypto, which causes this issue even though the major version of libcrypto hasn't changed.

Using the old library will probably work in the meantime, although I'm hesitant to recommend this, since there are various potential issues. If you want to avoid cluttering up /usr/lib, you should be able to drop it anywhere you like and use LD_LIBRARY_PATH=/path/to/directory/containing/it when launching the vnc server, by the way.

[bordaigorl]

@pl-semiotics thanks for the remarks. In which ways the workaround could cause problems?
Do you think simlinking the old version to the new one would work?
Would linking the library statically (wrt the old version) work and avoid the potential problems?

[bordaigorl]

I got the update and can confirm that ln /usr/lib/libcrypto.so.1.1 /usr/lib/libcrypto.so.1.0.2 works on my RM1.
I do not know if there are bad side effects of using the "wrong" version.
I'd like to push a fix for rmview but I am not sure which to pick. Shipping yet another binary seems a bit ugly, symlinking seems better but I don't know if it's safe (and I am not sure which version of libcrypto is on the RM2).
Any ideas?