http://bugzilla.suse.com/show_bug.cgi?id=996088 http://bugzilla.suse.com/show_bug.cgi?id=996088#c7 Stuart Rogers changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(stuart@stella-mar | |is.org.uk) | --- Comment #7 from Stuart Rogers --- OK so having read all this I have a couple of things to say. First I have not had this issue until the latest grub2 update. My m/b is an ASROCK 890FX Deluxe 5 but I have no idea how big the nvram is and have been unable to find the answer. It does have the latest available BIOS loaded. When this problem happened I decided to try to set the boot order from a konsole but the command failed as shown. I gather from what you are saying that this "MAY" have corrected itself on a physical reboot, however this is not intuitive from the error that is seen. If it happens again I will indeed try this before trying anything else. The net result of everything I did try ended up with no UEFI boot options being stored in nvram when I did eventually try to boot the PC, the only bootable OS was XP on the PATA disk in BIOS mode, or I could boot the TW DVD rescue system in either UEFI or BIOS mode. I am not sure I understand what you mean about "booting from file" (or via EFI shell) actually means, can you please explain further? If you mean loading the EFI Shell from BIOS this does not work on this motherboard as I have tried it but it cannot find anything to load. As bit of background this PC has 3 systems installed, a Windows XP system which is obviously not EFI, a 42.2 test install and Tumbleweed both of which are in EFI mode. The 42.2 system is on the first physical SATA disk, TW is on the second and the XP system is on a PATA disk. Could this be confusing things here? -- You are receiving this mail because: You are on the CC list for the bug.