http://bugzilla.novell.com/show_bug.cgi?id=571850 http://bugzilla.novell.com/show_bug.cgi?id=571850#c1 Jozef Uhliarik changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED --- Comment #1 from Jozef Uhliarik 2010-01-19 16:10:47 UTC --- Thanks Stephan I will take a look. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=571850 http://bugzilla.novell.com/show_bug.cgi?id=571850#c3 --- Comment #3 from Stephan Kulow 2010-01-20 08:42:38 UTC --- this is qemu-kvm - I do not even know they have a BIOS :) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=571850 http://bugzilla.novell.com/show_bug.cgi?id=571850#c5 Raymund Will changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rw@novell.com --- Comment #5 from Raymund Will 2010-01-20 16:46:48 UTC --- This is very strange, as (last time I looked) 'efivars.ko' could only successfully be loaded, if the kernel had been booted by an EFI loader (i.e. with 'boot_params.efi_info.efi_loader_signature == "EL64"'). May be you could check, that '/sys/firmware/efi/systab' is accessible and "reasonable" after loading 'efivars'? E.g. like

cat /sys/firmware/efi/systab MPS=0x0 ACPI20=0x9fbfe014 ACPI=0x9fbfe000 SMBIOS=0x9f93b000 HCDP=0x0 BOOTINFO=0x0 UGA=0x0

Coolo, what does your "machine" expose there? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=571850 http://bugzilla.novell.com/show_bug.cgi?id=571850#c7 --- Comment #7 from Stephan Kulow 2010-01-21 15:40:46 UTC --- modprobe works, but there is no such directory /sys/firmware/efi after modprobe -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=571850 http://bugzilla.novell.com/show_bug.cgi?id=571850#c9 --- Comment #9 from Raymund Will 2010-01-21 16:26:00 UTC --- BTW, the error message in %summary is bogus. This should definitely have an UEFI in there (like "x86_64/UEFI" or "UEFI-enabled x86_64"). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=571850 http://bugzilla.novell.com/show_bug.cgi?id=571850#c11 Jozef Uhliarik changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |FIXED --- Comment #11 from Jozef Uhliarik 2010-02-11 09:58:19 UTC --- I added checking of QEMU to support check in yast2-bootloader 2.19.3 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.