Power Manager brightness control issue  [Solved]

Help for Current Versions of MX
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
joegreen
Posts: 33
Joined: Sun Feb 19, 2023 1:54 am

Power Manager brightness control issue

#1 Post by joegreen »

Code: Select all

Snapshot created on: 20240906_1453
System:
  Kernel: 6.10.9-amd64 [6.10.9-1~mx23ahs] arch: x86_64 bits: 64 compiler: N/A
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.10.9-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.4_ahs_x64 Libretto July 31  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Laptop System: LENOVO product: 20YU001KUS v: ThinkPad P17 Gen 2i
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: LENOVO model: 20YU001KUS v: SDK0J40697 WIN serial: <superuser required> UEFI: LENOVO
    v: N37ET55W (1.36 ) date: 07/09/2024
Battery:
  ID-1: BAT0 charge: 67.7 Wh (76.6%) condition: 88.4/94.0 Wh (94.1%) volts: 12.2 min: 11.5
    model: Celxpert 5B10W13959 type: Li-poly serial: <filter> status: not charging cycles: 20
  Device-1: hidpp_battery_0 model: Logitech Wireless Mobile Mouse MX Anywhere 2S serial: <filter>
    charge: 100% (should be ignored) rechargeable: yes status: discharging
CPU:
  Info: model: 11th Gen Intel Core i7-11850H bits: 64 type: MT MCP arch: Tiger Lake gen: core 11
    level: v4 note: check built: 2020 process: Intel 10nm family: 6 model-id: 0x8D (141) stepping: 1
    microcode: 0x52
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 640 KiB
    desc: d-8x48 KiB; i-8x32 KiB L2: 10 MiB desc: 8x1.2 MiB L3: 24 MiB desc: 1x24 MiB
  Speed (MHz): avg: 833 high: 1100 min/max: 800/4800 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 1100 6: 800 7: 800 8: 800 9: 800
    10: 800 11: 800 12: 800 13: 1042 14: 800 15: 800 16: 800 bogomips: 79872
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB: conditional; RSB filling;
    PBRSB-eIBRS: SW sequence; BHI: SW loop, KVM: SW loop
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel TigerLake-H GT1 [UHD Graphics] vendor: Lenovo driver: i915 v: kernel
    arch: Gen-12.1 process: Intel 10nm built: 2020-21 ports: active: eDP-1 empty: DP-1, DP-2, DP-3,
    DP-4, DP-5, HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:9a60 class-ID: 0300
  Device-2: NVIDIA GA107GLM [RTX A2000 Mobile] vendor: Lenovo driver: nvidia v: 535.183.06
    non-free: 530.xx+ status: current (as of 2023-03) arch: Ampere code: GAxxx process: TSMC n7 (7nm)
    built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 8 link-max: lanes: 16 bus-ID: 01:00.0
    chip-ID: 10de:25b8 class-ID: 0300
  Device-3: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 3-4:3 chip-ID: 04f2:b6be
    class-ID: fe01 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa alternate: nv dri: iris gpu: i915
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26") s-diag: 583mm (22.95")
  Monitor-1: eDP-1 model: BOE Display 0x08de built: 2019 res: 1920x1080 hz: 60 dpi: 128
    gamma: 1.2 size: 382x215mm (15.04x8.46") diag: 438mm (17.3") ratio: 16:9 modes: 3840x2160
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: Mesa Intel UHD Graphics (TGL GT1)
    direct-render: Yes
Audio:
  Device-1: Intel Tiger Lake-H HD Audio vendor: Lenovo driver: sof-audio-pci-intel-tgl
    alternate: snd_hda_intel, snd_soc_avs, snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:43c8
    class-ID: 0401
  Device-2: NVIDIA vendor: Lenovo driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 8 link-max: lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:2291 class-ID: 0403
  API: ALSA v: k6.10.9-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 09:00.0 chip-ID: 8086:2725 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-2: Intel Ethernet I225-LM vendor: Lenovo driver: igc v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 port: N/A bus-ID: 0b:00.0 chip-ID: 8086:15f2 class-ID: 0200
  IF: eth0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-14:5 chip-ID: 8087:0032
    class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: N/A rfk-block: hardware: no
    software: no address: <filter>
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
Drives:
  Local Storage: total: 3.25 TiB used: 16 GiB (0.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WD BLACK SN770 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 731120WD temp: 39.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:8 vendor: Micron model: MTFDKBA512TFH size: 476.94 GiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 7006P7LN temp: 33.9 C scheme: GPT
  ID-3: /dev/nvme2n1 maj-min: 259:1 vendor: Western Digital model: WD BLACK SN850X 2000GB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 620361WD temp: 35.9 C scheme: GPT
  ID-4: /dev/sda maj-min: 8:0 type: USB vendor: Samsung model: Flash Drive size: 59.75 GiB
    block-size: physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 1100 scheme: GPT
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 22.79 GiB size: 22.27 GiB (97.69%) used: 16 GiB (71.8%) fs: ext4 dev: /dev/sda2
    maj-min: 8:2
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 6 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
  ID-2: swap-2 type: zram size: 256 MiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:
  Src: /sys System Temperatures: cpu: 50.0 C mobo: N/A
  Fan Speeds (RPM): fan-1: 1938 fan-2: 1630
Repos:
  Packages: pm: dpkg pkgs: 2187 libs: 1114 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
    2: deb http://mxrepo.com/mx/repo/ bookworm ahs
Info:
  Processes: 347 Uptime: 0m wakeups: 7 Memory: 31.06 GiB used: 1.56 GiB (5.0%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Hello,

The brightness control in XFCE Power Manager doesn't go to minimum any more for the last few days. The laptop brightness control keys, which are toggled in power manager to work with power manager, do go to minimum. Both controls used to work the same. To explain the issue more, imagine that the brightness slider all way turned down will still be 10% (guess) brightness. While using the physical buttons, reduces brightness correctly to minimum 2% (guess). So the minimum brightness position for the slider is not set to minimum somehow.

If I use Brightness systray from MX Tools, the slider on the hardware brightness works as intended and goes all the way to zero (total black). Which is not something I want. Plus, enabling The brightness systray causes severe lag and stutter.

Edit: Here is the screenshot of the problem. The brightness slider is all the way to the left, but we can see that the hardware backlight is at 9.
Image

Edit 2: Found a workaround for anybody in simmilar situation:
https://forum.endeavouros.com/t/is-it-p ... it/26660/5

In case the linked solution disappears, as I have seen many times, the workaround is:
xfce-power-manager to specify a minimum brightness level.

Run xfce4-settings-editor in terminal
Click on + Add and enter
Property:
/xfce4-power-manager/brightness-slider-min-level
Type:
Int
Value: e. g.
5

-OR-

completely via cli
xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/brightness-slider-min-level -t int --create -s 5
where -s 5 being an example minimum value of “5”.
Thank you for your time
Last edited by joegreen on Mon Sep 23, 2024 2:13 pm, edited 6 times in total.

User avatar
j2mcgreg
Global Moderator
Posts: 7189
Joined: Tue Oct 23, 2007 12:04 pm

Re: Power Manager brightness control issue

#2 Post by j2mcgreg »

Please share your complete QSI. If you have concerns about security, you can attach it to your first post so that only our members can access it -- not world + dog.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

joegreen
Posts: 33
Joined: Sun Feb 19, 2023 1:54 am

Re: Power Manager brightness control issue

#3 Post by joegreen »

j2mcgreg wrote: Wed Sep 18, 2024 8:29 am Please share your complete QSI. If you have concerns about security, you can attach it to your first post so that only our members can access it -- not world + dog.
Hello. Only repo sources are missing and I change them all the time depending on bandwidth performance . They are absolutely irrelevant.

User avatar
j2mcgreg
Global Moderator
Posts: 7189
Joined: Tue Oct 23, 2007 12:04 pm

Re: Power Manager brightness control issue

#4 Post by j2mcgreg »

joegreen wrote: Wed Sep 18, 2024 8:34 am
j2mcgreg wrote: Wed Sep 18, 2024 8:29 am Please share your complete QSI. If you have concerns about security, you can attach it to your first post so that only our members can access it -- not world + dog.
Hello. Only repo sources are missing and I change them all the time depending on bandwidth performance . They are absolutely irrelevant.
The rules of this forum require that the complete QSI report accompanies all help requests.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

User avatar
siamhie
Global Moderator
Posts: 3775
Joined: Fri Aug 20, 2021 5:45 pm

Re: Power Manager brightness control issue

#5 Post by siamhie »

joegreen wrote: Wed Sep 18, 2024 8:34 am
j2mcgreg wrote: Wed Sep 18, 2024 8:29 am Please share your complete QSI. If you have concerns about security, you can attach it to your first post so that only our members can access it -- not world + dog.
Hello. Only repo sources are missing and I change them all the time depending on bandwidth performance . They are absolutely irrelevant.

Have you added any Ubuntu repositories or other's outside of Debian/MX's? (would know if you had just left that in your QSI)
This is my Fluxbox . There are many others like it, but this one is mine. My Fluxbox is my best friend. It is my life.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.

joegreen
Posts: 33
Joined: Sun Feb 19, 2023 1:54 am

Re: Power Manager brightness control issue

#6 Post by joegreen »

I will redo the QSI asap. I'm booting windows at the moment. In the mean time, I just have Debian/MX repos. edit: DONE, added the repos

User avatar
CharlesV
Administrator
Posts: 8030
Joined: Sun Jul 07, 2019 5:11 pm

Re: Power Manager brightness control issue

#7 Post by CharlesV »

I saw this on an HP when the user dual booted into windows and did an update. The update had turned Fast Startup back up. I turned it off, Shut the machine down waited 1 min, then powered back up into Linux and the issue was gone.
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

joegreen
Posts: 33
Joined: Sun Feb 19, 2023 1:54 am

Re: Power Manager brightness control issue

#8 Post by joegreen »

CharlesV wrote: Wed Sep 18, 2024 10:34 am I saw this on an HP when the user dual booted into windows and did an update. The update had turned Fast Startup back up. I turned it off, Shut the machine down waited 1 min, then powered back up into Linux and the issue was gone.
Hello. Thank you for your time. I just checked. I don't have fast startup. In fact since I have disabled hibernation, I can't have fast start up enabled anyway.

User avatar
CharlesV
Administrator
Posts: 8030
Joined: Sun Jul 07, 2019 5:11 pm

Re: Power Manager brightness control issue

#9 Post by CharlesV »

Hmm.. And it is not your back light that is still showing right ?
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

joegreen
Posts: 33
Joined: Sun Feb 19, 2023 1:54 am

Re: Power Manager brightness control issue

#10 Post by joegreen »

CharlesV wrote: Wed Sep 18, 2024 11:47 am Hmm.. And it is not your back light that is still showing right ?
It is the back light. But the problem is that the power manager brightness slider should, and used to, dim the back light to minimum. Now when it is set all the way down, it is still too bright. But, with the physical brightness buttons, the brightness goes to actual minimum. I have added more details to my original post.

Post Reply

Return to “MX Help”