Hello, I started recently maintaining the Xanmod kernel in AUR (from the binary sources). My system is Manjaro. The original package maintainers need the binaries in /boot to have a fixed name (their boot manager is not Grub, but syslinux) and each filename modification means that the syslinux conf…

I found the fix and requested the grub Manjaro team to add a small patch. --- /etc/grub.d/10_linux 2023-04-05 16:07:52.000000000 +0200 +++ ./10_linux.new 2023-04-08 08:01:50.714844743 +0200 @@ -262,6 +262,10 @@ if test -e "${dirname}/${kbasename4}.kver" ; then version="$(cat ${dirname}/${kb…

[image] [HowTo] Build your very first custom kernel Tutorials Difficulty: ★★★★☆ warning If you compile your own custom kernel, you’re basically creating your own distro, so before you post any support questions here on the forum, please revert back to the Manjaro kernel …

The problem I’m facing is that the name of the kernel is not correctly detected by Grub in the grub.cfg file. Other than that, the kernel works fine, all modules are correctly loaded, dkms works fine as well. My question goes more towards Grub - and how it fails to retrieve the kernel name, althou…

A Manjaro kernel listing looks like this: /boot ├── amd-ucode.img ├── efi ├── grub ├── initramfs-5.15-x86_64-fallback.img ├── initramfs-5.15-x86_64.img ├── initramfs-5.18-x86_64-fallback.img ├── initramfs-5.18-x86_64.img ├── initramfs-5.19-x86_64-fallback.img ├── initramfs-5.19-x86_64.img ├── initr…

Sorry to insist, the issue is not that I don’t know how to include the kernel version in the image files, the issue is that in the given context (kernel version should not appear in the names of the image files, for the reasons already mentioned) I’m unable to convince Grub to pick the kernel name f…

[image] SoftExpert: echo "${pkgbase}" | install -Dm644 /dev/stdin "${modulesdir}/pkgbase" As I understand your quest - if the ${pkgbase} is empty the script write %PKGBASE% to kver - so perhaps check when writing to kver? Just throwing an idea if ! [[ -z ${pkgbase} ]]; then echo "${pkgb…

I also feel that conditional building might be the quick and easy solution; the main “hint” would be how to detect that Grub is present or not. Do you have any idea in that direction ? Also, the %PKGBASE% error message was a fluke, when I switched from the specifically named image files to the “ge…

This is only ideas It should be easy to detect if grub is installed which grub-mkconfig Which loader is active - I don’t think you can get a conclusive answer? You could use - if response contains ‘BootCurrent’ you know efi is used or not efibootmgr | grep BootCurrent This I got from a web sea…

Testing for the presence of grub.cfg would be a strong enough hint that Grub is used ?

It would - but not conclusive as the file could exist - even if rEFind or systemd-boot is used. And if a user is using EndeavourOS it may create entirely different issues as they use systemd boot and dracut

So, the most solid solution would be to amend the Grub scripts to search in priority for the .kver file content - which would make sense, actually; these files exist only to provide this exact information, right ? And if they do not exist, then Grub continues to parse the file names …

Custom kernel version is not correctly detected by Grub

Support AUR

Olli 7 April 2023 05:23 2