From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: fwupd: /sys/firmware/efi/efivars was not mounted
Date: Wed, 29 Jan 2020 09:32:28 +0100 [thread overview]
Message-ID: <20200129083228.Tx5yERpFYPak4Ux4EaKD3ZwtbPYuq31oxVNB52SKf8Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18612@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1792 bytes --]
New comment by Hoshpak on void-packages repository
https://github.com/void-linux/void-packages/issues/18612#issuecomment-579649264
Comment:
I tried it on my system as well. I used fwupdmgr in the past to update a Logitech unifying receiver and it also detects the two SSDs in the system. Efivars is now mounted manually:
```
# mount | grep efivars
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,relatime)
```
But still I get:
```
ââSystem Firmware:
â Device ID: 1d70a31dd3ff0941761550a38436fc990c6c3ff0
â Current version: 0.0.11
â Minimum Version: 0.0.11
â Vendor: ASUS (DMI:American Megatrends Inc.)
â Update Error: /sys/firmware/efi/efivars was not mounted
â GUID: 7039436b-6acf-433b-86a1-368ec2ef7e1f
â Device Flags: ⢠Internal device
â ⢠Requires AC power
â ⢠Needs a reboot after installation
â ⢠Cryptographic hash verification is available
```
So either something else is required or the firmware cannot be updated via fwupdmgr. In that case the error message would be misleading.
The update command shows me:
```
# fwupdmgr update
No upgrades for Unifying Receiver: current version is RQR12.10_B0032: RQR12.10_B0032=same, RQR12.08_B0030=older, RQR12.07_B0029=older
```
So it only considers the Unifying receiver but not the other three devices. This could be because though they could theoretically be updated via fwupdmgr, there's no firmware for these devices on the server. The get-releases command shows that there are no releases for either of the SSDs and that UEFI is not updateable.
next prev parent reply other threads:[~2020-01-29 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 15:28 [ISSUE] " voidlinux-github
2020-01-28 15:33 ` voidlinux-github
2020-01-28 15:33 ` voidlinux-github
2020-01-28 15:34 ` voidlinux-github
2020-01-28 15:49 ` voidlinux-github
2020-01-28 15:50 ` voidlinux-github
2020-01-29 8:32 ` voidlinux-github [this message]
2020-04-04 7:24 ` dawidpotocki
2020-04-25 0:47 ` dawidpotocki
2020-04-25 0:47 ` [ISSUE] [CLOSED] " dawidpotocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200129083228.Tx5yERpFYPak4Ux4EaKD3ZwtbPYuq31oxVNB52SKf8Q@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).