Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken BIOS setting mapping/efivars on Bazzite 41 #1800

Open
Emiliopg91 opened this issue Oct 29, 2024 · 2 comments
Open

Broken BIOS setting mapping/efivars on Bazzite 41 #1800

Emiliopg91 opened this issue Oct 29, 2024 · 2 comments
Labels
bug Something isn't working stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed

Comments

@Emiliopg91
Copy link

Emiliopg91 commented Oct 29, 2024

Describe the bug

after upgrading to stable-41.20241029 of image bazzite azzite-asus-nvidia-open, efivars stopped working so there's no way to control anything using rog-control-center

At the begining I thouth that it may be due to a rog-control-center bug, however i tried to run following command:

fwupdmgr get-bios-settings --json. The expected output was:
{
"BiosSettings" : [
{
"Name" : "nv_dynamic_boost",
"Description" : "Set the Nvidia dynamic boost limit",
"Filename" : "/sys/class/firmware-attributes/asus-bioscfg/attributes/nv_dynamic_boost",
"BiosSettingId" : "com.asus-bioscfg.nv_dynamic_boost",
"BiosSettingCurrentValue" : "5",
"BiosSettingReadOnly" : "false",
"BiosSettingType" : 2,
"BiosSettingLowerBound" : 5,
"BiosSettingUpperBound" : 25,
"BiosSettingScalarIncrement" : 1
},
{
"Name" : "charge_mode",
"Description" : "Show the current mode of charging",
"Filename" : "/sys/class/firmware-attributes/asus-bioscfg/attributes/charge_mode",
"BiosSettingId" : "com.asus-bioscfg.charge_mode",
"BiosSettingCurrentValue" : "1",
"BiosSettingReadOnly" : "false",
"BiosSettingType" : 1,
"BiosSettingPossibleValues" : [
"0",
"1",
"2"
]
},
{
"Name" : "nv_temp_target",
"Description" : "Set the Nvidia max thermal limit",
"Filename" : "/sys/class/firmware-attributes/asus-bioscfg/attributes/nv_temp_target",
"BiosSettingId" : "com.asus-bioscfg.nv_temp_target",
"BiosSettingCurrentValue" : "75",
"BiosSettingReadOnly" : "false",
"BiosSettingType" : 2,
"BiosSettingLowerBound" : 75,
"BiosSettingUpperBound" : 87,
"BiosSettingScalarIncrement" : 1
},
{
"Name" : "cores_performance",
"Description" : "Set the max available performance cores",
"Filename" : "/sys/class/firmware-attributes/asus-bioscfg/attributes/cores_performance",
"BiosSettingId" : "com.asus-bioscfg.cores_performance",
"BiosSettingCurrentValue" : "8",
"BiosSettingReadOnly" : "false",
"BiosSettingType" : 2,
"BiosSettingLowerBound" : 4,
"BiosSettingUpperBound" : 8,
"BiosSettingScalarIncrement" : 1
},
{
"Name" : "panel_overdrive",
"Description" : "Set the panel refresh overdrive",
"Filename" : "/sys/class/firmware-attributes/asus-bioscfg/attributes/panel_overdrive",
"BiosSettingId" : "com.asus-bioscfg.panel_overdrive",
"BiosSettingCurrentValue" : "1",
"BiosSettingReadOnly" : "false",
"BiosSettingType" : 1,
"BiosSettingPossibleValues" : [
"0",
"1"
]
},
{
"Name" : "ppt_pl1_spl",
"Description" : "Set the CPU slow package limit",
"Filename" : "/sys/class/firmware-attributes/asus-bioscfg/attributes/ppt_pl1_spl",
"BiosSettingId" : "com.asus-bioscfg.ppt_pl1_spl",
"BiosSettingCurrentValue" : "80",
"BiosSettingReadOnly" : "false",
"BiosSettingType" : 2,
"BiosSettingLowerBound" : 5,
"BiosSettingUpperBound" : 175,
"BiosSettingScalarIncrement" : 1
},
{
"Name" : "ppt_pl2_sppt",
"Description" : "Set the CPU fast package limit",
"Filename" : "/sys/class/firmware-attributes/asus-bioscfg/attributes/ppt_pl2_sppt",
"BiosSettingId" : "com.asus-bioscfg.ppt_pl2_sppt",
"BiosSettingCurrentValue" : "80",
"BiosSettingReadOnly" : "false",
"BiosSettingType" : 2,
"BiosSettingLowerBound" : 5,
"BiosSettingUpperBound" : 175,
"BiosSettingScalarIncrement" : 1
},
{
"Name" : "gpu_mux_mode",
"Description" : "Set the GPU display MUX mode",
"Filename" : "/sys/class/firmware-attributes/asus-bioscfg/attributes/gpu_mux_mode",
"BiosSettingId" : "com.asus-bioscfg.gpu_mux_mode",
"BiosSettingCurrentValue" : "1",
"BiosSettingReadOnly" : "false",
"BiosSettingType" : 1,
"BiosSettingPossibleValues" : [
"0",
"1"
]
},
{
"Name" : "dgpu_disable",
"Description" : "Disable the dGPU",
"Filename" : "/sys/class/firmware-attributes/asus-bioscfg/attributes/dgpu_disable",
"BiosSettingId" : "com.asus-bioscfg.dgpu_disable",
"BiosSettingCurrentValue" : "0",
"BiosSettingReadOnly" : "false",
"BiosSettingType" : 1,
"BiosSettingPossibleValues" : [
"0",
"1"
]
},
{
"Name" : "cores_efficiency",
"Description" : "Set the max available efficiency cores",
"Filename" : "/sys/class/firmware-attributes/asus-bioscfg/attributes/cores_efficiency",
"BiosSettingId" : "com.asus-bioscfg.cores_efficiency",
"BiosSettingCurrentValue" : "16",
"BiosSettingReadOnly" : "false",
"BiosSettingType" : 2,
"BiosSettingLowerBound" : 0,
"BiosSettingUpperBound" : 16,
"BiosSettingScalarIncrement" : 1
},
{
"Name" : "pending_reboot",
"Description" : "Los parámetros aplicarán tras reiniciar el sistema",
"Filename" : "/sys/class/firmware-attributes/asus-bioscfg/attributes/pending_reboot",
"BiosSettingId" : "com.asus-bioscfg.pending_reboot",
"BiosSettingCurrentValue" : "0",
"BiosSettingReadOnly" : "true",
"BiosSettingType" : 0
},
{
"Name" : "thermal_policy",
"Description" : "Fan stuff todo",
"Filename" : "/sys/class/firmware-attributes/asus-bioscfg/attributes/thermal_policy",
"BiosSettingId" : "com.asus-bioscfg.thermal_policy",
"BiosSettingCurrentValue" : "3",
"BiosSettingReadOnly" : "false",
"BiosSettingType" : 1,
"BiosSettingPossibleValues" : [
"0",
"1",
"2"
]
},
{
"Name" : "boot_sound",
"Description" : "Set the boot POST sound",
"Filename" : "/sys/class/firmware-attributes/asus-bioscfg/attributes/boot_sound",
"BiosSettingId" : "com.asus-bioscfg.boot_sound",
"BiosSettingCurrentValue" : "0",
"BiosSettingReadOnly" : "false",
"BiosSettingType" : 1,
"BiosSettingPossibleValues" : [
"0",
"1"
]
}
]
}

but the actual output is
{
"BiosSettings" : [ ]
}

So the problem is for sure the kernel integration with bios/firmware. It works perfectly on stable-40.20241020, so I reverted inmediatly

Please check it and do a regression for asus image

What did you expect to happen?

Mapping bios settings to it's corresponding efivar to allow rog-control-center or any other sofware to edit bios settings and adjust power limits to computer APUs

Output of rpm-ostree status

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-asus-nvidia-open:stable
Digest: sha256:ed4087e2816d464a9661182ad2e5ef3fb274c273c5bb6985bb63776df030d587
Version: 40.20241020 (2024-10-21T05:08:39Z)
LayeredPackages: liquidctl
Initramfs: regenerate

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-asus-nvidia-open:stable
Digest: sha256:44702eb6c52c6eda0c5219ae72b2aa4fd7409b61621cef6e8e1d56dcaef27570
Version: 41.20241029 (2024-10-29T03:46:06Z)
LayeredPackages: liquidctl
Initramfs: regenerate

Hardware

ROG Strix G614JZ_G614JZ

Extra information or context

No response

@dosubot dosubot bot added the bug Something isn't working label Oct 29, 2024
@antheas
Copy link
Contributor

antheas commented Oct 29, 2024

Please use ``` to quote code blocks

/sys/class/firmware-attributes/asus-bioscfg is something that is set by the out-of-tree patch series asus-linux is preparing to submit upstream. We do not carry that patch series on the new kernel.

This makes this a feature request. I will try to weed through the random series he spams online and merge part of them in.

Copy link

dosubot bot commented Jan 28, 2025

Hi, @Emiliopg91. I'm Dosu, and I'm helping the bazzite team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • You reported an issue with the Bazzite 41 image where efivars malfunction, impacting rog-control-center's BIOS management.
  • User antheas identified the problem as a missing out-of-tree patch series from asus-linux in the new kernel.
  • The issue has been categorized as a feature request, with plans to review and possibly integrate the patch series.

Next Steps:

  • Please let us know if this issue is still relevant to the latest version of the bazzite repository by commenting here.
  • If there is no further activity, the issue will be automatically closed in 14 days.

Thank you for your understanding and contribution!

@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed
Projects
None yet
Development

No branches or pull requests

2 participants