Welcome to our peer-to-peer forums, where owners help owners. Need help now? Visit eSupport here.

English Community

Linux Operating SystemsUbuntu
All Forum Topics
Options

5 Posts

06-17-2020

Germany

8 Signins

75 Page Views

  • Posts: 5
  • Registered: ‎06-17-2020
  • Location: Germany
  • Views: 75
  • Message 1 of 9

critical thunderbold firmware update under Linux

2020-06-17, 10:48 AM

Hi guys, 

I'm facing the critical firmware update for thunderbold-controler as mentioned in knowledbase (ht508988).

 

I'm running Kubuntu 20.04 LTS at T490 20N3.

I tried both, graphically gnome-firmware and comand-line fwupd to update firmware. There was some firmware updated, but thunderbold-controler still shows version 18.00 in gnome-firmware. Output of fwupd is as follows:

 

 

root@T490:/home/hen# service fwupd start

root@T490:/home/hen# fwupdmgr refresh --force

Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz

Downloading…             [***************************************]

Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.asc

 

Successfully downloaded new metadata: 3 local devices supported

root@T490:/home/hen# fwupdmgr update

• Thunderbolt Controller has no available firmware updates

• SAMSUNG MZVLB512HBJQ-000L7 has no available firmware updates

• System Firmware has the latest available firmware version

• UEFI Device Firmware has the latest available firmware version

• UEFI Device Firmware has the latest available firmware version

• UEFI Device Firmware has no available firmware updates

• UEFI Device Firmware has no available firmware updates

• UEFI Device Firmware has no available firmware updates

root@T490:/home/hen#

 

I found the specific update on fwupd.org/lvfs.

 

May I download the *.cap file and execute update like 'fwupdmgr install /path/to/file.cap [DEVICE-ID]' to get the update done?

 

Why fwupd does not find the update automatically? 

 

Thanks for your help!

Johann

 

 

 

More info from fwupd:

 

(after first firmware-update, I changed from Debina to Kubuntu – don't know, whether it does matter here)

 

root@T490:/home/hen# fwupdmgr get-history

No history

root@T490:/home/hen# fwupdmgr get-devices

20N3S02L00

├─Thunderbolt Controller:

│     Device ID:           407eb807d84d9f183eb58bd2948eb82be408e266

│     Summary:             Unmatched performance for high-speed I/O

│     Current version:     18.00

│     Vendor:              Lenovo (TBT:0x0109)

│     GUIDs:               10cc249a-9b30-5775-ad7f-59650a116059 ← TBT-01091804

│                          3e25bcc9-2a4b-50f9-bad3-e32cf6f7dafc ← TBT-01091804-controller0-0

│     Device Flags:        • Internal device

│                          • Updatable

│                          • Requires AC power

│                          • Device stages updates

│  

├─SAMSUNG MZVLB512HBJQ-000L7:

│     Device ID:           f2759da7fe8e0388c5f3601cb072f837b1070b03

│     Summary:             NVM Express Solid State Drive

│     Current version:     3L2QEXF7

│     Vendor:              Samsung Electronics Co Ltd (NVME:0x144D)

│     Serial Number:       S4ENNE0M405588

│     GUIDs:               6e54c992-d302-59ab-b454-2d26ddd63e6d ← NVME\VEN_144D&DEV_A808&REV_00

│                          47335265-a509-51f7-841e-1c94911af66b ← NVME\VEN_144D&DEV_A808

│                          f4ceb2a8-09c4-55c0-af2a-13ccd63925b1 ← SAMSUNG MZVLB512HBJQ-000L7

│     Device Flags:        • Internal device

│                          • Updatable

│                          • Requires AC power

│                          • Needs a reboot after installation

│                          • Device is usable for the duration of the update

│  

├─System Firmware:

│     Device ID:           6150dd1f7291b0709289ab8a53cc85a17e117ef2

│     Current version:     0.1.66

│     Minimum Version:     0.0.1

│     Vendor:              LENOVO (DMI:LENOVO)

│     GUID:                603baf73-b997-45b5-86b4-2f981a008e18

│     Device Flags:        • Internal device

│                          • Updatable

│                          • Requires AC power

│                          • Supported on remote server

│                          • Needs a reboot after installation

│                          • Cryptographic hash verification is available

│                          • Device is usable for the duration of the update

│  

├─UEFI Device Firmware:

│     Device ID:           b1c32d855d85a2124e865f0a03f8c2384dcca167

│     Current version:     192.47.1524

│     Minimum Version:     192.47.1524

│     Vendor:              DMI:LENOVO

│     GUID:                bf2d0f8b-f9a9-400c-8914-36c225d16eb4

│     Device Flags:        • Internal device

│                          • Updatable

│                          • Requires AC power

│                          • Supported on remote server

│                          • Needs a reboot after installation

│                          • Device is usable for the duration of the update

│  

├─UEFI Device Firmware:

│     Device ID:           489f23b2ba9c1adf3e9f9f10598c98ba5c6bba39

│     Current version:     0.1.19

│     Minimum Version:     0.1.19

│     Vendor:              DMI:LENOVO

│     GUID:                38ea6335-29ca-417b-8cd4-6b4e5e866f92

│     Device Flags:        • Internal device

│                          • Updatable

│                          • Requires AC power

│                          • Supported on remote server

│                          • Needs a reboot after installation

│                          • Device is usable for the duration of the update

│  

├─UEFI Device Firmware:

│     Device ID:           98a394c65d64ece8aae3126fb0f85364bb915b49

│     Current version:     1.1.16

│     Minimum Version:     0.0.1

│     Vendor:              DMI:LENOVO

│     GUID:                25dd5a7f-4151-401f-ae35-1440807c7bba

│     Device Flags:        • Internal device

│                          • Updatable

│                          • Requires AC power

│                          • Needs a reboot after installation

│                          • Device is usable for the duration of the update

│  

├─UEFI Device Firmware:

│     Device ID:           1d921cfee6793590bf19a4ad74a5039f0fbe28e5

│     Current version:     0.73.8

│     Minimum Version:     0.73.8

│     Vendor:              DMI:LENOVO

│     GUID:                0067661a-e24b-4927-ab57-596a472a8cc2

│     Device Flags:        • Internal device

│                          • Updatable

│                          • Requires AC power

│                          • Needs a reboot after installation

│                          • Device is usable for the duration of the update

│  

└─UEFI Device Firmware:

     Device ID:           720296b654bf23d974c282ad9cd59d0b9d33c971

     Current version:     0.0.26403

     Minimum Version:     0.0.1

     Vendor:              DMI:LENOVO

     GUID:                26aac102-e03d-4eb0-a663-9372614a765a

     Device Flags:        • Internal device

                          • Updatable

                          • Requires AC power

                          • Needs a reboot after installation

                          • Device is usable for the duration of the update

   

root@T490:/home/hen# fwupdmgr get-releases 407eb807d84d9f183eb58bd2948eb82be408e266

No releases found

root@T490:/home/hen#

 

 

 

(@staff why the hell you cant paste code here?)

 

Reply
Answer
Options

886 Posts

07-22-2019

Canada

538 Signins

6611 Page Views

  • Posts: 886
  • Registered: ‎07-22-2019
  • Location: Canada
  • Views: 6611

Re:critical thunderbold firmware update under Linux

2020-07-01, 2:36 AM

Hi @JESmh 
 

I confirmed with the firmware team that they haven't released the Assist mode firmware on LVFS which is why you're not seeing the update. Still tracking down exactly why it's not been released as it was done for other platforms

 

They did confirm that a workaround is to set the mode to Native mode in the BIOS, boot and do the update, and then go back to Assist mode. 

 

Hope that helps

Mark

Reply

Replies(8)
Options

886 Posts

07-22-2019

Canada

538 Signins

6611 Page Views

  • Posts: 886
  • Registered: ‎07-22-2019
  • Location: Canada
  • Views: 6611
  • Message 2 of 9

Re:critical thunderbold firmware update under Linux

2020-06-18, 19:07 PM

Hi @JESmh 

 

I don't know why it's not finding that firmware update. Which version of fwupd are you using? Can you make sure you're using the latest one? (I've used snaps to get the very latest previously if that helps)

 

I'll check with the firmware team for their input.

 

I have previously done firmware updates directly with the .cab but I have not tried it for the thunderbolt firmware so I don't know if it's recommended or not....

 

Mark

Reply
Options

5 Posts

06-17-2020

Germany

8 Signins

75 Page Views

  • Posts: 5
  • Registered: ‎06-17-2020
  • Location: Germany
  • Views: 75
  • Message 3 of 9

Re:critical thunderbold firmware update under Linux

2020-06-20, 21:54 PM
Hi Mark, thanks for your answer. fwupd: 1.3.9-4ubuntu0.1 as a dependency of fwupd-signed: 1.27.1ununtu1+1.3.9-4ubuntu0.1 both are up to date I will try as snap soon and report back here. Regards
Reply
Options

5 Posts

06-17-2020

Germany

8 Signins

75 Page Views

  • Posts: 5
  • Registered: ‎06-17-2020
  • Location: Germany
  • Views: 75
  • Message 4 of 9

Re:critical thunderbold firmware update under Linux

2020-06-26, 13:51 PM

Okay, I tried to use fwupd from snap repo, here the output:

 

 

root@T490:/home/hen# snap install --classic fwupd

Warnung: /snap/bin wurde nicht in »$PATH« gefunden. Wenn Sie die Sitzung seit der Installation von

        snapd nicht neu gestartet haben, versuchen Sie bitte dieses. Für weitere Einzelheiten:

        https://forum.snapcraft.io/t/9469.

 

fwupd 1.4.4 aus Richard Hughes installiert

root@T490:/home/hen# fwupdmgr get-devices

Unsupported daemon version 1.4.4, client version is 1.3.9

root@T490:/home/hen# fwupd.fwupdmgr get-devices

Befehl »fwupd.fwupdmgr« ist unter »/snap/bin/fwupd.fwupdmgr« verfügbar

Der Befehl konnte nicht gefunden werden, weil »/snap/bin« nicht Teil der Umgebungsvariable PATH ist.

fwupd.fwupdmgr: Befehl nicht gefunden.

root@T490:/home/hen# export PATH=$PATH:/snap/bin

root@T490:/home/hen# fwupd.fwupdmgr get-devices

20N3S02L00

├─Thunderbolt Controller:

│     Device ID:           407eb807d84d9f183eb58bd2948eb82be408e266

│     Summary:             Unmatched performance for high-speed I/O

│     Current version:     18.00

│     Vendor:              Lenovo (TBT:0x0109)

│     GUIDs:               10cc249a-9b30-5775-ad7f-59650a116059 ← TBT-01091804

│                          3e25bcc9-2a4b-50f9-bad3-e32cf6f7dafc ← TBT-01091804-controller0-0

│     Device Flags:        • Internal device

│                          • Updatable

│                          • Requires AC power

│                          • Device stages updates

 

[…]

 

root@T490:/home/hen# fwupd.fwupdmgr refresh --force

Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.jcat

Downloading…             [***************************************]

Fetching metadata https://cdn.fwupd.org/downloads/firmware-00649-stable.xml.gz

Downloading…             [***************************************]

Successfully downloaded new metadata: 0 local devices supported

root@T490:/home/hen# fwupd.fwupdmgr get-updates

2020/06/26 15:27:14.738242 cmd_run.go:923: WARNING: cannot copy user Xauthority file: Die Xauthority-Datei gehört nicht dem aktuellen Benutzer 0

• Thunderbolt Controller has no available firmware updates

• Embedded Controller has the latest available firmware version

• Intel Management Engine has the latest available firmware version

• SAMSUNG MZVLB512HBJQ-000L7 has no available firmware updates

• System Firmware has the latest available firmware version

• UEFI Device Firmware has no available firmware updates

• UEFI Device Firmware has no available firmware updates

• UEFI Device Firmware has no available firmware updates

root@T490:/home/hen#

 

 

I've seen to thinks: local devices supported, and the warning about the Xauthority file.

gnome-firmware window does not show flag "supported on LVFS"

 

I took a detailed look at the gnome-firmware window and noticed, that the flag "supported on LVFS" is missing for thunderbold and UEFI-devices (see screenshot). I think, it's using fwupd 1.3.9, snap version is 1.4.4, but does not work out of flow.

Reply
Options

886 Posts

07-22-2019

Canada

538 Signins

6611 Page Views

  • Posts: 886
  • Registered: ‎07-22-2019
  • Location: Canada
  • Views: 6611
  • Message 5 of 9

Re:critical thunderbold firmware update under Linux

2020-06-27, 23:40 PM

Hi @JESmh 

 

We're looking into this.

Basically as you've noted your GUID is different than the one the firmware on LVFS has.  I think it's because you have TBT BIOS assist mode enabled.

 

Will update when I hear back from the BIOS team. For the P52s we released two different firmware's to LVFS so that may be the solution. If you don't need BIOS assist mode then I'm guessing if you disable that you'll then be able to update - but I don't know if there are any consequences from doing that so would like to hear back from the FW team before I recommend it.

 

Apologies on the fwupd version - that was not responsible

 

Mark

Reply
Options

5 Posts

06-17-2020

Germany

8 Signins

75 Page Views

  • Posts: 5
  • Registered: ‎06-17-2020
  • Location: Germany
  • Views: 75
  • Message 6 of 9

Re:critical thunderbold firmware update under Linux

2020-06-28, 10:00 AM

Hi Mark,

 

I can confirm, I have TBT BIOS assist mode enabled currently.

 

trying to find info about TBT BIOS assist mode, I found a post where you explain necessity of this mode just to Kernel versions prior to 4.19. My actual Kernel version is 5.4.0 using Kubuntu 20.04, so there should be no disadvantages on disabling this feature.

 

Nevertheless I'll wait for your response from team consultation.

Reply
Answer
Options

886 Posts

07-22-2019

Canada

538 Signins

6611 Page Views

  • Posts: 886
  • Registered: ‎07-22-2019
  • Location: Canada
  • Views: 6611
  • Message 7 of 9

Re:critical thunderbold firmware update under Linux

2020-07-01, 2:36 AM

Hi @JESmh 
 

I confirmed with the firmware team that they haven't released the Assist mode firmware on LVFS which is why you're not seeing the update. Still tracking down exactly why it's not been released as it was done for other platforms

 

They did confirm that a workaround is to set the mode to Native mode in the BIOS, boot and do the update, and then go back to Assist mode. 

 

Hope that helps

Mark

0 person found this solution to be helpful.

This helped me too

Reply
Options

5 Posts

06-17-2020

Germany

8 Signins

75 Page Views

  • Posts: 5
  • Registered: ‎06-17-2020
  • Location: Germany
  • Views: 75
  • Message 8 of 9

Re:critical thunderbold firmware update under Linux

2020-07-02, 21:07 PM

Hi @MarkRHPearson,

 

thank you for your answer! That helps me. 

As I understood now the relations around the assist mode, I can leave it switched off.

 

But to stay clear here, I want to ask one last question: When I understood you right, updating the firmware in the one or the other mode, does update full firmware, regardless of the mode I'm using it later on (e.g.

update firmware while assist mode=on does update for both modes, on and off as 

update firmware while assist mode=off does update for both modes too)?

 

This answer should help @mohr24 too.

Reply
Options

886 Posts

07-22-2019

Canada

538 Signins

6611 Page Views

  • Posts: 886
  • Registered: ‎07-22-2019
  • Location: Canada
  • Views: 6611
  • Message 9 of 9

Re:critical thunderbold firmware update under Linux

2020-07-04, 2:19 AM

Hi @JESmh 

 

Yes - that's my understanding and what I was told. Full disclosure - I've not tried it myself yet (mostly because I don't have a T490) :) 

 

If you hit any problems let me know ASAP but fingers crossed it's smooth sailing. 

 

Mark

Reply
Forum Home

Community Guidelines

Please review our Guidelines before posting.

Learn More

Check out current deals!

Go Shop
X

Save

X

Delete

X

No, I don’t want to share ideas Yes, I agree to these terms