Today I needed to do a clean install. I downloaded and installed the distro as usual choosing similar installer options as I did in the past (however I didn’t install CUPS this time because idk what’s up with that vulnerabilities).

After a reboot and fixing some systemd-boot freeze issues in BIOS, the system started and the GDM login prompt appeared without any issues. But there was no usual gear icon in the corner that lets you choose between Wayland, X11 and GNOME Classic modes.

I tried to log in but I got my usual Wayland issue (2/3 of the screen is black and 1/3 is artifacting). So I needed to switch to X11 to figure out if I can do anything about the issue this time.

I rebooted to fix the display issue and entered CLI mode (ctrl + alt + f2). I checked for xorg packages and they were indeed installed. However doing startx gave an error about XAuthority not being configured and launched an empty session with 3 or 4 xterm windows.

For those thinking of the 61st /usr/lib rule, I do not have an NVidia GPU so that’s not the issue.

So, all of that made me think that new releases of EndeavourOS come with the stupid X11-less version of GNOME. Can I add the support myself via CLI or do I have to install an X11-only DE and use that to compile a version of GNOME with mandatory X11?

EDIT: everyone said that I should change the hardware but I figured out a fix myself. It turned out it was actually a distro issue.

  • GolfNovemberUniform@lemmy.mlOP
    link
    fedilink
    arrow-up
    1
    ·
    5 days ago

    What’s your hardware because I have had Wayland distros boot on laptops with old 900m nvidia GPUs without such a weird display bug.

    AMD A10-4600M and HD 7670M which is suspected to be dead. On Windows disabling integrated GPU caused the system to slow down a lot and have minor artifacts sometimes. I think the VRAM is dead. Though games work fine smh.

    You also said its your usual Wayland issue what other desktop environments have you used that have that same issue?

    GNOME, KDE and Hyprland. Though usually this bug only happens on suspend, logout or switching between X11 and Wayland without a reboot. This time I can’t even get to the desktop.

    • NullNet@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      1
      ·
      5 days ago

      I suspect it may be dieing too. But that’s also some pretty old hardware. Hell AMD abandoned driver support 8+ years so even if it wasn’t dieing support is gonna be hit and miss for such old laptop hardware.

      • GolfNovemberUniform@lemmy.mlOP
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        5 days ago

        Well I don’t have money for $2k laptops like absolutely everyone assumes here. The thing is that it was working before and it does work on Ubuntu live USB so it’s most likely a Wayland setup issue. Trying to say it’s old hardware just to protect Wayland is not a decision I can support in any way.

        • NullNet@lemmy.blahaj.zone
          link
          fedilink
          arrow-up
          3
          ·
          5 days ago

          I’m not sure where you live or the economics to speak on that but it’s 12+ years old from an era of amd hardware has iffy at best. It’s not something I’d recommend to use a rolling release distro on. Or even something graphically intensive as gnome or KDE. You don’t have to trash it but I think you should temper your expectations and use something thats still x11 maybe an LTS Ubuntu release