Firmware updates not appearing?

285 views
Skip to first unread message

Erinn Looney-Triggs

unread,
Apr 27, 2018, 1:30:08 PM4/27/18
to fwupd
First, thanks for this piece of software, huge fan, much needed especially if it can get into Dell servers, keeping up with firmware updates there is insane.

Second, well, as a brand new end user coming in I am pretty confused on how to use this thing:

I am running F28 workstation on a Dell XPS 9550, the daemon appears to be running, your page here: https://fwupd.org/users indicates I should just be able to pop into the gnome software center and I'll be notified of updates, nothing showed up (fair enough I thought, maybe there is nothing to update).

However, looking here: https://fwupd.org/lvfs/device/124c207d-5db8-4d95-bd31-34fd971b34f9 I see a newer BIOS has been uploaded than I have ( newer is version 1.7.0) so I dig deeper:

fwupdmgr get-devices

XPS 15 9550 System Firmware
 DeviceId:             2da31270d317b076424992de14a0f08ae373c137
 Guid:                 124c207d-5db8-4d95-bd31-34fd971b34f9
 Plugin:               uefi
 Flags:                internal|updatable|require-ac|supported|registered|needs
-reboot
 Version:              0.1.6.1
 VersionLowest:        0.1.6.1
 Icon:                 computer
 Created:              2018-04-27

Ok, so it is detecting the BIOS correctly (UEFI... whatever you want to call it). And I see a handy command: 

fwupdmgr get-updates

ignoring 5ab1e5b4c5e2639722437a5b7c5a8391c75fcabe [XPS 15 9550 TPM 1.2] as not u
pdatable
Not compatible with fwupd version: failed predicate [(null) (null) 1.0.6]
XPS 15 9550 Thunderbolt Controller has firmware updates:
GUID:                    c2ca983d-a03d-56c6-80c4-fbb38d829f50
ID:                      com.dell.tbtc2ca983d.firmware
Update Version:          16.00
Update Name:             Thunderbolt NVM for Xps Notebook 9550
Update Summary:          Xps Notebook 9550
Update Remote ID:        lvfs
Update Checksum:         SHA1(62b734f69f93568faa929e16f860f4e7219d72eb)
Update Location:         https://fwupd.org/downloads/75984aeb95d33ed7fab857b18b2
8ffe317cb870d-8FDJ2_NVM16.00.cab

Ok getting really confused now, I know the BIOS is out of date according to the website, software center indicates no updates, yet there appears to be an update? Is Fedora running it's own repo for this and it is out of date?

I think a little expansion in documentation on the end users page could go a long ways, but can someone explain what is going on above? Why isn't it detecting the BIOS update? Why is the software center not showing me the thunderbolt update? Am I just doing all of this wrong?

Again, really appreciate the work, not knocking it here at all, just trying to use it.

-Erinn

Mario.Li...@dell.com

unread,
Apr 27, 2018, 1:51:17 PM4/27/18
to erinn.loo...@gmail.com, fw...@googlegroups.com

Erinn,

 

A few thoughts.

  1. Gnome Software will only offer some updates if power is plugged in.  Is power plugged in when you checked?
  2. Did you configure gnome-software to not run at boot up in some way?  It should normally run in the background and refresh metadata on it’s own.

 

Now to unpack what you see below.

 

  • ignoring 5ab1e5b4c5e2639722437a5b7c5a8391c75fcabe [XPS 15 9550 TPM 1.2] as not updatable

This is expected, no updates for your TPM right now.

 

  • Not compatible with fwupd version: failed predicate [(null) (null) 1.0.6]

This is probably some device that you have on the system that’s incompatible with your particular fwupd version.

Do you have anything plugged in?  If not, then I’m a little worried that this might be the reason UEFI updates aren’t being offered.

 

  • XPS 15 9550 Thunderbolt Controller has firmware updates:

This is showing an update for your Thunderbolt controller (which is updated separately from the UEFI BIOS)

 

So for figuring out what’s going on:

  1. I guess lets start with what fwupd version do you have on F28?  1.0.6?  From dnf?
  2. Can you please share your `fwupdmgr hwids` output?
    1. This firmware is only supposed to install on e7eb42e2-06c6-5185-9c5f-33ff1dbb1c0b and d98dc575-9143-5a8f-a620-9440ef640c8d

 

  1. Try to manually run the following flow.

# fwupdmgr refresh

# fwupdmgr update

If that worked then there is probably something wrong in gnome-software not refreshing properly.

 

If it didn’t update please share all the output from these.

# fwupdmgr get-updates

# fwupdmgr get-devices

 

Thanks,

 

--
You received this message because you are subscribed to the Google Groups "fwupd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fwupd+un...@googlegroups.com.
To post to this group, send email to fw...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/fwupd/e61af4a8-e0d5-4d2e-b33c-13dc03ace817%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Mario.Li...@dell.com

unread,
Apr 27, 2018, 2:09:29 PM4/27/18
to erinn.loo...@gmail.com, fw...@googlegroups.com, hugh...@gmail.com

Erinn,

 

  • I run KDE normally, so I simply opened gnome-software, I would assume (since it sort of implies it is updating on opening) that it updated to the latest metadata.

I’m not sure if that’s how it works, but I would expect the same on that behavior.  Maybe Richard can confirm.

 

According to your HWID output this is matching

{e7eb42e2-06c6-5185-9c5f-33ff1dbb1c0b}   <- Manufacturer + ProductName

To the HWID listed in the metadata.

 

  • Not compatible with fwupd version: failed predicate [(null) (null) 1.0.6]

So I’m actually quite worried about this now.  Here’s where this error matches:

https://github.com/hughsie/fwupd/blob/1.0.6/src/fu-engine.c#L971

 

There is no version requirement in the LVFS metadata though (see the requires block).

  <component type="firmware">

    <id>com.dell.uefi124c207d.firmware</id>

   <requires>

      <firmware compare="regex" version="">vendor-id</firmware>

      <firmware>bootloader</firmware>

      <firmware>firmware</firmware>

      <id>org.freedesktop.fwupd</id>

      <hardware>e7eb42e2-06c6-5185-9c5f-33ff1dbb1c0b</hardware>

      <hardware>d98dc575-9143-5a8f-a620-9440ef640c8d</hardware>

    </requires>

    <name>XPS 15 9550/Precision 5510 System Update</name>

    <summary>Firmware for the Dell XPS 15 9550/Precision 5510</summary>

    <developer_name>Dell Inc.</developer_name>

    <description><p>Updating the system firmware improves performance.</p></description>

    <project_license>proprietary</project_license>

    <url type="homepage">http://support.dell.com/</url>

    <releases>

      <release timestamp="1519399999" urgency="medium" version="67328">

        <location>https://fwupd.org/downloads/493cb1217b0a4654bb63b8fdf423a8740d81029c-firmware_XPS9550_Precision5510_1.7.0.wu.cab</location>

        <checksum type="sha1" filename="493cb1217b0a4654bb63b8fdf423a8740d81029c-firmware_XPS9550_Precision5510_1.7.0.wu.cab" target="container">d36fddc85bdb60b86b129f90dfbd7aabe460d0e7</checksum>

        <checksum type="sha1" filename="firmware.bin" target="content">64392da05f465df3e41c82e67a92be94887c3fdc</checksum>

        <description><p>Enhancements:

      1. Improved the stability for the file transferring within pre-OS USB LAN connection

      2. Improved keyboard typing experience with high WPM</p></description>

        <size type="installed">10175459</size>

        <size type="download">9901518</size>

      </release>

      <release timestamp="1513035510" version="67073">

        <location>https://fwupd.org/downloads/8fdb183327dbae1a3179c2c38e001357fe517fac-Signed_1152921504627258619.cab</location>

        <checksum type="sha1" filename="8fdb183327dbae1a3179c2c38e001357fe517fac-Signed_1152921504627258619.cab" target="container">eb75ef78cb98e79f5be91f31b700b2370e031ea3</checksum>

        <checksum type="sha1" filename="firmware.bin" target="content">fc8e0673b871438a3c8e9c9beee91f55d1eee351</checksum>

        <size type="installed">10170614</size>

        <size type="download">9897355</size>

      </release>

      <release timestamp="1508251664" version="66817">

        <location>https://fwupd.org/downloads/dada11c9c82c229d9b6e745aa2ab887455ee39be-Signed_1152921504627396094.cab</location>

        <checksum type="sha1" filename="dada11c9c82c229d9b6e745aa2ab887455ee39be-Signed_1152921504627396094.cab" target="container">36864043452c3f4065608770954c798fdc36fbc3</checksum>

        <checksum type="sha1" filename="firmware.bin" target="content">70b608f1a92870321f739e6234cdf0d57d3a1dda</checksum>

        <size type="installed">9812732</size>

        <size type="download">9540922</size>

      </release>

    </releases>

    <provides>

      <firmware type="flashed">124c207d-5db8-4d95-bd31-34fd971b34f9</firmware>

    </provides>

  </component>

 

 

@Richard Hughes, I think LVFS shouldn’t be setting <id> unless there is a version in that block should it?

LVFS metadata generation bug?

 

From: Erinn Looney-Triggs [mailto:erinn.loo...@gmail.com]
Sent: Friday, April 27, 2018 1:00 PM
To: Limonciello, Mario; fw...@googlegroups.com
Subject: Re: [fwupd] Firmware updates not appearing?

 

Thanks for the fast response, I'll put replies inline below.

 

On 04/27/2018 11:51 AM, Mario.Li...@dell.com wrote:

Erinn,

 

A few thoughts.

  1. Gnome Software will only offer some updates if power is plugged in.  Is power plugged in when you checked?

Yes power is plugged in.

  1.  
  2. Did you configure gnome-software to not run at boot up in some way?  It should normally run in the background and refresh metadata on it’s own.

I run KDE normally, so I simply opened gnome-software, I would assume (since it sort of implies it is updating on opening) that it updated to the latest metadata.

  1.  

 

Now to unpack what you see below.

 

  • ignoring 5ab1e5b4c5e2639722437a5b7c5a8391c75fcabe [XPS 15 9550 TPM 1.2] as not updatable

This is expected, no updates for your TPM right now.

 

  • Not compatible with fwupd version: failed predicate [(null) (null) 1.0.6]

This is probably some device that you have on the system that’s incompatible with your particular fwupd version.

Do you have anything plugged in?  If not, then I’m a little worried that this might be the reason UEFI updates aren’t being offered.

I have nothing extra plugged in to the system (other than the power cord as mentioned), this is a stock standard XPS 15 9550.

 

  • XPS 15 9550 Thunderbolt Controller has firmware updates:

This is showing an update for your Thunderbolt controller (which is updated separately from the UEFI BIOS)

Yeah that I understand, just don't know why it didn't show up in the software center.

 

So for figuring out what’s going on:

  1. I guess lets start with what fwupd version do you have on F28?  1.0.6?  From dnf?

fwupd-1.0.6-1.fc28.x86_64 from dnf, nothing exciting going on here, stock standard.

  1.  
  2. Can you please share your `fwupdmgr hwids` output?
    1. This firmware is only supposed to install on e7eb42e2-06c6-5185-9c5f-33ff1dbb1c0b and d98dc575-9143-5a8f-a620-9440ef640c8d

Here you go:
Computer Information
--------------------
BiosVendor: Dell Inc.
BiosVersion: 1.6.1
BiosMajorRelease: 1
BiosMinorRelease: 6
Manufacturer: Dell Inc.
Family: To be filled by O.E.M.
ProductName: XPS 15 9550
ProductSku: 6E4
EnclosureKind: 9
BaseboardManufacturer: Dell Inc.
BaseboardProduct: Y9N5X

Hardware IDs
------------
{02426a34-0cf2-5b6a-b8c7-399e522b5695}   <- Manufacturer + Family + ProductName + ProductSku + BiosVendor + BiosVersion + BiosMajorRelease + BiosMinorRelease
{caa30c69-0992-515d-aa52-ea69e8d21ea0}   <- Manufacturer + Family + ProductName + BiosVendor + BiosVersion + BiosMajorRelease + BiosMinorRelease
{cd27e382-ec91-561b-a07c-7567e2d9be4a}   <- Manufacturer + ProductName + BiosVendor + BiosVersion + BiosMajorRelease + BiosMinorRelease
{f8aedd40-45c9-5257-99d2-4bff347b9e35}   <- Manufacturer + Family + ProductName + ProductSku + BaseboardManufacturer + BaseboardProduct
{da933d9a-7fef-5f0f-a6c1-651b456dabfc}   <- Manufacturer + Family + ProductName + ProductSku
{4bb1d123-604a-5d15-9a33-34420beb3128}   <- Manufacturer + Family + ProductName
{b3a33db4-7fd9-5a12-818e-375559abf660}   <- Manufacturer + ProductSku + BaseboardManufacturer + BaseboardProduct
{6e9d152f-c527-5443-bcc8-ef11c1ecbcf4}   <- Manufacturer + ProductSku
{2a3d1894-e364-5b5c-81d3-5c0b7a3be768}   <- Manufacturer + ProductName + BaseboardManufacturer + BaseboardProduct
{e7eb42e2-06c6-5185-9c5f-33ff1dbb1c0b}   <- Manufacturer + ProductName
{990d0202-e897-5c36-a57b-3deea1c86733}   <- Manufacturer + Family + BaseboardManufacturer + BaseboardProduct
{6e42ac8b-4502-5b9a-a1e0-0f91b0b639bd}   <- Manufacturer + Family
{29ca4080-4d68-5395-afe2-35fa9a4f13bf}   <- Manufacturer + EnclosureKind
{9589c6d4-86aa-5e19-8682-50bdb3753f87}   <- Manufacturer + BaseboardManufacturer + BaseboardProduct
{85d38fda-fc0e-5c6f-808f-076984ae7978}   <- Manufacturer


  1.  
    1.  

 

  1. Try to manually run the following flow.

# fwupdmgr refresh

# fwupdmgr update

If that worked then there is probably something wrong in gnome-software not refreshing properly.

Done, same output:
sudo fwupdmgr update


ignoring 5ab1e5b4c5e2639722437a5b7c5a8391c75fcabe [XPS 15 9550 TPM 1.2] as not updatable

Not compatible with fwupd version: failed predicate [(null) (null) 1.0.6]

No upgrades for XPS 15 9550 Thunderbolt Controller, current is 16.00: 16.00=same

 

If it didn’t update please share all the output from these.

# fwupdmgr get-updates

sudo fwupdmgr get-updates


ignoring 5ab1e5b4c5e2639722437a5b7c5a8391c75fcabe [XPS 15 9550 TPM 1.2] as not updatable

Not compatible with fwupd version: failed predicate [(null) (null) 1.0.6]

No upgrades for XPS 15 9550 Thunderbolt Controller, current is 16.00: 16.00=same

# fwupdmgr get-devices

sudo fwupdmgr get-devices
Intel AMT [unprovisioned]
  DeviceId:             088df415cdee883ec89563e41e6d495924250174
  Guid:                 2800f812-b7b4-2d4b-aca8-46e0ff65814c
  Summary:              Hardware and firmware technology for remote out-of-band management
  Plugin:               amt
  Flags:                internal|registered
  Vendor:               Intel Corporation
  Version:              11.8.50
  VersionBootloader:    11.8.50
  Icon:                 computer
  Created:              2018-04-27



XPS 15 9550 TPM 1.2

  DeviceId:             5ab1e5b4c5e2639722437a5b7c5a8391c75fcabe
  Guid:                 9055a777-a92f-55da-8d34-6614d8f9df92
  Summary:              Platform TPM device
  Plugin:               dell
  Flags:                internal|require-ac|supported|registered
  Vendor:               Dell Inc.
  Version:              5.81.0.0
  Icon:                 computer
  Created:              2018-04-27

XPS 15 9550 TPM 2.0
  DeviceId:             04d075f2971403e31c1dbdf3b38f709d7c2e749d
  Guid:                 75305a8e-596f-5a3b-9aea-ebee36dc585e
  Summary:              Alternate mode for platform TPM device
  Plugin:               dell
  Flags:                internal|require-ac|locked|registered
  Icon:                 computer
  Created:              2018-04-27



XPS 15 9550 System Firmware
  DeviceId:             2da31270d317b076424992de14a0f08ae373c137
  Guid:                 124c207d-5db8-4d95-bd31-34fd971b34f9
  Plugin:               uefi
  Flags:                internal|updatable|require-ac|supported|registered|needs-reboot
  Version:              0.1.6.1
  VersionLowest:        0.1.6.1
  Icon:                 computer
  Created:              2018-04-27

BCM2045A0
  DeviceId:             809dae5e935a4d7ccce2462d22cdd4416768cb0d
  Guid:                 f8498646-6724-5f55-9806-57b3f8636ad8
  Guid:                 35fd074d-7c78-599e-b37a-88931c63ba01
  Plugin:               dfu
  Flags:                updatable|registered
  Vendor:               Broadcom Corp
  VendorId:             USB:0x0A5C
  Version:              1.12
  Icon:                 drive-harddisk-usb
  Created:              2018-04-27

GM107M [GeForce GTX 960M]
  DeviceId:             3f0f51a4f03bccdad9f8ae1334bad4584b5ba875
  Guid:                 520d05a3-ece8-519e-88de-0755806314f4
  Plugin:               udev
  Flags:                internal|registered
  Vendor:               NVIDIA Corporation
  VendorId:             PCI:0x10DE
  Icon:                 audio-card
  Created:              2018-04-27

HD Graphics 530
  DeviceId:             8de6c7959053fd5798006dcc63590d33fa5e51cb
  Guid:                 8ec3e242-65bd-58ee-9c5e-b28f1e32e7ae
  Plugin:               udev
  Flags:                internal|registered
  Vendor:               Intel Corporation
  VendorId:             PCI:0x8086
  Icon:                 audio-card
  Created:              2018-04-27



XPS 15 9550 Thunderbolt Controller

  DeviceId:             24af7a654c1c03a8f4870f6f34556bf422e837f9
  Guid:                 c2ca983d-a03d-56c6-80c4-fbb38d829f50
  Summary:              Unmatched performance for high-speed I/O
  Plugin:               thunderbolt
  Flags:                internal|updatable|supported|registered
  Vendor:               Dell
  VendorId:             TBT:0x00D4
  Version:              16.00
  Icon:                 computer
  Created:              2018-04-27
  Modified:             2018-04-27
  UpdateState:          success


Richard Hughes

unread,
Apr 27, 2018, 2:42:36 PM4/27/18
to Mario Limonciello, erinn.loo...@gmail.com, fwupd
On 27 April 2018 at 19:09, <Mario.Li...@dell.com> wrote:
> I run KDE normally, so I simply opened gnome-software, I would assume (since
> it sort of implies it is updating on opening) that it updated to the latest
> metadata.

No, you need to click the refresh button in the updates panel. At
startup gnome-software downloads everything it needs to *start* but
not all the package or firmware updates themselves. If you run GNOME
this is all done in the background. GNOME Software only shows the
firmware as an update when it's been downloaded and checked.

> Not compatible with fwupd version: failed predicate [(null) (null) 1.0.6]

This is very odd, I've not seen that before.

> @Richard Hughes, I think LVFS shouldn’t be setting <id> unless there is a
> version in that block should it?

It should be using <id>, every component needs an <id> to be valid.

> LVFS metadata generation bug?

No.

I've reworked how the requirements are handled in git master recently
to be a bit more robust; is there any chance you can try the build
here and tell me if it fixes the issue?
https://people.freedesktop.org/~hughsient/fedora/28/

Richard

Mario.Li...@dell.com

unread,
Apr 27, 2018, 2:45:28 PM4/27/18
to hugh...@gmail.com, erinn.loo...@gmail.com, fw...@googlegroups.com

> -----Original Message-----
> From: Richard Hughes [mailto:hugh...@gmail.com]
> Sent: Friday, April 27, 2018 1:43 PM
> To: Limonciello, Mario
> Cc: erinn.loo...@gmail.com; fwupd
> Subject: Re: [fwupd] Firmware updates not appearing?
>
> On 27 April 2018 at 19:09, <Mario.Li...@dell.com> wrote:
> > I run KDE normally, so I simply opened gnome-software, I would assume (since
> > it sort of implies it is updating on opening) that it updated to the latest
> > metadata.
>
> No, you need to click the refresh button in the updates panel. At
> startup gnome-software downloads everything it needs to *start* but
> not all the package or firmware updates themselves. If you run GNOME
> this is all done in the background. GNOME Software only shows the
> firmware as an update when it's been downloaded and checked.
>
> > Not compatible with fwupd version: failed predicate [(null) (null) 1.0.6]
>
> This is very odd, I've not seen that before.
>
> > @Richard Hughes, I think LVFS shouldn’t be setting <id> unless there is a
> > version in that block should it?
>
> It should be using <id>, every component needs an <id> to be valid.
>
> > LVFS metadata generation bug?
>
> No.

Not the component ID, the requires ID. Does the requires need an ID
when it's not setting a version for requirement?
Eg this:
<id>org.freedesktop.fwupd</id>

Erinn Looney-Triggs

unread,
Apr 27, 2018, 2:46:01 PM4/27/18
to Mario.Li...@dell.com, fw...@googlegroups.com

Thanks for the fast response, I'll put replies inline below.


On 04/27/2018 11:51 AM, Mario.Li...@dell.com wrote:

Erinn,

 

A few thoughts.

  1. Gnome Software will only offer some updates if power is plugged in.  Is power plugged in when you checked?
Yes power is plugged in.

  1. Did you configure gnome-software to not run at boot up in some way?  It should normally run in the background and refresh metadata on it’s own.
    I run KDE normally, so I simply opened gnome-software, I would assume (since it sort of implies it is updating on opening) that it updated to the latest metadata.

     

    Now to unpack what you see below.

     

    • ignoring 5ab1e5b4c5e2639722437a5b7c5a8391c75fcabe [XPS 15 9550 TPM 1.2] as not updatable

    This is expected, no updates for your TPM right now.

     

    • Not compatible with fwupd version: failed predicate [(null) (null) 1.0.6]

    This is probably some device that you have on the system that’s incompatible with your particular fwupd version.

    Do you have anything plugged in?  If not, then I’m a little worried that this might be the reason UEFI updates aren’t being offered.

    I have nothing extra plugged in to the system (other than the power cord as mentioned), this is a stock standard XPS 15 9550.

     

    • XPS 15 9550 Thunderbolt Controller has firmware updates:

    This is showing an update for your Thunderbolt controller (which is updated separately from the UEFI BIOS)

    Yeah that I understand, just don't know why it didn't show up in the software center.

     

    So for figuring out what’s going on:

    1. I guess lets start with what fwupd version do you have on F28?  1.0.6?  From dnf?
    fwupd-1.0.6-1.fc28.x86_64 from dnf, nothing exciting going on here, stock standard.

    1. Can you please share your `fwupdmgr hwids` output?
      1. This firmware is only supposed to install on e7eb42e2-06c6-5185-9c5f-33ff1dbb1c0b and d98dc575-9143-5a8f-a620-9440ef640c8d
      Here you go:

       

      1. Try to manually run the following flow.

      # fwupdmgr refresh

      # fwupdmgr update

      If that worked then there is probably something wrong in gnome-software not refreshing properly.

      Done, same output:
      sudo fwupdmgr update

      ignoring 5ab1e5b4c5e2639722437a5b7c5a8391c75fcabe [XPS 15 9550 TPM 1.2] as not updatable
      Not compatible with fwupd version: failed predicate [(null) (null) 1.0.6]
      No upgrades for XPS 15 9550 Thunderbolt Controller, current is 16.00: 16.00=same

       

      If it didn’t update please share all the output from these.

      # fwupdmgr get-updates

      sudo fwupdmgr get-updates

      ignoring 5ab1e5b4c5e2639722437a5b7c5a8391c75fcabe [XPS 15 9550 TPM 1.2] as not updatable
      Not compatible with fwupd version: failed predicate [(null) (null) 1.0.6]
      No upgrades for XPS 15 9550 Thunderbolt Controller, current is 16.00: 16.00=same

      # fwupdmgr get-devices

      sudo fwupdmgr get-devices
      Intel AMT [unprovisioned]
        DeviceId:             088df415cdee883ec89563e41e6d495924250174
        Guid:                 2800f812-b7b4-2d4b-aca8-46e0ff65814c
        Summary:              Hardware and firmware technology for remote out-of-band management
        Plugin:               amt
        Flags:                internal|registered
        Vendor:               Intel Corporation
        Version:              11.8.50
        VersionBootloader:    11.8.50
        Icon:                 computer
        Created:              2018-04-27

      XPS 15 9550 TPM 1.2
        DeviceId:             5ab1e5b4c5e2639722437a5b7c5a8391c75fcabe
        Guid:                 9055a777-a92f-55da-8d34-6614d8f9df92
        Summary:              Platform TPM device
        Plugin:               dell
        Flags:                internal|require-ac|supported|registered
        Vendor:               Dell Inc.
        Version:              5.81.0.0
        Icon:                 computer
        Created:              2018-04-27

      XPS 15 9550 TPM 2.0
        DeviceId:             04d075f2971403e31c1dbdf3b38f709d7c2e749d
        Guid:                 75305a8e-596f-5a3b-9aea-ebee36dc585e
        Summary:              Alternate mode for platform TPM device
        Plugin:               dell
        Flags:                internal|require-ac|locked|registered
        Icon:                 computer
        Created:              2018-04-27

      XPS 15 9550 System Firmware
        DeviceId:             2da31270d317b076424992de14a0f08ae373c137
        Guid:                 124c207d-5db8-4d95-bd31-34fd971b34f9
        Plugin:               uefi
        Flags:                internal|updatable|require-ac|supported|registered|needs-reboot
        Version:              0.1.6.1
        VersionLowest:        0.1.6.1
        Icon:                 computer
        Created:              2018-04-27

      XPS 15 9550 Thunderbolt Controller
        DeviceId:             24af7a654c1c03a8f4870f6f34556bf422e837f9
        Guid:                 c2ca983d-a03d-56c6-80c4-fbb38d829f50
        Summary:              Unmatched performance for high-speed I/O
        Plugin:               thunderbolt
        Flags:                internal|updatable|supported|registered
        Vendor:               Dell
        VendorId:             TBT:0x00D4
        Version:              16.00
        Icon:                 computer
        Created:              2018-04-27
        Modified:             2018-04-27
        UpdateState:          success

       

      Thanks,

      Mario.Li...@dell.com

      unread,
      Apr 27, 2018, 3:29:35 PM4/27/18
      to hugh...@gmail.com, erinn.loo...@gmail.com, fw...@googlegroups.com
      Oh I think it actually is supposed to be that when a hardware ID gets used
      that there should have been a minimum version of fwupd set by LVFS
      (1.0.1 IIRC).

      Since no version is set but the tag is set it's confusing fwupd.

      Richard Hughes

      unread,
      Apr 27, 2018, 4:18:00 PM4/27/18
      to Mario Limonciello, erinn.loo...@gmail.com, fwupd
      On 27 April 2018 at 20:29, <Mario.Li...@dell.com> wrote:
      > Since no version is set but the tag is set it's confusing fwupd.

      Concur. I don't know why it's just affecting
      com.dell.uefi124c207d.firmware -- I'm debugging now.

      Richard.

      Erinn Looney-Triggs

      unread,
      Apr 27, 2018, 4:26:30 PM4/27/18
      to Mario.Li...@dell.com, hugh...@gmail.com, fw...@googlegroups.com
      Can't (easily) do the upgrade:

       Problem 1: cannot install the best update candidate for package
      fwupd-1.0.6-1.fc28.x86_64
        - nothing provides libfwup.so.1(libfwup.so.1)(64bit) needed by
      fwupd-1.0.7-0.392.20180427git.fc28.x86_64
       Problem 2: package gnome-software-3.28.1-1.fc28.x86_64 requires
      fwupd(x86-64) >= 1.0.3, but none of the providers can be installed
        - package fwupd-1.0.6-1.fc28.x86_64 requires fwupd-labels =
      1.0.6-1.fc28, but none of the providers can be installed
        - cannot install both
      fwupd-labels-1.0.7-0.392.20180427git.fc28.x86_64 and
      fwupd-labels-1.0.6-1.fc28.x86_64
        - cannot install the best update candidate for package
      gnome-software-3.28.1-1.fc28.x86_64
        - cannot install the best update candidate for package
      fwupd-labels-1.0.6-1.fc28.x86_64
        - nothing provides libfwup.so.1(libfwup.so.1)(64bit) needed by
      fwupd-1.0.7-0.392.20180427git.fc28.x86_64

      -Erinn

      Richard Hughes

      unread,
      Apr 27, 2018, 4:35:57 PM4/27/18
      to Mario Limonciello, erinn.loo...@gmail.com, fwupd
      On 27 April 2018 at 21:17, Richard Hughes <hugh...@gmail.com> wrote:
      > Concur. I don't know why it's just affecting
      > com.dell.uefi124c207d.firmware -- I'm debugging now.

      It would appear this firmware was uploaded after requirement adding
      was added to the LVFS, but before the fix that makes an "any"
      requirement get deleted:
      https://github.com/hughsie/lvfs-website/blob/master/app/views_component.py#L145

      I've manually deleted the requirement (this was the only firmware
      affected), regenerated the metadata and purged the CDN. Erinn, sorry
      for misreading the <id> thing -- could you try again for me now? You
      can use the existing fwupd version without having to update to the new
      one.

      Richard

      Erinn Looney-Triggs

      unread,
      Apr 28, 2018, 1:20:16 AM4/28/18
      to Richard Hughes, Mario Limonciello, fwupd
      Did a refresh and now I get this:

      fwupdmgr get-updates
      ignoring 5ab1e5b4c5e2639722437a5b7c5a8391c75fcabe [XPS 15 9550 TPM 1.2]
      as not updatable
      no HWIDs matched d98dc575-9143-5a8f-a620-9440ef640c8d

      So still no update listed for the BIOS, but less errors :).

      -Erinn

      Richard Hughes

      unread,
      Apr 29, 2018, 3:07:43 PM4/29/18
      to Erinn Looney-Triggs, Mario Limonciello, fwupd
      On 27 April 2018 at 22:10, Erinn Looney-Triggs
      <erinn.loo...@gmail.com> wrote:
      > no HWIDs matched d98dc575-9143-5a8f-a620-9440ef640c8d

      So that's failing the check for a specific model of hardware. Perhaps
      Mario can fill us in on why that specific firmware matches only on
      specific hwids?

      Richard.

      Mario.Li...@dell.com

      unread,
      Apr 30, 2018, 10:18:44 AM4/30/18
      to hugh...@gmail.com, erinn.loo...@gmail.com, fw...@googlegroups.com
      > -----Original Message-----
      > From: Richard Hughes [mailto:hugh...@gmail.com]
      > Sent: Sunday, April 29, 2018 2:08 PM
      > To: Erinn Looney-Triggs
      > Cc: Limonciello, Mario; fwupd
      > Subject: Re: [fwupd] Firmware updates not appearing?
      >
      That firmware matches upon two HWID's for the two different models
      it can be installed upon (XPS 9550 and Precision 5510).

      Snipped from the LVFS metadata:
      <hardware>e7eb42e2-06c6-5185-9c5f-33ff1dbb1c0b</hardware>
      <hardware>d98dc575-9143-5a8f-a620-9440ef640c8d</hardware>

      This also matches Erinn's reported hwid (From an earlier email):
      {e7eb42e2-06c6-5185-9c5f-33ff1dbb1c0b} <- Manufacturer + ProductName

      I am suspecting this to be a bug in the implementation on fwupd's HWIDs
      check (or at least the understanding as they are used on LVFS).

      Currently fwupd will walk through each requirement and see if it meets
      requirements. Since there are two HWIDs listed it has to meet "both"
      HWIDs to pass. Instead it should be checking if "either" of the HWIDs
      matched.


      Richard Hughes

      unread,
      Apr 30, 2018, 10:32:51 AM4/30/18
      to Mario Limonciello, Erinn Looney-Triggs, fwupd
      On 30 April 2018 at 15:18, <Mario.Li...@dell.com> wrote:
      > I am suspecting this to be a bug in the implementation on fwupd's HWIDs
      > check (or at least the understanding as they are used on LVFS).

      The HWID requirements are processed as AND rather than OR. If we want
      the OR behaviour then we need to use a single requirement and a regex.
      I agree the LVFS interface doesn't actually give any guidance here. If
      you file it, I'll fix it.

      Richard.

      Mario.Li...@dell.com

      unread,
      Apr 30, 2018, 10:40:26 AM4/30/18
      to hugh...@gmail.com, erinn.loo...@gmail.com, fw...@googlegroups.com
      > -----Original Message-----
      > From: Richard Hughes [mailto:hugh...@gmail.com]
      > Sent: Monday, April 30, 2018 9:33 AM
      > To: Limonciello, Mario
      > Cc: Erinn Looney-Triggs; fwupd
      > Subject: Re: [fwupd] Firmware updates not appearing?
      >
      OK: https://github.com/hughsie/lvfs-website/issues/110

      Can you manually remove or adjust those HWIDs to regex for now for this one
      so Erinn can update?

      Richard Hughes

      unread,
      May 1, 2018, 7:40:13 AM5/1/18
      to Mario Limonciello, Erinn Looney-Triggs, fwupd
      On 30 April 2018 at 15:38, <Mario.Li...@dell.com> wrote:
      > Can you manually remove or adjust those HWIDs to regex for now for this one
      > so Erinn can update?

      No easily, but I did create two PRs (fwupd and LVFS) to fix this like
      you suggested.

      Richard.

      Mario.Li...@dell.com

      unread,
      May 1, 2018, 10:02:37 AM5/1/18
      to hugh...@gmail.com, erinn.loo...@gmail.com, fw...@googlegroups.com
      > -----Original Message-----
      > From: Richard Hughes [mailto:hugh...@gmail.com]
      > Sent: Tuesday, May 1, 2018 6:40 AM
      > To: Limonciello, Mario
      > Cc: Erinn Looney-Triggs; fwupd
      > Subject: Re: [fwupd] Firmware updates not appearing?
      >
      Erinn,

      Since the PR will require a new fwupd client version to support the change in HWID
      format change you'll have to manually download/install the CAB file.

      As I can tell the HWID is not added to the XML metadata in the CAB, it's only in the
      LVFS metadata. That means you can manually download the file from:
      https://fwupd.org/lvfs/component/610/all

      and install using:
      # fwupdmgr install <file.cab>

      Thanks,
      Reply all
      Reply to author
      Forward
      0 new messages