1 |
On Wed, Jan 25, 2017 at 6:58 PM, Alan Grimes <ALONZOTG@×××××××.net> wrote: |
2 |
> Tom H wrote: |
3 |
|
4 |
|
5 |
>> AFAIK, when you load the kernel directly from the EFI firmware, it has |
6 |
>> to have the ".efi" suffix. But that doesn't explain why it would stall |
7 |
>> when loaded from grub... |
8 |
>> |
9 |
>> Somewhat OT: Regarding grub, your "/boot/" is messy. It might not be |
10 |
>> making a difference for (efi)-grub2's functioning but you have grub1 |
11 |
>> files (*stage1_5), grub2 bios files (i386-pc/), as well as grub2 efi |
12 |
>> files (x86_64-efi/). |
13 |
> |
14 |
> Yeah, I've been using that directory for many many long years, I ended |
15 |
> up removing the grub directory completely and re-installing, it's much |
16 |
> cleaner now. |
17 |
|
18 |
ACK. I just thought that I'd point it out. |
19 |
|
20 |
|
21 |
> I think there's something with how I'm compiling the kernel and the EFI |
22 |
> boot requirements aren't quite being met and the loader is trying to |
23 |
> execute non-code or some other error of that general nature. But that's |
24 |
> just a brainstorm, I really hate it when my machine gives me this kind |
25 |
> of problem where I don't even have an error message. |
26 |
|
27 |
If you're loading the kernel from grub, you don't have to compile the |
28 |
efi stub/stuff into the kernel. |
29 |
|
30 |
|
31 |
> #### FROM GRUB.CFG ##### |
32 |
> |
33 |
> echo 'Loading Linux 4.6.7 ...' |
34 |
> <<<< it successfully executes this line |
35 |
> linux /vmlinuz-4.6.7 root=/dev/sda2 ro |
36 |
> <<<< but fails before the first output from the kernel |
37 |
> |
38 |
> ############ |
39 |
|
40 |
Looking at your grub.cfg, I wonder whether "linux /vmlinuz-4.6.7 ..." |
41 |
is correct. |
42 |
|
43 |
Looking at your original "tree" output, it looks like you're mounting |
44 |
the ESP at "/boot" and that grub's being loaded from |
45 |
"/boot/EFI/gentoo/grubx64.efi". |
46 |
|
47 |
What are the grub.cfg lines that start with "search" and "set root"? |