vasiliospavlos How do I know what to enter?

Copy the kernel version you want from /boot/efi/EFI/com.solus-project
to
/boot/efi/EFI/loader.conf
e.g.
if in /boot/efi/EFI/com.solus-project folder there is kernel-com.solus-project.current.5.3.18-140
you edit the /boot/efi/EFI/loader.conf file to read
default Solus-current-5.3.18-140
On the next reboot the kernel current-5.3.18-140 will be used

      stylste

      okay, so update.

      I don’t have any of those folders (except boot,
      obviously). I am nearly certain I installed with UEFI in mind but there’s a ‘grub’ folder.

      inside of ‘boot’ there are four archives which appear to be kernel names / versions.

      should I reinstall as UEFI and see if that’s the case?

      Edit: well tried reinstalling as UEFI. That was a colassal mistake. Same issue now I don’t have grub to enable ‘nomodeset’ (black screens, monitors turn off from no signal)

      edit 2: now I can’t even get past my motherboards boot screen. Cool.

      edit 3: the saga continues. I’m running the live USB. Just going to format the SSD and start over (again)

      edit 4: SSD formatted and awaiting instructions lol

        Do you have any other linux dist. instlled on your ssd now or earlier?

          Is there any other disk mounted on the system?
          Edit
          What is the output of
          lsblk
          on the teminal?

            stylste

            I got this error when running sudo dd if=/dev/zero of=/nvme0n1 bs=1M

            dd: error writing '/nvme0n1': No space left on device
            1+0 records in
            0+0 records out
            0 bytes copied, 0.000540503 s, 0.0 kB/s

            edit: I just changed the command to sudo dd if=/dev/zero of=/dev/nvme0n1 bs=1M

            it appears to be running (no errors yet). In top it shows dd running at 90% CPU 🙂

            edit #2: Okay, weird, it ran for a while, but then still gave me an error:

            dd: error writing '/dev/nvme0n1': No space left on device
            953870+0 records in
            953869+0 records out
            1000204886016 bytes (1.0 TB, 932 GiB) copied, 784.706 s, 1.3 GB/s

            I'm learning a metric ton! Now what?

              Install nvme-cli to check your disk for errors
              sudo eopkg install nvme-cli
              and run it
              sudo nvme smart-log /dev/nvme0n1

                It did not like that. TON of "failed" errors when installing the pkg. Like, dozens.

                Says no space left on device. Going to reboot live USB and try again.

                stylste

                here's the output from sudo nvme smart-log /dev/nvme0n1

                critical_warning : 0
                temperature : 45 C
                available_spare : 100%
                available_spare_threshold : 10%
                percentage_used : 0%
                data_units_read : 17,305
                data_units_written : 2,058,962
                host_read_commands : 241,815
                host_write_commands : 2,122,446
                controller_busy_time : 14
                power_cycles : 24
                power_on_hours : 1
                unsafe_shutdowns : 10
                media_errors : 0
                num_err_log_entries : 33
                Warning Temperature Time : 0
                Critical Composite Temperature Time : 0
                Temperature Sensor 1 : 45 C
                Temperature Sensor 2 : 54 C
                Thermal Management T1 Trans Count : 0
                Thermal Management T2 Trans Count : 0
                Thermal Management T1 Total Time : 0
                Thermal Management T2 Total Time : 0

                  stylste

                  output appears to be the same

                  Smart Log for NVME device:nvme0n1 namespace-id:ffffffff
                  critical_warning : 0
                  temperature : 45 C
                  available_spare : 100%
                  available_spare_threshold : 10%
                  percentage_used : 0%
                  data_units_read : 17,312
                  data_units_written : 2,058,962
                  host_read_commands : 241,954
                  host_write_commands : 2,122,446
                  controller_busy_time : 14
                  power_cycles : 24
                  power_on_hours : 1
                  unsafe_shutdowns : 10
                  media_errors : 0
                  num_err_log_entries : 34
                  Warning Temperature Time : 0
                  Critical Composite Temperature Time : 0
                  Temperature Sensor 1 : 45 C
                  Temperature Sensor 2 : 54 C
                  Thermal Management T1 Trans Count : 0
                  Thermal Management T2 Trans Count : 0
                  Thermal Management T1 Total Time : 0
                  Thermal Management T2 Total Time : 0

                    same output as last time:
                    dd: error writing '/dev/nvme0n1': No space left on device
                    953870+0 records in
                    953869+0 records out
                    1000204886016 bytes (1.0 TB, 932 GiB) copied, 759.482 s, 1.3 GB/s

                    I'm trying to understand exactly what this is doing, so let me break it down, tell me where I'm wrong.

                    I'm formatting an empty drive that's never had anything but 2 previous installations of Solus on it in order to get properly load the amdgpu drivers so two monitors will display. And now this brand new Samsung EVO 970 is broken? Which is why we're checking using nvme?

                    How did you formated your disk earlier?