For the first time I am actually switching my main PC from Windows to Linux.

Problem: When booting into Fedora there was no display output, I changed it to safe graphics to install everything and that fixed it but after the install finished I tried turning it back off and there was still no display output

What I have already tried: I’ve tried installing drivers and everything I could find although that shouldn’t be the problem since I have an AMD 6700xt and Fedora comes with AMD drivers built in. I also tried Installing Linux Mint thinking maybe the distro was the problem but it came up with the same issue.

And if anyone suggests it no there is no way I am going to daily drive on safe graphics.

Edit: I am dual booting on a single 500gb ssd with windows already installed on the other half of the drive, not sure if that would be the problem. Also a similar problem was happening on windows if I left the screen in login for too long without signing in the display would show no signal and it wouldn’t wake up if I moved my mouse or clicked or pressed any keys.

  • eldavi@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    11 days ago

    Do you see any errors/failures/timeouts/etc in the logs when you use journalctl?

    • pbjamm@beehaw.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 days ago

      Fore sure more details needed. I run LMDE6 on my system and its RX7600 works perfectly out of the box.
      currently kernel 6.10

    • pineapple@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 days ago

      Yeah there are a lot although I would still consider myself a beginner at Linux and the terminal so I’m not really sure what the logs mean and which ones specifically I should be looking for.

      • eldavi@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        11 days ago

        unless you’re using a very old or niche distribution, all of your logs are centralized in to a single space and the command journalctl will let you look at them.

        in your situation i would use the command journalctl -f to get a live action printout of all the things that are happening as you try to start your x server and you can look through them to find messages in the logs that contain something like “failure” or “error” or “timeout” to find clues as to what’s causing your problem.

        you don’t need the xserver to run linux and most distributions give you 7 virtual terminals that you can log into without the xserver and each one can be accessed using the keyboard combinations alt+crtl+f1 through alt+crtl+f7.

        when i used to be in situations like yours i would log into two virtual terminals. i would use one of them to run tail -f $logname and the other to start the xserver. tail -f $logname is the older deprecated version of journalctl -fand they both show you what’s happening in your computer as it occurs. you’ll likely only need to see it once or twice to get a sense of what’s happening and what the interval looks like and you can accomplish something similar if you keep track of your own timestamps by hand and then look through the logs searching for those timestamps in the logs.

        share the log messages with errors/failures/timeout/whatever in them and we can both look for clues using google or ai.