Troubleshooting a screen brightness issue and I noticed this error. I have no Idea how to set the power limit in range?

amdgpu 0000:c4:00.0: amdgpu: New power limit (30) is out of range [100,120]
amdgpu 0000:c4:00.0: amdgpu: Failed to set power limit value

I also see this [drm] Cannot find any crtc or sizes, although it’s not in red and have no idea if they are related.

Im using arch, and have installed the mesa, lib32-mesa, vulkan-radeon, lib32-vulkan-radeon packages.

c4:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 33 [Radeon RX 7600/7600 XT/7600M XT/7600S/7700S / PRO W7600] (rev c1)
        Subsystem: Framework Computer Inc. Device 0007
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu
c5:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Strix [Radeon 880M / 890M] (rev c1)
        Subsystem: Framework Computer Inc. Device 000d
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu

I also had the power-profiles-daemon installed. I have removed it but the error presists.

I’ve been reading about setting power limmits can be a bad thing on amd GPU’s https://gitlab.freedesktop.org/drm/amd/-/issues/2992#note_2310545

Any thoughts?

Edit: when plugged in the error disappears. Only happens on battery power. Just booted four times, two on ac power no error and two on battery with same error.

Might be a kernel or driver bug. Curious on how to figure out whats going on so I can report it to the proper plaice…

  • just_another_person@lemmy.world
    31·
    1 day ago

    Your power restrictions are preventing the higher power settings.

    If you’re using Gnome or KDE, you can use the applets to just turn it up a notch and get more brightness.

    • Maiq@piefed.socialOPEnglish
      2·
      1 day ago

      Using hyprland. On my first install a few days ago the backlight buttons worked fine. Then I nuked that install to install btrfs so I could use snapper. I’m thinking the backlight might have been working then because i installed plasma-meta and kde-applications-meta, they probably pulled in whatever was talking to the display. Although that’s just my speculation.

      On the amd errors i have I’ve found they only happen on battery power. Confirmed by booting four times. Two on ac had no errors but the two on battery did. Probably a driver bug. Likely unrelated to the backlight.

      Ill try booting up a live usb with kde in the morning to see if the backlight works there. Maybe eOS or something.

      • just_another_person@lemmy.world
        31·
        1 day ago

        Back up a bit because you’re conflating a number of things, so let me try to break it down:

        1. If you’re using Hyprland, you’re losing all the power management features of the more fully featured DE’s like Gnome or KDE. This isn’t a flaw, it’s just an acceptance of the trade-off.
        2. Unless you’ve directly intervened, the power profiles are set to whatever your distro installs and sets from the initial install. Which leads to…
        3. There are different defaults for powered vs battery by default. If you’re on a laptop and you don’t have the DE helpers, you’re on your own.
        4. The hardware power management built in to your laptop may be playing a role here, so check your BIOS
        5. Check dmesg to see what live changes your hardware controllers might be making
        6. Check the Framework forums for keywords related to “Hyprland” to see if somebody has easy scripts for you to help. Otherwise, just switch to a DE that manages power the way you’d expect.
        • Maiq@piefed.socialOPEnglish
          1·
          23 hours ago

          Your probably right, might be getting ahead of myself.

          Installed powerkit, it is for x11 but I thought id give her a whirl. Setting brightness on AC plug works. Like me, powerkit complains about not being able to start xscreensaver.

          The cpupower-gui fails with a python argparse error. Using power-profiles-daemon and checking cpupower frequency-info the profiles are changing.

          turbostat as root fails with cpu0 msr offset 0x611 read failed - i/o error. Still researching.

          Checking dmesg isn’t reporting anything but the initial amdgpu errors that happen on first boot on battery. I just started cp2077, the dmesg’s after game start all seem normal using battery power. Looks like it’s only happening on boot.

          I’ll keep monitoring.

          I’ll search around in my hyprland.conf to make sure the brightness keymappings are correct. powerkit changing brightness makes me think it’s a config problem.