Re: Xorg doesn't find input devices with "Input: allow matching device IDs on property bits" applied

[Randy Dunlap]

On 10/22/17 12:32, Arthur Marsh wrote:
> After a recent git pull and kernel build and reboot, Xorg could not find the input devices and I was left with unresponsive mouse and keyboard until I could remotely shut-down and boot into an earlier kernel.
> 
> With good kernels, Xorg.log showed evdev finding the mouse and keyboard.
> 
> Bisecting lead to this commit:
> 
> Âgit bisect good
> 8724ecb072293f109a6f5dc93be8a98bf61fe14f is the first bad commit
> commit 8724ecb072293f109a6f5dc93be8a98bf61fe14f
> Author: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
> Date:ÂÂ Mon Oct 9 12:01:14 2017 -0700
> 
> ÂÂÂ Input: allow matching device IDs on property bits
> 
> ÂÂÂ Let's allow matching input devices on their property bits, both in-kernel
> ÂÂÂ and when generating module aliases.
> 
> ÂÂÂ Tested-by: Roderick Colenbrander <roderick.colenbrander@xxxxxxxx>
> ÂÂÂ Signed-off-by: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
> 
> :040000 040000 4192943bfd5affbe9e86c14efd690bda5c90bd82 d30b9d9c3a7ed1a6078f56a3bec2a82e0ba09570 MÂÂÂÂÂ drivers
> :040000 040000 d39ca313c8d6dc86ad1175bf9374c76d9c134e82 8717e17cbb0556629dd8cf7a7c34694dd299925c MÂÂÂÂÂ include
> :040000 040000 ba4684d3706ca73868f39e90f673e3926e23e3ba 811ed0e561768778c86eefa4c5ea5f866a542156 MÂÂÂÂÂ scripts
> 
> I am happy to run further tests if needed.
> 
> Arthur.

Hi,
See https://lkml.org/lkml/2017/10/22/125  for a patch.


-- 
~Randy