12/27/2023 0 Comments Launchbar adress![]() But if you do, I suspect by installing refind, by playing with the multiple efi* named packages and tools, you can restore that, or it might be that your BIOS allows that directly. The second question is probably safe if you don't use PXE boot or other boot method, at least that's what I understand. I think the first can be safely answered "No" if you don't plan on booting via a removable USB stick, while the second is the one that does the restoring. For example, if your NVRAM variables have been set up such that your system contacts a PXE server on every boot, this would preserve that behavior. However, you may prefer to disable this behavior and avoid changes to your boot configuration. GRUB can configure your platform's NVRAM variables so that it boots into Debian automatically when powered on. Update NVRAM variables to automatically boot into Debian? If so, you will need to make sure that GRUB is configured successfully to be able to boot any other OS installations correctly. However, it may remove the ability to boot any other operating systems that also depend on this path. If you force an extra installation of GRUB to the EFI removable media path, this should ensure that this system will boot Debian correctly despite such a problem. Some EFI-based systems are buggy and do not handle new bootloaders correctly. When reinstalling grub-efi-amd64 onto the disk, I think the scariest questions were to these:įorce extra installation to the EFI removable media path? Update-grub22) reinstall grub-efi-amd64 and make Debian the default Hints for anyone reading this in the hope to fix the same issue, hopefully it will make things better, not worse (see the text below): I tried regenerating the grub configuration, installing it and also tried restoring the default proper boot sequence (and I even installed refind in the system during my fumbling), but I think somewhere between grub-efi-amd64 reconfiguration and its reinstallation I managed to do the right thing, as the default boot screen is the Grub one now. In the end, I realized that I could via BIOS actually select manually which EFI executable should be booted into, so I was able to boot with some manual intervention during boot into the regular system. I even forgot where or how was the EFI installed on the disk and EFI, even if it should be more reliable and simpler, I never got the hang of it. When buying the laptop it had FreeDOS installed on it and some HP rescue app, which I did not wipe when installing Debian. I also tried to boot in rescue mode the Buster first DVD (to avoid the need for network), I was able to enter the partition, mount the EFI partition, too, but since I didn't want to mess the setup even more or depend on an external USB stick, I didn't know where should I try to write the Grub EFI config - the root partition is on an NVME storage. There is even a bug report in Debian about this error, bug #984760.Īdding to the pile of confusion my own confused solution: I tried supergrubdisk2/rescatux, it didn't work for me, it might have been a combination of me using LVM and grub-efi-amd64. I looked for a solution and it seemed everyone was stuck or the solution was unclear. I was waiting for the inevitable and dreading the wireless issues, but since mid-august Bullseye became stable, turning Stretch into oldoldstable, I decided that I had to do the upgrade, at least to buster.Įverything went quite smooth, except that after the reboot, the laptop failed to boot with this Grub error:Įrror: symbol ‘grub_is_lockdown’ not found More reason to wait for a newer release that would contain a driver inside the official kernel. I also tend to wait for the first or even second update of the release to avoid any sharp edges.Īs this laptop has a Realtek 8821CE wireless card that wasn't officially supported in the Linux kernel, I had to use an out-of-tree hacked driver to have the wireless work on Stretch kernels such as 4.19, it didn't even got along with DKMS, so all compilations and installations of it, I did them manually. ![]() I have been Debian Stretch running on my HP Pavilion 14-ce0000nq laptop since buying it back in April 2019, just before my presence at Oxidizeconf where I presented " How to Rust When Standards Are Defined in C".ĭebian Buster (aka Debian 10) was released about 4 months later and I've been postponing the upgrade as my free time isn't what it used to be.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |