Coreboot 4.12-Purism-4, Pureboot Release 15 updates now available

Firmware Coreboot
1

PureBoot Release 15

  • Rebased on HEADS upstream master branch (89c45770)
  • Updated PureBoot kernel to 5.4.69 for all Librem devices
  • Added board name, kernel version to System Info screen
  • Improved handling of empty disks, or running without a fixed internal disk
  • Improved readability of filenames in GUI notifications
  • Updated gpg2 toolstack to v2.2.21
  • Updated flashrom to support Cometlake boards
  • Scaled screen resolution on Librem 15v4 to 1080p to improve text/UI readability
  • Added support for Librem Mini v2
  • Added support for Librem Server L1UM

coreboot 4.12-Purism-4

  • Synchronized Librem Mini with upstream coreboot
    • Updated PL1/long turbo boost power from 15W to 25W
    • Updated PL2/short turbo boost power from 25W to 51W
    • Adjusted SATA tuning parameters for 2.5" drive
    • Adjusted GPIO config for better stability and power usage
  • Updated CPU microcode for all Librem boards
  • Backported a patch for better memory alignment
  • Added support for Librem Mini v2

Update via Purism’s coreboot Utility Script:

4 Likes
2

thanks!

Installed on Librem-Mini v1.

So far 4k display issues are fixed.

I am testing the re-enable of SATA3 on that 2.5’ ssd.

3

No the issue for SATA is still there

[Wed Nov 11 17:41:03 2020] ata1.00: exception Emask 0x10 SAct 0xff00 SErr 0x440100 action 0x6 frozen
[Wed Nov 11 17:41:03 2020] ata1.00: irq_stat 0x08000000, interface fatal error
[Wed Nov 11 17:41:03 2020] ata1: SError: { UnrecovData CommWake Handshk }
[Wed Nov 11 17:41:03 2020] ata1.00: failed command: WRITE FPDMA QUEUED
[Wed Nov 11 17:41:03 2020] ata1.00: cmd 61/40:40:31:41:b8/05:00:20:00:00/40 tag 8 ncq dma 688128 out
                                res 40/00:40:31:41:b8/00:00:20:00:00/40 Emask 0x10 (ATA bus error)
[Wed Nov 11 17:41:03 2020] ata1.00: status: { DRDY }
[Wed Nov 11 17:41:03 2020] ata1.00: failed command: WRITE FPDMA QUEUED
[Wed Nov 11 17:41:03 2020] ata1.00: cmd 61/10:48:21:1c:a8/00:00:20:00:00/40 tag 9 ncq dma 8192 out
                                res 40/00:40:31:41:b8/00:00:20:00:00/40 Emask 0x10 (ATA bus error)
[Wed Nov 11 17:41:03 2020] ata1.00: status: { DRDY }
[Wed Nov 11 17:41:03 2020] ata1.00: failed command: WRITE FPDMA QUEUED
[Wed Nov 11 17:41:03 2020] ata1.00: cmd 61/50:50:71:59:a8/00:00:20:00:00/40 tag 10 ncq dma 40960 out
                                res 40/00:40:31:41:b8/00:00:20:00:00/40 Emask 0x10 (ATA bus error)
[Wed Nov 11 17:41:03 2020] ata1.00: status: { DRDY }
[Wed Nov 11 17:41:03 2020] ata1.00: failed command: WRITE FPDMA QUEUED
[Wed Nov 11 17:41:03 2020] ata1.00: cmd 61/c0:58:71:46:b8/02:00:20:00:00/40 tag 11 ncq dma 360448 out
                                res 40/00:40:31:41:b8/00:00:20:00:00/40 Emask 0x10 (ATA bus error)
[Wed Nov 11 17:41:03 2020] ata1.00: status: { DRDY }
[Wed Nov 11 17:41:03 2020] ata1.00: failed command: WRITE FPDMA QUEUED
[Wed Nov 11 17:41:03 2020] ata1.00: cmd 61/38:60:31:49:b8/03:00:20:00:00/40 tag 12 ncq dma 421888 out
                                res 40/00:40:31:41:b8/00:00:20:00:00/40 Emask 0x10 (ATA bus error)
[Wed Nov 11 17:41:03 2020] ata1.00: status: { DRDY }
[Wed Nov 11 17:41:03 2020] ata1.00: failed command: WRITE FPDMA QUEUED
[Wed Nov 11 17:41:03 2020] ata1.00: cmd 61/80:68:f1:68:a8/00:00:20:00:00/40 tag 13 ncq dma 65536 out
                                res 40/00:40:31:41:b8/00:00:20:00:00/40 Emask 0x10 (ATA bus error)
[Wed Nov 11 17:41:03 2020] ata1.00: status: { DRDY }
[Wed Nov 11 17:41:03 2020] ata1.00: failed command: WRITE FPDMA QUEUED
[Wed Nov 11 17:41:03 2020] ata1.00: cmd 61/10:70:a1:69:a8/00:00:20:00:00/40 tag 14 ncq dma 8192 out
                                res 40/00:40:31:41:b8/00:00:20:00:00/40 Emask 0x10 (ATA bus error)
[Wed Nov 11 17:41:03 2020] ata1.00: status: { DRDY }
[Wed Nov 11 17:41:03 2020] ata1.00: failed command: WRITE FPDMA QUEUED
[Wed Nov 11 17:41:03 2020] ata1.00: cmd 61/08:78:49:a8:a8/00:00:20:00:00/40 tag 15 ncq dma 4096 out
                                res 40/00:40:31:41:b8/00:00:20:00:00/40 Emask 0x10 (ATA bus error)
[Wed Nov 11 17:41:03 2020] ata1.00: status: { DRDY }
[Wed Nov 11 17:41:03 2020] ata1: hard resetting link
[Wed Nov 11 17:41:03 2020] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
4

this is running PureOS 9?

Likely a kernel issue, and updating to PureOS 10 (or even just a 5.x kernel) would resolve it

5

I am on PureOS byzantium

uname -a
Linux compu2 5.9.0-1-amd64 #1 SMP Debian 5.9.1-1 (2020-10-17) x86_64 GNU/Linux

cat /etc/os-release 

ID=pureos
NAME=PureOS
PRETTY_NAME=PureOS

VERSION_ID=10.0
VERSION_CODENAME=byzantium

HOME_URL="https://pureos.net/"
SUPPORT_URL="https://puri.sm/faq/#faq-WherecanIfindoutmoreaboutPureOS"
BUG_REPORT_URL="https://tracker.pureos.net/"

LOGO=pureos-logo-icon

Also the system never wakes up, eventually the screen goes blank when I am AFK, and I am never able to wake up the system even if the power light is on.

I have to hard power off the system.

I reverted to the bios that works ok for me coreboot-librem_mini-4.12-Purism-3-1-DP_test.rom

I updated the issue -> https://source.puri.sm/coreboot/coreboot/-/issues/12

6

So far 4k display issues are fixed.

What is this issue?

7

On Librem-Mini :

  1. The boot options were not displayed
  2. Once booted up, the resolution and zoom settings were reset to 100% ( on a UHD monitor I use 200%)
  3. The user interface was laggy, mouse lag when moving feeling like 1996 again on kde 1 with 486 sx16.

Those issues were fixed for my Librem-Mini on 4k screen using display-port.

2 Likes
8

issue was with 4K displays attached to the DisplayPort output only

1 Like
9

this is very odd, if the system isn’t suspended (sleep/S3, flashing LED) then it’s just the display being powered down by the OS, and it should power back on without any firmware intervention

10

thanks for the update and keeping us posted here on the Purism-forums !

i’ll report back with my experience soon enough …

11

yep, and I dont have this issue with the custom firmware that I am running.

coreboot-librem_mini-4.12-Purism-3-1-DP_test.rom

I reverted to this one, for me it’s almost ok, only missing the SATA link speed set to 6G

12

please open an issue here: https://source.puri.sm/coreboot/coreboot/-/issues

13

Already done since a few versions now :slight_smile:

14

I meant for the screen blanking issue in 4.12-Purism-4

15

silly me :wink:

16

Trying to use the precompiled images I get the following error:

Error downloading file pureboot-librem13v4-Release-15.rom.gz

Is this intentional and I have to build from source?

17

I filed an issue in the Coreboot utility project here: https://source.puri.sm/coreboot/utility/-/issues/7

The pre-compiled image has an underscore between “librem” and the model number in this release.

For now, you can manually edit the script on line 64 (https://source.puri.sm/coreboot/utility/-/blob/master/coreboot_util.sh#L64) so that the line reads the following:

COREBOOT_HEADS_IMAGE_13v4="pureboot-librem_13v4-${PUREBOOT_VERSION}.rom"
2 Likes
18

thanks, fixed

19

And all working, thanks @MrChromebox

20

;; pureos9-gdisk-benchmark
;; WD-red-NAS-500GB SATA3 m2-internal-SSD(80mm)
;;
;; sudo dmidecode
;;
;; # dmidecode 3.2
;; Getting SMBIOS data from sysfs.
;; SMBIOS 2.8 present.
;; 18 structures occupying 817 bytes.
;; Table at 0x89C22020.
;;
;; Handle 0x0000, DMI type 0, 26 bytes
;; BIOS Information
;; Vendor: coreboot
;; Version: 4.12-Purism-4
;; Release Date: 11/06/2020
;; 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.12
;; Firmware Revision: 0.0
;;
;; disk temp @
;; erasing 32GB-ext4-bench-partition4 reached 64 degree celsius @ 26.5 ambient temp
;;
;; disk temp @
;; performing benchmark reached 64 degree celsius @ 26.5 ambient temp
;;
;; disk temp @
;; idle after benchmark complete is 46 degree celsius @ 26.5 ambient temp

this is for the Librem-Mini-v1 with PureOS-9-Amber(Stable) for the time being. will update for Byzantium if any worthwhile differences occur. we need an integrated benchmarking-tool for stuff like this :wink:

pureos9-gdisks-bench-wd-ssd-1
pureos9-gdisks-bench-wd-ssd-1738Ă—580 120 KB

pureos9-gdisks-bench-wd-ssd-2
pureos9-gdisks-bench-wd-ssd-2741Ă—582 148 KB
pureos9-gdisks-bench-wd-ssd-4
pureos9-gdisks-bench-wd-ssd-4740Ă—580 126 KB
pureos9-gdisks-bench-wd-ssd-8
pureos9-gdisks-bench-wd-ssd-8743Ă—580 175 KB
pureos9-gdisks-bench-wd-ssd-16
pureos9-gdisks-bench-wd-ssd-16738Ă—582 122 KB
pureos9-gdisks-bench-wd-ssd-32
pureos9-gdisks-bench-wd-ssd-32743Ă—584 188 KB
pureos9-gdisks-bench-wd-ssd-64
pureos9-gdisks-bench-wd-ssd-64740Ă—582 144 KB
pureos9-gdisks-bench-wd-ssd-128
pureos9-gdisks-bench-wd-ssd-128741Ă—582 158 KB
pureos9-gdisks-bench-wd-ssd-256
pureos9-gdisks-bench-wd-ssd-256739Ă—580 140 KB
pureos9-gdisks-bench-wd-ssd-512
pureos9-gdisks-bench-wd-ssd-512740Ă—580 78.9 KB
pureos9-gdisks-bench-wd-ssd-1000
pureos9-gdisks-bench-wd-ssd-1000740Ă—576 120 KB

1 Like