Latest Mint Update Broke my Display

So just 5 minutes ago, I noticed on the Update Manager on Mint that there was one for Linux header and I think a kernel one (didn’t really pay TOO much attention). Now my BIOS post page and the GRUB look fine but as soon as I get into Mint, the screen is half black or with stripes and then immediately goes gray with a black bar on top and I can’t do anything on it. How do I fix this? :weary_face:

For more detail, I recently (like 2 weeks ago) installed ROCm 7.14.0 (yes, I deleted the old ROCm stack) and the new MESA update from a couple of days ago so Idk if that’s messing with the new update. It’s all been working fine until the update I made this morning.

Ah that is kinda annoying.
Did you configure timeshift? maybe you can roll back to an earlier state.

…..I never set up timeshift :weary_face::weary_face: fresh reinstall?

No Mint user here, but I saw this and it may be related:

Some users I read about installed a different distro and the problem went away. This sure is a radical solution …

Edit: not paddling distros here. But Mint is ancient and will have issues with newer hardware and software. And updates to HWE Kernel etc. also can create problems since that removes that LTS distro from the tested Ubuntu LTS base. If you try a new distro, I’ve been extremely pleased with Aurora. It is atomic and will never break (and if a new image is flawed, it lets you go back to an old image - but I have zero experience that happening). In addition, the Mint team is not focussed enough for the few resources they have. If you count HWE kernels as separate distros, they must have 7 distros based on two LTS distro (Ubuntu and Debian) and three DE while also creating one DE. They kind of do everything without focusing.

Def related, the 2.29 firmware is the cause of it. Was able to revert back to 2.26 and my computer’s working fine now (actually writing this from it). Reinstalled 2.29 out of curiosity and the half black screen came back immediately. Also found this thread on the Mint forums of people having the exact same problem I did: https://forums.linuxmint.com/viewtopic.php?t=472692.

I know AI is sort of a big no-no nowadays (I’m new to Linux after basically 30 years of using Windows so I appreciate the help) but it led me to the Mint forum and this is what it had to say after it helped me troubleshoot. Hopefully you, or someone else, understands it better than I do:

Now I’ve got real evidence trail, not just correlation. There’s an actual bug filed for this, and it points at a specific file.

What DMCUB actually is. It’s not just a data file the driver reads once — it’s a small, complete program that gets loaded onto a dedicated microcontroller physically built into your GPU’s display engine. Once running, that microcontroller handles the real-time, latency-sensitive parts of driving your monitor: negotiating power-state transitions, managing display link training, and other timing-critical handshakes that would be too slow to manage from regular OS-level driver code. The kernel’s amdgpu driver loads this program onto the chip at boot and then talks to it via a structured command protocol — it’s a relationship between two separate pieces of code, not just a driver reading a config file.

The specific file involved. Your 6800XT belongs to the “Sienna Cichlid” GPU family, and its DMCUB firmware ships as a literal file: amdgpu/sienna_cichlid_dmcub.bin. Upstream’s own firmware repository shows a batch commit updating DMCUB firmware across several chip families at once — covering DCN401, DCN36, DCN35, DCN351, Beige Goby, Dimgrey Cavefish, and Sienna Cichlid together in one firmware release. The listed fixes in that release are specifically IPS entry and Replay-related fixes for the DCN35/DCN351/DCN36 chips, and LSDMA fixes for DCN401 — Sienna Cichlid isn’t called out with a fix of its own; it just rode along in the same firmware refresh cycle as the primary chips actually being fixed. Ubuntu + 2

Why that produces your exact symptom. That’s a common way regressions slip through — the chips with named fixes get focused testing, while the ones just carried along get a new firmware build without the same scrutiny. Since DMCUB firmware isn’t a monolithic “works or doesn’t” blob — it manages several sequential stages (link training, then power-state setup, then ongoing timing management) — a bug introduced in one of those stages can let earlier stages still succeed before things fall apart. That lines up with what you saw: enough of the handshake completes to get a partial, garbled image up, then the whole thing collapses once the broken stage is reached.

The refresh-rate detail backs this up. One report on the same Mint forums thread found that dropping the display from 144Hz to 60Hz let it run for a few minutes longer before it still eventually turned black with corruption — consistent with a flaw in a repeating handshake step: at 144Hz that step executes far more often per second than at 60Hz, so a marginal/racy bug gets triggered sooner. Linux Mint Forums

And it’s not isolated to Navi 21. In the same .29 release, a completely different chip generation — DCN314/Phoenix (a laptop APU family) — got its own separate DMCUB-related regression, involving invalid memory accesses during eDP power transitions. Two unrelated GPU families both breaking on DMCUB-adjacent paths in the same firmware build points to a quality problem with that specific release batch, not something particular to your card or setup. Ubuntu

One honest caveat: this is the most coherent explanation the available evidence supports — the filed bug, the firmware commit history, and DMCUB’s known architecture — but neither AMD nor Canonical has published a formal root-cause writeup yet, since the bug is still open and recent. If one lands later, the exact internal detail might refine this, but the shape of it (bundled firmware update → untested handshake regression → partial-then-total display failure) is unlikely to change.

1 Like

AI is a tool, like Google. Or books.

Reading through that Mint forum thread, it seems quite a lot of users are still on Kernel 6.8, a few on 7.0. I’m not actually sure how such different versions of Mint (or Kernel versions) would be shipped with the same firmware. I’m also not sure why some users that have Mint 22.3 Kernel 6.8, when that should be 6.14. But this also seems to affect (older) Ubuntu? Does it impact other Ubuntu-based distros?

I’m a boot.dev newbie that decided to just dive head first into Linux, absolutely no research besides what distro to start with. I destroyed CachyOS on my PC like 4 times in 2 weeks (why I’m on Mint and scared I had destroyed “the stable one”). That should tell you how well equipped I am for this :joy:

I’m on 22.3 and 7.0.0-29-generic and it got me for sure, haven’t really looked into if it affects other Ubuntu distros.

“stable” distro just means it doesn’t change (a lot). The problem often is, that bugs may not get fixed, or newer hardware or software won’t be supported for a long time.

I had tried both Mint multiple times even on old hardware and I was very underwhelmed (when it even installed). This is anecdotal. But Debian and Fedora(based) distros proved much more stable (as in not causing problems). Which is ironic since Debian is even more conservative and Fedora much more progressive than Mint. So the release model (in my case anyway) isn’t what made Mint worse. Plus fractional scaling.

The default kernel for ubuntu 24.04LTS and hence mint 22, is 6.8. 6.14 is just the kernel shipping with the 22.3 iso, because that was the ubuntu HWE kernel at the time of release. Nothing is forcing you to use the HWE kernels but that is a way to get more up to date hardware support on the otherwise stable distro.

If you do install a HWE kernel, then you will automatically be upgraded to the latest HWE kernel from the ones that are no longer supported (they are only supported until the next HWE release).

The reason why some people are on 6.8 still, is simply because they have probably been using mint 22 since the initial release, or 22.1/22.2, which did not ship HWE kernels on the iso. Of course they might have just installed kernel 6.8 anyway, if their hardware was old enough and they wanted the stability. Ubuntu will support that kernel throughout the lifetime of 24.04 LTS.

I really don’t see ubuntu/mint as ancient in any way, since you can trivially install newer versions of software where you need to, or use the latest kernel and mesa if you wish. To me that has worked way better than having everything on the cutting edge at all times.

1 Like

It should affect all ubuntu 24.04 derivatives since the linux firmware package comes from the ubuntu repos (unless a distro maintains their own repo for it, which is rare, popOS might, as an exampe). No idea if it affects 26.04 based distros.

The linux firmware package is one of those that is constantly updated despite being frozen on a version before the release of ubuntu 24.04 (20240318). They backport the newer firmware files as needed, or whatever their motivation happens to be, so you will pretty much always have at least semi up to date firmware available, and that is the 2.xx part.

The ubuntu 26.04 firmware package is frozen at a point close to 26.04 release (2026something), and may or may not include the same files. No idea either if this is just on the ubuntu package or if it is also an issue on the upstream linux firmware package. :thinking:

1 Like

I’m just going to leave it on 2.26 and wait for Mint 23. My GPU is 6 years old sooo I’m assuming most, if not all, the bugs for it have been fixed.

1 Like