Installing kernel modules

Now for my next task at getting manjaro to fully work. I don't have a keyboard backlight on my asus rog ga502du. I have read through this entire post linked below

https://forum.manjaro.org/t/asus-rog-gl504g-keyboard-back-light/82789/38

I have also read this post as well https://wiki.archlinux.org/index.php/ASUS_GL702ZC#Backlight
and done all of the instructions on getting keyboard backlight to work except I am missing the 2 modules it has listed. amdgpu_bl0 , and asus::kbd_backlight

I have also installed

https://www.archlinux.org/packages/community/x86_64/brightnessctl/

The question is how do I install the 2 modules that the arch wiki says I need. I think that may be the missing piece to this puzzle. When I run brighnessctl it only lists my screen backlight currently. My currently kernel version is 5.2.11-1-MANJARO running the latest release of xfce minimal install via architect.

post output

ls -la /sys/class/leds
lsmod | grep -Ei 'asus|kbd|laptop|wmi'

have you tried the asus-kbd-backlight package in the AUR ?

> ls -la /sys/class/leds                                                   
> total 0
> drwxr-xr-x  2 root root 0 Oct  8 05:37 .
> drwxr-xr-x 58 root root 0 Oct  8 05:37 ..
> lrwxrwxrwx  1 root root 0 Oct  8 12:37 asus::lightbar -> ../../devices/platform/asus-nb-wmi/leds/asus::lightbar
> lrwxrwxrwx  1 root root 0 Oct  8 12:37 asus-wireless::airplane -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/leds/asus-wireless::airplane
> lrwxrwxrwx  1 root root 0 Oct  8 19:36 input14::capslock -> ../../devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb3/3-1/3-1:1.0/0003:0B05:1866.0002/input/input14/input14::capslock
> lrwxrwxrwx  1 root root 0 Oct  8 19:36 input14::compose -> ../../devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb3/3-1/3-1:1.0/0003:0B05:1866.0002/input/input14/input14::compose
> lrwxrwxrwx  1 root root 0 Oct  8 19:36 input14::kana -> ../../devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb3/3-1/3-1:1.0/0003:0B05:1866.0002/input/input14/input14::kana
> lrwxrwxrwx  1 root root 0 Oct  8 19:36 input14::numlock -> ../../devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb3/3-1/3-1:1.0/0003:0B05:1866.0002/input/input14/input14::numlock
> lrwxrwxrwx  1 root root 0 Oct  8 19:36 input14::scrolllock -> ../../devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb3/3-1/3-1:1.0/0003:0B05:1866.0002/input/input14/input14::scrolllock
> lrwxrwxrwx  1 root root 0 Oct  8 19:36 input15::capslock -> ../../devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb3/3-1/3-1:1.1/0003:0B05:1866.0003/input/input15/input15::capslock
> lrwxrwxrwx  1 root root 0 Oct  8 19:36 input15::compose -> ../../devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb3/3-1/3-1:1.1/0003:0B05:1866.0003/input/input15/input15::compose
> lrwxrwxrwx  1 root root 0 Oct  8 19:36 input15::kana -> ../../devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb3/3-1/3-1:1.1/0003:0B05:1866.0003/input/input15/input15::kana
> lrwxrwxrwx  1 root root 0 Oct  8 19:36 input15::numlock -> ../../devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb3/3-1/3-1:1.1/0003:0B05:1866.0003/input/input15/input15::numlock
> lrwxrwxrwx  1 root root 0 Oct  8 19:36 input15::scrolllock -> ../../devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb3/3-1/3-1:1.1/0003:0B05:1866.0003/input/input15/input15::scrolllock
> lrwxrwxrwx  1 root root 0 Oct  8 19:36 input20::capslock -> ../../devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb3/3-2/3-2:1.0/0003:045E:07B2.0005/input/input20/input20::capslock
> lrwxrwxrwx  1 root root 0 Oct  8 19:36 input20::numlock -> ../../devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb3/3-2/3-2:1.0/0003:045E:07B2.0005/input/input20/input20::numlock
> lrwxrwxrwx  1 root root 0 Oct  8 19:36 input20::scrolllock -> ../../devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb3/3-2/3-2:1.0/0003:045E:07B2.0005/input/input20/input20::scrolllock
> lrwxrwxrwx  1 root root 0 Oct  8 12:37 input5::capslock -> ../../devices/platform/i8042/serio0/input/input5/input5::capslock
> lrwxrwxrwx  1 root root 0 Oct  8 12:37 input5::numlock -> ../../devices/platform/i8042/serio0/input/input5/input5::numlock
> lrwxrwxrwx  1 root root 0 Oct  8 12:37 input5::scrolllock -> ../../devices/platform/i8042/serio0/input/input5/input5::scrolllock
asus_nb_wmi            28672  0
asus_wmi               32768  1 asus_nb_wmi
sparse_keymap          16384  1 asus_wmi
wmi_bmof               16384  0
rfkill                 28672  6 asus_wmi,bluetooth,cfg80211
wmi                    36864  2 asus_wmi,wmi_bmof
asus_wireless          20480  0
atkbd                  36864  0
libps2                 20480  1 atkbd
i8042                  32768  1 asus_nb_wmi
serio                  28672  4 serio_raw,atkbd,i8042
asus-kbd-backlight                                                                                                                                                                     
cat: '/sys/devices/platform/asus-nb-wmi/leds/asus::kbd_backlight/max_brightness': No such file or directory
cat: '/sys/devices/platform/asus-nb-wmi/leds/asus::kbd_backlight/brightness': No such file or directory
1 Like

please edit and put 3 backtics ``` above and below outputs so they are formatted properly.

1 Like

try this

echo "blacklist asus-nb-wmi" | sudo tee /etc/modprobe.d/asus-nb-wmi.conf

and reboot after, any change?

No change, I am not holding my breath on this. I have never had it work on the 8 distros I have tried.

im sure there is some way of making it work, some google-fu will likely be necessary. do a github search for tools others may of made or modified to work on similar hardware. this is where persistence is a requirement

What about the 2 modules the arch wiki lists that I don't have on my system. Is there anyway to add those to my kernel.

this?

The relevant module seems to be amdgpu_bl0 , and asus::kbd_backlight for the keyboard backlight.

amdgpu_b10 is a module, and asus::kbd_backlight is a directory on sysfs. did you check to see if you had tham amdgpu module?

modinfo amdgpu-b10
modinfo amdgpu_b10
#try both, does it return any info?

you may need to add this kernel parameter for it to work properly.

acpi_backlight=vendor

and instead of being in /sys/class/leds it might be
/sys/class/backlight/

post:

ls -laR /sys/class/backlight/
~ >>> ls -laR /sys/class/backlight/                                            
/sys/class/backlight/:
total 0
drwxr-xr-x  2 root root 0 Oct  9 06:08 .
drwxr-xr-x 58 root root 0 Oct  9 06:08 ..
lrwxrwxrwx  1 root root 0 Oct  9 20:08 amdgpu_bl1 -> ../../devices/pci0000:00/0000:00:08.1/0000:05:00.0/backlight/amdgpu_bl1

From what I have been reading the keyboard back light on asus mother boards that have the aura built in. Is that the keyboard back light is controlled by SMBus specifically the second one. The issue is that the linux kernel doesn't recognized that one. I was able to find this on the github

I get lost at the part where he talks about a patch for the kernel. I ran a few of the commands listed below the install in that link and this it what comes up.

~ >>> modprobe i2c-dev i2c-piix4                                            [1]
modprobe: ERROR: could not insert 'i2c_dev': Operation not permitted
~ >>> sudo i2cdetect -l                                                     [1]
sudo: i2cdetect: command not found
~ >>>

Also decided to pull some error reports, one of the backlights is failing to load. I am guessing its my keyboard backlight. Here are the outputs

>>> journalctl -p 3 -xb                                                      
-- Logs begin at Mon 2019-10-07 12:35:30 MST, end at Wed 2019-10-09 20:29:29 MS>
Oct 09 13:08:48 manjaro-rog kernel: pci 0000:00:00.2: AMD-Vi: Unable to write t>
Oct 09 13:08:48 manjaro-rog kernel: tpm_crb MSFT0101:00: can't request region f>
Oct 09 13:08:48 manjaro-rog kernel: sp5100-tco sp5100-tco: Watchdog hardware is>
Oct 09 20:08:29 manjaro-rog kernel: [drm:construct [amdgpu]] *ERROR* construct:>
Oct 09 20:08:29 manjaro-rog kernel: [drm:construct [amdgpu]] *ERROR* construct:>
Oct 09 20:08:29 manjaro-rog systemd-backlight[769]: Failed to get backlight or >
Oct 09 20:08:29 manjaro-rog systemd[1]: Failed to start Load/Save Screen Backli>
-- Subject: A start job for unit systemd-backlight@backlight:acpi_video0.servic>
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
-- 
-- A start job for unit systemd-backlight@backlight:acpi_video0.service has fin>
-- 
-- The job identifier is 507 and the job result is failed.
Oct 09 20:11:13 manjaro-rog kernel: ucsi_ccg 3-0008: failed to reset PPM!
Oct 09 20:11:13 manjaro-rog kernel: ucsi_ccg 3-0008: PPM init failed (-110)
lines 1-17/17 (END)...skipping...
-- Logs begin at Mon 2019-10-07 12:35:30 MST, end at Wed 2019-10-09 20:29:29 MST. --
Oct 09 13:08:48 manjaro-rog kernel: pci 0000:00:00.2: AMD-Vi: Unable to write to IOMMU perf counter.
Oct 09 13:08:48 manjaro-rog kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xbcbe8000-0xbcbebfff]
Oct 09 13:08:48 manjaro-rog kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
Oct 09 20:08:29 manjaro-rog kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3
Oct 09 20:08:29 manjaro-rog kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3
Oct 09 20:08:29 manjaro-rog systemd-backlight[769]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
Oct 09 20:08:29 manjaro-rog systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
-- Subject: A start job for unit systemd-backlight@backlight:acpi_video0.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
-- 
-- A start job for unit systemd-backlight@backlight:acpi_video0.service has finished with a failure.
-- 
-- The job identifier is 507 and the job result is failed.
Oct 09 20:11:13 manjaro-rog kernel: ucsi_ccg 3-0008: failed to reset PPM!
Oct 09 20:11:13 manjaro-rog kernel: ucsi_ccg 3-0008: PPM init failed (-110)
systemctl --failed                                                                                                                                                           [130]
  UNIT                                            LOAD   ACTIVE SUB    DESCRIPTION                                                   
● systemd-backlight@backlight:acpi_video0.service loaded failed failed Load/Save Screen Backlight Brightness of backlight:acpi_video0

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

1 loaded units listed

i2c-dev i used to use to grab EDID info, i just tried to modprobe it now

~ >>> sudo modprobe 12c_dev                                                                          [1]
modprobe: FATAL: Module 12c_dev not found in directory /lib/modules/5.3.5-1-MANJARO

i dont know whats goin on there, i'll try with 4.19

for OpenAura, install the needed kernel modules first. make sure you have your matching kernel headers and dkms installed.

if your using linux52 and/or yay is already installed (edit as needed)

sudo pacman -S yay linux52-headers dkms i2c-tools

yay -S i2c-piix4-aura-dkms
~ >>> yay -Si i2c-piix4-aura-dkms                                                                       
:: Querying AUR...
Repository      : aur
Name            : i2c-piix4-aura-dkms
Keywords        : None
Version         : 5.3.4-1
Description     : The i2c-piix4 kernel driver, patched to be used with OpenAuraSDK: https://gitlab.com/CalcProgrammer1/OpenAuraSDK
URL             : https://bugzilla.kernel.org/show_bug.cgi?id=202587
AUR URL         : https://aur.archlinux.org/packages/i2c-piix4-aura-dkms

you need to use sudo when modprobing modules.

Looks like a typo in the module name: you surely meant to modprobe i2c_dev?

1 Like

modprobing 12c-dev usually works fine. there are a lot of modules that are named with a - and present as _ after loading.

example:

~ >>> sudo rmmod i2c-hid                                                                                
rmmod: ERROR: Module i2c_hid is not currently loaded
~ >>> sudo rmmod i2c_hid                                                                             [1]
rmmod: ERROR: Module i2c_hid is not currently loaded
~ >>> sudo modprobe i2c_hid                                                                          [1]
~ >>> sudo rmmod i2c_hid                                                                                
~ >>> sudo modprobe i2c-hid                                                                             
~ >>> sudo rmmod i2c-hid                                                                                
~ >>>
~ >>>                                                                                                   
~ >>> sudo modprobe i2c_hid                                                                             
~ >>> sudo rmmod i2c-hid      

but yes, i did check both before posting that.

i2c-dev must be missing from kernel 5.3, it loads fine on 4.19

~ >>> sudo modprobe i2c-dev                                                                             
~ >>> lsmod | grep i2c-dev                                                                              
i2c_dev                20480  0
~ >>>            

I meant the 12c.. (starting with number one) vs i2c..(starting with lowercase letter i).

1 Like

oh.. um... yeah so thinking before second cup of coffee is apparently not so forgiving :man_facepalming:

Forum kindly sponsored by Bytemark