search

ublue-os / bazzite

Bazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld.
https://bazzite.gg
Apache License 2.0
3.21k stars 172 forks source link

No more HDR in gamemode today with updated bazzite-deck:stable #1084

Open herbalizer404 opened 2 months ago

herbalizer404 commented 2 months ago

Describe the bug

No more HDR in gamemode today with updated bazzite-deck:stable. It was working fine yesterday night. It is still working on desktop mode. HDR grey out in gamemode

What did you expect to happen?

HDR to be usable in both gamemode and desktop mode.

Output of rpm-ostree status

State: idle
Deployments:
● ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:349ddc3efa844187ca3b7f1ae16c880b00e18aaabf995d876ee6bf36554d22c0
                  Version: 40.20240505.0 (2024-05-05T05:45:58Z)
          LayeredPackages: iftop sunshine

  ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:testing
                   Digest: sha256:4f24a2e6e6dcfb03c1253b5037c9023c4eae38520cad20315e45cea427bb1503
                  Version: 40.20240505.0 (2024-05-05T05:46:27Z)
          LayeredPackages: iftop sunshine

Hardware

full AMD config, AMD 7900 GRE + AMD ryzen 5 7600

Extra information or context

.local/share/Steam/logs/steamui_system.txt:

GAMEMODE: [2024-05-07 01:10:47] Initialized CSystemReportController [2024-05-07 01:10:47] RegisterGamescopeControl: binding gamescope-control: name: 8 bind-version: 3 have-version: 3 want-version: 3 [2024-05-07 01:10:47] CGamescopeController: skipping external display populate workaround [2024-05-07 01:10:47] gamescope feature support: feature: 1 version: 1 flags: 0 [2024-05-07 01:10:47] gamescope feature support: feature: 2 version: 1 flags: 0 [2024-05-07 01:10:47] gamescope feature support: feature: 3 version: 1 flags: 0 [2024-05-07 01:10:47] gamescope feature support: feature: 4 version: 1 flags: 0 [2024-05-07 01:10:47] gamescope feature support: feature: 5 version: 1 flags: 0 [2024-05-07 01:10:47] gamescope feature support: feature: 0 version: 0 flags: 0 [2024-05-07 01:10:47] gamescope: active display changed: FMX - MStar Demo - internal:0 hdr_capable:0 vrr:0 [2024-05-07 01:10:47] Settings profile change: display: FMX-MStar Demo active: 1 [2024-05-07 01:10:47] CGamescopeController: set unified framerate UI enabled: 1 [2024-05-07 01:10:47] CGamescopeController: initalized implementation: linux [2024-05-07 01:10:47] CGamescopeController: mode changed: 60 Hz [2024-05-07 01:10:47] CGamescopeController: set app target framerate: 60 [2024-05-07 01:10:47] CGamescopeController: set app target refresh cycle: 60 - 0x0 [2024-05-07 01:10:47] CGamescopeController: set unified framerate UI enabled: 1 [2024-05-07 01:10:47] CGamescopeController: set framerate limit disabled: 0 [2024-05-07 01:10:47] CGamescopeController: set app target refresh cycle: 60 - 0x0 [2024-05-07 01:10:47] CGamescopeController: set display refresh rate: 60 [2024-05-07 01:10:47] CGamescopeController: set app target refresh cycle: 60 - 0x0 [2024-05-07 01:10:47] CGamescopeController: set use game refresh rate in steam: 1 [2024-05-07 01:10:47] CGamescopeController: set mura correction disabled: 0 [2024-05-07 01:10:47] CGamescopeController: set include steamui in screenshots: 1 [2024-05-07 01:10:50] DeveloperModeChanged: /usr/bin/steamos-polkit-helpers/steamos-devkit-mode --enable: failed [2024-05-07 01:10:50] System details: codename: variant:kinoite version:40 build: bios:2.10 cef_debugging:1 [2024-05-07 01:10:50] System details: codename: variant:kinoite version:40 build: bios:2.10 cef_debugging:1 [2024-05-07 01:10:51] CGamescopeController: YldSetBlurParams: mode:0 radius:0 duration:0 [2024-05-07 01:11:06] CGamescopeController: YldSetBlurParams: mode:0 radius:0 duration:0 [2024-05-07 01:11:06] CGamescopeController: YldSetBlurParams: mode:0 radius:0 duration:0 [2024-05-07 01:11:10] Error: CX11WindowProperty: failed to read window property: GAMESCOPE_COLOR_APP_WANTS_HDR_FEEDBACK [2024-05-07 01:11:10] CGamescopeControllerLinux::YldGetState(): app-wants: 0 [2024-05-07 01:11:13] CGamescopeController: YldSetBlurParams: mode:0 radius:0 duration:0 [2024-05-07 01:11:13] CGamescopeController: YldSetBlurParams: mode:0 radius:0 duration:0

DESKTOP MODE: [2024-05-07 01:11:22] Client version: 1714854927 [2024-05-07 01:11:22] Initialized CSystemDockManagerController: 0 [2024-05-07 01:11:22] Initialized CSystemAudioDeviceController: 0 [2024-05-07 01:11:22] Initialized CSystemDisplayController: 0 [2024-05-07 01:11:22] Allow drive unmount: 0 [2024-05-07 01:11:22] Allow drive adopt: 0 [2024-05-07 01:11:22] Trim supported: 0 - [2024-05-07 01:11:22] RescheduleTrimAll: ignoring request because trim is unsupported [2024-05-07 01:11:22] Initialized CSystemPerfController: 0 [2024-05-07 01:11:22] Initialized CSteamUINetworkController: 1 [2024-05-07 01:11:22] Initialized CSystemReportController [2024-05-07 01:11:22] CGamescopeController: initalized implementation: linux

Saroufim commented 2 months ago

Experiencing the same problem here. I see nothing in the logs that could be meaningful to extract nor did I find a way to work around this.

herbalizer404 commented 2 months ago

@Saroufim I just tried to rebase to bazzite-deck:testing and bazzite-deck:39 without success, also tried to changes steam deck beta and stable channel from gamemode interface without success. It seems like something has been broken in gamemode config files and make hdr unusable.

(full AMD config, AMD 7900 GRE + AMD ryzen 5 7600)

Wiggoggs commented 2 months ago

I'm having the same problem. Can confirm that downgrading to the 4/27 release restored HDR functionality in gamemode: bazzite-rollback-helper rebase bazzite-deck:40-stable-20240427

rebasing to stable once again shows HDR disabled in gamemode.

Also running full AMD: Ryzen 7 7800x3d + Radeon RX 6800 XT

herbalizer404 commented 2 months ago

@Wiggoggs I tried your rollback command, but I couldn't boot at all in gamemode anymore :( I'm back in stable with no hdr, waiting for a fix for now!

herbalizer404 commented 2 months ago

@Wiggoggs This one worked fine for me with HDR: bazzite-rollback-helper rebase bazzite-deck:40-stable-20240502

Wiggoggs commented 2 months ago

@Wiggoggs This one worked fine for me with HDR: bazzite-rollback-helper rebase bazzite-deck:40-stable-20240502

That's weird, because I specifically tried that one after trying the earlier image that worked for me and HDR was not functioning with it either. I'm happy you found an earlier image that works while we wait for a fix!

herbalizer404 commented 2 months ago

@Wiggoggs Thank you, glad we found our own ways to maintain HDR, and yeah really weird that it's working differently with same specific package. Let's pray someone is reading us :)

Saroufim commented 2 months ago

That specific image has no 3D acceleration for me. Proton games complain that DirectX is missing. I'm having to choose between 3D acceleration or HDR.

rekh127 commented 1 month ago

Also having this issue on intel gpu. Like withSaroufim bazzite-deck:40-stable-20240502 does bring back hdr but nukes the gpu

Ihmoda commented 1 month ago

Same issue for me with a 6950xt and 5600x build. Rolled back to 40-stable-20240427.

hivehivemind commented 1 month ago

Can replicate on a RX 7900 XT + 5800X3D - Bazzite 2-240517.

herbalizer404 commented 1 month ago

Has anyone tried more recent builds from récent days to check if there was a fix ?

Wiggoggs commented 1 month ago

Has anyone tried more recent builds from récent days to check if there was a fix ?

@herbalizer404 I've tried every build as they have been released, no fix for me yet. I'll update here if I notice it's fixed

cchulo commented 1 month ago

What version is gamescope on in 240517 vs latest?

Ihmoda commented 1 month ago

What version is gamescope on in 240517 vs latest?

Could be wrong, but I think the issue first appeared after the update to gamescope to 3.14.12 (if the problem is indeed gamescope related). The 240502 build did not have the issue and it appeared in the 240505 stable image first, which I think contained the update from gamescope 3.14.11 to 3.14.12 here https://github.com/ublue-os/bazzite/commit/b79e24dc9cfbb797ff3767bcfc479d13d9fab5a7#diff-f77fa5d44c04bc519c8db585ba3fac541384b9a16ce1b850a27557b39ce3bcdeR5

cchulo commented 1 month ago

@Ihmoda thanks, i took a look, looks like there were some changes done to fix something to do with constraining the cursor to the main surface, it is unclear if that is the source of our issues, I asked them to take a look (hoping someone from the gamescope dev team answers me). There have been at least 5 additional patch updates, up to 3.14.17, how would we go about testing these patches ourselves and see if the issue was resolved with one of these patches?

Ihmoda commented 1 month ago

@Ihmoda thanks, i took a look, looks like there were some changes done to fix something to do with constraining the cursor to the main surface, it is unclear if that is the source of our issues, I asked them to take a look (hoping someone from the gamescope dev team answers me). There have been at least 5 additional patch updates, up to 3.14.17, how would we go about testing these patches ourselves and see if the issue was resolved with one of these patches?

I'm guessing we would need to build a bazzite image ourselves after specifying the latest gamescope version, like was done here.

Looks like the latest stable Bazzite image (240522) only goes up to gamescope v.3.14.16-2 (and yeah, bug still exists there).

Would also be nice if we could build a custom image to confirm that the gamescope upgrade diff is what caused the problem, seems likely but all I can say for sure is that the stable/testing versions that first introduced 3.14.12 include the bug, but it's possible that another commit from the same day introduced the problem.

idk-some-guy commented 1 month ago

Its worth noting that the latest fully updated chimeraOS does indeed run HDR in gamescope-session on my system. Makes me think it may not be a gamescope issue, as theirs is up to date.

KyleGospo commented 1 month ago

Its worth noting that the latest fully updated chimeraOS does indeed run HDR in gamescope-session on my system. Makes me think it may not be a gamescope issue, as theirs is up to date.

image

KyleGospo commented 1 month ago

Looks like the latest stable Bazzite image (240522) only goes up to gamescope v.3.14.16-2 (and yeah, bug still exists there).

Latest stable build is on 3.14.17

Ihmoda commented 1 month ago

Looks like the latest stable Bazzite image (240522) only goes up to gamescope v.3.14.16-2 (and yeah, bug still exists there).

Latest stable build is on 3.14.17

Thanks, problem continues to persist for me in 40-stable-20240524. Is it possible for users to select an older version of gamescope via custom layering?

cchulo commented 1 month ago

Looks like the latest stable Bazzite image (240522) only goes up to gamescope v.3.14.16-2 (and yeah, bug still exists there).

Latest stable build is on 3.14.17

Thanks, problem continues to persist for me in 40-stable-20240524. Is it possible for users to select an older version of gamescope via custom layering?

i think you can do this by creating your own rpm that obsoletes the one in bazzite-deck's base image via layering with rpm-ostree install ./path/to/my/custom/rpm

I can't think of any consequences to this. ~I do wonder though, is there anything in 3.14.x that is crucial for bazzite at this point in time? can we not revert back to 3.13 for the bazzite-deck flavor? 3.14's HDR is broken as a result of this upgrade~

Actually I take that last part back, what version is gamescope-plus based on? is bazzite-deck not using gamescope-plus?

idk-some-guy commented 1 month ago

So I did some testing. I tried to override bazzite gamescope with version 3.13.9, but still no HDR. Here is my rpm package I used, providing it in case someone wanna check i did things right. Command I used was rpm-ostree install --force-replacefiles. PLEASE DONT INSTALL A RANDOM BINARY FROM THE INTERNET UPLOADED BY A RANDOM GUY, make your own, it takes 5 minutes. https://drive.google.com/file/d/1wiu7PhBLiJnnPjgMmh1jxYpMUItP3UnQ/view?usp=sharing

The override itself is definitely working as I originally forgot to chmod 755 gamescope and it had predictable results

It would be interesting to see someone do this the other way. Start at an older build where it works and override just gamescope with the latest version and see if it works, if it does, I'd also like to see the list of "added" and "modified" from rpm-ostree. To see which other packages change.

Adding relevant logs just for reference: gamescope-cmd /usr/bin/gamescope --max-scale 2 --hdr-enabled --prefer-vk-device 1002:744c -e --xwayland-count 2 -O HDMI-A-1,* -R /run/user/1000/gamescope.Gj6YTgI/startup.socket -T /run/user/1000/gamescope.Gj6YTgI/stats.pipe gamescope-stdout

ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
vulkan: selecting physical device 'AMD Radeon RX 7900 XTX (RADV NAVI31)': queue family 1 (general queue family 0)
vulkan: physical device supports DRM format modifiers
wlserver: [backend/headless/backend.c:67] Creating headless backend
wlserver: [libseat] [libseat/backend/seatd.c:64] Could not connect to socket /run/seatd.sock: No such file or directory
wlserver: [libseat] [libseat/libseat.c:76] Backend 'seatd' failed to open seat, skipping
wlserver: [libseat] [libseat/libseat.c:73] Seat opened with backend 'logind'
wlserver: [backend/session/session.c:108] Successfully loaded libseat session
drm: opening DRM node '/dev/dri/card1'
drm: Immediate flips disabled from environment
drm: Connector HDMI-A-2 -> PHL - Philips FTV
drm: [colorimetry]: EDID with colorimetry detected. Using it
drm: [colorimetry]: r 0.677734 0.321289
drm: [colorimetry]: g 0.265625 0.673828
drm: [colorimetry]: b 0.144531 0.047852
drm: [colorimetry]: w 0.312500 0.328125
drm: Connector HDMI-A-2 -> PHL - Philips FTV
drm: [colorimetry]: EDID with colorimetry detected. Using it
drm: [colorimetry]: r 0.677734 0.321289
drm: [colorimetry]: g 0.265625 0.673828
drm: [colorimetry]: b 0.144531 0.047852
drm: [colorimetry]: w 0.312500 0.328125
drm: Connectors:
drm:   HDMI-A-2 (connected)
drm:   DP-2 (disconnected)
drm:   HDMI-A-1 (disconnected)
drm:   DP-1 (disconnected)
drm: selecting connector HDMI-A-2
drm: selecting mode 3840x2160@120Hz
vulkan: supported DRM formats for sampling usage:
vulkan:   AR24 (0x34325241)
vulkan:   XR24 (0x34325258)
vulkan:   AB24 (0x34324241)
vulkan:   XB24 (0x34324258)
vulkan:   RG16 (0x36314752)
vulkan:   NV12 (0x3231564E)
vulkan:   AB4H (0x48344241)
vulkan:   XB4H (0x48344258)
vulkan:   AB48 (0x38344241)
vulkan:   XB48 (0x38344258)
vulkan:   AB30 (0x30334241)
vulkan:   XB30 (0x30334258)
vulkan:   AR30 (0x30335241)
vulkan:   XR30 (0x30335258)
wlserver: Using explicit sync when available
wlserver: Running compositor on wayland display 'gamescope-0'
wlserver: [backend/headless/backend.c:17] Starting headless backend
wlserver: [backend/libinput/backend.c:88] Starting libinput backend
wlserver: [backend/libinput/events.c:69] Adding Power Button [0:1]
wlserver: [backend/libinput/events.c:69] Adding Video Bus [0:6]
wlserver: [backend/libinput/events.c:69] Adding Power Button [0:1]
wlserver: [backend/libinput/events.c:69] Adding Generic USB Audio [2821:6778]
wlserver: [backend/libinput/events.c:69] Adding Sony Interactive Entertainment DualSense Edge Wireless Controller Touchpad [1356:3570]
wlserver: [backend/libinput/events.c:69] Adding Asus WMI hotkeys [0:0]
wlserver: [backend/libinput/events.c:69] Adding Eee PC WMI hotkeys [0:0]
wlserver: [backend/libinput/backend.c:127] libinput successfully initialized
wlserver: Successfully initialized libei for input emulation!
wlserver: [xwayland/server.c:107] Starting Xwayland on :0
wlserver: [xwayland/server.c:107] Starting Xwayland on :1
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86CameraAccessEnable
> Warning:          Could not resolve keysym XF86CameraAccessDisable
> Warning:          Could not resolve keysym XF86CameraAccessToggle
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          > Could not resolve keysym XF86CameraAccessEnable
Warning:          > Could not resolve keysym XF86NextElement
Warning:          > Could not resolve keysym XF86CameraAccessDisable
Warning:          > Could not resolve keysym XF86PreviousElement
Warning:          > Could not resolve keysym XF86CameraAccessToggle
Warning:          Could not resolve keysym XF86AutopilotEngageToggle
> Warning:          Could not resolve keysym XF86MarkWaypoint
> > Warning:          Warning:          Could not resolve keysym XF86NextElement
Could not resolve keysym XF86Sos
> > Warning:          Warning:          Could not resolve keysym XF86PreviousElement
Could not resolve keysym XF86NavChart
> > Warning:          Warning:          Could not resolve keysym XF86AutopilotEngageToggle
Could not resolve keysym XF86FishingChart
> > Warning:          Warning:          Could not resolve keysym XF86MarkWaypoint
Could not resolve keysym XF86SingleRangeRadar
> > Warning:          Warning:          Could not resolve keysym XF86Sos
Could not resolve keysym XF86DualRangeRadar
> Warning:          Could not resolve keysym XF86NavChart
> > Warning:          Warning:          Could not resolve keysym XF86RadarOverlay
Could not resolve keysym XF86FishingChart
> > Warning:          Warning:          Could not resolve keysym XF86TraditionalSonar
Could not resolve keysym XF86SingleRangeRadar
> > Warning:          Warning:          Could not resolve keysym XF86ClearvuSonar
Could not resolve keysym XF86DualRangeRadar
> > Warning:          Warning:          Could not resolve keysym XF86SidevuSonar
Could not resolve keysym XF86RadarOverlay
> > Warning:          Warning:          Could not resolve keysym XF86NavInfo
Could not resolve keysym XF86TraditionalSonar
> Warning:          Could not resolve keysym XF86ClearvuSonar
> Warning:          Could not resolve keysym XF86SidevuSonar
> Warning:          Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
Errors from xkbcomp are not fatal to the X server
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x56009629e3c0 (res 0x5600963f8470)
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x560096280340 (res 0x5600963f9670)
wlserver: [xwayland/server.c:272] Xserver is ready
wlserver: [xwayland/server.c:272] Xserver is ready
pipewire: stream state changed: connecting
pipewire: stream state changed: paused
pipewire: stream available on node ID: 42
xwm: Embedded, no cursor set. Using left_ptr by default.
xwm: Embedded, no cursor set. Using left_ptr by default.
vblank: Using timerfd.
josh edid: Wrote new edid to: /home/idksomeguy/.config/gamescope/edid.bin
wlserver: Updating mode for xwayland server #0: 3840x2160@120
pipewire: renegotiating stream params (size: 3840x2160)
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x560096207ce0 (res 0x5600963bb150)
cchulo commented 1 month ago

So I did some testing. I tried to override bazzite gamescope with version 3.13.9, but still no HDR. Here is my rpm package I used, providing it in case someone wanna check i did things right. Command I used was rpm-ostree install --force-replacefiles. PLEASE DONT INSTALL A RANDOM BINARY FROM THE INTERNET UPLOADED BY A RANDOM GUY, make your own, it takes 5 minutes. https://drive.google.com/file/d/1wiu7PhBLiJnnPjgMmh1jxYpMUItP3UnQ/view?usp=sharing

The override itself is definitely working as I originally forgot to chmod 755 gamescope and it had predictable results

It would be interesting to see someone do this the other way. Start at an older build where it works and override just gamescope with the latest version and see if it works, if it does, I'd also like to see the list of "added" and "modified" from rpm-ostree. To see which other packages change

thanks for testing. So to narrow it down it shouldn't be too difficult, going back to the image that someone earlier commented that worked is from 4/27, my best educated guess is its from this commit: https://github.com/ublue-os/bazzite/commit/b4297c9ad87305dc2cbcbdfce1279afbd9877a8b Its a bit difficult since the published image does not seem to include git tag from what it was built from, or at least its not obvious to me. Looking through this commit and I can see that the gamescope version was the jupiter that the steam deck uses: https://github.com/ublue-os/bazzite/blob/b4297c9ad87305dc2cbcbdfce1279afbd9877a8b/spec_files/gamescope/gamescope.spec#L84

its difficult to say what's changed, there's 2080 commits: https://github.com/ValveSoftware/gamescope/tree/jupiter-3.6

@KyleGospo why was it updated from the gamescope version that steam deck is on for the bazzite-deck image?

KyleGospo commented 1 month ago

We match SteamOS's main branch at this time. I can also confirm HDR works fine on my LCD when docked, and OLED at all times.

cchulo commented 1 month ago

this may be a problem on non-steam deck hardware then, my HTPC is a HX99G with RX 6600M GPU. I recall while digging through gamescope-session code there was a check for enabling HDR based on whether or not the codename "galileo" was present somewhere on the hardware. I don't remember if this was evlav gamescope-session or chimera-os', i'll dig around some more

stanier commented 1 month ago

I can also confirm HDR works fine on my LCD when docked, and OLED at all times.

this may be a problem on non-steam deck hardware then,

It's not working on my 512GB LCD Deck, updated (through ujust) within last 24 hours, so this is not exclusive to non-Deck devices.

cchulo commented 1 month ago

I can also confirm HDR works fine on my LCD when docked, and OLED at all times.

this may be a problem on non-steam deck hardware then,

It's not working on my 512GB LCD Deck, updated (through ujust) within last 24 hours, so this is not exclusive to non-Deck devices.

ah i see, sorry for jumping the gun in making the wrong assumption, I guess at this point I have no idea what's wrong nor have an idea of where to go look, i'll keep poking around, when i find something I will update ya'll here, would be great if gamescope devs could comment as well on the other issue.

Ihmoda commented 1 month ago

So I did some testing. I tried to override bazzite gamescope with version 3.13.9, but still no HDR. Here is my rpm package I used, providing it in case someone wanna check i did things right. Command I used was rpm-ostree install --force-replacefiles. PLEASE DONT INSTALL A RANDOM BINARY FROM THE INTERNET UPLOADED BY A RANDOM GUY, make your own, it takes 5 minutes. https://drive.google.com/file/d/1wiu7PhBLiJnnPjgMmh1jxYpMUItP3UnQ/view?usp=sharing

The override itself is definitely working as I originally forgot to chmod 755 gamescope and it had predictable results

It would be interesting to see someone do this the other way. Start at an older build where it works and override just gamescope with the latest version and see if it works, if it does, I'd also like to see the list of "added" and "modified" from rpm-ostree. To see which other packages change.

Adding relevant logs just for reference: gamescope-cmd /usr/bin/gamescope --max-scale 2 --hdr-enabled --prefer-vk-device 1002:744c -e --xwayland-count 2 -O HDMI-A-1,* -R /run/user/1000/gamescope.Gj6YTgI/startup.socket -T /run/user/1000/gamescope.Gj6YTgI/stats.pipe gamescope-stdout

ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
vulkan: selecting physical device 'AMD Radeon RX 7900 XTX (RADV NAVI31)': queue family 1 (general queue family 0)
vulkan: physical device supports DRM format modifiers
wlserver: [backend/headless/backend.c:67] Creating headless backend
wlserver: [libseat] [libseat/backend/seatd.c:64] Could not connect to socket /run/seatd.sock: No such file or directory
wlserver: [libseat] [libseat/libseat.c:76] Backend 'seatd' failed to open seat, skipping
wlserver: [libseat] [libseat/libseat.c:73] Seat opened with backend 'logind'
wlserver: [backend/session/session.c:108] Successfully loaded libseat session
drm: opening DRM node '/dev/dri/card1'
drm: Immediate flips disabled from environment
drm: Connector HDMI-A-2 -> PHL - Philips FTV
drm: [colorimetry]: EDID with colorimetry detected. Using it
drm: [colorimetry]: r 0.677734 0.321289
drm: [colorimetry]: g 0.265625 0.673828
drm: [colorimetry]: b 0.144531 0.047852
drm: [colorimetry]: w 0.312500 0.328125
drm: Connector HDMI-A-2 -> PHL - Philips FTV
drm: [colorimetry]: EDID with colorimetry detected. Using it
drm: [colorimetry]: r 0.677734 0.321289
drm: [colorimetry]: g 0.265625 0.673828
drm: [colorimetry]: b 0.144531 0.047852
drm: [colorimetry]: w 0.312500 0.328125
drm: Connectors:
drm:   HDMI-A-2 (connected)
drm:   DP-2 (disconnected)
drm:   HDMI-A-1 (disconnected)
drm:   DP-1 (disconnected)
drm: selecting connector HDMI-A-2
drm: selecting mode 3840x2160@120Hz
vulkan: supported DRM formats for sampling usage:
vulkan:   AR24 (0x34325241)
vulkan:   XR24 (0x34325258)
vulkan:   AB24 (0x34324241)
vulkan:   XB24 (0x34324258)
vulkan:   RG16 (0x36314752)
vulkan:   NV12 (0x3231564E)
vulkan:   AB4H (0x48344241)
vulkan:   XB4H (0x48344258)
vulkan:   AB48 (0x38344241)
vulkan:   XB48 (0x38344258)
vulkan:   AB30 (0x30334241)
vulkan:   XB30 (0x30334258)
vulkan:   AR30 (0x30335241)
vulkan:   XR30 (0x30335258)
wlserver: Using explicit sync when available
wlserver: Running compositor on wayland display 'gamescope-0'
wlserver: [backend/headless/backend.c:17] Starting headless backend
wlserver: [backend/libinput/backend.c:88] Starting libinput backend
wlserver: [backend/libinput/events.c:69] Adding Power Button [0:1]
wlserver: [backend/libinput/events.c:69] Adding Video Bus [0:6]
wlserver: [backend/libinput/events.c:69] Adding Power Button [0:1]
wlserver: [backend/libinput/events.c:69] Adding Generic USB Audio [2821:6778]
wlserver: [backend/libinput/events.c:69] Adding Sony Interactive Entertainment DualSense Edge Wireless Controller Touchpad [1356:3570]
wlserver: [backend/libinput/events.c:69] Adding Asus WMI hotkeys [0:0]
wlserver: [backend/libinput/events.c:69] Adding Eee PC WMI hotkeys [0:0]
wlserver: [backend/libinput/backend.c:127] libinput successfully initialized
wlserver: Successfully initialized libei for input emulation!
wlserver: [xwayland/server.c:107] Starting Xwayland on :0
wlserver: [xwayland/server.c:107] Starting Xwayland on :1
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86CameraAccessEnable
> Warning:          Could not resolve keysym XF86CameraAccessDisable
> Warning:          Could not resolve keysym XF86CameraAccessToggle
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          > Could not resolve keysym XF86CameraAccessEnable
Warning:          > Could not resolve keysym XF86NextElement
Warning:          > Could not resolve keysym XF86CameraAccessDisable
Warning:          > Could not resolve keysym XF86PreviousElement
Warning:          > Could not resolve keysym XF86CameraAccessToggle
Warning:          Could not resolve keysym XF86AutopilotEngageToggle
> Warning:          Could not resolve keysym XF86MarkWaypoint
> > Warning:          Warning:          Could not resolve keysym XF86NextElement
Could not resolve keysym XF86Sos
> > Warning:          Warning:          Could not resolve keysym XF86PreviousElement
Could not resolve keysym XF86NavChart
> > Warning:          Warning:          Could not resolve keysym XF86AutopilotEngageToggle
Could not resolve keysym XF86FishingChart
> > Warning:          Warning:          Could not resolve keysym XF86MarkWaypoint
Could not resolve keysym XF86SingleRangeRadar
> > Warning:          Warning:          Could not resolve keysym XF86Sos
Could not resolve keysym XF86DualRangeRadar
> Warning:          Could not resolve keysym XF86NavChart
> > Warning:          Warning:          Could not resolve keysym XF86RadarOverlay
Could not resolve keysym XF86FishingChart
> > Warning:          Warning:          Could not resolve keysym XF86TraditionalSonar
Could not resolve keysym XF86SingleRangeRadar
> > Warning:          Warning:          Could not resolve keysym XF86ClearvuSonar
Could not resolve keysym XF86DualRangeRadar
> > Warning:          Warning:          Could not resolve keysym XF86SidevuSonar
Could not resolve keysym XF86RadarOverlay
> > Warning:          Warning:          Could not resolve keysym XF86NavInfo
Could not resolve keysym XF86TraditionalSonar
> Warning:          Could not resolve keysym XF86ClearvuSonar
> Warning:          Could not resolve keysym XF86SidevuSonar
> Warning:          Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
Errors from xkbcomp are not fatal to the X server
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x56009629e3c0 (res 0x5600963f8470)
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x560096280340 (res 0x5600963f9670)
wlserver: [xwayland/server.c:272] Xserver is ready
wlserver: [xwayland/server.c:272] Xserver is ready
pipewire: stream state changed: connecting
pipewire: stream state changed: paused
pipewire: stream available on node ID: 42
xwm: Embedded, no cursor set. Using left_ptr by default.
xwm: Embedded, no cursor set. Using left_ptr by default.
vblank: Using timerfd.
josh edid: Wrote new edid to: /home/idksomeguy/.config/gamescope/edid.bin
wlserver: Updating mode for xwayland server #0: 3840x2160@120
pipewire: renegotiating stream params (size: 3840x2160)
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x560096207ce0 (res 0x5600963bb150)

I updated today's stable (2024-05-28) and rolled back gamescope to 3.13.9 (rpm-ostree install --force-replacefiles <path_to_older_gamescope_rpm>) and that fixed the issue for me. On 6950xt so likely works for all RDNA 2 cards.

Think this confirms that the issue is gamescope related.

idk-some-guy commented 1 month ago

Interesting it didn't work for me, did you use my rpm?

Ihmoda commented 1 month ago

d you use my

Foolishly I did use your rpm (if you are a malicious actor, bravo, because your warning made me trust it more).

It did fix HDR for me in gamemode on my 6950xt, however the gamescope version seemed to cause another issue where default resolution was getting detected as 720p on my monitor so ended up rolling back to the 0427 image once again.

For my edification, can you explain how you created the RPM for gamescope? I tried to do it using the .spec file for gamescope in the bazzite repo from an earlier commit c60e4c1 (gamescope 3.14.11 is the last version that works with HDR in game mode I think) but was getting build errors. Was trying to follow the info presented here: https://www.redhat.com/sysadmin/create-rpm-package.

idk-some-guy commented 1 month ago

d you use my

Foolishly I did use your rpm (if you are a malicious actor, bravo, because your warning made me trust it more).

It did fix HDR for me in gamemode on my 6950xt, however the gamescope version seemed to cause another issue where default resolution was getting detected as 720p on my monitor so ended up rolling back to the 0427 image once again.

For my edification, can you explain how you created the RPM for gamescope? I tried to do it using the .spec file for gamescope in the bazzite repo from an earlier commit c60e4c1 (gamescope 3.14.11 is the last version that works with HDR in game mode I think) but was getting build errors. Was trying to follow the info presented here: https://www.redhat.com/sysadmin/create-rpm-package.

Okay, so for some reason my hdr just doesn't work anymore then even tho it did before. Fun. That's why I asked if you used mine.

You can get bigger than 720p by putting an env in /etc/environment. Can not for the life of me remember what it was tho, something like STEAM_RESTRICT_720P=0. Adding --bypass-steam-resolution to gamescopecmd might also work instead if you like me can no longer find that damn env.

I built it from the ground up. Extracted a known good Gamescope rpm from package repo, removed all the extra files, like docs and so on so I was left with just the gamescope bin, the vk layer, the json for the vk layer.

Followed this in a toolbox with additional steps like chmodding the binary to make it executable

https://www.reddit.com/r/Fedora/s/Qkp3gQSDez

Once I had the rpm it auto detected a need for openvrapi which Bazzite doesn't ship so I used rpmrebuild to remove it, and here we are.

idk-some-guy commented 1 month ago

just fyi, my fork of chimeraos unstable, according to this: https://github.com/idk-some-guy/idk-chimeraos/blob/master/pkgs/gamescope-plus/PKGBUILD is using gamescope from their repo which is only 1 commit behind valve. ergo up to date. and HDR works. even tho it shouldnt. would it be worth maybe to reopen the possibility that its not gamescope itself? or that chimeraos team actually found a patch in one of their 19 commits?

cchulo commented 1 month ago

to everyone in this thread with the issue, are you using HDMI? can you try displayport if so on the image with the problem? my HX99G lacks displayports, and usb 4 isn't working. I have a suspicion this may be an issue with HDMI

Wiggoggs commented 1 month ago

to everyone in this thread with the issue, are you using HDMI? can you try displayport if so on the image with the problem? my H99GX lacks displayports, and usb 4 isn't working. I have a suspicion this may be an issue with HDMI

@cchulo I've been using displayport from the start, unfortunately, so I don't think it's an HDMI issue

idk-some-guy commented 1 month ago

Same issue with a USB4 DPALT -> HDMI cable

yoyossef commented 1 month ago

Same issue with a DP -> HDMI 2.1 cable

herbalizer404 commented 1 month ago

This issue is the most commented of every issues, open and closed ones from repo. Please guys from bazzite, give us a fix!

anyoneyun commented 1 month ago

Can reproduce with latest stable, using 7800XT

Ihmoda commented 1 month ago

Believe this PR that was merged yesterday fixes the issue: https://github.com/ublue-os/bazzite/pull/1200 (thanks devs!). Last stable is from 5/31 so will need to wait for a new stable build to test out.

KyleGospo commented 1 month ago

Believe this PR that was merged yesterday fixes the issue: https://github.com/ublue-os/bazzite/pull/1200 (thanks devs!). Last stable is from 5/31 so will need to wait for a new stable build to test out.

This is building now along with a fix for DRM leasing (VR headsets) under GNOME Wayland (but since we're in the HDR issue I doubt anyone here cares 😂)

I will push new ISOs today as well

Ihmoda commented 1 month ago

Believe this PR that was merged yesterday fixes the issue: #1200 (thanks devs!). Last stable is from 5/31 so will need to wait for a new stable build to test out.

This is building now along with a fix for DRM leasing (VR headsets) under GNOME Wayland (but since we're in the HDR issue I doubt anyone here cares 😂)

I will push new ISOs today as well

Thanks, confirmed working for me now on 40-stable-20240603 with an AMD RDNA 2 GPU. Many thanks!

cchulo commented 1 month ago

@KyleGospo the issue still persists for me, option is still greyed out after updating, confirmed to be on 40-stable-20240603

rekh127 commented 1 month ago

I updated a few minutes ago and HDR is still not working for me. HDR option states not available on this display

KyleGospo commented 1 month ago

If you have previously layered an older build of gamescope please ensure that it is no longer layered.

Same is true for any config changes, please remove those.

cchulo commented 1 month ago

i reimaged my htpc using the latest bazzite-deck-stable iso yesterday, and can confirm that no other rpms were overlayed. I'm going to try a few things to see if i can replicate Ihmoda's success. @Ihmoda do you have the latest stable release for gamescope? no rpms overlayed?

Ihmoda commented 1 month ago

On the 06/03 stable and using a 6950xt. Output of rpm-ostree status:

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:e42275027f210acb8c2c615c3fa49be4a6217358fb789c9e2f8f21dee10a91d2
                  Version: 40.20240603.0 (2024-06-03T18:18:53Z)
          LayeredPackages: sunshine

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:40-stable-20240427
                   Digest: sha256:67bb1f9dd52a420f080fd67e71a60bb6f732c12bacab7d27476dfbdca601c757
                  Version: 40.20240427.0 (2024-04-27T22:36:59Z)
          LayeredPackages: sunshine
anyoneyun commented 1 month ago

I can confirm hdr is now working for me on latest stable build 7800xt over hdmi

FrankUrbainsky commented 1 month ago

Can also confirm HDR now working with a 7900xt over hdmi

Wiggoggs commented 1 month ago

I can confirm that it's back to working on my hardware: Ryzen 7 7800x3d + Radeon RX 6800 XT

Interestingly, it was not working at first when I rebooted after updating, but rebooting an additional time fixed the problem and there have been no issues since