Radeon GPU Video Ports are not recognized even the GPU itself gets recognized RX 7900 XT
Hello,
first of all i'm very sorry for my bad english and thank you very much for reading my issue. I'm pretty new to Linux so its possible, that i miss some information you need for helping me. Issue: A few weeks i build me a new PC on which i have a big issue with Linux and have no idea how to fix this issue. After the moment Grub starts booting Linux i do not get any video out of my Graphics card. It doesn't matter which Linux distribution i try the issue is on all distributions i tried so far (Manjaro, Kubuntu, Arch, Debian). On Xrandr i can see the video signals of my motherboard but not these from my GPU. The issue can't be on the Hardware itself because the video ports are working on Grub and in Windows, additional if i type neofetch in the shell it shows me my gpu. Hardware i'm using: OS's: Arch Linux / Windows 11 (Dual Boot) GPU: RX 7900 XT (Sapphire Nitro+) CPU: Ryzen 7 7800X3D Mainboard: Asus TUF B650-Plus Wifi Ram: G.Skill Flare X5 Both of my monitors are plugged in via DP Things i already tried: Using different Distributions (Manjaro, Debian, Arch, Kubuntu) Using "nomodeset" in grub Resetting Vmos Repluging the GPU Thank you in advance. |
Try it with only one monitor and plug it via HDMI.
First monitor may not work via DP (same issue here with a Radeon RX 6600). |
Quote:
Loading Linux Linux ... Loading initial ramdisk ... after these my screen gets frozen. |
The Ryzen 7 7800X3D contains an IGP. Go to UEFI and completely disable this IGP.
|
Quote:
|
Can you boot a live Linux (knoppix, grml, …) into console or GUI?
|
Quote:
|
Are there any log files i could check for error messages?
|
The traditional log for graphics is Xorg.0.log in /var/log/. Some distros and/or DMs move it to your homedir, in ~/.local/share/xorg/. The DM may have its own log(s) in /var/log/, e.g. sddm.log or lightdm/. The journal should also have relevant logging that is available per specific unit, such as journalctl -b -2 -u lightdm to access LightDM info for the second prior boot.
|
Quote:
in Xorg.0.log i found Code:
[ 7.434] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=3 (/dev/input/event12) it shows me, that the drivers are loaded Code:
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14d8 with "sudo modprobe amdgpu" i dont get any error message and with "lsmod | grep amdgpu" i get amdgpu 13352960 58 amdxcp 12288 1 amdgpu i2c_algo_bit 20480 1 amdgpu drm_ttm_helper 12288 1 amdgpu ttm 110592 2 amdgpu,drm_ttm_helper drm_exec 12288 1 amdgpu gpu_sched 65536 1 amdgpu drm_suballoc_helper 12288 1 amdgpu drm_buddy 20480 1 amdgpu drm_display_helper 229376 2 amdgpu video 77824 3 asus_wmi,amdgpu,asus_nb_wmi another thing i tested was using amdgpu.dc=0 in the grub parameters but didn't worked. i also tried reinstalling following packages xf86-video-amdgpu-git mesa-git lib32-mesa-git vulkan-radeon-git in journalctl -b -2 -u sddm and in var/log/sddm.log there is no error message |
Code:
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 31 [Radeon RX 7900 XT/7900 XTX] (rev cc) Code:
0e:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raphael (rev cb) |
inxi -GSaz --vs does a nice, concise job of reporting drivers, software and hardware. Due to the nature of X, it cannot provide some graphics info unless run from within a running X session. "Drivers" manifest in multiple layers. The kernel "driver" is called a kernel module, amdgpu in your case for both your GPUs. Non-working X more often is not a failure of kernel module, but other layers, such as DRM, Mesa and/or display driver, all of which inxi tries to report status on.
With both onboard and discrete GPU in the same PC, it is often necessary to adjust BIOS settings to get graphics output from the output ports desired. Some users employ a discrete GPU for "offloading" certain video operations, not directly through its own output ports. It used to be normal that it was impossible to employ outputs from both motherboard and discrete GPU card on the same boot, an either/or situation. Some newer hardware allows both, possibly yours. When Xorg.0.log has only one line containing (EE) (near the top), then any graphics trouble encountered is normally in the software that runs on it, not X itself. Any (EE) line after the first relates to a problem area. Nomodeset is a troubleshooting parameter, intended to allow minimal graphics capability that enables troubleshooting within a limited graphical environment. It's use otherwise will always reduce functionality below that normally expected when all is well. |
Quote:
with inxi -GSaz --vs it shows me Code:
perl: warning: Setting locale failed. Code:
perl: warning: Setting locale failed. is there a way to set a driver as primary driver manually? |
Quote:
|
When was the Sapphire Nitro+ introduced to market? Is it possible that your installed firmware isn't new enough to include it? The latest amdgpu firmware I've seen is 20240201 in Tumbleweed. "Sapphire NITRO+ driver: N/A" in inxi suggests firmware is likely your obstacle. I would expect kernel module amdgpu to apply to both discrete and onboard GPUs.
-Gxx is a subset of -Ga. The inxi 3.3.31 version's -G I think was still a little buggy. 3.3.33 was released 2 days ago, and may better describe your configuration. If your distro doesn't disallow it, you can update it directly from upstream using its -U switch. If it doesn't work, you may need to edit /etc/inxi.conf to disable the disabler. Or just get inxi from upstream directly. |
All times are GMT -5. The time now is 02:46 PM. |