GNOME has been transitioning away from x11 for awhile now I think the fedora 41 is now Wayland only. What's your hardware because I have had Wayland distros boot on laptops with old 900m nvidia GPUs without such a weird display bug. You also said its your usual Wayland issue what other desktop environments have you used that have that same issue?
this post was submitted on 31 Oct 2024
20 points (100.0% liked)
Linux
48012 readers
965 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
fedora 41 is now Wayland only
Really, is it???
Edit: Yes it really is, amazing news
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.
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.
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.
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
i hit the easy button on my latest setup with a linux laptop from a linux manufacturer complete with its thier own OS with its own paid maintainers and reading your post reminded of the efforts like this that i don't do anymore because of that easy button.
it's been 5-ish years for me so bare with me while i try to catch up while we troubleshoot this together:
i'm unfamiliar with endeaverOS; is it a redhat or debian variant; which release/version?
what's the nvidia gpu model and are you planning on sticking with wayland and gnome?
Ok now people are trolling me in return. Great.
i don't understand
I highly doubt that but, in case you're telling the truth, let me explain.
EndeavourOS is popular and based on Arch Linux which is another popular rolling release distro. Rolling releases don't have actual releases btw. They just update ISOs once in a while and call it releases.
What was a red flag for me in your message was the part about NVidia. I literally said my GPU is not NVidia and you asked what NVidia GPU I had. That sounded very much like trolling.
Also I think I saw you reply to one of my joke comments so I thought this could be your own one.
thanks for explaining and i think i can understand your perspective.
if i understand you correctly: the lemmyverse has likewise made me weary and i had the realization that my paranoia of trolls where at an all time high because of the election.
i read through your post quickly the first time about because of that paranoia and made many assumptions based on my own experiences. as i said earlier; i haven't touched this area of my knowledge in several years and all of the questions always seemed to involve the word nvidia in the past and i assumed this was one of them.
i'm geniune in my effort to reach out and i think can prove it by trying to help: we need more information. Do you have access to the system's logs that would contain the package installation details?
Ok, mister/miss, thank you for such an advanced explanation and absence of fight creation.
Do you have access to the system's logs that would contain the package installation details?
I have access to the system via CLI but idk where I can find the logs. After all I don't even know how to use curl or grep. I'm not a very advanced user.
i'm going to assume that endeaveros is using systemd so you'll need journalctl and sudo at a minimum.
do you have access to both? as in can you run both commands?
I can run all commands. I just can't start the GUI. I'd also assume that commands like btop (TTY tools that require full color or image support) won't work.
Also I can't access anything after a GUI login attempt without a reboot so if the logs aren't saved, I can't access them.
in your shoes: i would run journalctl -f to watch the logs scroll by on screen in one virtual terminal (whatever the systemd equivalent is nowadays; it was alt+ctrl+f1 through f7 back i the sysv-init days) and try to log in again on the base xserver virtual terminal and try to watch for errors/failures/warnings messages from that those scrolling logs.
journalctl is a unifiied logging system that comes with systemd so your logs are likely to persist there and it has built in tools to help you narrow it down if you see anything in the logs.
When I try to log in, the screen goes black with artifacts and switching to another terminal to see logs is impossible.
when you use an xserver, it occupies one of those virtual terminals that i referenced in my last message.
most distros use 7 virtual terminals and the xserver is usually dedicated to one of them and that means you can use the keyboard shortcuts of alt+ctrl+f1 through alt+ctrl+f7 to switch from your xserver and into a bash prompt where you can then log in without the xserver and execute that command to look at the logs.
you can toggle between all 7 terminals at any time without impacting each other; you can use those keyboard shortcuts to help you troubleshoot this and all xserver problems in an "alt-tab" like fashion switching back and forth between the xserver and six other terminals where you can do things like execute commands; look at logs; & modify configs.
I don't think you understand what I say so I guess you won't be able to help me.
your call and good luck