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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715146 Title: Not Suspending When Lid is Closed Causing Heat Issue Status in linux package in Ubuntu: Expired Bug description: I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files. I then: sudo vi /etc/systemd/logind.conf Changed: HandleLidSwitchDocked=suspend when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: shawn 1786 F.... pulseaudio DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-09-04 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/02/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.0 dmi.board.name: 05JK94 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
