Comment # 26 on bug 1224773 from Imo Hester

(In reply to Stefan Dirsch from comment #25)
> Thanks for figuring this out, Imo! So it seems 
> 
>   transactional-update initrd
> 
> doesn't work in a consistent way, at least not together with systemd-boot.
> Ignaz will look into this.
> 
> I'm wondering if we're seing two separate issues here. Could you check once
> more by re-installing the KMP if transactional-update initrd is being
> running during that installation (it should!)? I need to know if the initrd
> is just being installed to the wrong location or systemd-boot configuration
> not adjusted correctly respectively. Or if no initrd is being re-created at
> all during KMP installation.

Hey there. I am not entirely sure how to test this so here is what I did:

1) sudo transactional-update pkg rm nvidia-driver-G06-kmp-default
(This removed also *-compute-G06, *-video-G06, *-util-G06, *-gl-G06
2) sudo reboot
3) sudo transactional-update pkg in nvidia-driver-G06-kmp-default
4) sudo reboot
5) cd /boot
6) ll
> total 88476
> drwxr-xr-x. 5 root root    65536 Jan  1  1970 efi
> -rw-------. 1 root root 90530598 Jun  2 07:53 initrd-6.9.1-1-default

As you can see the initrd-6.9.1-1-default is still the one from yesterday which
I manually generated using transactional-update initrd

Also

7) cd /boot/efi/opensuse-aeon/6.9.1-1-default
8) ll
> total 277568
> -rwxr-xr-x. 1 root root 178947935 Mai 25 10:22 initrd-4c6dba516f5f3d230a1f5f1e144106e46c960602
> -rwxr-xr-x. 1 root root  90530598 Jun  2 07:58 initrd-6.9.1-1-default
> -rwxr-xr-x. 1 root root  14641520 Mai 17 13:59 linux-6b13316fa0178df1fd6898c8f96f96ab9ecbbbe1

does not reveal any new initramfs files.

I suppose transactional-update initrd is not being executed or the initramfs is
stored to an entirely different location I did not yet found.

Does this help?