Mario Limonciello

Is 2164 your latest version? That looks correct..

Would you please share that strace output from your attempt? Would you also please add `--verbose` to your invocation? Also, can this reproduce with `fwupdtool install-blob`?

> fwupdtool install-blob doesn't seem to recognize 50b94ce5-8b63-4849-8af4-ea479356f0e3 Can you try just `fwupdtool install-blob foo.bin` and then pick the device from the picker? > openat(AT_FDCWD, "\351R\256\252\n", O_RDONLY) = -1 ENOENT...

I don't understand why no device showing up. Can we see verbose output for fwupdtool?

Wait a minute; you're using the `fwupdate` from the fwupdate project!? I figured you were using the `fwupdate` that we distribute with _fwupd_'s `fwupdate` compatibility tool.. It's not worth doing...

> Loading… [* ]18:42:53:0606 FuContext Failed to load SMBIOS: structure larger than available data That is worrying. When you provide the full `fwupdtool get-devices --verbose` output, I would like to...

> Therefore, I don't see a way to access it on a locked down or strict_dev_mem kernel. Debian — and I guess other distributions — has a patch to enable...

I'm really perplexed why this just started to show up in Ubuntu 21.04, is it just people adopting it more lately? Neither libjcat nor fwupd in 21.04 have been touched...

>There are some systems that, even while attached to some sort of AC mains, will decide to allow the battery to go into a DISCHARGING state (either for battery health,...

It should be detecting your EFI system partition and then mounts it if it's not mounted. Can you please manually mount it and share the output of tree from it?...