Tom H wrote: > On Wed, Jan 25, 2017 at 1:05 PM, Alan Grimes <alonz...@verizon.net> wrote: >> The linux kernel stalls stone cold dead in either direct from firmware >> or pass through grub mode. > AFAIK, when you load the kernel directly from the EFI firmware, it has > to have the ".efi" suffix. But that doesn't explain why it would stall > when loaded from grub... > > Somewhat OT: Regarding grub, your "/boot/" is messy. It might not be > making a difference for (efi)-grub2's functioning but you have grub1 > files (*stage1_5), grub2 bios files (i386-pc/), as well as grub2 efi > files (x86_64-efi/).
Yeah, I've been using that directory for many many long years, I ended up removing the grub directory completely and re-installing, it's much cleaner now. I think there's something with how I'm compiling the kernel and the EFI boot requirements aren't quite being met and the loader is trying to execute non-code or some other error of that general nature. But that's just a brainstorm, I really hate it when my machine gives me this kind of problem where I don't even have an error message. #### FROM GRUB.CFG ##### echo 'Loading Linux 4.6.7 ...' <<<< it successfully executes this line. linux /vmlinuz-4.6.7 root=/dev/sda2 ro check_enable_amd_mmconf amd_iommu=fullflush iommu=soft <<<< but fails before the first output from the kernel. ############ Hmm, I just realized that I had been assuming my machine had a proper 64 bit loader, maybe it's 32 bit for some stupid reason, enabling kernel flag and doing another test (after dinner and some youtube vids...) -- Strange Game. The only winning move is not to play. Powers are not rights.