Solved Brightness Issue : Max brightness too low in HP Victus

Solved issue

anshuman@linux

New Member
Joined
Jun 2, 2023
Messages
5
Reaction score
0
Credits
37
I am currently using HP Victus with RTX 3050
I tried Kali Linux , Ubuntu , Manjaro , Fedora , Zorin , Pop OS , Vanilla but
I am facing a low brightness issue in all these distros, i.e., the max brightness is very low and the slider is also inverted.
I tried all the things Mentioned in these threads -
but nothing helped. Please help me fix it.
 


....
I am facing a low brightness issue in all these distros, i.e., the max brightness is very low and the slider is also inverted.
... Please help me to fix it.
The xcalib program is able to change brightness and contrast on screens, but I'm not familiar with it's outputs on your machine. Nevertheless the following variables would be among the ones to experiment with:
Code:
-red <gamma> <brightness-percent> <contrast-percent>
-green <gamma> <brightness-percent> <contrast-percent>
-blue <gamma> <brightness-percent> <contrast-percent>

There'll likely be a bit of learning and experiment to see what the program offers for this issue. It's not a "simple" solution like adding a kernel parameter or adjusting a /sys variable, but if it works in this case, it offers a fine grained level of control not often available by other means.
 
Welcome to the forums. Please stop changing distros only for this. Stay with a Linux OS that you are comfortable with for other reasons.

Maybe using "xrandr" could help if it exists in the system. I have an HP2000 which is 11 years old with Sandy Bridge Intel CPU and 4GB RAM.

On my computer:
Code:
[~]$ xrandr
Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192
LVDS-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 344mm x 193mm
   1366x768      60.03*+
   1280x720      60.00    59.99    59.86    59.74  
   1024x768      60.04    60.00  
   960x720       60.00  
   928x696       60.05  
   896x672       60.01  
   1024x576      59.95    59.96    59.90    59.82  
   960x600       59.93    60.00  
   960x540       59.96    59.99    59.63    59.82  
   800x600       60.00    60.32    56.25  
   840x525       60.01    59.88  
   864x486       59.92    59.57  
   700x525       59.98  
   800x450       59.95    59.82  
   640x512       60.02  
   700x450       59.96    59.88  
   640x480       60.00    59.94  
   720x405       59.51    58.99  
   684x384       59.88    59.85  
   640x400       59.88    59.98  
   640x360       59.86    59.83    59.84    59.32  
   512x384       60.00  
   512x288       60.00    59.92  
   480x270       59.63    59.82  
   400x300       60.32    56.34  
   432x243       59.92    59.57  
   320x240       60.05  
   360x202       59.51    59.13  
   320x180       59.84    59.32  
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)

Discover which label listed first says "connected primary" on your computer.

Then do the following command line:

Code:
xrandr --output LVDS-1 --brightness 1.0

Where "output" is the actual label reported on your computer, and the number after "brightness" is from 0.0 to 1.0.

Be careful with this! Might cause a totally black screen and might not be able to see what you're doing. I don't know if this works under Wayland, and a few Linux OS don't come with "xrandr".

If the command works for you, you will have to include it somewhere in the desktop session "startup" routine. I know half to do it on older GNOME but because it offers a GUI option to run a "dot-desktop" file when the desktop is being started.
 
i have tried xrandr method but it's not working

Welcome to the forums. Please stop changing distros only for this. Stay with a Linux OS that you are comfortable with for other reasons.

Maybe using "xrandr" could help if it exists in the system. I have an HP2000 which is 11 years old with Sandy Bridge Intel CPU and 4GB RAM.

On my computer:
Code:
[~]$ xrandr
Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192
LVDS-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 344mm x 193mm
   1366x768      60.03*+
   1280x720      60.00    59.99    59.86    59.74
   1024x768      60.04    60.00
   960x720       60.00
   928x696       60.05
   896x672       60.01
   1024x576      59.95    59.96    59.90    59.82
   960x600       59.93    60.00
   960x540       59.96    59.99    59.63    59.82
   800x600       60.00    60.32    56.25
   840x525       60.01    59.88
   864x486       59.92    59.57
   700x525       59.98
   800x450       59.95    59.82
   640x512       60.02
   700x450       59.96    59.88
   640x480       60.00    59.94
   720x405       59.51    58.99
   684x384       59.88    59.85
   640x400       59.88    59.98
   640x360       59.86    59.83    59.84    59.32
   512x384       60.00
   512x288       60.00    59.92
   480x270       59.63    59.82
   400x300       60.32    56.34
   432x243       59.92    59.57
   320x240       60.05
   360x202       59.51    59.13
   320x180       59.84    59.32
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)

Discover which label listed first says "connected primary" on your computer.

Then do the following command line:

Code:
xrandr --output LVDS-1 --brightness 1.0

Where "output" is the actual label reported on your computer, and the number after "brightness" is from 0.0 to 1.0.

Be careful with this! Might cause a totally black screen and might not be able to see what you're doing. I don't know if this works under Wayland, and a few Linux OS don't come with "xrandr".

If the command works for you, you will have to include it somewhere in the desktop session "startup" routine. I know half to do it on older GNOME but because it offers a GUI option to run a "dot-desktop" file when the desktop is being started.
 
It looks like your laptop hates Linux. o_O

The guy who started the thread in Manjaro forums went really deep trying to fix it and offered a lot of information. This must mean that there are a few computers out there, and their manufacturers who furtively decided to remain in Microsoft's camp. Which is a shame. They should be punished through sales. I have such a computer. Although I could boot into Linux, it requires antics which includes pressing ESC key too many times.

Do you have a separate monitor that you could plug into your computer? Although that might not be acceptable. If that screen is also too dim and resists adjustment then you should consider buying a new computer or reinstalling Windows11 on your computer. You could keep installing Linux distros over other ones but it wouldn't do any good. Because this requires a firmware module or something else in the Linux kernel that properly adjusts the viewport -- privileged information kept by H.P. and by Microsoft.

Wait around a few days. I hope somebody else could help you who knows much more about equipment.
 
Hello, maybe it is too late, maybe it is no help to you at all (I found a workaround on a different linux distribution) but I decided to type this comment anyway. I am new to Linux and in no way am I an expert, I am just sharing my (limited) experience.

I have an old DELL laptop (intel igpu, nvidia dgpu) on which I have installed PopOS and have not faced any issues with screen brightness; I also have an HP Victus 15 laptop with AMD igpu and nvidia 3050 dgpu and faced the same issue you have. Initially I installed PopOS, encountered the backlight issue (inverted controls on both keyboard and controls slider; maximal output too low) and decided to switch and try out debian 12. Following the instructions given in your linked zorin forum thread, I did
Code:
sudo nano /etc/default/grub
and modified the content of the Linux_default lines to either:
Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi_backlight=video"
or
Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi_backlight=vendor"
and, after doing
Code:
sudo update-grub
and rebooting, the screen was very bright, the keyboard controls weren't working and depending on which line I added, the slider in the options was either entirely missing or was present but not affecting the brightness at all.
Afterwards, from the GNOME extension manager, I found and downloaded the Soft Brightness Plus extension (https://github.com/jkitching/soft-brightness-plus), which allowed me to decrease the brightness of my display using the slider and the keyboard shortcuts.

PS: I also installed nvidia drivers and added nvidia-drm.modeset=1 to the grub config file before adding the SBP extension - not sure if this played a role or not in SBP's success.

PS2: Edits for clarity.
 
Last edited:
Hello, maybe it is too late, maybe it is no help to you at all (I found a workaround on a different linux distribution) but I decided to type this comment anyway. I am new to Linux and in no way am I an expert, I am just sharing my (limited) experience.

I have an old DELL laptop (intel igpu, nvidia dgpu) on which I have installed PopOS and have not faced any issues with screen brightness; I also have an HP Victus 15 laptop with AMD igpu and nvidia 3050 dgpu and faced the same issue you have. Initially I installed PopOS, encountered the backlight issue (inverted controls on both keyboard and controls slider; maximal output too low) and decided to switch and try out debian 12. Following the instructions given in your linked zorin forum thread, I did
Code:
sudo nano /etc/default/grub
and modified the content of the Linux_default lines to either:
Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi_backlight=video"
or
Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi_backlight=vendor"
and, after doing
Code:
sudo update-grub
and rebooting, the screen was very bright, the keyboard controls weren't working and depending on which line I added, the slider in the options was either entirely missing or was present but not affecting the brightness at all.
Afterwards, from the GNOME extension manager, I found and downloaded the Soft Brightness Plus extension (https://github.com/jkitching/soft-brightness-plus), which allowed me to decrease the brightness of my display using the slider and the keyboard shortcuts.

PS: I also installed nvidia drivers and added nvidia-drm.modeset=1 to the grub config file before adding the SBP extension - not sure if this played a role or not in SBP's success.

PS2: Edits for clarity.
love you bro , it Worked now i can control Brightness with Brightness slider
 
Hello, maybe it is too late, maybe it is no help to you at all (I found a workaround on a different linux distribution) but I decided to type this comment anyway. I am new to Linux and in no way am I an expert, I am just sharing my (limited) experience.

I have an old DELL laptop (intel igpu, nvidia dgpu) on which I have installed PopOS and have not faced any issues with screen brightness; I also have an HP Victus 15 laptop with AMD igpu and nvidia 3050 dgpu and faced the same issue you have. Initially I installed PopOS, encountered the backlight issue (inverted controls on both keyboard and controls slider; maximal output too low) and decided to switch and try out debian 12. Following the instructions given in your linked zorin forum thread, I did
Code:
sudo nano /etc/default/grub
and modified the content of the Linux_default lines to either:
Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi_backlight=video"
or
Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi_backlight=vendor"
and, after doing
Code:
sudo update-grub
and rebooting, the screen was very bright, the keyboard controls weren't working and depending on which line I added, the slider in the options was either entirely missing or was present but not affecting the brightness at all.
Afterwards, from the GNOME extension manager, I found and downloaded the Soft Brightness Plus extension (https://github.com/jkitching/soft-brightness-plus), which allowed me to decrease the brightness of my display using the slider and the keyboard shortcuts.

PS: I also installed nvidia drivers and added nvidia-drm.modeset=1 to the grub config file before adding the SBP extension - not sure if this played a role or not in SBP's success.

PS2: Edits for clarity.
Bro but the SBP is messing with the display and consuming battery a lot. Does it happen to you?
 

Members online


Top