You might check the output of efibootmgr to see if the listing it gives you is as you expect. For example, maybe you've managed to disable an entry which should be enabled or something like that.
I did look at the efibootmgr bootoptions, but it'll only list the cd drive and the entries placed there by the command issued above.
And thank you for the guide .. If i mess up again I'll give it a bash
]]>It involves extracting the firmware for your laptop on another computer, renaming a file and copying it to a FAT32 flash drive, and booting in recovery mode, and looks like it should always work.
]]>I've managed to flash my BIOS, the delete key doesn't work, but I can now get into a boot menu by pressing escape, which also allows me into the BIOS setup itself. Not perfect like; but considering where I was yesterday I can't really complain at all .
The problem with a bug report is that I don't really have anything to offer with regards to useful information. I'll see about filing one though.
Thanks again
]]>I am glad to hear that you got your system working though.
I have definitely never heard efibootmgr causing inaccess to the bios settings though. Maybe this might be a good thing to file a bug report for with upstream. Of course, with UEFI's newness, things are different from system to system, so they cannot be 100% sure that the software will be perfect in all cases. Still it might be good to make them aware (even if it was, in fact, something that you borked), as maybe it might save another poor individual from the smae problem.
Do you have a UEFI shell? Maybe you should use it's took to create boot manager entries instead.
]]>I'm assuming that somehow one of the EFI vars may be related to the key which accesses the bios menu, but i'm not sure how it may have been modified and I can't seem to find any information regarding it.
I'm half considering flashing my BIOS with a new update on the off chance that it'll repair whatever's gone wrong with it.. But if you guys have any ideas i'd love to hear them .
]]>.. I just need to not be dumb this time I think..
]]>EDIT: Do'h! I see you fixed it before I submitted my post. Glad you got your doorstop working
]]>.. Fingers crossed I won't balls it up this time. Thank you for your support there .
]]>EDIT: Fixed terminology.
]]>With the *.efi file, it didn't appear where the guide said it would, so I was trying to be extra careful to ensure that things were as close to the guide as possible.
I'm looking for some way to reset the bios; but it's not looking good at the moment
]]>So you cannot enter the "boot select menu" or the bios?
]]>I just picked up a new laptop, Asus N56VZ, whopped an SSD into it and began the install process; intending to boot via UEFI and grub2.
Everything was going fine, until I executed this command:
efibootmgr -c -g -d /dev/sdX -p Y -w -L "Arch Linux (rEFInd)" -l '\\EFI\\arch\\refind\\refindx64.efi'
It seemed to work fine, but didn't put the expected file (refindx64.efi) in the correct place. It ended up in /usr/.../refind/refindx64.efi
I figured that this was probably wrong, so deleted the files and rebooted with the intention of reloading the live cd and following the instructions more closely.
I now cannot boot, nor enter the Asus BIOS by pressing delete (i was getting in there earlier fine) all it'll give me is a prompt which says Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key.
Needless to say, I'm bricking myself at the thought of turning this thing into an expensive doorstop.. Any help you guys could offer would be magnificent.
Many thanks in advance,
- Ataxia
]]>