Closed wshanks closed 6 months ago
hughsie
commented
6 months ago Ugh, so I really didn't think getting the BOS descriptor would affect anything. 2/2 of the reports are Kensington mice, which might be helpful. Out of interest, does sudo gusbcmd save also cause a warning and for the mouse not to work too?
wshanks
commented
6 months ago sudo gusbcmd save does cause the mouse to stop working. I don't see a warning on the console. This is what I see in journalctl -xe:
Mar 04 11:53:29 wshankspurple sudo[13308]: wshanks : TTY=pts/1 ; PWD=/home/wshanks ; USER=root ; COMMAND=/usr/bin/gusbcmd save
Mar 04 11:53:29 wshankspurple audit[13308]: USER_CMD pid=13308 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='cwd="/home/wshanks" cmd=67757362636D642073617665 exe="/usr/bin/sudo" terminal=pts/1 r>
Mar 04 11:53:29 wshankspurple audit[13308]: CRED_REFR pid=13308 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_env,pam_fprintd acct="root" exe="/usr/bin/sudo" hostname>
Mar 04 11:53:29 wshankspurple gnome-terminal-[5272]: void terminal_screen_shell_preexec(VteTerminal*): assertion '!priv->between_preexec_and_precmd' failed
Mar 04 11:53:29 wshankspurple sudo[13308]: pam_unix(sudo:session): session opened for user root(uid=0) by wshanks(uid=1000)
Mar 04 11:53:29 wshankspurple audit[13308]: USER_START pid=13308 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_syst>
Mar 04 11:53:30 wshankspurple kernel: usb 3-7: usbfs: process 13310 (gusbcmd) did not claim interface 0 before use
Mar 04 11:53:30 wshankspurple kernel: usb 3-1: usbfs: process 13310 (gusbcmd) did not claim interface 0 before use
Mar 04 11:53:30 wshankspurple sudo[13308]: pam_unix(sudo:session): session closed for user rootFrom internet searching, it seems like the mouse may have been manufactured in 2006, so it is pretty old. It hasn't otherwise given me any reason to replace it though.
I changed the issue description because I had written it back when I thought it was important that the mouse was behind a dock and a hub.
hughsie
commented
6 months ago sudo gusbcmd save does cause the mouse to stop working
@superm1 okay if I add the VID/PID to an internal no-bos-descriptor flag or something like that?
superm1
commented
6 months ago I mean it makes sense certainly as a bandaid; but are we missing something in the design? Should we maybe only be opting in devices with a manufacturing date that's new enough?
hughsie
commented
6 months ago I mean it makes sense certainly as a bandaid; but are we missing something in the design?
Maybe!? Getting a USB descriptor shouldn't brick the device, and I'm also wondering how this doesn't break in Windows too.
Should we maybe only be opting in devices with a manufacturing date that's new enough?
How do we get the manufacturing date tho?
hughsie
commented
6 months ago @wshanks can you get us the sudo lsusb -vvv output please
superm1
commented
6 months ago How do we get the manufacturing date tho?
I was naively hoping there was something in the descriptor to go on. If not; then lets see if there are any better heuristics.
wshanks
commented
6 months ago Here is the sudo lsusb -vvv output:
polter-rnd
commented
6 months ago I can confirm the same with A4tech keyboard, Fedora 39 with fwupd-fwupd-1.9.14-1:
Bus 003 Device 003: ID 09da:2268 A4Tech Co., Ltd. USB Keyboard
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 [unknown]
bDeviceSubClass 0 [unknown]
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x09da A4Tech Co., Ltd.
idProduct 0x2268 USB Keyboard
bcdDevice 1.04
iManufacturer 1 SONiX
iProduct 2 USB Keyboard
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x003b
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 1 Keyboard
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 79
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 [unknown]
bInterfaceProtocol 0
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 52
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0003 1x 3 bytes
bInterval 10
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0000
(Bus Powered)Keyboard stopped working right after fwupd daemon restart during upgrade.
hughsie
commented
6 months ago Also see https://github.com/hughsie/libgusb/pull/117 -- one or the other is fine, and this is just covering both bases.
heyakyra
commented
6 months ago For googlers, this also seems to affect Ledger Nano X
kdj0c
commented
6 months ago FYI This also affect Nostromo n52 gamepad.
This makes it disconnect/reconnect in loop:
[ 610.101511] hid-generic 0003:050D:0815.0386: input,hidraw1: USB HID v1.10 Mouse [Honey Bee Nostromo SpeedPad2 ] on usb-0000:05:00.3-1/input1 [ 610.117114] usb 3-1: USB disconnect, device number 76 [ 610.446931] usb 3-1: new low-speed USB device number 77 using xhci_hcd [ 610.594508] usb 3-1: New USB device found, idVendor=050d, idProduct=0815, bcdDevice= 2.10 [ 610.594516] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 610.594520] usb 3-1: Product: Nostromo SpeedPad2 [ 610.594524] usb 3-1: Manufacturer: Honey Bee [ 610.646861] input: Honey Bee Nostromo SpeedPad2 as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:05:00.3/usb3/3-1/3-1:1.0/0003:050D:0815.0387/input/input922 [ 610.698538] hid-generic 0003:050D:0815.0387: input,hidraw0: USB HID v1.10 Keyboard [Honey Bee Nostromo SpeedPad2 ] on usb-0000:05:00.3-1/input0 [ 610.703784] input: Honey Bee Nostromo SpeedPad2 as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:05:00.3/usb3/3-1/3-1:1.1/0003:050D:0815.0388/input/input923 [ 610.755706] hid-generic 0003:050D:0815.0388: input,hidraw1: USB HID v1.10 Mouse [Honey Bee Nostromo SpeedPad2 ] on usb-0000:05:00.3-1/input1 [ 662.668052] usb 3-1: USB disconnect, device number 77 [ 663.053234] usb 3-1: new low-speed USB device number 78 using xhci_hcd [ 663.197720] usb 3-1: New USB device found, idVendor=050d, idProduct=0815, bcdDevice= 2.10 [ 663.197727] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 663.197731] usb 3-1: Product: Nostromo SpeedPad2 [ 663.197734] usb 3-1: Manufacturer: Honey Bee [ 663.238075] input: Honey Bee Nostromo SpeedPad2 as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:05:00.3/usb3/3-1/3-1:1.0/0003:050D:0815.0389/input
hughsie
commented
6 months ago @kdj0c does that work in Windows? That's got bcdDevice= 2.10 and so should accept getting the BOS descriptors. I'm guessing stopping fwupd and then doing "sudo gusbcmd save" makes the device act in the same way?
kdj0c
commented
6 months ago @kdj0c does that work in Windows? That's got bcdDevice= 2.10 and so should accept getting the BOS descriptors. I'm guessing stopping fwupd and then doing "sudo gusbcmd save" makes the device act in the same way?
I don't have a windows installation here, so I don't know if it still works.
Also here is the log when I run:
fwupdtool get-devices --verbose --verbose
10:30:09.672 FuUsbDevice ignoring missing BOS descriptor: USB error on device 050d:0815 : Input/Output Error [-1]
On Fedora 39, I fixed the issue by downgrading fwupd to fwupd-1.9.5-2.fc39.
ofourdan
commented
6 months ago Same here, latest fwupd 1.9.14 breaks my old trustee Wacom Bamboo One.
The device gets removed then re-added, then removed again continuously with fwupd 1.9.14.
Reverting to 1.9.13 fixes that issue.
[ 2.071746] input: Wacom Bamboo1 Pen as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:056A:0069.0002/input/input10
[ 2.071792] wacom 0003:056A:0069.0002: hidraw1: USB HID v1.10 Mouse [WACOM CTF-430 V2.0-0] on usb-0000:00:14.0-2/input0Attaching lsusb-vvv.txt
hughsie
commented
6 months ago @ofourdan on a hunch, can you try the https://copr.fedorainfracloud.org/coprs/rhughes/fwupd/ build please
superm1
commented
6 months ago Or you can grab snap/flatpak artifacts if it's easier depending on your distro.
ofourdan
commented
6 months ago @ofourdan on a hunch, can you try the https://copr.fedorainfracloud.org/coprs/rhughes/fwupd/ build please
Works for me! :+1:
hughsie
commented
6 months ago Works for me! 👍
Okay, so I think the last commit was unnecessary -- I think we just need a release with https://github.com/fwupd/fwupd/commit/f92ea06110f5075d7b94c90ad1a637f6b43a647c included. @superm1 I'm tempted to leave it in as an example on what to do -- and so we can quirk without a recompile if a broken USB 2.1 device turns up in the real world. Or maybe we remove the .quirk file and leave the code change?
superm1
commented
6 months ago Let's leave both. I agree it's easier to quirk later if the infra is there. Who knows with ancient USB what we'll find!
smunaut
commented
1 month ago Damn, it took me forever to find this issue ...
My FTDI FT232 USB Serial adapter wasn't working properly ( data transfers were still working but any control transfer to set baudrate etc were crashed, the whole EP0 was unresponsive after trying to get BOS desc) and this was caused by fwupd ( which is 1.9.14 on stable gentoo ).
hughsie
commented
1 month ago which is 1.9.14 on stable gentoo
This is terribly old. I thought Gentoo was famous for getting the latest versions of everything?
smunaut
commented
1 month ago 1.9.20 is available but it's not the default, it has to be selected explicitely. I opened a bug on gentoo tracker to bump the stable/default version.
Describe the bug A Kensington USB mouse (this one if it is relevant) stopped working after I applied the most recent updates on my Fedora 39 laptop (Lenovo ThinkPad T14 Gen 2). When I look at the system logs, I see
That message led me to this Debian mailing list post from a few days ago which describes a similar issue and goes into more detail of attempted debugging steps. For me, I found that the mouse just did not work at all, rather than partially working like reported there. I tried
systemctl stop fwupd.serviceand confirmed that the mouse started working again after unplugging it and plugging it back in.systemctl start fwupd.servicestopped the mouse from working once again. Checking the history of dnf updates, I see that thefwupdpackages were updated from 1.9.13 to 1.9.14:and I do not notice other relevant packages being updated (like something with
usbin the name).Like the mailing list post points out, the most suspicious line in the release notes for 1.9.14 seems to be "Fix DS-20 descriptors by opening the GUsbDevice earlier" and I noticed that is some previous discussion about difficulties with nested USB hubs here (the only thing that comes up when I search for "BOS descriptor").
One other note -- when I first noticed this, I actually had the mouse plugged into a StarTech USB hub (which lsusb detects as "Genesys Logic, Inc. GL3523 Hub") which was then plugged into a Lenovo Thunderbolt 4 dock which was plugged into the Thunderbolt 4 port of the laptop. However, I then tested and got the same issue both using the mouse plugged directly into the dock and using the mouse plugged directly into a usb port on the laptop.
Steps to Reproduce This is mostly described above:
systemctl stop fwupd.servicesystemctl start fwupd.serviceIn my standard set up, I have a webcam and keyboard plugged into the StarTech hub plugged into the Thunderbolt 4 dock as well and they are not affected by fwupd.
Expected behavior
fwupd.serviceshould not stop the mouse from working.fwupd version information Please provide the version of the daemon and client.
Please note how you installed it (
apt,dnf,pacman, source, etc): dnf**fwupd device information**
Please provide the output of the fwupd devices recognized in your system. **NOTE**: I ran this without the Thunderbolt 4 dock or the StarTech hub for simplicity, so it should just be a standard Thinkpad T14 Gen 2 output with a USB mouse plugged in. ```shell fwupdmgr get-devices --show-all-devices LENOVO 20W1SB9V00 │ ├─Unknown Device: │ Device ID: 63223cc2d1b0b8d4c45ef8cedcb1f45315d3ff20 │ GUID: ca5c154c-a46a-59d8-bf77-0ca40522cc85 ← GPIO\ID_INT34C5:00 │ ├─11th Gen Intel Core™ i5-1145G7 @ 2.60GHz: │ Device ID: 4bde70ba4e39b28f9eab1628f9dd6e6244c03027 │ Current version: 0x000000b6 │ Vendor: Intel │ GUIDs: 2347ad97-b545-5bae-b6b3-b70a9553cbba ← CPUID\PRO_0&FAM_06&MOD_8C │ 1df99df5-22f4-5505-98cc-22dcc53b132a ← CPUID\PRO_0&FAM_06&MOD_8C&STP_1 │ Device Flags: • Internal device │ ├─B140HAK03.2: │ Device ID: aec1a869eb0df71b7cea6b3ac71d39b830faf164 │ GUID: 5f821c3a-9b73-5259-8678-7f49c11213b4 ← DRM\VEN_AUO&DEV_323D │ Device Flags: • Internal device │ ├─Battery: │ Device ID: f95c9218acd12697af946874bfe4239587209232 │ Summary: UEFI ESRT device │ Current version: 1.2.10 │ Minimum Version: 0.0.1 │ Vendor: Lenovo (DMI:LENOVO) │ Update State: Success │ GUID: b16a1723-93ae-4863-ade5-64b615907621 │ Device Flags: • Internal device │ • Updatable │ • System requires external power source │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ Device Requests: • Message │ ├─Embedded Controller: │ Device ID: 2292ae5236790b47884e37cf162dcf23bfcd1c60 │ Summary: UEFI ESRT device │ Current version: 0.1.44 │ Minimum Version: 0.1.44 │ Vendor: Lenovo (DMI:LENOVO) │ Update State: Success │ GUID: 2a5d161c-0ba2-4136-94b3-c027f0a7e5fc │ Device Flags: • Internal device │ • Updatable │ • System requires external power source │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ Device Requests: • Message │ ├─Integrated Camera: │ Device ID: 3fa281ddf80d8a06b8ee5d8beb48d38ee95a9627 │ Current version: 61.18 │ Vendor: Chicony Electronics Co.,Ltd. (USB:0x04F2) │ Serial Number: 0001 │ GUID: f8d483f9-9284-51b6-9363-7e6d59c40a97 ← USB\VID_04F2&PID_B6D0 │ Device Flags: • Updatable │ ├─Intel Management Engine: │ Device ID: 349bb341230b1a86e5effe7dfe4337e1590227bd │ Summary: UEFI ESRT device │ Current version: 240.47.2473 │ Minimum Version: 0.0.1 │ Vendor: Lenovo (DMI:LENOVO) │ Update State: Success │ GUID: 9a03b1ec-b756-4414-bc09-1f573603aeaa │ Device Flags: • Internal device │ • Updatable │ • System requires external power source │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ Device Requests: • Message │ ├─Prometheus: │ │ Device ID: 0d5d05911800242bb1f35287012cdcbd9b381148 │ │ Summary: Fingerprint reader │ │ Current version: 10.01.3478575 │ │ Vendor: Synaptics (USB:0x06CB) │ │ Install Duration: 2 seconds │ │ Serial Number: 152097630560557 │ │ GUID: 8088f861-6318-5b1e-9ce4-fbddbedb09ac ← USB\VID_06CB&PID_00BD │ │ Device Flags: • Updatable │ │ • Supported on remote server │ │ • Cryptographic hash verification is available │ │ • Signed Payload │ │ │ └─Prometheus IOTA Config: │ Device ID: 73e606488fec47b3e3f9288094f66fded0051446 │ Summary: Fingerprint reader config │ Current version: 0029 │ Minimum Version: 0029 │ Vendor: Synaptics (USB:0x06CB) │ GUIDs: 7c5a1e62-38fa-5859-9337-09dbac6377e4 ← USB\VID_06CB&PID_00BD-cfg │ 8a12a1dd-5e54-5cb8-9607-c3a4e3e9a7e4 ← USB\VID_06CB&PID_00BD&CFG1_3462&CFG2_500 │ Device Flags: • Updatable │ • Supported on remote server │ • Only version upgrades are allowed │ • Signed Payload │ ├─SKHynix HFS256GDE9X081N: │ Device ID: 04e17fcf7d3de91da49a163ffe4907855c3648be │ Summary: NVM Express solid state drive │ Current version: 41730C20 │ Vendor: SK hynix (NVME:0x1C5C) │ Serial Number: FYB5N018811405G4R │ GUIDs: 0ee57466-ca9d-5f10-a005-ec6bacf6fb82 ← NVME\VEN_1C5C&DEV_174A │ 34e06406-f620-5b9d-a9cd-7f3a4e648633 ← NVME\VEN_1C5C&DEV_174A&SUBSYS_1C5C174A │ 59919342-93e0-53d6-bf67-851cb77dd09a ← SKHynix_HFS256GDE9X081N │ Device Flags: • Internal device │ • Updatable │ • System requires external power source │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ • Signed Payload │ ├─System Firmware: │ │ Device ID: a45df35ac0e948ee180fe216a5f703f32dda163f │ │ Summary: UEFI ESRT device │ │ Current version: 0.1.60 │ │ Vendor: Lenovo (DMI:LENOVO) │ │ Update State: Success │ │ GUID: 973a10fa-79c0-453e-b78c-27b55cc0e6eb │ │ Device Flags: • Internal device │ │ • Updatable │ │ • System requires external power source │ │ • Supported on remote server │ │ • Needs a reboot after installation │ │ • Cryptographic hash verification is available │ │ • Device is usable for the duration of the update │ │ Device Requests: • Message │ │ │ ├─AMT [unprovisioned]: │ │ Device ID: 8d5470e73fd9a31eaa460b2b6aea95483fe3f14c │ │ Summary: Hardware and firmware technology for remote out-of-band management │ │ Current version: 15.0.47.2473 │ │ Bootloader Version:15.0.47.2473 │ │ Vendor: Intel Corporation (MEI:0x8086) │ │ GUIDs: 12f80028-b4b7-4b2d-aca8-46e0ff65814c │ │ f18c7464-aa01-5b3d-bd4f-6623597d0f70 ← MEI\VEN_8086&DEV_A0E0 │ │ 85de056a-374c-5590-96e8-e6acda56603c ← MEI\VEN_8086&DEV_A0E0&SUBSYS_17AA22C9 │ │ Device Flags: • Internal device │ │ │ ├─BootGuard Configuration: │ │ Device ID: b0d4430dfa6bde9f0c22680df36dbc8c15c80753 │ │ Current version: 20 │ │ Vendor: Intel Corporation (MEI:0x8086) │ │ GUIDs: dd17041c-09ea-4b17-a271-5b989867ec65 │ │ f18c7464-aa01-5b3d-bd4f-6623597d0f70 ← MEI\VEN_8086&DEV_A0E0 │ │ 85de056a-374c-5590-96e8-e6acda56603c ← MEI\VEN_8086&DEV_A0E0&SUBSYS_17AA22C9 │ │ Device Flags: • Internal device │ │ │ └─UEFI dbx: │ Device ID: 362301da643102b9f38477387e2193e57abaa590 │ Summary: UEFI revocation database │ Current version: 371 │ Minimum Version: 371 │ Vendor: UEFI:Linux Foundation │ Install Duration: 1 second │ GUIDs: 5971a208-da00-5fce-b5f5-1234342f9cf7 ← UEFI\CRT_A9087D1044AD18F7A94916D284CBC01827CF23CD8F60B79072C9CAA1FEF4D649&ARCH_X64 │ f8ba2887-9411-5c36-9cee-88995bb39731 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_X64 │ Device Flags: • Internal device │ • Updatable │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ • Only version upgrades are allowed │ • Signed Payload │ ├─TPM: │ Device ID: c6a80ac3a22083423992a3cb15018989f37834d6 │ Current version: 7.85.17.51968 │ Vendor: Infineon (TPM:IFX) │ GUIDs: 5eebb112-75ad-5536-b173-a11eb3399402 ← TPM\VEN_IFX&DEV_0000 │ ddf995da-1b32-5a8a-bc1b-8d5af4b38b51 ← TPM\VEN_IFX&MOD_SLB9670 │ 6d81ab63-db2e-50ac-934f-6be9accf5e02 ← TPM\VEN_IFX&DEV_0000&VER_2.0 │ 301555de-680d-5ddc-b995-7553fc9138f1 ← TPM\VEN_IFX&MOD_SLB9670&VER_2.0 │ Device Flags: • Internal device │ • System requires external power source │ • Needs a reboot after installation │ • Device can recover flash failures │ • Full disk encryption secrets may be invalidated when updating │ • Signed Payload │ ├─TigerLake-LP GT2 [Iris Xe Graphics]: │ Device ID: 5792b48846ce271fab11c4a545f7a3df0d36e00a │ Current version: 01 │ Vendor: Intel Corporation (PCI:0x8086) │ GUIDs: 54ff3ed7-1ea3-5279-975f-93c13bf2aa53 ← PCI\VEN_8086&DEV_9A49 │ cee01228-7f61-5a47-adab-0584d7f5884f ← PCI\VEN_8086&DEV_9A49&SUBSYS_17AA22C9 │ Device Flags: • Internal device │ • Cryptographic hash verification is available │ ├─UEFI Device Firmware: │ Device ID: d96de5c124b60ed6241ebcb6bb2c839cb5580786 │ Summary: UEFI ESRT device │ Current version: 0 │ Minimum Version: 1 │ Vendor: DMI:LENOVO │ Update State: Success │ GUID: f9046fe1-204a-4fd9-a991-f15075745b98 │ Device Flags: • Internal device │ • Updatable │ • System requires external power source │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ Device Requests: • Message │ ├─UEFI Device Firmware: │ Device ID: f37fb01122dd62c773f4e84ec89737e059712d59 │ Summary: UEFI ESRT device │ Current version: 1 │ Minimum Version: 1 │ Vendor: DMI:LENOVO │ Update State: Success │ GUID: 408e7431-1bfc-4b53-b318-a756e7cd641c │ Device Flags: • Internal device │ • Updatable │ • System requires external power source │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ Device Requests: • Message │ ├─UEFI Device Firmware: │ Device ID: 36efb79c255f402f619fa9eb53cd659db51f2a04 │ Summary: UEFI ESRT device │ Current version: 3082665 │ Vendor: DMI:LENOVO │ Update State: Success │ GUID: f0f8c8b2-9c7d-480c-9c2a-2831f1d7d7c3 │ Device Flags: • Internal device │ • Updatable │ • System requires external power source │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ Device Requests: • Message │ ├─UEFI Device Firmware: │ Device ID: 11a7fbdd09ce583e58b899660fe10f147fd155a2 │ Summary: UEFI ESRT device │ Current version: 24856 │ Minimum Version: 1 │ Vendor: DMI:LENOVO │ Update State: Success │ GUID: 4b3d2033-ae0c-4f25-bc3f-96f0ed347569 │ Device Flags: • Internal device │ • Updatable │ • System requires external power source │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ Device Requests: • Message │ └─UEFI Platform Key: Device ID: 6924110cde4fa051bfdc600a60620dc7aa9d3c6a Summary: Lenovo Ltd. PK CA 2012 Vendor: Lenovo Ltd. GUID: 71599d14-9b31-5270-b3bd-74c494585820 ← UEFI\CRT_9AEF2123F4DE7C19AFABD909BB2C8CAC4411E07E ```Additional questions