Created attachment 73584 [details]
Output of various commands
I'm cloning this bug because it was assigned to other_other and there was no answer in almost two years. I think Input Devices is the right component for this so I hope someone can help us with it.
As stated in the original bug, I have very little experience compiling kernel modules, but I'm willing to learn whatever is needed to help you help me get this to work.
According to Lenovo's website (consumersupport.lenovo.com/ot/en/DriversDownLoads/Drivers_Show_4482.html), in Windows the SlideNav depends on the Synaptics driver. This makes me think that the SlideNav manufacturer is Synaptics. It is also called slidebar in many hardware manuals from Lenovo.
In addition, in /proc/bus/input/devices I have a "PS/2 Generic Mouse" even when there's no PS/2 connector in my notebook. Since Synaptics touchpads are also PS/2, I'm guessing that the slidenav is detected as that extra mouse.
+++ This bug was initially created as a clone of Bug #16004 +++
Lenovo Yxx0 laptops have a touch inductive panel http://www.gigamark.com/images/stories/8/Lenovo_y550/Untitled-4.jpg contains the pretty cool navigation slidebar http://www.fcenter.ru/img/article/notebooks/Lenovo_IdeaPad_Y550P/152399.jpg
How SlideNav should work:
User assign applications to the numbers. When user want to launch one of them, they touch slidenav in any place (touch but did not raise finger), after that driver show applications list on the screen http://www.fcenter.ru/img/article/notebooks/Lenovo_IdeaPad_Y550P/152341.jpg User move finger to the lift or to the right, until needed application was selected on the screen. After apllication selected user raise finger and this application started.
I tried use tp-smapi-dkms for detect slidenav buttons, but it's not work for me with error: No such device.
Folding it back into one bug (and I'll move the assignment)
However bugzilla is a bug tracking facility not a way to ask for new drivers so I am not surprised it has been ignored.
*** This bug has been marked as a duplicate of bug 16004 ***