[image] freed00m: Hmm, then it’s ptobably newer bug. I have no clue then. A friend just send me this 209721 – No output after AMDGPU loads. It seems this issue will be fixed soon! Answer from anon80505238 on forum.manjaro.org
[image] freed00m: Hmm, then it’s ptobably newer bug. I have no clue then. A friend just send me this 209721 – No output after AMDGPU loads. It seems this issue will be fixed soon! Answer from anon80505238 on forum.manjaro.org
🌐
Gentoo Wiki
wiki.gentoo.org › wiki › AMDGPU
AMDGPU - Gentoo wiki
Likewise, if DC needs to be disabled for any particular reason, option amdgpu.dc=0 can be used on the kernel command line.
🌐
Linux Kernel
kernel.org › doc › html › v5.7 › gpu › amdgpu-dc.html
drm/amd/display - Display Core (DC) — The Linux Kernel documentation
When CONFIG_DRM_AMD_DC is enabled, DC will be initialized by default for supported ASICs. To force disable, set amdgpu.dc=0 on kernel command line.
🌐
GitHub
github.com › rockowitz › ddcutil › issues › 99
ddcutil works with amdgpu.dc=0 but not with amdgpu.dc=1 · Issue #99 · rockowitz/ddcutil
December 13, 2019 - With amdgpu.dc=0 (disabled) ddcutil works correctly for adjusting all monitor settings. I need amdgpu.dc=1 to have audio through displayport to my monitor. When booted with amdgpu.dc=1, ddcutil fai...
Author   rockowitz
🌐
Arch Linux Forums
bbs.archlinux.org › viewtopic.php
[solved] 5.13.1 amdgpu black screen / [testing] Repo Forum / Arch Linux Forums
July 11, 2021 - I've bypassed this stuff by changing amdgpu.dc to 0 (amdgpu.dc = 0) and by downgrading to the latest 5.12 kernel.
🌐
Reddit
reddit.com › r/linuxquestions › amdgpu dc causes one issue when enabled, different issue when disabled
r/linuxquestions on Reddit: AMDGPU DC causes one issue when enabled, different issue when disabled
August 27, 2018 -

TL;DR: With amdgpu.dc=0, my 1440p monitor works, but intensive games will eventually crash my system. With amdgpu.dc=1, intensive games are perfectly stable, but my 1440p monitor doesn't work.

I'll start from the beginning.

When I upgraded to Lubuntu 18.04 w/ Kernel 4.15 back in April my primary monitor, a 1440p DVI monitor, was receiving no signal. Xrandr could detect the monitor was plugged in, but no modes were found. After some Googling I found out that setting amdgpu.dc=0 fixed this problem.

Fast forward to Wednesday and with the recent release of Steam Play, I'm eager to start testing some games. I launch a number of titles and run a few benchmarks, everything seems fine. Then I try to play GTA V for an extended period of time. This is when I discover that after playing for about 30 minutes, the graphics start to get corrupted and then eventually my system freezes.

I look at my kernel log and discover that at the exact moment the graphical corruption begins, I start getting spammed with variations of the following lines:

Aug 25 23:54:59 THE-GIANT-SLAB kernel: [10462.962860] amdgpu 0000:23:00.0: GPU fault detected: 146 0x0ff0480c
Aug 25 23:54:59 THE-GIANT-SLAB kernel: [10462.962864] amdgpu 0000:23:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x000003FE
Aug 25 23:54:59 THE-GIANT-SLAB kernel: [10462.962866] amdgpu 0000:23:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0404800C
Aug 25 23:54:59 THE-GIANT-SLAB kernel: [10462.962869] amdgpu 0000:23:00.0: VM fault (0x0c, vmid 2) at page 1022, read from 'TC4' (0x54433400) (72)

I spend a couple of days running various tests to try and either verify or debunk the claim of a faulty GPU. I had a breakthrough today when I decided to try launching the kernel without amdgpu.dc=0. As expected, it boots up and my 1440p monitor is not receiving a signal. I have now been playing GTA V for about two hours without any errors in dmesg.

So that's the situation. I can either have my monitor working, and experience full system crashes, or I can have perfectly stable gameplay, but only on my smaller secondary monitor. As I'm sure you can imagine, neither situation is particularly ideal.

How do I even start trying to come up with a solution to this?

Thanks in advance for your advice.

EDIT: Dunno how I completely forgot to post my specs. Derp.

GPU: 8GB Sapphire RX 480 Nitro+

CPU: AMD Ryzen 5 1600

RAM: 16GB Corsair Vengeance LPX 3200MHz

Mobo: MSI Tomahawk B350

Kernel: 4.15.0.33-generic

Mesa version: 18.3.0-devel (padoka PPA)

EDIT 2: Installing a fresher kernel sorted it out. Currently using my 1440p monitor with AMDGPU DC enabled. Thanks everyone! Now if you'll excuse me, I'm off to play some GTA V...

🌐
Linux Mint Forums
forums.linuxmint.com › board index › main edition support › hardware support › graphics cards & monitors
[SOLVED] AMDGPU conflict with iGPU (screen blank, login loop) - Linux Mint Forums
SucremePi wrote: ⤴Fri Oct 13, 2023 12:10 pmso when pc starts up, everything would work for a couple of seconds and then screen would freeze, and then turn off, and then turn back on and il be at the login screen. Try adding the amdgpu.dc=0 kernel parameter to see if that helps.
Find elsewhere
🌐
Red Hat
bugzilla.redhat.com › show_bug.cgi
1594488 – Blank screen since Kernel 4.17 (AMDGPU.DC) on Amd Radeon RX460 and RX380 on Ultrawidescreen Monitor
Red Hat Bugzilla – Bug 1594488 · This site requires JavaScript to be enabled to function correctly, please enable it · Privacy Contact FAQ Legal
🌐
Jsykora
jsykora.info › 2024 › 03 › linux-6-7-x-on-amd-gpu-rx570-requires-the-kernel-parameter-amdgpu-dc0
Linux 6.7.x on AMD GPU RX570 requires the kernel parameter amdgpu.dc=0 – Wired && Coded;
[ 7.708052] amdgpu 0000:09:00.0: [drm] Cannot find any crtc or sizes · Googling that message led to the bbs.archlinux forum with the advise from April 2020 to add the kernel boot command line parameter: amdgpu.dc=0 · This solved the blank screen issue. I added this parameter in /etc/default/grub to the parameter GRUB_CMDLINE_LINUX, and regenerated the main configuration file with grub2-mkconfig.
🌐
Dedoimedo
dedoimedo.com › computers › linux-amd-gpu-black-screen-boot.html
Linux, AMD GPU, black screen on boot
December 23, 2021 - amdgpu.noretry=0 amdgpu.dc=1 · These need to be appended to the kernel boot line in the boot menu.
🌐
ArchWiki
wiki.archlinux.org › title › AMDGPU
AMDGPU - ArchWiki
May 28, 2026 - If you encounter issues where the ... you can workaround the issue by setting the kernel parameter amdgpu.runpm=0, which prevents the dGPU from being powered down dynamically at runtime....
🌐
Reddit
reddit.com › r/linuxmemes › amdgpu.dc=0 my beloved 🥰
r/linuxmemes on Reddit: amdgpu.dc=0 my beloved 🥰
June 2, 2021 - amdgpu is your AMD GPU and DC is disconnect. so when you make that value 0 it prevents it from being disconnected. boom it's foolproof.
🌐
DRI
dri.freedesktop.org › docs › drm › gpu › amdgpu › display › dc-debug.html
Display Core Debug tools — The Linux Kernel documentation
In summary, the dc_debug_options is an interesting form for identifying the problem. Display core provides a feature named visual confirmation, which is a set of bars added at the scanout time by the driver to convey some specific information. In general, you can enable this debug option by using: echo <N> > /sys/kernel/debug/dri/0/amdgpu...
🌐
Random Blog
randomblog.hu › fix-amdgpu-driver-problems-for-your-amd-video-card-in-ubuntu-18-04-after-upgrading-to-a-new-kernel
Fix AMDGPU driver problems for your AMD video card in Ubuntu 18.04 after upgrading to a new kernel – Random Blog
January 27, 2020 - GRUB_GFXMODE=1920x1080x32 GRUB_CMDLINE_LINUX_DEFAULT="radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1"
Top answer
1 of 3
3

June 14, 2018 Update

Based on this ArchLinux forum thread it appears you need to add:

amdgpu.dc=0

to your /etc/default/grub LINUX line after quiet splash. Then run sudo update-grub.


Being a new install of Ubuntu 18.04 you are one of the lucky ones that can use journalctl to look at the last boot (which locked up). Use:

journalctl -b-1

Then press the End key to jump to EOF (End Of File). In my successful last boot it says:

Jun 10 16:18:51 alien systemd[1]: Unmounting /mnt/d...
Jun 10 16:18:51 alien systemd[1]: Unmounted /run/user/1000.
Jun 10 16:18:51 alien systemd[1]: Unmounted /media/rick/Ubuntu 18.04 LTS amd64.
Jun 10 16:18:51 alien systemd[1]: Unmounted /boot/efi.
Jun 10 16:18:51 alien ntfs-3g[648]: Unmounting /dev/nvme0n1p8 (Shared_WSL+Linux)
Jun 10 16:18:51 alien ntfs-3g[648]: Permissions cache : 21 writes, 4033288 reads, 99.9% hits
Jun 10 16:18:51 alien systemd[1]: Unmounted /media/rick/casper-rw.
Jun 10 16:18:51 alien systemd[1]: Unmounted /mnt/e.
Jun 10 16:18:51 alien ntfs-3g[736]: Unmounting /dev/sda3 (HGST_Win10)
Jun 10 16:18:51 alien ntfs-3g[736]: Permissions cache : 754 writes, 4108560 reads, 99.9% hits
Jun 10 16:18:51 alien ntfs-3g[637]: Unmounting /dev/nvme0n1p4 (NVMe_Win10)
Jun 10 16:18:51 alien ntfs-3g[637]: Permissions cache : 987 writes, 4983239 reads, 99.9% hits
Jun 10 16:18:51 alien systemd[1]: Unmounted /mnt/d.
Jun 10 16:18:51 alien systemd[1]: Unmounted /mnt/c.
Jun 10 16:18:51 alien systemd[1]: Reached target Unmount All Filesystems.
Jun 10 16:18:51 alien systemd[1]: Stopped target Local File Systems (Pre).
Jun 10 16:18:51 alien systemd[1]: Stopped Remount Root and Kernel File Systems.
Jun 10 16:18:51 alien systemd[1]: Stopped Create Static Device Nodes in /dev.
Jun 10 16:18:51 alien systemd[1]: Reached target Shutdown.
Jun 10 16:18:51 alien systemd[1]: Reached target Final Step.
Jun 10 16:18:51 alien systemd[1]: dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device: Dev dev-
Jun 10 16:18:51 alien systemd[1]: Received SIGRTMIN+20 from PID 18665 (plymouthd).
Jun 10 16:18:51 alien systemd[1]: Started Show Plymouth Reboot Screen.
Jun 10 16:18:51 alien systemd[1]: Starting Reboot...
Jun 10 16:18:51 alien systemd[1]: Shutting down.
Jun 10 16:18:51 alien kernel: systemd-shutdow: 36 output lines suppressed due to ratelimiting
Jun 10 16:18:51 alien systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Jun 10 16:18:51 alien dnsmasq[1393]: exiting on receipt of SIGTERM
Jun 10 16:18:51 alien systemd-journald[288]: Journal stopped
lines 46804-46832/46832 (END)

In yours you need to look for error messages.

You may have to use the Page Up key to see them.

When you have found what you are looking for (or have given up looking) press Q to exit.

If overheating was causing the shutdown you can install Intel Powerclamp: Stop cpu from overheating

Besides lm-sensors you can get temperature readings for all thermal zones directly from the command line using this one-liner:

$ paste <(cat /sys/class/thermal/thermal_zone*/type) <(cat /sys/class/thermal/thermal_zone*/temp) | column -s $'\t' -t | sed 's/\(.\)..$/.\1°C/'

INT3400 Thermal  20.0°C
SEN1             44.0°C
SEN2             52.0°C
SEN3             64.0°C
SEN4             59.0°C
B0D4             73.0°C
pch_skylake      76.5°C
x86_pkg_temp     73.0°C

Reported in Celsius and drop the last three zeros.

2 of 3
1

in addition to solution with amdgpu.dc=0 kernel option, upgrade to ubuntu 18.10 kernel based on linux 4.18 has fixed this issue and no longer requires this amdgpu.dc=0 parameter in kernel boot for graphics to work correctly. (AMD Stoney hardware)

🌐
Phoronix
phoronix.com › home › forum › linux graphics drivers › radeon linux drivers
Linux 4.17 To Enable AMDGPU DC By Default For All Supported GPUs - Phoronix Forums
March 16, 2018 - Config: Polaris RX 480 System: Debian Sid Kernel: Linux 4.15.0-1-amd64 Source: /etc/default/grub $ sudo vim /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet iommu=pt iommu=1 amdgpu.dc=1 amdgpu.audio=1" #GRUB_CMDLINE_LINUX="text" #GRUB_CMDLINE_LINUX="" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
🌐
Linux Kernel
docs.kernel.org › gpu › amdgpu › module-parameters.html
Module Parameters — The Linux Kernel documentation
This is to keep the wavefront context for debugging (0 = queue eviction, 1 = no queue eviction). The default is 0 (queue eviction). ... Enable PCIe P2P (requires large-BAR). Default value: true (on) ... Override display features enabled. See enum DC_FEATURE_MASK in drivers/gpu/drm/amd/incl...