On Tue, 2019-04-09 at 23:10 -0600, Chris Murphy wrote: > On Tue, Apr 9, 2019 at 1:37 AM Berend De Schouwer > <berend.de.schouwer@xxxxxxxxx> wrote: > > grub.cfg did contain: > > > > insmod blscfg > > blscfg > > > > /boot/loader/entries has 5 .conf files and a rescue.conf > > > > grub gave no menus. > > That means GRUB can't find or read the .conf files in > /boot/loader/entries so it's going to take some effort to figure out > where the problem is. I've found BZ https://bugzilla.redhat.com/show_bug.cgi?id=1652806 > Is there anything unique about the storage stack? Is this BIOS or > UEFI? Is /boot its own volume or is it a directory on / ? And what's > the file system? BIOS (or CSM). Theoretically the laptop supports UEFI. In practice it doesn't. Neither Linux nor Windows was installed using EFI on this laptop. /boot/efi is empty (not mounted, no partition) /boot is it's own volume, 500 MB, ext4. / is lvm and luks. The grub update deleted two other boot options: memtest and dban. (Windows is unused, but it was installed using not-EFI.) > If you want to dive into this even more in the meantime, at the grub > prompt: > > set debug=all > blscfg > Now you'll get a page of very verbose debug info as that command > executes. Press space and you'll get a new page. Depending on where > the problem is, it might be a few pages of debug info or it might be > 50. And if you can't find some hint scrolling through all that, > you'll > need to take a cell phone photo or video if it's not a VM, of > everything after blscfg :-D and maybe I'll have a moment to look at > it, or maybe Javier can look (he's on the bls project). Planning to do this today when it's a bit calmer, and I've got a bootable USB stick to rescue the machine. BLS means no boot. > > This is using a BIOS, not EFI. (EFI on this laptop is kaput.) > > Ok well if this is some legacy BIOS setting, EFI is definitely > working > and then running a CSM to present a faux-BIOS to GRUB and the kernel. > Maybe that EFI implementation has bugs and there are no firmware > updates from the manufacturer and the work around is to use the CSM? I did look for firmware updates, and again with the meltdown bugs. Nothing. _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
