Some hardware stuck at 15W TDP in gamescope-session

HikariKnight · 2024-03-15T15:52:03.717Z

Writing this here so we have a place to track this. @d3Xt3r has this issue and we confirmed earlier today it is not related to https://github.com/ublue-os/bazzite/issues/320 `ENABLE_HARDWARE_CONTROL_ON_NON_DECK_HARDWARE` is set to 0 so `/usr/bin/steamos-polkit-helpers/steamos-priv-write` is disabled, yet the TDP gets set to 15W in gamescope. They are currently using the dirty workaround from the #320 issue until we can track down the cause. @d3Xt3r if you could provide `rpm-ostree status`, `rpm-ostree kargs` and also the hardware of the affected system it might help to get us started on looking into this. For now, if anyone stumbles upon this issue, use the workaround provided here: https://github.com/ublue-os/bazzite/issues/320#issuecomment-1725206390

H

HikariKnightOP•3/15/24, 8:05 PM

@Kyle Gospo any thoughts about how this could happen, since this is the 2nd person it has happened to now? since i thought this was only done through

steamos-priv-write

steamos-priv-write

steamos-priv-write

steamos-priv-write

might need help tracking this down when youre back from scale and d3xt3r provides us with the details i asked for

and if we dont find it out, i can make an ujust command for the dirty workaround i originally made as it should not impact performance, its just annoying.

K

Kyle Gospo•3/15/24, 8:08 PM

No clue, should only be priv write

K

Kyle Gospo•3/15/24, 8:08 PM

Nothing else has root access to limit it

K

Kyle Gospo•3/15/24, 8:08 PM

Unless explicitly installed

K

Kyle Gospo•3/15/24, 8:08 PM

simpledeckyTDP for instance will use ryzenadj

K

Kyle Gospo•3/15/24, 8:08 PM

So if that's installed, there's your TDP limit

H

HikariKnightOP•3/15/24, 8:14 PM

think they said they only installed lact but didnt do anything in it.

H

HikariKnightOP•3/15/24, 8:15 PM

at least there is the brute force workaround i made back in the beginning

H

HikariKnightOP•3/15/24, 8:15 PM

i hate it

D

d3Xt3r•3/16/24, 6:51 AM

Okay, some good news and bad news. I decided to wipe my drive and reinstall my bazzite-deck from scratch - fresh offline ISO, installed and updated to latest stable. Didn't install LACT, Decky or anything of that sort. Ran
cat /sys/class/hwmon/hwmon0/power1_cap_default
cat /sys/class/hwmon/hwmon0/power1_cap_default
cat /sys/class/hwmon/hwmon0/power1_cap_default
cat /sys/class/hwmon/hwmon0/power1_cap_default and it now shows
212000000
212000000
212000000
212000000!
/sys/class/hwmon/hwmon0/power1_cap_max
/sys/class/hwmon/hwmon0/power1_cap_max
/sys/class/hwmon/hwmon0/power1_cap_max
/sys/class/hwmon/hwmon0/power1_cap_maxalso shows
280000000
280000000
280000000
280000000, which matches with what Adrenalin in Windows showed. So that's all well and good.

Unfortunately, it didn't really fix the my slow game performance. I tried maxing out the game settings to see how far I can push the GPU but it seems to max out around 526MHz and 30W, and this is happening in all games (both native ones like Last Epoch and Proton ones like Diablo 4). This is happening in both desktop and game mode btw. Also tried running furmark and I was only getting 5FPS and again, the power did not exceed 30W.

I'm not sure where it's getting that 30W limit from. Is
/sys/class/hwmon/hwmon0/power1_cap_max
/sys/class/hwmon/hwmon0/power1_cap_max
/sys/class/hwmon/hwmon0/power1_cap_max
/sys/class/hwmon/hwmon0/power1_cap_max the right path? I could run LACT to double-check but don't want to risk changing any values. What do you guys think?

Edit: So I suspect that 30W thing is just a MangoHud reporting glitch,

/sys/class/hwmon/hwmon0/power1_cap_default

/sys/class/hwmon/hwmon0/power1_cap_default

/sys/class/hwmon/hwmon0/power1_cap_default

/sys/class/hwmon/hwmon0/power1_cap_default still reports

15000000

15000000

15000000

15000000 so ignore the above.

D

d3Xt3r•3/16/24, 7:03 AM

K

Kyle Gospo•3/16/24, 7:03 AM

https://github.com/ublue-os/bazzite/blob/main/spec_files%2Fjupiter-hw-support%2Fpriv-write.patch

GitHub

bazzite/spec_files/jupiter-hw-support/priv-write.patch at main · ub...

Bazzite is an OCI image that serves as an alternative operating system for the Steam Deck, and a ready-to-game SteamOS-like for desktop computers, living room home theater PCs, and numerous other h...

K

Kyle Gospo•3/16/24, 7:04 AM

This is the patch that should prevent this from doing anything

K

Kyle Gospo•3/16/24, 7:05 AM

Feel free to install LACT, that's easily disabled

K

Kyle Gospo•3/16/24, 7:05 AM

Curious what you find

K

Kyle Gospo•3/16/24, 7:14 AM

echo "commit: Skipped - see /etc/default/steam-hardware-control" | systemd-cat -t p-steamos-priv-write -p warning

K

Kyle Gospo•3/16/24, 7:14 AM

It also writes logs

K

Kyle Gospo•3/16/24, 7:14 AM

So it's worth checking that

K

Kyle Gospo•3/16/24, 8:00 AM

https://gitlab.com/evlaV/jupiter-hw-support/-/blob/master/usr/bin/steamos-polkit-helpers/steamos-priv-write?ref_type=heads

GitLab

usr/bin/steamos-polkit-helpers/steamos-priv-write · master · evlaV ...

GitLab.com

D

d3Xt3r•3/16/24, 11:52 AM

journactl has the following logs:

p-steamos-priv-write[5795]: checking: /sys/class/hwmon/hwmon0/power2_cap
p-steamos-priv-write[5798]: commit: Skipped - see /etc/default/steam-hardware-control
p-steamos-priv-write[5801]: decline: 15000000 -> /sys/class/hwmon/hwmon0/power2_cap

p-steamos-priv-write[5795]: checking: /sys/class/hwmon/hwmon0/power2_cap
p-steamos-priv-write[5798]: commit: Skipped - see /etc/default/steam-hardware-control
p-steamos-priv-write[5801]: decline: 15000000 -> /sys/class/hwmon/hwmon0/power2_cap

p-steamos-priv-write[5795]: checking: /sys/class/hwmon/hwmon0/power2_cap
p-steamos-priv-write[5798]: commit: Skipped - see /etc/default/steam-hardware-control
p-steamos-priv-write[5801]: decline: 15000000 -> /sys/class/hwmon/hwmon0/power2_cap

p-steamos-priv-write[5795]: checking: /sys/class/hwmon/hwmon0/power2_cap
p-steamos-priv-write[5798]: commit: Skipped - see /etc/default/steam-hardware-control
p-steamos-priv-write[5801]: decline: 15000000 -> /sys/class/hwmon/hwmon0/power2_cap

Which is interesting because I don't have a any power2* files in that path.

I also installed LACT and it is showing 15W, and it looks like this is being set in

/sys/class/hwmon/hwmon0/power1_cap

/sys/class/hwmon/hwmon0/power1_cap

/sys/class/hwmon/hwmon0/power1_cap

/sys/class/hwmon/hwmon0/power1_cap.

Edit: Now that I look at the log again, maybe that decline is not working because it's writing to a non-existent file?

---
Btw @HikariKnight:

rpm-ostree kargs :

rhgb quiet root=UUID=5125c6a7-d169-4e52-9a0c-8e010e37cdeb rootflags=subvol=root rw ostree=/ostree/boot.0/default/200d6b192b97a3b6e644cd8b288f642db8fc254676a0b2c9811df40aba3d5a44/0 gpu_sched.sched_policy=0

rhgb quiet root=UUID=5125c6a7-d169-4e52-9a0c-8e010e37cdeb rootflags=subvol=root rw ostree=/ostree/boot.0/default/200d6b192b97a3b6e644cd8b288f642db8fc254676a0b2c9811df40aba3d5a44/0 gpu_sched.sched_policy=0

rhgb quiet root=UUID=5125c6a7-d169-4e52-9a0c-8e010e37cdeb rootflags=subvol=root rw ostree=/ostree/boot.0/default/200d6b192b97a3b6e644cd8b288f642db8fc254676a0b2c9811df40aba3d5a44/0 gpu_sched.sched_policy=0

rhgb quiet root=UUID=5125c6a7-d169-4e52-9a0c-8e010e37cdeb rootflags=subvol=root rw ostree=/ostree/boot.0/default/200d6b192b97a3b6e644cd8b288f642db8fc254676a0b2c9811df40aba3d5a44/0 gpu_sched.sched_policy=0

specs:

Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX B450-I GAMING v: Rev 1.xx
    serial: <superuser required> UEFI: American Megatrends v: 5302
    date: 10/20/2023
CPU:
  Info: 6-core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP cache: L2: 3 MiB
  Speed (MHz): avg: 2196 min/max: 2200/4208 cores: 1: 2196 2: 2200 3: 2195
    4: 2196 5: 2196 6: 2196 7: 2196 8: 2196 9: 2200 10: 2196 11: 2196 12: 2196
Graphics:
  Device-1: AMD Navi 32 [Radeon RX 7700 XT / 7800 XT] driver: amdgpu v: kernel
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.2
    compositor: kwin_wayland driver: N/A resolution: 2560x1440
  API: EGL v: 1.5 drivers: radeonsi,swrast
    platforms: wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.3.6 renderer: AMD
    Radeon RX 7800 XT (radeonsi navi32 LLVM 17.0.6 DRM 3.57
    6.7.9-204.fsync.fc39.x86_64)
  API: Vulkan v: 1.3.275 drivers: N/A surfaces: xcb,xlib,wayland

Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX B450-I GAMING v: Rev 1.xx
    serial: <superuser required> UEFI: American Megatrends v: 5302
    date: 10/20/2023
CPU:
  Info: 6-core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP cache: L2: 3 MiB
  Speed (MHz): avg: 2196 min/max: 2200/4208 cores: 1: 2196 2: 2200 3: 2195
    4: 2196 5: 2196 6: 2196 7: 2196 8: 2196 9: 2200 10: 2196 11: 2196 12: 2196
Graphics:
  Device-1: AMD Navi 32 [Radeon RX 7700 XT / 7800 XT] driver: amdgpu v: kernel
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.2
    compositor: kwin_wayland driver: N/A resolution: 2560x1440
  API: EGL v: 1.5 drivers: radeonsi,swrast
    platforms: wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.3.6 renderer: AMD
    Radeon RX 7800 XT (radeonsi navi32 LLVM 17.0.6 DRM 3.57
    6.7.9-204.fsync.fc39.x86_64)
  API: Vulkan v: 1.3.275 drivers: N/A surfaces: xcb,xlib,wayland

Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX B450-I GAMING v: Rev 1.xx
    serial: <superuser required> UEFI: American Megatrends v: 5302
    date: 10/20/2023
CPU:
  Info: 6-core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP cache: L2: 3 MiB
  Speed (MHz): avg: 2196 min/max: 2200/4208 cores: 1: 2196 2: 2200 3: 2195
    4: 2196 5: 2196 6: 2196 7: 2196 8: 2196 9: 2200 10: 2196 11: 2196 12: 2196
Graphics:
  Device-1: AMD Navi 32 [Radeon RX 7700 XT / 7800 XT] driver: amdgpu v: kernel
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.2
    compositor: kwin_wayland driver: N/A resolution: 2560x1440
  API: EGL v: 1.5 drivers: radeonsi,swrast
    platforms: wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.3.6 renderer: AMD
    Radeon RX 7800 XT (radeonsi navi32 LLVM 17.0.6 DRM 3.57
    6.7.9-204.fsync.fc39.x86_64)
  API: Vulkan v: 1.3.275 drivers: N/A surfaces: xcb,xlib,wayland

Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX B450-I GAMING v: Rev 1.xx
    serial: <superuser required> UEFI: American Megatrends v: 5302
    date: 10/20/2023
CPU:
  Info: 6-core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP cache: L2: 3 MiB
  Speed (MHz): avg: 2196 min/max: 2200/4208 cores: 1: 2196 2: 2200 3: 2195
    4: 2196 5: 2196 6: 2196 7: 2196 8: 2196 9: 2200 10: 2196 11: 2196 12: 2196
Graphics:
  Device-1: AMD Navi 32 [Radeon RX 7700 XT / 7800 XT] driver: amdgpu v: kernel
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.2
    compositor: kwin_wayland driver: N/A resolution: 2560x1440
  API: EGL v: 1.5 drivers: radeonsi,swrast
    platforms: wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.3.6 renderer: AMD
    Radeon RX 7800 XT (radeonsi navi32 LLVM 17.0.6 DRM 3.57
    6.7.9-204.fsync.fc39.x86_64)
  API: Vulkan v: 1.3.275 drivers: N/A surfaces: xcb,xlib,wayland

---

D

d3Xt3r•3/16/24, 11:54 AM

H

HikariKnightOP•3/16/24, 12:47 PM

i see nothing that should cause it to do this

D

d3Xt3r•3/16/24, 12:48 PM

Any reason why steamos-priv-write is refering to power2_cap when it doesn't exist?

H

HikariKnightOP•3/16/24, 12:49 PM

it refers to it because thats where gamescope-session tells it to write to

H

HikariKnightOP•3/16/24, 12:49 PM

if [[ "$WRITE_PATH" == /sys/class/hwmon/hwmon*/power*_cap ]]; then
   if [[ ":Jupiter:" =~ ":$SYS_ID:" || ":Galileo:" =~ ":$SYS_ID:" || "$ENABLE_HARDWARE_CONTROL_ON_NON_DECK_HARDWARE" = 1 ]]; then
      CommitWrite
   else
      echo "commit: Skipped - see /etc/default/steam-hardware-control" | systemd-cat -t p-steamos-priv-write -p warning
   fi
fi

if [[ "$WRITE_PATH" == /sys/class/hwmon/hwmon*/power*_cap ]]; then
   if [[ ":Jupiter:" =~ ":$SYS_ID:" || ":Galileo:" =~ ":$SYS_ID:" || "$ENABLE_HARDWARE_CONTROL_ON_NON_DECK_HARDWARE" = 1 ]]; then
      CommitWrite
   else
      echo "commit: Skipped - see /etc/default/steam-hardware-control" | systemd-cat -t p-steamos-priv-write -p warning
   fi
fi

if [[ "$WRITE_PATH" == /sys/class/hwmon/hwmon*/power*_cap ]]; then
   if [[ ":Jupiter:" =~ ":$SYS_ID:" || ":Galileo:" =~ ":$SYS_ID:" || "$ENABLE_HARDWARE_CONTROL_ON_NON_DECK_HARDWARE" = 1 ]]; then
      CommitWrite
   else
      echo "commit: Skipped - see /etc/default/steam-hardware-control" | systemd-cat -t p-steamos-priv-write -p warning
   fi
fi

if [[ "$WRITE_PATH" == /sys/class/hwmon/hwmon*/power*_cap ]]; then
   if [[ ":Jupiter:" =~ ":$SYS_ID:" || ":Galileo:" =~ ":$SYS_ID:" || "$ENABLE_HARDWARE_CONTROL_ON_NON_DECK_HARDWARE" = 1 ]]; then
      CommitWrite
   else
      echo "commit: Skipped - see /etc/default/steam-hardware-control" | systemd-cat -t p-steamos-priv-write -p warning
   fi
fi

H

HikariKnightOP•3/16/24, 12:50 PM

if steamdeck or hardware controls enabled then commit the write

H

HikariKnightOP•3/16/24, 12:50 PM

otherwise skip it and declinewrite

H

HikariKnightOP•3/16/24, 12:50 PM

decline is at the bottom of the script and runs this

H

HikariKnightOP•3/16/24, 12:50 PM

function DeclineWrite()
{
    echo "decline: $WRITE_VALUE -> $WRITE_PATH" | systemd-cat -t p-steamos-priv-write -p err
    exit 1
}

function DeclineWrite()
{
    echo "decline: $WRITE_VALUE -> $WRITE_PATH" | systemd-cat -t p-steamos-priv-write -p err
    exit 1
}

function DeclineWrite()
{
    echo "decline: $WRITE_VALUE -> $WRITE_PATH" | systemd-cat -t p-steamos-priv-write -p err
    exit 1
}

function DeclineWrite()
{
    echo "decline: $WRITE_VALUE -> $WRITE_PATH" | systemd-cat -t p-steamos-priv-write -p err
    exit 1
}

H

HikariKnightOP•3/16/24, 12:51 PM

i am curious if this also happens on the desktop image

HHikariKnight i am curious if this also happens on the desktop image

D

d3Xt3r•3/16/24, 12:53 PM

From the comment from the other guy, apparently the desktop image is fine

H

HikariKnightOP•3/16/24, 12:55 PM

ok so it is one of the packages in the deck image that does this

H

HikariKnightOP•3/16/24, 12:55 PM

thats going to take a while to go through

K

Kyle Gospo•3/16/24, 4:31 PM

@antheas could this be adjustor?

KKyle Gospo @antheas could this be adjustor?

A

antheas•3/16/24, 4:32 PM

Needs to be explicitly turned on

K

Kyle Gospo•3/16/24, 4:32 PM

Good, good

K

Kyle Gospo•3/16/24, 4:33 PM

Really confused what's setting this then

A

antheas•3/16/24, 4:33 PM

Also only supports 2 cpus

A

antheas•3/16/24, 4:33 PM

But never hurts to open hhd and verify

A

antheas•3/16/24, 4:34 PM

Also only writes to the cpu

A

antheas•3/16/24, 4:35 PM

We have gotten another 1-2 reports from egpu users though

A

antheas•3/16/24, 4:35 PM

I was trying to see if ryzenadj also changed the tdp limit of amd gpus

A

antheas•3/16/24, 4:35 PM

Results were inconclusive

H

HikariKnightOP•3/16/24, 4:46 PM

also seems to only affect some hardware as i cannot replicate it with RX6600XT and Ryzen 5 5600x

HHikariKnight also seems to only affect some hardware as i cannot replicate it with RX6600XT a...

D

d3Xt3r•3/16/24, 8:08 PM

I had the same issue with a 6600 XT, same desktop. Actually bought my GPU because I thought my 6600 XT was too old/slow for Last Epoch lol, didn't know about the TDP limits then.

H

HikariKnightOP•3/16/24, 8:09 PM

huh, this is getting even weirder then

A

antheas•3/16/24, 8:11 PM

Seems like steam is setting the limit for some reason

A

antheas•3/16/24, 8:11 PM

15w is steam deck I mean come on

Aantheas 15w is steam deck I mean come on

H

HikariKnightOP•3/16/24, 8:12 PM

yeah it is, it is just weird it affects a super small subset of hardware and its setting it in a different way than the rest of steamos which uses

steamos-priv-write

steamos-priv-write

steamos-priv-write

steamos-priv-write

Some hardware stuck at 15W TDP in gamescope-session

Similar Threads

Similar Threads

Similar Threads