Darryl Gregorash composed on 2024-01-22 00:49 (UTC-0500):
Felix Miata wrote:
Darryl Gregorash composed on 2024-01-21 22:56 (UTC-0600):
Andrei Borzenkov wrote:
You confuse "boot previous kernel" with "boot from snapshot".
I think that, if I boot from a snapshot that had a different (previous) kernel version, then I am booting a previous kernel, yes? ;)
I suggested to boot a previous kernel, not an entire previous operating system, which is what booting a snapshot amounts to; to change fewest practical potential failure points at a time, not many. Booting a snapshot facilitates getting back in business quickly well, but not so much isolating or solving a problem arising from updating.
But what is there in anything Marc has posted so far that suggests simply recreating the initramfs file will solve the problem?
He's the one with the problem. We're here to help him solve it. That includes possible troubleshooting steps, one of which is to try regenerating the initrd.
If the kernel update somehow did not complete properly, then I doubt dracut/mkinitrd will resolve the issue.
Maybe it would, maybe it wouldn't. It's a troubleshooting step. We don't yet know what the issue causing the failure is.
Assuming that Marc cannot simply do a system rollback, would it make sense to a) boot into the previous kernel b) do an unconditional update on the following packages: kernel-default kernel-default-extra kernel-default-optional c) reboot ?
Looks like a longer, more complicated series of steps to me, which I'm in no position to test. /If/ he's on an recent installation, or is otherwise using btrfs and snapshotting, whether or not he accepted the partitioning defaults or otherwise configured btrfs and snapshotting, /then/ it's a path he could try. What I suggested would work or not regardless his / filesystem, and whether or not snapshotting is available to him. Your way will require he reinstall all updates or wait for some of those to be installed again, plus new. My way he keeps all the updates unrelated to kernel and existing initrd. Both ways he's using the older kernel and doesn't know what went wrong until he does some troubleshooting. These describe options, not demands. I'm wild-guessing his problem is either kernel backporting introduced a problem with his quite youthful CPU that escaped QA, or more likely, a backport introduced a need for NVidia driver update that has yet to become available, if even recognized. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata