-
Notifications
You must be signed in to change notification settings - Fork 437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TPM 2.0 firmware update not working on Dell XPS 9360 #689
Comments
What's the message it shows? And if you run |
On 08/27/18 17:49, Mario Limonciello wrote:
What's the message it shows?
Something like, that it found an update file. The screen turns
black then. Can I access these messages from GNU/Linux?
And if you run `fwupdmgr get-results
3f0ecc7823ee99c718693e8ecca38f54e8738dc5` what does it show?
Here are all the results, but that’s for the system firmware
and not TPM.
```
$ fwupdmgr get-results a60b665c769b019e30f31001e91ab31e24d7a035Device a60b665c769b019e30f31001e91ab31e24d7a035 has no results to report
$ fwupdmgr get-results 3f0ecc7823ee99c718693e8ecca38f54e8738dc5Failed to find 3f0ecc7823ee99c718693e8ecca38f54e8738dc5 in history database: No devices found
$ fwupdmgr get-results 9516070bdf03a7484d1145383fc0faeb9c51a521XPS13 9360 Thunderbolt Controller
DeviceId: 9516070bdf03a7484d1145383fc0faeb9c51a521
Guid: 4d86f168-e1cc-5995-afd3-ae9df6a14f5e
Plugin: thunderbolt
Flags: internal|updatable|reported
Version: 00.00
Created: 2018-08-27
Modified: 2018-08-27
UpdateState: success
[Release]
Version: 21.00
Checksum: SHA1(d621932738d56a024cbcc516d9810e4c6ffe477a)
TrustFlags: none
AppstreamGlibVersion: 0.7.4
KernelVersion: 4.18.3-041803-generic
FwupdVersion: 1.0.6
ThunderboltSafeMode: True
GUsbVersion: 0.2.11
BootTime: 1535363748
CpuArchitecture: x86_64
```
|
So it found an update, and then went black and rebooted? You never saw the Dell screen and a progress bar (like you do with UEFI capsule updates)? Sorry, my mistake, can you see if there are any results for |
On 08/27/18 17:59, Mario Limonciello wrote:
> Something like, that it found an update file. The screen turns
black then. Can I access these messages from GNU/Linux?
So it found an update, and then went black and rebooted? You never
saw the Dell screen and a progress bar (like you do with UEFI capsule
updates)?
Yes, I never saw that.
Sorry, my mistake, can you see if there are any results for
`6f9095025a636a5185bfce08ed8e9fc845bc4b8a`?
`fwupdmgr get-results` doesn’t list this ID. There is only the TPM 2.0
ID (a60b665c769b019e30f31001e91ab31e24d7a035), which has no results to
report.
|
OK. Do you know if in this configuration you have UEFI capsule updates have been working in general (non-TPM)? I notice that you have a newer kernel version in place. Did you also change anything else? Would you care to please check your |
On 08/27/18 18:14, Mario Limonciello wrote:
> Yes, I never saw that.
OK. Do you know if in this configuration you have UEFI capsule
updates have been working in general (non-TPM)?
Yes, the Thunderbolt firmware update worked, and the previous UEFI
firmware updates too.
I notice that you have a newer kernel version in place. Did you also
change anything else?
No, I didn’t change anything else.
Would you care to please check your `fwupd.service` journal? I'd
like to see the cached `efibootmgr` output it did before the update
attempt.
```
$ sudo fwupdmgr update
Downloading 1.3.1.0 for XPS 13 9360 TPM 2.0...
Updating 1.3.1.0 on XPS 13 9360 TPM 2.0...
Decompressing… [***************************************]
Authenticating… [***************************************]
Scheduling… [***************************************]
No upgrades for XPS 13 9360 System Firmware, current is 0.2.8.1: 0.2.8.1=same, 0.2.7.1=older, 0.2.6.2=older, 0.2.5.1=older, 0.2.4.2=older, 0.2.3.1=older, 0.2.2.1=older, 0.2.1.0=older, 0.1.3.7=older, 0.1.3.5=older, 0.1.3.2=older, 0.1.2.3=older
Downloading 21.00 for XPS13 9360 Thunderbolt Controller...
Updating 21.00 on XPS13 9360 Thunderbolt Controller...
Decompressing… [***************************************]
Authenticating… [***************************************]
Restarting device… [***************************************]
An update requires a reboot to complete. Restart now? [Y|n]: n
$ journalctl -u fwupd.service -b
-- Logs begin at Mon 2017-10-23 13:12:43 CEST, end at Tue 2018-08-28 11:48:24 CEST. --
Aug 28 11:43:24 Ixpees systemd[1]: Starting Firmware update daemon...
Aug 28 11:43:46 Ixpees fwupd[2013]: failed to get native mode status: Error reading from file: Eingabe-/Ausgabefehler
Aug 28 11:43:46 Ixpees fwupd[2013]: using plugins: upower, amt, colorhug, thunderbolt, altos, ebitdo, udev, dell, csr, nitrokey, dfu, steelseries, unifying, uefi, synapticsmst, thunderbolt_p
Aug 28 11:43:46 Ixpees fwupd[2013]: Daemon ready for requests
Aug 28 11:43:46 Ixpees systemd[1]: Started Firmware update daemon.
Aug 28 11:43:47 Ixpees fwupd[2013]: /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:00.0/0000:03:00.0/domain0/0-0 is in safe mode -- VID/DID will need to be set by another plugin
Aug 28 11:47:15 Ixpees fwupd[2013]: failed to add USB device: 1d6b:0002 is not supported: USB error on device 1d6b:0002 : Input/output error [-1]
Aug 28 11:47:15 Ixpees fwupd[2013]: failed to add USB device: 1d6b:0003 is not supported: USB error on device 1d6b:0003 : Input/output error [-1]
Aug 28 11:47:44 Ixpees fwupd[2013]: new device version '21.0' was is not '21.00', fixing up
```
|
Just FYI , I have this exact same issue: |
Same issue here, failing to update on Dell XPS 9360, running Ubuntu 18.04, 1.3.0.1 -> 1.3.1.0 |
Same here! I think
|
Those affected by this, is your tpm owned? |
I will check |
Hi! Same issue here, failing to update on Dell XPS 9360, running Ubuntu 18.04, 1.3.0.1 -> 1.3.1.0 |
Please try the snap and see if it still happens there. |
@superm1 thanks for advise! For me it works with latest snap sudo fwupdmgr --version sudo fwupdmgr get-updates -v sudo fwupdmgr update -v An update requires a reboot to complete. Restart now? [Y|n]: Y |
Great thanks. |
Hi, I have the very same problem under Debian.
What does "owned TPM" mean ? |
You might consider looking at https://docs.microsoft.com/en-us/windows/security/information-protection/tpm/initialize-and-configure-ownership-of-the-tpm for some high level information about TPM ownership. To fwupd being owned means that it contains data that can not be cleared by the OS. You'll need to enter BIOS firmware setup and clear the TPM there. Then fwupd will be able to perform a TPM firmware upgrade. |
They explicitly advise against clearing the TPM via the BIOS. |
If you're using Windows on the machine this is true, Bitlocker keys are stored in the TPM and you might not be able to boot the machine again if you use it. fwupd is disabling updates (ignoring the device) for the same reason. So it's up to you if you can clear the TPM or not to perform this update. |
Works like a charm, thanks ! |
Ubuntu 18.04 tells me that a firmware update is available.
$ efivar -l | grep fw 0abba7dc-e516-4167-bbf5-4d9d1c739416-fwupdate-73c2051d-8688-56fb-a93f-d56a9b455e52-0
Please answer the following questions:
from source
,pacman
,apt-get
, etc): aptStarting the update seems to work.
On the next startup, the firmware shows a message, that it tries to apply the update, but then after the (automatic) reboot the old firmware is still there.
The text was updated successfully, but these errors were encountered: