Mailinglist Archive: opensuse-bugs (3349 mails)

< Previous Next >
[Bug 978593] EFI fails to load up the grub2 image erroring out on snapshot path
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 06 May 2016 12:21:12 +0000
  • Message-id: <bug-978593-21960-AUZ2wdcGpE@http.bugzilla.suse.com/>
http://bugzilla.suse.com/show_bug.cgi?id=978593
http://bugzilla.suse.com/show_bug.cgi?id=978593#c21

--- Comment #21 from Alexander Graf <agraf@xxxxxxxx> ---
(In reply to Michael Chang from comment #20)
(In reply to Alexander Graf from comment #19)
(In reply to Michael Chang from comment #18)
(In reply to Alexander Graf from comment #16)
(In reply to Michael Chang from comment #15)


I think if what you say is true, the best solution would be to just include
efivars.ko in the installer system. Then the rest should resolve itself
automatically, because we will detect the correct type of system again.

There may be some misunderstanding here, the "efivars" seen already built-in
in kernel while "efivarsfs" is a kernel module and not available in install
system.

At least from my test

ls /sys/firmware/efi/efivars

outputs nothing but

ls /sys/firmware/efi/vars

outputs plenty of files.

In your patch it's testing /sys/firmware/efi/efivars ...

Yes, but the person pulling a change to perl-bootloader is the same person that
would pull a change to the list of modules we include during the install phase.
So changing it to efi/vars doesn't allow us to proceed any faster.

The reason I chose efivars over efi/vars is that it's easier to identify that
there are no variables. The efivars directory is simply empty if you don't have
any efi variables available. The efi/vars directory always contains special
files to modify entries.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
References