system76 / coreboot Goto Github PK

Currently, some hotkeys are done in hardware.

The touchpad lock provides no visual notification of being activated, unlike the one we have from the WMI driver.

The keyboard brightness has no visual notification, and cannot be changed using software. On the darp5, the color of the keyboard is hardcoded and defaults to blue.

The airplane mode toggle has no visual notification, sometimes comes on at unexpected times, and it cannot be turned off using the toggle in the operating system. Only the airplane mode hotkey can turn it off.

The following needs to be done:

• Switch EC to use software hotkeys
• Release packages to support software airplane mode toggle
• Update kernel with driver to support touchpad lock, keyboard brightness, and airplane mode LED
• Potentially add support for software fan control

Lots of good stuff in there for other systems.

Having the ability to set charge limit at 80 % and to start back up at 40 % or any other range would help improve battery life.

Flash Coreboot with UEFI on the following machines:

• Carl - galp2
• Emma - galp2
• Harris - galp2
• May - galp2
• Katie - galp3
• Louisa - galp3-b
• Aaron - galp3-b
• Alex - galp3-b
• Ben C. - galp3-b
• Joshua - galp3-c (13 inch)
• Jeremy - galp3-c (14 inch)
• Ben S. - darp5 - after dock testing

Getting this error when running update.sh in firmware-open:

jacob@serw12:~/Work/firmware-open$ ./scripts/update.sh 
Already up to date.
fatal: remote error: want 6c0c4691e5bb446e0e428ebca595164709c59586 not valid
fatal: Fetched in submodule path 'coreboot/3rdparty/intel-microcode', but it did not contain 6c0c4691e5bb446e0e428ebca595164709c59586. Direct fetching of that commit failed.
fatal: 
fatal: Failed to recurse into submodule path 'coreboot'

Happens whether I clone via git:// or https://.

GNOME Settings shows that TBT is either disabled in the BIOS or has the incorrect security level.

Pop 18.10 Intel image
Latest SeaBIOS as of today.

On a HiDPI display like the galp2, the BIOS settings screen does not fill the entire screen, making reading the menu options difficult to read (really small).

Hi System76!

I'm following coreboot source code for a few days. And getting updates more than one time in a day. I wanted to learn how you work, and do you have any other policy about your own hardware.

Thanks, happy hacking!

I was wondering why the lemp9 is current the only device from you which is upstream in the Coreboot Repo

In this Repo and firmware-open Repo

• addw1
• addw2
• bonw14
• darp5
• darp6
• darp7
• galp2
• galp3
• galp3-b
• galp3-c
• galp4
• galp5
• gaze14
• gaze15
• gaze16
• lemp9
• lemp10
• oryp5
• oryp6
• oryp7
• oryp8

Why the are all not upstream in Coreboot? I think it's good that you develop Coreboot for these models, but I don't think it's good that they don't go upstream into Coreboot.

You (and other OEMs) are use Barebones from Clevo.

I have a Gigabyte Aorus Pro X570 WiFi I would like coreboot on, and heard that it was being ported to newer AMD Chipsets, but I don’t see any definitions in the code for anything other than gen 1(Picasso) boards

Booting qubes 4.0.3; xen 4.8.5 as well as qubes 4.1; xen 4.14 on the Clevo L141MU with system76 firmware flashed via the system76-firmware tool results in a xen panic at boot: IO-APIC + timer doesn't work!
See attached picture for detailed error message while run with apic_verbosity=debug

I'm not able to enable the webcam with F10 or the hardware does not see the webcam. It is not listed in 'lsusb'.

aaronhoneycutt@pop-os ~/g/fresh-install-script> lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
aaronhoneycutt@pop-os ~/g/fresh-install-script>

Seems that there isn't a system uuid assigned by coreboot or by system76's build of it: or just specifically for oryp7?

07/20/2021 4.13 coreboot 2021-07-20_93c2809

From dmidecode:

Handle 0x0001, DMI type 1, 27 bytes
System Information
	Manufacturer: System76
	Product Name: Oryx Pro
	Version: oryp7
	Serial Number: 123456789
	UUID: Not Settable
	Wake-up Type: Reserved
	SKU Number: Not Specified
	Family: Not Specified

From working install of same Popos release:

Handle 0x0001, DMI type 1, 27 bytes
System Information
	Manufacturer: Dell Inc.
	Product Name: OptiPlex 9020M
	Version: 00
	Serial Number: ZZZZZZ
	UUID: 4c4c4544-AAAA-ZZZZ-XXXX-b3c04f323832
	Wake-up Type: Power Switch
	SKU Number: 0669
	Family: Not Specified

Removed identifiers....

This might or might not be a related issue:

acidanthera/bugtracker#711

OS:

# pop-upgrade release check
checking if pop-upgrade requires an update
      Current Release: 21.10
         Next Release: 22.04
New Release Available: false

Hello there, was wondering if testing was done for measured boot on coreboot 4.14+?