unknown filesystem efivarfs
Bug #1650337 reported by
UlfZibis
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
| Disco |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
Please add file system efivarfs to 32-bit Linux kernel, so on EFI machine following command could be executed:
sudo mount -t efivarfs efivarfs /sys/firmware/
See also: bug 1648278
| no longer affects: | grub2-signed (Ubuntu) |
| description: | updated |
Revision history for this message
| Alkis Georgopoulos (alkisg) wrote | #1 |
| affects: | linux-lts-xenial (Ubuntu) → linux-signed (Ubuntu) |
| Changed in linux-signed (Ubuntu): | |
| importance: | Undecided → Low |
| status: | New → Confirmed |
Revision history for this message
| UlfZibis (ulf-zibis) wrote | #2 |
| affects: | linux-signed (Ubuntu) → linux (Ubuntu) |
| Changed in linux (Ubuntu Disco): | |
| status: | Confirmed → Triaged |
| tags: | added: cscc |
Revision history for this message
| Jonathan Polak (jpolak) wrote | #3 |
| Changed in linux (Ubuntu Disco): | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
I'm having this issue with Ubuntu MATE 18.04.1 32bit on 64bit UEFI hardware.
I think the problem is caused by the following kernel configuration directive, which is set on 64bit, but not on 32bit:
CONFIG_EFI_MIXED=y
Now this is supposed to allow 32bit firmware to boot 64bit kernels, but if I'm reading the code correctly, it's necessary for the opposite as well, otherwise the efivarfs file system doesn't exist, and efibootmgr/
http://
Btw, in dmesg the following message is shown:
efi: setup done, disabling due to 32/64-bit mismatch
And efivarfs doesn't exist in /proc/filesystems, even though /sys/firmware/efi is populated.