Checking inside /usr/lib/kernel/install.d/, you can see the mechanisms in place for installing new kernel entries. Not knowing what you did to your config (did you back it up before making changes?), you should check if the entries are being populated properly in /boot/loader/entries/. If they are, you have likely toyed with the BLS config in some way that broke being able to load dynamic entries without mkconfig.

If that is indeed the case, I wouldn't know exactly what you touched to break it, but this discussion forum might give some insight.

If this isn't the problem, it might be helpful to post your grub config minus any sensitive details to help determine what is going wrong.

ChatGPT gave the following. Follow at your own risk. Most important is to check if the file locations are compatible with Fedora.

To automate running the update-grub command after each kernel update, you can create a script and set it up to run automatically. Here's a more direct approach:

1. Open a text editor and create a new script file. For example, you can name it "update_grub.sh".

2. In the script file, add the following lines:

   #!/bin/bash
   /usr/sbin/update-grub
   

3. Save the script file in a location where it can be easily accessed, such as your home directory.

4. Make the script executable by running the following command in the terminal:

   chmod +x /path/to/update_grub.sh
   

5. Next, you can set up a cron job to run this script automatically. Open your crontab file by running:

   crontab -e
   

6. Add a new line at the end of the crontab file to schedule the script to run after each kernel update. For example:

   @reboot /path/to/update_grub.sh
   

7. Save and exit the crontab file.

With these steps, the update-grub command will be executed automatically after each kernel update, ensuring that the new kernel version boots successfully.