Comment # 77 on bug 1224773 from Imo Hester

(In reply to Alberto Planas Dominguez from comment #76)
> (In reply to Imo Hester from comment #75)
> 
> > There seems to be a new initrd which matches the date and time of the driver
> > installation (snapshot 4) which is also used in the latest boot entry but
> > for some reason it seems not to contain the nvidia driver modules but
> > nouveau seems to be black listed now.
> 
> If you generate the initrd manually, do you less the modules included?
> 
> dracut --reproducible --force /tmp/initrd-0 6.10.9-1-default
> 
> you can use lsinitrd to inspect it
> 
> lsinitrd /tmp/initrd-0 | grep -i nvidia

I need to do a correction to my previous reply.

In fact the driver installation did worked just fine for some reason the MOK
enrollment for secure boot never happened. I had to disable secure boot for a
quick test and the driver is now loaded.

Whcih lkeaves us with the following issues:

- GPG repo key is not imported automatically and the user has to do this after
adding the repo and before rebooting the system other wise the health check
will get stuck in a boot loop
- TPM predictions are not updated on it's own
- Seucre boot MOK enrollment seems to be not happening.

The later I tested with Kalpa where the MOK enrollment worked as usual. After
installing the driver and rebooting I was prompted to enroll the MOK and the
driver was loaded afterwards.
I know Kalpa is very different from Aeon but I just had it at hand as I am
running it on this very same machine.