Searching a bit, it looks like some folks are having success with the Radeon 5700 (XT) and Fedora 32.
Not me. :-/
I first posted on ask.fedoraproject.org; and while I was able to drill down and get a bit more information, responses there seem to have tapered off.
A few data points:
$ lspci -k | grep -EA3 'VGA|3D|Display' 09:00.0 **VGA** compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c1) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 0b36 Kernel modules: amdgpu 09:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio
While that checks out, for some reason amdgpu isn’t listed in the lsmod output:
$ sudo lsmod | grep amd edac_mce_amd 32768 0 kvm_amd 114688 0 kvm 806912 1 kvm_amd ccp 102400 1 kvm_amd amd_iommu_v2 20480 0 pinctrl_amd 32768 0
I don’t get Wayland when I log in; I get the X11 fallback. Looking at the Xorg log, it never even tries the amdgpu driver. It tries the radeon driver; and when that fails, I get the generic framebuffer fallback.
Any suggestions for next steps to take?
On 7/1/20 10:44 PM, Braden McDaniel wrote:
$ lspci -k | grep -EA3 'VGA|3D|Display' 09:00.0 **VGA** compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c1) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 0b36 Kernel modules: amdgpu 09:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio
While that checks out, for some reason amdgpu isn’t listed in the lsmod output:
$ sudo lsmod | grep amd edac_mce_amd 32768 0 kvm_amd 114688 0 kvm 806912 1 kvm_amd ccp 102400 1 kvm_amd amd_iommu_v2 20480 0 pinctrl_amd 32768 0
What happens if you run "modprobe amdgpu"? What is the output of "cat /proc/cmdline"? Look through the logs starting from boot to see if anything is happening with the amd driver. "journalctl -b"
I don’t get Wayland when I log in; I get the X11 fallback. Looking at the Xorg log, it never even tries the amdgpu driver. It tries the radeon driver; and when that fails, I get the generic framebuffer fallback.
There is no amdgpu X driver. It's either radeon or modesetting. After running that modprobe command, try logging in again.
On Jul 2, 2020, at 2:09 AM, Samuel Sieb samuel@sieb.net wrote:
On 7/1/20 10:44 PM, Braden McDaniel wrote:
$ lspci -k | grep -EA3 'VGA|3D|Display' 09:00.0 **VGA** compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c1) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 0b36 Kernel modules: amdgpu 09:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 HDMI Audio
While that checks out, for some reason amdgpu isn’t listed in the lsmod output:
$ sudo lsmod | grep amd edac_mce_amd 32768 0 kvm_amd 114688 0 kvm 806912 1 kvm_amd ccp 102400 1 kvm_amd amd_iommu_v2 20480 0 pinctrl_amd 32768 0
What happens if you run "modprobe amdgpu"?
This:
# modprobe amdgpu modprobe: ERROR: could not insert 'amdgpu': Invalid argument
What is the output of "cat /proc/cmdline"?
This:
# cat /proc/cmdline BOOT_IMAGE=(hd1,gpt2)/vmlinuz-5.7.6-201.fc32.x86_64 root=UUID=cbcfb536-a8c8-4f79-8efd-60bec46d8a39 ro resume=UUID=9c3b9288-3bec-4565-8edc-c2083d05e51d nomodeset rhgb quiet
Look through the logs starting from boot to see if anything is happening with the amd driver. "journalctl -b"
Searching through that for “amd”:
Jul 02 02:25:33 mull kernel: amd_uncore: AMD NB counters detected Jul 02 02:25:33 mull kernel: amd_uncore: AMD LLC counters detected
This looks suspicious:
Jul 02 02:25:34 mull kernel: [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
Same thing a few seconds later:
Jul 02 02:25:39 mull kernel: [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
There is no amdgpu X driver. It's either radeon or modesetting.
Ah.
On Thu, Jul 2, 2020 at 12:14 PM Braden McDaniel braden@endoframe.com wrote:
# cat /proc/cmdline BOOT_IMAGE=(hd1,gpt2)/vmlinuz-5.7.6-201.fc32.x86_64 root=UUID=cbcfb536-a8c8-4f79-8efd-60bec46d8a39 ro resume=UUID=9c3b9288-3bec-4565-8edc-c2083d05e51d nomodeset rhgb quiet
This looks suspicious:
Jul 02 02:25:34 mull kernel: [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
Same thing a few seconds later:
Jul 02 02:25:39 mull kernel: [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
Just a guess based on this thread (I have no extra knowledge about the amd drivers) but it looks like the driver requires mode setting, but you've explicitly disabled it on the kernel command line (nomodeset).
Instead of changing it and regenerating the kernel parameters, I would try just editing it during grub boot and remove the "nomodeset" and see what happens.
Thanks, Richard
On Jul 2, 2020, at 1:55 PM, Richard Shaw hobbes1069@gmail.com wrote:
On Thu, Jul 2, 2020 at 12:14 PM Braden McDaniel braden@endoframe.com wrote:
# cat /proc/cmdline BOOT_IMAGE=(hd1,gpt2)/vmlinuz-5.7.6-201.fc32.x86_64 root=UUID=cbcfb536-a8c8-4f79-8efd-60bec46d8a39 ro resume=UUID=9c3b9288-3bec-4565-8edc-c2083d05e51d nomodeset rhgb quiet
This looks suspicious:
Jul 02 02:25:34 mull kernel: [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
Same thing a few seconds later:
Jul 02 02:25:39 mull kernel: [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
Just a guess based on this thread (I have no extra knowledge about the amd drivers) but it looks like the driver requires mode setting, but you've explicitly disabled it on the kernel command line (nomodeset).
Instead of changing it and regenerating the kernel parameters, I would try just editing it during grub boot and remove the "nomodeset" and see what happens.
Yep, that was it. Thanks!
For the record, *I* didn’t add “nomodeset” to the kernel command line; the Fedora install did that. Maybe you get that when installing with the “basic graphics” installer?
On 7/2/20 2:52 PM, Braden McDaniel wrote:
For the record, *I* didn’t add “nomodeset” to the kernel command line; the Fedora install did that. Maybe you get that when installing with the “basic graphics” installer?
Yes. What was the reason that you chose that option when installing?
On Jul 2, 2020, at 7:43 PM, Samuel Sieb samuel@sieb.net wrote:
On 7/2/20 2:52 PM, Braden McDaniel wrote:
For the record, *I* didn’t add “nomodeset” to the kernel command line; the Fedora install did that. Maybe you get that when installing with the “basic graphics” installer?
Yes. What was the reason that you chose that option when installing?
The default graphical installer failed entirely and fell back to the text mode installer.
On 2020-07-02 19:43, Samuel Sieb wrote:
On 7/2/20 2:52 PM, Braden McDaniel wrote:
For the record, *I* didn’t add “nomodeset” to the kernel command line; the Fedora install did that. Maybe you get that when installing with the “basic graphics” installer?
Yes.
…And it turns out that though I modified all but the rescue kernel command lines (using grubby) to omit the "nomodeset" argument, new kernels that are installed via updates still get that argument.
How do I change the template that new kernels use for their default arguments?
On Wed, 1 Jul 2020 23:09:29 -0700 Samuel Sieb samuel@sieb.net wrote:
There is no amdgpu X driver.
Yes there is. It's xorg-x11-drv-amdgpu. It's not installed by default the last time I looked.
Jim
On Jul 2, 2020, at 2:04 PM, James Szinger jszinger@gmail.com wrote:
On Wed, 1 Jul 2020 23:09:29 -0700 Samuel Sieb samuel@sieb.net wrote:
There is no amdgpu X driver.
Yes there is. It's xorg-x11-drv-amdgpu. It's not installed by default the last time I looked.
I did find that and install it; but that did not seem to improve my situation.
On Thu, 2 Jul 2020 15:03:44 -0400 Braden McDaniel braden@endoframe.com wrote:
On Jul 2, 2020, at 2:04 PM, James Szinger jszinger@gmail.com wrote:
On Wed, 1 Jul 2020 23:09:29 -0700 Samuel Sieb samuel@sieb.net wrote:
There is no amdgpu X driver.
Yes there is. It's xorg-x11-drv-amdgpu. It's not installed by default the last time I looked.
I did find that and install it; but that did not seem to improve my situation.
I think the nomodeset kernel parameter is key.
Jim
On 7/2/20 11:04 AM, James Szinger wrote:
On Wed, 1 Jul 2020 23:09:29 -0700 Samuel Sieb samuel@sieb.net wrote:
There is no amdgpu X driver.
Yes there is. It's xorg-x11-drv-amdgpu. It's not installed by default the last time I looked.
Interesting, I wonder what it's for. My computer with a new AMD GPU doesn't have that driver and works perfectly fine. Although it is using Wayland, so maybe it's not needed there.
-
Braden McDaniel -
James Szinger -
Richard Shaw -
Samuel Sieb