![brightness control not working windows 7 lenovo brightness control not working windows 7 lenovo](https://i.imgur.com/504N8Uu.png)
I wrote up many of the steps I took in this answer: Ubuntu 15.10: Various "types" of freezes and now unexpected shutdown which solved most my problems on an Intel Ivy Bridge platform and it may very well help your Sky Lake platform.Okay so I was able to fix the problem, and in a very odd way. When I upgrade to Ubuntu 16.04 it brought with it Kernel 16.04 and I had all types of problems with suspend/resume, thin fonts, black screens instead of wallpaper, higher than normal CPU usage and hotter than normal temperatures. I just stumbled across this Ubuntu webpage on brightness keys: Note the BusID should match the output of: lspci -nnk | grep -iA2 vgaĪlso replace intel_backlight above with what appears in lspci command if different.Īnother option to try is change grub command line with acpi_backlight=vendor. Then populate the file with: Section "Device" Then edit the file using: gksu gedit /usr/share/X11//nf The most popular solution is to create the file by typing: sudo touch /usr/share/X11//nf I haven't had problems with brightness keys since 2012 with my older laptop (Toshiba Satellite Core 2 Duo) under Ubuntu 14.04 but it appears many users have. # The redirection into /tmp/log probably doesn't make any differenceĪnd also an equivalent ideapad-monitor-brightness-down file with xdotool key 232 and that solved the problem. However, acpi_listen showed that video/brightnessdown and video/brightnessup events were being generated, so then, after some googling, I put the following in a new file, /etc/acpi/events/ideapad-monitor-brightness-up: # same event as reported by acpi_listenĮvent=video/brightnessup BRTUP 00000086 00000000 KĪction=su vivek -c "export DISPLAY=:0.0 xdotool getactivewindow & xdotool key 233 2>&1 > /tmp/log" However, some weeks later, due to some packages/drivers I changed, xev stopped reporting the XF86 events and so the above method did not work. So I simply used Ubuntu's shortcut manager and registered the two keys (which were read as their XF86 equivalents) to the xdotool commands. Then I tried two things to get the brightness to work.įirst, I noticed that xev now showed me the events XF86MonBrightnessUp and XF86MonBrightnessDown for the two keys, which means everything was working fine at the X level. I first noticed that running xdotool key 232 and xdotool key 233 increased and decreased the brightness perfectly (including the change notification in Unity).
![brightness control not working windows 7 lenovo brightness control not working windows 7 lenovo](https://i.ytimg.com/vi/mVguLBtKF34/maxresdefault.jpg)
The second step was making the keys change the brightness. Setkeycodes e04c 224 # Brightness down -> brightness down Based on that, I put this in my /etc/rc.local/: setkeycodes e054 225 # Brightness up -> brightness up I had a laptop of a similar model (Lenovo Z400) and I looked at what keycodes were generated for it. The first step was making the keys detectable. I finally solved this using a couple of workarounds. Subsystem: Lenovo Skylake Integrated Graphics Root 0xd3, subw 0x0, time 391368, (728,884), root:(793,936),Īdditional outputs: $ lspci -nnk | grep -iA2 vgaĠ0:02.0 VGA compatible controller : Intel Corporation Sky Lake Integrated Graphics (rev 07) KeyRelease event, serial 37, synthetic NO, window 0x3c00001, State 0x0, keycode 120 (keysym 0x0, NoSymbol), same_screen YES, The output is: KeyPress event, serial 37, synthetic NO, window 0x3c00001, Please let me know if someone knows how to fix this and also if any additional information will be useful in debugging this issue.Īdding acpi_osi=Linux acpi_backlight=intel_backlight to the line in grub seems to make the brightness down key generate something in xev (though nothing in acpi_listen yet). Nothing inside Ubuntu seems to be able to detect these keys, so I'm not sure making any changes in the grub config will matter at all.
![brightness control not working windows 7 lenovo brightness control not working windows 7 lenovo](https://techviral.net/wp-content/uploads/2018/10/Enable-Adaptive-Brightness-1.png)
Running echo | sudo tee /sys/class/backlight/intel_backlight/brightness works fine and changes the brightness, and so does changing it from Settings > Brightness and Lock. Running xev also did not give me any output for the brightness up/down keys.Īfter editing the GRUB_CMDLINE_LINUX_DEFAULT line in /etc/default/grub several times with options like acpi_backlight=vendor, e_native_backlight=1, acpi_osi=Linux and acpi_osi=, I can confirm that this changes the soft links in /sys/class/backlight/ and I currently only have intel_backlight there. Running acpi_listen shows me generated events for volume up/down keys, but not for brightness up/down. Unfortunately, the brightness up/down keys don't work. I have a new Lenovo Ideapad 500S with a fresh Ubuntu 16.04.1 running on it.