DEV Community: Saramsh Shrestha

Fix brightness not working in linux | Gamming laptop | AMD + nVidia (hybrid gpu).

Saramsh Shrestha — Thu, 17 Jul 2025 14:50:44 +0000

There was a moment in your life that you want to make a switch to linux but no matter which kernal or distro you used. Brightness sliders does not work properly. I was facing the same issue too. I have fixed this issues after few hours of debugging and now you can too without loosing hours or days.

My config:

Laptop: Asus TUF A15, Ryzen 6800HS with RTX2050

OS: Fedora 42 KDE

Steps 1: Check what controller your display backlight is using.

ls /sys/class/backlight

//output
nvidia_wmi_ec_backlight

You can have other output: intel_backlight, acpi_video0 or nvidia_wmi_ec_backlight.

Step 2: Lets first identify you GPUs first.

lspci | grep -E "VGA|3D"

//output
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 2050] (rev a1)

05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 6
80M] (rev c8)

I have AMD Radeon build in and Nvidia graphics. My screen backlight is controlled by AMD Radeon graphics so I have to change the backlight controller. This is done by changing the GRUB Configuration.

Step 3: Lets modify the GRUB config.

sudo nano /etc/default/grub

// Search and Replace this config
GRUB_CMDLINE_LINUX="rhgb quiet acpi_backlight=native amdgpu.backlight=0 nvidia-drm.modeset=1"

You can see I have change the config based on my internal GPU as its AMD. You can this based on you config.

// First Try This:
GRUB_CMDLINE_LINUX="quiet splash acpi_backlight=native"

// Second Try This:
GRUB_CMDLINE_LINUX="quiet splash acpi_backlight=vendor"

// These are final options to force use built in graphics

// For intel forced intel builtin graphics
GRUB_CMDLINE_LINUX="quiet splash acpi_backlight=native i915.enable_dpcd_backlight=1"

// For Intel Nvidia Hybrid
GRUB_CMDLINE_LINUX="quiet splash acpi_backlight=vendor nvidia.NVreg_EnableBacklightHandler=1"

You should try multiple times which one works for you.

Step 4: Save the config and reboot.

sudo update-grub       # Ubuntu/Debian
sudo grub2-mkconfig -o /boot/grub2/grub.cfg   # Fedora/RHEL

// For Reboot
reboot

You should apply appropriate command to update the GRUB then reboot the system.

Try each config until one works for you. Then each iteration that correct backlight drivers are used.

ls /sys/class/backlight

//output
amdgpu_bl2

Mine is changed from nvidia_wmi_ec_backlight to amdgpu_b12. Now my laptop display brightness slider is working fine.

You can use tools like brightnessctl and xrand if they works out for you. Sometimes they might work any config.

Increase your Code Quality “Blazing Fast”

Saramsh Shrestha — Fri, 04 Nov 2022 14:10:29 +0000

I have been coding for the past 2 yrs and these are some simple things I have observed to increase readability “blazing fast”. Code readability increases maintainability and code quality.

1. Decrease the Code Size

We have all been through some code where we have to scroll to the infinite to find that one function. So to avoid that keep your code between 100–500 lines of code per file. Split the file into multiple files and separate the files into their proper directory and filename. Any code with more than 500 lines is really hard to read, scroll and understand.

Split the files and keep 100–500 lines of code per file.

2. Name Variables Properly

There is no strict rule for naming a variable but there are some most used methods for consistency. Make functions, classes, constants, and Interface properly based on functionality.

Don’t name variables like (a,b, i, j,k, one, s1, p1) or something similar, and use camelCase for variable names compose of multiple words.

For Constants: Use all uppercase names.

const DATABASE = "ANIME";
const _USERNAME = "BLEACH";
const PASSWORD_FOR_BLEACH = "RANGIKU";

For Interface: The interface name starts with I (for interface).

interface IShape {
    area: number
}

For Classes: Class names should start with a capital letter. I use the same method for functions that are exported.

class Shape extends IShape {
    //...
}

export function GetAll() {
    //...
}

Keep variable’s name meaningful and consistent.

3. DRY (Do Not Repeat Yourself)

Programming at its core is to solve repetitive problems. Reduce the copy paste past as much as possible. “Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.” We can achieve DRY by creating functions and classes to make sure that any logic should be written in only one place.

Do not repeat yourself, use functions or classes to reduce code repetition.

4. KISS (Keep It Simple, Stupid)

A simple design makes service and maintenance a lot easier. Try not to make the code any more complex than necessary.

Keep your code as simple as possible.

5. Be Empathetic

Try to write the code from the maintainer's point of view. We should help each other out by increasing the code by making it better than you found.

Contribute to making code better than you found it.

6. Comments.

Good code is code that does not need any documentation. Try not to comment everywhere and let the variable names and function names document themselves but there are exceptions. Add comments for places where it’s complex to understand. Better Comments Extension can help on this one.

Less amount of comments the better.

7. Use Prettier or Code Formatter’s.

Consistently using the same style throughout your code makes it easier to read. Code that is easy to read is easier to understand by you as well as by potential collaborators. Therefore, adhering to a coding style reduces the risk of mistakes and makes it easier to work together on software.

Use code formatter.

Using a readme.md file to add more detail about your project is a really good way to increase the maintainability of the code.

Want to learn more

Learn more about SOLID design principles and the book clean code by uncle bob.

Article on SOLID Principles: [https://blog.bitsrc.io/solid-principles-in-typescript-153e6923ffdb]