On Sun, Oct 22, 2017 at 08:04:49PM +0200, Damien Wyart wrote:
> >>> - is evdev driver in your kernel compiled as a module?
>
> >> Yes, it is.
>
> > OK, so this must be module loading issue that I missed. Just to
> > confirm, if you "modprobe evdev" it all starts to work?
>
> Yes, I confirm loadi
>>> - is evdev driver in your kernel compiled as a module?
>> Yes, it is.
> OK, so this must be module loading issue that I missed. Just to
> confirm, if you "modprobe evdev" it all starts to work?
Yes, I confirm loading the module by hand makes everything work ok.
Thanks for your replies!
Dam
On Sun, Oct 22, 2017 at 10:27 AM, Damien Wyart wrote:
>>> Should that commit be reverted for now? Maybe other people will be
>>> able to reproduce it?
>
> On Sun, Oct 22, 2017 at 6:37 PM, Dmitry Torokhov
> wrote:
>> Hm, that is not good. A few question before we decide to revert:
>
>> - do your d
>> Should that commit be reverted for now? Maybe other people will be
>> able to reproduce it?
On Sun, Oct 22, 2017 at 6:37 PM, Dmitry Torokhov
wrote:
> Hm, that is not good. A few question before we decide to revert:
> - do your devices work on text console?
Yes, they do.
> - can you post /pr
On Sun, Oct 22, 2017 at 8:46 AM, Damien Wyart wrote:
> Hi,
>
> Having compiled a kernel today (bfc1168de949c in Linus' tree), I
> noticed keyboard and mouse were not working at all (stuck at X DM
> level).
>
> After digging a bit, I realized only one change in the recent input
> commits was quite
Hi,
Having compiled a kernel today (bfc1168de949c in Linus' tree), I
noticed keyboard and mouse were not working at all (stuck at X DM
level).
After digging a bit, I realized only one change in the recent input
commits was quite general, and bingo, reverting "allow matching device
IDs on property
6 matches
Mail list logo
