Difference between revisions of "ThinkPad OSD"

From ArchWiki
Jump to: navigation, search
(Loading nvram at boot and give permission to access /dev/nvram)
(minor formatting updates)
Line 3: Line 3:
 
= Getting ThinkPad OSD working on Arch Linux =
 
= Getting ThinkPad OSD working on Arch Linux =
 
== General Note ==
 
== General Note ==
New desktop environments ([[gnome]], [[kde]], and maybe even [[xfce]]) support their own osd notifications for important events (volume up/down/mute and brightness up/down), which might be enough for most users. In order to use those notifications instead of the ones provided by TPB, map the keyboard-events of those keys to the proper keycodes.
+
New desktop environments ([[GNOME]], [[KDE]], and maybe even [[Xfce]]) support their own osd notifications for important events (volume up/down/mute and brightness up/down), which might be enough for most users. In order to use those notifications instead of the ones provided by TPB, map the keyboard-events of those keys to the proper keycodes.
  
 
== Loading nvram at boot and give permission to access /dev/nvram ==
 
== Loading nvram at boot and give permission to access /dev/nvram ==
* Add nvram to MODULES=(... nvram) in /etc/rc.conf
+
* Add {{ic|nvram}} to MODULES=(... nvram) in {{ic|/etc/rc.conf}}
Note: Check if there is already a line matching "nvram" in the /etc/udev/rules.d/ directory.<br />
+
{{Note|Check if there is already a line matching {{ic|nvram}} in the {{ic|/etc/udev/rules.d/}} directory.
In this case you have to modify the existing entry and do not create a tpb.rules.
+
 
 +
In this case, you have to modify the existing entry, and do not create a tpb.rules.}}
  
  

Revision as of 23:17, 16 December 2011


Getting ThinkPad OSD working on Arch Linux

General Note

New desktop environments (GNOME, KDE, and maybe even Xfce) support their own osd notifications for important events (volume up/down/mute and brightness up/down), which might be enough for most users. In order to use those notifications instead of the ones provided by TPB, map the keyboard-events of those keys to the proper keycodes.

Loading nvram at boot and give permission to access /dev/nvram

  • Add nvram to MODULES=(... nvram) in /etc/rc.conf
Note: Check if there is already a line matching nvram in the /etc/udev/rules.d/ directory. In this case, you have to modify the existing entry, and do not create a tpb.rules.


In udev 119-1

  • Edit file, WARNING: It will be overwritten with new udev update!

/etc/udev/rules.d/51-arch.rules

KERNEL=="nvram",   NAME="misc/%k", SYMLINK+="%k", GROUP="kmem", MODE="0666"
  • Note: this line seems to work better for some users:
KERNEL=="nvram", GROUP="kmem", MODE="0666"


In older udev

  • Add udev rule for setting the permissions to /etc/udev/rules.d/

/etc/udev/rules.d/tpb.rules:

KERNEL=="nvram", NAME="misc/%k", SYMLINK+="%k", MODE="0660", GROUP="users"

Setting a more readable color and better placement

/etc/tpbrc:

OSDCOLOR    Green
OSDVERTICAL 0
OSDHORIZONTAL 0
OSDPOS      MIDDLE
OSDALIGN    CENTER

Starting with KDE

~/.kde/Autostart/tpb-startup.sh:

# Start Thinkpad OSD daemon
if [ -x /usr/bin/tpb ] &&  [ -w /dev/nvram ] && [ -r /dev/nvram ]; then
    /usr/bin/tpb -d
fi

Starting with Fluxbox

~/.fluxbox/startup

# Start Thinkpad OSD daemon
if [ -x /usr/bin/tpb ] &&  [ -w /dev/nvram ] && [ -r /dev/nvram ]; then
    /usr/bin/tpb -d
fi