Just started to happen a few days ago, probably something with the new AI-slop-drivers cause I think I did an update recently.
Idk why my post was flagged as spam, I was literally directed here from the Bazzite terminal error. I’m happy to provide Screenshots of the error, but I cannot launch any games without a complete blackout
dmesg.txt (105.3 KB)
journal.txt (8.0 KB)
Hello I see you are using bazzite? OS or the app store app presumeably, and some kind of experimental fedora based immutable operating system, with an encrypted harddrive, and wayland, and even selinux, pretty much all the things that are antithetical to gaming, and having a good experience.
Every single part of your OS is considered problematic, and for general desktop stability, and especially gaming on nvidia
In other words, you are using wayland(experimental) as well as an immutable fedora based OS(experimental) and my ‘experimental’ is a nice way of explaining to people their system is unstable, and likely to break.
A quick search for the error in your title, suggests the problem is in fact related to nvidia on wayland. (many people have reported problems related to parts of your setup in otherwords)
For nvidia users, wayland has been unstable and problematic for a long time, and honestly if we had more honest testers out there, we would learn it’s problematic on other graphics hardware, but that’s the true nature of the situation.
The best advice we can possibly give to people, is to recommend a stable system, and display server, namely xorg, and especially for nvidia users.
Immutable fedora distro’s are interesting ideally, but are going to give you a ton of problems, such as making it difficult/impossible for individuals(you) to take control of their system, which is exactly how we typically fix PC’s.
What might be a simple fix, in almost any hypthetical example, on a stable base system, is now dramatically more complex/impossible on an immutable distro, and you are essentially reliant on upstream to fix the problems, which in every other computing project in history, has been an unsuccessful paradigm.
Here’s some references I found… with a quick lazy search
users report the problem, combined with wayland, and it might be related to the integrated/discrete combo of graphics cards on laptops, which is related to the BIOS/UEFI configuration
Then, you report that “this seems to have bricked your gpu, youre getting no bios screen now”
First of all, we have no way of knowing what kind of computer you have, if you don’t tell us. And real human beings, like basic general information, as opposed to cryptic programmatic log output.
If we knew, what kind of computer you had, what kind of graphics hardware, what kind of desktop(+display server) that would be the most helpful information, for regular human beings.
If your hardware, is configured appropriately, and nothing visually is out of order, than you may fix your problem by power cycling your system, and then after rebooting, closely examine your UEFI menu, and the options available to you, for changing the configuration of your system,
on a laptop, power cycling requires special esoteric information, that you may require, if that’s what you have, the battery has to be removed, while the laptop is plugged in to a power extension cable that can be turned off(with a grounding pin on the wire(typical in the US, but not all countries)) and then you have to hold down the power button for between 30-60 seconds, to flush the power cells you are able to.
After properly power cycling your computer, you will want to figure out what options are available for disabling the integrated graphics card on your PC, in order to use Nvidia as the primary(and only) graphics card. You may even just reset the configuration options instead.
Then you will want to wield a good live cd installed properly on a USB, if all else fails and you cant boot into ‘bazzite’ a trusty live cd will let you at least use your computer, with good sane default settings (and hopefully xorg) and then you can get a real stable operating system to start enjoying your computer again, I highly recommend non-experimental ‘Stable’ operating systems, with xorg, again, such as Debian/Ubuntu (or even fedora, possibly with selinux disabled, now is a good time for nvidia users to grab fedora live cd’s, before they drop xorg support)
(source: using/testing Gnu/Linux and building PC’s for eternity)
After you fix your hardware issue, and if you want to use Fedora, then I highly recommend to you to use Fedora XFCE+Xorg for the best, and rock-solid+stable experience.
I really like how good gnome+kde look by default, and with little effort required by end users, but in real life practice, using the computer frequently, they have proven to become unreliable/unstable in various scenarios over time.(for a very long time(many years))
XFCE on Xorg in contrast, is so rock-solid and utterly stable, you could run that system 24/7 without issues, until upstream(the distributor) pushes out an update that accidentally breaks with your local system configuration, which happens all the time.(typically related to the kernel+graphics driver)
For Fedora gnome, and probably eventually it’s kde version too, they are in a rush to drop xorg support, similarly to other projects, which is simply disasterous, for our whole community.
This thread for example, is a complete and total waste of time, but here you are, compelled to use an unstable/experimental operating system, and here I am, patiently explaining to you, to stop doing that.
Look I don’t think you’re being serious at all, I read your logs and didn’t see anything that you were talking about, and I really just sought to give you(or anyone) the utmost standard basic helpful advice with the benefit of the doubt, despite the fact that you look like a spammer with the name “junk” as well as “juice” and “420” combined.
It would be helpful to others, to provide general information about your system, and any other relevant information to your problem.
You have to understand, that right now, the internet is full of misinformation surrounding wayland, so it’s really frustrating to me, from my point of view, whenever anyone brings it up, so I feel like I have to explain everything about the situation, because we live in a vacuum, where spammers have free reign, without contest, to create misinformation, due to what is called, the free-and-open internet.
In a typical linux forum, if you bring up experimental usages of the standard software they do support, you will be told virtually the same thing, that they do not support experimental use scenario’s, precisely because it adds so much complexity to the situation.
That’s what I tell people with nvidia, that if they’re using wayland, then yes, there will be significant bugs/crashes/instability, that are dangerous to the software and hardware of the system, because wayland is experimental, and unstable, so at the very least, they should be using xorg, before beginning to complain about the driver malfunctioning.
This is actually the solution posted on cachyOS forums, that I linked to above, which summarily gave the exact same blunt reply that I did, explaining to them patiently, that they should really be using Xorg (the updated, and modern version of X11)
In spite of the log message, this is a bug specific to kwin_wayland (KDE’s compositor for Wayland).
You’ll almost certainly get the same behavior on any distro running KDE and Wayland on your hardware. The occurrence is quite random. Some things, like video games or watching videos, might make it more likely, but it’s difficult to tell if that really makes a difference. It can happen at any time, or not happen at all for days, and then multiple times in a single day.
It does not occur at all under KDE X11, nor with Gnome running Wayland (from what I’ve heard; I don’t often use Gnome myself).
Unfortunately, this bug has been around for years and, judging by the dismissive misdirection of blame in the log message, will not be fixed any time soon… or perhaps ever.
If you wish to continue using KDE Wayland in spite of this, you may find it useful to set up a global keyboard shortcut (KDE settings > Shortcuts, Add New > Command/Script) to run this:
kwin_wayland --replaceIt will restart kwin_wayland, and thus resume refreshing your screen.
Unfortunately, unlike under X11, restarting kwin under Wayland will cause many (but not all) applications to crash. But, at least, you get to recover your system without a hard reboot.
I would recommend using X11 instead.
So to recap the situation, the issue you are reporting, is clearly linked directly to kwin+wayland, and not merely the Nvidia driver, which you obviously are attempting to pin the blame on here. I honestly don’t think youre seriously seeking help, having provided us with precisely ZERO helpful information about your situation: such as a general description of your system/hardware
There’s also no way in hell, you fried your hardware running a couple apps on your computer. This isn’t the 1980’s or 1990’s anymore, in the modern world our hardware is incredibly resilient, and the whole firmware stack aside from the system engineering itself has self-protection mechanisms built in, that prevent your hardware from ever breaking, especially, the nvidia card. Hell, I’ve got cards from nvidia that have run for years 12+ hours a day, non-stop, non-stop heavy workloads, that are 10+ years old, and still rock-solid brand new, ready to serve another custom system build, when I get around to it.