[Solved] Laptop brightness can not be changed on Asus TUF A15 FA506N

Need help with peripherals or devices?
Post Reply
Message
Author
Raxus
Posts: 10
Joined: 2024-06-06 06:35

[Solved] Laptop brightness can not be changed on Asus TUF A15 FA506N

#1 Post by Raxus »

Hi Everyone,


As of recently i have a new laptop for work (Asus TUF A15 FA506N) which i turned into a dual boot with Windows and Debian (Gnome).
First thing i have noticed was that my wifi adapter did not work, so i've added bookworm-backports to /etc/apt/sources.list.
It installed a new kernel version (6.7.12+bpo-amd64) and after that wifi worked just fine.


Next thing i have done was install Nvidia drivers, which installed succesfully.
One thing i noticed was that the windowing system moved from wayland to X11, but i'm fine with that.

Finally i noticed that the laptops build-in monitor's brightness can not be changed.
The brightness is dim compared to the external monitor and it's causing me to get a headache.

I am able to change the slider in Gnome's settings, but the change does not reflect into the actual brightness changing.
When booting into Windows, i am able to change the brightness.
I have already followed some suggestions online, but none fixed my issue.

I am open to do a clean install if needed.


Does anyone know where to start with this issue?


Thanks in advance!
Last edited by Raxus on 2024-06-17 11:15, edited 3 times in total.

Raxus
Posts: 10
Joined: 2024-06-06 06:35

Re: Laptop brightness can not be changed

#2 Post by Raxus »

This is the results of inxi

Code: Select all

System:
  Kernel: 6.7.12+bpo-amd64 arch: x86_64 bits: 64 compiler: N/A
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.7.12+bpo-amd64
    root=UUID=63a73ddf-2ead-4efa-9231-d491ce2a8850 ro nvidia-drm.modeset=1
    nvidia-drm.modeset=1 quiet acpi_osi=Linux acpi_backlight=vendor
  Desktop: GNOME v: 43.9 tk: GTK v: 3.24.38 wm: gnome-shell dm: GDM3 v: 43.0
    Distro: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: ASUSTeK product: ASUS TUF Gaming A15 FA506NC_FA506NC
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: FA506NC v: 1.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: FA506NC.302 date: 12/26/2023
Battery:
  ID-1: BAT1 charge: 45.7 Wh (92.9%) condition: 49.2/48.1 Wh (102.2%)
    volts: 13.0 min: 11.7 model: ASUS A32-K55 type: Li-ion serial: N/A
    status: charging
CPU:
  Info: model: AMD Ryzen 5 7535HS with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 3+ gen: 4 level: v3 note: check built: 2022 process: TSMC n6 (7nm)
    family: 0x19 (25) model-id: 0x44 (68) stepping: 1 microcode: 0xA404102
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
    L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 1049 high: 2252 min/max: 400/4603 scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 1370 2: 400 3: 400
    4: 400 5: 1397 6: 1396 7: 1395 8: 400 9: 2252 10: 1395 11: 400 12: 1387
    bogomips: 79049
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  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: Vulnerable: Safe RET, no microcode
  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: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GA107M [GeForce RTX 3050 Mobile] vendor: ASUSTeK
    driver: nvidia v: 525.147.05 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 ports: active: none off: HDMI-A-1 empty: DP-9
    bus-ID: 01:00.0 chip-ID: 10de:25a2 class-ID: 0300
  Device-2: AMD Rembrandt [Radeon 680M] vendor: ASUSTeK driver: amdgpu
    v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22
    pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1,
    DP-2, DP-3, DP-4, DP-5, DP-6, DP-7, DP-8 bus-ID: 06:00.0
    chip-ID: 1002:1681 class-ID: 0300 temp: 56.0 C
  Device-3: Shine-optics USB2.0 HD UVC WebCam type: USB driver: uvcvideo
    bus-ID: 1-4:2 chip-ID: 3277:0029 class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9
    compositor: gnome-shell driver: X: loaded: amdgpu,nvidia
    unloaded: fbdev,modesetting,nouveau,radeon,vesa alternate: nv
    dri: radeonsi gpu: amdgpu,nvidia,nvidia-nvswitch display-ID: :1 screens: 1
  Screen-1: 0 s-res: 5360x1440 s-dpi: 96 s-size: 1418x381mm (55.83x15.00")
    s-diag: 1468mm (57.81")
  Monitor-1: HDMI-A-1 mapped: HDMI-1-0 note: disabled pos: primary,top-left
    model: LG (GoldStar) HDR WQHD serial: <filter> built: 2023 res: 3440x1440
    hz: 85 dpi: 107 gamma: 1.2 size: 820x346mm (32.28x13.62")
    diag: 888mm (34.9") modes: max: 3440x1440 min: 640x480
  Monitor-2: eDP-1 mapped: eDP pos: bottom-r model: ChiMei InnoLux 0x1521
    built: 2020 res: 1920x1080 hz: 144 dpi: 142 gamma: 1.2
    size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon Graphics (rembrandt
    LLVM 15.0.6 DRM 3.57 6.7.12+bpo-amd64) direct-render: Yes
Audio:
  Device-1: NVIDIA vendor: ASUSTeK 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
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: ASUSTeK
    driver: snd_pci_acp6x v: kernel alternate: snd_pci_acp3x, snd_rn_pci_acp3x,
    snd_pci_acp5x, snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_rembrandt pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 06:00.5 chip-ID: 1022:15e2
    class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 06:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.7.12+bpo-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: e000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Realtek RTL8852BE PCIe 802.11ax Wireless Network
    vendor: AzureWave driver: rtw89_8852be v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 04:00.0 chip-ID: 10ec:b852
    class-ID: 0280
  IF: wlp4s0 state: down mac: <filter>
Bluetooth:
  Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb v: 0.8
    bus-ID: 3-3:4 chip-ID: 13d3:3571 class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0
    lmp-v: 5.2 sub-v: 91cb hci-v: 5.2 rev: dfb7
  Info: acl-mtu: 1021:6 sco-mtu: 255:12 link-policy: rswitch hold sniff park
    link-mode: peripheral accept service-classes: rendering, capturing, object
    transfer, audio, telephony
Drives:
  Local Storage: total: 715.41 GiB used: 51.67 GiB (7.2%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: MZVLB256HAHQ-000H1 size: 238.47 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: EXD70H1Q temp: 37.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:5 vendor: Western Digital model: WD PC
    SN740 SDDPNQD-512G-1102 size: 476.94 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 73113000 temp: 35.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 233.42 GiB size: 228.7 GiB (97.98%)
    used: 51.64 GiB (22.6%) fs: ext4 dev: /dev/nvme1n1p7 maj-min: 259:12
  ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%)
    used: 37.8 MiB (14.8%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:6
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 977 MiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme1n1p8 maj-min: 259:13
Sensors:
  System Temperatures: cpu: 60.4 C mobo: N/A gpu: amdgpu temp: 57.0 C
  Fan Speeds (RPM): cpu: 2400
Repos:
  Packages: 2243 pm: dpkg pkgs: 2196 libs: 1041
    tools: apt,apt-get,gnome-software,synaptic pm: flatpak pkgs: 47
  Active apt repos in: /etc/apt/sources.list
    1: deb http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware
    2: deb-src http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware
    3: deb http://deb.debian.org/debian/ bookworm-backports main non-free-firmware
    4: deb-src http://deb.debian.org/debian/ bookworm-backports main non-free-firmware
    5: deb http://security.debian.org/debian-security bookworm-security main non-free-firmware
    6: deb-src http://security.debian.org/debian-security bookworm-security main non-free-firmware
    7: deb http://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware
    8: deb-src http://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/apandada1-ubuntu-brightness-controller-bookworm.list
    1: deb https://ppa.launchpadcontent.net/apandada1/brightness-controller/ubuntu/ bookworm main
  Active apt repos in: /etc/apt/sources.list.d/vscode.list
    1: deb [arch=amd64,arm64,armhf] https://packages.microsoft.com/repos/code stable main
Info:
  Processes: 432 Uptime: 23m wakeups: 1 Memory: 14.95 GiB
  used: 5.98 GiB (40.0%) Init: systemd v: 252 target: graphical (5)
  default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Shell: Bash v: 5.2.15 running-in: gjs inxi: 3.3.26

Aki
Global Moderator
Global Moderator
Posts: 3232
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 88 times
Been thanked: 427 times

Re: Laptop brightness can not be changed

#3 Post by Aki »

Hello,
Raxus wrote: 2024-06-06 07:06 As of recently i have a new laptop for work (Asus TUF A15 FA506N) which i turned into a dual boot with Windows and Debian (Gnome).
[..]
I noticed that the laptops build-in monitor's brightness can not be changed.
The brightness is dim compared to the external monitor and it's causing me to get a headache.

I am able to change the slider in Gnome's settings, but the change does not reflect into the actual brightness changing.
When booting into Windows, i am able to change the brightness.
Does the brightness control work from the keyboard ?

You computer uses a hybrid graphic architecture (amd+nvidia).

You may try setting the amdgpu.backlight parameter (amdgpu.backlight=0):

Code: Select all

/sbin/modinfo amdgpu | grep backlight
parm:           abmlevel:ABM level (0 = off (default), 1-4 = backlight reduction level)  (uint)
parm:           backlight:Backlight control (0 = pwm, 1 = aux, -1 auto (default)) (bint)
Please add "Asus TUF A15 FA506N" to the subject of the first post, like that: "Laptop brightness can not be changed with Asus TUF A15 FA506N"

Hope this helps.

--
note: moved to "Hardware" sub-forum.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

Raxus
Posts: 10
Joined: 2024-06-06 06:35

Re: Laptop brightness can not be changed

#4 Post by Raxus »

Hello,

Thanks for your reply
Aki wrote: 2024-06-06 12:11 Does the brightness control work from the keyboard ?
No, the popup appears on the screen, but the actual brightness does not change.

I have done what you suggested, but the problem is still there.
However, the little popup used to appear on my external monitor, and now appears on my laptop monitor. So maybe it's a step in the right direction.

Aki
Global Moderator
Global Moderator
Posts: 3232
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 88 times
Been thanked: 427 times

Re: Laptop brightness can not be changed

#5 Post by Aki »

Hello,
Raxus wrote: 2024-06-06 14:01 No, the popup appears on the screen, but the actual brightness does not change.
I have done what you suggested, but the problem is still there.
However, the little popup used to appear on my external monitor, and now appears on my laptop monitor. So maybe it's a step in the right direction.
Does your computer's main screen (panel) use LCD technology (it's not an OLED)?
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

Raxus
Posts: 10
Joined: 2024-06-06 06:35

Re: Laptop brightness can not be changed

#6 Post by Raxus »

Aki wrote: 2024-06-06 14:58 Hello,
Raxus wrote: 2024-06-06 14:01 No, the popup appears on the screen, but the actual brightness does not change.
I have done what you suggested, but the problem is still there.
However, the little popup used to appear on my external monitor, and now appears on my laptop monitor. So maybe it's a step in the right direction.
Does your computer's main screen (panel) use LCD technology (it's not an OLED)?
The specifications say it's an IPS monitor.

Raxus
Posts: 10
Joined: 2024-06-06 06:35

Re: Laptop brightness can not be changed on Asus TUF A15 FA506N

#7 Post by Raxus »

Does anyone have any other idea i can try?

dlu2021
Posts: 222
Joined: 2021-08-13 19:55
Location: Minnesota
Has thanked: 8 times
Been thanked: 42 times

Re: Laptop brightness can not be changed on Asus TUF A15 FA506N

#8 Post by dlu2021 »

Have you read through the arch wiki backlight article yet? It mentions that you might need a kernel module for asus laptops, asus-nb-wmi.

https://wiki.archlinux.org/title/Backlight

Raxus
Posts: 10
Joined: 2024-06-06 06:35

Re: Laptop brightness can not be changed on Asus TUF A15 FA506N

#9 Post by Raxus »

dlu2021 wrote: 2024-06-10 18:22 Have you read through the arch wiki backlight article yet? It mentions that you might need a kernel module for asus laptops, asus-nb-wmi.

https://wiki.archlinux.org/title/Backlight
I have not tried this yet. However, when running "lsmod | grep asus" i get the following output:

Code: Select all

$ lsmod | grep asus
asus_nb_wmi            28672  0
asus_wmi               86016  1 asus_nb_wmi
sparse_keymap          12288  1 asus_wmi
platform_profile       12288  1 asus_wmi
ledtrig_audio          12288  2 snd_hda_codec_generic,asus_wmi
rfkill                 40960  8 asus_wmi,bluetooth,cfg80211
video                  77824  5 nvidia_wmi_ec_backlight,asus_wmi,amdgpu,asus_nb_wmi,nvidia_modeset
battery                28672  1 asus_wmi
wmi                    40960  4 video,nvidia_wmi_ec_backlight,asus_wmi,wmi_bmof
Is it safe to asume that the kernel module is loaded already?

dlu2021
Posts: 222
Joined: 2021-08-13 19:55
Location: Minnesota
Has thanked: 8 times
Been thanked: 42 times

Re: Laptop brightness can not be changed on Asus TUF A15 FA506N

#10 Post by dlu2021 »

Yes, looks like it. There were also some Optimus specific things to try in the link to the arch wiki as well that you could try as well.

Raxus
Posts: 10
Joined: 2024-06-06 06:35

Re: Laptop brightness can not be changed on Asus TUF A15 FA506N

#11 Post by Raxus »

dlu2021 wrote: 2024-06-11 14:54 Yes, looks like it. There were also some Optimus specific things to try in the link to the arch wiki as well that you could try as well.
I have tried that as well but did not solve my issue.
I'm starting to fear that my device is one of those 'weird' devices that Hans speaks of in this article:

https://hansdegoede.livejournal.com/26427.html

Dai_trying
Posts: 1110
Joined: 2016-01-07 12:25
Has thanked: 7 times
Been thanked: 19 times

Re: Laptop brightness can not be changed on Asus TUF A15 FA506N

#12 Post by Dai_trying »

On my Asus gaming laptop I installed asusctl to enable things like battery charge levels, fan curves, rgb keyboard etc. I don't know if there is anything to help with the screen brightness but it might be worth looking into.

Raxus
Posts: 10
Joined: 2024-06-06 06:35

Re: Laptop brightness can not be changed on Asus TUF A15 FA506N

#13 Post by Raxus »

Dai_trying wrote: 2024-06-13 07:45 On my Asus gaming laptop I installed asusctl to enable things like battery charge levels, fan curves, rgb keyboard etc. I don't know if there is anything to help with the screen brightness but it might be worth looking into.
Hi, thanks for the reply!

I have tried this by installing Fedora on a different partition, but that also did not solve my issue.

Raxus
Posts: 10
Joined: 2024-06-06 06:35

Re: Laptop brightness can not be changed on Asus TUF A15 FA506N

#14 Post by Raxus »

Hi everyone!

I found an other article online that suggested to use the following kernel parametes:

Code: Select all

acpi_osi=! idle=nomwait quiet splash acpi_backlight=native
And suprisingly, these fixed my problem!


Can anyone explain to me what these parameters do?



Thanks everyone for the help!

Aki
Global Moderator
Global Moderator
Posts: 3232
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 88 times
Been thanked: 427 times

Re: Laptop brightness can not be changed on Asus TUF A15 FA506N

#15 Post by Aki »

Hello,
Raxus wrote: 2024-06-17 10:45 I found an other article online that suggested to use the following kernel parametes:

Code: Select all

acpi_osi=! idle=nomwait quiet splash acpi_backlight=native
And suprisingly, these fixed my problem!
Can anyone explain to me what these parameters do?
You can see here for kernel parameters: Just a guess, but I think the one that probably solves the problem is this:

Code: Select all

        acpi_backlight= [HW,ACPI]
                        { vendor | video | native | none }
                        If set to vendor, prefer vendor-specific driver
                        (e.g. thinkpad_acpi, sony_acpi, etc.) instead
                        of the ACPI video.ko driver.
                        If set to video, use the ACPI video.ko driver.
                        If set to native, use the device's native backlight mode.
                        If set to none, disable the ACPI backlight interface.
I would test if the above parameter is sufficient to solve the problem.

The other parameter maybe involved is:

Code: Select all

        acpi_osi=       [HW,ACPI] Modify list of supported OS interface strings
                        acpi_osi="string1"      # add string1
                        acpi_osi="!string2"     # remove string2
                        acpi_osi=!*             # remove all strings
                        acpi_osi=!              # disable all built-in OS vendor
                                                  strings
                        acpi_osi=!!             # enable all built-in OS vendor
                                                  strings
                        acpi_osi=               # disable all strings

                        'acpi_osi=!' can be used in combination with single or
                        multiple 'acpi_osi="string1"' to support specific OS
                        vendor string(s).  Note that such command can only
                        affect the default state of the OS vendor strings, thus
                        it cannot affect the default state of the feature group
                        strings and the current state of the OS vendor strings,
                        specifying it multiple times through kernel command line
                        is meaningless.  This command is useful when one do not
                        care about the state of the feature group strings which
                        should be controlled by the OSPM.
                        Examples:
                          1. 'acpi_osi=! acpi_osi="Windows 2000"' is equivalent
                             to 'acpi_osi="Windows 2000" acpi_osi=!', they all
                             can make '_OSI("Windows 2000")' TRUE.

                        'acpi_osi=' cannot be used in combination with other
                        'acpi_osi=' command lines, the _OSI method will not
                        exist in the ACPI namespace.  NOTE that such command can
                        only affect the _OSI support state, thus specifying it
                        multiple times through kernel command line is also
                        meaningless.
                        Examples:
                          1. 'acpi_osi=' can make 'CondRefOf(_OSI, Local1)'
                             FALSE.

                        'acpi_osi=!*' can be used in combination with single or
                        multiple 'acpi_osi="string1"' to support specific
                        string(s).  Note that such command can affect the
                        current state of both the OS vendor strings and the
                        feature group strings, thus specifying it multiple times
                        through kernel command line is meaningful.  But it may
                        still not able to affect the final state of a string if
                        there are quirks related to this string.  This command
                        is useful when one want to control the state of the
                        feature group strings to debug BIOS issues related to
                        the OSPM features.
                        Examples:
                          1. 'acpi_osi="Module Device" acpi_osi=!*' can make
                             '_OSI("Module Device")' FALSE.
                          2. 'acpi_osi=!* acpi_osi="Module Device"' can make
                             '_OSI("Module Device")' TRUE.
                          3. 'acpi_osi=! acpi_osi=!* acpi_osi="Windows 2000"' is
                             equivalent to
                             'acpi_osi=!* acpi_osi=! acpi_osi="Windows 2000"'
                             and
                             'acpi_osi=!* acpi_osi="Windows 2000" acpi_osi=!',
                             they all will make '_OSI("Windows 2000")' TRUE.
The "idle", "quiet" and "splash" parameters should not be involved (see previous link for explanation of their usage).
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

Raxus
Posts: 10
Joined: 2024-06-06 06:35

Re: Laptop brightness can not be changed on Asus TUF A15 FA506N

#16 Post by Raxus »

Aki wrote: 2024-06-17 17:28 Hello,
Raxus wrote: 2024-06-17 10:45 I found an other article online that suggested to use the following kernel parametes:

Code: Select all

acpi_osi=! idle=nomwait quiet splash acpi_backlight=native
And suprisingly, these fixed my problem!
Can anyone explain to me what these parameters do?
You can see here for kernel parameters: Just a guess, but I think the one that probably solves the problem is this:

Code: Select all

        acpi_backlight= [HW,ACPI]
                        { vendor | video | native | none }
                        If set to vendor, prefer vendor-specific driver
                        (e.g. thinkpad_acpi, sony_acpi, etc.) instead
                        of the ACPI video.ko driver.
                        If set to video, use the ACPI video.ko driver.
                        If set to native, use the device's native backlight mode.
                        If set to none, disable the ACPI backlight interface.
I would test if the above parameter is sufficient to solve the problem.

The other parameter maybe involved is:

Code: Select all

        acpi_osi=       [HW,ACPI] Modify list of supported OS interface strings
                        acpi_osi="string1"      # add string1
                        acpi_osi="!string2"     # remove string2
                        acpi_osi=!*             # remove all strings
                        acpi_osi=!              # disable all built-in OS vendor
                                                  strings
                        acpi_osi=!!             # enable all built-in OS vendor
                                                  strings
                        acpi_osi=               # disable all strings

                        'acpi_osi=!' can be used in combination with single or
                        multiple 'acpi_osi="string1"' to support specific OS
                        vendor string(s).  Note that such command can only
                        affect the default state of the OS vendor strings, thus
                        it cannot affect the default state of the feature group
                        strings and the current state of the OS vendor strings,
                        specifying it multiple times through kernel command line
                        is meaningless.  This command is useful when one do not
                        care about the state of the feature group strings which
                        should be controlled by the OSPM.
                        Examples:
                          1. 'acpi_osi=! acpi_osi="Windows 2000"' is equivalent
                             to 'acpi_osi="Windows 2000" acpi_osi=!', they all
                             can make '_OSI("Windows 2000")' TRUE.

                        'acpi_osi=' cannot be used in combination with other
                        'acpi_osi=' command lines, the _OSI method will not
                        exist in the ACPI namespace.  NOTE that such command can
                        only affect the _OSI support state, thus specifying it
                        multiple times through kernel command line is also
                        meaningless.
                        Examples:
                          1. 'acpi_osi=' can make 'CondRefOf(_OSI, Local1)'
                             FALSE.

                        'acpi_osi=!*' can be used in combination with single or
                        multiple 'acpi_osi="string1"' to support specific
                        string(s).  Note that such command can affect the
                        current state of both the OS vendor strings and the
                        feature group strings, thus specifying it multiple times
                        through kernel command line is meaningful.  But it may
                        still not able to affect the final state of a string if
                        there are quirks related to this string.  This command
                        is useful when one want to control the state of the
                        feature group strings to debug BIOS issues related to
                        the OSPM features.
                        Examples:
                          1. 'acpi_osi="Module Device" acpi_osi=!*' can make
                             '_OSI("Module Device")' FALSE.
                          2. 'acpi_osi=!* acpi_osi="Module Device"' can make
                             '_OSI("Module Device")' TRUE.
                          3. 'acpi_osi=! acpi_osi=!* acpi_osi="Windows 2000"' is
                             equivalent to
                             'acpi_osi=!* acpi_osi=! acpi_osi="Windows 2000"'
                             and
                             'acpi_osi=!* acpi_osi="Windows 2000" acpi_osi=!',
                             they all will make '_OSI("Windows 2000")' TRUE.
The "idle", "quiet" and "splash" parameters should not be involved (see previous link for explanation of their usage).

Thanks for your reply.

I believe it's the combination of all the ACPI parameters that solved it. Will run a test later today.

Post Reply