Ryzen 5 3600

RX 580 (Asus Dual 8G)

Like the title says, it correctly identified the monitors by model (Dell U2419HX) and I had multiple options for how I wanted the displays set up (moving them around, duplicating vs. extending, etc).

When I installed to my SSD, it now shows "Unknown Display" and doesn't allow me to change any options (resolution, extending, etc).

They're connected via DisplayPort (one directly connected to mobo, other via MST). This shouldn't play into it, since again, it worked on the Live USB without issue.I've also tried plugging the second monitor directly into the RX580, but that doesn't even turn the display on (the #2 DP port is known good from previous testing)

Checked DoFlicky, nothing available. Running latest version of budgie solus.

Justin Wanting to make sure I understand correctly...

I should run inxi -G on both the live USB and my full install and then compare the drivers?

If they're different, how can I load those drivers to the full install? (pretty new at this. somewhat familiar with command line in *bsd and *nix though)

      Justin They are different!

      Full Install:

      Graphics:
  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] 
  driver: N/A 
  Display: x11 server: X.Org 1.20.6 driver: ati,vesa 
  unloaded: fbdev,modesetting,radeon resolution: 1920x1080~N/A 
  OpenGL: renderer: llvmpipe (LLVM 9.0.0 128 bits) v: 3.3 Mesa 19.3.3

      Live USB:

      Graphics:
Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] 
  driver: amdgpu
  Display: x11 server: X.Org 1.20.6 driver: amdgpu,ati
  unloaded: fbdev,modesetting,radeon resolution: 1920x1080~N/A 
  OpenGL: renderer: Radeon RX580 Series (POLARIS10 DRM 3.35.0
  5.4.12-144.current LLVM 9.0.0
  v: 4.5 Mesa 19.3.2

      So, I do have to enter nomodeset before quiet splash in grub before it'll boot. Otherwise, the screen will go black (and say no signal). When that happens, I have to hit CTRL + ALT + F2 to get into tty.

      What's weird is, when I booted off the Live USB it worked fine -- and it continued to work fine when I exited the Live USB and went into the full install! A reboot of the full install brings the problem right back.

          Did you update your system after the installation?
          If yes check if you have the previous kernel .
          As root you can edit the /boot/efi/EFI/loader/loader.conf to use the kernel you want.
          I hope it will work for you as it dit for me when i installed and updated solus the first time.

          Edit
          You will find the kernels that you have in /boot/efi/EFI/com.solus-project

            DataDrake

            Hmmm. I figured as much. it's the only way I can get into the desktop though. Which is even more confusing, because it should be loading the same drivers as it did on the Live USB, no?

            stylste

            I did update the system, I installed it using a Live USB i downloaded maybe an hour before that. When you say "use the kernel you want", is it as easy as changing that string of text? How do I know what to enter? Are there other steps involved in updating the kernel? Sorry, total noob about that stuff.

                  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.