kmilo-legacy needed to display brightness changes, zoom, etc, on Thinkpad T41p

Same here with a ThinkPad R40 and Kubuntu 6.10.

I got it partly working by installing kmilo-thinkpad, loading nvram module and changing the rights of /dev/nvram:

sudo addgroup nvram
sudo adduser username nvram
sudo chown :nvram /dev/nvram
appending "nvram" to /etc/modules

This states also the problem described above. The volume bar jumps around quite a bit.

See also similar bug #31778 which is marked "fix released".

Sorry, I misspelled the packagename. I installed kmilo-legacy not kmilo-thinkpad.

As to the problem of the generic kmilo plugin interfering with kmilo-legacy, there is a workaround which I posted in bug #61822: just delete the file /usr/share/services/kmilo/kmilo_generic.desktop (or move it somewhere else, whatever).

Thanks for the hint Adrian!

To make this work fully I had to execute "kcmshell thinkpad", activate "Run Thinkpad Buttons KMilo plugin" and deactivate "Change volume in software". Then I had to go to System Settings, Advanced, Service Manager, select "KMilo", stop the service, then restart it.

After that when changing volume, brightness or toggling the ThinkLight the proper OSD should appear.

Same problem is with Kubuntu 7.04 (feisty fawn) on a X60s.
As is mentioned in the package description, I should file a bug, as done now.

Same here with a ThinkPad R40 and Kubuntu 7.04.

The installation of kmilo-legacy doesn't solve the problem completely. I also had to do the steps posted in the above workaround.
But the workaround I posted before works only partially.

The group of /dev/nvram changes on every reboot back to the kmem group. And I think it would be a bad idea to add the user to the kmem group. This will maybe lead to a security hole. The kmem group is also set on /dev/mem /dev/kmem and /dev/port.

Please fix this bug. It is annoying to figure out what is wrong this time. It worked perfectly with dapper drake.

The combined workaround (nvram permissions, installing kmilo-legacy, disabling kmilo_generic.desktop) works here (X60 1709-CTO).

However, it also results in the loss of Fn-F4 suspend functionality. This is on 7.04. Suspend on lid close and from the logout action still works.

BTW you can make the nvram permission change "permanent" by editing the nvram line in /etc/udev/rules.d/40-permissions.rules. I've changed mine to 0640, group nvram.

Other solution is to add your user to group kmem
After all this also works nice on T42

BTW
I wonder if someone reads bugs like this, there should be button "Hey we found a solution! just add this to distro"

i report the same for thinkpat Z60m
after applying your advices i got the same results as dimitris :-/

one more think i've found out -- Fn+F3 has also stopped working. Before it had been showing battery status in KDE.

Rather than moving /usr/share/services/kmilo/kmilo_generic.desktop to disable the normal kmilo, run "kcmshell kcmkded" and in the bottom pane un-check kmilo. Also, you may need to add nvram to /etc/modules in addition to changing the udev rules for it.

Confirming due to responses. I am assuming this is still an issue with Hardy as well?

 Very much still here with up-to-date Hardy. To recap, in order to get the sound and brightness buttons to behave appropriately I have:

- Installed kmilo-legacy
- Moved kmilo_generic.desktop to kmilo_generic.desktop.disabled
- Unchecked "Set Volume in software" in "kcmshell thinkpad" (X60 has hardware mixer)
- Bounced the KMilo service

I tried doing the above in KDE 4.1 rc1 (on my T42), because volume and mute keys were not working. No luck. Other buttons seem to work. Anybody tried their luck with 4.1?

An update to the above: fn+f5 as well as brightness and thinklight buttons work, the rest doesn't.

I'm testing Kubuntu 8.10 (Intrepid Ibex) Beta, and my volume, brightness, and thinklight keys work fine. My media keys also work, except for the bug #285056. My Fn+F5 key for wireless/bluetooth control also works, except for bug #212839. kmilo isn't even in the Intrepid repositories, so I wouldn't expect it to be a problem. Can we mark this as fixed in Intrepid?

I'd say we could. ;-)