After the latest update I no longer get a prompt for the encryption password, it stays on the manufacturer's logo. I guessed entering the password might work (after multiple reboots), and it did. Anyone else?
Budgie DE

    murbert After the latest update I no longer get a prompt for the encryption password, it stays on the manufacturer's logo. I guessed entering the password might work (after multiple reboots), and it did. Anyone else?

    I just updated Budgie and rebooted. No issues at all.

    When you say "I no longer get a prompt for the encryption password, it stays on the manufacturer's logo." I'm assuming that you mean you are not getting to the login screen and login password, but instead getting stuck at the OEM logo. Is that correct? Are you seeing any errors during boot?

    My initial thought is to check for broken packages:
    sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall

    You might also try to revert the upgrade to an earlier state that worked. If nothing else, that will confirm that the current update is the source of the problem.

        murbert Anyone else?

        I don't do anything worth encrypting, but I've recently had the password prompt hide behind Etcher so quickly that I did't notice it at first. Is is possible that the encryption password prompt is hiding behind another window? Is there anything on the screen that you can move temporarily to take a look?

            ReillyBrogan What GPU do you use?

            Nvidia GTX750

            tomscharbach I'm assuming that you mean you are not getting to the login screen and login password, but instead getting stuck at the OEM logo. Is that correct?

            I get stuck at the HP logo but when I enter the encryption password it proceeds to the login screen normally. I am not getting a cursor/prompt to cue me to decrypt.
            edit to add - I got the prompt before the last update

            WetGeek Is there anything on the screen that you can move temporarily to take a look?

            It is the manufacturer's boot screen, same regardless of the OS I boot into

                  Are you on linux-current? This is probably a regression with simpledrm if anything.

                    Run this, I want to see your kernel log:

                    sudo journalctl -k -b0 --no-pager > kernel.log

                    Then copy and paste the contents of kernel.log to hastebin and then share the link for it here:

                      kaktuspalme Actually @murbert's GPU is still supported by the 515 series driver. The GTX 745, 750, and 750 TI from the 700 series didn't have their support dropped for whatever reason. And anyway they are using disk encryption and the nvidia driver isn't loaded until after the drive is unlocked (it's not built into the initrd as a consequence of how Solus distributes the initrd as part of the kernel packages) so it can't be the cause of the initial text-based output not appearing.

                      murbert what version of the kernel were you using before this update? I imagine 5.15.50 unless you hadn't updated in a while?

                      Anyway, I think I might have an idea of why this failed. Can you download this package and then run sudo eopkg it /path/to/linux-current-5.15.61-217-1-x86_64.eopkg and then sudo usysconf run -f after it. Let me know whether it helps or not.

                      Please then upload the kernel log from that boot. I want it whether the issue is still happening or if it's fixed.

                            ReillyBrogan what version of the kernel were you using before this update? I imagine 5.15.50 unless you hadn't updated in a while?

                            I update weekly so whatever the previous one was.

                              WetGeek I don't do anything worth encrypting

                              I don't either I suppose. It's more of a security thing in case my computer/drive gets stolen. At least they don't get my data this way.

                                murbert You didn't actually mention whether that kernel worked for you or not. The section that I expected to be different because of my changes is different but that doesn't actually mean you got the graphical output in the password entry section.

                                Oh NVM I see that you saying it didn't work got put in the quote section of the markdown.

                                  ReillyBrogan I installed that one and ran the following command like last time, still no decrypt prompt

                                    Well, unfortunately that was the last of the low-hanging fruit to test with. We're going to need to try a bunch of different kernel versions to see which version introduced this issue and then probably bisect our way through that version to find the exact commit that broke it (so that we can revert that commit or otherwise understand what we need to do to fix the issue). From this point on I'm going to be providing 2-3 kernel builds at a time, in each batch please test ALL of them and then for each one provide the kernel log and whether it worked or not. I'd recommend you also have linux-lts (and the matching nvidia package) installed so that you have a working kernel to boot into just in case.

                                      ReillyBrogan I'd recommend you also have linux-lts (and the matching nvidia package) installed so that you have a working kernel to boot into just in case.

                                      I just installed the lts and ran sudo clr-boot-manager set-kernel com.solus-project.lts.4.14.290-186
                                      When booting the HP logo now switches off after a bit and the screen goes black. Still no prompt but a better cue to decrypt.

                                        ReillyBrogan From this point on I'm going to be providing 2-3 kernel builds at a time, in each batch please test ALL of them and then for each one provide the kernel log and whether it worked or not

                                        From tomorrow morning until Friday morning I'll be away from this computer. If you give me anything to test today I will do my best to get to it before I leave, otherwise Friday is when I can do more testing