From: dawidpotocki <dawidpotocki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] fwupd: /sys/firmware/efi/efivars was not mounted
Date: Sat, 25 Apr 2020 02:47:56 +0200 [thread overview]
Message-ID: <20200425004756.XLHq4OaK2H1SUIIh9m_FExZ7AYUcqP_6mFrahKBDLgA@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: 1412 bytes --]
Closed issue by dawidpotocki on void-packages repository
https://github.com/void-linux/void-packages/issues/18612
Description:
### System
* xuname:
`Void 5.4.15_1 x86_64 GenuineIntel notuptodate rFFF`
* package:
`fwupd-1.3.6_1`
### Expected behavior
fwupd is able to update firmware, efivars are mounted.
### Actual behavior
When I'm doing `$ fwupdmgr get-devices`, I get
`Update Error: /sys/firmware/efi/efivars was not mounted`
Then when I try updating with `# fwupdmgr update`, I get
```
No upgrades for System Firmware: is not updatable
No upgrades for UEFI Device Firmware: is not updatable
No upgrades for UEFI Device Firmware: is not updatable
```
### Fix
The problem is that efivars are not mounted by Void. Doing something like this
will fix this issue.
```
$ sudo mount -t efivarfs efivarfs /sys/firmware/efi/efivars
```
After this, it should work just fine
```
$ sudo fwupdmgr get-updates
$ fwupdmgr get-devices
```
efivars have to be mounted as RW, not RO.
Since `/sys/firmware/efi/efivars` isn't immutable prior to kernel 4.5, doing
something like `rm -rf` on it can brick the device.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed8b0de5a33d2a2557dce7f9429dca8cb5bc5879
### Steps to reproduce the behavior
1. Install `fwupd`
2. Run `fwupdmgr get-devices`
3. Run `fwupdmgr update` as root
prev parent reply other threads:[~2020-04-25 0:47 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
2020-04-04 7:24 ` dawidpotocki
2020-04-25 0:47 ` dawidpotocki
2020-04-25 0:47 ` dawidpotocki [this message]
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=20200425004756.XLHq4OaK2H1SUIIh9m_FExZ7AYUcqP_6mFrahKBDLgA@z \
--to=dawidpotocki@users.noreply.github.com \
--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).