Description of problem: Sony Vaio SVE17137CXB keyboard LED backlight not working. Version-Release number of selected component (if applicable): Fedora 26 How reproducible: Always. Steps to Reproduce: 1. Install Fedora 26 or run live from usb pen drive. 2. No keyboard backlight. 3. No kbd_backlight device parameter at kernel sys directory tree. Actual results: No keyboard lights. Expected results: Keyboard lights light up on key press and turn off 20 secs after the last key press. Additional info: Initial thread: https://ask.fedoraproject.org/en/question/111566/sony-vaio-sve17137cxb-keyboard-leds-not-working I was using RHEL 7 a month ago and the keyboard lights worked perfectly. sys directory listing: # ll /sys/devices/platform/sony-laptop/ total 0 -r--r--r--. 1 root root 4096 Sep 25 21:07 battery_care_health -rw-r--r--. 1 root root 4096 Sep 25 21:07 battery_care_limiter lrwxrwxrwx. 1 root root 0 Sep 25 20:57 driver -> ../../../bus/platform/drivers/sony-laptop -rw-r--r--. 1 root root 4096 Sep 25 21:07 driver_override -rw-r--r--. 1 root root 4096 Sep 25 21:07 fan_forced -r--r--r--. 1 root root 4096 Sep 25 21:07 fanspeed -rw-r--r--. 1 root root 4096 Sep 25 21:07 lid_resume_S5 -r--r--r--. 1 root root 4096 Sep 25 21:07 modalias -r--r--r--. 1 root root 4096 Sep 25 21:07 panel_id drwxr-xr-x. 2 root root 0 Sep 25 21:07 power lrwxrwxrwx. 1 root root 0 Sep 25 20:57 subsystem -> ../../../bus/platform -rw-r--r--. 1 root root 4096 Sep 25 21:07 thermal_control -r--r--r--. 1 root root 4096 Sep 25 21:07 thermal_profiles -rw-r--r--. 1 root root 4096 Sep 25 21:07 touchpad -rw-r--r--. 1 root root 4096 Sep 25 21:07 uevent -rw-r--r--. 1 root root 4096 Sep 25 21:07 usb_charge **I will gladly provide any information needed**
Additional information: - I am using UEFI boot and THE KEYBOARD LIGHTS WORK FINE ON GRUB !!! however once booting out of grub, the light goes out 20 sec and never light up. - I upgraded to Fedora kernel 4.13.13-300 using dnf, still not working. - I have tried out the sony-laptop kernel module params "compat" "kbd_backlight" "kbd_backlight_timeout" with several different values and still not working.
Can you try creating a: /etc/modprobe.d/local.conf file with the following there: blacklist sony-laptop And see if that at least keeps the backlight on ?
Thanks Hans, indeed it works, the keyboard backlight stays on for 20 secs after the last keypress and goes off, then back on at the first keypress. However, there is no linux device to control the keyboard backlight: # ls /sys/class/backlight/ radeon_bl0 Aside from that everything looks like it is working fine, except for the keyboard. The numpad is chaotic, every numpad number key causes undefined behaviors on the KDE, even the scroll-lock led goes on and off at random. Not sure if this is an improvement, for now I will keep the sony-laptop module available, just in case. But at least we have more information. Thanks again Hans.
(In reply to Fernando Farias from comment #3) > Thanks Hans, indeed it works, the keyboard backlight stays on for 20 secs > after the last keypress and goes off, then back on at the first keypress.> > However, there is no linux device to control the keyboard backlight: > > # ls /sys/class/backlight/ > radeon_bl0 Ok, re-reading your original post, you said things do work in RHEL-7, does that include getting a /sys/class/backlight entry for the keyboard? (note I would expect a /sys/class/leds entry as that the standard kbd backlight userspace ABI) > Aside from that everything looks like it is working fine, except for the > keyboard. > The numpad is chaotic, every numpad number key causes undefined behaviors on > the KDE, even the scroll-lock led goes on and off at random. Does this chaotic numpad thing only happen when blacklisting sony-laptop, or is this an independent problem? If this happens because of the blacklisting of sony-laptop then the best fix is probably to modify the sony-laptop driver to not touch the keyboard-backlight stuff on your model, although if sonay-laptop does work in RHEL-7, we should probably figure out what changed.
> Does this chaotic numpad thing only happen when blacklisting sony-laptop, or is this an independent problem? Only happens when blacklisting sony-laptop. > if sonay-laptop does work in RHEL-7, we should probably figure out what changed. I downloaded RHEL 7.4 and put it in a USB stick. Then tried to shrink Fedora27 and install RHEL 7.4 in a new partition. The stick was broken and left me half way into the installation... Some things I manage to test: - RHEL 7.4: keyboard backlight works fine. it has the normal 20secs delay. - RHEL 7.4: numpad works fine. - RHEL 7.4: Scroll lock actually works. (the hotkey is fn+numlk and never saw it working on Fedora) I will get a working usb stick and full install RHEL 7.4 so I can test the /sys/class things, and then report back my findings.
#!/bin/sh echo 1 > /sys/class/leds/input14::scrolllock/brightness check for the correct inputXX number ;)
backlight.sh #### #!/bin/sh echo 1 > /sys/class/leds/input14::scrolllock/brightness check for the correct inputXX number ;)
#!/bin/sh foo=$(find /sys/class/leds "$(cd ..; pwd)" -name "*scrolllock") bar="$foo/brightness" echo 1 > $bar more tricky script automated ;) enjoy //linux never fail//
(In reply to Zed from comment #8) > #!/bin/sh > foo=$(find /sys/class/leds "$(cd ..; pwd)" -name "*scrolllock") > bar="$foo/brightness" > echo 1 > $bar > > > > more tricky script automated ;) enjoy //linux never fail// Hi Zed, as stated in the description, the problem is with the keyboard BACKLIGHT LEDS, which are NOT being DETECTED BY KERNEL. The capslock, numlock, and scrolllock leds works just fine. Here is the listing just as an added info: [root@evaio leds]# ll total 0 lrwxrwxrwx 1 root root 0 Feb 13 16:46 ath9k-phy0 -> ../../devices/pci0000:00/0000:00:1c.0/0000:02:00.0/leds/ath9k-phy0 lrwxrwxrwx 1 root root 0 Feb 13 16:46 input2::capslock -> ../../devices/platform/i8042/serio0/input/input2/input2::capslock lrwxrwxrwx 1 root root 0 Feb 13 16:46 input2::numlock -> ../../devices/platform/i8042/serio0/input/input2/input2::numlock lrwxrwxrwx 1 root root 0 Feb 13 16:46 input2::scrolllock -> ../../devices/platform/i8042/serio0/input/input2/input2::scrolllock Thanks anyways.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.