Samsung nc20 brightness keys do not send release events

Hi Barry,

Thanks for writing the patch and additionally escalating this upstream, that's awesome and much appreciated. From the upstream bug report it indeed looks like this'll get merged upstream at which point the Ubuntu kernel team will cherry-pick the patch back into the Ubuntu kernel. The Ubuntu kernel is currently frozen for the upcoming Jaunty release, but I'll go ahead and approve the Jaunty nomination for a stable release update. Thanks.

can you please test the kernel in http://people.ubuntu.com/~manjo/lp360247-jaunty/ and report back here ?

Hi,

I installed the kernel and it works fine. It overwrote the 2.6.28-11-generic one that i had compiled myself. I installed it on Jaunty beta and I can check with the full release when it goes live tomorrow.

The fix also requires that the nc20 model is added to the hal-info configuration files as per the patch in https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/359814 but that fix hasn't been integrated just yet.

Thanks!

Barry.

submitted sru for jaunty, kindly push patch upstream.

Is that comment directed at me? I'm pretty new to all of this so forgive my newbieness! The last time that I checked the patch has been incorporated into the latest prepatch of 2.6.30: http://lwn.net/Articles/329525/

Thanks, Barry.

SRU justification:

IMPACT: Samsung nc20 brightness keys do not send release events
FIX: patch similar to the one done for NC10 laptops, use dmi_match to call
atkbd_samsung_keymap_fixup for NC20.
TEST: A test kernel from http://people.ubuntu.com/~manjo/lp360247-jaunty/
was tested by the originator of the bug, and verified to fix this problem.

Accepted linux into jaunty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Thanks, will verify later on today.

Apologies for the delay, I thought that the update was going to show in update manager. I installed the kernel and headers (2.6.28-12) with apt-get on the terminal just now and I can confirm that the fix is working. Thanks to everyone for your help.

I see no reason for the karmic task being "incomplete".

This bug was fixed in the package linux - 2.6.28-13.44

---------------
linux (2.6.28-13.44) jaunty-proposed; urgency=low

  [ Stefan Bader ]

  * Revert "SAUCE: [jaunty] ALSA: Add retry for Intel8x0 clock measurement"
  * Revert "SAUCE: [jaunty] ALSA: Fix clock and buffer calculations for
    Intel8x0"
  * Revert "SAUCE: [jaunty] ALSA: Fix buffer positions and checks"

linux (2.6.28-12.43) jaunty-proposed; urgency=low

  [ Amit Kucheria ]

  * Enable SYN_COOKIES for iop32x and versatile flavours
    - LP: #361687
  * SAUCE: Quirk for BT USB device on MacbookPro to be reset before use
    - LP: #332443

  [ Brad Figg ]

  * [jaunty] Add missing mvsas (Marvel SAS 6440) module configuration.
    - LP: #352336

  [ Chuck Short ]

  * SAUCE: [USB] Unusual Device support for Gold MP3 Player Energy
    - LP: #125250

  [ Daniel T Chen ]

  * SAUCE: [jaunty] ALSA: Fix buffer positions and checks
    - LP: #345627
  * SAUCE: [jaunty] ALSA: Fix clock and buffer calculations for Intel8x0
    - LP: #345627
  * SAUCE: [jaunty] ALSA: Add retry for Intel8x0 clock measurement
    - LP: #345627

  [ Luke Yelavich ]

  * disable CONFIG_SND_HDA_INPUT_BEEP on amd64 and i386
    - LP: #331589

  [ Makito SHIOKAWA ]

  * [ARM] 5404/1: Fix condition in arm_elf_read_implies_exec() to set
    READ_IMPLIES_EXEC
    - LP: #364358

  [ Manoj Iyer ]

  * SAUCE: Added quirk to fix key release for Samsung NC20
    - LP: #360247

  [ Oleg Nesterov ]

  * posix timers: fix RLIMIT_CPU && fork()
    - LP: #361508

  [ Scott James Remnant ]

  * [Config] Disable libusual and the ub driver
    - LP: #364538

  [ Stefan Bader ]

  * Disable unwanted staging builds
    - LP: #366144
  * Remove prism2_usb driver from ubuntu and use the one from staging
    - LP: #325366
  * SAUCE: Make rtl8187se depend on WIRELESS_EXT
    - LP: #366144
  * Disable CONFIG_RTL8187SE for armel.versatile
    - LP: #366144

  [ Tejun Heo ]

  * libata: handle SEMB signature better
    - LP: #257790

  [ Tim Gardner ]

  * Set USB_SERIAL=m for i386/amd64
    - LP: #345002
  * SAUCE: Jaunty - aic79xx - set reset delay to 5 seconds, down from 15.
    - LP: #79542
  * SAUCE: (drop after 2.6.28) Wifi suspend/resume scan timeout fixes
    - LP: #336055
  * Sony laptop: Sony Vaio laptops do not enable wwan power by default.
    - LP: #364678

  [ Tyler Hicks ]

  * SAUCE: (drop after 2.6.28) eCryptfs: Larger buffer for encrypted
    symlink targets
    - LP: #357345

  [ Upstream Kernel Changes ]

  * V4L/DVB (9999): gspca - zc3xx: Webcam 046d:089d added.
    - LP: #326674
  * V4L/DVB (10044): gspca - pac7311: Webcam 093a:2620 added.
    - LP: #363195
  * hwmon: (it87) Add support for the ITE IT8720F
    - LP: #357766
  * vgacon: Return the upper half of 512 character fonts
    - LP: #355057
  * drm/i915: add support for G41 chipset
    - LP: #365958

 -- Stefan Bader <email address hidden> Mon, 25 May 2009 17:30:40 +0200

The same problem occurs with the Samsung Q320.

There is the same problem with the Samsung Q210. Please submit this patch for the q210 too.

Hi,
same problem with Samsung R700 Aura.

I can confirm that the fixes regarding /usr/share/hal/fdi/information/10freedesktop/30-keymap-misc.fdi make the hotkeys come to life in Xorg. But I still have problems in fixing the kernel regarding the key release events.

The "forced_release_keys" array in "atkbd_samsung_keymap_fixup" contains scan codes that would be absolutely suitable for the R700 (if these hexadecimal values really represent scancodes with msb set to one (break codes))
The next thing to be done is an entry in "atkbd_dmi_quirk_table[]". I have done that. To reproduce it just copy the entry for the NC20 and set DMI_PRODUCT_NAME to "SR700". That should do the trick, if I am right.

The next step would be to compile the kernel. Now before i do that and take these 4h i could really spend better, i just want to ask: is there an easy way? At least something easier as described in the Kernel/Compile instrcutions? Something that does it by, say: "dpkg-buildpackage" and out comes your kernel .deb, your l-r-m package, and so on? Would be cool :-) -> It also would be cool if the changes to /usr/share/hal/fdi/information/10freedesktop/30-keymap-misc.fdi and linux/drivers/input/keyboard/atkbd.c would be in the updates anyway soon. I can upload the files if this is wished.

The next thing to mention is that gnome seems to realize that I press say, the "brightness up"-key, because it displays an osd telling me that brightness goes up... but the screen brightness does not change with my nvidia card.
I have tried smartdimmer -s and that works. How can I get gnome or whatever is responsible for that to use smartdimmer or anything that works?

help would be great :-)

cheers,

Manuel Gaus

ok...
got it running here too...

just stopped the whining and compiled/installed the kernel my custom kernel according to the ubuntu kernel/compile howto. That fixed up the repeating keys.

For the backlight problem i wrote a little dbus listener in perl that listens to /org/freedesktop/PowerManagement/Backlight events and sets the brightness appropriately using smartdimmer.

It is probably best, if I attach the files I modified.

Full path is /usr/share/hal/fdi/information/10freedesktop/30-keymap-misc.fdi

I put that to /opt/smartdimmerd
To run it I changed the launcher of gnome-power-manager in gnome autostart to point to /opt/smartdimmerd.
The first time that smartdimmerd tries to establish a dbus connection to the power-managers backlight service will fail, because power-manager does not run yet. But obviously this kicks of the launching of gnome-power-manager, so that the second try connecting to the service succeeds.

This is not really clean, I know, but my knowledge of gnome, hal, dbus and so on is rather shallow, so I am quite satisfied having come so far... brightness adjustment works at least :-)

have fun...

Manuel Gaus

Does this fix contain a solution for the Q320? If so, will this fix be downloaded during a system update? Sorry for the questions, I'm new to al this...

Setting Fix Committed. Please open new bugs for differing hardware as, even though the behavior may seem the same, on different hardware the fix will be specific to that hardware. Please also attach apport data to any new bug filed.

Thanks!

-JFo