RM2 firm:3.16.2.3 - input/output error

[prichelle]

Trying to run the software on my new RM2.

Having this error:

2024/12/25 11:03:03 read /proc/196/mem: input/output error
2024/12/25 11:03:03 read /proc/196/mem: input/output error

Any idea how to solve it ?

[owulveryck]

Maybe restart the device and try again.
My guess is that the xochitl process has respawn and it is causing this error

[Lewiscowles1986]

This works for me on 3.16.2.3 self-compiled today. Amazing software. Did you use a pre-built binary @prichelle or can you say which commit sha you built, and if you used the makefile, and what commands you used?

[runjerry]

I am having the same error on my RM2 (3.16.2.3), for both pre-built binary and self-compiled version (both v0.18).

[Lewiscowles1986]

Ah, this could be that you are not using main specifically commit hash faf29d8e8d812704c47b2444ba34cf87cd3903f7
link

So maybe try checking out that commit sha and let us know if that works @runjerry

[runjerry]

Ah, this could be that you are not using main specifically commit hash faf29d8e8d812704c47b2444ba34cf87cd3903f7 link

So maybe try checking out that commit sha and let us know if that works @runjerry

Thank you for your suggestions. But I still got the same error self-compiling from the above commit. Any further idea?

[Lewiscowles1986]

read /proc/196/mem: input/output error

no idea. I've never received this error. But then I'm on the rMpp, so maybe some paper-pro code is causing this?

[lorenzo-di-gregorio]

Ah, this could be that you are not using main specifically commit hash faf29d8e8d812704c47b2444ba34cf87cd3903f7 link
So maybe try checking out that commit sha and let us know if that works @runjerry

Thank you for your suggestions. But I still got the same error self-compiling from the above commit. Any further idea?

I get the same error after the last update 4.2.87 on reMarkable 2.0 Linux Kernel 5.4.70-v1.5.1-rm11x, image version 3.16.2.3.

I get TLS handshake error from 10.11.99.9:: remote error: tls: unknown certificate and then
read /proc//mem: input/output error

With RK_HTTPS=false of course I do not get the TLS handshake error, but I still get the input/output error.

[owulveryck]

It looks that it cannot find the pid of the xochitl process.
Did you try the v0.18 of the tool?
We may have introduced a regression with the new code.

[lorenzo-di-gregorio]

this is v0.18 as binary and I have checked that the xochitl process has the process number reported in the proc-mem string on the console, I can also see it in proc-maps.

[lorenzo-di-gregorio]

Maybe the following sightings can help spotting the problem. I've dug a bit into the issue following https://blog.owulveryck.info/2021/03/30/streaming-the-remarkable-2.html and I've noticed that in /proc/$(pidof xochitl)/maps I see:

6e642000-6fe00000 rw-s a9d00000 00:06 1138       /dev/fb0
6fe00000-6fec6000 rw-p 00000000 00:00 0 
6fec6000-6ff00000 ---p 00000000 00:00 0 
6ff00000-6ff02000 r--s 00000000 b3:04 262349     /home/root/.cache/remarkable/xochitl/qmlcache/e424f67b8d71d979cd711710afe192ea7cc96647.qmlc
6ff02000-6ff10000 r--s 00000000 b3:04 262354     /home/root/.cache/remarkable/xochitl/qmlcache/6cc884f70452b695f0e6c611289a4620476780b9.qmlc
6ff10000-6ff15000 r-xp 00000000 b3:02 2156       /usr/lib/plugins/imageformats/libqico.so
6ff15000-6ff24000 ---p 00005000 b3:02 2156       /usr/lib/plugins/imageformats/libqico.so

I can read exactly 1138688 bytes (from 0x6fe00000 to 0x6FF16000) with

dd if=/proc/$(pidof xochitl)/mem of=image.raw count=1138688 bs=1 skip=$((0x6fe00000))

and not one byte more, otherwise I get Input/output error.