Support for Remarkable 2

[faroit]

• KOReader version: v2020.10
• Device: Remarkable 2

Issue

Koreader does not start on Remarkable 2.

• screen freezes
• systemctl start xochitl brings it back to normal

Steps to reproduce

Followed installation instruction on https://github.com/koreader/koreader/wiki/Installation-on-ReMarkable

crash.log (if applicable)

Original fb settings: bitdepth = 32, rotation = 0
Switching fb bitdepth to 8bpp & rotation to Portrait
[FBInk] Detected a reMarkable (Zero Gravitas)
Variable fb info: 260x1408 (260x23936), 32bpp @ rotation: 1 (Clockwise, 90°)
Fixed fb info: ID is "mxs-lcdif", length of fb mem: 33554432 bytes & line length: 1040 bytes
---------------------------------------------
                launching...
  _  _____  ____                _
 | |/ / _ \|  _ \ ___  __ _  __| | ___ _ __
 | ' / | | | |_) / _ \/ _` |/ _` |/ _ \ '__|
 | . \ |_| |  _ <  __/ (_| | (_| |  __/ |
 |_|\_\___/|_| \_\___|\__,_|\__,_|\___|_|

 It's a scroll... It's a codex... It's KOReader!

 [*] Current time: 10/14/20-14:29:45
 [*] Version: v2020.10-1-gac6b121_2020-10-10

ffi.load: blitbuffer
ffi.load: SDL2
ffi.load (warning): libSDL2.so: cannot open shared object file: No such file or directory
ffi.load: libSDL2-2.0.so
ffi.load (warning): libSDL2-2.0.so: cannot open shared object file: No such file or directory
ffi.load: libSDL2-2.0.so.0
ffi.load (warning): libSDL2-2.0.so.0: cannot open shared object file: No such file or directory
SDL2 not loaded:        ./setupkoenv.lua:27: Not able to load dynamic library: libSDL2-2.0.so.0
[ko-input] Forked off fake event generator(pid:325).
10/14/20-14:29:45 INFO  initializing for device reMarkable
10/14/20-14:29:45 INFO  framebuffer resolution: {
    ["w"] = 260,
    ["h"] = 1408
}
ffi.load: libs/libmupdf.so
ffi.load: libs/libwrap-mupdf.so
ffi.load: libs/libfreetype.so.6
10/14/20-14:29:46 INFO  Loading plugins from directory: plugins
ffi.load: sqlite3
ffi.load: z
ffi.load (assisted searchpath): ./libs/libz.so.1
ffi.load: sqlite3
10/14/20-14:29:46 INFO  Plugin  plugins/autofrontlight.koplugin/main.lua  has been disabled.
10/14/20-14:29:46 INFO  Plugin  plugins/autostandby.koplugin/main.lua  has been disabled.
10/14/20-14:29:46 INFO  Plugin  plugins/timesync.koplugin/main.lua  has been disabled.
10/14/20-14:29:46 INFO  Plugin  plugins/SSH.koplugin/main.lua  has been disabled.
10/14/20-14:29:46 INFO  Plugin  plugins/keepalive.koplugin/main.lua  has been disabled.
10/14/20-14:29:46 INFO  Plugin  plugins/hello.koplugin/main.lua  has been disabled.
10/14/20-14:29:46 INFO  FM loaded plugin autosuspend at plugins/autosuspend.koplugin
10/14/20-14:29:46 INFO  FM loaded plugin backgroundrunner at plugins/backgroundrunner.koplugin
10/14/20-14:29:46 INFO  FM loaded plugin batterystat at plugins/batterystat.koplugin
10/14/20-14:29:46 INFO  FM loaded plugin calibre at plugins/calibre.koplugin
10/14/20-14:29:46 INFO  FM loaded plugin coverbrowser at plugins/coverbrowser.koplugin
10/14/20-14:29:46 INFO  FM loaded plugin docsettingtweak at plugins/docsettingtweak.koplugin
10/14/20-14:29:46 INFO  FM loaded plugin evernote at plugins/evernote.koplugin
10/14/20-14:29:46 INFO  FM loaded plugin gestures at plugins/gestures.koplugin
ffi.load: libs/liblept.so.5
ffi.load: libs/libk2pdfopt.so.2

[NiLuJe]

The rM 2 isn't actually supported, as you've just found out ;o).

The fb info looks... wonky as hell. There wouldn't happen to be another fb device would it? Because fb0 doesn't look to be the one we want here...

[faroit]

@NiLuJe thanks for the reply. If there is anything I could do to help, just let me know.

[NiLuJe]

I'd start with what tinkerers have managed to do on the rM 2 in general. I don't have (either) device, so I don't even really know where those kind of discussions usually happen, but I don't think it's on MobileRead like our other platforms. Reddit? Discord?

[NiLuJe]

Apparently, surprise, surprise, the kernel sources aren't out. So, I assume people are waiting on that, first.

[faroit]

@NiLuJe @pazos @raisjnn @tcrs I am glad to help (e.g. giving you more details or giving you access to my device through a video call).

[gbyl]

@faroit Even for RM1 there are simply not enough contributors who own the device to have feature-parity with say the Kobo port of KOReader. It might take a while until RM2 is supported. Here is a bit more info about what you can look forward to: Eeems-Org/oxide#48 (comment)

[raisjn]

thanks @faroit, i'm still waiting to receive my rM2 but have been very interested in trying to draw anything to the framebuffer.

you can ping me on discord (username: rsjn) if you have time to do a call and poke around. there's a lot of friendly homebrew devs on discord server, so you can usually get help with any homebrew apps there.

it originally took me about a week (maybe less, maybe more) to figure out how to draw to framebuffer for rM1 and that was with other people's work available. my main goal is figuring out how to draw anything into the FB, from there, i think everything else will follow.

currently, i think the display is elcdif with mxsfb driver, but not sure if we are using kms/drm driver or fbdev. if its using kms, then drawing may be pretty different. i'm hoping that we still have access via /dev/fb0 and that there aren't undocumented ioctls we need to use.

[raisjn]

also, cc @ddvk

[NiLuJe]

Assuming this behaves like a sane Linux system, KMS shouldn't prevent using the raw fb device.

e.g., that jokey comment at the end is accurate: over the years, I've tested it against both amdgpudrmfb fbs & whatever the binary nvidia blob actually does ^^.

[FBInk] Variable fb info: 2560x1440, 32bpp @ rotation: 0 (Upright, 0°)
[FBInk] Fixed fb info: ID is "amdgpudrmfb", length of fb mem: 14745600 bytes & line length: 10240 bytes

[raisjn]

Assuming this behaves like a sane Linux system, KMS shouldn't prevent using the raw fb device.

good point! bokluk also checked and it looks like /dev/fb0 is being used (and not /dev/dri/render*), so xochitl is using fbdev (at least for some things)