Comment # 27 on bug 1224773 from Imo Hester
Another thing I noticed is, that systemd-boot took over my initramfs
modification to the boot loader entry I did a few snapshots ago.

Therefore I expect the next Kernel update to break the system or at least the
boot process and (hopefully) Aeon will rollback to the previous snapshot.

I attached an archive with the entries for snapshot 34 - 39. As you can see 34
and 35 are still lisitng initrd-4c6dba516f5f3d230a1f5f1e144106e46c960602 as
theri initramfs while every entry after 35 (thus 36, 37, 38, 39) all list
initrd-6.9.1-1-default.
Which is the one I manually moved there and initially modified the entrie 36 to
use this. This changes seems to have been carried over to every following
entry.

Therefore I expect a new Kernel or driver update to break the system. Unless I
re-generated a initramfs manually and fix the boot entry before rebooting


You are receiving this mail because: