Another issue about fwupdmgr get-updates

penny-farthing

Since several posts have been published on this subject, so here is what the following terminal commands show me:

administrateur@solus-pc ~ $ sudo fwupdmgr get-updates
[sudo] password for administrateur:
WARNING: Les mises à jour de capsule UEFI ne sont pas disponibles ou pas activées dans la configuration du micrologiciel
Voir https://github.com/fwupd/fwupd/wiki/PluginFlag:capsules-unsupported pour plus d'informations.
WARNING: Ce paquet n'a pas été validé, il peut ne pas fonctionner correctement.
Devices with no available firmware updates: 
 • KEK CA
 • Windows Production PCA
 • CT500BX500SSD1
 • SBAT
 • WD10EZEX-08M2NA0
Devices with the latest available firmware version:
 • UEFI dbx
Gigabyte Technology Co., Ltd. B85M-D3H
│
└─UEFI CA:
  │   Identifiant de l'appareil: 5bc922b7bd1adb5b6f99592611404036bd9f42d0
  │   Version actuelle:   2011
  │   Fournisseur:        Microsoft (UEFI:Microsoft)
  │   Erreur de mise à jour: Not enough efivarfs space, requested 16,4 Ko and got 1,2 Ko
  │   GUIDs:              26f42cba-9bf6-5365-802b-e250eb757e96 ← UEFI\VENDOR_Microsoft&NAME_Microsoft-UEFI-CA
  │                       c34a7e6a-bd86-5244-8bd0-7db66fd3c073 ← UEFI\CRT_E30CF09DABEAB32A6E3B07A7135245DE05FFB658
  │   Drapeaux de périphérique: • Périphérique interne
  │                       • Supported on remote server
  │                       • Doit redémarrer après une mise à jour
  │                       • Mise à jour possible
  │                       • Signed Payload
  │                       • Can tag for emulation
  │ 
  └─Secure Boot Signature Database Configuration Update:
        Nouvelle version: 2023
        Remote ID:        lvfs
        Release ID:       116503
        Résumé:           UEFI Secure Boot Signature Database
        Licence:          Propriétaire
        Taille:           10,0 Ko
        Created:          2025-04-29 00:00:00
        Urgence:          Haute
          Tested:         2025-09-17 00:00:00
          Distribution:   fedora 42 (workstation)
          Old version:    2011
          Version[fwupd]: 2.0.16
          Tested:         2025-07-24 00:00:00
          Distribution:   nixos 25.11
          Old version:    2011
          Version[fwupd]: 2.0.12
        Fournisseur:      Linux Foundation
        Release Flags:    • Trusted metadata
                          • Is upgrade
        Description:      
        This updates the 3rd Party UEFI Signature Database (the "db") to the latest release from Microsoft. It also adds the latest OptionROM UEFI Signature Database update.
        Somme de contrôle: 6819c8098f09f4332a102194df6a033563aa288073b16315c5b88860fefb7e74
      
administrateur@solus-pc ~ $ df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
/dev/sda6          131G     36G   89G  29% /
devtmpfs           7,7G       0  7,7G   0% /dev
tmpfs              7,8G       0  7,8G   0% /dev/shm
efivarfs           128K    127K     0 100% /sys/firmware/efi/efivars
tmpfs              3,1G    9,7M  3,1G   1% /run
tmpfs              7,8G    8,0K  7,8G   1% /tmp
/dev/sdb1          901G    832G   24G  98% /home
tmpfs              1,6G    184K  1,6G   1% /run/user/1007
/dev/sda5         1022M    400M  623M  40% /boot
administrateur@solus-pc ~ $

On my computer, I've set up a dual boot (with Windows installed first, then Solus installed later (but it's Solus that launches without any intervention from my part)). Here's some additional information:

administrateur@solus-pc ~ $ neofetch
            -```````````                  administrateur@solus-pc 
          `-+/------------.`              ----------------------- 
       .---:mNo---------------.           OS: Solus 4.7 Endurance x86_64 
     .-----yMMMy:---------------.         Host: B85M-D3H 
   `------oMMMMMm/----------------`       Kernel: 6.16.5-322.current 
  .------/MMMMMMMN+----------------.      Uptime: 15 mins 
 .------/NMMMMMMMMm-+/--------------.     Packages: 1410 (eopkg), 34 (flatpak) 
`------/NMMMMMMMMMN-:mh/-------------`    Shell: bash 5.3.3 
.-----/NMMMMMMMMMMM:-+MMd//oso/:-----.    Resolution: 1920x1080 
-----/NMMMMMMMMMMMM+--mMMMh::smMmyo:--    DE: Budgie 10.9.2 
----+NMMMMMMMMMMMMMo--yMMMMNo-:yMMMMd/.   WM: Mutter(Budgie) 
.--oMMMMMMMMMMMMMMMy--yMMMMMMh:-yMMMy-`   Theme: Qogir-Dark [GTK2/3] 
`-sMMMMMMMMMMMMMMMMh--dMMMMMMMd:/Ny+y.    Icons: Qogir-Dark [GTK2/3] 
`-/+osyhhdmmNNMMMMMm-/MMMMMMMmh+/ohm+     Terminal: gnome-terminal 
  .------------:://+-/++++++oshddys:      CPU: Intel i3-4160 (4) @ 3.600GHz 
   -hhhhyyyyyyyyyyyhhhhddddhysssso-       GPU: Intel 4th Generation Core Processor Fami 
    `:ossssssyysssssssssssssssso:`        GPU: NVIDIA GeForce GTX 1050 Ti 
      `:+ssssssssssssssssssss+-           Memory: 3121MiB / 15868MiB 
         `-/+ssssssssssso+/-`

I notice that there's no more space available in the /sys/firmware/efi/efivars folder. What could explain this?
I must say that this doesn't prevent my computer from working properly; it's just that the firmware should no longer be able to be updated, if I understand correctly.

Should I be worried?
Thanks in advance for your advice.

BuzzPCSOS

penny-farthing This may have been coincidental but maybe worth a look. Noticed that my own efivarfs was about 98%. Looked in UEFI BIOS and saw that there were a number of boot options that were no longer used (several bootable USB devices, Fedora and a Windows utility disc). I deleted the unused entries and rebooted at which time efivarfs was much lower %. Initially about 39% I think, but it seems to have slowly risen to about 66%.
I keep an eye on file system usage with df -h --output=source,fstype,size,used,avail,pcent
Slightly off topic or totally misleading? Not sure but either way keeping the number of stored boot devices low can only be an improvement to system security. Hope it is helpful in some way.

brent

your get-updates output looks healthy and does not reflect the connection problems the rest of us have.

solus has a known big where not all the old kernels get removed that happens to only a handful (like the fwupmgr bug).
do a search here on 'efivars' and do some reading. in some threads Solus devs step in to explain how to safely thin that folder out if it gets too full. Make sure your /boot is 1GB as well.

IMHO the efivars-too-full is a distinct problem from the connection problem in fwupdmgr.

penny-farthing

brent
Harvey

Thank you both for your feedback.

Harvey

efivars is not managed by Solus, it is your systems UEFI. It should be fine no matter what and clean up itself as required, if it does not there is literally nothing Solus can do.

penny-farthing

BuzzPCSOS

That's what I did, but that has not changed the results:

administrateur@solus-pc ~ $ efibootmgr
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,0000,0002
Boot0000* Windows Boot Manager	HD(3,GPT,a2c81dcc-64eb-43b7-8a9e-f6bf52c21619,0x10c02800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000061000100000010000000040000007fff0400
Boot0002  UEFI OS	HD(5,GPT,b0a3ab93-c274-4201-aed5-e9f711f1774f,0x10c3c800,0x200000)/\EFI\BOOT\BOOTX64.EFI
Boot0003* Solus Linux Bootloader	HD(5,GPT,b0a3ab93-c274-4201-aed5-e9f711f1774f,0x10c3c800,0x200000)/\EFI\com.solus-project\bootloaderx64.efi
administrateur@solus-pc ~ $ df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
/dev/sda6          131G     36G   89G  29% /
devtmpfs           7,7G       0  7,7G   0% /dev
tmpfs              7,8G       0  7,8G   0% /dev/shm
efivarfs           128K    127K     0 100% /sys/firmware/efi/efivars
tmpfs              3,1G    9,7M  3,1G   1% /run
tmpfs              7,8G    8,0K  7,8G   1% /tmp
/dev/sdb1          901G    832G   24G  98% /home
tmpfs              1,6G    152K  1,6G   1% /run/user/1007
administrateur@solus-pc ~ $

Thank you anyway for your answer.

BuzzPCSOS

penny-farthing Thanks for the feedback. Well I did say that my whole solution may well have only had coincidental success.
Suggest that it wight be worth trying this command
sudo fwupdmgr refresh && fwupdmgr get-updates
That certainly seemed to fix my fwupdmgr issues.

penny-farthing

BuzzPCSOS

Here's the result:
administrateur@solus-pc ~ $ sudo fwupdmgr refresh && fwupdmgr get-updates

[sudo] password for administrateur:
WARNING: Les mises à jour de capsule UEFI ne sont pas disponibles ou pas activées dans la configuration du micrologiciel
Voir https://github.com/fwupd/fwupd/wiki/PluginFlag:capsules-unsupported pour plus d'informations.
WARNING: Ce paquet n'a pas été validé, il peut ne pas fonctionner correctement.
Metadata is up to date; use --force to refresh again.

So, to clarify, I entered the terminal commands separately in the order you indicated, which now looks like this:

administrateur@solus-pc ~ $ sudo fwupdmgr refresh
WARNING: Les mises à jour de capsule UEFI ne sont pas disponibles ou pas activées dans la configuration du micrologiciel
Voir https://github.com/fwupd/fwupd/wiki/PluginFlag:capsules-unsupported pour plus d'informations.
WARNING: Ce paquet n'a pas été validé, il peut ne pas fonctionner correctement.
Metadata is up to date; use --force to refresh again.

administrateur@solus-pc ~ $ sudo fwupdmgr refresh --force
WARNING: Les mises à jour de capsule UEFI ne sont pas disponibles ou pas activées dans la configuration du micrologiciel
Voir https://github.com/fwupd/fwupd/wiki/PluginFlag:capsules-unsupported pour plus d'informations.
WARNING: Ce paquet n'a pas été validé, il peut ne pas fonctionner correctement.
Mise à jour lvfs
Téléchargement…          [***************************************]
Successfully downloaded new metadata:
 • 3 devices are updatable
 • 2 devices are supported in the enabled remotes (an update has been published)

administrateur@solus-pc ~ $ fwupdmgr get-updates
WARNING: Les mises à jour de capsule UEFI ne sont pas disponibles ou pas activées dans la configuration du micrologiciel
Voir https://github.com/fwupd/fwupd/wiki/PluginFlag:capsules-unsupported pour plus d'informations.
WARNING: Ce paquet n'a pas été validé, il peut ne pas fonctionner correctement.
Devices with no available firmware updates:
• KEK CA
• Windows Production PCA
• CT500BX500SSD1
• SBAT
• WD10EZEX-08M2NA0
Devices with the latest available firmware version:
• UEFI dbx
Gigabyte Technology Co., Ltd. B85M-D3H
│
└─UEFI CA:
│ Identifiant de l'appareil: 5bc922b7bd1adb5b6f99592611404036bd9f42d0
│ Version actuelle: 2011
│ Fournisseur: Microsoft (UEFI:Microsoft)
│ Erreur de mise à jour: Not enough efivarfs space, requested 16,4 Ko and got 1,2 Ko
│ GUIDs: 26f42cba-9bf6-5365-802b-e250eb757e96 ← UEFI\VENDOR_Microsoft&NAME_Microsoft-UEFI-CA
│ c34a7e6a-bd86-5244-8bd0-7db66fd3c073 ← UEFI\CRT_E30CF09DABEAB32A6E3B07A7135245DE05FFB658
│ Drapeaux de périphérique: • Périphérique interne
│ • Supported on remote server
│ • Doit redémarrer après une mise à jour
│ • Mise à jour possible
│ • Signed Payload
│ • Can tag for emulation
│
└─Secure Boot Signature Database Configuration Update:
Nouvelle version: 2023
Remote ID: lvfs
Release ID: 116503
Résumé: UEFI Secure Boot Signature Database
Licence: Propriétaire
Taille: 10,0 Ko
Created: 2025-04-29 00:00:00
Urgence: Haute
Tested: 2025-09-17 00:00:00
Distribution: fedora 42 (workstation)
Old version: 2011
Version[fwupd]: 2.0.16
Tested: 2025-07-24 00:00:00
Distribution: nixos 25.11
Old version: 2011
Version[fwupd]: 2.0.12
Fournisseur: Linux Foundation
Release Flags: • Trusted metadata
• Is upgrade
Description:
This updates the 3rd Party UEFI Signature Database (the "db") to the latest release from Microsoft. It also adds the latest OptionROM UEFI Signature Database update.
Somme de contrôle: 6819c8098f09f4332a102194df6a033563aa288073b16315c5b88860fefb7e74

administrateur@solus-pc ~ $

This PC was built in 2014; perhaps is it too old to perform such updates?
If not, how should I proceed? (any help would be appreciated, thank you.)

BuzzPCSOS

penny-farthing From some of the error messages posted there is this link. A nice explanation and potential workaround. I hope this helps.
Edit: I would also suggest checking for an update at the manufacturers website as there may be a way to update your BIOS directly from a USB drive.

brent

BuzzPCSOS From some of the error messages posted there is this link. A nice explanation and potential workaround. I hope this helps.
Edit: I would also suggest checking for an update at the manufacturers website as there may be a way to update your BIOS directly from a USB drive.

did not ever see this. will explore remedies now. thank you.