Determine how to disable the Intel M.E. with the latest 14.x.x.x version.

With firmware 2019-10-03_01c09f0, the BIOS menu hangs when trying to select either the One Time Boot or Change Boot Order option. A hard poweroff is required to get out of this frozen state.

Since updated firmware was installed on the Darter yesterday afternoon, before booting the OS, a message is shown, Boot Failed. EFI USB Device.

There was discussion when seeing fwupd devices that had a newer version of firmware than was on fw-upd, that the user should not be notified of this "newer" firmware as it probably is not newer -firmware but just a lack updating fwupd.

I am wondering if we want to do the same thing with this firmware as the version includes the date. Potentially a version with a newer date should not notify that a firmware of an earlier date is a newer version.

Example:

Have
2019-10-23... installed and firmware-manager notifies that 2019-10-08... is the latest version.

I was testing dual boot on a Galago. I first started by flashing the latest firmware (as of October 22nd) then flashing Pop 19.10. I then installed Ubuntu 18.04 on the second drive in the machine, then clean installed Pop 19.10 back over the same drive it was initially imaged onto. After this, I tried reinstalling Ubuntu 18.04, but the installer kept failing on both drives. I then reinstalled the same firmware version and tried Pop 19.10 and 18.04 several times each, from different USB drives, installing to both internal drives, and the installer would fail every time.

At one point, I was trying to boot to one of our M.2 enclosures with 19.10 on it, and the BIOS menu broke completely, and it is stuck in that state. The machine now boots directly into BIOS without showing the splash screen. Selecting "Boot Default" does nothing, and no boot options are shown in "One Time Boot" or "Change Boot Order". I will leave the machine as-is for further investigation.

When the Thunderbolt storage device is recognized in gnome-control-center, the storage should be seen with lsblk or in Disks or under Other Locations in nautilus. This is not the case, there appears no way to access the storage on the disk.

This is not an issue with proprietary firmware on the previous model.

When booting into the firmware updater to update firmware, the user is prompted twice to press Enter.

There should only be one prompt for an Enter

With the system completely off, booting it up and then pressing Esc will launch the systemd-boot menu, not the BIOS Settings.

This does not happen on a reboot.

With AC Power connected, rebooting with a Thunderbolt drive plugged in, the system went into a very odd suspend loop. With nothing on the screen, the indicator lights showed the system on for about 15-30 seconds. Then the system would suspend (power led started blinking). After pressing the power button, the system would once again sit with the display off for about 15-30 seconds before suspending again. I got out of this loop by unplugging power, unplugging the Thunderbolt drive, and holding the power button on the laptop. Once the system was off, I turned it back on and have since been unable to recreate the issue.

In the BIOS menu, holding the down arrow for a while sometimes gets the cursor stuck briefly in a cycle where it scrolls through all menu items. It doesn't happen consistently, but I have seen it several times.

The firmware was flashed on Friday 8/23/19 and build that day as well. The feature doesn't work and neither does the indicator. Running on Pop 19.04 with the latest updates.

system76-packages.txt

dmidecode.txt

After selecting "Change Boot Order" from the main menu, I am taken to a menu with an option called "Change Boot Order", with two other options "Commit Changes and Exit" and "Discard Changes and Exit". To change or view the boot order, I have to hit Enter again, rearrange the boot items, hit Enter once more, then select "Commit Changes and Exit". This menu in between the main menu and the boot order list feels like an unnecessary extra step since I cannot actually change the boot order without going one level deeper into the menu.

On the Galago with a 2.5" drive and an M.2 SATA drive, when I go to the One Time Boot menu, I see two options: "EFI Hard Drive" and "EFI Hard Drive 1". Would it be better to number them 1 and 2 instead?

I'm getting an error while doing 'cargo install cargo-xbuild' when it tries to compile serde.

There are a sequence of errors similar to this one below. Ideas?

error[E0412]: cannot find type NonZeroI8 in module num

System is: Ubuntu 18.04 64bit

brian@ubu18:~/system76$ rustc --version
rustc 1.35.0-nightly (9d71ec135 2019-03-10)

Log:
brian@ubu18:~/system76$ cargo install cargo-xbuild
Updating crates.io index
Downloaded cargo-xbuild v0.5.15
Downloaded 1 crates (24.9 KB) in 1.69s
Installing cargo-xbuild v0.5.15
Downloaded cargo_metadata v0.5.8
Downloaded fs2 v0.4.3
Downloaded error-chain v0.7.2
Downloaded serde_derive v1.0.99
Downloaded tempdir v0.3.7
Downloaded libc v0.2.62
Downloaded serde v1.0.99
Downloaded rustc_version v0.1.7
Downloaded toml v0.2.1
Downloaded serde_json v1.0.40
Downloaded semver v0.9.0
Downloaded rand v0.4.6
Downloaded proc-macro2 v1.0.3
Downloaded walkdir v1.0.7
Downloaded remove_dir_all v0.5.2
Downloaded quote v1.0.2
Downloaded unicode-xid v0.2.0
Downloaded error-chain v0.11.0
Downloaded ryu v1.0.0
Downloaded syn v1.0.5
Downloaded semver-parser v0.7.0
Downloaded itoa v0.4.4
Downloaded rustc-serialize v0.3.24
Downloaded same-file v0.1.3
Downloaded semver v0.1.20
Compiling proc-macro2 v1.0.3
Compiling unicode-xid v0.2.0
Compiling syn v1.0.5
Compiling ryu v1.0.0
Compiling libc v0.2.62
Compiling serde v1.0.99
Compiling semver-parser v0.7.0
Compiling itoa v0.4.4
Compiling semver v0.1.20
Compiling error-chain v0.11.0
Compiling cargo-xbuild v0.5.15
Compiling remove_dir_all v0.5.2
Compiling rustc-serialize v0.3.24
Compiling same-file v0.1.3
Compiling error-chain v0.7.2
Compiling rustc_version v0.1.7
Compiling walkdir v1.0.7
error[E0412]: cannot find type NonZeroI8 in module num
--> /home/brian/.cargo/registry/src/github.com-1ecc6299db9ec823/serde-1.0.99/src/de/impls.rs:2416:5
|
2416 | NonZeroI8,
| ^^^^^^^^^ help: a struct with a similar name exists: NonZeroU8

error[E0412]: cannot find type NonZeroI16 in module num
--> /home/brian/.cargo/registry/src/github.com-1ecc6299db9ec823/serde-1.0.99/src/de/impls.rs:2417:5
|
2417 | NonZeroI16,
| ^^^^^^^^^^ help: a struct with a similar name exists: NonZeroU16

error[E0412]: cannot find type NonZeroI32 in module num
--> /home/brian/.cargo/registry/src/github.com-1ecc6299db9ec823/serde-1.0.99/src/de/impls.rs:2418:5
|
2418 | NonZeroI32,
| ^^^^^^^^^^ help: a struct with a similar name exists: NonZeroU32

error[E0412]: cannot find type NonZeroI64 in module num
--> /home/brian/.cargo/registry/src/github.com-1ecc6299db9ec823/serde-1.0.99/src/de/impls.rs:2419:5
|
2419 | NonZeroI64,
| ^^^^^^^^^^ help: a struct with a similar name exists: NonZeroU64

error[E0412]: cannot find type NonZeroIsize in module num
--> /home/brian/.cargo/registry/src/github.com-1ecc6299db9ec823/serde-1.0.99/src/de/impls.rs:2420:5
|
2420 | NonZeroIsize,
| ^^^^^^^^^^^^ help: a struct with a similar name exists: NonZeroUsize

error[E0412]: cannot find type NonZeroI128 in module num
--> /home/brian/.cargo/registry/src/github.com-1ecc6299db9ec823/serde-1.0.99/src/de/impls.rs:2432:9
|
2432 | NonZeroI128,
| ^^^^^^^^^^^ help: a struct with a similar name exists: NonZeroU128

error[E0412]: cannot find type NonZeroI8 in module num
--> /home/brian/.cargo/registry/src/github.com-1ecc6299db9ec823/serde-1.0.99/src/ser/impls.rs:493:5
|
493 | NonZeroI8,
| ^^^^^^^^^ help: a struct with a similar name exists: NonZeroU8

error[E0412]: cannot find type NonZeroI16 in module num
--> /home/brian/.cargo/registry/src/github.com-1ecc6299db9ec823/serde-1.0.99/src/ser/impls.rs:494:5
|
494 | NonZeroI16,
| ^^^^^^^^^^ help: a struct with a similar name exists: NonZeroU16

error[E0412]: cannot find type NonZeroI32 in module num
--> /home/brian/.cargo/registry/src/github.com-1ecc6299db9ec823/serde-1.0.99/src/ser/impls.rs:495:5
|
495 | NonZeroI32,
| ^^^^^^^^^^ help: a struct with a similar name exists: NonZeroU32

error[E0412]: cannot find type NonZeroI64 in module num
--> /home/brian/.cargo/registry/src/github.com-1ecc6299db9ec823/serde-1.0.99/src/ser/impls.rs:496:5
|
496 | NonZeroI64,
| ^^^^^^^^^^ help: a struct with a similar name exists: NonZeroU64

error[E0412]: cannot find type NonZeroIsize in module num
--> /home/brian/.cargo/registry/src/github.com-1ecc6299db9ec823/serde-1.0.99/src/ser/impls.rs:497:5
|
497 | NonZeroIsize,
| ^^^^^^^^^^^^ help: a struct with a similar name exists: NonZeroUsize

error[E0412]: cannot find type NonZeroI128 in module num
--> /home/brian/.cargo/registry/src/github.com-1ecc6299db9ec823/serde-1.0.99/src/ser/impls.rs:509:9
|
509 | NonZeroI128,
| ^^^^^^^^^^^ help: a struct with a similar name exists: NonZeroU128

Compiling toml v0.2.1
error: aborting due to 12 previous errors

For more information about this error, try rustc --explain E0412.
error: Could not compile serde.
warning: build failed, waiting for other jobs to finish...
error: failed to compile cargo-xbuild v0.5.15, intermediate artifacts can be found at /tmp/cargo-installBZUZ1C

Caused by:
build failed

I was noticing on a number of reboots, the system would take quite a while to boot back up.

I am able to recreate the issue pretty consistently by doing the following:

• Cold boot system
• Log in
• Plug in USB 3.0 type A M.2 enclosure on right side of Galago Pro
• Reboot machine

During the reboot of the machine, it pretty quickly powers down and back up to the System76 splash screen. After that the system sits with a terminal cursor in the top left for close to 90 seconds.

systemd-analyze shows that the kernel took a significant amount of time to load (1min 26sec last time I checked).

Checking dmesg I see the following logs around the largest gap in time. This makes me think it has something to do with Thunderbolt initiation.

kernel_load.log

The Darter Pro fails to boot from a variety of USB devices. All of the below listed devices were recognized and mounted within the OS on all 3 USB ports.

For reference when referring to specific USB ports on the Darter Pro:
USB port 1: Port closest to the power button
USB port 2: Port next to USB port 1
USB port 3: Port on the other side of the machine

The following are the devices tried. They all had a bootable OS installed. The usb drive was plugged in while the machine was off and then the system was cold booted (checkbox checked if boot was successful):

• SanDisk Cruzer Blade 8GB

• SanDisk Cruzer Micro 8GB

  • This USB for some reason has a second "drive" a "SanDisk Cruzer CD Drive" at /dev/sr0.

  • Two options are therefore shown in the bios menu, USB Device and USB Device

  • USB Device goes to a grub shell

  • USB Device 1 fails and goes back to the main BIOS menu. Very quickly an error message is shown (but practically impossible to read without the aid of a camera):

  • 

  • It is a little concerning to me that this error mentions pressing a key to continue but I was never given the opportunity to do so.

  • This happened connected to each usb port.

• SanDisk Ultra USB 3.0 32GB

  • All 3 USB ports booted the drive to a grub shell

• DataStick Pro by Centon

  • When connected to any of the USB ports, the drive was not recognized in the bios menu

• ASUS Republic of Gamers giveaway flash drive

  • When plugged in to the USB port 1 or 3, the drive was not recognized in the bios menu
  • When plugged into port 2, the system booted to a GRUB shell

• USB 3.0 System76 Pop!_OS Flash drive

  • All 3 USB ports booted the drive to a grub shell

This may be similarly related to #10

@WatchMkr reported the keyboard sometimes failing to work on resume. @system76/quality-assurance could you test on the lab systems as well?

On the current firmware, bootable usb devices are listed as EFI USB Device, EFI USB Device 2, etc.

On INSYDE firmware, the drives are listed with unique names/descriptions (eg. SanDisk Cruzer). It is much easier to identify a device this way.

After updating firmware via USB, the system boots straight into the BIOS menu. I understand the desire to want to do that for previous proprietary BIOS versions, but I am unsure of the use for this with open firmware.

Currently the description for the Boot Default BIOS menu option reads This selection will direct the system to continue to booting process. This feels very complex and potentially too verbose to clearly describe to a user what this option does.

It was also noticed that the other two BIOS menu options are written in second person ("this menu will take you to..."). For better consistency, these options should probably either avoid "you" or use it for all three menu options.

Ideas that might be better:
This selection will direct the system to boot
`This selection will direct the system to the booting process".

For what it is worth, the current phrasing is what is currently listed on INSYDE proprietary firmware so potentially this is a non-issue.

When booting from an external drive to update firmware, the firmware updater appears for a second or two before rebooting without a prompt. There is then quite a long time before the firmware updater reappears.

I could see this being misinterpreted in many different ways as it is not clear that the updater is still working properly.

After upgrading from 19.04 to 19.10, the one time boot menu now shows 5 options listed Pop!_OS 19.10.

I will provide more details on a future install.

When installing firmware from usb drive, when booting from the usb drive for the first time, the firmware updater appears for a couple of seconds before rebooting immediately. After rebooting I am prompted to press Enter to start the upgrade. Is this intended?

On the Darter, attempting to boot from an external M.2 USB drive goes to a GRUB shell. This happens on all USB 3 type A ports on the machine. This drive works on proprietary firmware on the previous model.

Plugging in a (laptop)usb-c to DisplayPort(monitor) cable to get an external display does not work. On the darp5 and galp3-c a setting in the BIOS needs to be made to enable the external display to work: Advanced->Advanced Chipset Control->DDI Control: DDI to TBT (was DDI to mDP).

I am unable to reach the systemd-boot menu without setting a timeout (show that it is displayed). Usually(with proprietary firmware) I have success selecting the boot option from the bios menu and then pressing Space. That does not work here. I also tried just pressing Space or Shift when the system is booting but pressing just about any key takes me into the bios menu.

Similar to the proprietary INSYDE firmware, it would be nice for the "One Time Boot" menu to recognize when a new bootable device is connected/disconnected and update the boot options accordingly.

Thunderbolt works better when using this kernel parameter:

pci=assign-busses,hpmemsize=1G,hpbussize=8

Running 2019-10-07_5d2e96c (-dirty, because of commented out "SMMSTORE".to_string(),). When pressing the power button to resume from suspend, the lights on the machine light up as thought the system is resuming but I see no progress on the screen. I did not let the system sit long enough to see if it eventually does reinitialize, I will investigate first thing in the morning.

When using the Fn hotkeys to change volume or display brightness, the key will occasionally require repeated keypresses instead of being holdable. Being able to hold the key down to quickly adjust the volume or screen brightness is much more convenient than having to press the key a bunch of times. @brs17 was seeing this intermittently on the i5 Darter Pro, though I have not encountered it yet.

With a USB device plugged in (usb 2 or 3.*), a reboot of the system takes over 70 seconds to get back to the System76 BIOS splash screen. This reboot can happen from either the BIOS menu or the operating system itself.

EDIT:

After further investigation, I found that if I decline to do a firmware update while in the firmware updater (by pressing Space), then every subsequent reboot takes over 70 seconds (to get to the System76 BIOS splash screen). Once the system is completely powered off, the issue will no longer persist.

After a firmware update on open firmware, the system boots into the BIOS menu. This was done with proprietary firmware to disable the M.E. As this is not necessary on models using open firmware, there is no need to boot into the BIOS.

On a Darter Pro:

After having installed Pop!_OS 19.04 to a NVMe drive, I removed the drive. Upon booting the system, I was taken to an EFI shell that gives the message that there is nothing to mount. Going into the bios, I still see Pop!_OS 19.04, Linux Boot Manager, and an EFI shell as bootable options.

On proprietary firmware provided by upstream, in a similar situation, the system shows a message: Default Boot Device Missing or Boot Failed. Insert Recovery Media and Hit any key Then Select 'Boot Manager' to choose a new Boot Device or to Boot Recovery Media. In the bios menu there are no selectable options from which to boot.

I think it is important in this situation to make it clear to the user that there is no bootable media immediately available.

When a dual boot is set up with two separate EFI partitions, Pop must be the default boot option in order to access the systemd-boot menu. Holding spacebar after selecting the Pop entry does nothing and the machine boots straight into Pop.

Currently the BIOS menu does not list the hardware currently installed. This is useful when trying to diagnose a hardware issue and unable to boot into an OS.

INSYDE firmware currently lists CPU, memory frequency, and memory size.

On the Galago Pro, if I unplug AC power at a specific point while the system is rebooting, the system will turn off. The point to remove the AC power is right around the time that the system is about to reboot (before the System76 splash screen). I have been able to recreate the issue providing AC via the barrel jack as well as via usb-c.

Steps to reproduce issue:

1. System is off
2. Plug in external harddrive with firmware written to it.
3. Press Esc when System76 logo appears.
4. See system sit for quite a while before eventually getting into the BIOS menu.

When booting a system with multiple drives, all of the drives will appear even if there is nothing from which to boot on a specific drive.

Implement support for firmware updates to coreboot firmware

• https://github.com/system76/firmware/pull/174
• pop-os/system76-firmware#20

Driver support required

• pop-os/system76-driver#132

Currently the BIOS menu does not show the current version of firmware that the system is running. I would think having the version listed would be valuable when debugging an issue or making sure that firmware is up-to-date.

After setting up a Pop!_OS 19.04 install I quite frequently found the Thunderbolt settings page in gnome-control-center saying No Thunderbolt support. At first I thought it required a Thunderbolt device to be plugged in on boot for it to be initialized properly, but later found Thunderbolt working between cold boots and reboots. For a while Thunderbolt seemed to be recognized in gnome-control-center but then eventually No Thunderbolt support appears again.

I have yet to discover how to get Thunderbolt support not to work consistently.

Oct 3 15:54:48 pop-os kernel: [ 2938.517757] iwlwifi 0000:00:14.3: Unhandled alg: 0x707
Oct 3 16:53:55 pop-os kernel: [ 6485.442249] pcieport 0000:02:01.0: bridge window [mem 0x00100000-0x000fffff] to [bus 04] add_size 400000 add_align 100000
Oct 3 16:53:55 pop-os kernel: [ 6485.442292] pcieport 0000:02:01.0: BAR 14: no space for [mem size 0x00400000]
Oct 3 16:53:55 pop-os kernel: [ 6485.442297] pcieport 0000:02:01.0: BAR 14: failed to assign [mem size 0x00400000]
Oct 3 16:53:55 pop-os kernel: [ 6485.442303] pcieport 0000:02:01.0: BAR 14: no space for [mem size 0x00400000]
Oct 3 16:53:55 pop-os kernel: [ 6485.442307] pcieport 0000:02:01.0: BAR 14: failed to assign [mem size 0x00400000]
Oct 3 17:43:35 pop-os kernel: [ 9465.342413] PM: suspend entry (deep)
Oct 4 13:58:18 pop-os kernel: [ 9465.353201] Filesystems sync: 0.010 seconds
Oct 4 13:58:18 pop-os kernel: [ 9465.353533] Freezing user space processes ... (elapsed 0.124 seconds) done.
Oct 4 13:58:18 pop-os kernel: [ 9465.478250] OOM killer disabled.
Oct 4 13:58:18 pop-os kernel: [ 9465.478253] Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done.
Oct 4 13:58:18 pop-os kernel: [ 9465.480657] printk: Suspending console(s) (use no_console_suspend to debug)
Oct 4 13:58:18 pop-os kernel: [ 9465.483107] wlp0s20f3: deauthenticating from ac:86:74:bf:2e:10 by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 4 13:58:18 pop-os kernel: [ 9467.374649] ACPI: EC: interrupt blocked
Oct 4 13:58:18 pop-os kernel: [ 9467.436309] ACPI: Preparing to enter system sleep state S3
Oct 4 13:58:18 pop-os kernel: [ 9467.438765] ACPI: EC: event blocked
Oct 4 13:58:18 pop-os kernel: [ 9467.438766] ACPI: EC: EC stopped
Oct 4 13:58:18 pop-os kernel: [ 9467.438796] PM: Saving platform NVS memory
Oct 4 13:58:18 pop-os kernel: [ 9467.438798] Disabling non-boot CPUs ...
Oct 4 13:58:18 pop-os kernel: [ 9467.441782] smpboot: CPU 1 is now offline
Oct 4 13:58:18 pop-os kernel: [ 9467.447700] smpboot: CPU 2 is now offline
Oct 4 13:58:18 pop-os kernel: [ 9467.451354] irq_migrate_all_off_this_cpu: 6 callbacks suppressed
Oct 4 13:58:18 pop-os kernel: [ 9467.451356] IRQ 122: no longer affine to CPU3
Oct 4 13:58:18 pop-os kernel: [ 9467.451366] IRQ 130: no longer affine to CPU3
Oct 4 13:58:18 pop-os kernel: [ 9467.451378] IRQ 160: no longer affine to CPU3
Oct 4 13:58:18 pop-os kernel: [ 9467.452410] smpboot: CPU 3 is now offline
Oct 4 13:58:18 pop-os kernel: [ 9467.456141] IRQ 161: no longer affine to CPU4
Oct 4 13:58:18 pop-os kernel: [ 9467.456149] IRQ 162: no longer affine to CPU4
Oct 4 13:58:18 pop-os kernel: [ 9467.456155] IRQ 164: no longer affine to CPU4
Oct 4 13:58:18 pop-os kernel: [ 9467.456162] IRQ 166: no longer affine to CPU4
Oct 4 13:58:18 pop-os kernel: [ 9467.456168] IRQ 167: no longer affine to CPU4
Oct 4 13:58:18 pop-os kernel: [ 9467.456174] IRQ 168: no longer affine to CPU4
Oct 4 13:58:18 pop-os kernel: [ 9467.458341] smpboot: CPU 4 is now offline
Oct 4 13:58:18 pop-os kernel: [ 9467.462077] IRQ 123: no longer affine to CPU5
Oct 4 13:58:18 pop-os kernel: [ 9467.463174] smpboot: CPU 5 is now offline
Oct 4 13:58:18 pop-os kernel: [ 9467.469303] smpboot: CPU 6 is now offline
Oct 4 13:58:18 pop-os kernel: [ 9467.474279] smpboot: CPU 7 is now offline
Oct 4 13:58:18 pop-os kernel: [ 9467.481087] ACPI: Low-level resume complete
Oct 4 13:58:18 pop-os kernel: [ 9467.481150] ACPI: EC: EC started
Oct 4 13:58:18 pop-os kernel: [ 9467.481150] PM: Restoring platform NVS memory
Oct 4 13:58:18 pop-os kernel: [ 9467.481990] Enabling non-boot CPUs ...
Oct 4 13:58:18 pop-os kernel: [ 9467.482024] x86: Booting SMP configuration:
Oct 4 13:58:18 pop-os kernel: [ 9467.482024] smpboot: Booting Node 0 Processor 1 APIC 0x1
Oct 4 13:58:18 pop-os kernel: [ 9467.482620] CPU1 is up
Oct 4 13:58:18 pop-os kernel: [ 9467.482646] smpboot: Booting Node 0 Processor 2 APIC 0x2
Oct 4 13:58:18 pop-os kernel: [ 9467.483136] CPU2 is up
Oct 4 13:58:18 pop-os kernel: [ 9467.483158] smpboot: Booting Node 0 Processor 3 APIC 0x3
Oct 4 13:58:18 pop-os kernel: [ 9467.483655] CPU3 is up
Oct 4 13:58:18 pop-os kernel: [ 9467.483676] smpboot: Booting Node 0 Processor 4 APIC 0x4
Oct 4 13:58:18 pop-os kernel: [ 9467.484191] CPU4 is up
Oct 4 13:58:18 pop-os kernel: [ 9467.484212] smpboot: Booting Node 0 Processor 5 APIC 0x5
Oct 4 13:58:18 pop-os kernel: [ 9467.484718] CPU5 is up
Oct 4 13:58:18 pop-os kernel: [ 9467.484737] smpboot: Booting Node 0 Processor 6 APIC 0x6
Oct 4 13:58:18 pop-os kernel: [ 9467.485263] CPU6 is up
Oct 4 13:58:18 pop-os kernel: [ 9467.485283] smpboot: Booting Node 0 Processor 7 APIC 0x7
Oct 4 13:58:18 pop-os kernel: [ 9467.485810] CPU7 is up
Oct 4 13:58:18 pop-os kernel: [ 9467.487996] ACPI: Waking up from system sleep state S3
Oct 4 13:58:18 pop-os kernel: [ 9468.538304] ACPI: EC: interrupt unblocked
Oct 4 13:58:18 pop-os kernel: [ 9468.601227] ACPI: EC: event unblocked
Oct 4 13:58:18 pop-os kernel: [ 9468.601652] usb usb3: root hub lost power or was reset
Oct 4 13:58:18 pop-os kernel: [ 9468.601656] usb usb4: root hub lost power or was reset
Oct 4 13:58:18 pop-os kernel: [ 9468.707598] nvme nvme0: Shutdown timeout set to 8 seconds
Oct 4 13:58:18 pop-os kernel: [ 9468.722290] nvme nvme0: 8/0/0 default/read/poll queues
Oct 4 13:58:18 pop-os kernel: [ 9468.847315] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
Oct 4 13:58:18 pop-os kernel: [ 9468.918160] ata1: SATA link down (SStatus 4 SControl 300)
Oct 4 13:58:18 pop-os kernel: [ 9469.739943] psmouse serio2: synaptics: queried max coordinates: x [..5718], y [..4908]
Oct 4 13:58:18 pop-os kernel: [ 9469.859560] psmouse serio2: synaptics: queried min coordinates: x [1238..], y [956..]
Oct 4 13:58:18 pop-os kernel: [ 9550.943355] thunderbolt 0000:03:00.0: failed to send driver ready to ICM
Oct 4 13:58:18 pop-os kernel: [ 9550.943654] OOM killer enabled.
Oct 4 13:58:18 pop-os kernel: [ 9550.943656] Restarting tasks ...
Oct 4 13:58:18 pop-os kernel: [ 9550.943873] usb 1-4: USB disconnect, device number 2
Oct 4 13:58:18 pop-os kernel: [ 9550.950463] done.
Oct 4 13:58:18 pop-os kernel: [ 9550.950685] Bluetooth: hci0: Bootloader revision 0.1 build 0 week 30 2018
Oct 4 13:58:18 pop-os kernel: [ 9550.951689] Bluetooth: hci0: Device revision is 2
Oct 4 13:58:18 pop-os kernel: [ 9550.951691] Bluetooth: hci0: Secure boot is enabled
Oct 4 13:58:18 pop-os kernel: [ 9550.951692] Bluetooth: hci0: OTP lock is enabled
Oct 4 13:58:18 pop-os kernel: [ 9550.951692] Bluetooth: hci0: API lock is enabled
Oct 4 13:58:18 pop-os kernel: [ 9550.951693] Bluetooth: hci0: Debug lock is disabled
Oct 4 13:58:18 pop-os kernel: [ 9550.951695] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Oct 4 13:58:18 pop-os kernel: [ 9550.951973] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-1.sfi
Oct 4 13:58:18 pop-os kernel: [ 9551.286973] PM: suspend exit
Oct 4 13:58:20 pop-os kernel: [ 9552.667666] Generic Realtek PHY r8169-601:00: attached PHY driver [Generic Realtek PHY] (mii_bus:phy_addr=r8169-601:00, irq=IGNORE)
Oct 4 13:58:20 pop-os kernel: [ 9552.674663] Bluetooth: hci0: Waiting for firmware download to complete
Oct 4 13:58:20 pop-os kernel: [ 9552.675663] Bluetooth: hci0: Firmware loaded in 1684938 usecs
Oct 4 13:58:20 pop-os kernel: [ 9552.675713] Bluetooth: hci0: Waiting for device to boot
Oct 4 13:58:20 pop-os kernel: [ 9552.688819] Bluetooth: hci0: Device booted in 12808 usecs
Oct 4 13:58:20 pop-os kernel: [ 9552.688885] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-1.ddc
Oct 4 13:58:20 pop-os kernel: [ 9552.703853] Bluetooth: hci0: Applying Intel DDC parameters completed
Oct 4 13:58:20 pop-os kernel: [ 9552.779354] r8169 0000:06:00.1 enp6s0f1: Link is Down
Oct 4 13:58:21 pop-os kernel: [ 9553.564809] wlp0s20f3: authenticate with ac:86:74:bf:2e:30
Oct 4 13:58:21 pop-os kernel: [ 9553.568593] wlp0s20f3: send auth to ac:86:74:bf:2e:30 (try 1/3)
Oct 4 13:58:21 pop-os kernel: [ 9553.579242] iwlwifi 0000:00:14.3: Unhandled alg: 0x707
Oct 4 13:58:21 pop-os kernel: [ 9553.595682] wlp0s20f3: authenticated
Oct 4 13:58:21 pop-os kernel: [ 9553.599545] wlp0s20f3: associate with ac:86:74:bf:2e:30 (try 1/3)
Oct 4 13:58:21 pop-os kernel: [ 9553.601847] wlp0s20f3: RX AssocResp from ac:86:74:bf:2e:30 (capab=0x11 status=0 aid=11)
Oct 4 13:58:21 pop-os kernel: [ 9553.603914] wlp0s20f3: associated
Oct 4 13:58:21 pop-os kernel: [ 9553.609167] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready
Oct 4 14:00:54 pop-os kernel: [ 9705.930851] usb 1-4: new full-speed USB device number 5 using xhci_hcd
Oct 4 14:00:54 pop-os kernel: [ 9706.082621] usb 1-4: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=12.09
Oct 4 14:00:54 pop-os kernel: [ 9706.082629] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 4 14:00:54 pop-os kernel: [ 9706.082634] usb 1-4: Product: USB Receiver
Oct 4 14:00:54 pop-os kernel: [ 9706.082638] usb 1-4: Manufacturer: Logitech
Oct 4 14:00:54 pop-os kernel: [ 9706.092242] logitech-djreceiver 0003:046D:C52B.0007: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-4/input2
Oct 4 14:00:54 pop-os kernel: [ 9706.224713] input: Logitech MX Ergo as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.2/0003:046D:C52B.0007/0003:046D:406F.0008/input/input47
Oct 4 14:00:54 pop-os kernel: [ 9706.226060] logitech-hidpp-device 0003:046D:406F.0008: input,hidraw1: USB HID v1.11 Keyboard [Logitech MX Ergo] on usb-0000:00:14.0-4/input2:1
Oct 4 14:00:56 pop-os kernel: [ 9708.177867] logitech-hidpp-device 0003:046D:406F.0008: HID++ 4.5 device connected.

On the main BIOS menu, an option is shown in the bottom bar that says "Esc=Exit", however hitting the escape key at the main menu does not exit the BIOS. Seeing that prompt makes me expect the escape key to exit the BIOS menu and begin booting normally. To boot normally, I have to select "Boot Default" instead.

Currently the description for the One Time Boot menu is: This selection will take you to the Boot Manager. There is no other reference to a Boot Manager in this BIOS menu.

A similar issue exists for the Change Boot Order menu described: ...will take you to Boot Maintenance Manager where Boot Maintenance Manager is not referenced anywhere else.

Every time I install an operating system to the machine, a new efi entry is created.

This is the case if I install the same OS over and over again which results in potentially having numerous boot entries that all have the same text while pointing to nothing.

Fixed by 921f96d

Error:

src/cpu/x86/Makefile.inc:21: *** Halting the build due to unknown TARGET_STAGE select. Stop.

Currently when scrolling through the boot options under One Time Boot, the options have a description with the Device Path. This potentially helps a user select the correct boot option when the human readable description is vague.

The same Device Path description is not provided when changing the boot order but would be an improvement over the description showing the exact same text as is highlighted.

When removing all of the boot devices, the system currently does not remove all boot entries from the BIOS menu but should as there is nothing from which to boot.