How Can I Set Up Dual-Screen With E Ink Linux And HDMI?

Short and practical checklist from my weekend tinkering: first, find the device — run 'xrandr' (X11) or 'swaymsg -t get_outputs' (Wayland), 'lsusb' and 'dmesg' for USB/DisplayLink, and look for framebuffer devices under '/dev/fb*' if it’s an SPI/HAT panel. If it’s DisplayLink, install the evdi/displaylink driver with DKMS; if it’s a native HDMI e‑ink monitor it usually acts like any other display.

Then arrange screens: on X use 'xrandr --output HDMI-1 --right-of eDP-1' and tweak '--mode' or '--scale' as needed; on sway use output commands. Disable or reduce compositor effects for the e‑ink display (compositors often cause annoying partial redraws). For HATs use vendor utilities to push updates or refresh the panel explicitly — many people use a script that forces a full refresh after big UI changes.

Final tips: use large fonts and high‑contrast themes, turn off animations in browsers and desktops, and prefer apps that render static images (PDF readers, image viewers, simple terminals). If you run into tearing/blank screens check kernel logs, group permissions for 'video', and whether the driver is bound to the right output. Once tuned, an e‑ink second monitor is wonderfully low‑strain for reading and long coding sessions.

Okay, let’s get this humming — I love tinkering with odd displays, so here’s a clear path to get an e‑ink panel working side-by-side with an HDMI screen on Linux.

First, identify how your e‑ink is connected. If it’s a true HDMI e‑ink monitor (like some Dasung or HDMI‑capable Waveshare units), it will show up as a normal output in 'xrandr' or your desktop settings. Run 'xrandr --verbose' or 'xrandr --listproviders' to see outputs. If it’s a USB display (DisplayLink) you’ll likely need the 'evdi'/'displaylink' driver installed; check 'lsusb' and 'dmesg' to confirm. If it’s an e‑ink HAT or SPI panel (common for Raspberry Pi style setups), it might expose a framebuffer device like '/dev/fb1' instead of a normal monitor.

Once you’ve identified it, configure the layout. For X11: use 'xrandr --output HDMI-1 --auto --right-of eDP-1' (replace names shown by your system). You can set modes, scale or rotation with extra flags. For Wayland (sway/wlroots) use 'swaymsg output HDMI-A-1 enable' or 'wlr-randr' depending on compositor. If you’re using a framebuffer device, you’ll either run a compositor that can bind to it or push images directly with framebuffer tools (for SPI/HAT style panels use vendor scripts or Python libraries that call the epaper driver to update the screen).

Important e‑ink tips: disable or tweak compositors because many compositors’ partial redraws confuse e‑ink refresh logic — try turning off picom or using a compositorless session for the e‑ink output. Increase font sizes, use high‑contrast color schemes, and disable animations to avoid constant full refreshes. If your vendor provides a refresh utility (many do), create a small script or udev rule to force a full refresh after big updates. Expect slower refresh behaviour and design workflows (terminals, readers, static docs) around that. Play with it and enjoy the relaxing, paperlike setup!

This got me excited — I’ve set up a few two‑monitor rigs, including an e‑ink screen, so here’s a practical, no-nonsense walkthrough that worked for me.

Step one: discovery. Open a terminal and run 'xrandr' (for X11) or 'lsusb' and 'dmesg' if the display is USB. If the e‑ink is HDMI‑native, it shows as an output like 'HDMI‑1'. If it’s DisplayLink, you’ll see a USB vendor ID and probably need the 'displaylink'/'evdi' stack. If it’s an SPI HAT (Raspberry Pi scenarios), look for '/dev/fb1' or check the vendor’s Python tools.

Step two: drivers. For DisplayLink: install the official driver or community packages (on Debian/Ubuntu that usually means DKMS + evdi). For HDMI‑native no extra driver is usually needed. For framebuffer e‑ink HATs use the vendor-provided kernel module or their 'epd' Python scripts.

Step three: layout and tweaks. With X: 'xrandr --output HDMI-1 --mode 1200x825 --right-of eDP-1'. With sway: 'swaymsg output DP-1 pos 1920 0'. Disable compositor effects on the e‑ink screen (compositors can introduce partial updates that look terrible). I like to script a forced full-refresh using the vendor tool after moving windows or changing backgrounds. Also change cursor settings (big, static) and prefer apps that render static content — 'zathura', 'feh', or terminal apps like 'st' look great.

If things fail: check logs ('journalctl -k', 'dmesg'), confirm '/dev/fb*' permissions, and make sure your user is in groups like 'video'. Small note — many e‑ink monitors will never be as snappy as LCDs, so plan to use the e‑ink primarily for reading, coding with static layouts, or terminal work. It becomes wonderfully restful once tuned right.