Thanks for the report. A few people have encountered this issue and you can do one of two things to "fix" it.

Workaround #1:

1. Turn on the computer
2. Boot into linux-current kernel
3. Wait the amount of time you usually waited for password entry screen to be visible. You can wait an few seconds to be safe here but I assume you already have a good idea of how long it usually takes.
4. Enter your LUKS password.
5. Hit enter. The display should initialize and show you your login page assuming you put in your password correctly.

Workaround #2:

1. Install linux-lts and the corresponding Nvidia package (most likely nvidia-glx-driver unless you are on nvidia-470-glx-driver or nvidia-390-glx-driver due to having older hardware). You may need to do workaround #1 to get to a point where you can install this.
2. Reboot
3. Tap down to keep the boot menu around. Choose the linux-lts 5.15 kernel and everything should be fine.

Workaround #1 is better if you want to stay on the 6.0 kernel (perhaps you have some hardware that benefits from the upgrade). Workaround #2 is better if all your hardware was already supported on 5.15 and if you need to see the LUKS unlock screen.

Both workarounds are temporary while we figure out how to best solve this. Ultimately the issue is that Solus directly manages the initrd (where the LUKS unlock happens). Our current architecture means that we can't have the Nvidia drivers loaded during this time, so we need to make sure that the kernel has a generic module that can handle display until the LUKS unlock happens. This is at odds with the kernel developers who are trying to modernize their generic drivers since we have to downgrade to the older unmaintained generic driver in order to make it work with Nvidia cards during the initrd.

The best solution is to figure out a way to ensure that Nvidia drivers are present in the initrd, though that's going to take time to figure out with our current architecture and the interim solution is likely that we are just going to use the deprecated driver until that happens.

Can the people experiencing this issue please respond with the following information:

• Hardware (GPU, CPU, Motherboard are the most important)
• Whether your install is using UEFI or BIOS (IE are you using grub to boot or sd-boot?)
• The output of the command cat /proc/cmdline
• The output of the command eopkg info linux-current
• The output of the command eopkg li | grep current

Sure.

• MSI B450I GAMING PLUS AC
• AMD Ryzen 5 2600
• NVIDIA GeForce GTX 1080 (MSI GeForce GTX 1080 GAMING X 8G)
• UEFI

initrd=\EFI\com.solus-project\initrd-com.solus-project.current.6.0.9-222 root=UUID=<uuid1> rd.luks.uuid=<uuid2> quiet loglevel=3 splash systemd.show_status=false rw radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 resume=UUID=<uuid3> systemd.unified_cgroup_hierarchy=0

Installed package:
Name                : linux-current, version: 6.0.9, release: 222
Summary             : Linux kernel image and modules (current)
Description         : The Linux kernel and modules, the core of the operating system
Licenses            : GPL-2.0-only
Component           : kernel.image
Dependencies        : 
Distribution        : Solus, Dist. Release: 1
Architecture        : x86_64, Installed Size: 127.55 MB
Reverse Dependencies: 

Package found in Solus repository:
Name                : linux-current, version: 6.0.9, release: 222
Summary             : Linux kernel image and modules (current)
Description         : The Linux kernel and modules, the core of the operating system
Licenses            : GPL-2.0-only
Component           : kernel.image
Dependencies        : 
Distribution        : Solus, Dist. Release: 1
Architecture        : x86_64, Installed Size: 127.55 MB, Package Size: 116.25 MB
Reverse Dependencies: linux-current-dbginfo virtualbox-current

$ eopkg info nvidia-glx-driver-current

Installed package:
Name                : nvidia-glx-driver-current, version: 520.56.06, release: 440
Summary             : NVIDIA Binary Driver (Current Kernel)
Description         : NVIDIA Binary Driver (Current Kernel)
Licenses            : EULA
Component           : kernel.drivers
Dependencies        : nvidia-glx-driver-common 
Distribution        : Solus, Dist. Release: 1
Architecture        : x86_64, Installed Size: 45.58 MB
Reverse Dependencies: 

@darkness I added eopkg li | grep current to the list of commands. I didn't realize that the nvidia kernel drivers didn't have a rundep on linux-current and thus wouldn't be displayed in the output of eopkg info linux-current.

Also, just so everyone is aware we're planning on doing an early sync once we figure out this issue so that this fix is available ASAP.

@darkness Assuming you aren't using any other addon kernel modules like broadcom-sta and are using the default Nvidia driver can you please test this kernel?

sudo eopkg it https://solus.reillybrogan.com:8443/T10446/linux-current-6.0.9-223-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10446/nvidia-glx-driver-32bit-520.56.06-441-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10446/nvidia-glx-driver-common-520.56.06-441-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10446/nvidia-glx-driver-current-520.56.06-441-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10446/nvidia-glx-driver-modaliases-520.56.06-441-1-x86_64.eopkg

@ReillyBrogan it installed the packages successfully, but it still boots without showing the LUKS screen. I verified that they were newer via eopkg info after the reboot.

/edit: FYI I will not be able to test for the next 24 hours (at least).

In T10446#199377, @darkness wrote:

@ReillyBrogan it installed the packages successfully, but it still boots without showing the LUKS screen. I verified that they were newer via eopkg info after the reboot.

/edit: FYI I will not be able to test for the next 24 hours (at least).

Thanks for testing!

For anyone else with this issue, could you please try the following diagnostic steps and report back so I can continue to narrow this down?

1. After blind booting into the linux-current kernel are you able to switch to an alternate TTY with something like CTRL + ALT + F3? Does it work and display the text console?
2. Can you try appending nvidia-drm.modeset=1 to your kernel command line? To do this rapidly tap the down key as you are booting until the boot menu is displayed. Then select the linux-current entry and hit e to edit the command line. Add the flag at the end and hit enter to boot. Note that the nvidia-drm driver doesn't fully support all the features the main nvidia driver has so expect some things to not work. This is just for testing.
3. Can you try it with video=efifb?
4. Can you try it with video=vesafb?
5. And finally can you install this testing kernel to see if it fixes the issue (make sure you test it without any flags).:

sudo eopkg it https://solus.reillybrogan.com:8443/T10446/linux-current-6.0.9-223-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10446/nvidia-glx-driver-32bit-520.56.06-441-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10446/nvidia-glx-driver-common-520.56.06-441-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10446/nvidia-glx-driver-current-520.56.06-441-1-x86_64.eopkg https://solus.reillybrogan.com:8443/T10446/nvidia-glx-driver-modaliases-520.56.06-441-1-x86_64.eopkg

In T10446#199380, @Teroh wrote:

I cant do any further kernel testing because i need the PC for work for the next days and dont wanna break anything.

Steps 1-4 are temporary and can easily be reverted by just rebooting the PC. There's no risk of breaking anything, you can always power off the PC and power it back on and you'll be right back to where you started. The boot options are not persisted between boots.

Only step 5 will actually make a permanent change to your PC, but even that should be fairly low risk. If you're concerned you can install linux-lts and nvidia-glx-driver and you'll have a working kernel that you can boot into if you run into issues.

Mainboard: Z170XP-SLI
CPU: Intel i7-7700K (8) @ 4.500GHz
GPU: NVIDIA GeForce GTX 1080

 ~ cat /proc/cmdline 
initrd=\EFI\com.solus-project\initrd-com.solus-project.current.6.0.9-222 root=UUID=debf18ad-9fa9-45ee-ae3e-9e2035fe0e49 rd.luks.uuid=b86c3448-6df8-42a9-8042-867ad5f4afd8 quiet loglevel=3 splash systemd.show_status=false rw radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 resume=UUID=b739379f-ad8c-4d87-a902-841ab838bf75

~ eopkg info linux-current
Installed package:
Name                : linux-current, version: 6.0.9, release: 222
Summary             : Linux kernel image and modules (current)
Description         : The Linux kernel and modules, the core of the operating system
Licenses            : GPL-2.0-only
Component           : kernel.image
Dependencies        : 
Distribution        : Solus, Dist. Release: 1
Architecture        : x86_64, Installed Size: 127.55 MB
Reverse Dependencies: virtualbox-current 

Package found in Solus repository:
Name                : linux-current, version: 6.0.9, release: 222
Summary             : Linux kernel image and modules (current)
Description         : The Linux kernel and modules, the core of the operating system
Licenses            : GPL-2.0-only
Component           : kernel.image
Dependencies        : 
Distribution        : Solus, Dist. Release: 1
Architecture        : x86_64, Installed Size: 127.55 MB, Package Size: 116.25 MB
Reverse Dependencies: linux-current-dbginfo virtualbox-current 

~ eopkg li | grep current 
linux-current                            - Linux kernel image and modules (current)
nvidia-glx-driver-current                - NVIDIA Binary Driver (Current Kernel)
virtualbox-current                       - VirtualBox host modules for the linux-current kernel

@siru would you mind following steps 1-4 in this comment? It would be very useful diagnostics information for me. T10446#199378

Are you willing to test a new version of the kernel with a potential fix? If so I'll provide you with the right command to use.

1. Switching to a different TTY does work but the fonts are not readable

5. Installing the packages did not fix the issue for me (I could still boot by just typing the FDE password without prompt)

In T10446#199391, @siru wrote:

1. Switching to a different TTY does work but the fonts are not readable

5. Installing the packages did not fix the issue for me (I could still boot by just typing the FDE password without prompt)

And uname -r definitely shows that you are on 6.0.9-223.current after installing the test packages and rebooting?

2. Fixed it for me -- got FDE prompt displayed. Computer is still on:

~ uname -r                                                                                    
6.0.9-222.current

Should I try 3. and 4. as well?

Hi, I made sure to boot the "fixed" kernel -- it works now! Many Thanks!

~ uname -r
6.0.9-223.current

In T10446#199393, @siru wrote:

2. Fixed it for me -- got FDE prompt displayed. Computer is still on:

~ uname -r                                                                                    
6.0.9-222.current

Should I try 3. and 4. as well?

Yes, 3 and 4 are useful diagnostics information at least.

And it's strange that you're still on the older kernel. Can you do sudo clr-boot-manager set-kernel com.solus-project.current.6.0.9-223 and then reboot?

Okay, with the "222" kernel only 2. works -- 3. 4. do not. Also the "223" kernel works by itself.

FYI we're going to do an extra sync today to get the fix for this out quicker. Anyone who installed the experimental packages will need to perform an extra action after that sync happens so that everything keeps working.

# Update as normal (you should see kernel `6.0.10-224.current` get installed)
sudo eopkg up
# DON'T REBOOT YET
# Re-install Nvidia driver:
sudo eopkg it nvidia-glx-driver-32bit nvidia-glx-driver-common nvidia-glx-driver-current nvidia-glx-driver-modaliases --reinstall

# Make sure that the Nvidia kernel module is in the correct place:
stat /lib/modules/6.0.10-224.current/kernel/drivers/video/nvidia.ko.zst
# As long as you see output that's not "No such file or directory" you're good

# Reboot

# If for whatever reason you are still on an older kernel you can run the following command to fix the bootloader configuration
sudo clr-boot-manager set-kernel com.solus-project.current.6.0.10-224

The sync a few min ago fixed the issue for me.

Thanks for the quick work on it.