No, because it won't install. I tried "fwupdmgr install eac3961ba9bd466f6e34d9276c27d524395d7c3c- NN1TN_NVM21.00.cab", but I got:
could not find thunderbolt device at /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:00.0/0000:03:00.0/domain0/0-0 So I rebooted with Thunderbolt enabled. That gave me: Decompressing… [- ] could not validate firmware: Error reading from file: Input/output error. See https://github.com/hughsie/fwupd/wiki/Thunderbolt:-Validation-failed-or-unknown-device for more information. But a second call gave me the same error as before the reboot (i.e. as before re-enabling Thunderbolt). Enabling test fwupd remote through lvfs-testing.conf gave me the same results after refresh+update, so I guess I typed the right commands. Just after reboot, probably around the time of the first fwupdmgr call, I got this in the dmesg. Could be related: [ma dec 25 23:04:04 2017] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0 [ma dec 25 23:04:04 2017] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ma dec 25 23:04:04 2017] pcieport 0000:00:1c.0: device [8086:9d10] error status/mask=00000001/00002000 [ma dec 25 23:04:04 2017] pcieport 0000:00:1c.0: [ 0] Receiver Error (First) [ma dec 25 23:04:04 2017] xhci_hcd 0000:39:00.0: remove, state 1 [ma dec 25 23:04:04 2017] usb usb4: USB disconnect, device number 1 [ma dec 25 23:04:04 2017] xhci_hcd 0000:39:00.0: USB bus 4 deregistered [ma dec 25 23:04:04 2017] xhci_hcd 0000:39:00.0: xHCI host controller not responding, assume dead [ma dec 25 23:04:04 2017] xhci_hcd 0000:39:00.0: remove, state 1 [ma dec 25 23:04:04 2017] usb usb3: USB disconnect, device number 1 [ma dec 25 23:04:04 2017] xhci_hcd 0000:39:00.0: Host halt failed, -19 [ma dec 25 23:04:04 2017] xhci_hcd 0000:39:00.0: Host not accessible, reset failed. [ma dec 25 23:04:04 2017] xhci_hcd 0000:39:00.0: USB bus 3 deregistered [ma dec 25 23:04:04 2017] thunderbolt 0000:03:00.0: stopping RX ring 0 [ma dec 25 23:04:04 2017] thunderbolt 0000:03:00.0: disabling interrupt at register 0x38200 bit 12 (0xffffffff -> 0xffffefff) [ma dec 25 23:04:04 2017] thunderbolt 0000:03:00.0: stopping TX ring 0 [ma dec 25 23:04:04 2017] thunderbolt 0000:03:00.0: disabling interrupt at register 0x38200 bit 0 (0xffffffff -> 0xfffffffe) [ma dec 25 23:04:04 2017] thunderbolt 0000:03:00.0: control channel stopped [ma dec 25 23:04:04 2017] thunderbolt 0000:03:00.0: freeing RX ring 0 [ma dec 25 23:04:04 2017] thunderbolt 0000:03:00.0: freeing TX ring 0 [ma dec 25 23:04:04 2017] thunderbolt 0000:03:00.0: shutdown [ma dec 25 23:04:04 2017] pci_bus 0000:03: busn_res: [bus 03] is released [ma dec 25 23:04:04 2017] pci_bus 0000:04: busn_res: [bus 04-38] is released [ma dec 25 23:04:04 2017] pci_bus 0000:39: busn_res: [bus 39] is released [ma dec 25 23:04:04 2017] pci_bus 0000:02: busn_res: [bus 02-39] is released Although the dmesg starts about 30s earlier with a bunch of other messages (mainly pci and some thunderbolt, usb and acpi). Possibly the first call took that long. ... [ma dec 25 23:03:37 2017] thunderbolt 0000:03:00.0: NHI initialized, starting thunderbolt ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
