Bug#995270: fwupdmgr: WARNING: Firmware can not be updated in legacy BIOS mode
Package: fwupd
Version: 1.5.7-4
Severity: normal
X-Debbugs-Cc: tg@mirbsd.de
tglase@tglase-nb:~ $ sudo fwupdmgr get-devices
WARNING: Firmware can not be updated in legacy BIOS mode
See https://github.com/fwupd/fwupd/wiki/PluginFlag:legacy-bios for more information.
[…]
I’ve followed the instructions on the listed page and added uefi
to the list of disabled plugins, but the message still is shown.
This laptop doesn’t have EFI.
-- System Information:
Debian Release: 11.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'oldstable-updates'), (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)
Versions of packages fwupd depends on:
ii libc6 2.31-13
ii libcurl3-gnutls 7.74.0-1.3+b1
ii libefiboot1 37-6
ii libelf1 0.183-3
ii libelogind0 [libsystemd0] 246.9.1-1+debian1
ii libflashrom1 1.2-5
ii libfwupd2 1.5.7-4
ii libfwupdplugin1 1.5.7-4
ii libglib2.0-0 2.66.8-1
ii libgnutls30 3.7.1-5
ii libgudev-1.0-0 234-1
ii libgusb2 0.3.5-1
ii libjcat1 0.1.3-2
ii libjson-glib-1.0-0 1.6.2-1
ii libpolkit-gobject-1-0 0.105-31
ii libsmbios-c2 2.4.3-1
ii libsqlite3-0 3.34.1-3
ii libtss2-esys-3.0.2-0 3.0.3-2
ii libxmlb1 0.1.15-2
ii shared-mime-info 2.0-1
Versions of packages fwupd recommends:
pn bolt <none>
ii dbus 1.12.20-2
pn fwupd-signed <none>
ii python3 3.9.2-3
pn secureboot-db <none>
ii udisks2 2.9.2-2
Versions of packages fwupd suggests:
pn gir1.2-fwupd-2.0 <none>
-- Configuration Files:
/etc/fwupd/daemon.conf changed:
[fwupd]
DisabledDevices=
DisabledPlugins=test;test_ble;invalid;uefi
ArchiveSizeMax=0
IdleTimeout=7200
VerboseDomains=
UpdateMotd=true
EnumerateAllDevices=false
ApprovedFirmware=
BlockedFirmware=
UriSchemes=
-- no debconf information
Reply to: