Hi Everyone,
We are working on a new update to 3.06 to try and address the issues that a number of users are experiencing.
Given that users are not able to update successfully to the new version on the first try, we do not want to move this release out of beta.
This updater moved from using the our bios vendor updater tool, to capsule based updates due to the vendor updater tool not supporting retimer firmware updates which are required for thunderbolt certification.
We are currently tracking the following issues:
- When using the windows updater, the update is not always applied on reboot. We think this may be happening when people have their battery fully charged, causing the battery status to discharging/idle.
- EFI shell updater: fail with a script error. This is caused by not cleanly unmounting the usb drive the update is on when it was created. The UEFI filesystem driver will not allow writing to a drive that is is not properly unmounted. We plan to add a check before starting the update process to make sure the drive is writable.
- EFI shell updater: During the update process the system will reboot and portions of the update will not run successfully due to the drive not being recognized by the bios after the reboot, causing the system to boot into the OS on the SSD. We are still looking at a mitigation for this, but if you still want to ensure your update is successful make sure you get to the last update screen. And if not reboot, press F12 for the boot menu and select your thumb drive to continue the update process. You may need to unplug/replug your usb drive in the F12 boot menu to be recognized.
- After finishing the update, some high speed functions may not work on one side of the laptop. This seems to be due to the PD/retimer not resetting correctly during the retimer update, causing all DP/USB3 functions to not work. The current mitigation is to power off the laptop, remove AC, wait 2 minutes and then reboot. This will fully power off the retimer and PD controllers and reset their state.
- When updating in Linux with LVFS, one user experienced a boot loop. We suspect this may be due to the battery charge status mentioned previously. We would suggest booting into the bios, and unplugging the battery for 10 minutes, then plugging in an adapter, and rebooting to see if the capsule update needs battery charging status to update properly.