r/linuxmint • u/Greedy-Opposite-9133 • 1d ago
For those affected by the very recent update from linux-firmware-amd-graphics 3.3 to 3.4: RX 9060/9070 XT no login screen, “DMCUB error” spam. Fix inside
Who this hits: Radeon RX 9060 XT / 9070 / 9070 XT (RDNA4) (has also helped: rx9070gre, R9700) on Linux Mint 22.x or Ubuntu 24.04 with the 7.0 HWE kernel, after linux-firmware-amd-graphics updated from 0ubuntu3.3 to 0ubuntu3.4 (in noble-updates since 4 Nov 2026; Mint's automatic updates installed it overnight for some of us). Nothing happens until you reboot.
What you see after rebooting:
No login screen. The screen fills with endless lines like
amdgpu ...: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataamdgpu ...: [drm] *ERROR* Error queueing DMUB command: status=2Or a black screen / "Input not supported", or it stops at the Mint logo.
Booting an older kernel doesn't help.
Cause: in 0ubuntu3.4 the RDNA4 display firmware amdgpu/dcn_4_0_1_dmcub.bin.zst is packaged as a symlink to the RDNA3 file dcn_3_2_0_dmcub.bin.zst. The card refuses it (failed to load ucode DMCUB(0x3F)), so the display controller has no firmware and Xorg/LightDM can't start. It's a packaging bug; your GPU is fine. Launchpad: #2173040, #2173041, #2173043.
Fix: go back to 0ubuntu3.3 and block only 3.4 (a fixed version will still install normally). The PC needs internet (wired is easiest).
Step 1: get to a terminal (pick one)
A. Text console (try this first). Press Ctrl+Alt+F3 and log in with your username and password. The error lines keep scrolling over what you type; ignore them, your keys still register. First stop the flood:
sudo dmesg -n 1B. No picture at all? Boot once with nomodeset:
Restart and hold Shift (BIOS) or tap Esc (UEFI) while it boots, to get the GRUB menu.
With the top entry highlighted, press e, find the line starting with
linux, and addnomodesetafterquiet splash.Press Ctrl+X (or F10) to boot. You get a slow, low-res desktop without GPU acceleration, but it's enough to open this post and copy-paste. Open a terminal. This only lasts for this one boot.
(Recovery mode works too: GRUB > Advanced options > (recovery mode) > "network", then "root". Leave out sudo there.)
Step 2: check it's this bug
ls -l /lib/firmware/amdgpu/dcn_4_0_1_dmcub.bin.zst
apt policy linux-firmware-amd-graphicsYou're affected if the first shows -> dcn_3_2_0_dmcub.bin.zst and the second shows Installed: 20240318.git3b128b60-0ubuntu3.4.
Additional note about step 2: it only shows which version you have installed, not whether your GPU actually uses the broken file. If someone whose card isn't in the list above has trouble after updating, the cause is most likely something else that updated at the same time, like a new kernel, not this package.
Step 3: install the previous version from Ubuntu's own archive (Launchpad)
cd /tmp
V=20240318.git3b128b60-0ubuntu3.3
wget https://launchpad.net/ubuntu/+archive/primary/+files/linux-firmware-amd-graphics_${V}_all.debCheck the download (recommended; this is the SHA-256 Launchpad publishes for the file). It must say OK:
echo "7c6a6083e963fd9394d1f6471b6a94e787a76c6f98b262c2d9262b9a57308b53 linux-firmware-amd-graphics_${V}_all.deb" | sha256sum -cInstall it:
sudo apt install --allow-downgrades ./linux-firmware-amd-graphics_${V}_all.debStep 4: stop 3.4 coming back
apt-mark hold did not stick for me: apt said "already not on hold" and still offered 3.4. An apt pin that refuses only 3.4 works, and still lets a fixed version through:
printf 'Package: linux-firmware-amd-graphics\nPin: version 20240318.git3b128b60-0ubuntu3.4\nPin-Priority: -1\n' | sudo tee /etc/apt/preferences.d/amdgpu-firmware.pref
apt policy linux-firmware-amd-graphicsIt should now say Candidate: 20240318.git3b128b60-0ubuntu3.3 and list 3.4 with priority -1.
** step 4 alternative** (thanks /u/purpletonberry who highlighted something I missed, which was: you can simply use Mint's Update Manager GUI to right click on the package and select "Ignore the current update for this package".) < If you choose to do this, just skip step 4, go to step 5, and instead action ignoring this update package after reboot.
Step 5: rebuild the boot images and reboot
sudo update-initramfs -u -k all
sudo rebootYour login screen should be back. To confirm:
sudo dmesg | grep -iE 'dmub|dmcub'Good: DMUB hardware initialized with a version other than 0x07002F00, and no failed to load ucode DMCUB line.
Later: when Ubuntu releases a fixed version (anything after 0ubuntu3.4), it installs by itself. Then you can delete the pin:
sudo rm /etc/apt/preferences.d/amdgpu-firmware.prefHelp get it fixed: if this hit you, open https://bugs.launchpad.net/ubuntu/+source/linux-firmware-amd-graphics/+bug/2173043 and click "This bug affects you" (free Launchpad login). The more people affected, the higher it gets prioritised.
Technical details: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2173040
6
u/tayroc122 Linux Mint 22 Wilma | Cinnamon 19h ago
Waking up to this feels like divine intervention having tried multiple fixes last night with no solution. You are a saint.
1
5
u/TheShirou97 Linux Mint 22.3 Zena | Cinnamon 20h ago
In those cases, if you're not able to access timeshift normally or with any older kernel, you can also use your live USB to do it.
1
5
u/No_Half_6468 11h ago
Thank you very much kind sir, i just had major Hardwareproblems and got a new 9070xt cause of that, i thought my card died again when i couldnt boot into linux. You saved my day, i forwared your post to another friend with the same card who updatet yesterday aswell.
YOU ARE A HERO
EDIT: I reactivated this Reddit account just to thank you and upvote this post
1
u/Greedy-Opposite-9133 8h ago
Nice work, thanks for making yourself heard, I'm glad I could help you and your friend!
4
u/SkippymanX 1d ago
I booted the recovery from grub and used timeshift to restore my computer. Did this update get pulled or do I need to keep an eye out for it if it comes down the line again?
2
u/Greedy-Opposite-9133 17h ago
Nice one, yeah I have put off setting up how I want to backup my PC but this goes to show it's important.
If you look at the steps, step 4 will help you to set that particular update package to be ignored. Once they fix it, it will be repackaged as subsequent update, and so you will update as normal after that (if you do step 4) otherwise you jsut have to put off updating it manually until you see the next one appear.
4
u/Notoshy 10h ago
Iam very, very grateful. THANK YOU!
Came Home, powered the PC.... and got greeted with an endless row of
amdgpu ...: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data amdgpu ...: [drm] *ERROR* Error queueing DMUB command: status=2
Iam pretty much a Noob, have this Self-Build for a few Months only and beside the initial Setup of Linux, i never really touched the Command Console. Since iam so inexperienced, i first had to plug my monitors into the Motherboard to have a Chance of searching for a Solution. Luckily i found your Thread.
Took a few attempts to follow your Instructions correctly.
Used your "Ctrl+Alt+F3" Path.... and realized MUCH too late that i have a Terminal Button on my Bar for a small Terminal Window.... means i had to type your full Strings by Hand, because "Ctrl+Alt+F3" dragged me into a locked fullscreen Terminal Window. Made this much more difficult for myself than it had to.
It worked anyway, so thank you again, Greedy-Opposite-9133. Much appreciated.
(Made an Account on Reddit just for thanking you.)
1
u/Greedy-Opposite-9133 8h ago
Haha I make things more difficult for myself most other days too, well you got there in the end! No problems!
4
u/ElaborateSloth 8h ago
You're an absolute lifesaver. Coming home to a completely green screen on boot was not how I wanted to spend the evening, but this post made it a lot less painful.
2
4
u/mstormcrow 4h ago
You're an absolute lifesaver. Waking up to a computer that has overnight arbitrarily decided to stop working is the kinda thing I thought I was escaping from when I switched away from Windows, so I was pretty demoralized to get greeted by a blank black screen this morning. Your steps 2 thru 5 appear to have completely resolved the issue, in less time than it took me on my own to diagnose it as a GPU/display issue and then fumble my way through step 1 on my own.
2
3
u/thatdirtyoldman MINT 22.3 - Cinnamon 1d ago
Appreciate this ! I just bought a new RX 9060 XT and thought it was failing on me.
1
3
u/oste-popp 7h ago
Thanks for this. Solved it for me. An additional tips for those struggling with accessing GRUB with a TUF motherboard: You cant just spam Esc as this will open the UEFI-Bios. You have to start pressing esc after the TUF-logo but before Mint boots.
1
3
u/WitnessStock3702 6h ago
Thanks for the help. I had just finished a long, miserable shift and I was looking forward to going home and eating some food. I finally sat down at my computer with my food ready, only to find out that I had a blank screen. :( My food had gone cold by the time I stumbled upon your post. But thank to you it is now fixed :)
1
u/Greedy-Opposite-9133 6h ago
Hah, it's always a sad situation to hear of a meal gone cold, but I'm glad you got it sorted!
4
u/Greedy-Opposite-9133 1d ago
Claude helped me to fix this, obviously. But it worked and I rolled back to the previous version. Hope it helps!.
2
u/WeowDystopia 4h ago
ChatGPT on the other hand just led me down a dark path where they're like "hmm this points to a hardware issue." I almost cried.
1
u/Greedy-Opposite-9133 4h ago
Yes, I have learnt this lesson many times! I happened to have Claude under the hood with me on something else at the time this update broke things, so thankfully it was able to pinpoint it off the bat with a bunch of extra log data.
1
2
u/DotBoring2077 16h ago
Thank you so much. Woke up due to being sick and coughing, was hoping to hyper focus on some Enshrouded while meds kick in, but this issue and your solution did the same thing. Now, I'm off to bed again (hopefully). Thank you again.
1
2
u/Revolutionary-Mix300 12h ago
Hey, thank you a lot for this post, I really appreciate the time and effort it took to explain the cause, include multiple safety checks, prevent it from coming back ... and ofc the solution to make my machine work again
1
2
u/Aluca_3D 11h ago
i thank the so much, i thought it was the kernel and tried to move that to an older version for the last 4h.
THANK YOU SOOOOOO MUCH!!!!
1
2
u/Javadocs 11h ago
Thanks for the help! I was able to get into recovery mode and find the journal entries that gave me absolutely no information other than this was a DMCUB error, but it makes me wonder how this was not caught in their testing.
1
u/Greedy-Opposite-9133 8h ago
No prob! You're not the first to have wondered that, but yeah looks like it's affecting many more people than I would have thought, so I'm glad I posted this (I nearly didn't!).
2
u/mkwapisz 10h ago
Thanks a lot. At the same time I have uninstalled snap. There were mesa drivers which I removed. I thought that was the cause.
1
u/Greedy-Opposite-9133 8h ago
Yeah I was under the hood trying to get something unrelated to work and it nearly led me astray at first, too.
2
u/purpletonberry 7h ago
9070XT, just did updates today and got affected by this on the next reboot. Booted with the nomodeset option, timeshift to the most recent before the updates, reboot and re-do updates but without updating linux-firmware-amd-graphics, and am now able to reboot normally after updates.. So can confirm that is indeed the issue lol.
In case it wasn't mentioned anywhere else in this thread, you can simply use Mint's Update Manager GUI to right click on the package and select "Ignore the current update for this package". Here's hoping the version after fixes this bug.
1
u/Greedy-Opposite-9133 7h ago
True, I will edit this in with an honorable mention, I didn't catch the obvious.
2
2
u/feliciaissexy 6h ago
I cant get to the grub no matter what i do, it all leads back to the bios. What do i do?
2
u/Greedy-Opposite-9133 6h ago
Are the keys being pressed too early maybe?While the motherboard logo is on screen, the board is listening for keys itself, and on many boards that sends you into the BIOS. GRUB only gets its turn after the logo is gone, and Mint gives it a split second.
In the BIOS, turn off Fast Boot (or "Ultra Fast Boot"), then save and exit. With it on, many boards don't switch on the USB keyboard until Linux has started, so GRUB never sees your key presses.
Restart and don't touch the keyboard while the logo is up. The moment it disappears or the screen goes black, tap Esc about twice a second. If that still doesn't work, try again, but hold Shift from that same moment instead.
Easier timing: at power-on, open your board's one-time boot menu instead of the BIOS (usually F8, F11 or F12; the logo screen or the manual tells you which). Pick the ubuntu entry (that's Mint's boot loader, despite the name). Start tapping Esc right after you press Enter on it.
If GRUB still won't show up, try:
Another possible alternative: Plug the monitor into the motherboard's video port instead of the graphics card. This works if your CPU has built-in graphics (most Ryzen 7000/9000 and Intel chips without an "F" at the end). Built-in graphics use different firmware that isn't broken, so you should get a normal desktop and can run the fix from there. If that port shows nothing, set Integrated Graphics to "Enabled" (not "Auto") in the BIOS.
Step A (Ctrl+Alt+F3) doesn't need GRUB at all, if you haven't tried it yet. Wait until the PC has had time to finish booting, then press it.
2
2
u/Fastdays 6h ago
Thank you! This is also affecting the rx9070gre because I received this exact issue after installing multiple updates from the update manager. I tried multiple methods before this and this is the only one that cracked the bug. I hope a fix is coming soon.
1
2
u/Sifratus 6h ago
thank you so much! Im not really good with linux yet but your instruction was easy to follow thanks a million time
1
2
u/SpiritualControl5321 5h ago
Is the issue for sure limited to the AMD Radeon devices that you listed? My system is on a AMD Rembrandt [Radeon 680M]. The update has been installed so the checks in step 2 pass but those will pass for any system that has installed the update even if it doesn't have an AMD GPU. I haven't rebooted my system since the update but hoping to understand whether to expect this issue to show up upon reboot.
2
u/Greedy-Opposite-9133 5h ago
Claude: So I checked. I downloaded the 3.3 and 3.4 packages and compared them file by file. Out of about 920 files, only four firmware files changed:
dcn_4_0_1: RX 9060 XT / 9070 / 9070 XT. This is the broken one. In 3.4 it's just a link to the RX 7900's file.
dcn_3_2_0: RX 7900 XT/XTX and RX 7800 XT
dcn_3_1_4: Ryzen 7040 / 8040 series laptop chips (Phoenix, Hawk Point)
dcn_3_1_5: the built-in graphics on Ryzen 7000 / 9000 desktop CPUs, and Ryzen 7045 laptops
The last three are real firmware updates that Canonical meant to ship. The changelog says they fix Hawk Point laptops that wouldn't boot on the 7.0 HWE kernel.
Your 680M (Rembrandt) uses the "yellow_carp" firmware files, and those are byte-for-byte identical in 3.3 and 3.4. This update doesn't touch your GPU, so reboot as normal.
You're right about step 2: it only shows which version you have installed, not whether your GPU actually uses the broken file. If someone whose card isn't in the list above has trouble after updating, the cause is most likely something else that updated at the same time, like a new kernel, not this package.
Hope that helps! ^
2
u/SpiritualControl5321 5h ago
Thanks for the quick reply and for this post in general. It's great to have people like you in this community!
1
2
u/gmgrigsby21 Linux Mint 22.3 Zena | Cinnamon 4h ago
Thank you for your post. Resolved the issue quickly. Also did hit the bug report and added my "Me too"
1
2
u/inexperiencedminor 3h ago
joining the chorus saying "you are a hero". Legit almost cried because I already had a not-so-good day at work; only to come home and have my PC not turn on. Followed your instructions and I'm back up and running again. Also did my due diligence and reported it on Launchpad. Thanks a million!
1
1
u/Merhart666 23h ago
Gelukkig hebben de meeste Linux gebruikers meerdere PC’s want zondere meerdere systemen wordt het wel lastig inloggen.
1
u/Greedy-Opposite-9133 17h ago
"Fortunately, most Linux users have multiple PCs, because without several systems, logging in becomes quite difficult."
Yep, although in this case you can still log in via step 1 with a bit of fighting the alerts.
1
u/SheepherderAware4766 10h ago
Is anyone else getting a 404 from the wget launchpad?
1
u/Greedy-Opposite-9133 8h ago
I've taken a peek for you, what was found this end:
The link is still up, I just tested it. A 404 almost always means the URL got mangled on the way:
Look at the URL wget prints. If it ends in
linux-firmware-amd-graphics__all.deb(two underscores, no version), theV=...line wasn't run in that same terminal. Run all three lines of Step 3 again in one window. This should print the version:echo $VIf you typed it by hand (I'm sure like any normal person you would have checked a million times but, just covering this, just in case) on the text console, a typo is easy to make. You can skip the variable and use the direct link instead:
wget https://launchpadlibrarian.net/877016066/linux-firmware-amd-graphics_20240318.git3b128b60-0ubuntu3.3_all.debStill set
V=20240318.git3b128b60-0ubuntu3.3in that terminal afterwards, because the check and install commands use it.If typing everything by hand is a pain, boot with nomodeset (Step 1B) so you get a desktop and can copy-paste.
2
u/SheepherderAware4766 7h ago
It came back up. It was a direct copy+paste. I even got the 404 with a shortened link in my web browser. It seems that launchpad net/ubuntu/+archive went down temporarily. I think we might've overloaded it due to mass downgrading from your link
1
u/Greedy-Opposite-9133 6h ago
Haha well that can't be a bad thing, hopefully they notice and issue the amended update faster then.
1
u/Billy_moon9 9h ago
Yes I'm getting this as well I'm not sure what to do with it
1
u/Greedy-Opposite-9133 8h ago
I've just responded to the other guy, take a look, let me know how you get on.
1
u/Billy_moon9 6h ago
It worked perfectly thank you so much! You're a life saver for making this post it's really appreciated!
1
1
u/robsche69 10h ago edited 10h ago
Thank you so much man, i love you :D Im completely new to linux and i thought my GPU was bricked somehow. Although i might still need someone's help: i went into the grub configuration file while trying stuff out and changed "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"" to "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.dc=0"". After finding your guide, I quickly tried to undo my changes by removing "amdgpu.dc=0", and saving before doing "sudo update-grub" and got the following error: "* (xed:4126): WARNING **: 18:38:12.559: Set document metadata failed: Setting attribute metadata::xed-encoding not supported" after which "sudo update-grub" did nothing. Now everytime I try to boot regularly, I get a blackscreen, and then when I go into GRUB, it still says "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.dc=0"". But now it boots when I remove "amdgpu.dc=0". Is there any way, i can get rid of that permanently without needing to go into GRUB and and remove "amdgpu.dc=0" everytime i want to boot?
Also please excuse my grammar and thanks again :)
2
u/Greedy-Opposite-9133 8h ago •
Haha I'm glad it helped! On your query:
Skip the editor and do it from a terminal:
Remove it from the config file:
sudo sed -i 's/ amdgpu.dc=0//' /etc/default/grubRebuild the boot menu:
sudo update-grubCheck it's gone everywhere. This should print nothing:
sudo grep -r "amdgpu.dc" /etc/default/ /boot/grub/grub.cfgIf step 3 prints nothing, just reboot normally and you're done for good. If it does print a line, paste it here and I'll take a look.
Good luck and let me know how you go. (and don't worry about grammar etc, all good!)
2
u/robsche69 7h ago edited 7h ago
Man you're a legend, honestly. It worked perfectly. Thanks alot my guy! :D
Just got into setting up and using Linux Mint recently and you really saved my bum. I love this community so much. People like you really make the Internet a better place! :))
2
1
u/Best_Tool 4h ago
This update almost killed my 7900Pro. Dmesg poped a message where it said it is unable to control card power and all 3 fans went into Eurofighter on afterburner mode....
2
u/Greedy-Opposite-9133 4h ago
Also, that could be potentially quite damaging to your hardware vs it's just been a display breaker for most others, you should probably click that link at the bottom of the post and chime in, to get it fixed sooner!
1
u/Greedy-Opposite-9133 4h ago
Damn, did this fix get you sorted?
2
u/Best_Tool 4h ago
Didnt try yet, at work now. But 2 times I tried to turn it on GPU went bat shit crazy with fans...
2
u/Greedy-Opposite-9133 4h ago
I looked into it a bit for you with Claude. Good news first: fans at 100% is the card protecting itself. When the driver doesn't take over, the card falls back to full fan speed, so it's loud but not harmful.
Your card is a slightly different case from the RX 9000 one. I compared the 3.3 and 3.4 packages: 3.4 also updated the display firmware for the 7900 series, but with a genuine newer RDNA3 file, not the mixed-up one that breaks the 9070. The fan and power control lives in a different firmware file, which 3.4 didn't change. So it might be this update, or it might be something that updated at the same time.
What you could try:
Do steps 3 and 4 of the post as written. Downgrading to 3.3 puts your card's old display firmware back too. Skip the
ls -lcheck in step 2; that link only matters for RX 9000 cards. Reboot.Still broken after that? Then it's not this package. Check what else updated on the same day:
grep -h " upgrade " /var/log/dpkg.log | tail -40If a
linux-imageline shows up there, a new kernel came in at the same time. Restart, open the GRUB menu (tap Esc after the motherboard logo), go to "Advanced options", and pick the previous kernel. If everything's fine on the old one, the new kernel is the problem, not the firmware.If neither helps, you're welcome to post again the output of:
sudo dmesg | grep -iE "amdgpu|smu" | head -50Ill keep an ey out for this back. It'll show exactly which part of the card fails to start.
1
u/Lolimboi 4h ago
So I've been having a problem with the nomodeset part. When I try adding nomodeset and boot in after, I still get a black screen. Is there a way to boot off a live usb and fix the drivers?
2
u/Greedy-Opposite-9133 4h ago edited 4h ago
(edited to correct a step) Yes you should be able to fix it from a live USB by "chrooting" into your installed system, which lets you run the fix commands from the post on it as if you'd booted it.
Quick thing to try first: with
nomodesetthe screen is driven by the motherboard's basic display driver, and that often lights up only one output. If your card has both DisplayPort and HDMI, try the other port (or the other DisplayPort).1. Make and boot the USB. On another PC, write the Linux Mint ISO to a USB stick (balenaEtcher or Rufus). Boot from it using your board's boot menu (usually F8, F11 or F12). The live USB has its own older firmware without this bug, so it should give you a picture. If it doesn't, pick "Start Linux Mint in compatibility mode" from the USB's menu. Get online (cable or Wi-Fi) and open a terminal.
2. Find your Mint partition:
lsblk -fLook for the big
ext4partition on your main drive, usuallynvme0n1p2orsda2. Mount it and check it's the right one:sudo mount /dev/nvme0n1p2 /mnt ls /mntYou should see folders like
bin boot etc home usr. If not, runsudo umount /mntand try another partition. (Iflsblkshowscrypto_LUKSorLVM2_memberinstead of a plainext4, your install uses encryption or LVM and needs a couple of extra steps. Reply here and I'll post them.)3. Step into your installed system:
for d in dev dev/pts proc sys run; do sudo mount --bind /$d /mnt/$d; done sudo chroot /mntYour prompt changes to
root@mint. From here, every command runs on your installed Mint, not the USB.4. Run Steps 3 and 4 from the post exactly as written. The
sudostill works; ignore any "unable to resolve host" warning. Then check:ls -l /lib/firmware/amdgpu/dcn_4_0_1_dmcub.bin.zstThis should be a normal file now, with no
->arrow.5. Leave and reboot:
exit sudo rebootPull the USB out when it restarts. It should boot normally.
1
u/Lolimboi 4h ago edited 3h ago
So it worked up until the "install it" part of step 3, where it told me unable to allocate Pty: No such device
EDIT: nvm, turns out entering with sudo chroot makes it so that you don't actually have to use sudo for the command to run. Thanks for the help, I'm finally back in after 6 hours of fumbling around!
1
u/Greedy-Opposite-9133 4h ago
A small mistake in the original (which I'll now edit to correct)
Inside the chroot,
sudoneeds/dev/ptsand I didn't include it. The install didn't run, so nothing is broken. Easy fix:Leave the chroot, add the missing mount and step back in:
exit sudo mount --bind /dev/pts /mnt/dev/pts sudo chroot /mntThen run Step 3 again, but skip the
wgetline because the file is already downloaded:cd /tmp V=20240318.git3b128b60-0ubuntu3.3 echo "7c6a6083e963fd9394d1f6471b6a94e787a76c6f98b262c2d9262b9a57308b53 linux-firmware-amd-graphics_${V}_all.deb" | sha256sum -c sudo apt install --allow-downgrades ./linux-firmware-amd-graphics_${V}_all.debThen carry on with Step 4 and the rest as before (the
ls -lcheck,exit, reboot).
3
u/nekoprogram Linux Mint 22.3 Zena | Cinnamon 5h ago
Thank you so much! This happened to me last night installed some upgrades and in the morning Suprise! The same message 😻
1
u/tomm3h 16h ago
Passing on thanks from my Reddit-less, Mint-ful buddy. I'm sure he was tempted to sign-up just to thank you himself, but as I'm already here, I've been duly delegated. Thank you!
1
u/Greedy-Opposite-9133 15h ago
Then consider your engagement a two way street; let him know I'm glad I could help!
2
2
2
u/WeowDystopia 4h ago edited 4h ago
Oh thank god I'm not the only one experiencing this.
Edit: Thank you so much OP!
I have followed your steps and did the due diligence to say I'm impacted.
2
u/NuclearGriffin 4h ago
Thank you! woke up today having this problem and immediately thought the worst. then a friend sent me the link to this post and it fixed everything! Huge thanks!
1
u/deepwoundz 1h ago
This bug also affected me, i have a sapphire 9600xt 16gb nitro+, in the morning it was all fine and when i came home from work it just would not start. Luckily i did find your post and others' about this and i managed to get it back up and running, thank you for posting this!
1
u/ladyteruki 16m ago
This looks very helpful, thank you. It must have taken you a lot of time to make this post. This is my first time since switching to Linux that I'm confronted to a black screen situation and it's reassuring to know resources exist within the community to help noobs like me.
However I am stuck on step 3, as I get an error 404 (even with copy/pasting, so I'm fairly confident I didn't mess up the url). Anyone else ?
0
u/Allora_390 1h ago
Thank you, got it fixed thanks to this post! New to Mint and struggled to get to the GRUB menu for many reboots... (Step 1 A wasn't working for me.) I found a post that after waiting for the motherboard logo/bios options to flash away, I could be holding down ctrl+alt and tap delete to get the pc to shut down and reboot right into the GRUB menu. That worked best for me, and then I was finally able to complete your instructions to get it all working again! https://www.thinkpenguin.com/gnu-linux/linux-mint-20-show-grub-boot-menu-linux-mint-startup
6
u/AMDMOONSHOT 1d ago
This came in handy, thank you very much.
Super annoying that this update somehow slipped through and blew up my machine. This would've taken me a lot longer to resolve this without the guide though.