touchscreen that worked in artful with 4.12 no longer works with 4.13
- Bionic (18.04)
- Bug #1745342
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
High
|
Unassigned | ||
Artful |
Won't Fix
|
High
|
Unassigned | ||
Bionic |
Expired
|
High
|
Unassigned |
Bug Description
I have a Dell Venue 11 Pro 7139, and when I installed artful on it (before release) it worked fine. Recently (over the xmas break I think but I'm not sure; this is not a machine I intended to pay too much attention to) the kernel moved from 4.12 to 4.13, and the touchscreen has stopped working.
I _think_ the last kernel to work was 4.12.0-13. I haven't done any sort of bisection though.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-
ProcVersionSign
Uname: Linux 4.13.0-31-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC1D0p: john 1041 F...m pulseaudio
/dev/snd/
Date: Thu Jan 25 10:18:51 2018
InstallationDate: Installed on 2017-07-10 (198 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
MachineType: Dell Inc. Venue 11 Pro 7139
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.169.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/15/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 0Y4RMT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Venue 11 Pro 7139
dmi.product.
dmi.sys.vendor: Dell Inc.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #1 |
- AlsaInfo.txt Edit (41.1 KiB, text/plain; charset="utf-8")
- CRDA.txt Edit (426 bytes, text/plain; charset="utf-8")
- CurrentDmesg.txt Edit (58.5 KiB, text/plain; charset="utf-8")
- Dependencies.txt Edit (2.8 KiB, text/plain; charset="utf-8")
- IwConfig.txt Edit (514 bytes, text/plain; charset="utf-8")
- JournalErrors.txt Edit (68.0 KiB, text/plain; charset="utf-8")
- Lspci.txt Edit (8.5 KiB, text/plain; charset="utf-8")
- Lsusb.txt Edit (559 bytes, text/plain; charset="utf-8")
- ProcCpuinfo.txt Edit (4.3 KiB, text/plain; charset="utf-8")
- ProcCpuinfoMinimal.txt Edit (1.1 KiB, text/plain; charset="utf-8")
- ProcEnviron.txt Edit (347 bytes, text/plain; charset="utf-8")
- ProcInterrupts.txt Edit (3.2 KiB, text/plain; charset="utf-8")
- ProcModules.txt Edit (7.7 KiB, text/plain; charset="utf-8")
- PulseList.txt Edit (23.4 KiB, text/plain; charset="utf-8")
- RfKill.txt Edit (161 bytes, text/plain; charset="utf-8")
- UdevDb.txt Edit (171.4 KiB, text/plain; charset="utf-8")
- WifiSyslog.txt Edit (87.0 KiB, text/plain; charset="utf-8")
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed | #2 |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #3 |
Would it be possible for you to test the latest upstream kernel? Refer to https:/
If this bug is fixed in the mainline kernel, please add the following tag 'kernel-
If the mainline kernel does not fix this bug, please add the tag: 'kernel-
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".
Thanks in advance.
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
tags: | added: kernel-da-key |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #4 |
$ uname -a
Linux flimsy 4.15.0-
tags: | added: kernel-bug-exists-upstream |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #5 |
We can perform a kernel bisect to identify the commit that introduced this regression. We first need to identify the last kernel version that did not have the bug and the first kernel version that did.
Can you next test v4.13-rc1:
http://
Changed in linux (Ubuntu Artful): | |
status: | New → In Progress |
Changed in linux (Ubuntu Bionic): | |
status: | Confirmed → In Progress |
Changed in linux (Ubuntu Artful): | |
importance: | Undecided → High |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
Changed in linux (Ubuntu Bionic): | |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #6 |
With
john@flimsy:~$ uname -a
Linux flimsy 4.13.0-
the touchscreen does not work.
With
john@flimsy:~$ uname -a
Linux flimsy 4.12.14-
from http://
the touchscreen _does_ work.
HTH,
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #7 |
Can you test v4.12 final to see if it also does not have the bug. 4.12.14 and 4.13-rc1 are not linear, so that's why we also need to test 4.12.
If 4.12 is good, I'll start a bisect between 4.12 and 4.13-rc1, which will give us the offending commit. A bisect will require testing of 10 kernel or so.
4.12 final is available from:
http://
Thanks in advance!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #8 |
Linux flimsy 4.12.0-
works.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #9 |
I started a kernel bisect between v4.12 final and v4.13-rc1. The kernel bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
e5f76a2e0e84ca2
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #10 |
$ uname -a
Linux flimsy 4.12.0-
did _not_ work.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #11 |
I built the next test kernel, up to the following commit:
1849f800fba32cd
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #12 |
Sorry for the delay :-) was at the doc's.
$ uname -a
Linux flimsy 4.12.0-
did _not_ work.
Thanks,
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #13 |
I built the next test kernel, up to the following commit:
cbcd4f08aa637b7
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #14 |
$ uname -a
Linux flimsy 4.12.0-
did _not_ work.
Thank you!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #15 |
I built the next test kernel, up to the following commit:
1b044f1cfc65a7d
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #16 |
$ uname -a
Linux flimsy 4.12.0-
did _not_ work.
Thank you!
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #17 |
I built the next test kernel, up to the following commit:
892ad5acca0b2dd
The test kernel can be downloaded from:
http://
Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.
Thanks in advance
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #18 |
$ uname -a
Linux flimsy 4.12.0-
did _not_ work.
Thank you.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #19 |
I built the next test kernel, up to the following commit:
e442cbf910c71fb
The test kernel can be downloaded from:
http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #20 |
$ uname -a
Linux flimsy 4.12.0-
did _not_ work.
Thank you.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #21 |
Eventually one of these test kernels should work and narrow down the bisect :-)
I built the next test kernel, up to the following commit:
d86c4d8ef31b3d9
The test kernel can be downloaded from:
http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #22 |
At some point somebody will figure out how to do newton-raphson instead of bisect.
$ uname -a
Linux flimsy 4.12.0-
did _not_ work.
Can't be much further now...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #23 |
I built the next test kernel, up to the following commit:
fdd050b5b3c9681
The test kernel can be downloaded from:
http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #24 |
$ uname -a
Linux flimsy 4.12.0-
did _not_ work.
What's the significance of the "rc5" in this last batch? I would've thought these were prior to the known-good 4.12 final.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #25 |
To build these kernels, I use a script called mainline-build-one, which is in the kteam-tools repository[0].
The script comes up with the name of the .deb by using the date and the git command 'git describe SHA1'. So in the case of the last commit tested:
git describe fdd050b5b3c9681
v4.12-rc5-
If the script used '--contains' with git describe, it would report the actual kernel version that contains that commit, for example:
git describe --contains fdd050b5b3c9681
v4.13-rc1~
[0] git://git.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #26 |
I built the next test kernel, up to the following commit:
a104c9f22c7d073
The test kernel can be downloaded from:
http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #27 |
$ uname -a
Linux flimsy 4.12.0-
did _not_ work.
Thank you.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #28 |
I built the next test kernel, up to the following commit:
b040ad9cf6a169c
The test kernel can be downloaded from:
http://
Hide
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #29 |
$ uname -a
Linux flimsy 4.12.0-
did _not_ work...
also plymouthd crashed, but that might be unrelated :-)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #30 |
I built the next test kernel, up to the following commit:
edea55abb86ff67
The test kernel can be downloaded from:
http://
I figured we would have a few 'good' kernels by now. There are only a few more steps in the bisect. Can you confirm v4.12 final was defiantly good? It is available at:
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #31 |
I just confirmed that
$ uname -a
Linux flimsy 4.12.0-
works, and that
$ uname -a
Linux flimsy 4.12.0-
does not work.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #32 |
I built the next test kernel, up to the following commit:
03ea8ad78cfb291
The test kernel can be downloaded from:
http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #33 |
Happy February!
With
$ uname -a
Linux flimsy 4.12.0-
it didn't work either.
Would it be possible to do a 4.12 final build in the same way you're doing the bisect builds? I'm starting to worry it's something in the build that changed.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #34 |
I built the next test kernel, up to the following commit:
9bddeb2a5b98150
The test kernel can be downloaded from:
http://
I also built a 4.12 final kernel using the same build method that I'm using for the bisect. That kernel can be downloaded from:
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #35 |
With the kernel in the 4.12 directory,
~$ uname -a
Linux flimsy 4.12.0-
the touchscreen did not work.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #36 |
Hmm, ok. I'm using a fit remote to artful for that build. Let me try building the kernel using Zesty or Xenial remote.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #37 |
Can you give the following kernel a try:
http://
It's the exact same tree as the last 4.12 kernel. If it works, that probably means the bug was introduced by a config change.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #38 |
The linux-headers deb seems to be truncated in that one.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #39 |
Do you need the headers file for something? To test the kernel, you should only have to install the linux-image and linux-image-extra .debs.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #40 |
Ah, ok then, I'll give it a try.
(there haven't been linux-image-extra debs in all this)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #41 |
with the one from 4.12/zesty-remote,
~$ uname -a
Linux flimsy 4.12.0-
it works.
I get the impression this is not good news.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #42 |
Sorry, your right. These are mainline kernels, so there is no -extra package.
So it sounds like the bug is due to a config change. I'll take a look at the git logs and see if any changes stick out.
Could you give the following two Ubuntu kernels a try:
4.12.0-14: https:/
4.13.0-10: https:/
With these kernels, you need to install both the linux-image and linux-image-extra .debs.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #43 |
Linux flimsy 4.12.0-13-generic #14-Ubuntu SMP Sat Sep 2 15:52:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
works;
Linux flimsy 4.13.0-10-generic #11-Ubuntu SMP Sun Sep 10 23:39:40 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
does not.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #44 |
Thanks for testing those two. That really points at a config change. Can you post the output from the following, so I can see the hardware info:
dmesg > dmesg.log
lspci -vvnn > lspci-vvnn.log
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #45 |
Nevermind comment #44. I see that is already posted to the bug. I'll see if I can see which config change could have caused this withing needing a bisect between those two versions.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #46 |
The lspci and dmesg attached to the bug are from when the touchscreen is not working. Can you boot a kernel where the touchscreen does work and collect that info?
dmesg > dmesg-working.log
lspci -vvnn > lspci-working.log
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #47 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #48 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #49 |
Comparing your two dmesg logs, I can see that the touchscreen is identified in the good dmesg, but nothing in the bad one. Here's the message from the good one:
[ 3.296644] input: SYNA7500:00 06CB:3AF0 as /devices/
[ 3.298646] hid-multitouch 0018:06CB:
I see one touchscreen specific change from 4.12.0-13 and 4.13.0-10. I disabled this option and reverted commit 78bcac7b2ae1e4f in this test kernel:
http://
Can you give this kernel a try? If it still has the bug, we can bisect between 4.12.0-13 and 4.13.0-10 and see if we can narrow it down that way.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #50 |
There seem to be two kernels there, so I tried them both: the touchscreen didn't work with either of them.
$ uname -a
Linux flimsy 4.13.0-32-generic #35~lp1745342Co
and
$ uname -a
Linux flimsy 4.13.0-32-generic #35~lp1745342ST
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #51 |
Thanks for testing. I'll have to review some of the other config differences between 4.13.0-10 and 4.12.0-13.
Another thing we could test is the latest Bionic kernel to see if a config change was already made there to resolve this. That kernel is available from:
https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #52 |
Hello again! Sorry for the delay.
With
$ uname -a
Linux flimsy 4.14.0-16-generic #19-Ubuntu SMP Mon Jan 8 17:50:31 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
no dice.
Thank you,
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #53 |
Can you give the following kernel a try:
http://
This kernel has CONFIG_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #54 |
Hello!
With
$ uname -a
Linux flimsy 4.13.0-32-generic #35~lp1745342Co
still no luck.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #55 |
I have one more test kernel to try:
http://
Can you give this kernel a try? If it still has the bug?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #56 |
Hello,
I tried with
$ uname -a
Linux flimsy 4.13.0-32-generic #35~lp1745342DE
and the bug is still there.
Sorry...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #57 |
I have another test kernel to try:
http://
Can you give this kernel a try? If it still has the bug?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #58 |
flimsy:~$ uname -a
Linux flimsy 4.13.0-32-generic #35~lp1745342Co
flimsy:~$
still nope.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #59 |
Thanks for testing. Those are the config changes that stick out. Next I'll try manually bisecting through the config file to figure out which one it is. I'll have another test kernel shortly.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #60 |
I'm bisecting through the config files manually. I have two test kenrels, one should be good and one should be bad. The test kernels are available here:
http://
http://
What I'm doing is building a v4.13-rc1 test kernel using just the top half of the new kernel config options and using the bottom half of the config file for the other test kernel. Depending on which one shows the bug, I'll then divide the bad config file in half again.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #61 |
Disappointing news I'm afraid: with the bottom half,
Linux flimsy 4.13.0-
the touchscreen didn't work; with the top half,
Linux flimsy 4.13.0-
the touchscreen didn't work.
Just to make sure I tried 4.12.0-13.14 again and it continues to work there.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Kai-Heng Feng (kaihengfeng) wrote : | #62 |
First, kudos to Joseph, my guesswork is based on his hard work.
Here's my theory: SMO91D0 (iio sensor hub) is connected to i2c's master adapter, SYNA7500 is connected to i2c's slave adapter.
We can see that in v4.12, both of them gets detected but SMO* doesn't get probed correctly. In v4.13, the support for i2c master/slave code got merged, now SMO* device can work, but the SYNA* is missing, because it's connected to the slave adapter.
Here's the relevant code:
#if IS_ENABLED(
extern int i2c_dw_
#else
static inline int i2c_dw_
#endif
Right now CONFIG_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #63 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Kai-Heng Feng (kaihengfeng) wrote : | #64 |
Well, that's quite unfortunate.
Can you attach the output of `udevadm info -e` and `dmesg` with kernel parameter `i2c_hid.
Also, from another bug report, the touchscreen works after resume from suspend.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #65 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #66 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #67 |
I just tried suspending with the 4.15 kernel, the touchscreen does not work after resume either.
It does work after resume with the 4.12 kernel.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #68 |
The touchscreen works for John with the upstream 4.12 final kernel found here:
http://
That kernel does not have CONFIG_I2C_SLAVE set.
Maybe one thing to try would be to boot with that kernel, confirm the touchscreen works, then capture the config options from the running kernel. That can be done with:
cat /boot/config-
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #69 |
It might also be good to capture the same output from upstream v4.13-rc1, since the touchpad does not work with that kernel. We can then do a diff of the two.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #70 |
I put the two configs on http://
Including a diff at http://
HTH,
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Kai-Heng Feng (kaihengfeng) wrote : | #71 |
Okay, please try this,
http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #72 |
With
Linux flimsy 4.15.0-9-generic #10~lp1745342+2 SMP Tue Feb 13 01:54:54 CST 2018 x86_64 x86_64 x86_64 GNU/Linux
the touchscreen didn't work.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Kai-Heng Feng (kaihengfeng) wrote : | #73 |
Yea, but is its ACPI device alive? Please attach `dmesg` and `udevadm info -e`.
According to comment #65, the SYNA7500's _STA says it's not alive:
P: /devices/
E: DEVPATH=
E: MODALIAS=
E: SUBSYSTEM=acpi
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #74 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Thomas Bielawski (tfbielawski) wrote : Re: [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13 | #75 |
I moved on to Fedora 27. The bug is present in Fedora 27 as well. It was
not present in Fedora 26. It's the same story with Ubuntu....through bug
was not there in 17.04 but showed up in 17.10.
So, maybe it's a Gnome bug
I'm waiting for 18.04 final release before testing Ubuntu waters again.
Thank you for your response
On Feb 13, 2018 04:35, "John Lenton" <email address hidden> wrote:
https:/
--
You received this bug notification because you are subscribed to a
duplicate bug report (1722677).
https:/
Title:
touchscreen that worked in artful with 4.12 no longer works with 4.13
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
I have a Dell Venue 11 Pro 7139, and when I installed artful on it
(before release) it worked fine. Recently (over the xmas break I think
but I'm not sure; this is not a machine I intended to pay too much
attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
has stopped working.
I _think_ the last kernel to work was 4.12.0-13. I haven't done any
sort of bisection though.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-
ProcVersionSi
Uname: Linux 4.13.0-31-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesI
USER PID ACCESS COMMAND
/dev/
/dev/
/dev/
Date: Thu Jan 25 10:18:51 2018
InstallationDate: Installed on 2017-07-10 (198 days ago)
InstallationM
MachineType: Dell Inc. Venue 11 Pro 7139
ProcFB: 0 inteldrmfb
ProcKernelCmd
root=UUID=
RelatedPackag
linux-
linux-
linux-firmware 1.169.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/15/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 0Y4RMT
dmi.board.vendor: Dell Inc.
dmi.board.
dmi.chassis.type: 8
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
pnVenue11Pro713
dmi.product.name: Venue 11 Pro 7139
dmi.product.
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Kai-Heng Feng (kaihengfeng) wrote : | #76 |
Actually, there's a great hint:
commit b5cc1699191829c
Author: Hans de Goede <email address hidden>
Date: Sun Jul 9 21:05:13 2017 +0200
ACPI / x86: Add Dell Venue 11 Pro 7130 touchscreen to always_present_ids
Let's do that same for 7139.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #77 |
I'll try that in a moment.
For what it's worth I've also got a 7140, running 16.04. That one's running 4.13.0-32 just fine. If there's anything you want me to try on it, just let me know.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #78 |
[ +0.000000] Linux version 4.15.0-9-generic (root@Ryzen) (gcc version 7.2.0 (Ubuntu 7.2.0-18ubuntu2)) #10~lp1745342+3 SMP Wed Feb 14 00:02:23 CST 2018
it worked!
I also suspended it, and it comes back fine from a short suspend; I'll leave it for a while to see if it also comes back ok from a longer one.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Kai-Heng Feng (kaihengfeng) wrote : | #79 |
Please attach the output of `cat /sys/firmware/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #80 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #81 |
- /sys/firmware/acpi/tables/DSDT for 7139 Edit (70.2 KiB, application/octet-stream)
The 7139 came back from suspend ~20 minutes later just fine.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
redx (redx) wrote : | #82 |
I have tested the patch and the touch is detected correctly, but if I detach and then reattach the dock keyboard, the keyboard stops working until i reboot the tablet.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Thomas Bielawski (tfbielawski) wrote : | #83 |
On Feb 13, 2018 14:15, "redx" <email address hidden> wrote:
> I have tested the patch and the touch is detected correctly, but if I
> detach and then reattach the dock keyboard, the keyboard stops working
> until i reboot the tablet.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1722677).
> https:/
>
> Title:
> touchscreen that worked in artful with 4.12 no longer works with 4.13
>
> Status in linux package in Ubuntu:
> In Progress
> Status in linux source package in Artful:
> In Progress
> Status in linux source package in Bionic:
> In Progress
>
> Bug description:
> I have a Dell Venue 11 Pro 7139, and when I installed artful on it
> (before release) it worked fine. Recently (over the xmas break I think
> but I'm not sure; this is not a machine I intended to pay too much
> attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
> has stopped working.
>
> I _think_ the last kernel to work was 4.12.0-13. I haven't done any
> sort of bisection though.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 17.10
> Package: linux-image-
> ProcVersionSign
> Uname: Linux 4.13.0-31-generic x86_64
> ApportVersion: 2.20.7-0ubuntu3.7
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: john 1041 F.... pulseaudio
> /dev/snd/pcmC1D0p: john 1041 F...m pulseaudio
> /dev/snd/controlC1: john 1041 F.... pulseaudio
> Date: Thu Jan 25 10:18:51 2018
> InstallationDate: Installed on 2017-07-10 (198 days ago)
> InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170709)
> MachineType: Dell Inc. Venue 11 Pro 7139
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=
> root=UUID=
> vt.handoff=7
> RelatedPackageV
> linux-restricte
> linux-backports
> linux-firmware 1.169.2
> SourcePackage: linux
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 06/15/2015
> dmi.bios.vendor: Dell Inc.
> dmi.bios.version: A16
> dmi.board.name: 0Y4RMT
> dmi.board.vendor: Dell Inc.
> dmi.board.version: A00
> dmi.chassis.type: 8
> dmi.chassis.vendor: Dell Inc.
> dmi.modalias: dmi:bvnDellInc.
> pnVenue11Pro713
> dmi.product.name: Venue 11 Pro 7139
> dmi.product.
> dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https:/
> 1745342/
>
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #84 |
@redx dmesg from after re-plugging the keyboard a few times might help?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Thomas Bielawski (tfbielawski) wrote : | #85 |
I apologize if you missed this, but I have moved on to Fedora 27. I'm
afraid I'm unable to help you with Ubuntu issues. The keyboard issue isn't
a problem for me anymore.
I do appreciate the hard work y'all have put into addressing the touch
screen issue, which seems to be a problem with many Gnome distributions.
On Feb 14, 2018 04:26, "John Lenton" <email address hidden> wrote:
@redx dmesg from after re-plugging the keyboard a few times might help?
--
You received this bug notification because you are subscribed to a
duplicate bug report (1722677).
https:/
Title:
touchscreen that worked in artful with 4.12 no longer works with 4.13
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
I have a Dell Venue 11 Pro 7139, and when I installed artful on it
(before release) it worked fine. Recently (over the xmas break I think
but I'm not sure; this is not a machine I intended to pay too much
attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
has stopped working.
I _think_ the last kernel to work was 4.12.0-13. I haven't done any
sort of bisection though.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-
ProcVersionSi
Uname: Linux 4.13.0-31-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesI
USER PID ACCESS COMMAND
/dev/
/dev/
/dev/
Date: Thu Jan 25 10:18:51 2018
InstallationDate: Installed on 2017-07-10 (198 days ago)
InstallationM
MachineType: Dell Inc. Venue 11 Pro 7139
ProcFB: 0 inteldrmfb
ProcKernelCmd
root=UUID=
RelatedPackag
linux-
linux-
linux-firmware 1.169.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/15/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 0Y4RMT
dmi.board.vendor: Dell Inc.
dmi.board.
dmi.chassis.type: 8
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
pnVenue11Pro713
dmi.product.name: Venue 11 Pro 7139
dmi.product.
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https:/
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Kai-Heng Feng (kaihengfeng) wrote : | #86 |
So let's focus on 7139.
John, do you have the keyboard issue other users have?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
redx (redx) wrote : | #87 |
sorry for the delay but I'm having busy days, tonight or tomorrow I will send you the logs of dmsg. I have the 7139 model.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #88 |
Kai, I don't use the 7139 with a keyboard dock. I have a keyboard dock on my 7140, and I can use it with my 7139 to test. I'll do that this evening and report back.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
redx (redx) wrote : | #89 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
redx (redx) wrote : | #90 |
do you need other type of logs?
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #91 |
- dmesg_4.15.0-9-generic.log Edit (64.3 KiB, text/plain)
Yes, I can confirm that with the 4.15.0-9 kernel with which the touchscreen works, if I disconnect the keyboard dock I need to power cycle (not just reboot) the machine to get it back.
Dmesg for disconnecting and reconnecting the dock for the 4.15.0-9 and the old 4.12.0-13 (with which the touchscreen also worked, and does not lose the keyboard dock) attached.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
John Lenton (chipaca) wrote : | #92 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Kai-Heng Feng (kaihengfeng) wrote : | #93 |
Do you also lose the keyboard dock in v4.13?
If it's the case, then I guess there's a commit that regressed both keyboard and touchscreen.
Changed in linux (Ubuntu Artful): | |
status: | In Progress → Incomplete |
Changed in linux (Ubuntu Bionic): | |
status: | In Progress → Incomplete |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Andy Whitcroft (apw) wrote : Closing unsupported series nomination. | #94 |
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.
Changed in linux (Ubuntu Artful): | |
status: | Incomplete → Won't Fix |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Launchpad Janitor (janitor) wrote : | #95 |
[Expired for linux (Ubuntu Bionic) because there has been no activity for 60 days.]
Changed in linux (Ubuntu Bionic): | |
status: | Incomplete → Expired |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Launchpad Janitor (janitor) wrote : | #96 |
[Expired for linux (Ubuntu) because there has been no activity for 60 days.]
Changed in linux (Ubuntu): | |
status: | Incomplete → Expired |
This change was made by a bot.