Bug 850781 - efi variables not read correctly on Lenovo Thinkpad L430
efi variables not read correctly on Lenovo Thinkpad L430
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
17
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthew Garrett
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-22 08:16 EDT by Michael Laß
Modified: 2013-01-08 11:04 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-01-08 11:04:39 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michael Laß 2012-08-22 08:16:12 EDT
Description of problem:

When using the Thinkpad L430 in UEFI mode you can not read the current content of nvram via efibootmgr. Running "efibootmgr -v" creates no output.
You can create boot entries via efibootmgr, but in this case all current entries are deleted. This is also what's happening during the Fedora installation. The result is that you cannot boot other systems and not even boot from other devices anymore after installing Fedora.

The reason might be that in /sys/firmware/efi/vars there are only two files: del_var and new_var. According to http://www.kernel.org/doc/Documentation/ABI/stable/sysfs-firmware-efi-vars there should be many more.

I'm not shure if this is a kernel bug or a bug in Lenovos UEFI-BIOS. But the entries can be read in Windows without problems (using "bcdedit /enum firmware") so there seems to be a way to read the content of nvram.


Version-Release number of selected component (if applicable):
Fedora 17
Kernel 3.5.2-1.fc17.x86_64
Newest UEFI-BIOS version released by Lenovo (ver. 1.11)


How reproducible:

Steps to Reproduce:
1. Boot fedora from a livecd/-usb whatever
2. As root run efibootmgr -v
3. Create a new entry using efibootmgr
  
Actual results:
There is no output. When creating a new entry all other entries are deleted, so you can only boot the entry you just inserted.

Expected results:
The current entries in nvram should be displayed. When creating a new entry it should be appended to those already existing.

Additional info:
dmesg shows the following lines:
[    1.044100] EFI Variables Facility v0.08 2004-May-17
[    1.044104] efivars: get_next_variable: status=8000000000000002

Please tell me if I can provide any other useful details.
Comment 1 Josh Boyer 2013-01-08 10:36:33 EST
Are you still having this issue with the 3.6.10 or newer kernel updates?
Comment 2 Michael Laß 2013-01-08 11:01:22 EST
After a mainboard defect (that might have been related to a bug in the EFI system) I decided to switch back to legacy boot. So unfortunately I can't test this anymore.
Comment 3 Josh Boyer 2013-01-08 11:04:39 EST
OK.  We've not had similar reports that I'm aware of, so we'll close this bug out for now.  If you happen to hit it again, please let us know.

Note You need to log in before you can comment on or make changes to this bug.