Bug 1960937

After manually bisect the OSTree commits, for Silverblue Rawhide, 

● ostree://fedora:fedora/rawhide/x86_64/silverblue
                   Version: Rawhide.20210513.n.0 (2021-05-13T06:06:02Z)
                    Commit: a20dcca277db19444d7072c658aa1ead3d3d2b895a91f91b7007c39d0f687511
              GPGSignature: Valid signature by 787EA6AE1147EEE56C40B30CDB4639719867C58F
                    Pinned: yes

  ostree://fedora:fedora/rawhide/x86_64/silverblue
                   Version: Rawhide.20210514.n.0 (2021-05-14T06:04:28Z)
                    Commit: 49fa46896e4ac009dc476f4149eb1ce526acd6fe40a54020391ccfe4de8d8b4f
              GPGSignature: Valid signature by 787EA6AE1147EEE56C40B30CDB4639719867C58F
                    Pinned: yes

Rawhide.20210513.n.0 last known good
Rawhide.20210514.n.0 first known bad

For Silverblue 34

ostree://fedora:fedora/34/x86_64/silverblue
                   Version: 34.20210513.0 (2021-05-13T00:46:10Z)
                    Commit: 0a791a0478306d9462880703af5c235b8142371e09e9ec079e04fb29845748c6
              GPGSignature: Valid signature by 8C5BA6990BDB26E19F2A1A801161AE6945719A39

  ostree://fedora:fedora/34/x86_64/silverblue
                   Version: 34.20210514.0 (2021-05-14T17:29:31Z)
                    Commit: 3d7ee56bc58dd5fd534e6b1966c90e52a1f4f5651d967fadd0f79c385af6c149
              GPGSignature: Valid signature by 8C5BA6990BDB26E19F2A1A801161AE6945719A39
                    Pinned: yes



34.20210513.0 last known good
34.20210514.0 first known bad

Looks like the radeon driver doesn't handle modifiers.

Also testing with Fedora 34 Workstation.

GOLD release is working fine.

Same problem once updated to latest

rpm -qa | egrep -i "gnome-session|mutter"
gnome-session-40.1.1-1.fc34.x86_64
mutter-40.1-1.fc34.x86_64
gnome-session-xsession-40.1.1-1.fc34.x86_64
gnome-session-wayland-session-40.1.1-1.fc34.x86_64
gdm-40.0-1.fc34.x86_64

00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] (pro
g-if 00 [VGA controller])
	Subsystem: Gigabyte Technology Co., Ltd Device d000
	Flags: bus master, fast devsel, latency 0, IRQ 49, IOMMU group 0
	Memory at c0000000 (64-bit, prefetchable) [size=256M]
	Memory at d0000000 (64-bit, prefetchable) [size=8M]
	I/O ports at f000 [size=256]
	Memory at feb00000 (32-bit, non-prefetchable) [size=256K]
	Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: radeon
	Kernel modules: radeon, amdgpu

(In reply to Jonas Ådahl from comment #3)
> Looks like the radeon driver doesn't handle modifiers.

Thank you very much for your hints!  GDM started OK with amdgpu driver.

I switched over to use amdgpu driver by using below kernel parameters:
$ cat /proc/cmdline 
BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.11.21-300.fc34.x86_64 root=UUID=bda68cec-a76d-4e6a-be52-fefcff9f76a6 ro rootflags=subvol=root amdgpu.dc=0 radeon.cik_support=0 radeon.si_support=0 amdgpu.cik_support=1

$ sudo lspci -v
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] (prog-if 00 [VGA cont
roller])
	Subsystem: Gigabyte Technology Co., Ltd Device d000
	Flags: bus master, fast devsel, latency 0, IRQ 48, IOMMU group 0
	Memory at c0000000 (64-bit, prefetchable) [size=256M]
	Memory at d0000000 (64-bit, prefetchable) [size=8M]
	I/O ports at f000 [size=256]
	Memory at feb00000 (32-bit, non-prefetchable) [size=256K]
	Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: [48] Vendor Specific Information: Len=08 <?>
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Capabilities: [270] Secondary PCI Express
	Capabilities: [2b0] Address Translation Service (ATS)
	Capabilities: [2c0] Page Request Interface (PRI)
	Capabilities: [2d0] Process Address Space ID (PASID)
	Kernel driver in use: amdgpu
	Kernel modules: radeon, amdgpu

(In reply to Sampson Fung from comment #5)
> (In reply to Jonas Ådahl from comment #3)
> > Looks like the radeon driver doesn't handle modifiers.
> 
> Thank you very much for your hints!  GDM started OK with amdgpu driver.
> 
> I switched over to use amdgpu driver by using below kernel parameters:
> $ cat /proc/cmdline 
> BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.11.21-300.fc34.x86_64
> root=UUID=bda68cec-a76d-4e6a-be52-fefcff9f76a6 ro rootflags=subvol=root
> amdgpu.dc=0 radeon.cik_support=0 radeon.si_support=0 amdgpu.cik_support=1
> 
> $ sudo lspci -v
> 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
> Kaveri [Radeon R7 Graphics] (prog-if 00 [VGA cont
> roller])
> 	Subsystem: Gigabyte Technology Co., Ltd Device d000
> 	Flags: bus master, fast devsel, latency 0, IRQ 48, IOMMU group 0
> 	Memory at c0000000 (64-bit, prefetchable) [size=256M]
> 	Memory at d0000000 (64-bit, prefetchable) [size=8M]
> 	I/O ports at f000 [size=256]
> 	Memory at feb00000 (32-bit, non-prefetchable) [size=256K]
> 	Expansion ROM at 000c0000 [disabled] [size=128K]
> 	Capabilities: [48] Vendor Specific Information: Len=08 <?>
> 	Capabilities: [50] Power Management version 3
> 	Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00
> 	Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
> 	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
> 	Capabilities: [270] Secondary PCI Express
> 	Capabilities: [2b0] Address Translation Service (ATS)
> 	Capabilities: [2c0] Page Request Interface (PRI)
> 	Capabilities: [2d0] Process Address Space ID (PASID)
> 	Kernel driver in use: amdgpu
> 	Kernel modules: radeon, amdgpu

amdgpu avoid this gdm hanging issues for me, but then sound over hdmi is not working .  https://bugzilla.redhat.com/show_bug.cgi?id=1963026

In compare when using KDE

Deployments:
● ostree://fedora:fedora/rawhide/x86_64/kinoite
                   Version: Rawhide.20210522.n.1 (2021-05-22T18:26:11Z)
                BaseCommit: 8a915542daaff13a2d1d6c328f261080de00a5445988157ad62b6e6f329c339e
              GPGSignature: Valid signature by 787EA6AE1147EEE56C40B30CDB4639719867C58F
           LayeredPackages: gnome-tweaks hdparm iotop sg3_utils smartmontools sway terminator


radeon is working fine, hdmi sound also normal.

00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] (prog-if 00 [VGA controller])
        Subsystem: Gigabyte Technology Co., Ltd Device d000
        Flags: bus master, fast devsel, latency 0, IRQ 46, IOMMU group 0
        Memory at f8000000 (64-bit, prefetchable) [size=64M]
        Memory at fc000000 (64-bit, prefetchable) [size=8M]
        I/O ports at f000 [size=256]
        Memory at feb00000 (32-bit, non-prefetchable) [size=256K]
        Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: [48] Vendor Specific Information: Len=08 <?>
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00
        Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
        Capabilities: [270] Secondary PCI Express
        Capabilities: [2b0] Address Translation Service (ATS)
        Capabilities: [2c0] Page Request Interface (PRI)
        Capabilities: [2d0] Process Address Space ID (PASID)
        Kernel driver in use: radeon
        Kernel modules: radeon, amdgpu

since I also run Kaveri and Radeon, this bug is not so nice to hear about !

Since this is related to amdgpu and the blank blinking cursor, then this maybe relevant:

https://bugzilla.redhat.com/show_bug.cgi?id=1964480

(In reply to naderkhalid from comment #9)
> Since this is related to amdgpu and the blank blinking cursor, then this
> maybe relevant:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1964480

In my case, GDM is hanging with radeon but OK with amdgpu.

In 1964480 I'm getting the cursor on blank screen even though I'm using amdgpu kernel driver.
It eventually worked after resetting the amdgpu driver.
I guess then the 2 issues are different even though they share some symptoms.

Try adding

DRIVERS=="radeon", SUBSYSTEM=="drm", TAG+="mutter-device-disable-kms-modifiers"

to /usr/lib/udev/rules.d/61-mutter.rules and remoot.

(In reply to Jonas Ådahl from comment #12)
> Try adding
> 
> DRIVERS=="radeon", SUBSYSTEM=="drm",
> TAG+="mutter-device-disable-kms-modifiers"
> 
> to /usr/lib/udev/rules.d/61-mutter.rules and remoot.

As I am using Silverblue, where /usr is readonly.

How can I have this rule change under Silverblue?

(In reply to Jonas Ådahl from comment #12)
> Try adding
> 
> DRIVERS=="radeon", SUBSYSTEM=="drm",
> TAG+="mutter-device-disable-kms-modifiers"
> 
> to /usr/lib/udev/rules.d/61-mutter.rules and remoot.

Thank you very much!

I am able to login Gnome via GDM after your suggested change!

(In reply to Sampson Fung from comment #13)
> (In reply to Jonas Ådahl from comment #12)
> > Try adding
> > 
> > DRIVERS=="radeon", SUBSYSTEM=="drm",
> > TAG+="mutter-device-disable-kms-modifiers"
> > 
> > to /usr/lib/udev/rules.d/61-mutter.rules and remoot.
> 
> As I am using Silverblue, where /usr is readonly.
> 
> How can I have this rule change under Silverblue?

I find the solution at:
https://www.reddit.com/r/Fedora/comments/ctagcc/how_do_i_edit_udev_rules_on_silverblue/exjqovp?utm_source=share&utm_medium=web2x&context=3

cp /usr/lib/udev/rules.d/61-mutter.rules /etc/udev/rules.d
then edit /etc/udev/rules.d/61-mutter.rules

FEDORA-2021-895047c304 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-895047c304

FEDORA-2021-895047c304 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-895047c304`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-895047c304

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

(In reply to Fedora Update System from comment #17)
> FEDORA-2021-895047c304 has been pushed to the Fedora 34 testing repository.
> Soon you'll be able to install the update with the following command:
> `sudo dnf upgrade --enablerepo=updates-testing
> --advisory=FEDORA-2021-895047c304`
> You can provide feedback for this update here:
> https://bodhi.fedoraproject.org/updates/FEDORA-2021-895047c304
> 
> See also https://fedoraproject.org/wiki/QA:Updates_Testing for more
> information on how to test updates.

Do not work for me.

(In reply to Sampson Fung from comment #18)
> (In reply to Fedora Update System from comment #17)
> > FEDORA-2021-895047c304 has been pushed to the Fedora 34 testing repository.
> > Soon you'll be able to install the update with the following command:
> > `sudo dnf upgrade --enablerepo=updates-testing
> > --advisory=FEDORA-2021-895047c304`
> > You can provide feedback for this update here:
> > https://bodhi.fedoraproject.org/updates/FEDORA-2021-895047c304
> > 
> > See also https://fedoraproject.org/wiki/QA:Updates_Testing for more
> > information on how to test updates.
> 
> Do not work for me.

Did you reboot after? What does 'udevadm info /dev/dri/card0' say? The fix is identical to what you verified works in https://bugzilla.redhat.com/show_bug.cgi?id=1960937#c14.

(In reply to Jonas Ådahl from comment #19)
> (In reply to Sampson Fung from comment #18)
> > (In reply to Fedora Update System from comment #17)
> > > FEDORA-2021-895047c304 has been pushed to the Fedora 34 testing repository.
> > > Soon you'll be able to install the update with the following command:
> > > `sudo dnf upgrade --enablerepo=updates-testing
> > > --advisory=FEDORA-2021-895047c304`
> > > You can provide feedback for this update here:
> > > https://bodhi.fedoraproject.org/updates/FEDORA-2021-895047c304
> > > 
> > > See also https://fedoraproject.org/wiki/QA:Updates_Testing for more
> > > information on how to test updates.
> > 
> > Do not work for me.
> 
> Did you reboot after? What does 'udevadm info /dev/dri/card0' say? The fix
> is identical to what you verified works in
> https://bugzilla.redhat.com/show_bug.cgi?id=1960937#c14.

I am sorry - my previous test on the update has errors on undoing your suggested changes.  I only comment out the "radeon" line, but not removing the custom rule file.

This time, it works

1.  Remove /etc/udev/rules.d/61-mutters.rules # to remove any manually overrides

2.  Install the update by rpm-ostree override, reboot.

3.  sudo udevadm info /dev/dri/card0
P: /devices/pci0000:00/0000:00:01.0/drm/card0
N: dri/card0
L: 0
S: dri/by-path/pci-0000:00:01.0-card
E: DEVPATH=/devices/pci0000:00/0000:00:01.0/drm/card0
E: DEVNAME=/dev/dri/card0
E: DEVTYPE=drm_minor
E: MAJOR=226
E: MINOR=0
E: SUBSYSTEM=drm
E: USEC_INITIALIZED=7486543
E: ID_PATH=pci-0000:00:01.0
E: ID_PATH_TAG=pci-0000_00_01_0
E: ID_FOR_SEAT=drm-pci-0000_00_01_0
E: DEVLINKS=/dev/dri/by-path/pci-0000:00:01.0-card
E: TAGS=:mutter-device-disable-kms-modifiers:master-of-seat:uaccess:seat:
E: CURRENT_TAGS=:mutter-device-disable-kms-modifiers:master-of-seat:uaccess:seat:

I am sorry for the confusion caused.

Thank you very much for your help!

Thanks for testing again!

FEDORA-2021-895047c304 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.