On Mon, Jul 27, 2020, 9:06 PM Peter King via talk, <[email protected]> wrote:
> Well, no joy in Mudville. > > I disabled Secure Boot by deleted the PK key, which did indeed result in > the motherboard BIOS recognizing that Secure Boot was disabled. And, it > recognizes the NVMe drive as the boot device, indeed the only boot device, > which is good. > > But ... despite all that, it still does not boot. I tried it with CSM on > and CSM off, still no boot. Efibootmgr this time *did* list the NVMe drive > as an EFI option (after the USB flash drive), but still no boot. Tried it > with various options enabled and disabled, still no joy. > I don't use Arch myself but the various GPT or MBR and Hybrid schemes are covered, along with issues, notes and warnings here. > https://wiki.archlinux.org/index.php/Arch_boot_process > Damned if I can figure it out. I feel like I'm getting closer ... but no > way forward seems obvious. Any ideas? Any reason to think that another > motherboard might be less difficult to get up and running? > I don't think so. You are making progress. It might be that the bootloader can't actually access /boot or because of some confusion in addressing the partition table format. HTH Russell > > -- > Peter King [email protected] > Department of Philosophy > 170 St. George Street #521 > The University of Toronto (416)-946-3170 ofc > Toronto, ON M5R 2M8 > CANADA > > http://individual.utoronto.ca/pking/ > > ========================================================================= > GPG keyID 0x7587EC42 (2B14 A355 46BC 2A16 D0BC 36F5 1FE6 D32A 7587 EC42) > gpg --keyserver pgp.mit.edu --recv-keys 7587EC42 > --- > Post to this mailing list [email protected] > Unsubscribe from this mailing list > https://gtalug.org/mailman/listinfo/talk >
--- Post to this mailing list [email protected] Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
