On May 20 2017 or thereabouts, Dmitry Torokhov wrote:
> On Sat, May 20, 2017 at 11:59:50AM +0200, Benjamin Tissoires wrote:
> > Hi,
> >
> > On May 20 2017 or thereabouts, Pascal Wichmann wrote:
> > > > Looks like you running your patched kernel?
> > > That's right.
> > >
> > >
> > > >>>
On May 20 2017 or thereabouts, Dmitry Torokhov wrote:
> On Sat, May 20, 2017 at 11:59:50AM +0200, Benjamin Tissoires wrote:
> > Hi,
> >
> > On May 20 2017 or thereabouts, Pascal Wichmann wrote:
> > > > Looks like you running your patched kernel?
> > > That's right.
> > >
> > >
> > > >>>
On Sat, May 20, 2017 at 11:59:50AM +0200, Benjamin Tissoires wrote:
> Hi,
>
> On May 20 2017 or thereabouts, Pascal Wichmann wrote:
> > > Looks like you running your patched kernel?
> > That's right.
> >
> >
> > >>> CONFIG_RMI4_CORE=m
> > >>> CONFIG_RMI4_I2C=m
> > >>> CONFIG_RMI4_SPI=m
> > >>>
On Sat, May 20, 2017 at 11:59:50AM +0200, Benjamin Tissoires wrote:
> Hi,
>
> On May 20 2017 or thereabouts, Pascal Wichmann wrote:
> > > Looks like you running your patched kernel?
> > That's right.
> >
> >
> > >>> CONFIG_RMI4_CORE=m
> > >>> CONFIG_RMI4_I2C=m
> > >>> CONFIG_RMI4_SPI=m
> > >>>
Hi,
On May 20 2017 or thereabouts, Pascal Wichmann wrote:
> > Looks like you running your patched kernel?
> That's right.
>
>
> >>> CONFIG_RMI4_CORE=m
> >>> CONFIG_RMI4_I2C=m
> >>> CONFIG_RMI4_SPI=m
> >>> # CONFIG_RMI4_SMB is not set
> >
> > This is your issue I believe.
>
> Indeed, enabling
Hi,
On May 20 2017 or thereabouts, Pascal Wichmann wrote:
> > Looks like you running your patched kernel?
> That's right.
>
>
> >>> CONFIG_RMI4_CORE=m
> >>> CONFIG_RMI4_I2C=m
> >>> CONFIG_RMI4_SPI=m
> >>> # CONFIG_RMI4_SMB is not set
> >
> > This is your issue I believe.
>
> Indeed, enabling
> Looks like you running your patched kernel?
That's right.
>>> CONFIG_RMI4_CORE=m
>>> CONFIG_RMI4_I2C=m
>>> CONFIG_RMI4_SPI=m
>>> # CONFIG_RMI4_SMB is not set
>
> This is your issue I believe.
Indeed, enabling that configuration solves that issue.
However, I think it is quite unintuitive that
> Looks like you running your patched kernel?
That's right.
>>> CONFIG_RMI4_CORE=m
>>> CONFIG_RMI4_I2C=m
>>> CONFIG_RMI4_SPI=m
>>> # CONFIG_RMI4_SMB is not set
>
> This is your issue I believe.
Indeed, enabling that configuration solves that issue.
However, I think it is quite unintuitive that
On Fri, May 19, 2017 at 10:35:59PM +0200, Pascal Wichmann wrote:
> > Hmm, what about rmi_core and rmi_smbus? It might be quicker if you send
> > your dmesg, .config and lsmod...
>
> dmesg:
>
...
> > [ 12.944519] psmouse serio1: synaptics: queried max coordinates: x
> > [..5712], y [..4780]
>
On Fri, May 19, 2017 at 10:35:59PM +0200, Pascal Wichmann wrote:
> > Hmm, what about rmi_core and rmi_smbus? It might be quicker if you send
> > your dmesg, .config and lsmod...
>
> dmesg:
>
...
> > [ 12.944519] psmouse serio1: synaptics: queried max coordinates: x
> > [..5712], y [..4780]
>
On Fri, May 19, 2017 at 09:37:32PM +0200, Pascal Wichmann wrote:
> > Do you have i801_smbus driver enabled and loaded?
>
> I have the following line in my kernel configuration:
>
> > CONFIG_I2C_I801=m
>
> Following i2c/smbus-related modules are loaded:
>
> > lsmod | grep i2c
>
On Fri, May 19, 2017 at 09:37:32PM +0200, Pascal Wichmann wrote:
> > Do you have i801_smbus driver enabled and loaded?
>
> I have the following line in my kernel configuration:
>
> > CONFIG_I2C_I801=m
>
> Following i2c/smbus-related modules are loaded:
>
> > lsmod | grep i2c
>
> Do you have i801_smbus driver enabled and loaded?
I have the following line in my kernel configuration:
> CONFIG_I2C_I801=m
Following i2c/smbus-related modules are loaded:
> lsmod | grep i2c
:(
> i2c_smbus 16384 0
> Do you have i801_smbus driver enabled and loaded?
I have the following line in my kernel configuration:
> CONFIG_I2C_I801=m
Following i2c/smbus-related modules are loaded:
> lsmod | grep i2c
:(
> i2c_smbus 16384 0
On May 19, 2017 11:46:16 AM PDT, Pascal Wichmann
wrote:
>Hello,
>
>using the latest 4.12-rc1 kernel, the trackpoint and touchpad of my
>Thinkpad X250 are not recognized.
>
>This is caused by commit
>e839ffa Input: synaptics - add support for Intertouch devices
>
>
>The
On May 19, 2017 11:46:16 AM PDT, Pascal Wichmann
wrote:
>Hello,
>
>using the latest 4.12-rc1 kernel, the trackpoint and touchpad of my
>Thinkpad X250 are not recognized.
>
>This is caused by commit
>e839ffa Input: synaptics - add support for Intertouch devices
>
>
>The specific problem seems to
Hello,
using the latest 4.12-rc1 kernel, the trackpoint and touchpad of my
Thinkpad X250 are not recognized.
This is caused by commit
e839ffa Input: synaptics - add support for Intertouch devices
The specific problem seems to be the detection of whether to use
synaptics_intertouch for the
Hello,
using the latest 4.12-rc1 kernel, the trackpoint and touchpad of my
Thinkpad X250 are not recognized.
This is caused by commit
e839ffa Input: synaptics - add support for Intertouch devices
The specific problem seems to be the detection of whether to use
synaptics_intertouch for the
18 matches
Mail list logo