On Thu, Dec 14, 2017 at 6:59 AM, Akemi Yagi <amyagi@xxxxxxxxx> wrote:
> On Thu, Dec 14, 2017 at 5:39 AM, Gary Stainburn <gary@xxxxxxxxxxxxxx>
> wrote:
>
>> After getting nowhere with the mokutil command I decided to use the other
>> option and turn off secure boot in the BIOS settings.
>>
>> I had been loathed to do this because every time I do anything in the
>> BIOS it
>> stuffs the boot order and reverts to booting straight into Win8. Guess
>> what,
>> as soon as I turned off secure boot it did exactly that. Turnng secure
>> boot
>> back on made no difference.
>>
>> Thankfully, the mailing list archives for this list still contain the
>> instructions on how to fix it.
>>
>> For those interested, it involved pressing F9 at boot time to select the
>> boot
>> menu and selecting the Centos option. This then went through GRUB as
>> normal
>> and booted. I then used 'eftbootmgr -o' to define the correct boot
>> sequence.
>>
>> The upshot is that I now have a laptop that boots correctly, and that
>> successfully uses the built in Broadcom WiFi adaptor.
>>
>> Thanks everyone for your help
>>
>
> Glad to hear things are now working for you.
>
> Just wanted to add a note that you can use ELRepo's drivers with
> SecureBoot enabled if you so wish.
> Here's how:
>
>
> http://elrepo.org/tiki/SecureBootKey
>
> Akemi
>
> Another [important] note if you are running CentOS 7.4. There is an issue
with the current version of shim in CentOS 7.4. The details can be found
here:
https://bugs.centos.org/view.php?id=14050
Follow the workaround in that bug report. Hope the problem gets fixed soon
by CentOS devs.
Akemi
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
