{"type":"rich","version":"1.0","provider_name":"phorkie","provider_url":"https:\/\/p.cweiske.de\/","title":"puri.sm librem 13 v3","author_name":"Christian Weiske","cache_age":86400,"width":900,"height":900,"html":"<!-- embedding all files of https:\/\/p.cweiske.de\/584 -->\n<link rel=\"stylesheet\" href=\"https:\/\/p.cweiske.de\/css\/embed.css\"\/>\n<div class=\"phork\" id=\"584\">\n    <div class=\"phork-file\">\n <div class=\"phork-content\">\n  \n<div class=\"document\" id=\"wrong-hardware-revision-reported\">\n<h1 class=\"title\">Wrong Hardware revision reported<\/h1>\n\n<p>I have a Librem 13 v3, but it it reported as v2:<\/p>\n<pre class=\"literal-block\">\n$ sudo .\/cbmem -c | egrep -i &quot;coreboot-|purism|librem&quot;\ncoreboot-4.8.1-7-g30300027ce-4.8.1-Purism-3 Wed Aug 15 04:00:19 UTC 2018 bootblock starting...\ncoreboot-4.8.1-7-g30300027ce-4.8.1-Purism-3 Wed Aug 15 04:00:19 UTC 2018 romstage starting...\ncoreboot-4.8.1-7-g30300027ce-4.8.1-Purism-3 Wed Aug 15 04:00:19 UTC 2018 postcar starting...\ncoreboot-4.8.1-7-g30300027ce-4.8.1-Purism-3 Wed Aug 15 04:00:19 UTC 2018 ramstage starting...\nRoot Device (Purism Librem 13 v2)\nFound mainboard Purism Librem 13 v2\n<\/pre>\n<p>This seems to be a hardware error; Purism failed to change their revision number:<\/p>\n<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>\n<p><cite>dmidecode<\/cite> reports correctly:<\/p>\n<pre class=\"literal-block\">\n$ sudo dmidecode\n# dmidecode 3.1\nGetting SMBIOS data from sysfs.\nSMBIOS 2.7 present.\n8 structures occupying 428 bytes.\nTable at 0x7AA9A020.\n\nHandle 0x0000, DMI type 0, 24 bytes\nBIOS Information\n        Vendor: coreboot\n        Version: 4.8.1-Purism-3\n        Release Date: 08\/15\/2018\n        ROM Size: 16 MB\n        Characteristics:\n                PCI is supported\n                PC Card (PCMCIA) is supported\n                BIOS is upgradeable\n                Selectable boot is supported\n                ACPI is supported\n                Targeted content distribution is supported\n        BIOS Revision: 4.0\n        Firmware Revision: 0.0\n\nHandle 0x0001, DMI type 1, 27 bytes\nSystem Information\n        Manufacturer: Purism\n        Product Name: Librem 13 v3\n        Version: 3.0\n        Serial Number: 317739\n        UUID: Not Settable\n        Wake-up Type: Reserved\n        SKU Number: Not Specified\n        Family: Librem 13\n\nHandle 0x0002, DMI type 2, 14 bytes\nBase Board Information\n        Manufacturer: Purism\n        Product Name: Librem 13 v3\n        Version: 3.0\n        Serial Number: 317739\n        Asset Tag: Not Specified\n        Features: None\n        Location In Chassis: Not Specified\n        Chassis Handle: 0x0003\n        Type: Unknown\n<\/pre>\n<\/div>\n\n <\/div>\n <div class=\"phork-meta\">\n  <a href=\"https:\/\/p.cweiske.de\/584\/rev-raw\/37e5dead6e32708f706f66892e2b3d7f00fe3174\/cbmem-wrong-version.rst\" style=\"float: right\">view raw source<\/a>\n  <a href=\"https:\/\/p.cweiske.de\/584#cbmem-wrong-version.rst\">cbmem-wrong-version.rst<\/a>\n <\/div>\n<\/div>\n    <div class=\"phork-file\">\n <div class=\"phork-content\">\n  \n<div class=\"document\" id=\"pipe-key\">\n<h1 class=\"title\">Pipe key<\/h1>\n\n<p>Pipe key did not work on German keyboard after upgrading from Debian 9 stable to unstable.<\/p>\n<ul class=\"simple\">\n<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>\n<li><a class=\"reference external\" href=\"https:\/\/tracker.pureos.net\/T486\">https:\/\/tracker.pureos.net\/T486<\/a><\/li>\n<\/ul>\n<\/div>\n\n <\/div>\n <div class=\"phork-meta\">\n  <a href=\"https:\/\/p.cweiske.de\/584\/rev-raw\/37e5dead6e32708f706f66892e2b3d7f00fe3174\/hardware.rst\" style=\"float: right\">view raw source<\/a>\n  <a href=\"https:\/\/p.cweiske.de\/584#hardware.rst\">hardware.rst<\/a>\n <\/div>\n<\/div>\n    <div class=\"phork-file\">\n <div class=\"phork-content\">\n  \n<div class=\"document\" id=\"hidpi\">\n<h1 class=\"title\">HiDPI<\/h1>\n\n<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>\n<p>The librem 13 v3 has 1920x1080 px resolution, on 13&quot;. -This is &quot;hidpi&quot;.- actually, it's mdpi, because it's not double the &quot;normal&quot; resolution but only 1.6x.<\/p>\n<p>Standard PureOS shipped had much too small fonts and icons.<\/p>\n<p>xdpyinfo reported 96 dpi resolution, which is really wrong. In reality it's 166 dpi.<\/p>\n<p>I told X11 to use the real screen size, and Cinnamon uses this information correctly (KDE, Gnome, Mate, XFCE not):<\/p>\n<pre class=\"literal-block\">\n$ cat \/etc\/X11\/xorg.conf.d\/90-librem-display.conf\n# xdpyinfo | grep -B2 resolution\n# https:\/\/wiki.archlinux.org\/index.php\/xorg#Display_size_and_DPI\nSection &quot;Monitor&quot;\n    Identifier   &quot;eDP-1&quot;\n    DisplaySize  294 166 # In millimeters\nEndSection\n<\/pre>\n<p>I also had to set &quot;Font scaling factor&quot; in the cinnamon font settings to 1.3<\/p>\n<div class=\"section\" id=\"mate-desktop\">\n<h1>Mate desktop<\/h1>\n<p>Settings &gt; Appearance &gt; Fonts &gt; Details &gt; DPI: 125<\/p>\n<p>On 166 (automatic) the fonts were too large.<\/p>\n<\/div>\n<div class=\"section\" id=\"qt\">\n<h1>Qt<\/h1>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"http:\/\/doc.qt.io\/qt-5\/highdpi.html\">http:\/\/doc.qt.io\/qt-5\/highdpi.html<\/a><\/li>\n<\/ul>\n<blockquote>\nThe 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>\n<p>Setting the DPI value manually to a lower values gives better font sizes:<\/p>\n<pre class=\"literal-block\">\n$ QT_FONT_DPI=128 zeal\n<\/pre>\n<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>\n<\/div>\n<div class=\"section\" id=\"ding-tk\">\n<h1>Ding \/ Tk<\/h1>\n<p>Edit ding executable, add:<\/p>\n<pre class=\"literal-block\">\ntk scaling 2.0\n<\/pre>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/stackoverflow.com\/a\/34133102\/282601\">https:\/\/stackoverflow.com\/a\/34133102\/282601<\/a><\/li>\n<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>\n<\/ul>\n<\/div>\n<\/div>\n\n <\/div>\n <div class=\"phork-meta\">\n  <a href=\"https:\/\/p.cweiske.de\/584\/rev-raw\/37e5dead6e32708f706f66892e2b3d7f00fe3174\/hidpi.rst\" style=\"float: right\">view raw source<\/a>\n  <a href=\"https:\/\/p.cweiske.de\/584#hidpi.rst\">hidpi.rst<\/a>\n <\/div>\n<\/div>\n    <div class=\"phork-file\">\n <div class=\"phork-content\">\n  \n<div class=\"document\" id=\"fan-at-full-speed-after-resume\">\n<h1 class=\"title\">Fan at full speed after resume<\/h1>\n\n<p>At first I thought it was again Cinnamon that took all the CPU, but it was a firmware problem.<\/p>\n<p>Wrong: I needed a new coreboot version to fix this.<\/p>\n<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>\n<p>Instructions:<\/p>\n<ul class=\"simple\">\n<li><a class=\"reference external\" href=\"https:\/\/puri.sm\/coreboot\/\">https:\/\/puri.sm\/coreboot\/<\/a><\/li>\n<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>\n<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>\n<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>\n<\/ul>\n<\/div>\n\n <\/div>\n <div class=\"phork-meta\">\n  <a href=\"https:\/\/p.cweiske.de\/584\/rev-raw\/37e5dead6e32708f706f66892e2b3d7f00fe3174\/suspend-resume-fan.rst\" style=\"float: right\">view raw source<\/a>\n  <a href=\"https:\/\/p.cweiske.de\/584#suspend-resume-fan.rst\">suspend-resume-fan.rst<\/a>\n <\/div>\n<\/div>\n<\/div>\n"}