Tried to install Solus on HP Pavilion 15-dk0xxx with core i5-9300H, gtx 1050(3gb), 8Gb DDR4, Samsung 256GB PM981 NVMe PCIe M.2 +Seagate Barracuda 1 Tb ST1000LM049 SATA.
Solus 4.0 starts from usb flash drive and succsessfully installs on this laptop but when I upgrade it with "sudo eopkg ur" then "sudo eopkg up" it upgrades to Solus 4.1 then freezes with no respond. Even if I reboot laptop, after 0.5-2 minutes from start system freezes again with no respond. And I didn't even try to install nvidia drivers. Don't know what to do with this.
If I try to boot and install Solus 4.1 from usb drive(4.1 version not even always starts from usb drive), the Solus installer will freeze after finding my Seagate drive while scanning all available drives(where to install Solus, same with Gparted - it just endlessly looking for any drive). Even if it finds all drives, it always freezes(or endlessly tries to write something) after trying to start installing on my SSD drive - I don't know why either.
Tried a few USB and a few times with different ISOs and even tried to start installation from my phone - nothing new.

    JLoGukA

    You might be running into the NVME issue that some encounter on the current kernels. I believe 5.9+ have patches for it, so you might need to wait until 5.10 gets out of RC status and try again then.

        Saijin_Naib I'm no expert, and there could be other issues with NVMe drives I've not seen mentioned, but the issue you mention would be the ONE thing I'd be confident ruling out. The devs have deliberately held back the current kernel to 5.6 because of this issue, and they've prepared to update the current kernel only for when 5.10 gets out of RC.

            nathanpainchaud I'm no expert, either, but I agree.

            I think that NVMe issues can be ruled out, for two reasons:

            (1) As you note, Solus 4.1 installation does not use kernels with the NVMe/kernel issue. The 4.1 live USB installs kernel 5.4.12, and that kernel is updated to 5.6.19 during post-installation updates. The NVMe conflicts occur in kernels 5.7, 5.8 and (to some extent) 5.9.

            (2) I am running Solus 4.1 with kernel 5.6.19 on a Dell Optiplex Micro 7070, 256GB Samsung NVMe PM 981a PCIe M.2 drive, and have been running Solus Budgie (initially 3.9999, then 4.0, then 4.1) on that drive for almost a year without issues. I could be wrong, but I find it hard to believe that there is a significant difference between the PM 981 that JLoGukA is running and the PM 981a that I am running.

            I'm wondering if something is going on with the +Seagate Barracuda 1 Tb ST1000LM049 SATA. SATA drives shouldn't cause a problem, and the ST1000LM049 is commonly used, but what JLoGukA is describing does sound like a drive/controller related issue.

                Saijin_Naib You might be running into the NVME issue that some encounter on the current kernels. I believe 5.9+ have patches for it, so you might need to wait until 5.10 gets out of RC status and try again then.

                No the NVMe issues that were fixed before 5.10 were regressions seen in kernels after the one we have as our linux-current.

                    tomscharbach
                    Thank you for respond! I wish I could disable the Seagate drive in BIOS settings, but there's no such setting... I believe too that there's some problem with this drive because recently while I have been working on Windows 10(it is installed on ssd), the GPT structure of this hdd has been somehow messed(no viruses) with data remained untouched so I could find almost all files with programs like R.Saver.
                    Don't know if there are any issue with NVME since Solus 4.0 runs well on my laptop without updates.
                    I'm going to try to disable hdd physically and if no luck, will wait for stable 5.10 or any news about Solus upgrades.

                        JLoGukA My guess is that the Seagate is the issue, based on what you said about the GPT mess on that drive. I had that (good NMVe M.2 drive and 1TB 2.5-inch SATA with messed up GPT) happen on a Windows 10 computer, and it screwed everything up until I cleaned the offending hard drive and rebuilt it from ground up using diskpart.

                        Since you have Windows 10 on the M.2 SSD, you might be able to use diskpart and/or the Disk Management tool to clean the Seagate drive and rebuild it without opening up the laptop. I've done that a number of times over the years.

                        But if I were in your shoes, I'd do what you suggest -- go into the laptop and physically disconnect and/or remove the Seagate and see if that solves the problem. If it does, then you can clean and rebuild (or simply replace) the Seagate drive.

                        Since it looks like you are going to open up the laptop to disconnect the drive, and it is possible that the Seagate drive itself might be going bad, you might consider replacing it with a 1TB SSD. You can pick up a name-brand (e.g. Samsung, PNY, Sandisk, WD) 2.5-inch 1TB SSD for around $100 US these days.

                        JLoGukA Don't know if there are any issue with NVME since Solus 4.0 runs well on my laptop without updates.

                        There won't be any NVMe issues installing Solus 4.1. The USB installs kernel 5.4.12 (which does not have the NVMe issue) and upgrades it to kernel 5.6.19 (no NVMe issue) during the post-installation upgrades. The Solus team skipped over the kernels with the issue (5.7, 5.8 and 5.9). Solus 4.2, when it is released in a bit, will use kernel 5.10 (again no problem). Go without fear on that score.

                              tomscharbach, JoshStrobl
                              Hello, just got around removing my hdd from laptop then tried to install solus - still no success... Installer just never ends looking for my ssd although Gparted is able to see it now without any further problems.
                              Maybe it is really NVME problem. Can it be because of TPM 2.0 or Intel Software Extensions? Going to try to disable them.
                              This is my SSD:

                              ![/SPOILER][SPOILER]
                              (src)

                                  I Disabled TPM, Intel software extensions, virtualization, secure boot - no success... Now I'm just curious why. Will try to install via PXE server.

                                    JLoGukA The Samsung M.2 NVMe is in the computer, and the Seagate Barracuda 1 Tb ST1000LM049 SATA is NOT in the computer. You are trying to install to the Samsung M.2 NVMe using a Solus 4.1 Live USB. Gparted can see the Samsung. The Solus Live USB works when you boot, but when you try to install Solus 4.1 off the live USB, the Solus installer can't find the Samsung. You are attempting a UEFI/EFI install according to Solus instructions (Secure Boot off, UEFI install, ACHI/RAID settings and so on). Solus 4 installs, but Solus 4.1 does not. Is that all correct?

                                    Two questions:

                                    (1) When you go into BIOS (F2 while booting on Dell, but I don't know what it is the HP pre-boot call is) does the UEFI recognize the Samsung? I'm guessing that it does.

                                    (2) With the Solus Live USB up and running, open the File Manager, click on "Other Locations" and look down the list that opens. Can you see the Samsung on that list (it should read something like "254 GB volume" and be identified with a /dev/sda3 designation). I don't have a guess here, but on both my Solus computers, the Solus Live USB can see /dev/sda3 on the NVMe SSD drive.

                                    It is the answer to (2) that I am most interested in. If the Solus Live USB sees the Samsung NVMe drive in File Manager, then I have no idea why it doesn't see it during the install. If the Solus Live USB doesn't see the Samsung NVMe drive in File Manager "Other Locations", I'm baffled, but then at least we have a starting point.

                                    I really doubt that TPM of the other things you disabled (other than Secure Boot, which must be disabled in order to run the Solus Live USB and subsequently install) are likely culprits. I have TPM enabled on both my Solus computers, but I'm not familiar with Intel Software Guard Extensions, so I don't know about that as a potential issue.

                                    I have a stray thought that might be -- or, more likely isn't -- relevant. I'm not particularly knowledgeable about HP computers, but about a year ago I installed three HP ELITEDESK MINI PC's at the small railroad museum where I volunteer as the IT guy. The computers had been set up by a QuickBooks/QuickbooksPOS vendor, so all I had to do was hook them up, start them up, get them on the network and hook up printers, scanners and other peripherals. Other than update Windows 10 and clear out all the bloatware that Microsoft and HP love to install, I didn't have to muck around in them. But I notice that on every boot cycle, just when the HP logo showed up, there was a message about "HP Sure Start" or something like that. I didn't know what it was, so I called the vendor and asked what it was and how to get rid of it. The vendor told me that it was an HP pre-boot process to protect the boot and that I couldn't get rid of it. I doubt that this (or one of the other wonderful things that HP loves to put on computers) is causing the problem, but it might be worth a Google if that or something like it is showing up during the boot process on your computer.

                                    This absolutely baffles me. Something is blocking (protecting) the Samsung during the installation process in 4.1, but didn't in 4. It has to be something in the HP pre-boot processes or something in conflict with the 5.4 kernel. It isn't impossible that there is something going on with NVMe, but no NVMe issues have been reported with kernel 5.4. so it is real unlikely.

                                    Yikes! I love mysteries, but you must be tearing your hair out.

                                    I'm hoping that someone with more expertise that I have will read this, and jump in.

                                        tomscharbach Something is blocking (protecting) the Samsung during the installation process in 4.1

                                        Drive in File Manager but not in install not too unusual--sometimes formatting, sometimes compatibility...but valid.
                                        What you said there, though, kind of struck me as a permissions things gone south maybe.
                                        I love mysteries, I have no expertise, and I'd give myself too much credit if I thought half my guesses were right🙂

                                            brent I can see how it might be a permissions issue, but I can also see how it might a drive formatting issue or lots of other things. I have no idea.

                                            I'm going to search Reddit's Solus Project forum and look around the internet to see if I can find anything that might be helpful to JLoGukA, but usually when I do that, I end up digging a hole faster than a mole with a power shovel, ending up more confused than when I started. But I'm going to look, anyway. If you can think of anything, it is bound to help.

                                            I guess, if I were JLoGuka at this point, I would resort to brute force, and do a brand new, destructive (that is wipe out everything on the drive, following the "custom" install method that allows you to delete every partition on the drive before installing) installation of Windows 10 with Windows Media Creator (his computer came with Windows, so it is licensed), creating a clean Windows install that wipes out everything on the drive (volumes, partitions, the whole works) and creates a working Windows drive.

                                            That would, it seems to me, reset the drive's volumes, partitions and so on, wiping out any issues related to the way the drive was affected (perhaps corrupted somehow) by JLoGukA's initial failed update from Solus 4 to Solus 4.1.

                                            And then, after Windows was up and running, I'd try to do a similar destructive install of Solus 4.1 from the Solus Live USB to see if that would work after the drive had been wiped/rebuilt by the Windows install.

                                            That is a lot of work, but it is the only thing I can think of right now.

                                                tomscharbach partition awfulness and residues between 4.0 and 4.1 that lead to tried'n'true brute force (effective if it can be afforded) will remedy this. I'd like to think there was an alternative, too. I agree that more brain power will locate where the fixable part is. Feels like you are close. Done many days with other posters and so many have done many days helping me. Beauty of the forum. Nice of you to help OP.
                                                edit: typo

                                                    brent I guess JLoGukA could accomplish the "destroy the drive to save it" using a Live Gparted Rescue USB, and that might be simpler than the "Windows to Solus" method I would use. I just don't have any experience with the Gparted in that context to recommend it.

                                                    I did some poking around on Reddit's Solus Project forum, and the closest I came was an older post that didn't seem real helpful.

                                                        tomscharbach
                                                        Your idea about wiping all ssd drive is awesome, but I have to tell you that I already wiped it out for clean installation of Windows. Anyway, I don't have any important files there so, why not to do it second time 🙂.
                                                        I really appreciate your effort in helping me and I want to solve that mystery too 🙂
                                                        Gonna wipe the drive in 1 hour

                                                          tomscharbach
                                                          Also, I didn't mention it earlier, but Solus is not first linux distribution that I have problems with. I already tried to install latest deepin - it simply refused to boot. Mint - crashed while installing(maybe because iso file was on my phone - it is unstable to install with this method).
                                                          Ubuntu installer crashed (but when did 3 attempts to install it, on 3rd time it installed successfully, same with Elementary, however it based on Ubuntu...)
                                                          Even tried to install hackintosh - I have got stable(and tested with exact same kexts, drivers and configs on similar hardware) image of BigSur and Catalina. MacOs was installed successfully, but then installer also crashed when it tried to access nvme to apply some updates on existing system.
                                                          I know that I am writing about VERY subjective things that are different for every computer but I've got strong feeling that something is wrong with this exact laptop... Just don't know why. Maybe it finally is nvme but... why when it is only one year old and it's lifecycle is far from end
                                                          And only Windows is absolutely stable on this laptop 🙂

                                                              • [deleted]

                                                              • Post #18

                                                              JLoGukA It definitely sounds like a hardware issue to me. Might be the NVMe drive is actually faulty.

                                                                @[deleted] #45343 yeah.... I think I will replace this ssd with something else later. And wait for Solus 4.2 XD

                                                                  JLoGukA Thank you for respond! I wish I could disable the Seagate drive in BIOS settings, but there's no such setting... I believe too that there's some problem with this drive because recently while Carton déménagement pour livre I have been working on Windows 10(it is installed on ssd), the GPT structure of this hdd has been somehow messed(no viruses) with data remained untouched so I could find almost all files with programs like R.Saver.
                                                                  Don't know if there are any issue with NVME since Solus 4.0 runs well on my laptop without updates.
                                                                  I'm going to try to disable hdd physically and if no luck, will wait for stable 5.10 or any news about Solus upgrades.

                                                                  Yes, sometimes wndows 10 is a problem, but hey we do with it.

                                                                    JLoGukA

                                                                    JLoGukA I think I will replace this ssd with something else later. And wait for Solus 4.2 XD

                                                                    Makes sense. You must be really tired of this ...