cosmic-comp[2182]: Unable to set adaptive VRR state

[Calleh12]

Hi,

I recently updated and havent rebooted in a while. Now I cannot get to the greeter as it is stuck in an error loop. I believe it is due to cosmic greeter as looking into journalctl logs I can see error messages from it. The logs are spammed with
pop-os cosmic-comp[2182]: Unable to set adaptive VRR state: The underlying drm surface encountered an error: The DrmDevice is missing a required property 'VRR_ENABLED' for handle (42)

AS it is spammed I truncated that part. I'm currently in recovery mode.

logs.txt

Any help is appreciated!

[gabriele2000]

Hi,

I recently updated and havent rebooted in a while. Now I cannot get to the greeter as it is stuck in an error loop. I believe it is due to cosmic greeter as looking into journalctl logs I can see error messages from it. The logs are spammed with pop-os cosmic-comp[2182]: Unable to set adaptive VRR state: The underlying drm surface encountered an error: The DrmDevice is missing a required property 'VRR_ENABLED' for handle (42)

AS it is spammed I truncated that part. I'm currently in recovery mode.

logs.txt

Any help is appreciated!

Let me guess.
Mesa 25 and AMD gpu?

Press CTRL+ALT+F2 or F3, or whatever to boot into a TTY.
Insert your username and password.

Run this:
sudo kernelstub -a radeon.si_support=0 amdgpu.si_support=1
then run
sudo update-initramfs -u

[Calleh12]

Thanks for your suggestion. You are correct that I'm using an amd gpu (Radeon HD 8550M) and mesa, although on Mesa 24.0.9-0ubuntu0. I gave it a try anyway, but it didn't work.

I'm no longer so sure its the 'Unable to set adaptive VRR state' after analyzing the journalctl logs closer.

journalctl-error-logs.txt

I'm out of my depth here so I have no clue. But outputs like

pop-os pipewire[1720]: spa.v4l2: Cannot open '/dev/video0': 13, Permission denied
...
pop-os cosmic-comp[2347]: thread 'main' panicked at 'called Result::unwrap() on an Err value: Error::NoDevice(DrmNode { dev: 57984, ty: Render })': src/backend/kms/surface/mod.rs:290
...
pop-os cosmic-comp[2252]: thread 'surface-eDP-1' panicked at 'called Result::unwrap() on an Err value: PoisonError { .. }': /build/cosmic-comp-agwlUy/cosmic-comp-0.1174464732824.04~155f8d2/vendor/smithay/src/desktop/wayland/layer.rs:68

As these outputs are recurring in the logs, I believe it would explain why I'm stuck in a loop while the greeter tries to start.

Is there anything else I could provide or perhaps try to get it working?

[gabriele2000]

Thanks for your suggestion. You are correct that I'm using an amd gpu (Radeon HD 8550M) and mesa, although on Mesa 24.0.9-0ubuntu0. I gave it a try anyway, but it didn't work.

Wait, if you're using Pop_Os I strongly suggest you to update the system, because we're now at mesa 25.0.1.

By the way, mesa two drivers for AMD:

• radeon, the one for older card
• amdgpu, the one for newer cards

What I did was to tell mesa, using the kernel parameter, to use the amdgpu driver.
Let me check... all right, for your GPU you should use radeon
So, log in in a TTY as I described the other day and:

1 - Let's remove previous parameters:
sudo kernelstub -d radeon.si_support=0 amdgpu.si_support=1

2 - Let's add the new parameters:
sudo kernelstub -a radeon.si_support=1 amdgpu.si_support=0

3 - Let's update the boot image:
sudo update-initramfs -u

You can reboot, hopefully everything will work!

---

Now that the really practical part is done, let's analyze the errors that you pointed out!

pop-os pipewire[1720]: spa.v4l2: Cannot open '/dev/video0': 13, Permission denied

All right, so, spa.v4l2 is a webcam, it's telling you that pipewire can't open it.
The reason is simple: cosmic-session starts cosmic-greeter, cosmic-comp and the other elements.
cosmic-greeter, in our case, is the most important one: after you login, everything will be unlocked... permissions, keyrings, your session settings and terminal settings, stuff like that.

pop-os cosmic-comp[2347]: thread 'main' panicked at 'called Result::unwrap() on an Err value: Error::NoDevice(DrmNode { dev: 57984, ty: Render })': src/backend/kms/surface/mod.rs:290
...
pop-os cosmic-comp[2252]: thread 'surface-eDP-1' panicked at 'called Result::unwrap() on an Err value: PoisonError { .. }': /build/cosmic-comp-agwlUy/cosmic-comp-0.1174464732824.04~155f8d2/vendor/smithay/src/desktop/wayland/layer.rs:68

That's exactly what was happening in my dad's PC, a Desktop with an AMD dedicated GPU.
Mesa shat itself and didn't select the correct driver, or the two drivers conflicted.

[Calleh12]

It works! Thanks for your help. 👍

I added the kernel options as you mention and updated Mesa 25.0.1-2pop1174377952924.04~a9ccba8, but I was still not greeted. I added "nomodeset" and now it works. To be sure that nomodeset was actually the necessary option, I removed it and rebooted. Sure enough, I was stuck.

I suppose our discussion is not related to the adaptive vrr state. I'm not entirely sure what to do with the issue now that it is fixed for me.

[gabriele2000]

It works! Thanks for your help. 👍

I added the kernel options as you mention and updated Mesa 25.0.1-2pop1174377952924.04~a9ccba8, but I was still not greeted. I added "nomodeset" and now it works. To be sure that nomodeset was actually the necessary option, I removed it and rebooted. Sure enough, I was stuck.

I suppose our discussion is not related to the adaptive vrr state. I'm not entirely sure what to do with the issue now that it is fixed for me.

That's very weird.
To be clear, nomodeset disables the GPU acceleration, that's not optimal.
Maybe others can help better, or COSMIC can be "fixed" (quotation marks because I don't know if the culprit is COSMIC or Smithay, or MESA)

[Calleh12]

Oh. That explains the sluggish feeling.

I fetched two journalctl logs, one where nomodeset is set, and one without.

journalctl.log
journalctl-nomodeset.log

Hopefully that is useful for some. The permission denied looks a bit wierd to me.

[Calleh12]

I added kisa-mesa ppa and changed the pin-priority (2000) to be able to upgrade mesa packages to 25.0.3. This solved my issue. Meaning I do not have to use nomodeset anymore.

I will add the apt log for those that are curious of what was upgraded.
kisak-upgrade.log

[gabriele2000]

I will add the apt log for those that are curious of what was upgraded. kisak-upgrade.log

Awesome, I'll ping @mmstick so maybe MESA could be rebased to that version, avoiding messing with PPAs

[mmstick]

I'll make a PR for Mesa 25.0.3

[mmstick]

pop-os/mesa#37