On 2018-12-25 08:23, Fredrik wrote: Thank you for your answer.
Just a quick note here - grub-mkconfig will not create a usable config if the kernel is just called "vmlinuz". If you append a version string after it (vmlinuz-4.14 or whatever) it should generate a proper config with fancy menus.
It's what I discovered. After renaming it to vmlinuz-4.14.40 grub generated a config file with that entry. Before I had some doubts because it was rather empty. I guess there was no entry in the grub configuration file. That's why I got the grub shell. Everything is fine now, I can boot, thank you! But I have another question: does need somebody to update the installation guide or the users are supposed to know it ? Normally the kernel version is appened to vmlinuz, but nothing more was specified in the installation guide, so I thought it was ok.
- I have some doubts, but I changed a few options in the kernel. All options for uefi where compiled in the kernel not as module. I have also set the command line argument in the kernel with a PARTUUID:
[*] Built-in kernel command line
(root=PARTUUID=55898d79.........e0709) Built-in kernel command string
If you intend to use grub I'd recommend not placing stuff like that in the kernel command-line. I assume the bootloaders arguments would overrule those settings but I'm just guessing as I've never tried it. Keep it simple and just remove that setting.
I think it's still there, but it boots. I'll remove it as soon as my system will be fully installed.
Do I need to create an initramfs ? All related UEFI options are not compiled as modules. By the way the PARTUUID is the partition of root, not my ESP partition. Finally, the output of efibootmgr: Not for UEFI. From what I can tell you dont need a initrd.
Yes, it was not necessary. Thank you for your help!