В Пт, 03/01/2014 в 19:27 +0100, Günther J. Niederwimmer пишет:
Am Freitag, 3. Januar 2014, 21:31:38 schrieb Andrey Borzenkov:
В Пт, 03/01/2014 в 17:40 +0100, Günther J. Niederwimmer пишет:
Am Freitag, 3. Januar 2014, 20:28:59 schrieb Andrey Borzenkov:
В Пт, 03/01/2014 в 17:19 +0100, Günther J. Niederwimmer пишет:
Hello,
Am Freitag, 3. Januar 2014, 20:03:44 schrieb Andrey Borzenkov:
В Пт, 03/01/2014 в 16:48 +0100, Günther J. Niederwimmer пишет: > Hello, > > The ASUS People like to know is any Motherboard running with > openSUSE > 13.1 > with Secure Boot and AMI Bios. > > Please let me know the Boards for a Answer. > > The Problem, I have two new ASUS Boards with Problems to boot with > Secure > Boot and the SUSE People mean this is a ASUS implementation > Problem?
Do you have bug numbers?
Yes ;)
grub2 in 13.1 had bug that was fixed in later update. Did you test
- install in UEFI mode with secure boot disabled - apply all updates - enable secure boot
Yes, but with enabled Secure Boot the system is not starting, win 8 is starting :-(.
You ignored my question about installing updates. And in bug report you also said you tested 13.1 GA, and never said anything about applying later updates.
Pardon,
I don't ignore your Question ;). Yes I install all update, yes I test it again with secure boot, but it is not working ?
Is this wrong in the message from Gary Lin, I understand the Message in that way, the Microsoft Signature is on the wrong Place implemented ?
I looked at your bug report once more and I still miss clear description, *what* does not work. Booting is multistage process and secure boot in this case adds even more steps. Your bug report gives no reasons to believe that problem is in signature verification. Actually it does not give any information beyond "it does not work". That is why I said you - start step by step, determine at which step booting fails. If problem is signature verification, you should get error - either from firmware or from shim. Do you get one? If yes - please show picture of this error.
And only a Bios Update bring back the function to boot with secure Boot?
OK, I test it again.
And BTW this bug could also affect non-secure boot case.
> Now like ASUS to know the Boards there are running with openSUSE > 13.1. > > Thanks for the Help,
-- mit freundlichen Grüßen / best Regards,
Günther J. Niederwimmer
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org