https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c65 --- Comment #65 from Imo Hester <vortex@z-ray.de> --- I re-tested the driver installation on another fresh Aeon RC3 install with similar results. The sole issue the 2nd system did not ran into is the TPM issue as the system has no TPM chip and thus uses the fallback mode and is asking for a password to unlock the system on every boot anyway. To summarize the issues observed so far: 1) Installing the driver repository and then immediately reboot will result in a boot loop as the repository key does not get automatically accepted. The Aeon healthchecker will notice an issue and then reboot the system without rolling back. Therefore the "broken" snapshot is booted again and the situation repeats. To circumvent this issue the user has to run any transactional-update packaging command using -c to get into a interactive mode based on the latest unbooted snapshot to (always) trust the repository key. 2) Installing the actual driver package itself does not seem to trigger a rebuild of the initrd file. The user has to do this manually, move the initrd file from /boot/ to the correct location and edit the latest boot entry to use the newly created initrd file. 3) Installing the driver package will break the automatic decryption of the root file system as the TPM predictions have changed. Which is to be expected as the initrd file was altered. Therefore the TPM chip refuses to unlock the system and asks for the recovery key. The user has to input this key on every boot. Also updating the TPM predictions manually does not work either see: boo#1228859. For the 3rd issue I did not yet found a manual solution. All 3 issues apply at least for the G06 and G05 driver package at least for me. For more detailed step by step descriptions feel free to checkout my previous replies. Kind regards, Imo -- You are receiving this mail because: You are on the CC list for the bug.