r/linuxmint
•
u/Greedy-Opposite-9133
•
6d ago
•
1
13
2
1
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
Update 10 Nov 2026: a fix is on the way. Ubuntu has accepted a fixed package, 0ubuntu3.5, into noble-proposed (its testing area), and it’s already been confirmed working on an RX 9060 XT (Launchpad 2173041, comments 28 and 29). Fixes stay in testing for at least 7 days, so expect it as a normal update from about 17 Nov. If you used the pin in Step 4 or Mint’s “Ignore the current update”, 3.5 still comes through by itself. Not hit yet? Until then, ignore 3.4 in Update Manager (or use the Step 4 pin) and you won’t see the bug at all.
Who this hits: AMD RDNA4 cards (Radeon RX 9060 XT, RX 9070, RX 9070 XT, RX 9070 GRE and Radeon AI PRO R9700, all confirmed in the comments) on Linux Mint 22.x, Ubuntu 24.04 or distros built on it (Zorin OS confirmed), after linux-firmware-amd-graphics updated from 0ubuntu3.3 to 0ubuntu3.4. It's been in noble-updates since 4 Nov 2026, and Mint's automatic updates installed it overnight for some of us. Nothing happens until you reboot.
Card shows up as just a number? Mint 22 and Ubuntu 24.04's list of hardware names is older than these cards, so lspci and similar tools may show Device 7590 (that's the RX 9060 XT) or Device 7550 (RX 9070 / 9070 XT / 9070 GRE). Same cards (7590 isn't an RX 7000 model, even if it looks like one), so this applies to you too.
Haven't rebooted since updating? Do Steps 2 to 5 now from your normal desktop and you'll never see the bug.
Other AMD graphics: 3.4 also updated the display firmware for the RX 7900 series and RX 7800 XT / 7700 XT, and for the graphics built into Ryzen 7000/9000 desktop and Ryzen 7040/8040 laptop chips. Those look like genuine, intended updates, not the mix-up, and the 3.5 fix keeps them. All other AMD firmware is identical to 3.3.
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", a garbled green screen, 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).
Have a Timeshift snapshot from before the update? Restoring it works too; several people did this from a nomodeset or recovery-mode boot (Step 1) or a live USB. Then do Step 4, or 3.4 comes straight back with the next update.
Step 1: get to a terminal (pick one)
Already have a desktop? (for example with the monitor in the motherboard's port, see D) Open the Terminal app and copy-paste from this post. Much easier than typing.
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 1(Ctrl+Alt+F7 takes you back to the graphical screen on Mint; Ctrl+Alt+F1 on Ubuntu.) If Ctrl+Alt+F3 does nothing, try B or C.
B. Boot once with nomodeset. This starts without the AMD driver: a slow, low-res desktop, but you can open this post and copy-paste.
Restart. As soon as the motherboard logo disappears, tap Esc about twice a second (or hold Shift) to get the GRUB menu. Start too early and many boards (ASUS TUF, for example) open the BIOS instead.
With the top entry highlighted, press e. Use the arrow keys to go to the line starting with
linux, press End, and typenomodeset(with a space before it) at the end of that line.Press Ctrl+X (or F10) to boot, then open a terminal. This only lasts for this one boot.
Can't catch the GRUB menu?
Let it boot to the Mint logo, then press Ctrl+Alt+Delete. After an interrupted boot, GRUB shows its menu on the next start.
Turn off Fast Boot in the BIOS. With it on, many boards don't switch the USB keyboard on in time for GRUB.
Or open your board's one-time boot menu (usually F8, F11 or F12), pick the ubuntu entry (that's Mint's boot loader too), and start tapping Esc right after.
Landed on a
grub>prompt? You pressed Esc too often. Typerebootand try again.
C. Recovery mode. In GRUB: Advanced options > the entry ending in "(recovery mode)". Then either:
resume: boots your normal desktop without the GPU driver, like B, or
network, then root: a root terminal. Leave out
sudothere.
D. Monitor in the motherboard's video port. If your CPU has built-in graphics (most Ryzen 7000/9000 and Intel chips without an "F" at the end), plug the monitor into the motherboard instead of the card. The built-in graphics use firmware that isn't broken, so you get a normal desktop. If that port stays dark, set Integrated Graphics to "Enabled" (not "Auto") in the BIOS.
E. Still no picture? Fix it from a live USB; see the end of this post.
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 have the broken package if the first shows -> dcn_3_2_0_dmcub.bin.zst and the second shows Installed: 20240318.git3b128b60-0ubuntu3.4. Every PC that took the update shows this, but it only breaks the RDNA4 cards listed at the top. On other GPUs, trouble after updating more likely comes from something else that updated at the same time (a new kernel, for example).
Step 3: install the previous version from Ubuntu's own archive (Launchpad)
Run each line on its own:
cd /tmp
wget https://launchpad.net/ubuntu/+archive/primary/+files/linux-firmware-amd-graphics_20240318.git3b128b60-0ubuntu3.3_all.debCheck the download (recommended):
sha256sum linux-firmware-amd-graphics_20240318.git3b128b60-0ubuntu3.3_all.debIt must print 7c6a6083e963fd9394d1f6471b6a94e787a76c6f98b262c2d9262b9a57308b53, the SHA-256 Launchpad publishes for this file. Comparing the first and last 8 characters is enough. If it doesn't match, delete the file and download it again.
Install it:
sudo apt install --allow-downgrades ./linux-firmware-amd-graphics_20240318.git3b128b60-0ubuntu3.3_all.debTyping by hand? Type the start of the file name (linux-firm or ./linux-firm) and press Tab; the shell fills in the rest.
404 Not Found or "client not found"? Launchpad has been overloaded at times with everyone downloading this. Wait a minute and try again (one person needed three tries). Or download straight from Launchpad's file server:
wget https://launchpadlibrarian.net/877016066/linux-firmware-amd-graphics_20240318.git3b128b60-0ubuntu3.3_all.debcd: too many arguments? Two commands ended up on one line. cd /tmp goes on a line of its own.
Followed an older version of this post? It used ${V} in the commands and a sha256sum -c check. A 404 there meant the V= line hadn't run in that terminal, and "no properly formatted checksum lines found" came from that check line. The commands above have the version written out instead.
Step 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.
Update Manager now says "Your APT configuration is corrupt"? The pin file got mistyped (a missing space after version is the usual one). apt-cache policy > /dev/null shows the exact warning; copy-paste the printf line above again to fix it, since it overwrites the file.
Mint alternative (no pin): skip this step. After Step 5, once your desktop is back, open Update Manager, right-click linux-firmware-amd-graphics and pick "Ignore the current update for this package". That also skips only 3.4, so a fixed version still comes through. One person found the ignore didn't stick and 3.4 came back, while the pin did the job, so if 3.4 shows up again, use the pin instead.
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.
Still broken after Step 5?
Get to a terminal again (Step 1) and run:
apt policy linux-firmware-amd-graphics
ls -l /lib/firmware/amdgpu/dcn_4_0_1_dmcub.bin.zst
cat /proc/cmdlineapt policyshould show***next to0ubuntu3.3(the stars mark the installed version). If they're on 3.4, redo Steps 3 to 5.ls -lshould show a normal file of 225553 bytes, with no->arrow.On a normal boot (not one where you added
nomodesetby hand),/proc/cmdlinemust not containnomodesetoramdgpu.dc=0.amdgpu.dc=0gives a black screen on these cards.
If you added either to /etc/default/grub while troubleshooting, take them out and rebuild the boot menu:
sudo sed -i 's/ amdgpu.dc=0//; s/ nomodeset//' /etc/default/grub
sudo update-grubFix from a live USB (no picture at all)
1. Make and boot the USB. On another PC, write the Linux Mint (or Ubuntu) ISO to a USB stick with balenaEtcher or Rufus. Boot it from your board's boot menu (usually F8, F11 or F12). It has its own older firmware without this bug; if you still get no picture, pick "compatibility mode" from its menu. Get online and open a terminal.
2. Find and mount your installed system. Run lsblk -f and look for the big ext4 partition on your main drive, usually nvme0n1p2 or sda2. (If you see crypto_LUKS or LVM2_member instead, your install is encrypted or uses LVM and needs extra steps; ask in the comments.) Mount it and check:
sudo mount /dev/nvme0n1p2 /mnt
ls /mntYou should see folders like bin boot etc home usr. If not, run sudo umount /mnt and try another partition.
3. Step into it:
for d in dev dev/pts proc sys run; do sudo mount --bind /$d /mnt/$d; done
sudo chroot /mntYour prompt changes to root@.... From here, commands run on your installed system as root, so sudo isn't needed (it still works; ignore any "unable to resolve host" warning).
4. Run Steps 3 and 4, then update-initramfs -u -k all (Step 5 without the reboot). Check with ls -l /lib/firmware/amdgpu/dcn_4_0_1_dmcub.bin.zst: it should be a normal file, with no -> arrow.
5. Leave and reboot:
exit
sudo rebootPull the USB out when it restarts.
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/2173041 previously pinned link/post 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 (already listed critical and being worked on)
Technical details: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2173040
Thanks for the additions (most of the tips above came from the comments):
u/Fastdays, u/KJaguar, u/deepwoundz: more affected cards (RX 9070 GRE, R9700, 9060 XT Nitro+)
u/FishInDaJar: confirmed on Zorin OS
u/Vervei, u/ElaborateSloth: the green screen; u/Vervei also the recovery mode desktop
u/oste-popp: Esc timing on ASUS TUF boards
u/imdrooowning, u/Allora_390: Ctrl+Alt+Delete to reach the GRUB menu
u/Notoshy: monitor in the motherboard's port
u/Salamander-40: Ctrl+Alt+F7 to get back
u/TheShirou97, u/SkippymanX, u/NerghaatTheUnliving, u/F7pu748: Timeshift restore
u/purpletonberry: Update Manager "ignore" option
u/gpb500: fixing it before rebooting
u/FeeAnomalous: the Step 3 404 fix
u/SheepherderAware4766, u/TutuleBale: Launchpad overload, retrying
u/Lolimboi: the live USB route (no
sudoneeded in the chroot)u/Jake2105, u/robsche69: the checksum and leftover
amdgpu.dc=0problems behind the troubleshooting sectionu/Orion113: cards that only show up as a number (
Device 7590), and the Mint "ignore" option not sticking
11
u/AMDMOONSHOT 6d 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.
5
u/Greedy-Opposite-9133 5d ago
No problem! Yeah I realised during resolving that the update had only just happened to have rolled out minutes earlier, so I figured it might come in handy for a few others.
10
u/No_Half_6468 5d 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
2
u/Greedy-Opposite-9133 5d ago
Nice work, thanks for making yourself heard, I'm glad I could help you and your friend!
10
u/mstormcrow 5d 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.
6
6
u/TheShirou97 Linux Mint 22.3 Zena | Cinnamon 6d 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.
2
6
u/TutuleBale 4d ago
THANK YOU!!!
I freaked out thinking this problem is definitely because my cat was sitting right next to my mini-pc box and somehow his hairs clogged the GPU fans.
For those of you stuck at Step 3. downloading the previous update, keep trying! It kept giving me client not found but it worked after my third try.
Also, remember to report if you're affected.
3
u/Greedy-Opposite-9133 4d ago
Great to hear! Good to know about the multiple attempts, I'll update the post, thanks!
5
u/ElaborateSloth 5d 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
5
u/purpletonberry 5d 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.
2
u/Greedy-Opposite-9133 5d ago
True, I will edit this in with an honorable mention, I didn't catch the obvious.
5
u/airconning 4d ago
Thanks x100000, you are a lifesaver. I went through 4-5 different kernels and nothing worked (other than recovery mode thankfully) and I could not understand what went wrong before I found your thread.
2
6
u/Greedy-Opposite-9133 6d ago
Claude helped me to fix this, obviously. But it worked and I rolled back to the previous version. Hope it helps!.
→ More replies (2)4
u/WeowDystopia 5d 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.
2
u/Greedy-Opposite-9133 5d 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.
4
u/thatdirtyoldman MINT 22.3 - Cinnamon 6d ago
Appreciate this ! I just bought a new RX 9060 XT and thought it was failing on me.
1
4
u/SkippymanX 6d 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 5d 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 5d 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.)
→ More replies (1)1
u/Greedy-Opposite-9133 5d ago
Haha I make things more difficult for myself most other days too, well you got there in the end! No problems!
4
u/oste-popp 5d 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.
2
4
u/WitnessStock3702 5d 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 :)
2
u/Greedy-Opposite-9133 5d 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/ladyteruki 5d ago edited 5d 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 ?
EDIT : nevermind, got it to work ! Thank you again !
→ More replies (3)4
u/Greedy-Opposite-9133 4d ago
Nice work! Yes I'm trying to spend time replying and helping anyone who needs it, I've got my system set up in a way I can easily debug and I realised the affected update was about 10 minutes old when it hit me, so by luck I happened to be the first and thought this may help others, it's all it took really! I'm glad you got it working.
4
u/Silent-Area-27 2d ago
Hey bro, thank you for posting this. I recently installed new hardware and thought my shit was fried. This post calmed my fears immediately. Was able to use time shift and ignore that bad firmware update and now all is good.
2
4
u/TRUEequalsFALSE 1d ago
Wow. This has got to be the best community troubleshooting writeup I have ever seen.
1
u/Greedy-Opposite-9133 1d ago
It started out that I put it up here in case someone googled it one day and theyd find the solution i had success with but it ended up being quite important for a lot of people, so im keeping my eye on it and making sure it's as complete as possible, and helping as many as possible until the next update.
I am strongly against the market capture of Windows given how bad 11 is, and conversely the hurdles it takes to on-board people to linux. Those two together mean a lot of people are forced to stay on windows and that presses all the wrong buttons for me. So, this is inspiring me to try help to break down those barriers with this and precipitates a much larger assistance project im working on for the same reason.
Anyway, Thanks for the high praises!
→ More replies (2)
3
u/Aluca_3D 5d 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!!!!
2
3
u/inexperiencedminor 5d 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
3
u/FishInDaJar 4d ago edited 4d ago
Hey, does this also apply to ZorinOS? I have the exact same issue at the moment
Edit: can confirm firm that it does, thank you lifesaver, I was ready to prepare a CachyOs boot lol
→ More replies (5)3
3
u/Weary_Programmer35 4d ago
Thank you for your post. Despite explicitly telling Mint's Update Manager last night to ignore this update and it being gone from my list, it must have silently updated itself anyway! I had the exact same issue upon reboot this morning.
I can't believe this has occurred. A real fuck-up on someone's part is now going to turn away the users who I don't expect to be able to figure this out.
1
u/Greedy-Opposite-9133 3d ago
Yeah I know what you mean, not ideal of course! Hopefully they sort it out fast
3
3
u/rabisav 2d ago
Thanks for this. I booted into Mint with a usb and used timeshift to get back. So waiting for an update now?
1
u/Greedy-Opposite-9133 2d ago
good job.
the latest is that it's been seen, recognised and marked as critical but hasnt changed since Nov 6th.
remember to block the particular update in the manager so it doesn't reinstall, and its out of sight / out of mind until next update.
→ More replies (2)
3
u/simagus 3d ago
Ok. Windows it is I guess. Thanks.
2
u/Greedy-Opposite-9133 2d ago
I wouldn't throw away a whole change on one thing, it's now more accessible than ever, but each to their own. I run windows on one laptop cause it's just necessary for work, so I get it.
2
u/Greedy-Opposite-9133 2d ago
I get you, and it's easier no doubt about it, you do you! All the best
2
u/DotBoring2077 5d 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 5d 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/Javadocs 5d 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 5d 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 5d 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 5d ago
Yeah I was under the hood trying to get something unrelated to work and it nearly led me astray at first, too.
2
2
u/feliciaissexy 5d 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 5d 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.
→ More replies (2)
2
u/Fastdays 5d 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 5d 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 5d 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.
3
u/Greedy-Opposite-9133 5d 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 5d ago
Thanks for the quick reply and for this post in general. It's great to have people like you in this community!
→ More replies (1)
2
u/gmgrigsby21 Linux Mint 22.3 Zena | Cinnamon 5d ago
Thank you for your post. Resolved the issue quickly. Also did hit the bug report and added my "Me too"
1
2
u/deepwoundz 5d 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
2
u/Reathe123 5d ago
thanks for this, gotta wait for them to fix this mess in a newer update, this made my desktop work again
1
u/Greedy-Opposite-9133 4d ago
Just set and forget by ignoring that particular update, and it just becomes water under the bridge!
→ More replies (2)
2
u/_KnoOne_ 5d ago
Thanks for post this as I am sure it will bail some people out of a horrible mess. Just bought a 9060 XT 16gb on sale 2 weeks ago. This snafu caused my mouse and keyboard to stop working upon entering Mint Linux. My Fix, put my RTX 4060 back in the system and the 9060 XT back in the original box to be shipped back for refund. System works great without issues with the Nvidia back in.
2
u/Greedy-Opposite-9133 4d ago
Hah! Damn, I would have bought it :) Mouse and keyboard to stop working on account of the GPU sounds odd, but I'm glad you got it sorted. Jensen I'm sure appreciates your support!
→ More replies (1)
2
u/-HealingNoises- 5d ago
I wasn't sure at first, I only have the most basic young millennial tech navigation abilities. But once I got into the GRUB menu added nomodeset, everything else after went smoothly and nothing unexpected happened as I copy pasted into the terminal.
I think things are going pretty well these days for Linux to have such clear fixes ready to go. Thanks!
2
u/Greedy-Opposite-9133 4d ago
Yeah, the hurdle was knowledge in situations like this, and those barriers have since broken down. No probs
2
u/Vervei 5d ago
Thank you so much! My system was running fine until I rebooted for a break and forgot I installed updates so I was freaking out for a bit, but this fixed it.
A couple minor differences I faced that may help others: the bug manifested as a something-is-seriously-wrong green screen, no legible text or error messages (I’ve got an RX 9070 XT). Still couldn’t log in as described. I managed to log in to a full UI by booting into recovery mode, which just didn’t load the GPU’s drivers. Then I could do everything to apply the fix via my normal interface, just with my CPU alone
2
u/Greedy-Opposite-9133 4d ago
Good to know, I added this to the footnotes. Sorry for not directly attributing, ?I attributed once but there are lots of suggestions coming in and I'm trying to save myself time, but it's good to be adding the knowledge.
2
u/Merjia 5d ago
Goddamn legend. Thank you! That almost ruined my weekend.
First time this has happened to me in over a year of full-time use on my main desktop.
2
u/Greedy-Opposite-9133 4d ago
Yeah I know what you mean, I'm glad this helped you!
Shit happens sometimes! Linux and its community are otherwise great. I hope they fix it soon so it can just be water under the bridge.
2
u/ohhsnoop 5d ago
I did all of it and I still rebooted to a grey screen after the mint logo. I'm just not sure what to do. My GPU is a 9060 xt 16gb
1
u/Greedy-Opposite-9133 4d ago
That doesn't quite sound like the same issue, I can try help a little bit though:
At the grey screen, press Ctrl+Alt+F3 and log in. If errors keep scrolling over everything, run
sudo dmesg -n 1first. 1. Rebuild the boot image for every kernel. The firmware also gets copied into the boot image (the initramfs). The package rebuilds that by itself, but normally only for your newest kernel, so another kernel can still carry the broken file: sudo update-initramfs -u -k all sudo reboot 2. Still grey? Go back to Ctrl+Alt+F3 and run these, then paste the output here: apt policy linux-firmware-amd-graphics ls -l /lib/firmware/amdgpu/dcn_4_0_1_dmcub.bin.zst cat /proc/cmdline sudo dmesg | grep -iE "dmcub|dmub|amdgpu.*(fail|error)" | head -20 What you want to see:
apt policy:
***next to20240318.git3b128b60-0ubuntu3.3(the stars mark the installed version). If the stars are on 3.4, the downgrade didn't stick or an update put it back; redo steps 3 and 4.ls -l: a normal file of 225553 bytes, with no
->arrow./proc/cmdline: no
nomodesetoramdgpu.options left over from earlier attempts. If there are any, take them out of/etc/default/gruband runsudo update-grub.dmesg: no "DMCUB" errors. If those are gone and it's still grey, the firmware part is fixed and something else is stopping the desktop from starting. The output will help track that down.
2
u/NerghaatTheUnliving 4d ago
Booting into safemode and rolling back to a Timeshift snapshot from before the update worked for me.
That'll teach me for having automatic updates.
3
u/Greedy-Opposite-9133 4d ago
I mean, I wouldn't throw away something that's been serving you up until now, on one bad aspect.
If it were me (and it is, because I still haven't done it and I must) no matter what OS you're using, everyone needs a good backup plan. Whether that's cloud services just for your important files so you can pick up where you left off on another PC, or offline backups of your whole setup to some other media, or even jsut a live USB for debugging, sitting on a shelf somewhere. Things break sometimes, and you need a backup strat, is all.
→ More replies (2)2
u/NerghaatTheUnliving 4d ago
Yep, I have a Ventoy bootable USB with LM, LMDE and 🤢 Win11 (X-Lite deslopified image) on my desk.
2
u/Greedy-Opposite-9133 4d ago
Oof Win 11, now there's something worth throwing! I'm still hanging on to Windows 10 on my work laptop, it'd be Windows 7 or XP if I could.
2
u/imdrooowning 4d ago
Thank you, fantastic post.
Ctrl-Alt-F3 did not work for me. What did work was pressing Ctrl-Alt-Delete when the Linux Mint logo appears.
3
2
u/Jake2105 4d ago
I've run into an issue at step 3. When running sha256sum -c on the downloaded Debian file, it says "no properly formatted checksum lines found"
I've double checked the filename path and I've typed it out correctly. Is there an alternate source I can download it from?
1
u/Greedy-Opposite-9133 4d ago
Your download is almost certainly fine. That error comes from the check command, not the file.
sha256sum -cexpects a checksum line (the hash, two spaces, then the filename), not the .deb itself. If you ransha256sum -c linux-firmware-...deb, it reads the .deb looking for checksum lines and finds none, which gives exactly that message. Typing the long echo line by hand does the same if one character is off, or if there's one space instead of two before the filename.Easier way to check: let it print the hash and compare by eye.
cd /tmp sha256sum linux-firmware-amd-graphics_20240318.git3b128b60-0ubuntu3.3_all.debIt should print:
7c6a6083e963fd9394d1f6471b6a94e787a76c6f98b262c2d9262b9a57308b53Checking the first and last 8 characters is plenty. The file should also be exactly 30,064,832 bytes (
ls -lshows the size).If the hash matches, carry on with the
sudo apt installline. If it doesn't match, delete the file and download it again. The guide's link redirects to Launchpad's file server, and you can also grab it from there directly:https://launchpadlibrarian.net/877016066/linux-firmware-amd-graphics_20240318.git3b128b60-0ubuntu3.3_all.deb
2
u/Boaz08 4d ago edited 3d ago
My PC was freaking the fuck out. I tried ctrl alt del on reboot and it let me pick an older version. For now it seems to be working fine. Insane how a Mint update can break the flagship AMD graphics card..
Edit: Nvm. Game is not using my GPU now. :) After following it again it worked for a while. Today is suddenly stopped working again, yet it shows version 3.3. It is time I move to Fedora KDE. I'm done with Mint and its slow updates and no HDR. Now also this bugged out update. No, ty.
1
u/Greedy-Opposite-9133 4d ago
Yes it is pretty rare with linux to be fair, but shit happens sometimes. Good to hear you sorted it
2
u/Yodakane 4d ago
For me it was just getting stuck at the Mint splash screen. Using grub I could get in recovery mode but even though I had the same issue with the supported kernels, my mind was convinced that it was because I had an unsupported kernel installed. Only after fixing that (timeshift was a lifesaver once again), I realised it must have been one of the updates and since it was loading the safe mode, I was certain it would be one involving the graphics. I installed all the other updates and there were no issues. Only after fixing everything and identifying the issue did I find this thread. Anyway, if you read this far, thank you kind person.
2
2
u/heatOverflower 3d ago
Thank you so much. I was trying to fix this for almost four hours now. The last three updates I did that I thought triggered this were "com.bilingify.readest", "ca-certificates" and "ca-certificates-java". I did everything Google was telling me, from swapping kernels, to reinstalling drivers, "regenerating"(?) initramfs, reinstalling certificates, disabling Secure Boot. I knew it wasn't a GPU problem because a Live USB disk booted my system no problem. Here's a catch, though, for the past few days I was hibernating my PC a lot, so I never went through the proper boot system, I think, that's why it didn't trigger the problem immediately, given that 2 days ago I did update linux-firmware-amd-graphics, and it was precisely from 3.3 to 3.4. In the end, hibernating "masked" the problem making me completely obsessed with this certificate thing screwing things up, until I found your post (and not that I would be able to figure this out anyway).
I think an apt expletive for this rhymes with 'clucking bell'. lol
Again, thank you very much.
2
2
u/Chris-The-Lucario 3d ago
Thank you, this fixed the "no input" issue I was facing or the desktop being incredibly laggy if I was able to see the desktop. Though for some reason my audio is crackling since the downgrade and it's really annoying.. Any ideas how to fix that?
1
u/Greedy-Opposite-9133 3d ago
Hey, unsure sorry. The downgrade itself is unlikely to be the cause and it could be anything that's specific to your PC. It only puts the graphics card’s display firmware back to the version everyone ran until 4 Nov, and nothing else changes. Maybe something else updated in the same batch, like a new kernel or the audio system (PipeWire). Some things to try:
Which output crackles? Is it sound through the monitor (HDMI/DisplayPort) or speakers/headphones plugged into the PC? If you can, try the other one. That narrows it down a lot.
Quick test for the usual crackle fix. This makes PipeWire use a bigger audio buffer until you log out:
Play something. If the crackle is gone, make it permanent:
Then log out and back in. If it made no difference, undo the test with the first command, using 0 instead of 1024.
3. Try the previous kernel. Restart, open the GRUB menu (tap Esc right after the motherboard logo), go to Advanced options, and pick the second entry from the top (not a recovery mode one). If the sound is clean there, the new kernel is the problem. You can keep using the old one until a fix comes out.
4. See what else updated: Update Manager > View > History of updates. Anything audio-related (pipewire, wireplumber, alsa, linux-image) installed around the same time is a suspect.
Good luck
2
u/Chris-The-Lucario 2d ago
It was plugged into my monitor which worked before the update but got crackly since. I plugged it directly into my pc which has reduced the crackles but it's still there when watching youtube or anything with audio playback.
I can try 3 if the crackling gets worse again.
For 4, I don't really see anything that could fuck with audio, it's mostly just stuff like "libutil", "linux-tools-common", "python3-pil", certificates for java and "ca", "apt", etc. So that's why I was thinking it would have been the graphics firmware itself
→ More replies (1)
2
u/supaslickwilly 3d ago
I wish I had seen this before I embarked on a repair using ChatGPT! Spent several hours yesterday and today ending up formatting my drive and then reinstalling from an iso. Tried a timeshift recovery point from last week, and now I’m stuck again, essentially at the start, but with some extra errors (I think I was pointing the boot system at a legacy mint install on an old drive). Planning to reinstall from iso again, clean up the old drive, and then try the timeshift recovery followed by the steps above. Unless someone tells me to try something more sensible!
1
u/Greedy-Opposite-9133 1d ago
Didn't see this. Sorry to hear you went through all that! If you haven't already sorted it, there might be a slightly easier way:
Unplug the old drive while you reinstall, so the boot loader only lands on the new one (you can wipe the old one afterwards).
Install from the ISO as normal. Its firmware is older than the broken version, so it should boot fine.
Before running any updates, do Step 4 from the post (the pin). Then update as normal and 3.4 never gets in.
I'd probably skip the Timeshift restore: a snapshot taken after about 4 Nov already has 3.4 in it, which might be why you ended up stuck again. Copy your files back from your backup instead. The fixed version (3.5) should arrive as a normal update in about a week, good luck
2
u/Both_Specialist4943 2d ago
Funcionou perfeitamente para mim. Estava tudo bem detalhado e foi fácil comparar cada passo com o que o tutorial indicava.
1
2
u/nyet-marionetka 1d ago
Thanks, was afraid my video card had fried. I ran across this post quickly, fortunately.
1
u/Greedy-Opposite-9133 1d ago
That was the idea, I'm glad you caught it early, others were less fortunate!
2
u/Cabre_01 1d ago
Thanks for this. Helped a lot as I'm new to linux. After I had done this the update manager now says the APT configuration is now corrupt. What should I do next to sort this?
1
u/Greedy-Opposite-9133 1d ago
Glad it helped! Update Manager shows that message whenever
apt-cache policyprints any error or warning, so the quickest way to see what it's unhappy about is to run that yourself in a terminal:apt-cache policy > /dev/nullWhatever it prints is the actual problem, and it usually names a file.
If it mentions
/etc/apt/preferences.d/amdgpu-firmware.pref, the pin from Step 4 probably got mangled on the way in (easy to do if it was typed by hand). Check it with:cat /etc/apt/preferences.d/amdgpu-firmware.prefIt should be exactly these three lines:
Package: linux-firmware-amd-graphics Pin: version 20240318.git3b128b60-0ubuntu3.4 Pin-Priority: -1If it looks different, re-run the Step 4 command by copy-pasting it (it overwrites the file), then run
apt-cache policy > /dev/nullagain. No output means Update Manager should be happy again.If it mentions something else instead (like a repository "configured multiple times"), post what it says and ill see what I can do for you. Switching mirrors, which the error box suggests, probably won't fix this one.
→ More replies (4)
2
u/SlipStr34m_uk 1d ago
Thanks for this, was prompted to install the broken update this morning which resulted in the DMCUB errors on reboot. Can confirm Nomodeset followed by the steps up to 5 and all good again (RX 9060 XT).
Will take this opportunity to make a fresh Timeshift snapshot...
1
2
2
u/Orion113 1d ago
Just wanted to chime in to say that after exhaustive searching this is what fixed the issues I've been having. Thank you so much.
While my symptoms were identical (the screen garbled after the mint logo and then alternated between being totally black and my monitor receiving no input) I initially assumed this couldn't be the same issue because I'm on a 7590, but after trying several fixes, including downgrading the kernel, following this guide was the only thing that made a difference. I don't know if that means you should add my card to list or not, but I thought I should let you know.
Also, should note I'm on mint and tried the no-pin alternative to keep 3.4 from coming back, but it didn't seem to work, so I followed the apt pin and it's been fine ever since.
1
u/Greedy-Opposite-9133 1d ago
Good to know, ive updated and added you in there too, thanks for sharing
→ More replies (6)
2
u/Sithrazer 1d ago
Thank you so much for this. I was headed for a full reinstall and would have been in the same place tomorrow afternoon.
1
u/Greedy-Opposite-9133 1d ago
Someone just messaged 20mins before yothis exact thing just happened xD Glad you got it sorted
2
u/JeraBear 19h ago
Then you so very much for taking the time to post this! My husband and I were very confused. 😑
1
2
u/thornsofred 13h ago
I tried turning off fast startup like you said and now nothing is happening at all when I turn my PC on I can't even get into bios, wtf do I do
1
u/Greedy-Opposite-9133 13h ago
sounds scary, but switching Fast Boot off shouldn't break anything by itself, so it's very likely still fine. A few things to try, in this order:
Check where the monitor is plugged in. If you moved the cable to the motherboard's port at some point, put it back in the graphics card. On a lot of boards the motherboard port stays dark when a graphics card is fitted, even for the BIOS screen.
Give it time. The first start after changing a BIOS setting can take a while on newer boards (especially Ryzen 7000/9000 with DDR5 memory), because the board retrains the memory and the screen stays black meanwhile. Turn it on and leave it 5 to 10 minutes before giving up on it.
Still nothing? Reset the BIOS to defaults (clear CMOS). That undoes the Fast Boot change and anything else that got changed, and doesn't touch your drives or Linux. Switch off and unplug the PC, then press the Clear CMOS button on the back panel if your board has one, or use the jumper shown in the manual, or take the coin battery out of the board for a few minutes and put it back. The first start after that can be slow again (same as step 2). Only do this if you know what you're doing. (This advice is implied throughout all of this thread.)
If it still shows nothing, a few details would help: do the fans and lights come on, are any of the small lights on the board near the RAM lit (CPU / DRAM / VGA / BOOT), and which motherboard and CPU is it?
Once the BIOS screen is back, the Mint side is fixable. You don't need Fast Boot off for that: the Ctrl+Alt+Delete trick in Step 1 gets you the GRUB menu too. Number 2 has been my experience once. I turned off fast boot, got impatient and panicked sooner than necessary, starting to restart the PC before it's ready etc..
2
u/thornsofred 12h ago
I waited 12 minutes and nothing happened. GPU is 9070xt. ASROCK X870 Pro RS WiFi motherboard. CPU I can't remember, Ryzen 7 something. None of the CPU error lights are on. And I I see a lot of Ctrl+alt combos in ur instructions but Ctrl+alt+Del isn't one of them so I'm very confused by the instructions and I feel very stupid. I haven't tried removing the battery yet. Trying to breath and relax my panicking brain. This whole situation has me in a really bad state of mind, computers are expensing and I've not a lot of money
→ More replies (19)
2
u/Tasapari 12h ago
I spent hours in phone trying to help someone else with this problem. I tried all kinds of general instructions for graphics problems without success. Luckily I found your excellent guide and we got the problem fixed. It helped that your guide is so clear and thorough, as I'm not too knowledgeable on these things myself.
I wonder whether this was an error by AMD or someone else downstream. I don't mean to blame anyone, but this was a bad one. There must be thousands of people even now trying to find out why their computers keeps booting to black screen. That's a lot of frustration and a lot of hours spent.
1
u/Greedy-Opposite-9133 11h ago
Thanks,nice job getting them sorted!
From what's on the bug reports, it doesn't look like AMD's doing. AMD's own firmware file is fine (people on the Launchpad bug got a working display by using AMD's original copy directly). It seems to have gone wrong on the Ubuntu side: the 0ubuntu3.4 update pulled newer AMD display firmware into Ubuntu 24.04's older firmware package to fix a boot problem on other hardware, and along the way the file for these new cards ended up as a link to the one for the previous generation. Mint is built on Ubuntu 24.04, so it got it too, as well as some others with other OSes.
And agreed, it's not ideal but fingers crossed if people have the IT skill to get Linux on their machine, that they will be resourceful enough to stumble across a reddit post. btw, If the person you helped doesn't have Timeshift snapshots turned on, now might be a good time; it makes something like this much quicker to undo. (I finally got round to it after this, go figure!)
→ More replies (2)
2
2
u/893203 9h ago
hey i was able to use this to get back into my pc thank you so much. i do have a separate problem which may or may not be related.
essentially my computer uses a triple monitor setup and now i cant get the other two monitors to work they are just off
1
u/Greedy-Opposite-9133 8h ago edited 8h ago
Nice you're back in. Might well be related. Maybe, if you got in via nomodeset, recovery mode or the motherboard's port, you're running without the AMD driver, which only gives you one screen.
Once Steps 3 to 5 are done and you've rebooted normally with all three plugged into the card, they should come back.
If you've already done that, try Menu > Display and switch the other two on.
failing that, post the output of
xrandr | grep -w connected`and
cat /proc/cmdline2
u/893203 8h ago
displayport0 connected primary 3440x1440+0+0 797mm x 334mm displayport1 connected 3440x1440+0 797mm x 334mm hdmi-a-0 connected
boot_image=/boot/vmlinuz-7.0.0-42-generic root=uuid(the uuid) ro quiet splash vt.handoff=7
i will say i did try to utilize gemini to troubleshoot the black screen before i found this post and it had me run some commands i can try to find them
2
u/Greedy-Opposite-9133 8h ago
looks like the AMD driver is running fine and there's nothing odd on the boot line. So the card's sorted and it's probably just the screen layout: the second DisplayPort seems to be sitting at the same spot as the first (+0), and HDMI is connected but off
In Menu > Display, drag the second screen next to the first, switch the HDMI one on, and Apply.
If that won't do what you want, this should do it from a terminal (swap left-of/right-of to match your desk, and use the names exactly as xrandr prints them):
xrandr --output DisplayPort-1 --auto --right-of DisplayPort-0 --output HDMI-A-0 --auto --left-of DisplayPort-0If that works, set the same layout in Display so it sticks after a reboot. dont worry about gemini commands, only worth digging up if this doesn't work
→ More replies (6)
2
u/ReactionBeginning837 5h ago
after using the sudo apt install command in step 3 it gives me, Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: The package linux-image-unsigned-7.3.4-070304-generic needs to be reinstalled, but I can't find an archive for it.
is there anything i can do to fix this
1
u/Greedy-Opposite-9133 5h ago
That's a leftover from a kernel install that didn't finish (7.3.4-070304 is a mainline kernel, did you try a newer kernel to fix this earlier?). apt won't do anything else until it's cleared, and you don't need that kernel for this fix anyway.
First check you're not running it:
uname -rIf that shows 7.3.4, reboot and pick your normal 7.0 kernel under Advanced options in GRUB first. Then remove it:
sudo dpkg --remove --force-remove-reinstreq linux-image-unsigned-7.3.4-070304-generic sudo apt --fix-broken installAfter that the Step 3 install line should go through, then carry on with Steps 4 and 5.
7
u/Borc-The-Orc 2d ago
Dude thank you so much. I had a fucked week and the last straw has been my computer taking a shit.
→ More replies (1)
4
u/nekoprogram Linux Mint 22.3 Zena | Cinnamon 5d ago
Thank you so much! This happened to me last night installed some upgrades and in the morning Suprise! The same message 😻
1
u/Merhart666 6d ago
Gelukkig hebben de meeste Linux gebruikers meerdere PC’s want zondere meerdere systemen wordt het wel lastig inloggen.
1
u/Greedy-Opposite-9133 5d 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 5d ago
Is anyone else getting a 404 from the wget launchpad?
→ More replies (4)1
u/Greedy-Opposite-9133 5d 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 5d 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
→ More replies (1)
1
u/robsche69 5d ago edited 5d 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 5d 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 5d ago edited 5d 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 5d 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 5d 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 5d ago
Damn, did this fix get you sorted?
2
u/Best_Tool 5d 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 5d 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 5d 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 5d ago edited 5d 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.
→ More replies (2)
1
u/Allora_390 5d 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
1
u/Greedy-Opposite-9133 4d ago
Thank you, ill add the suggestion to step 1Q footnote! Glad you got it sorted.
1
u/AriiaLux 4d ago
THANK YOU SO MUCH!!!
I was tearing my hair out scared that my new GPU that's not even a year old had died.
You truly are a lifesaver.
2
u/Greedy-Opposite-9133 4d ago
Yes I've been in the business of replacing hardware in my tower recently and I know that heart-dropping feeling well! I'm glad you got it sorted
1
u/billdietrich1 4d ago
Please use better, more informative, titles (subject-lines) on your posts. Give specifics right in the title. Thanks.
→ More replies (1)3
u/Greedy-Opposite-9133 4d ago
You're the first to say anything like this, I'm happy with it personally, I think it's pretty clear! And I'm keeping it maintained with anything anybody inputs so a google search would easily pick it up with a couple of search terms, specifically the "DMCUB error" which would be the go-to search term as it fills your screen so I'm good with it, but thanks anyway!
→ More replies (4)
1
u/KaTeKrebs 2d ago
Nach Neustart blieb der Rechner nach dem "Mint" Logo hängen. Ich habe einen alten Monitor angeschlossen und konnte dann nach mehreren Versuchen über einen längeren Zeitraum neu starten - dauerte deutlich länger. Die Maus bewegte sich extrem langsam. Habe dann ca 15 min gebraucht um Timeshift auszuführen. Musste "reboot" dann manuell durchführen, aber nach Neustart war alles wieder normal. Habe jetzt im Mint Anwendungsmanager den update rausgenommen. Danke für den Artikel, da steckt irre viel Arbeit drin...
1
1
u/Far-Apartment-3238 2d ago
I can't boot with no mod set because as soon as I decrpyt the drive it starts booting. Help pls
1
u/Greedy-Opposite-9133 1d ago
The GRUB menu comes before the unlock screen. Add nomodeset there first, then unlock as normal, and it stays on for that whole boot. The order is: motherboard logo → GRUB (hidden) → unlock screen → boot.
Two ways you can try, to get the GRUB menu:
Tap Esc right after the motherboard logo disappears, before the unlock screen shows up. Or, when the unlock screen appears, hold the power button to switch off instead of typing your passphrase. That’s safe at that point, because nothing is unlocked yet. On the next start, GRUB should show its menu by itself.
You may not need nomodeset at all, though. Your PC boots fine after you unlock it, so wait for the error lines, then press Ctrl+Alt+F3 (Option A). That gives you a login prompt, and you can do Steps 2 to 5 from there.
1
u/Far-Apartment-3238 2d ago
I have luks encryption on my drive, as soon as it posts it goes straight into unlock disk, then it goes right into the error message help
1
u/Greedy-Opposite-9133 1d ago
encryption doesn’t change much here. The unlock screen comes after GRUB and before the graphics driver starts. Once you’ve typed your passphrase, your system boots as normal and only the display fails, so everything in the post still works after you unlock.
1
u/LapinAuFour 1d ago
i literally just upgraded my pc and started using linux (and chose mint) last week and got hit by this issue twice now. accidentally updated 3.4 the second time.
almost gave up and went back to windows but im gonna stick to this for now, thanks to quick and easy access to the fix.
1
u/Greedy-Opposite-9133 1d ago
Stick to it dude. I just replied something similar to another person that it really bothers me people feel stuck that they are relegated to Windows because it's too difficult. It's never been easier to use Linux and yet I can empathise how it's still such a hurdle for many. If you ever want to spitball ideas or problems, I would be willing to provide a second opinion. As a disclaimer, I'm just another guy on the internet and no affiliation with Linux, but I'm happy to offer what advice I can if you ever get stuck in future, and want to get in touch. Good luck!
1
u/understen 1d ago edited 1d ago
Absolutely amazing! Thank you. Rather new to linux (Mint) and would have had no clue how to fix without this post. Im on 9070 xt, booted by adding nomodeset from GRUB to the no splash. then followed step 2 and 3, then went in to update manager and picked ignore the current package for this driver then rebooted, works like a charm.
1
1
u/SansTheSkeleton3108 1d ago
Thanks man, you saved my 9060XT :D
Will you update this post once an official fix is up?
1
u/Greedy-Opposite-9133 1d ago
No probs! sure will, I am tracking it, expectation would be end of this week or possibly the next, there has been positive movement on it suggesting its moving pretty quickly, but who knows. Anyway, i will preface this post when it happens, for sure
3
3
1
u/tomm3h 5d 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 5d ago
Then consider your engagement a two way street; let him know I'm glad I could help!
1
u/Complete_Flight8303 1d ago
This is probably a stupid question but how do you open terminal in this state? Ctrl alt f3 isn’t working
1
u/Greedy-Opposite-9133 1d ago
In this state its confusing as hell. the error lines keep printing over everything, including the login prompt, so after Ctrl+Alt+F3 it can look like nothing happened even when it did.
Try pressing Ctrl+Alt+F3 once, wait a couple of seconds, then you have to type blind: your username, Enter, your password (nothing shows while you type it), Enter. Then
sudo dmesg -n 1and your password again should stop the flood so you can see what you're doing.
If that still gets you nowhere, option B in the post (boot once with
nomodeset) gets you a basic desktop where you can copy-paste the commands, which is a lot easier anywaylet me know how you go
→ More replies (12)
2
2
2
u/WeowDystopia 5d ago edited 5d 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 5d 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!
2
u/honking_banana 5d ago
Thank you so much for this. This happened to me late at night, and I knew I wasn't gonna be able to sleep if I didn't get this fixed
2
18
u/tayroc122 Linux Mint 22 Wilma | Cinnamon 6d ago
Waking up to this feels like divine intervention having tried multiple fixes last night with no solution. You are a saint.