The same bug on Lenovo Y410p, Ubuntu 13.4 64bit.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1173874
Title:
Ubuntu 13.04 boot to black screen
Status in “linux” package in Ubuntu:
Hi wangjun (biggerchina),
Thank you for testing the linux/input/elan-i2c-ids.h! So somehow
elan_i2c can't handle this device either. Is there anything like
"elan_i2c i2c-ELAN060F:00: invalid report id data" in dmesg as similar
to https://bugzilla.kernel.org/show_bug.cgi?id=203467?
Btw, when
Hi Stefano Galassi (iltoga) and wangjun (biggerchina)
Thank you for providing the info!
So this ELAN touchpad's HID reporter descriptors could be read and
parsed but it couldn't be started at all since no HID reports are
received.
Now the only way I can think of to tackle this issue is to
And for those who have the Synaptics touchpad, I've found a way to make
the touchpad almost work. You can apply the following patch which will
make kernel use hid-rmi handle the device without blacklisting hid-
mulitouch,
diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
index
@injkgz
And also for those who have difficult building the custom kernel which
is not necessary, you can build a single pinctrl-amd.ko.
1. After you download the attached file which contains fixed pinctrl-
amd.c and other heades for building, run make to build this module,
$ make
make -C
@wangjun (biggerchina)
Thank you for sharing the result in #170.
I'm surprised to know that with pin's direction set to "out", no new "no
data" message shows when putting the touchpad aside.
Can you share the interrupt counter for me when you don't use the
touchpad? For my laptop, the number of
@Helmut Stult (helmut-stult)
> @Coiby Xu (coiby)
> Apparently there was a similar problem with the 4.19 kernel, but with
the Intel CPU, which was then solved with the following patch.
>
https://gitlab.manjaro.org/packages/core/linux419/-/blob/master/ELAN_touchpad_i2c_hid_pinctrl.pat
@PD (pd1986)
> @wangjun (biggerchina), @Coiby Xu (coiby)
> Could you please summarize what you tested and did for patch? I am
completely lost. :D
Basically, I want wangjun to find out the minimum time for manually
triggering a interrupt for the ELAN touchpad. You may be also check
@wangjun (biggerchina)
Thank you for sharing the result! Then we can be completely sure glitch
filter is the sole root cause.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Additional notes to #211:
Actually rebooting your machine is not necessary for simply testing the
module. You can remove the old kernel first,
$ sudo rmmod i2c-hid
and then insert the new module with the parameter "polling_mode=1"
$ sudo insmod i2c-hid.ko polling_mode=1
For have persistent
On Tue, Oct 13, 2020 at 05:27:44AM -, Azizkhan wrote:
>> i2c-hid.polling_mode=1 to the kernel boot parameters to make the
>touchpad work.
>you mean that I can just flash 5.9 kernel and then add to grub this line:
>GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video.use_native_backlight=1
hed-kernel.sh)`
>
>Note the need for updating GRUB_CMDLINE_LINUX_DEFAULT with i2c-
>hid.polling_mode=1
>
>(First time I've built the Linux Kernel myself or even commented on
>here!)
Congratulations!
>Thanks to @Coiby Xu (coiby)
You are welcome!
--
You received this b
For those who want to try the polling mode i2c-hid, here are the
instructions to build a single i2c-hid module without building a whole
kernel or downloading the whole kernel source code,
1. After you download the attached file which contains patched i2c-hid-core.c
and other headers for
Fix on #211
Another header file hid-ids.h is required to build i2c-hid module.
Attached is the updated zip file.
** Attachment added: "i2c-hid_standalone.zip"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5422562/+files/i2c-hid_standalone.zip
--
You received this
On Thu, Oct 15, 2020 at 05:37:46AM -, Kai-Heng Feng wrote:
>Coiby, can you please work on a DMI based workaround in gpiolib-acpi.c?
>It'll have higher chance to get merged.
>
Thank you for the suggestion! Linus Walleij also suggested introducing
a new quirk [1]. Although my main effort is on
@wangjun Thank you for doing this experiment!
1. When the touchpad works by setting pin's direction=out, you could see
lots of "no data" message ("IRQ triggered but there's no data") keeping
popping up after moving your finger away from the touchpad, am I
correct?
2. When pin's direction=out,
Hi all,
Can you test the follow patch works for your touchpad? Disabling glitch
filter seems to eliminate the root cause.
$ git diff
diff --git a/drivers/pinctrl/pinctrl-amd.c b/drivers/pinctrl/pinctrl-amd.c
index 9a760f5cd7ed..e786d779d6c8 100644
--- a/drivers/pinctrl/pinctrl-amd.c
+++
>>1. When the touchpad works by setting pin's direction=out, you could
see lots of "no data" message ("IRQ triggered but there's no data")
keeping popping up after moving your finger away from the touchpad, am I
correct?
> no, wrong. when run : echo out > direction,
> dmesg say :
> [ 133.854926]
Thank you for testing this patch! I'm glad it also works for both
04F3:3140 and 04F3:3186. I was completely new to things like I2C, HID
before investigating this touchpad issue. So thank you for your patience
with me.
Note this patch is meant to be a temporary specifically for this laptop.
It
Today I find something interesting about the GPIO controller. I wonder
if the same thing would happen to the ELAN touchpads.
For those who have the ELAN touchpad, could you show me the result of
the following experiment with a kernel not having the
polling_pin_state_touchpad.patch?
```bash
#
Hi wangjun,
Thank you for testing the script. Sorry I notice there's some problems
with the instructions in # 132. And those instructions can't be executed
as a single shell script.
If you go to /sys/class/gpio, do you see a folder named gpio386?
- If yes, cd to gpio386. "echo out > direction".
For Legion-5 15ARH05, the GPIO chip is managed by drivers/pinctrl
/pinctrl-amd.c. So the fix for drivers/gpio/gpio-amd-fch.c is irrelevant
to this issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
(For those who read # 132, please ignore it and this is re-written
version.)
For the Synaptics touchpad, the following experiment would make the
touchpad work. Could you share the result with the ELAN touchpad?
1. Install hid-tools and start hid-recorder as the root user
```bash
# install
@@wangjun Good to know that! What's the result of "echo value"? And
what's the output of hdi-recorder with and without fingers on the
touchpad?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
On Sun, Oct 11, 2020 at 07:07:37PM -, Paulinski wrote:
>Is there any chance that his patch will be part of the official kernel
>build soon?
I have yet to submit the patch of fixing the root cause. But I've
submitted a patch of adding polling mode to the i2c-hid module to
On Thu, Oct 15, 2020 at 04:27:05PM -, Lu Do wrote:
>Just try this morning the #210, it's working well on ubuntu 20.04 !
>Thanks @Coiby Xu (coiby)
>
>I also confirmed the suspend will break the touchpad
Thank you for testing it! I've sent a new patch to
https://lore.kernel.org/pat
On Thu, Oct 15, 2020 at 04:11:49PM -, Helmut Stult wrote:
>@Coiby Xu (coiby)
>
>We have received feedback in our forum that the touchpad no longer works
>after a resuming from suspend.
>
>I've attached the link - maybe you can take a look at it.
>
>https://forum.manjaro
On Sat, Oct 17, 2020 at 03:23:05PM -, Ivan Zakharyaschev wrote:
>I had problems (the touchpad not working and the suspend not working)
>with ELAN0001:00 04F3:3140 under linux-image-unsigned-5.6.0-1021-oem on
>Ubuntu, but they are gone if I manually unbind the device from
>elants_i2c driver and
@PD (pd1986)
> If I am not misunderstanding, does it mean that only patch for pinctrl-amd.c
> without changing i2c-hid-core.c should solve the problem?
Yes, you are right! Only commenting out one line of code in pinctrl-
amd.c would be sufficient for fixing this laptop model. But for now we
are
@Piotr Tomaszewski (nfm886)
> Hey Coiby Xu (coiby),
> That's does not works. Manjaro Linux 5.8.11-1-MANJARO x86_64 20.1.1 Mikah
> and make ending up with error 2
> translated error is
> make [1]: *** No objects found and no makefile found. Stop
You should run make in the folde
On Sat, Oct 10, 2020 at 11:38:27AM -, PD wrote:
>@Coiby Xu (coiby)
>Thanks a log for your contribution
>
It's my pleasure!
>I tried to use the way of "echo out > gpio386/direction" to fix the
>problem without patching the kernel, but I found Touchpad click
>se
On Sat, Oct 10, 2020 at 12:45:58PM -, Piotr Tomaszewski wrote:
>Hey @Coiby Xu (coiby),
>Last question from me :)
>How can I use #189 with PopOS? After "make" when I run "modinfo" I got output
>like that:
>
>name: pinctrl_amd
>filename:
@wangjun
Thank you for sharing the results and investigating this touchpad issue!
One thing confuses me is for the ELAN touchpad, no single interrupt
fires when you put finger on the touchpad while for the Synaptics
touchpad, you still see interrupts firing but with a very rate of ~7Hz.
Judging
The code 04F3 indeed represents the vendor ELAN. It seems I need to dig
into the lower level driver (one that talk to the touchd firmware
directly) to find out more info.
Btw, I Googled "Linux ELAN touchpad" and found another solution [kernel
- ELAN Touchpad not working on Lenovo Thinkbook with
Hi Helmut,
Thank you for sharing the article on MSFT (I'm been long wondering what
does MSFT mean).
> Right, it affects all MSFT touchpads.
>
> At the moment there is nothing for MSFT - we will have to be very patient and
> hope, that someone can find a driver for it.
I think The Microsoft
Hi Stefano,
> sudo evtest
>
>
> /dev/input/event17: Elan Touchpad
> /dev/input/event18: MSFT0001:00 04F3:3140
> Select the device event number [0-27]: 17
> Input driver version is 1.0.1
> Input device ID: bus 0x18 vendor 0x4f3 product 0x3140 version 0x100
> Input device name: "Elan
Hi,
I've found out that there is something wrong with the GPIO interrupt
controller under Linux. For the details, you can check
https://www.spinics.net/lists/linux-input/msg69267.html. While I'm
still working on the ultimate solution, you may be interested in the
patch as attached which makes
Thank you for testing the patch!
I'm sory I forgot the fact Lenovo ships different kinds of touchpads for
the same laptop model and neglected this bug report is for MSFT0001:00
04F3:3140. Yours must also this touchpad device whose vendor is Elan
(04F3).
I assume it should be also handled by
Sorry I made another mistake. hid_rmi is specifically for the Synaptics
RMI4 touchpads. We use let hid_elan handle this device. The
vendor id should be added to elan_devices in drivers/hid/hid-
elan.c. Can you give the following patch a try?
diff --git a/drivers/hid/hid-elan.c
Although Elan Touchpad is listed in the output of xinput, "0" in
"hid_elan 16384 0" shows hid_elan is not being used. Is there an entry
named "*:04F3:3140.*" under /sys/bus/hid/drivers/hid-elan/?
> plus I found that this device is already defined in hid-elan.c
I couldn't find the string 0x3140.
I am now working on this issue.
I can confirm the solution provided by
https://www.cnblogs.com/mikeguan/p/13126497.html works. What the solution does
is,
- blacklist hid_multitouch
- Add the vendor id and product id of this touchpad device to hid_device_id in
drivers/hid/hid-rmi.c
I've
Hi Robin Windey (r0wi) and Stéphane Roussel (stephane-roussel),
On Fri, Dec 25, 2020 at 08:52:35PM -, Robin Windey wrote:
>Had access to another Ideapad with touchpad MSFT0001:00 04F3:3140
>installed. Kernel 5.10.2-051002-generic #202012210832 did not work out
>of the box but in combination
Hi Kai-Heng Feng,
On Sun, Dec 20, 2020 at 07:30:12AM -, Kai-Heng Feng wrote:
>8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
>account debounce settings") is part of a series with 18 patches, so it's
>safer to only bakcport it for 5.10 kernels.
Although it's part of a
@Mike Boruta
On Tue, Nov 24, 2020 at 02:37:34AM -, Mike Boruta wrote:
>@Coiby Xu (coiby)
>
>Yes, that summarizes my findings nicely.
That's a bit strange. It should work for at least 5.7 as well. If you
have time, you can show me the result of
"sudo cat /sys/kernel/debug/gpio|g
@Azizkhan (injkgz)
On Mon, Nov 23, 2020 at 04:39:29PM -, Pedro Ribeiro wrote:
>@Azizkhan (injkgz)
>
>I don't think it is, I believe the for-next branch in linux-gpio will
>only be integrated in 5.11, but @Coiby Xu (coiby) should be able to
>confirm that.
>
It may also be ba
@Pedro Ribeiro
On Wed, Nov 25, 2020 at 10:23:25AM -, Pedro Ribeiro wrote:
>Don't want to hijack this thread, but has anyone here with a Legion 5
>(AMD version) has gotten the backlight working in Discrete graphics mode
>(only the nvidia GPU enabled)?
Have you tried installing the proprietary
Hi Mike,
On Sat, Dec 05, 2020 at 09:09:35PM -, Mike Boruta wrote:
>Hello Coiby,
>
>Hmm, as far as I can tell the proper module is being used since I
>executed the same steps for both the 5.7.19 and 5.8 kernels. I also
>confirmed this by running `modinfo pinctrl_amd` and verifying that it is
Hi @Maxim (pavlenkoms),
Is your laptop also a Lenovo Legion-5 model?
On Thu, Nov 12, 2020 at 09:02:54AM -, Maxim wrote:
>Hi @Coiby Xu (coiby)
>I tried #189 and #211 (different combinations) on mate-ubuntu 20.04 with
>custom kernels 5.8 and 5.9
>I tried to install Manjaro with k
@Pedro Ribeiro (pedrib)
On Sun, Nov 22, 2020 at 07:48:27AM -, Pedro Ribeiro wrote:
>@Coiby Xu (coiby)
>
>I build the next branch of linux-gpio (which contains the patch you mentioned
>in #251), and the trackpad works just fine without the hid polling on the
>kernel command
@Mike Boruta (maridius)
On Sun, Nov 15, 2020 at 08:34:03PM -, Mike Boruta wrote:
>@Coiby Xu (coiby)
>
>It seems that the patch in 171 does not work (i.e. touchpad is still
>dead) on kernels older than 5.8. I tried 5.4.75, 5.7.19, and 5.8.18. I
>don't really want to look in
Hi Mike,
On Sun, Nov 29, 2020 at 08:07:43PM -, Mike Boruta wrote:
>@Coiby Xu (coiby)
>
>Hello Coiby, had some time today so I compiled 5.7.19 from ubuntu
>mainline (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7.19/) with
>pinctrl_amd configured as a module, applied th
Hi all,
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git) has
the complete solution to fix this bug. So we can expect kernel v5.11 to
fix this issue without any additional work. Before the release of v5.11,
you are suggested to use #189 to save your
Hi Logan,
On Sun, Dec 6, 2020 at 12:05 PM Logan <1887...@bugs.launchpad.net> wrote:
> The output Coiby requested
> [root@lappy-the-laptop ~]# journalctl -k | grep -i amd_
> Dec 05 15:55:13 lappy-the-laptop kernel: amd_uncore: AMD NB counters detected
> Dec 05 15:55:13 lappy-the-laptop kernel:
Hi Mike,
On Sun, Dec 06, 2020 at 09:12:23PM -, Mike Boruta wrote:
>Hello Coiby,
>
>I built and installed the module as per the instructions in the branch
>you linked me to and `journalctl -k|grep amd_gpio` showed nothing. No
>new printouts in the kernel log. So I recompiled the module again
Hi @Helmut Stult (helmut-stult)
On Wed, Dec 16, 2020 at 6:32 PM Helmut Stult <1887...@bugs.launchpad.net>
wrote:
> The problem is your last patch
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pinctrl
>
On Wed, Nov 04, 2020 at 12:12:24PM -, Von wrote:
>@Coiby Xu (coiby)
>
>> Will decreasing
>polling_interval_active_us to 1ms fix the problem?
>> $echo 1000 > /sys/module/i2c_hid/parameters/polling_interval_active_us
>
>Yes, I installed the latest versi
On Sun, Nov 08, 2020 at 03:03:03AM -, Mike Boruta wrote:
>Hello again, I manually applied both the patches present in #239 and in
>#171 to kernel 5.4.0-52 without success (touch pad still does not work),
>however I applied the patch listed on #109 with success. My device is a
>MSFT0001:00
On Sun, Nov 08, 2020 at 01:14:48PM -, Mike Boruta wrote:
>Definitely! The attached output was compiled from 5.4.0-52 with the
>patch listed in 171.
#171 should fix your touchpad. According to your shared gpio-config,
that patch didn't take effect. So I guess you are still using the old
On Sun, Nov 08, 2020 at 07:38:15PM -, Azizkhan wrote:
>Hi all!
>@Coiby Xu (coiby)
>When your patch will be applied to mainline kernel? When we can just update
>our kernels and do nothing to fix touchpad?
I'm not sure when these patch(es) will be accepted and mer
On Sun, Nov 08, 2020 at 04:33:43PM -, Baq Domalaq wrote:
>Hi everyone! I have the same problem with my touchpad on Lenovo Ideapad
>Gaming 3 15ARH05 under Pop!_OS.
>
>My touchpad device number is slightly different:
>MSFT0001:00 06CB:CE2D
>
>I've applied a patch in comment #179 (I assumed
The patch in #239 depends on this patch [1] which requires to build the
whole kernel. For now, I would suggest adopting #189 to fix the touchpad
for daily use. But if anyone want to test the patch so we can push it
into the mainline kernel early, you can send me your email address and
I'll Cc you
On Tue, Oct 27, 2020 at 07:53:05PM -, Von wrote:
>The standalone patch #217 is working for MSFT0001:00 04F3:3140 but isn't
>working perfectly for MSFT0001:00 06CB:7F28. The MSFT0001:00 06CB:7F28
>touchpad frequently locks into scroll mode when using multitouch
>gestures.
Thank you for
On Tue, Oct 20, 2020 at 09:28:54AM -, Benjamin Rogoll wrote:
>Hey there guy, can anyone tell me what im doing wrong with the patch
>provided in #217. The tutorial in #211 doesnt work for me.
>
>p_$$/tmp.o; mkdir -p
>/home/benjamin/Downloads/i2c-hid_standalone(1)/i2c-hid_standalone/.tmp_$$;
) and R7000P whose BIOS set the debounce timeout
to 124.8ms which led to kernel receiving only ~7 HID reports per second.
Cc: Hans de Goede
Cc: Andy Shevchenko
Cc: 1887...@bugs.launchpad.net
BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190
Message-Id:
Signed-off-by: Coiby Xu
On Wed, Nov 04, 2020 at 10:42:38PM +0200, Andy Shevchenko wrote:
>On Wed, Nov 4, 2020 at 6:05 PM Coiby Xu wrote:
>>
>> Debounce filter setting should be independent from irq type setting
>> because according to the ACPI specs, there are separate arguments for
>>
** Description changed:
+ Update (#296)
+ =
+
+ The latest kernel tree
+ (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git) has
+ the complete solution to fix this bug. So we can expect kernel v5.11 to
+ fix this issue without any additional work. Before the release
Hi Mike Boruta (maridius),
> On Sun, Nov 29, 2020 at 08:07:43PM -, Mike Boruta wrote:
> >@Coiby Xu (coiby)
> >
> >Hello Coiby, had some time today so I compiled 5.7.19 from ubuntu
> >mainline (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7.19/) with
> >p
HI Nicolas,
On Fri, Jan 29, 2021 at 12:07:30PM -, Nicolas Rogues wrote:
>Following the bot's message, I do not see a new kernel in -proposed ?
>(with 5.8.0-41-generic rightg now). Is this a bot bug, or is there a
>newer 5.8 kernel with all patches applied ?
>
>Regarding brightness control, as
On Mon, Jan 25, 2021 at 07:03:55PM -, Adam Felson wrote:
>Before I grab'n'build 5.11, I'd like to know if my issue is similar.
>I have a lenovo ideapad 730s.
>The touchpad works fine for pointing, single, double and triple clicks.
>I have tried both the synaptics and libinput drivers. It's
On Thu, Jan 21, 2021 at 01:05:48PM -, Joe Zhou wrote:
>Lenovo R7000P Laptop. Sadly, still not a good solution. The touch pad
>now works with kernel 5.11.0, but it has problem with Nvidia GPU and the
>brightness control is not working. I can have Nvidia GPU working and
>manually do some fixes
Hi Marton,
On Tue, Feb 23, 2021 at 05:00:30PM -, Marton Danko wrote:
>Hi Coiby,
>
>Did you find anything about why it still doesn't work properly on my
>machine?
>
Your GPIO pin register value for the touchpad is 0x51b00 which means the
root cause has been fixed. I've less certain about the
On Wed, Feb 24, 2021 at 04:20:15PM -, Marton Danko wrote:
>I've done it and it's still registered primary action for that user too,
>it did not change anything.
I still think there's something wrong in the user space. I found a
similar bug report [1]. What's the output of "sudo libinput
On Tue, Mar 02, 2021 at 01:40:54AM -, Helmut Stult wrote:
>Works again - have to set CONFIG_I2C_HID_ACPI=m in config
Well done!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
On Fri, Feb 26, 2021 at 02:28:24PM -, Marton Danko wrote:
>Hi Coiby,
>
>Thanks, it seems that correctly telling which hardware button do I press.
>Right:
>-event18 POINTER_BUTTON +0.174s BTN_RIGHT (273) pressed, seat count: 1
> event18 POINTER_BUTTON +0.318s BTN_RIGHT (273)
On Mon, Apr 05, 2021 at 03:22:24PM -, James Hennig wrote:
>Since this is the main thread on the Internet about this issue, I
>suppose it is appropriate to post here even though I am using Manjaro.
>
>- This issue is non-present on a Thinkpad 3 14ADA05 with touchpad
>MSFT0001:00 06CB:CE2D on
On Sat, Mar 06, 2021 at 03:24:35PM -, Shatadru Banerjee wrote:
>I want to politely point out that this thread is not helping anymore; it
>has become mere chit-chat. Things were confusing to begin with and
>unfortunately it is becoming more confusing. What is the fix? Does is
>work with a
Hi resolve,
On Sun, Feb 14, 2021 at 04:09:09PM -, roselove wrote:
>Hi, I think I personally tried everything from bbs.archlinux.org,
>forum.manjaro.org, reddit, https://github.com/coiby/standalone_i2c_hid,
>bugzilla, bugs.launchpad.net, etc...
>
>I tried Coiby solution this very day
Hi Maton,
On Mon, Feb 15, 2021 at 08:46:57AM -, Maton Danko wrote:
>I've checked the 5.11.0-rc7 and the touchpad still doesn't work
>properly, on the left and right bottom side the same primary action is
>being taken instead of secondary on the right and primary on the left!
>
5.11.0-rc7 is
78 matches
Mail list logo
