Fedora 36 (Nobara) Black Screen with AMD Radeon 6600 after Update

Hi all,

I am having trouble with my Fedora 36 after upgrade to new kernel kernel-5.19.6-202.fsync.fc36.x86_64 (from kernel-5.19.4-201.fsync.fc36.x86_64 which also gave the same issue)
I’m running an AMD Radeon RX 6600 on 4x monitors.
There is no login screen, just black screen, sometimes with mouse pointer, sometimes without.

I can log in without issue if I use a previous kernel-5.18.19-201.fsync.fc36.x86_64
But anything after that, kernel-5.19.4-201.fsync.fc36.x86_64 and kernel-5.19.6-203.fsync.fc36.x86_64 gives me a black screen.

Here is a list of the current kernels available on my machine:

[linux@192-168-###-### ~]$ rpm -qa kernel

Here are the details of my machine:

[linux@192-168-###-### ~]$ inxi -Fzx
  Kernel: 5.18.19-201.fsync.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.37-27.fc36 Desktop: KDE Plasma v: 5.25.4
    Distro: Nobara release 36 (Thirty Six)
  Type: Desktop Mobo: ASUSTeK model: P8Z68 DELUXE/GEN3 v: Rev 1.xx
    serial: <superuser required> UEFI: American Megatrends v: 3304
    date: 04/17/2012
  Info: quad core model: Intel Core i7-2600K bits: 64 type: MT MCP
    arch: Sandy Bridge rev: 7 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 3408 high: 3586 min/max: 1600/3800 cores: 1: 3544
    2: 3073 3: 3060 4: 3477 5: 3458 6: 3541 7: 3526 8: 3586 bogomips: 54578
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Device-1: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] vendor: XFX
    driver: amdgpu v: kernel arch: RDNA 2 bus-ID: 04:00.0
  Device-2: Microsoft LifeCam VX-2000 type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 2-1.1:3
  Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.3 driver: X:
    loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu
    resolution: 1: 1920x1080~60Hz 2: 1920x1080~60Hz 3: 1920x1080~60Hz
    4: 1920x1080~60Hz
    renderer: NAVI23 (navi23 LLVM 14.0.5 DRM 3.46 5.18.19-201.fsync.fc36.x86_64)
    v: 4.6 Mesa 22.3.0-devel direct render: Yes
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio
    vendor: ASUSTeK P8P67 Deluxe driver: snd_hda_intel bus-ID: 2-1.1:3
    v: kernel bus-ID: 00:1b.0
  Device-2: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel
    bus-ID: 04:00.1
  Device-3: Microsoft LifeCam VX-2000 type: USB
    driver: snd-usb-audio,uvcvideo
  Sound Server-1: ALSA v: k5.18.19-201.fsync.fc36.x86_64 running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.57 running: yes
  Device-1: Intel 82579V Gigabit Network vendor: ASUSTeK P8P67 Deluxe
    driver: e1000e v: kernel port: f040 bus-ID: 00:19.0
  IF: eno1 state: down mac: <filter>
  Device-2: Qualcomm Atheros AR9462 Wireless Network Adapter
    vendor: Lite-On driver: ath9k v: kernel bus-ID: 0e:00.0
  IF: wlp14s0 state: down mac: <filter>
  Device-3: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK P8P67 and other motherboards driver: r8169 v: kernel
    port: a000 bus-ID: 11:00.0
  IF: enp17s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
  Device-1: ASUSTek Bluetooth Adapter type: USB driver: btusb v: 0.8
    bus-ID: 2-1.7:7
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
  Local Storage: total: 5.89 TiB used: 408.12 GiB (6.8%)
  ID-1: /dev/sda vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB
  ID-2: /dev/sdb vendor: Western Digital model: WD Green 2.5 1000GB
    size: 931.51 GiB
  ID-3: /dev/sdc vendor: Kingston model: SHSS37A480G size: 447.13 GiB
  ID-4: /dev/sdd vendor: Western Digital model: WD40EZRZ-00GXCB0
    size: 3.64 TiB
  ID-1: / size: 929.91 GiB used: 407.8 GiB (43.9%) fs: btrfs dev: /dev/dm-0
    mapped: luks-150d30bd-############
  ID-2: /boot size: 973.4 MiB used: 322.3 MiB (33.1%) fs: ext4
    dev: /dev/sdb2
  ID-3: /home size: 929.91 GiB used: 407.8 GiB (43.9%) fs: btrfs
    dev: /dev/dm-0 mapped: luks-150d30bd-##########
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
  System Temperatures: cpu: 36.0 C mobo: N/A gpu: amdgpu temp: 36.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
  Processes: 404 Uptime: 18m Memory: 31.21 GiB used: 7.42 GiB (23.8%)
  Init: systemd target: graphical (5) Compilers: gcc: 12.2.1 clang: 14.0.5
  Packages: 183 Shell: Bash v: 5.1.16 inxi: 3.3.19

and the Graphics card information is here:

[linux@192-168-###-### ~]$ dnf list installed \*amd*
Installed Packages
amd-gpu-firmware.noarch                                                                        20220815-138.fc36                                                                      @nobara-base
teamd.x86_64                                                                                   1.31-5.fc36                                                                            @anaconda   
xorg-x11-drv-amdgpu.x86_64                                                                     22.0.0-1.fc36                                                                          @anaconda   

and here:

[linux@192-168-###-### ~]$ dmesg | grep -iE 'secure|amd'
[    0.000000] secureboot: Secure boot disabled
[    0.012034] secureboot: Secure boot disabled
[    0.012035] RAMDISK: [mem 0x5c55a000-0x5f3f2fff]
[    0.012037] Allocated new RAMDISK: [mem 0x81c14e000-0x81efe637b]
[    0.020233] Move RAMDISK from [mem 0x5c55a000-0x5f3f237b] to [mem 0x81c14e000-0x81efe637b]
[    8.393460] AMD-Vi: AMD IOMMUv2 functionality not available on this system - This is not a bug.
[    8.833093] [drm] amdgpu kernel modesetting enabled.
[    8.833166] amdgpu: CRAT table not found
[    8.833169] amdgpu: Virtual CRAT table created for CPU
[    8.833181] amdgpu: Topology: Add CPU node
[    8.833332] amdgpu 0000:04:00.0: vgaarb: deactivate vga console
[    8.833434] amdgpu 0000:04:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
[    8.834931] amdgpu 0000:04:00.0: No more image in the PCI ROM
[    8.834946] amdgpu 0000:04:00.0: amdgpu: Fetched VBIOS from ROM BAR
[    8.834948] amdgpu: ATOM BIOS: 113-23L86HMD2-D02
[    8.834963] amdgpu 0000:04:00.0: amdgpu: PCIE atomic ops is not supported
[    8.834990] amdgpu 0000:04:00.0: amdgpu: VRAM: 8176M 0x0000008000000000 - 0x00000081FEFFFFFF (8176M used)
[    8.834992] amdgpu 0000:04:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
[    8.834994] amdgpu 0000:04:00.0: amdgpu: AGP: 267894784M 0x0000008400000000 - 0x0000FFFFFFFFFFFF
[    8.835282] [drm] amdgpu: 8176M of VRAM memory ready
[    8.835283] [drm] amdgpu: 8176M of GTT memory ready.
[    8.841275] amdgpu 0000:04:00.0: amdgpu: PSP runtime database doesn't exist
[   12.611938] amdgpu 0000:04:00.0: amdgpu: STB initialized to 2048 entries
[   12.655317] amdgpu 0000:04:00.0: amdgpu: Will use PSP to load VCN firmware
[   12.821808] amdgpu 0000:04:00.0: amdgpu: RAS: optional ras ta ucode is not available
[   12.839908] amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[   12.839930] amdgpu 0000:04:00.0: amdgpu: smu driver if version = 0x0000000f, smu fw if version = 0x00000013, smu fw program = 0, version = 0x003b2900 (59.41.0)
[   12.839936] amdgpu 0000:04:00.0: amdgpu: SMU driver if version not matched
[   12.839945] amdgpu 0000:04:00.0: amdgpu: use vbios provided pptable
[   12.888666] amdgpu 0000:04:00.0: amdgpu: SMU is initialized successfully!
[   13.190228] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[   13.219383] amdgpu: HMM registered 8176MB device memory
[   13.219434] amdgpu: SRAT table not found
[   13.219435] amdgpu: Virtual CRAT table created for GPU
[   13.219595] amdgpu: Topology: Add dGPU node [0x73ff:0x1002]
[   13.219599] kfd kfd: amdgpu: added device 1002:73ff
[   13.219616] amdgpu 0000:04:00.0: amdgpu: SE 2, SH per SE 2, CU per SH 8, active_cu_number 28
[   13.219711] amdgpu 0000:04:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[   13.219712] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[   13.219714] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[   13.219715] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[   13.219716] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[   13.219717] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[   13.219718] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[   13.219719] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[   13.219720] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[   13.219721] amdgpu 0000:04:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[   13.219722] amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[   13.219723] amdgpu 0000:04:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
[   13.219724] amdgpu 0000:04:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1
[   13.219725] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1
[   13.219726] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1
[   13.219728] amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 1
[   13.221375] [drm] Initialized amdgpu 3.46.0 20150101 for 0000:04:00.0 on minor 0
[   13.225130] fbcon: amdgpudrmfb (fb0) is primary device
[   13.225133] amdgpu 0000:04:00.0: [drm] fb0: amdgpudrmfb frame buffer device
[   27.548659] snd_hda_intel 0000:04:00.1: bound 0000:04:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])

Any ideas how to resolve this problem?

What is this tag for? Have you been compiling and installing your own kernels? I don’t seem to have any of those patch versions here:

$ rpm -q kernel

What is the output of rpm -qi kernel?

Hi Scott,

I have not been compiling and installing my own kernels, these are kernels made by Glorious Eggroll (Thomas Crider) who is the brains at Redhat/Proton, has been making these for the Nobara project version of fedora 36.

Note: I managed to get it running but its intermittent, sometimes it boots up sometimes it doesn’t, but in order to make it boot, I have to first, on boot, do and edit (E) on the grub screen and add nomodeset, then boot up from there… then reboot after that back to normal then it will work. If I reboot it again after that without using the nomodeset hack, it will go to black screen so its obvious somewhere there is an issue with the graphics because it happens on both nvidia and amd and its not their drivers either, its something to do with the kernel updates and it happens on almost every kernel update. I’ve seen many posts here that include this same problem, often people claiming its the nvidia drivers, but its not because it also happens on amd as well and there has been a hack made by a contributor here named Jeff that seems to fix some of it. Nothing to do with the graphics drivers.

Here is the output as requested:

[linux@192-168-###-### ~]$ rpm -qi kernel
Name        : kernel
Version     : 5.18.19
Release     : 201.fsync.fc36
Architecture: x86_64
Install Date: Wed 24 Aug 2022 15:53:04
Group       : Unspecified
Size        : 0
License     : GPLv2 and Redistributable, no modification permitted
Signature   : RSA/SHA256, Wed 24 Aug 2022 06:47:08, Key ID 9e2b5b72d3a642fc
Source RPM  : kernel-5.18.19-201.fsync.fc36.src.rpm
Build Date  : Wed 24 Aug 2022 03:23:01
Build Host  : copr-hv-x86-64-01-prod-02069407-20220823-170509
Vendor      : Fedora Copr - user sentry
URL         : https://www.kernel.org/
Summary     : The Linux kernel
Description :
The kernel meta package
Name        : kernel
Version     : 5.19.6
Release     : 202.fsync.fc36
Architecture: x86_64
Install Date: Tue 06 Sep 2022 00:55:44
Group       : Unspecified
Size        : 0
License     : GPLv2 and Redistributable, no modification permitted
Signature   : RSA/SHA256, Mon 05 Sep 2022 22:23:25, Key ID ace25d2532ce7d06
Source RPM  : kernel-5.19.6-202.fsync.fc36.src.rpm
Build Date  : Mon 05 Sep 2022 19:03:54
Build Host  : copr-hv-x86-64-01-prod-02149606-20220905-084652
Vendor      : Fedora Copr - user gloriouseggroll
URL         : https://www.kernel.org/
Summary     : The Linux kernel
Description :
The kernel meta package
Name        : kernel
Version     : 5.19.6
Release     : 203.fsync.fc36
Architecture: x86_64
Install Date: Tue 06 Sep 2022 15:11:18
Group       : Unspecified
Size        : 0
License     : GPLv2 and Redistributable, no modification permitted
Signature   : RSA/SHA256, Tue 06 Sep 2022 13:17:02, Key ID ace25d2532ce7d06
Source RPM  : kernel-5.19.6-203.fsync.fc36.src.rpm
Build Date  : Tue 06 Sep 2022 09:48:40
Build Host  : copr-hv-x86-64-03-prod-02153647-20220905-223933
Vendor      : Fedora Copr - user gloriouseggroll
URL         : https://www.kernel.org/
Summary     : The Linux kernel
Description :
The kernel meta package


That can be fixed as a permanent solution by editing /etc/default/grub and adding that option into the kernel command line. Once the edit has been saved it can be updated into the boot loader with grub2-mkconfig -o /boot/grub2/grub.cfg. After editing that file the change will remain for updates until you do a complete new install that wipes out that file and replaces it.

That “hack” as you called it is actually a permanent fix for your system. Depending upon the hardware involved some need the modeset and some do not so it is difficult to actually provide an install method that works for everyone.

1 Like

Unfortunately if I make it a permanent solution by editing the grub.cfg, then I will not be able to set the screen resolution properly and its stuck at 800. I’m not sure why but once you reboot from that and go back to the original configuration, I’m able to log in again.

UPDATE: There has been a new update on the kernel (kernel-5.19.7-202.fsync.fc36.x86_64) for which the problem has now been resolved. Obviously this issue is very common on each kernel update and is always affecting the graphics.

The problem is, by this kind of thing happening, it ruins the great original experience one has with Fedora, especially for those that are new to the Fedora/Linux scene… Hopefully in the future, when kernels are updated and compiled, the graphics side of thing is checked properly before the update is released because nobody is really in a hurry to get the latest kernel, but when you do a dnf update or install software, and the updates appear, the most logical and rational thing would be to accept the updates so that your rig is working at its optimal, always trusting that those updates have been thoroughly tested, which unfortunately they aren’t, thus resulting in a black screen login… which then causes the user to get very frustrated with the operating system. Hopefully things change now and updates are released with a lot more caution.

Hey there. We are a community distribution and this kind of testing depends on users like you testing it out on their own hardware. This is a great simple way for you to help contribute to make Fedora better for yourself and other users with similar hardware as well. Please consider helping us vet future kernels:


No problem, I am very happy to help give feedback and with the testing of kernels, I use Fedora as a daily machine, I use it for 99% of the things I do and I’ve been using Linux (all sorts of distros) for the last 15 years at least… Fedora has always been the best by far. :bluethumb: