I've now tested current Intrepid on the system I mentioned in comment 10, and confirmed that there is a problem there.
lock screen: works
sleep: works
RF kill: works
detect screens: works
hibernate: didn't test (live CD)
brightness: works (in hardware), but no software event and thus no OSD
volume: works (in hardware), but no software event and thus no OSD
I noticed that:
1. thinkpad-keys was not running (it should be)
2. after starting thinkpad-keys, adjusting volume or brightness and then running thinkpad-keys --update triggered the OSD (so that part works)
3. Running acpid -d, I could see no events generated for brightness or volume
I don't know why thinkpad-keys wasn't running. Running sudo /etc/init.d/hotkey-setup started it, as it should. Could folks here comment on whether thinkpad-keys is running, whether the hotkey-setup init script starts it, and whether it makes a difference when it is running?
I've now tested current Intrepid on the system I mentioned in comment 10, and confirmed that there is a problem there.
lock screen: works
sleep: works
RF kill: works
detect screens: works
hibernate: didn't test (live CD)
brightness: works (in hardware), but no software event and thus no OSD
volume: works (in hardware), but no software event and thus no OSD
I noticed that:
1. thinkpad-keys was not running (it should be)
2. after starting thinkpad-keys, adjusting volume or brightness and then running thinkpad-keys --update triggered the OSD (so that part works)
3. Running acpid -d, I could see no events generated for brightness or volume
I don't know why thinkpad-keys wasn't running. Running sudo /etc/init. d/hotkey- setup started it, as it should. Could folks here comment on whether thinkpad-keys is running, whether the hotkey-setup init script starts it, and whether it makes a difference when it is running?