Instead of creating just one entry this command created three visible entries in the "BIOS-Settings" under the boot section. Instead I tried to execute efibootmgr just once with no other boot entries existing (you can find the command and the result here. There are similar issues reported on Wikipedia. I'd say this failure is reproducible by adding two or three boot entries using efibootmgr, but I didn't test it so far as I don't wanna hard-brick my notebook again. The program "efibootmgr" obviously shouldn't be able to hard-brick my notebook even if I would have entered a wrong command. When I pressed the power button it just displayed the ASUS-Logo and that was it (I couldn't access the "BIOS-Settings" with F2 pressing TAB sometimes removed the ASUS-Logo giving me a black screen with backlight the power button still worked making it possible to shutdown the keyboard-backlight was on). I extracted the exact commands responsible for this from the history (/root/.bash_history): 342 efibootmgr -create -part 2 -label "Gentoo-Main" -loader 'kernel-genkernel-x86_64-4.0.5-gentoo.efi' -u initrd='initramfs-genkernel-x86_64-4.0.5-gentoo.img'Ĥ99 efibootmgr -create -part 2 -label "Gentoo-Patch" -loader 'kernel-genkernel-x86_64-4.0.5-gentoo_patch.efi' -u initrd='initramfs-genkernel-x86_64-4.0.5-gentoo_patch.img'Īfter command 342 I could reboot without problems, but after command 500 (reboot) my notebook didn't boot up anymore.
#Compal hl90 drivers software
Since the firmware implements the UEFI-Specification I thought I'd use the UEFI-Implementation to manage the whole boot process instead of using additional software like GRUB2.Īs the "BIOS-Settings" don't offer an option to set boot parameters, which I needed for an external initramfs, I decided to use the program efibootmgr. I sadly ended up unexpectedly hard-bricking it after 11 days (it's fixed by now). I've recently bought an ASUS UX303LA-R4342H notebook, which is using an American Megatrends firmware (UEFI Version: (UX303LAB.)207). Tl dr - you might wanna just read "What happened", "The Issue" and "The Question" Prologue:
The ASUS support isn't cooperative at all and I guess they don't even understand the problem.
#Compal hl90 drivers update
Question-State: solved (not really but it basically works)Įdit (Current-Progress): ASUS released a new "BIOS-Update" (BIOS 210 Update FW) which fixes the "BIOS-Settings" issues, but I'm not sure if it also fixes the efibootmgr hard-bricking issues (I don't really want to test this, but theoretically it should).
0 kommentar(er)
