The big one

[crawfxrd]

• Rebase coreboot on the 4.15 release
• Rebase edk2 on the edk2-stable202108 release
• Update Rust toolchain to nightly-2021-06-15

Relevant issues

This change has the potential to affect most reported issues.

Resolves:

• Cannot install ESXi #191
• Provide install-time option to disable the ME #197
• How to Build / Flash the Lemp10 Bios without Intel ME? Lemp10 (Lemur Pro 10) and galp5 (Galago Pro 5) #219
• TGL: Thunderbolt does not work on kernel 5.13 #235
• lemp10: system occasionally resets efi boot options with no user intervention #238
• galp5 - 2021-09-20 FW build - boot entries disappearing. #246
• CONFIG_TPM_MEASURED_BOOT? coreboot#77
• flashing to darp5 breaks "7" key ec#138

May address:

• Variety of issues with bootable USB devices #23
• After upgrade from 19.04->19.10: 5 boot options labeled 19.10. #33
• System ocassionally hangs at BIOS splash screen #38
• After declining firmware update in firmware updater, rebooting takes over 70 seconds #41
• With AC power loss, rebooting system turns off #44
• Issues with multiple OS installs from USB #50
• First suspend after 18.04 install usually fails #56
• Darp5: Return of the 90 second resume delays #61
• Laptop not shutting down after a firmware update #71
• galp4: Sometimes fails to power off  #80
• galp4: USB-c storage device not recognized after suspend #83
• darp6: long boot time after certain sequences of boots/power-offs #117
• gaze15 keyboard input and battery monitor issue on firmware 2021-03-19_af2fbdf #183
• Fails to boot with USB keyboard/mouse plugged in. #230

Unblocks:

• Secure Boot support? #111
• Test fwupd Capsule On Disk support #225
• UEFI menu timeout is not respected #227

Introduces:

• edk2 exception when booting signed binary

TODO

• Update Rust components to work with the new toolchain
  • modeltool
  • ec
    • ectool
    • ecflash
    • ecsim
    • ecspy
  • firmware-setup
    • Serial only used for debug feature: Hide warnings behind the cfg?
  • firmware-smmstore
  • firmware-update
  • gop-policy
  • intel-spi
  • intelflash
  • orbclient: update no_std support?
  • orbfont: update no_std support?
• Remove libs/smmstore and replace it with apps/firmware-smmstore/examples/read in scripts/smmstore.sh
• Fix NVIDIA GPU resource allocation in coreboot / skip aperture checks in edk2
• Fix running firmware-setup in edk2
• Add SMMSTOREv2 commands to firmware-smmstore
• Update firmware-update to migrate SMMSTOREv1 data to SMMSTOREv2 data
• Write the changelog entry
• Basic documentation
  • CMOS option for IME
  • Secure Boot status
• Update Jenkins
  • Update Rust/install new toolchain to fix build
  • Remove edk2 build cache before building all models
  • Use new coreboot GCC toolchain: 8.3 -> 11.2 (very last thing, since current coreboot branch fails to build with 11.2)

[crawfxrd]

It seems edk2 fails if the build cache is present and file paths change in the INFs. We should have Jenkins delete Build/ once before attempting to build all the models.

[crawfxrd]

Updated the coreboot submodules to use absolute paths. Fresh checkouts will work now.

[jacobgkau]

78c1dfd builds and flashes on oryp8. Approving so we can merge this; full regression testing will be done on each model before the updates are released through the firmware updater.

[ZeddieXX]

Does this mean everything is fixed now? Can I update my firmware through the normal way it do I still need to clone this and compile?

If I still need to compile, what are the steps to clone, compile, and flash? Again I'm not a dev so I'll need step by step instructions.

Thanks!

[nkalkhof]

S76 support told me that there is no ETA for this new coreboot release so I compiled and flashed coreboot from system76 main branch approx two weeks ago on my lemp10 omitting the EC since I have an altered fan table. Had to unplug my CMOS battery to clear after flashing. After that everything seems to work including TBT4 and IME toggle.
Howevwer if you follow the latest issues it becomes clear that there the current codebase is still a litte rough around the edges. So if you are not in a hurry I'd recommend to wait. If you cannot wait there is a pretty straight forward documentation on how to proceed https://github.com/system76/firmware-open.

[ZeddieXX]

Thanks. Is there a list of issues left? I want to see if it will affect my use case before I compile and flash. Right now I haven't really been able to use my GALP5 because of the current issues of the boot entries being deleted every cold boot. I just left it on and using it as a "server". I would love to use it as a laptop again.

So wondering if the rough edges are still better than what I have now.

Thanks.

[jacobgkau]

@ZeddieXX The list of known issues would be the repo's issue list: https://github.com/system76/firmware-open/issues

There may be further issues that are yet unknown, which is why the update hasn't been pushed out to all models yet.

We are very close to releasing the update on lemp10-- #269 was a last-minute showstopper. oryp8 is having some NVIDIA-related issues, and while galp5 NVIDIA doesn't appear to be affected, I'm not sure if the changes to oryp8 will result in changes to galp5 as well.

If you don't want to wait for the update to be tested and released, you are welcome to just flash and try it yourself. If you want other people to try it for you first, then you'll have to wait for that to happen. The commands to build and flash are the same ones I provided earlier in this PR:

git clone https://github.com/system76/firmware-open
cd firmware-open
./scripts/update.sh
./scripts/deps.sh
./scripts/build.sh galp5
./scripts/flash.sh galp5

The only difference is not checking out any branch since this branch has now been merged.

[ethuleau]

Hi @nkalkhof, why and how did you altered your lemp10 fan table? Did you do that to be smoother?

[nkalkhof]

Hi @nkalkhof, why and how did you altered your lemp10 fan table? Did you do that to be smoother?

The fan curve is badly adjusted on the lemp10 in the 60-70°C range IMHO. I've adjusted the fan curve to let the fan kick in as soon as the package temperature trips 60°C. The fan then runs at very quiet ~2500RPM until the temperature drops below 55°C. This helps to keep the temperatures and the suddenly occuring fan noise in check. I still have some hope that S76 will offer a userspace adjustable option sometime in the future wink.

These are my changes (lemp10):
Add
CFLAGS+=-DBOARD_HEATUP=5 CFLAGS+=-DBOARD_COOLDOWN=20 CFLAGS+=-DBOARD_FAN_POINTS="
FAN_POINT(60, 30),
FAN_POINT(70, 40),
FAN_POINT(75, 50),
FAN_POINT(80, 60),
FAN_POINT(85, 65),
FAN_POINT(90, 65)"

to firmware-open/ec/src/board/system76/lemp10/board.mk and flash EC according to the instructions found in firmware-open git. Do this at your own risk!!!

[ZeddieXX]

When I try to flash, I get this error:
--- stderr
thread 'main' panicked at 'Unable to find hidapi-hidraw: "pkg-config" "--libs" "--cflags" "hidapi-hidraw" did not exit successfully: exit status: 1
--- stderr
Package hidapi-hidraw was not found in the pkg-config search path.
Perhaps you should add the directory containing hidapi-hidraw.pc' to the PKG_CONFIG_PATH environment variable No package 'hidapi-hidraw' found ', /home/zeddie/.cargo/registry/src/github.com-1ecc6299db9ec823/hidapi-1.2.7/build.rs:78:60 note: run with RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: build failed

[crawfxrd]

Run ./ec/scripts/deps.sh to install the missing deps.

[ZeddieXX]

Thanks. but now I'm getting:
zeddie@zedlin-galp5:/temp/firmware-open$ ./scripts/flash.sh galp5
Finished release [optimized] target(s) in 0.00s
SPI HSFSTS_CTL: WRSDIS | FDOPSS | FDV | FLOCKDN
SPI FILE: Loadingthread 'main' panicked at 'called Result::unwrap() on an Err value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/main.rs:68:30
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
zeddie@zedlin-galp5:/temp/firmware-open$

[ZeddieXX]

I'm going to run build.sh again, then try flashing again now that I ran the ./ec/scripts/deps.sh

[ZeddieXX]

That worked! Hopefully the issue with the missing EFI boot entries is fixed. Right now I'm trying out Fedora 35, no other OSes, so I probably wont be able to find out if the issue is fixed until I can shrink the partition and install a dual-boot Windows.

[ZeddieXX]

Hi. I still noticed the newest available firmware is still 2021-07-20_93C2809 for my galp5. When will a new firmware be released into the official update channel?

I just compiled and flashed the current one (2022-07-27_7e4a92c). Is there other bugs that's preventing a new firmware release for the galp5? It's been over a year and the latest available firmware in the official update channel didn't incorporate this merge (The big one).

[crawfxrd]

I am finishing up the Alder Lake boards, then will be making releases for previous generations.

I should be able to start making RCs next week.

[ZeddieXX]

Hi @crawfxrd . Any updates on RCs for GALP5? Still says 2021-07-20_93c2809 is the latest.

The last time I downloaded and compiled, I got the 2022-07-27_7e4a92c and I am still contstantly getting "new firmware update available" notifications even though I have a newer build.

Maybe a good idea to prevent Settings of false new firmware notifications if the built version is newer than what's offered in RC.

[jacobgkau]

I am still contstantly getting "new firmware update available" notifications even though I have a newer build.

You can disable those multiple ways!

Option 1: open Startup Apps and un-check Firmware Manager Check. This will not prevent Settings from working, but would need to be done on every user account individually.

Option 2: disable & stop system76-firmware-daemon.service. This will prevent Settings from manually checking for updates, but it will take effect for all users at once. You'll need to enable/start it again next time you want to check for updates.

sudo systemctl disable --now system76-firmware-daemon.service
sudo systemctl enable --now system76-firmware-daemon.service

(Tim can chime in on where we're at with a new release, but just going off of my knowledge, he's fixed some of the USB-C suspend issues, but some Thunderbolt suspend issues remain and have potentially gotten worse by being more exposed. There are also SSD issues he was working on fixing for lemp10 & darp7, although galp5 may have been less affected by those since it only has one SSD slot and no SATA support.)

Maybe a good idea to prevent Settings of false new firmware notifications if the built version is newer than what's offered in RC.

The one corner case this raises off the top of my head would be no longer allowing rollbacks (which we have had to do because of some of the issues that have prevented releases for a while). If a version is pulled, users who have already upgraded would not be prompted to downgrade, so rolling back would require adding a new version to the changelog just for the rollback (which I can see an argument for doing.) It would allow people who like to customize their fan curves, etc. to still receive update notifications, which would be nice. And it shouldn't be too difficult considering our versioning scheme.

[ZeddieXX]

Thanks for the update. I disabled in the Startup App since I'm the only user. Since it's been yet another month, any updates on an official release for the galp5 yet?

I'm currently on 2022-07-27_7e4a92c (I compiled and flashed myself). Anything I need to look out for if I compile and flash from the current main branch?

Thanks. Also looking forward to your Rust-based Cosmic DE. :)