I have a Librem 13 v3, but it it reported as v2:
$ sudo ./cbmem -c | egrep -i "coreboot-|purism|librem" coreboot-4.8.1-7-g30300027ce-4.8.1-Purism-3 Wed Aug 15 04:00:19 UTC 2018 bootblock starting... coreboot-4.8.1-7-g30300027ce-4.8.1-Purism-3 Wed Aug 15 04:00:19 UTC 2018 romstage starting... coreboot-4.8.1-7-g30300027ce-4.8.1-Purism-3 Wed Aug 15 04:00:19 UTC 2018 postcar starting... coreboot-4.8.1-7-g30300027ce-4.8.1-Purism-3 Wed Aug 15 04:00:19 UTC 2018 ramstage starting... Root Device (Purism Librem 13 v2) Found mainboard Purism Librem 13 v2
This seems to be a hardware error; Purism failed to change their revision number:
https://forums.puri.sm/t/new-librem-laptop/2823
dmidecode reports correctly:
$ sudo dmidecode # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. 8 structures occupying 428 bytes. Table at 0x7AA9A020. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: coreboot Version: 4.8.1-Purism-3 Release Date: 08/15/2018 ROM Size: 16 MB Characteristics: PCI is supported PC Card (PCMCIA) is supported BIOS is upgradeable Selectable boot is supported ACPI is supported Targeted content distribution is supported BIOS Revision: 4.0 Firmware Revision: 0.0 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Purism Product Name: Librem 13 v3 Version: 3.0 Serial Number: 317739 UUID: Not Settable Wake-up Type: Reserved SKU Number: Not Specified Family: Librem 13 Handle 0x0002, DMI type 2, 14 bytes Base Board Information Manufacturer: Purism Product Name: Librem 13 v3 Version: 3.0 Serial Number: 317739 Asset Tag: Not Specified Features: None Location In Chassis: Not Specified Chassis Handle: 0x0003 Type: Unknown
Pipe key did not work on German keyboard after upgrading from Debian 9 stable to unstable.
https://forums.puri.sm/t/librem-13-v3-font-size-too-small-or-too-large/3711/3
The librem 13 v3 has 1920x1080 px resolution, on 13". -This is "hidpi".- actually, it's mdpi, because it's not double the "normal" resolution but only 1.6x.
Standard PureOS shipped had much too small fonts and icons.
xdpyinfo reported 96 dpi resolution, which is really wrong. In reality it's 166 dpi.
I told X11 to use the real screen size, and Cinnamon uses this information correctly (KDE, Gnome, Mate, XFCE not):
$ cat /etc/X11/xorg.conf.d/90-librem-display.conf # xdpyinfo | grep -B2 resolution # https://wiki.archlinux.org/index.php/xorg#Display_size_and_DPI Section "Monitor" Identifier "eDP-1" DisplaySize 294 166 # In millimeters EndSection
I also had to set "Font scaling factor" in the cinnamon font settings to 1.3
Settings > Appearance > Fonts > Details > DPI: 125
On 166 (automatic) the fonts were too large.
The traditional approach to supporting high DPI has been one where Qt scaled fonts automatically, and then provided a DPI value that application code could use to scale the rest of the UI.
Setting the DPI value manually to a lower values gives better font sizes:
$ QT_FONT_DPI=128 zeal
Maybe the main issue is that Cinnamon pushes the configured font sizes (for Gtk) 1:1 to Qt, probably via the QT_QPA_PLATFORMTHEME variable.
Edit ding executable, add:
tk scaling 2.0
At first I thought it was again Cinnamon that took all the CPU, but it was a firmware problem.
Wrong: I needed a new coreboot version to fix this.
The problem still happens after upgrading the firmware to coreboot-4.8.1-7-g30300027ce-4.8.1-Purism-3.
Instructions: