https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c2 Richard Brown changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|qa-bugs@suse.de |screening-team-bugs@suse.de Assignee|rbrown@suse.com |screening-team-bugs@suse.de Component|Installation |3rd party software Product|openSUSE Aeon |openSUSE.org Version|Current |unspecified --- Comment #2 from Richard Brown --- Not an Aeon specific bug, nor a package in any Aeon-supported/maintained repo Looks to me that the packaging of the NVIDIA package is wrong /var/ should be avoided when packaging for any transactional distribution (ie Aeon, MicroOS, SLE Micro, etc) because the whole premise is that such systems don't change during runtime, whereas the whole premise of /var is for data that needs to change at runtime This is why transactonal-update doesn't mount var during the update, hence the observation in Comment #1 /usr/share/$FOO seems like a more natural and correct location for NVIDIA's public keys, as I assume they're not meant to change at runtime. Assigning to the appropriate category and a commnuity packager who may be willing to help -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c6 --- Comment #6 from Benjamin Sabatini --- The 555 driver was released a few hours ago, so hopefully, the fix was in before. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c9 Imo Hester changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED --- Comment #9 from Imo Hester --- Hi there, I just updated an old MicroOS Desktop system to Aeon RC 2 using the Aeon Installer. Unfortunately I need to report that nVidia drivers still can't be installed on Aeon RC2.

Mai 31 07:32:47 localhost systemd-udevd[1106]: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service

It seems it still can't import the MOK's for the nVidia driver. Looking up https://en.opensuse.org/SDB:NVIDIA_drivers#Secureboot Revealed: 1) The Wiki is outdated, as the MOKs has been moved to "/usr/share/nvidia-pubkeys" according to this ticket but 2) The directory "/usr/share/nvidia-pubkeys" does not exist on my system at all. Neither does the old "/var/lib/nvidia-pubkeys" I uploaded the full boot-log file of my current system. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c11 Imo Hester changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #11 from Imo Hester --- I think there is another issues with the driver. After disabling secure boot in my system the nvidia driver still does not get loaded because of nouveau it seems:

Mai 31 07:55:03 localhost kernel: NVRM: GPU 0000:01:00.0 is already bound to nouveau.

After manually running:

sudo transactional-update initrd sudo reboot

It still seems not to pickup the file "/usr/lib/modprobe.d/nvidia-default.conf" Which states:

blacklist nouveau

I'll attach a 2nd boot log -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c13 --- Comment #13 from Imo Hester --- Created attachment 875235 --> https://bugzilla.suse.com/attachment.cgi?id=875235&action=edit transactional update initrd log file -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c26 --- Comment #26 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? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c28 --- Comment #28 from Imo Hester --- Created attachment 875264 --> https://bugzilla.suse.com/attachment.cgi?id=875264&action=edit SystemD Boot entries 34 till 39 -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c36 --- Comment #36 from Imo Hester --- Just want to add some details: Unlike anticipated I did not require to re-fix the driver as I updated from Kernel 6.9.1 to 6.9.3. Somehow the kernel update itself or systemd-boot build a new initramfs for 6.9.3 AND the modprobe rules where included as well as put into the right location:

cd /boot/efi/opensuse-aeon/6.9.3-1-default/ ll -rwxr-xr-x. 1 root root 95383117 5. Jun 19:49 initrd-56b6a5223453a59edeb15854dc0ed58154332456 -rwxr-xr-x. 1 root root 14625136 30. Mai 10:00 linux-58d6d3c7cc8c858e239a8137fe4faa5b2fea52bf

vim /boot/efi/loader/entries/opensuse-aeon-6.9.3-1-default-50.conf # Boot Loader Specification type#1 entry title openSUSE Aeon 20240531 version 50@6.9.3-1-default sort-key opensuse-aeon options quiet loglevel=2 systemd.show_status=no console=ttyS0,115200 console=tty0 vt.global_cursor_default=0 ignition.platform.id=metal security=selinux selinux=1 root=UUID=42fc02eb-e038-424f-b5a5-aed45173338d rootflags=subvol=@/.snapshots/50/snapshot systemd.machine_id=7b5e214ac1c6413b9145cd262341e2fe linux /opensuse-aeon/6.9.3-1-default/linux-58d6d3c7cc8c858e239a8137fe4faa5b2fea52bf initrd /opensuse-aeon/6.9.3-1-default/initrd-56b6a5223453a59edeb15854dc0ed58154332456

So it seems at least updating just the kernel seem not to break things after the initial fix. A new initramfs is somehow generated correctly and picks up the additional modprode confs. I'll keep this thread updated as soon as driver 550.90.07 lands in the repos and get's updated. Probably that will require the re-fix as required initially as it might be a similar situation as like on a new system with a newly installed driver package. -- You are receiving this mail because: You are on the CC list for the bug.