It shouldn't. The APT package manager doesn't know we're replacing the files- so when you download an evdev update, it'll simply replace your hand-patched driver.
Originally Posted by ztrange
That's... weird. It doesn't seem to be autorepeating anymore, which indicates to me that the code is affecting the right keys... but the evdev driver no longer seems to be registering their key-down in the first place. And since this code just says 'KEY-DOWN', 'KEY-UP', it might be possible that something on your system is causing them to happen too quickly for the system to even count it as a keypress.
Originally Posted by dldeskins
Even odder, as I'm using a Satellite U305 myself; so I can say with reasonable certainty that it's probably not your hardware.
If you wouldn't mind answering a few questions for me...
1) Can you make sure that your keyboard shortcuts are still mapped to XF86VolumeDown and XF86VolumeUp in System->Preferences->Keyboard Shortcuts? I know it's basic, but I have to ask.
2) Did you ever use Hardy Heron? Did the volume knob work with that? Did it work with any past versions? Those used a different driver (kbd.so), which had a similar patch.
3) Can you run the following for me, spin the volume wheel a little while it's running and post the results?
'event1' should be the event number of your keyboard.
sudo evtest /dev/input/event1
You can press CTRL+C once you spin the volume wheel to exit.
I'd appreciate it if you included just a few lines of the information it prints when it first runs, too. They should look like this:
(Spinning the volume wheel might not do anything to the terminal. That's good.)
Input driver version is 1.0.0
Input device ID: bus 0x11 vendor 0x1 product 0x1 version 0xab41
Input device name: "AT Translated Set 2 keyboard"
Event code 113 (Mute)
Event code 114 (VolumeDown)
Event code 115 (VolumeUp)