Framebuffer size mismatch on rM2 v3.24.0.147 #25
Description
When trying to use goMarkableStream, the output looks like this - https://ibb.co/NdJg8HcR
I've previously used reSnap successfully, with no problems. It appeared after the last update (I was enrolled in the beta program)
reSnap -o 1.png output:
Input #0, rawvideo, from 'fd:':
Duration: N/A, start: 0.000000, bitrate: 1051315 kb/s
Stream #0:0: Video: rawvideo (Y1[0][16] / 0x10003159), gray16le, 1872x1404, 1051315 kb/s, 25 tbr, 25 tbn
Stream mapping:
Stream #0:0 -> #0:0 (rawvideo (native) -> png (native))
Output #0, image2, to '1.png':
Metadata:
encoder : Lavf61.7.100
Stream #0:0: Video: png, rgb24(pc, gbr/unknown/unknown, progressive), 1404x1872, q=2-31, 200 kb/s, 25 fps, 25 tbn
Metadata:
encoder : Lavc61.19.101 png
[image2 @ 0x2bd6ae40] The specified filename '1.png' does not contain an image sequence pattern or a pattern is invalid.
[image2 @ 0x2bd6ae40] Use a pattern such as %03d for an image sequence or use the -update option (with -frames:v 1 if needed) to write a single image.
[out#0/image2 @ 0x2bd6ad40] video:35KiB audio:0KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: unknown
frame= 1 fps=0.0 q=-0.0 Lsize=N/A time=00:00:00.04 bitrate=N/A speed=0.261xThe output file has correct size - 1404x1872.
When checking the framebuffers, there is only /dev/fb0.
fbset output:
mode "260x1408-85"
# D: 34.722 MHz, H: 132.024 kHz, V: 85.012 Hz
geometry 260 1408 260 23936 32
timings 28800 1 1 1 143 1 1
accel false
rgba 8/16,8/8,8/0,0/0
endmodewhich says that the framebuffer is 260x1408 - completely different size.
I've never used toltec nor changed anything in the framebuffer myself. There is also no fb shim in directories like /dev/shm/ (directory exists, its just empty)
What can be the cause of the problem? Is it just the update?
I've been thinking about installing ddvk's rm2fb which features a shim, but its a workaround, and would required downgrading rM2 version to v3.3.2.x