Brightness keys do not adjust brightness of screen on Lenovo Ideapad Z570. They adjust KDE's OSD and KDE's OSD shows that it is changing the brightness when switching power profiles, but these OSD changes do not indicate any actual change in the screen brightness. Echoing a number from 0-950 to /sys/class/backlight/intel_brightness/brightness as root is the only way I have found to adjust the brightness. This used to work in Fedora. I forgot when it broke. I think it broke some time with Fedora 19 or Fedora 20 although I am just now getting around to reporting it. Version-Release number of selected component (if applicable): I do not know what component this is a bug in (kernel?) $ uname -a Linux localhost.localdomain 3.17.7-300.fc21.x86_64 #1 SMP Wed Dec 17 03:08:44 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux How reproducible: always Additional info: I have tried all the kernel parameters listed here: https://bugzilla.redhat.com/show_bug.cgi?id=1012674#c19 acpi_backlight=vendor changed KDE's OSD so that it would only go down to 90% then immediately jump back to 100%. acpi_osi=Linux disabled the OSD. All other options had no effect. I also tried booting without the load_video line in GRUB. I boot with UEFI. $ ls -l /sys/class/backlight/ total 0 lrwxrwxrwx. 1 root root 0 Jan 29 00:04 acpi_video0 -> ../../devices/pci0000:00/0000:00:02.0/backlight/acpi_video0 lrwxrwxrwx. 1 root root 0 Jan 29 00:04 intel_backlight -> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1/intel_backlight $ ls -l /sys/class/backlight/intel_backlight/ total 0 -r--r--r--. 1 root root 4096 Jan 29 00:22 actual_brightness -rw-r--r--. 1 root root 4096 Jan 29 00:22 bl_power -rw-r--r--. 1 root root 4096 Jan 29 00:05 brightness lrwxrwxrwx. 1 root root 0 Jan 29 00:22 device -> ../../card0-LVDS-1 -r--r--r--. 1 root root 4096 Jan 29 00:04 max_brightness drwxr-xr-x. 2 root root 0 Jan 29 00:22 power lrwxrwxrwx. 1 root root 0 Jan 29 00:04 subsystem -> ../../../../../../../class/backlight -r--r--r--. 1 root root 4096 Jan 29 00:04 type -rw-r--r--. 1 root root 4096 Jan 29 00:03 uevent $ ls -l /sys/class/backlight/acpi_video0/ total 0 -r--r--r--. 1 root root 4096 Jan 29 00:22 actual_brightness -rw-r--r--. 1 root root 4096 Jan 29 00:04 bl_power -rw-r--r--. 1 root root 4096 Jan 29 00:04 brightness lrwxrwxrwx. 1 root root 0 Jan 29 00:22 device -> ../../../0000:00:02.0 -r--r--r--. 1 root root 4096 Jan 29 00:04 max_brightness drwxr-xr-x. 2 root root 0 Jan 29 00:22 power lrwxrwxrwx. 1 root root 0 Jan 29 00:04 subsystem -> ../../../../../class/backlight -r--r--r--. 1 root root 4096 Jan 29 00:04 type -rw-r--r--. 1 root root 4096 Jan 29 00:03 uevent # echo 500 > /sys/class/backlight/acpi_video0/brightness bash: echo: write error: Invalid argument # echo 500 > /sys/class/backlight/intel_backlight/brightness This actually changes the screen brightness. $ grep '.*' /sys/class/dmi/id/*_* 2> /dev/null /sys/class/dmi/id/bios_date:05/12/2011 /sys/class/dmi/id/bios_vendor:LENOVO /sys/class/dmi/id/bios_version:45CN34WW /sys/class/dmi/id/board_asset_tag:Base Board Asset Tag /sys/class/dmi/id/board_name:Emerald Lake /sys/class/dmi/id/board_vendor:LENOVO /sys/class/dmi/id/board_version:FAB1 /sys/class/dmi/id/chassis_asset_tag:Asset Tag /sys/class/dmi/id/chassis_type:10 /sys/class/dmi/id/chassis_vendor:LENOVO /sys/class/dmi/id/chassis_version:0.1 /sys/class/dmi/id/product_name:102434U /sys/class/dmi/id/product_version:Ideapad Z570 /sys/class/dmi/id/sys_vendor:LENOVO $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.17.7-300.fc21.x86_64 root=/dev/mapper/luks-7dcc71a4-9af0-467b-8269-b90e85361b7d ro rd.lvm.lv=fedora/swap rd.luks.uuid=luks-8bef245b-125a-42f7-8334-7d67ee2b1c18 rd.luks.uuid=luks-3956feaa-88b4-40d3-8e48-552b02e38b62 rd.lvm.lv=fedora/Fedora19 rd.luks.uuid=luks-7dcc71a4-9af0-467b-8269-b90e85361b7d threadirq # grep -i acpi /var/log/messages Jan 29 00:04:35 localhost kernel: [ 0.000000] BIOS-e820: [mem 0x000000000008f000-0x000000000008ffff] ACPI NVS Jan 29 00:04:35 localhost kernel: [ 0.000000] BIOS-e820: [mem 0x00000000bae51000-0x00000000bae70fff] ACPI NVS Jan 29 00:04:35 localhost kernel: [ 0.000000] BIOS-e820: [mem 0x00000000baf1f000-0x00000000baf9efff] ACPI NVS Jan 29 00:04:35 localhost kernel: [ 0.000000] BIOS-e820: [mem 0x00000000baf9f000-0x00000000baffefff] ACPI data Jan 29 00:04:35 localhost kernel: [ 0.000000] reserve setup_data: [mem 0x000000000008f000-0x000000000008ffff] ACPI NVS Jan 29 00:04:35 localhost kernel: [ 0.000000] reserve setup_data: [mem 0x00000000bae51000-0x00000000bae70fff] ACPI NVS Jan 29 00:04:35 localhost kernel: [ 0.000000] reserve setup_data: [mem 0x00000000baf1f000-0x00000000baf9efff] ACPI NVS Jan 29 00:04:35 localhost kernel: [ 0.000000] reserve setup_data: [mem 0x00000000baf9f000-0x00000000baffefff] ACPI data Jan 29 00:04:35 localhost kernel: [ 0.000000] efi: ACPI=0xbaffe000 ACPI 2.0=0xbaffe014 SMBIOS=0xbae2f000 Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: Early table checksum verification disabled Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: RSDP 0x00000000BAFFE014 000024 (v02 LENOVO) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: XSDT 0x00000000BAFFE120 000084 (v01 LENOVO CB-01 00000001 LENO 00000001) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: FACP 0x00000000BAFEE000 0000F4 (v03 LENOVO CB-01 00000001 PTL 00000001) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: DSDT 0x00000000BAFF1000 009B3E (v02 LENOVO SNB-CPT 00000000 INTL 20061109) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: FACS 0x00000000BAF3E000 000040 Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: SLIC 0x00000000BAFFD000 000176 (v01 LENOVO CB-01 00000001 LENO 00000001) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: SSDT 0x00000000BAFFB000 001068 (v01 LENOVO PtidDevc 00001000 INTL 20061109) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: ASF! 0x00000000BAFF0000 0000A5 (v32 LENOVO CB-01 00000001 PTL 00000001) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: HPET 0x00000000BAFED000 000038 (v01 LENOVO CB-01 00000001 PTL 00000001) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: APIC 0x00000000BAFEC000 000098 (v01 LENOVO CB-01 00000001 PTL 00000001) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: MCFG 0x00000000BAFEB000 00003C (v01 LENOVO CB-01 00000001 PTL 00000001) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: SSDT 0x00000000BAFEA000 000780 (v01 PmRef Cpu0Ist 00003000 INTL 20061109) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: SSDT 0x00000000BAFE9000 000996 (v01 PmRef CpuPm 00003000 INTL 20061109) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: UEFI 0x00000000BAFE8000 00003E (v01 LENOVO CB-01 00000001 PTL 00000001) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: UEFI 0x00000000BAFE7000 000042 (v01 PTL COMBUF 00000001 PTL 00000001) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: UEFI 0x00000000BAFE6000 000256 (v01 LENOVO CB-01 00000001 PTL 00000001) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: PM-Timer IO Port: 0x408 Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x00] disabled) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x00] disabled) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x00] disabled) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x00] disabled) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Jan 29 00:04:35 localhost kernel: [ 0.000000] Using ACPI (MADT) for SMP configuration information Jan 29 00:04:35 localhost kernel: [ 0.000000] ACPI: HPET id: 0x8086a301 base: 0xfed00000 Jan 29 00:04:35 localhost kernel: [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.17.7-300.fc21.x86_64 root=/dev/mapper/luks-7dcc71a4-9af0-467b-8269-b90e85361b7d ro rd.lvm.lv=fedora/swap rd.luks.uuid=luks-8bef245b-125a-42f7-8334-7d67ee2b1c18 rd.luks.uuid=luks-3956feaa-88b4-40d3-8e48-552b02e38b62 rd.lvm.lv=fedora/Fedora19 rd.luks.uuid=luks-7dcc71a4-9af0-467b-8269-b90e85361b7d threadirq "acpi_osi=!Windows 2012" Jan 29 00:04:35 localhost kernel: [ 0.000051] ACPI: Core revision 20140724 Jan 29 00:04:35 localhost kernel: [ 0.008142] ACPI: All ACPI Tables successfully acquired Jan 29 00:04:35 localhost kernel: [ 0.087647] PM: Registering ACPI NVS region [mem 0x0008f000-0x0008ffff] (4096 bytes) Jan 29 00:04:35 localhost kernel: [ 0.087651] PM: Registering ACPI NVS region [mem 0xbae51000-0xbae70fff] (131072 bytes) Jan 29 00:04:35 localhost kernel: [ 0.087655] PM: Registering ACPI NVS region [mem 0xbaf1f000-0xbaf9efff] (524288 bytes) Jan 29 00:04:35 localhost kernel: [ 0.088938] ACPI: bus type PCI registered Jan 29 00:04:35 localhost kernel: [ 0.088940] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 Jan 29 00:04:35 localhost kernel: [ 0.093001] ACPI: Added _OSI(Module Device) Jan 29 00:04:35 localhost kernel: [ 0.093005] ACPI: Added _OSI(Processor Device) Jan 29 00:04:35 localhost kernel: [ 0.093007] ACPI: Added _OSI(3.0 _SCP Extensions) Jan 29 00:04:35 localhost kernel: [ 0.093009] ACPI: Added _OSI(Processor Aggregator Device) Jan 29 00:04:35 localhost kernel: [ 0.093012] ACPI: Deleted _OSI(Windows 2012) Jan 29 00:04:35 localhost kernel: [ 0.095635] ACPI: Executed 1 blocks of module-level executable AML code Jan 29 00:04:35 localhost kernel: [ 0.100715] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored Jan 29 00:04:35 localhost kernel: [ 0.101015] ACPI: Dynamic OEM Table Load: Jan 29 00:04:35 localhost kernel: [ 0.101025] ACPI: SSDT 0xFFFF8801396E2000 00067C (v01 PmRef Cpu0Cst 00003001 INTL 20061109) Jan 29 00:04:35 localhost kernel: [ 0.103852] ACPI: Dynamic OEM Table Load: Jan 29 00:04:35 localhost kernel: [ 0.103859] ACPI: SSDT 0xFFFF88013971A000 000303 (v01 PmRef ApIst 00003000 INTL 20061109) Jan 29 00:04:35 localhost kernel: [ 0.106746] ACPI: Dynamic OEM Table Load: Jan 29 00:04:35 localhost kernel: [ 0.106753] ACPI: SSDT 0xFFFF880139741000 000119 (v01 PmRef ApCst 00003000 INTL 20061109) Jan 29 00:04:35 localhost kernel: [ 0.112246] ACPI: Interpreter enabled Jan 29 00:04:35 localhost kernel: [ 0.112259] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140724/hwxface-580) Jan 29 00:04:35 localhost kernel: [ 0.112274] ACPI: (supports S0 S1 S3 S4 S5) Jan 29 00:04:35 localhost kernel: [ 0.112277] ACPI: Using IOAPIC for interrupt routing Jan 29 00:04:35 localhost kernel: [ 0.112670] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in ACPI motherboard resources Jan 29 00:04:35 localhost kernel: [ 0.112784] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug Jan 29 00:04:35 localhost kernel: [ 0.118656] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e]) Jan 29 00:04:35 localhost kernel: [ 0.118663] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] Jan 29 00:04:35 localhost kernel: [ 0.118702] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM Jan 29 00:04:35 localhost kernel: [ 0.119972] pci 0000:00:1a.0: System wakeup disabled by ACPI Jan 29 00:04:35 localhost kernel: [ 0.120160] pci 0000:00:1b.0: System wakeup disabled by ACPI Jan 29 00:04:35 localhost kernel: [ 0.120328] pci 0000:00:1c.0: System wakeup disabled by ACPI Jan 29 00:04:35 localhost kernel: [ 0.120496] pci 0000:00:1c.1: System wakeup disabled by ACPI Jan 29 00:04:35 localhost kernel: [ 0.120674] pci 0000:00:1c.3: System wakeup disabled by ACPI Jan 29 00:04:35 localhost kernel: [ 0.120894] pci 0000:00:1d.0: System wakeup disabled by ACPI Jan 29 00:04:35 localhost kernel: [ 0.122865] pci 0000:02:00.0: System wakeup disabled by ACPI Jan 29 00:04:35 localhost kernel: [ 0.125762] pci 0000:03:00.0: System wakeup disabled by ACPI Jan 29 00:04:35 localhost kernel: [ 0.128279] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 10 *11 12 14 15) Jan 29 00:04:35 localhost kernel: [ 0.128332] ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled. Jan 29 00:04:35 localhost kernel: [ 0.128383] ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled. Jan 29 00:04:35 localhost kernel: [ 0.128433] ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled. Jan 29 00:04:35 localhost kernel: [ 0.128482] ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled. Jan 29 00:04:35 localhost kernel: [ 0.128532] ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled. Jan 29 00:04:35 localhost kernel: [ 0.128582] ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled. Jan 29 00:04:35 localhost kernel: [ 0.128635] ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled. Jan 29 00:04:35 localhost kernel: [ 0.128775] ACPI: Enabled 3 GPEs in block 00 to 3F Jan 29 00:04:35 localhost kernel: [ 0.128826] ACPI : EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62 Jan 29 00:04:35 localhost kernel: [ 0.129109] ACPI: bus type USB registered Jan 29 00:04:35 localhost kernel: [ 0.129285] PCI: Using ACPI for IRQ routing Jan 29 00:04:35 localhost kernel: [ 0.139499] pnp: PnP ACPI init Jan 29 00:04:35 localhost kernel: [ 0.140201] pnp: PnP ACPI: found 7 devices Jan 29 00:04:35 localhost kernel: [ 0.468136] ACPI: AC Adapter [ADP1] (on-line) Jan 29 00:04:35 localhost kernel: [ 0.468328] ACPI: Lid Switch [LID0] Jan 29 00:04:35 localhost kernel: [ 0.468416] ACPI: Sleep Button [SLPB] Jan 29 00:04:35 localhost kernel: [ 0.468497] ACPI: Power Button [PWRF] Jan 29 00:04:35 localhost kernel: [ 0.470504] ACPI: Thermal Zone [TZS0] (60 C) Jan 29 00:04:35 localhost kernel: [ 0.470721] ACPI: Thermal Zone [TZS1] (41 C) Jan 29 00:04:35 localhost kernel: [ 0.471586] ACPI: Battery Slot [BAT0] (battery present) Jan 29 00:04:35 localhost kernel: [ 3.358847] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) Jan 29 00:04:35 localhost kernel: [ 3.361380] acpi device:3e: registered as cooling_device4 Jan 29 00:04:35 localhost kernel: [ 22.623256] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000047f (\PMIO) (20140724/utaddress-258) Jan 29 00:04:35 localhost kernel: [ 22.628249] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jan 29 00:04:35 localhost kernel: [ 22.630477] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140724/utaddress-258) Jan 29 00:04:35 localhost kernel: [ 22.634824] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jan 29 00:04:35 localhost kernel: [ 22.636982] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140724/utaddress-258) Jan 29 00:04:35 localhost kernel: [ 22.641905] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jan 29 00:04:35 localhost kernel: [ 22.645269] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140724/utaddress-258) Jan 29 00:04:35 localhost kernel: [ 22.650997] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jan 29 00:04:35 localhost kernel: [ 22.826570] ACPI Warning: SystemIO range 0x000000000000efa0-0x000000000000efbf conflicts with OpRegion 0x000000000000efa0-0x000000000000efaf (\_SB_.PCI0.SBUS.SMBI) (20140724/utaddress-258) Jan 29 00:04:35 localhost kernel: [ 22.830236] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jan 29 00:04:35 localhost kernel: [ 24.199952] acer_wmi: Acer Laptop ACPI-WMI Extras Jan 29 00:04:35 localhost kernel: [ 24.216382] acer_wmi: Brightness must be controlled by acpi video driver Jan 29 00:03:29 localhost systemd: Stopping Load/Save Screen Backlight Brightness of backlight:acpi_video0... Jan 29 00:03:29 localhost systemd: Stopped Load/Save Screen Backlight Brightness of backlight:acpi_video0. Jan 29 00:04:28 localhost kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000047f (\PMIO) (20140724/utaddress-258) Jan 29 00:04:28 localhost kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jan 29 00:04:28 localhost kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140724/utaddress-258) Jan 29 00:04:28 localhost kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jan 29 00:04:28 localhost kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140724/utaddress-258) Jan 29 00:04:28 localhost kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jan 29 00:04:28 localhost kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140724/utaddress-258) Jan 29 00:04:28 localhost kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jan 29 00:04:28 localhost kernel: ACPI Warning: SystemIO range 0x000000000000efa0-0x000000000000efbf conflicts with OpRegion 0x000000000000efa0-0x000000000000efaf (\_SB_.PCI0.SBUS.SMBI) (20140724/utaddress-258) Jan 29 00:04:28 localhost kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jan 29 00:04:28 localhost kernel: acer_wmi: Acer Laptop ACPI-WMI Extras Jan 29 00:04:28 localhost kernel: acer_wmi: Brightness must be controlled by acpi video driver
Created attachment 988090 [details] Proposed patch fixing this
Hi, Thanks for the bug report. I've started a kernel scratch-build with a patch added which should fix this. Please download the following rpms: kernel-3.17.8-...rpm kernel-core-3.17.8-...rpm kernel-modules-3.17.8-...rpm For your arch from here: http://koji.fedoraproject.org/koji/taskinfo?taskID=8818095 (note this is still building atm) Save them all to the same directory (which should not contain other rpms) and do: sudo rpm -ivh kernel-*.rpm From within that directory. And then boot into the new kernel and check if the backlight works as expected. Regards, Hans
Nope, that did not fix the issue. :/ Now the OSD will immediately jump back to 100% when I try to decrease the brightness, like when using the kernel argument acpi_backlight=vendor before. Echoing to /sys/class/backlight/intel_backlight/brightness still works. There is now an 'ideapad' directory instead of 'acpi_video0' in /sys/class/backlight. Echoing to /sys/class/backlight/acpi_video0/brightness prints the same error (bash: echo: write error: Invalid argument). # ls -l /sys/class/backlight/ total 0 lrwxrwxrwx. 1 root root 0 Feb 4 18:47 ideapad -> ../../devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC2004:00/backlight/ideapad lrwxrwxrwx. 1 root root 0 Feb 4 18:47 intel_backlight -> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1/intel_backlight
Ugh, so with me getting the acer-wmi driver out of the way, the ideapad sees its chance to register its own backlight deivce, great (not). Can you try creating a /etc/modprobe.d/ideapad.conf with the following in there: blacklist ideapad-laptop And then reboot? This may cause you to loose some functionality of certain Fn + Function-Key key-combinations, but it should get your backlight to work, which will show that we're on the right track, once that is confirmed I need to rethink this.
That fixes it. :) I tried booting into 3.18.3-201.fc21.x86_64 with ideapad-laptop blacklisted and it works as well, so the patch you attached above is unnecessary. Function and volume keys all still work.
(In reply to Be from comment #5) > That fixes it. :) I tried booting into 3.18.3-201.fc21.x86_64 with > ideapad-laptop blacklisted and it works as well, so the patch you attached > above is unnecessary. Function and volume keys all still work. acpi_video0 is no longer present with 3.18.3-201.fc21.x86_64 with ideapad-laptop blacklisted: $ ls -l /sys/class/backlight/ total 0 lrwxrwxrwx. 1 root root 0 Feb 5 10:50 intel_backlight -> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1/intel_backlight
So should the ideapad-laptop kernel module be modified to prevent loading for Lenovo Z570?
Hi, So I've done a new set of patches which should really fix this. Please download the following rpms: kernel-3.18.8-...rpm kernel-core-3.18.8-...rpm kernel-modules-3.18.8-...rpm For your arch from here: http://koji.fedoraproject.org/koji/taskinfo?taskID=9129619 (note this is still building atm) Save them all to the same directory (which should not contain other rpms) and do: sudo rpm -ivh kernel-*.rpm From within that directory. Then mv /etc/modprobe.d/ideapad.conf to your home dir (so that it is no longer used), and then boot into the new kernel and check if the backlight works as expected. Thanks & Regards, Hans
Nope, still doesn't work without ideapad module blacklisted.
# uname -r 3.18.8-201.rhbz1187004.fc21.x86_64 # ls -l /sys/class/backlight/ total 0 lrwxrwxrwx. 1 root root 0 Mar 3 20:39 ideapad -> ../../devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC2004:00/backlight/ideapad lrwxrwxrwx. 1 root root 0 Mar 3 20:38 intel_backlight -> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1/intel_backlight
Hi, Ah, it took me a while, but this is caused by this recent(ish) commit, which (sorta) conflicts with my patches: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a11d342f Which suggests that the ideapad backlight interface should actually work ... can you try poking the brightness file directly in sysfs and see if this works or not (with the 3.18.8 kernel I build) ? Regards, Hans
# uname -r 3.18.8-201.rhbz1187004.fc21.x86_64 # echo 100 > /sys/class/backlight/ideapad/brightness bash: echo: write error: Invalid argument # echo 100 > /sys/class/backlight/intel_backlight/brightness # works
Hi, (In reply to Be from comment #12) > # uname -r > 3.18.8-201.rhbz1187004.fc21.x86_64 > # echo 100 > /sys/class/backlight/ideapad/brightness > bash: echo: write error: Invalid argument Hmm, firmware interfaces typically may have a different range, try doing a "cat max_brightness" first and then writing values in the range of 0 - max_brightness. Regards, Hans
max_brightness for ideapad is 10. I tried echoing values from 0 to 10 to brightness for ideapad. KDE's OSD popped up and showed the brightness was 10x whatever I echoed to brightness (that is, the OSD showed 20% when I echoed 2). However, this did not actually affect the backlight. Only echoing to intel_backlight/brightness changed the backlight (but not KDE's OSD).
(In reply to Be from comment #14) > max_brightness for ideapad is 10. I tried echoing values from 0 to 10 to > brightness for ideapad. KDE's OSD popped up and showed the brightness was > 10x whatever I echoed to brightness (that is, the OSD showed 20% when I > echoed 2). However, this did not actually affect the backlight. Only echoing > to intel_backlight/brightness changed the backlight (but not KDE's OSD). Ok, thanks for testing I'll send a mail to the author of the commit which somewhat conflicts with my fix: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a11d342f And I'll put you in the Cc, and then we'll go from there.
Hi, So I've done a new set of patches which should really really fix this. Please download the following rpms: kernel-3.19.1-...rpm kernel-core-3.19.1-...rpm kernel-modules-3.19.1-...rpm For your arch from here: http://koji.fedoraproject.org/koji/taskinfo?taskID=9273358 (note this is still building atm) Save them all to the same directory (which should not contain other rpms) and do: sudo rpm -ivh kernel-*.rpm From within that directory. Then mv /etc/modprobe.d/ideapad.conf to your home dir (so that it is no longer used), and then boot into the new kernel and check if the backlight works as expected. Thanks & Regards, Hans
That works, thanks. Volume keys still work too. intel_backlight is the only symlink in /sys/class/backlight
Created attachment 1004363 [details] [PATCH 1/2] acpi: video: Allow forcing native backlight on non win8 machines
Created attachment 1004364 [details] [PATCH 2/2] acpi: video: Add force native backlight quirk for Lenovo Ideapad Z570
Hi, (In reply to Be from comment #17) > That works, thanks. Volume keys still work too. intel_backlight is the only > symlink in /sys/class/backlight Good thanks for testing this. Josh can you please add the 2 patches which I've just attached to the Fedora kernel builds to fix this until the fixes trickle down through upstream ? The first (preperation) patch is already queued up upstream, the second patch I've just send upstream this morning. Thanks & Regards, Hans
Added, thanks!
kernel-3.19.2-201.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/FEDORA-2015-4457/kernel-3.19.2-201.fc21
kernel-4.0.0-0.rc5.git1.3.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/kernel-4.0.0-0.rc5.git1.3.fc22
Package kernel-3.19.2-201.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.19.2-201.fc21' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-4457/kernel-3.19.2-201.fc21 then log in and leave karma (feedback).
Without blacklisting ideapad_laptop with kernel-3.19.2-200.fc21.x86_64, both ideapad and intel_backlight appear in /sys/class/backlight. Upon boot, the backlight state is restored to where it was, but I still cannot change the brightness with the brightness keys. KDE's OSD shows that the brightness is at 100%. When I try to turn it down, the OSD goes down to 90 then jumps back to 100.
kernel-3.19.3-100.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/kernel-3.19.3-100.fc20
kernel-3.19.2-201.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
kernel-3.19.3-100.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.