Recently, I noticed that, from time to time, efivars values are
automatically restored to default thus making necessary to redo all the
steps in the aforementioned solution. Does anyone know if it is possible
to change this behavior? Thank you.
--
You received this bug notification because you
Confirmed that Kieran Clancy's solution (supplemented by ThOR27) works
on Samsung NP9005XT notebook. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1203592
Here it is.
** Attachment added: "kbdbri-hack.py"
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1203592/+attachment/5387619/+files/kbdbri-hack.py
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Queeq, yes I'd be interested in that Python script.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1203592
Title:
Keyboard backlight does not work in Samsung Series
For years I've been using a dirty Python script that listens on DBus for
keyboard backlight events and then keeps pushing the last heard value
through DBus every several seconds. Works fine most of the time, but
something turns off the backlight after a day or two of uptime (varies).
Mere turn
Got an issue tho. Either after suspend (or really long work session, not
sure), efivars get reset to zero, and I have to repeat whole procedure
again (including reboot)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Thank you Kieran Clancy, thank you ThOR27. Model Samsung SNP900X5T-
X01US. Can confirm that keyboard backlight now works with ambient light
sensor. Elementary OS Juno (Built on Ubuntu 18.04 LTS)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Hi,
Thanks for the tips here, I managed to get keyboard backlight working on
Kubuntu 17.04 with my NP900X3J - Samsung Style S50 (the key to change it
still doesnt works, and requires a reboot). I have to adapt what Kieran
said, what I did was:
# cd /sys/firmware/efi/efivars
# xxd -p
i have the solution contact me in my facebook
https://www.facebook.com/badiis1916
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1203592
Title:
Keyboard backlight
Kieran's solution doesn't work for Samsung NP940X3L. I tried to set it for the
following value:
xxd -p
/sys/firmware/efi/efivars/KBDBacklitLvl-5af56f53-985c-47d5-920c-f1c531d06852
070005
Backlight goes on briefly during early boot stages but then shuts off.
--
You received this bug
Sorry, forgot to mention that I'm on Linux Mint 17.3 (Ubuntu
14.04-based), kernel 4.5 generic, firmware 1.155.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1203592
OK never mind, works after the second reboot. I'd like to have a
solution that doesnt require reboot tho
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1203592
Title:
Kieran's solution doesn't work for me on Xubuntu 15.10 (900X3E). I can edit the
values with
xxd -p
/sys/firmware/efi/efivars/KBDBacklitLvl-8be4df61-93ca-11d2-aa0d-00e098032b8c
but they have no effect. Any ideas what else to try?
--
You received this bug notification because you are a member
... on my old 14.04 installation the backlit was always on, using CMS
and EFI off. I switched to EFI because of a CMS-related issue causing
kernel panics
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in
SImon N.
How do I write the hex value with xdd?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1203592
Title:
Keyboard backlight does not work in Samsung Series 9
I have Ubuntu 14.04 on two Samsung notebooks: a Series 9, model
NP900X4B-A02US ,and an ATIV Book 9 2014 Edition, model NP940X5J-K02US.
In the NP940X5J, Ubuntu is running with UEFI enabled. I confirm that
Kieran Clancy's solution works on that notebook.
In the NP900X4B, Ubuntu is running with
So do your think a fix that could be possible ? Is it available a kind of
package that fix keyboard backlit ?
Is it's useful I can post my DSDT and efivars like Simon, my KBDBacklitLvl is :
xxd -p
/sys/firmware/efi/efivars/KBDBacklitLvl-8be4df61-93ca-11d2-aa0d-00e098032b8c
070004
I have a
Thanks for looking into this!
You're right, I don't see a difference between 04 and 07.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1203592
Title:
Keyboard
Kieran,
thanks for the help.
./probe alwyas returns just
probe: Bad field: OSYS, 16 (0 bits)
The KBDBacklitLvl* variable seems to be right:
xxd -p KBDBacklitLvl-8be4df61-93ca-11d2-aa0d-00e098032b8c
070001
Writing 070005 makes the keyboard backlight bright on next reboot.
Btw: The
Simon,
Sorry about that - there was a syntax problem in regions.c
I've just updated it so it should work properly now, if you are happy to
test it again.
The keyboard shortcut is currently set up to connect to the samsung
laptop kernel driver, but since the module is disabled on UEFI, the
Kieran,
now it works, before there was 070001, I wrote 070005 for the second
probe (did the reboot i n between as well).
BR, Simon
** Attachment added: Output of probe
Thanks Simon,
Looks like the KBCL variable is indeed the right one. Strange that it
changed from 01 to 04 rather than 01 to 05 though... If you have time
for a few more tests, I would love to know what values it takes when the
UEFI variable is modified from 00 through 07.
Currently we have:
Here you are, the 04 was correct, I verified once again.
UEFI KBCL
00 00
01 01
02 02
03 03
04 04
05 04
06 04
07 04
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
Great work, thanks Simon.
I presume that there is no noticeable difference in brightness between
04 and 07 then?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1203592
** Attachment added: sudo cat /sys/firmware/acpi/tables/DSDT DSDT.aml
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1203592/+attachment/4121663/+files/DSDT.aml
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
** Attachment added: ls -la /sys/firmware/efi/efivars/ list.txt
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1203592/+attachment/4121664/+files/list.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Simon,
It looks like your UEFI variable has a different name:
KBDBacklitLvl-8be4df61-93ca-11d2-aa0d-00e098032b8c
Please do xxd on this and see if it looks similar to my
SecKeyboardBacklightLevel variable.
Thanks for your DSDT. It looks like your machine doesn't have a KBLL
variable... the
I don't know if this has been mentioned before, but bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283589 -
[Samsung NP530U3C-A01] LID close, AC, and battery status events not produced
anymore - seems to have some influence over this.
While the FN buttons do not work for keyboard
For those without KeyboardBacklight UEFI variables, can you attach a
list of the UEFI variables you do have, as well as attach a dump of your
DSDT:
sudo cat /sys/firmware/acpi/tables/DSDT DSDT.aml
If you are not using UEFI (e.g. you have no /sys/firmware/efi directory)
then none of this will
No luck here w/ Kieran Clancy's solution on a 940X.
Well, there was no *eyboard* file in the directory anyway...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1203592
Same here with a 900X3G, Kieran Clancy's solution doesn't work because
there is no *KeyboardBacklight* file.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1203592
I'm on a NP700Z5C using LMDE/Debian testing. Keyboard backlight works in
auto mode, and its Fn+F9, Fn+F10 keys do nothing. It would fine for me
if it were possible to at least turn it off or auto. For example: when
watching a film in a dark room it is not possible to turn off those
lights off.
I'd like to try Kieran Clancy's solution, but I don't know if it0ll be working
also on NP770Z5C notebook (I set UEFI and CMS OS BIOS Option)
How could I help ?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I also confirm that Kieran Clancy's solution works on Samsung NP900X4C, Ubuntu
14.04.
Thanks a lot man, this really was annoying me.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
If you have UEFI disabled, the keyboard backlight control should work
automatically through the samsung-laptop kernel module.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
Keyboard backlight does not work in my Samsung NP900X4B as well. I am
running Ubuntu 14.04 LTS with UEFI disabled.
The strange thing is that I had it working on my first installation of
Ubuntu on this notebook. I was running Ubuntu 12.04 at that time. Later
on, when I upgraded Ubuntu to 13.04,
I can confirm the solution of Kieran Clancy works on my samsung np900x4c
with ubuntu 14.04 LTS
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1203592
Title:
Keyboard
I was just screwing around with this and found out something
interesting.
In /etc/modprobe.d/samsung-backlight.conf you'll likely see;
blacklist samsung-laptop
options samsung-backlight use_sabi=0 levels=8 force=1
Remove the blacklist and keyboard backlight controls will work and
To complement what aisthesis said, now, in Ubuntu 14.04, the kb backlight
works.
It gets triggered only via the luminosity sensor, not the fn keys.
I don't recommend removing that blacklist, as its known to brick the
laptop in UEFI mode (atleast in old BIOS versions).
--
You received this bug
If you are using UEFI, do not remove the blacklist on samsung-laptop!
You are probably safe from the bricking bug with a recent kernel, but
there are other UEFI problems with samsung-laptop that have never been
resolved, like machine check exceptions.
I did find a way of setting the keyboard
Same problem here. From what I could read it is indeed that the special
hardware stuff are turned off my default in the kernel when it detects that the
system is running in UEFI mode.
This has been done because of a bug in the UEFI firmware from Samsung that
could brick the whole laptop.
From the discussion in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/130
a few worhtwile considerations:
- It is said that this is caused by UEFI bug though, since Samsung's special
hardware features are disabled in UEFI mode.
- It therefore only affects Samsung models
Hi,
I tried showkey --scancodes but there isn't any scancodes associated
with fn+f9 and fn+f10.
Regards
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1203592
Title:
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1203592
Title:
Keyboard backlight does
Any news regarding this, or any help needed?
There is also a discussion regarding this at
http://askubuntu.com/questions/233312/how-to-make-keyboard-backlight-fn-
buttons-work-in-samsung-series-9
** Description changed:
In Ubuntu 13.04, the keyboard backlight does not work in Samsung Series
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
Same result here:
fn+light down = scan code: 0x97 key code: kbdillumdown
fn +light uo = scan code: 0x96 key code: kbdillumup
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
Thanks, so the keymaps are fine. Moving to gnome-settings-daemon, it's
the power plugin's responsibility to control backlight.
** Package changed: udev (Ubuntu) = gnome-settings-daemon (Ubuntu)
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete = New
--
You received this
48 matches
Mail list logo
