Description of problem: Since cauldron's kernel was updated to what will become 3.0 (or whatever name it will end with) I expected the function keys of my samsung netbook to work out-of-the-box but that's not the case. While the volume keys work (as previously), the others don't. I may misunderstand something but as samsung platform drivers were merged in 2.6.39 (https://lkml.org/lkml/2011/2/9/334) I though that the use of the voria's samsung-tools (http://www.voria.org/forum/) would have become a thing of the past. Maybe some configuration option (SAMSUNG_LAPTOP ?) has to be enabled or some package has to be installed but I can't find information on that. How reproducible: Always Steps to Reproduce: For instance, backlight : 1. Press Fn+left arrow or right arrow 2. KDE display the gauge properly 3. The backlight intensity isn't adjusted.
Hardware: All => i586
After poking around I tried to insert the samsung-laptop module with no luck: [root@localhost ~]# sudo modprobe -v samsung-laptop insmod /lib/modules/3.0.0-desktop-0.rc7.2.1.mga2/kernel/drivers/platform/x86/samsung-laptop.ko.gz FATAL: Error inserting samsung_laptop (/lib/modules/3.0.0-desktop-0.rc7.2.1.mga2/kernel/drivers/platform/x86/samsung-laptop.ko.gz): No such device This is weird since my netwook model is listed among those in the module modinfo and in dmidecode: [root@localhost ~]# modinfo samsung-laptop | grep N210 alias: dmi*:svn*SAMSUNGELECTRONICSCO.,LTD.*:pn*N150P/N210P/N220P*:rn*N150P/N210P/N220P*: alias: dmi*:svn*SAMSUNGELECTRONICSCO.,LTD.*:pn*N150/N210/N220/N230*:rn*N150/N210/N220/N230*: [root@localhost ~]# dmidecode | grep -i N210 Product Name: N150/N210/N220 Product Name: N150/N210/N220 I also tried to pass "force=1" to modprobe, in this case the module seems to be inserted successfully but that does nothing regarding function keys: [root@localhost ~]# modprobe -v samsung_laptop force=1 insmod /lib/modules/3.0.0-desktop-0.rc7.2.1.mga2/kernel/drivers/platform/x86/samsung-laptop.ko.gz force=1 [root@localhost ~]# lsmod | grep samsung samsung_laptop 13226 0 rfkill 20958 4 samsung_laptop,bluetooth,cfg80211 I tried to add "samsung-laptop force=1" to /etc/modules but then the module isn't actually load for some reason (can't find a proper log file for module loading messages at boot time). Issuing the following made my screen goes black for a little and then back to previous state: [root@localhost ~]# modprobe -v samsung-laptop force=1 debug=1 insmod /lib/modules/3.0.0-desktop-0.rc7.2.1.mga2/kernel/drivers/platform/x86/samsung-laptop.ko.gz force=1 debug=1 That said, I can mess with the brightness by writing directly inside /sys/class/backlight/samsung/brightness: echo "8" > /sys/class/backlight/samsung/brightness increase the brightness a little until it reach the maximum (/sys/class/backlight/samsung/actual_brightness value is incremented by 1 until it reach 8) echo "1" > /sys/class/backlight/samsung/brightness decrease the brightness a little until it reach the minimum (/sys/class/backlight/samsung/actual_brightness value is decremented by 1 until it reach 1) When doing so sometime the KDE brightness gauge is displayed and sometime not. I'm out of things and ideas and parameters to mess with... Cheers ! Thomas
CC: (none) => pterjanAssignee: bugsquad => tmbSource RPM: (none) => kernel
Me again, I think I found why I have to pass force=1 to modprobe. modinfo tell me that the module expect DMI to read N150/N210/N220/N230 but my laptop product number is N150/N210/N220. Their is a similar issue with someone that has a N150 on the kernel bugzilla. I will post here: https://bugzilla.kernel.org/show_bug.cgi?id=36082. That may explain (I believe...) why the module isn't loaded at boot but still doesn't explains why the function keys don't work.
How does kernel-3.0.0-1.mga2 work for you ?
Still not working. Here are the various thing I did: I patched drivers/platform/x86/samsung-laptop.c so I don't need to use force=1 as argument and added a MODULE_ALIAS line to the module get autoloaded. Right the /sys/class/backlight/samsung* directory is available after boot without any action. Still I can't use my keys. It seems that the keys are correctly recognized since if I run "/lib/udev/keymap -i /dev/input/event0" and press the backlight keys their are recognized as "scan code: 0x88 key code: brightnessup" and "scan code: 0x89 key code: brightnessdown". I also played a bit with xbacklight without any luck. I'm really out of ideas.
(In reply to comment #4) > Still not working. > And that is with 3.0.0-1.mga2 ? > Here are the various thing I did: > I patched drivers/platform/x86/samsung-laptop.c so I don't need to use force=1 Patching is not needed with 3.0.0-1.mga2
(In reply to comment #5) > And that is with 3.0.0-1.mga2 ? Yes ! > Patching is not needed with 3.0.0-1.mga2 Where can I see the patch aplied to mageia's kernels ?
(In reply to comment #6) > (In reply to comment #5) > > And that is with 3.0.0-1.mga2 ? > Yes ! > > > Patching is not needed with 3.0.0-1.mga2 > Where can I see the patch aplied to mageia's kernels ? @tmb With these last words of Thomas Courbon, the Thomas-Thomas discussion grinds to a halt. Any comment is welcome :) @ Thomas Courbon If your problem got solved, please let us know
CC: (none) => marja11
Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED. @ Thomas Courbon If your problem got solved, please let us know, if it didn't, let us know, too
Keywords: (none) => NEEDINFO
To get backlight keys working add 'acpi_backlight=vendor' to grub's kernel line.
CC: (none) => jani.valimaa
@ Thomas Courbon, could you please reply to the question in comment 8? If you won't reply within two weeks from now, I will have to close this bug as OLD. Thank you.
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to update to the latest updates of their distribution, and if this issue turns out to still be reproducible in the latest updates, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDResolution: (none) => OLD