Bug 96875

Created attachment 124972 [details]
Content of /sys/class/dmi/id/modalias

Created attachment 124973 [details]
Virtual description of my input device

Created attachment 124974 [details]
udevadm info output

Created attachment 124975 [details]
Current libinput settings for the device

run the touchpad-edge-detector tool too please, so we know what the actual coordinates are the touchpad sends. thanks.

Created attachment 124997 [details]
touchpad-edge-detector tool

No problem, here it is...

hmm, you already have something that overrides the touchpad range. where is this coming from? I don't see anything upstream for this

(In reply to Peter Hutterer from comment #7)
> hmm, you already have something that overrides the touchpad range. where is
> this coming from? I don't see anything upstream for this

I'm not quite sure what do you mean. The only thing that I can say is that I followed the instructions and (maybe subjectively) I think that it worked, because I feel the difference and the values are now different; but I don't have actual proofs.

Maybe, if you give me some instructions, I can find something. 

Sorry for not being of any help...I'm only an intermediate user.

wait, so you mean you already put the hwdb file in place? if so that explains where the overrides come from, if not go search for a .hwdb file that sets 

EVDEV_ABS_00=1260:5853:54
EVDEV_ABS_01=821:5330:90

(In reply to Peter Hutterer from comment #9)
> wait, so you mean you already put the hwdb file in place? if so that
> explains where the overrides come from, if not go search for a .hwdb file
> that sets 
> 
> EVDEV_ABS_00=1260:5853:54
> EVDEV_ABS_01=821:5330:90

Yes, I already put it in place. For that reason, I wanted to report that it worked. The file that I used is attached (udev_rule).

ah, now I get it. though the touchpad edge detector sends different axis ranges than the ones in the udev rule. please run it again, make sure you really do reach all edges on the touchpad, then post the output numbers here. I'll get this into system asap after. bonus points for doing the resolution calculation for me based on the final set of numbers :)

Created attachment 125044 [details]
new udev rule

(In reply to Peter Hutterer from comment #11)
> ah, now I get it. though the touchpad edge detector sends different axis
> ranges than the ones in the udev rule. please run it again, make sure you
> really do reach all edges on the touchpad, then post the output numbers
> here. I'll get this into system asap after. bonus points for doing the
> resolution calculation for me based on the final set of numbers :)

I made it again and I attached the new udev rule (udev_rule_2). Although, the touchpad-egde-detector tool does not showed the exact numbers (but they are pretty close): 

Move one finger around the touchpad to detect the actual edges
Kernel says:	x [1170..5931], y [886..5330]
Touchpad sends:	x [1243..5927], y [902..5330] \^C

Touchpad size as listed by the kernel: 82x40mm
Calculate resolution as:
	x axis: 4761/<width in mm>
	y axis: 4444/<height in mm>

Suggested udev rule:
# <Laptop model description goes here>
evdev:name:SynPS/2 Synaptics TouchPad:dmi:bvnLENOVO:bvr2DCN18WW:bd06/18/2010:svnLENOVO:pn0911BCS:pvrLenovoV360:rvnLENOVO:rnMoutCook:rvrNotApplicable:cvnLENOVO:ct10:cvrN/A:*
 EVDEV_ABS_00=1243:5927:<x resolution>
 EVDEV_ABS_01=902:5330:<y resolution>

...I suppose that it does not matter,

thanks, submitted as: https://github.com/systemd/systemd/pull/3712

also I just filed bug 96910 because despite the axis corrections I think we should just get rid of the horizontal area in your case.

Merged into systemd, see https://github.com/systemd/systemd/pull/3712