> [root@gary ~]# efibootmgr -o 2002,2001,0003,0002
Try
efibootmgr -v -O -T ## capital O, to delete the entire boot order and timeout
efibootmgr -v -o 3,2 -t 3
I think making the DVD or USB the default boot options is a bad idea,
I wouldn't do that. Use the boot manager on demand if you need to
Well that's me stuffed again,
I did get to the point where I could press F9 and then select the Centos EFI
entry.
The problem only occurred after Windows installed a BIOS update, taking me
from F.65 to F.67. One of the first things I did to try to fix the problem
was to roll back F.65.
This
Hello there!
I'm stuck here on my CentOS6 w/ current EPEL's version of mingw32/64 gcc
(4.9.2), jealous about the Ubuntu's 5.3.0 version and even more jealous
about Fedora 24's top-recent 6.1.0.. and now I need msvcr120.dll
compatibility (provided by gcc 6.1.0).
Has anybody any experience w/ reco
On Thursday 15 September 2016 06:46:31 Chris Murphy wrote:
> Exactly what efibootmgr command are you using?
>
Chris,
They were included in my last email, along with the output
# get the current state
efibootmgr -v
# set the boot order DVD, USB, Centos, Windows
efibootmgr -o 2002,2001,0003,0
Am 14.09.2016 um 17:50 schrieb isdtor :
>
>> Not sure what would cause that error message, nor have I experienced it.
>> Looks like other people have seen it:
>> https://www.google.com/?gws_rd=ssl#q=gss_init_sec_context+failed+with+%5BUnspecified+GSS+failure.++Minor+code+may+provide+more+informat
5 matches
Mail list logo
