What nvme changes happened between kernel 5.15.1 and 5.15.3?
by Richard Cranium from LinuxQuestions.org on (#5S5ZQ)
I apologize for the too broad subject line.
I use LUKS to encrypt the physical volume of my LVM setup on this laptop. I always use the generic kernel with an initrd.
On this laptop, I had updated my Slackware64-current system on November 6, 2021 with a new kernel and an initrd based on it. That initrd worked (and is working now, as a matter of fact).
I recently upgraded this system and build a new initrd based on the 5.15.3 kernel on November 18, 2021, with that kernel and an initrd based on it. That initrd does not work; futzing about in the resulting command line tells me that the nvme device defined as the luks device doesn't exist at all when that bit of the init code executes.
That was a bit of a surprise and I wonder if anyone else has seen this problem.
I use LUKS to encrypt the physical volume of my LVM setup on this laptop. I always use the generic kernel with an initrd.
On this laptop, I had updated my Slackware64-current system on November 6, 2021 with a new kernel and an initrd based on it. That initrd worked (and is working now, as a matter of fact).
I recently upgraded this system and build a new initrd based on the 5.15.3 kernel on November 18, 2021, with that kernel and an initrd based on it. That initrd does not work; futzing about in the resulting command line tells me that the nvme device defined as the luks device doesn't exist at all when that bit of the init code executes.
That was a bit of a surprise and I wonder if anyone else has seen this problem.