How To Increase Brightness On Acer Laptop

[Rodney Liuzzo]

You may want to increase or decrease your screen brightness depending on the lighting conditions where you are using your computer. You may also want to decrease your brightness to save on battery power. Changing screen brightness on Windows 11 is very easy and can be done using several different methods. In this article, we will show you 4 different methods for how to change brightness on Windows 11.

Try 1: Tried Alok's suggestion. It just sits there as a startup application. Doesn't figure as an icon on the topbar of the screen, like the dropbox icon (my dropbox account it is linked to ubuntu) so that I can conveniently change the brightness.

Try 2: Also I must add, that the method System Settings -> Additional Drivers gives an empty list. In my earlier install (which I had to overwrite-reinstall :-(), the list had (I think) Intel Cedarview Graphics Driver. So must I install before trying the methods in any of the answers below?

Temporarily settled myself with this method:

• Pasted the setpci brightness command in a bash file brightness.sh
• Created a .desktop file for the command bash brightness.sh
• Made it an executable file.

Possibly, the second solution posted in this thread applies to your laptop as well: passing the options acpi_osi=Linux acpi_backlight=vendor to grub. Try to edit the line starting with "GRUB_CMDLINE_LINUX" in the file /etc/default/grub to:

The review :"For those of you whos laptop starts up with the screen brighter than the surface of the sun, this one is it. You can easily set this terminal program to stop your eyes from being bleeched by your laptop's screen brightness. Download the app, then go to the system tab, which is the cog shaped thing in the top right corner of your screen. Go to startup applications, and then set the command line to "xbacklight -set 0" (or whatever percentage you want your backlight to snap to on start up) and obviously, remove the quotes from that command. Wallah, that should straighten all of those pesky backlight problems out. Tell your friends, because this one is a keeper"

I've kept this thread bookmarked and I check it from time to time. I finally found a way to solve this problem (for my hardware), so I'm writing this answer for archive and hopefully help someone else.

The problem with the backlight sliding bar that should appear when hitting Fn+Left/Right arrow keys never worked for me except in Windows (I had to install Acer drivers after a fresh reinstall). I've put together something that seems to work using things I found here and in other places.

You can call it anything you like: anything.conf and it must be placed in /etc/init/This job is triggered when the computer is shutting down or rebooting and copies the file /sys/class/backlight/intel_backlight/actual_brightness to /var/backups/actualb (this too can be changed to whatever you like, but on the second job it has to be same).

as the brightness is moving all around, there is directory in /sys/class/backlight giving you semi-direct control of your devices. go to the one with your monitor name and you will find the file brightness. change the value in it...

in some cases linux cant change it on one device, so just go out and into another directory in /sys/class/backlight in order monitor, graphics, Xorg. Do not put values to high, try it gradually thou I would like to know what will happen. Probably kernel panic

I am back to the 32-bit OS! I had accidentally deleted /bin/sh resulting in a booting problem. So I decided to install Ubuntu 12.04 LTS 32-bit OS overwriting the entire 320 GB HDD. All my data is safe, for which I am profusely thankful to Dropbox and my cell phone!

I have made the change but not saved it. Pls check whether it is correct. I am a linux noob and I am afraid if I do something wrong and my laptop crashes, as this is my main laptop and very important for me right now. Thanks for your timely support?.

Everything else looks good.
The reason behind the time out (This will increase your boot time by about ten seconds) is to ensure you can access the Recovery Menu easily if you need to.
If you are freshly migrating to Linux, you may need to access that recovery menu before long and it would be better to have it easily accessible.

What the Timeout does at zero or at five seconds:
When you begin the boot up, a Loading Menu will run. If your timeout is set to 0 seconds, you probably won't even see it. If you set it to five seconds, then it will wait that amount of time before vanishing, for you to make a selection on that menu. You can set it to 7 seconds or ten seconds just as easily...
Some sloths I know set it to 60 seconds. But then, they also keep their monitors hanging upside down, too.
It is during that time that you can also select Recovery Mode or Recovery Menu and having it set to zero can mean you have to be Super Fast with your finger on the Left Shift Key to grab it.

I had a similar problem with my laptop as fn keys did not work!
I installed brightness-controller-git from AUR and solved that problem.
You can also try the command-line tool brightnessctl from manjaro repo as well.

Thank you for your suggestion. I installed brightnessctl from the official repository and it worked on kernel 6.1.49-1 LTS. After the installation, I simply needed to open up a terminal window and type:

It seems that my problem was the open source nvidia drivers. My manjaro installation is currently running on kernel 6.5.0-1, which is the latest one available at the time of writing this. The only downside to this is the closed source drivers. I prefer going full free and open source.

It is closed but none of the answers were satisfactory. I discovered that you can change the brightness on the external monitor by making it the primary display. In >System Preferences > Displays >Arrangement tab - drag the white bar at the top of your primary display over to the external monitor. You can then adjust the brightness on the external display using sliders or keyboard brightness keys. Once you have it as you like you can drag the white bar back to your primary display. No need for an app.

Could it be that it just works in iMacs or with keyboards that are not the integrated ones in laptops? I am using the keyboard that is part of the laptop, I will see if it works with an Apple "magic" keyboard later.

After upgrading to the 3.13 kernel from 3.12 on my laptop, I couldn't control the screen brightness via the function keys anymore as well. Downgrading to 3.12 fixed the problem. The microphone mute is also activated and cannot be de-activated by the function keys with 3.13. (My laptop is a Lenovo X230.)

my acer aspire one d257 lost fn key support for brightness, volume, mute, the numpad, and a couple others in 3.13 as well. Not that it matters, but the whole acpi_backlight=vendor business is deprecated in 3.13 forward. The linux kernel bugtracker has a couple of these problems that I'm following.

No I don't. It seems ibm's are the biggest culprit, but my acer has similar problems. I think they're adding specific models to the dmi table. It makes zero sense to me why acpi_video0 was added to our computers when we only have intel backlight. I'm still working on my bug in the upstream kernel bug-tracker here: _bug.cgi?id=71491

As a work around for folks with function keys not adjusting brightness install xfce4-power-manager
I started using it when I used awesome and if you dont want the system tray icon you can shut it off in the preferences but it allows for fn keys to adjust brightness

While working on my FN volume up/down/mute keys to see if I could map their scancodes to commands manually, I noticed that pressing them produces no events whatsoever. From this, I got the impression that I need to have certain kernel modules loaded for some FN key presses to register. So I looked at this, which mention several modules, the following of which are not loaded on my machine.

I can detect these fn keys in scancode using "showkey --scancodes" in console, but can not detect keycode in neither console(using "showkey --keycodes") or xorg (using "xev grep -A2 --line-buffered '^KeyRelease' sed -n '/keycode /s/^.*keycode \([0-9]*\).* (.*, \(.*\)).*$/\1 \2/p' "). These keycodes were detected before until some recent updates.

Besides for the most crippling issue (backlight), then no, not yet. I don't have the time at the moment to debug this, so I'm waiting and hoping some kind soul who happens to have the solution at hand comes by and shares it.

and tried fn+F5 and fn+F6 (screen backlight up and down); both commands now register key presses. I have rebooted since I last tried, so maybe the reason for the keypresses not being registered before is that I did an upgrade (possibly including a kernel update), and didn't reboot. My kernel version is 3.13.7-1.

Sorry to be so slow in responding. I note from the listings in your first post that you have the i915 module installed. I had the backlight problem you describe on my old Dell D630, with a GM965/GL960 controller, when I upgraded to kernel 3.14; the screen came up at its lowest light level (hurt my old eyes) and the function dim/bright keys were inoperable. I could fix the problem my adding "nomodeset" to my linux "line" in grub, but while the backlight/function-key problem was solved, the screen resolution was ugly and unacceptable. Ploughing through the long list of kernel parameters I came across this

c80f0f1006