http://bugzilla.opensuse.org/show_bug.cgi?id=921221 Neil Rickert changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nrickert@ameritech.net --- Comment #1 from Neil Rickert --- This seems strange. I have mostly heard good reports about ASUS implementation of UEFI. My UEFI experience (with Dell and Lenovo) there was no ncurses screen. The computer already had a Windows key, and shim has a signature from that key. Shim was accepted without problems. Not asking about trust a second time probably means that the key was saved in NVRAM the first time. I'm not sure why you wiped in legacy mode, instead of just turning off secure-boot but keeping UEFI mode. That should have avoided all key problems. (just a comment from someone with no official standing). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=921221 --- Comment #3 from Richard Brown --- Yes. I ran Windows 8.1, ran through the 'first time setup' routine, and played around before rebooting and trying to install openSUSE My impression is the Asus 'UEFI' implimentation seems robust, it's 'Bios' settings for configuring the PEK/keys/etc all seem like they know what I'm doing Given the problems went away only when I wiped the whole SSD, I suspect the problem is something to do with the UEFI partition on the hard disk they're shipping. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=921221 --- Comment #5 from Richard Brown --- I'm trying to negotiate some windows installation media out of Asus so I can reproduce this -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=921221 http://bugzilla.opensuse.org/show_bug.cgi?id=921221#c6 Vlada Kozousek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vlada.kozousek@gmail.com --- Comment #6 from Vlada Kozousek --- Hi, I have Asus X205TA eeeBook with Windows 10 running. I was not able to install from USB openSUSE 13.2 KDE Live. Having made a number of attempts with different BIOS settings machine always skips to booting Windows 10. I know that the USB stick is OK as I used it to install the software on another laptop, however as this is an older machine it does not have secure boot or Windows 10 installed, the machine dual boots with Windows 7. I was, however, able to install Linux Mint from USB on Asus machine without any problem. In my view there is something wrong with the UEFI in openSUSE installation directory. It would be great if somebody with in depth knowledge about secure boot protocol could investigate. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=921221 http://bugzilla.opensuse.org/show_bug.cgi?id=921221#c8 --- Comment #8 from Vlada Kozousek --- Hi, can confirm Asus X205TA uses Intel Atom processor. The 32-bit UEFI is in fact part of the Linux Mint installation, even thought the rest is 64bit. I was never able to boot into openSUSE KDE Live it always skipped into booting Windows 10. It does seem that 32-bit UEFI is required but my search did not find one for openSUSE. You are suggesting that there may not be one available ? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=921221 http://bugzilla.opensuse.org/show_bug.cgi?id=921221#c10 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FEATURE --- Comment #10 from Jiri Srain --- For the reference: https://features.opensuse.org/318252 I think that it makes sense to move the discussion to openFate... -- You are receiving this mail because: You are on the CC list for the bug.