puri.sm librem 13 v3

rich1.0phorkiehttps://p.cweiske.de/puri.sm librem 13 v3Christian Weiske86400900900 <link rel="stylesheet" href="https://p.cweiske.de/css/embed.css"/> <div class="phork" id="584"> <div class="phork-file"> <div class="phork-content"> <div class="document" id="wrong-hardware-revision-reported"> <h1 class="title">Wrong Hardware revision reported</h1> <p>I have a Librem 13 v3, but it it reported as v2:</p> <pre class="literal-block"> $ 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 </pre> <p>This seems to be a hardware error; Purism failed to change their revision number:</p> <p><a class="reference external" href="https://forums.puri.sm/t/new-librem-laptop/2823">https://forums.puri.sm/t/new-librem-laptop/2823</a></p> <p><cite>dmidecode</cite> reports correctly:</p> <pre class="literal-block"> $ 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 </pre> </div> </div> <div class="phork-meta"> <a href="https://p.cweiske.de/584/rev-raw/37e5dead6e32708f706f66892e2b3d7f00fe3174/cbmem-wrong-version.rst" style="float: right">view raw source</a> <a href="https://p.cweiske.de/584#cbmem-wrong-version.rst">cbmem-wrong-version.rst</a> </div> </div> <div class="phork-file"> <div class="phork-content"> <div class="document" id="pipe-key"> <h1 class="title">Pipe key</h1> <p>Pipe key did not work on German keyboard after upgrading from Debian 9 stable to unstable.</p> <ul class="simple"> <li><a class="reference external" href="https://forums.puri.sm/t/librem-13v2-german-keyboard-pureos-angle-brackets-pipe-key-dysfunctional/2828">https://forums.puri.sm/t/librem-13v2-german-keyboard-pureos-angle-brackets-pipe-key-dysfunctional/2828</a></li> <li><a class="reference external" href="https://tracker.pureos.net/T486">https://tracker.pureos.net/T486</a></li> </ul> </div> </div> <div class="phork-meta"> <a href="https://p.cweiske.de/584/rev-raw/37e5dead6e32708f706f66892e2b3d7f00fe3174/hardware.rst" style="float: right">view raw source</a> <a href="https://p.cweiske.de/584#hardware.rst">hardware.rst</a> </div> </div> <div class="phork-file"> <div class="phork-content"> <div class="document" id="hidpi"> <h1 class="title">HiDPI</h1> <p><a class="reference external" href="https://forums.puri.sm/t/librem-13-v3-font-size-too-small-or-too-large/3711/3">https://forums.puri.sm/t/librem-13-v3-font-size-too-small-or-too-large/3711/3</a></p> <p>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.</p> <p>Standard PureOS shipped had much too small fonts and icons.</p> <p>xdpyinfo reported 96 dpi resolution, which is really wrong. In reality it's 166 dpi.</p> <p>I told X11 to use the real screen size, and Cinnamon uses this information correctly (KDE, Gnome, Mate, XFCE not):</p> <pre class="literal-block"> $ 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 </pre> <p>I also had to set "Font scaling factor" in the cinnamon font settings to 1.3</p> <div class="section" id="mate-desktop"> <h1>Mate desktop</h1> <p>Settings > Appearance > Fonts > Details > DPI: 125</p> <p>On 166 (automatic) the fonts were too large.</p> </div> <div class="section" id="qt"> <h1>Qt</h1> <ul class="simple"> <li><a class="reference external" href="http://doc.qt.io/qt-5/highdpi.html">http://doc.qt.io/qt-5/highdpi.html</a></li> </ul> <blockquote> 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.</blockquote> <p>Setting the DPI value manually to a lower values gives better font sizes:</p> <pre class="literal-block"> $ QT_FONT_DPI=128 zeal </pre> <p>Maybe the main issue is that Cinnamon pushes the configured font sizes (for Gtk) 1:1 to Qt, probably via the <tt class="docutils literal">QT_QPA_PLATFORMTHEME</tt> variable.</p> </div> <div class="section" id="ding-tk"> <h1>Ding / Tk</h1> <p>Edit ding executable, add:</p> <pre class="literal-block"> tk scaling 2.0 </pre> <ul class="simple"> <li><a class="reference external" href="https://stackoverflow.com/a/34133102/282601">https://stackoverflow.com/a/34133102/282601</a></li> <li><a class="reference external" href="https://www.tcl.tk/man/tcl8.6/TkCmd/tk.htm#M10">https://www.tcl.tk/man/tcl8.6/TkCmd/tk.htm#M10</a></li> </ul> </div> </div> </div> <div class="phork-meta"> <a href="https://p.cweiske.de/584/rev-raw/37e5dead6e32708f706f66892e2b3d7f00fe3174/hidpi.rst" style="float: right">view raw source</a> <a href="https://p.cweiske.de/584#hidpi.rst">hidpi.rst</a> </div> </div> <div class="phork-file"> <div class="phork-content"> <div class="document" id="fan-at-full-speed-after-resume"> <h1 class="title">Fan at full speed after resume</h1> <p>At first I thought it was again Cinnamon that took all the CPU, but it was a firmware problem.</p> <p>Wrong: I needed a new coreboot version to fix this.</p> <p>The problem still happens after upgrading the firmware to <tt class="docutils literal"><span class="pre">coreboot-4.8.1-7-g30300027ce-4.8.1-Purism-3</span></tt>.</p> <p>Instructions:</p> <ul class="simple"> <li><a class="reference external" href="https://puri.sm/coreboot/">https://puri.sm/coreboot/</a></li> <li><a class="reference external" href="https://forums.puri.sm/t/building-coreboot-from-source-official-script/1264">https://forums.puri.sm/t/building-coreboot-from-source-official-script/1264</a></li> <li><a class="reference external" href="https://forums.puri.sm/t/fan-full-blast-after-sleep-coreboot-and-intel-me/3396">https://forums.puri.sm/t/fan-full-blast-after-sleep-coreboot-and-intel-me/3396</a></li> <li><a class="reference external" href="https://forums.puri.sm/t/cpu-fan-stuck-at-high-speed-sometimes/2641">https://forums.puri.sm/t/cpu-fan-stuck-at-high-speed-sometimes/2641</a></li> </ul> </div> </div> <div class="phork-meta"> <a href="https://p.cweiske.de/584/rev-raw/37e5dead6e32708f706f66892e2b3d7f00fe3174/suspend-resume-fan.rst" style="float: right">view raw source</a> <a href="https://p.cweiske.de/584#suspend-resume-fan.rst">suspend-resume-fan.rst</a> </div> </div> </div>