Page MenuHomeSolus

Kernel 5.14.12 doesn't display LUKS passphrase screen
Closed, ResolvedPublic


When booting with 5.14.12-200 kernel a blank screen is shown. After entering the correct passphrase for LUKS Solus does start. It works when selecting the previous kernel (5.14.10).

It probably is caused by changing CONFIG_FB_SIMPLE from y(es) to m(odule) [ ].

Event Timeline

darkness created this task.Oct 16 2021, 9:28 AM
darkness updated the task description. (Show Details)Oct 16 2021, 10:27 AM
JoshStrobl added a subscriber: JoshStrobl.EditedOct 16 2021, 11:06 AM

While I do not have this issue on my LUKS-based system, it does appear that a relevant change was made in 5.14.12 and this change has resulted in some other issues coming to the forefront.

JoshStrobl triaged this task as High priority.
JoshStrobl edited projects, added Software; removed Lacks Project.
JoshStrobl moved this task from Backlog to System and Configuration Fixes on the Software board.

@darkness If you don't mind testing before I commit to rebuilding all the separate drivers and modules, please run the command below. If you are using proprietary graphics, VirtualBox, broadcom-sta, etc. though do let me know, as those will not work due to lack of rebuilds against release 201.

sudo eopkg install
JoshStrobl changed the task status from Open to In Progress.Oct 16 2021, 11:54 AM
JoshStrobl lowered the priority of this task from High to Needs More Info.

I'm running NVIDIA Binary Driver (470.63.01-407) unfortunately.

JoshStrobl added a comment.EditedOct 16 2021, 12:19 PM

Alright, I'll cook that up for you as well and reply again with further instructions when that is hosted and available for installation.

@darkness Instructions below:

sudo eopkg install

If you have nvidia-glx-driver-32bit installed, you'll also want to run:

sudo eopkg install

With all of them installed I see the LUKS prompt again :) .

Yay, thanks for testing and filing the issue. Going to wait on some validation from some fine folks on the forums as well that encountered the same issues, but should get the kernels pushed out within a few hours if everything works out.

Now deployed to stable repo.