reMarkable Hardware
Hardware (rM2) / Photos
- 1.2 GHz dual core ARMv7 Processor rev 5 (armv7l) - 32 bit
- Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
- 1 GB LPDDR3 SDRAM
- 8 GB internal storage
- 10.3” monochrome 1872 x 1404 resolution (226 DPI)
- Wi-Fi 2.4GHz and 5GHz
- USB-C
- Accessory port - Pogo connector - dot on left side is in fact a host usb connector.
Display - VB3300-KCA
The rm2 does not use the embedded epdc (Electronic Paper Display Controller) of the imx7. Instead the e-Ink display is connected directly to the LCD controller. This means all stuff that the epdc would normally do is now done in software… The software that implements the epdc in software is called SWTCON by the reMarkable team. It’s closed sources.
The current workaround to get rm1 apps working on the rm2 is using the remarkable2-framebuffer project.
USB Ethernet interface
Remarkable rM2 device
dmesg
Driver is cdc_ether
Issue
10.11.99.1 not reachable
Usb is recognized (dmesg similar to above) but no working ethernet interface associated or the link is down.
=> This is because of network change I made to define a static ip for thist host. see network.
- when using networkd, an interface is created but down and not properly setup.
- when using NetworkManager no interface is created unless explicitly authorized:
Manual Workaround to resolve this (not persistant).
Host must have a different ip (10.11.99.2) than remarkable which must be the gateway (10.11.99.1) with routing different the default
Additional issue only public key available for this pc ?
I had messed up the network config for the remarkable (host ip vs gateway). so ssh root@10.11.99.1 brougth me back to the host - not the remarkable -, and the host has password authentication disabled.