Launchpad has imported 67 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=198715.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
------------------------------------------------------------------------
On 2018-02-07T20:50:42+00:00 aidanjacobhahn wrote:
Created attachment 274057
dmesg output after boot
I have an HP Envy x360 with a ryzen 5 2500U processor and I am running kernel 4.15.0-staging. When I am running windows 10 my touchscreen does work, and is detected as a hid-compliant touchscreen. I was able to pull some driver information from windows event viewer. It looks like windows is using the following driver: HID\ELAN0732&Col01\4&2e44c06e&0&0000 .
I have been communicating with people at the wacom-hid-descriptors repository and was advised that this is a kernel issue.
It does seem like the kernel can see my devices at
/sys/devices/platform/AMDI0010:00/i2c-0/i2c-ELAN0732:00 and
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/AMDI0010:00/ELAN0732:00 .
however even after loading the hid-touchscreen module, the i2c-hid module, and the elants-i2c module my touchscreen is not working.
I do have some ACPI errors in my dmesg log (attached) but I am not sure they are related. Let me know if there is additional information I can get you.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/0
------------------------------------------------------------------------
On 2018-02-07T21:26:05+00:00 killertofu wrote:
Link to the wacom-hid-descriptors bug report, for reference:
https://github.com/linuxwacom/wacom-hid-descriptors/issues/12
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/1
------------------------------------------------------------------------
On 2018-02-12T10:41:16+00:00 g.fitch wrote:
This appears to be related - same machine (HP Envy x360 with Ryzen):
[ 7.650876] i2c_designware AMDI0010:00: ACPI slave is not supported yet
[ 7.650913] i2c_designware AMDI0010:00: Standard-mode HCNT:LCNT = 642:749
[ 7.650919] i2c_designware AMDI0010:00: Fast-mode HCNT:LCNT = 132:239
[ 7.651103] i2c-dev: adapter [Synopsys DesignWare I2C adapter] registered as minor 5
[ 7.651111] i2c i2c-5: adapter [Synopsys DesignWare I2C adapter] registered
[ 7.651711] i2c i2c-5: client [ELAN0732:00] registered with bus id i2c-ELAN0732:00
[ 7.677151] i2c_designware AMDI0010:00: Standard-mode HCNT:LCNT = 642:749
[ 7.677157] i2c_designware AMDI0010:00: Fast-mode HCNT:LCNT = 132:239
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/2
------------------------------------------------------------------------
On 2018-02-13T01:25:31+00:00 aidanjacobhahn wrote:
I just tried kernel 4.16rc1
Touchscreen is still not operating. output very similar to 4.15 will attach another dmesg
(In reply to g.fitch from comment #2)
> This appears to be related - same machine (HP Envy x360 with Ryzen):
>
> [ 7.650876] i2c_designware AMDI0010:00: ACPI slave is not supported yet
> [ 7.650913] i2c_designware AMDI0010:00: Standard-mode HCNT:LCNT = 642:749
> [ 7.650919] i2c_designware AMDI0010:00: Fast-mode HCNT:LCNT = 132:239
> [ 7.651103] i2c-dev: adapter [Synopsys DesignWare I2C adapter] registered
> as minor 5
> [ 7.651111] i2c i2c-5: adapter [Synopsys DesignWare I2C adapter]
> registered
> [ 7.651711] i2c i2c-5: client [ELAN0732:00] registered with bus id
> i2c-ELAN0732:00
> [ 7.677151] i2c_designware AMDI0010:00: Standard-mode HCNT:LCNT = 642:749
> [ 7.677157] i2c_designware AMDI0010:00: Fast-mode HCNT:LCNT = 132:239
Which kernel are you using? I dont even get this output.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/3
------------------------------------------------------------------------
On 2018-02-13T01:27:15+00:00 aidanjacobhahn wrote:
Created attachment 274145
DMESG on 4.16rc1
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/4
------------------------------------------------------------------------
On 2018-02-13T03:10:16+00:00 aidanjacobhahn wrote:
I believe this problem to be related to the thread located here:
https://www.spinics.net/lists/linux-input/msg50784.html
I will attach disassembled ACPI tables in case they prove to be useful.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/5
------------------------------------------------------------------------
On 2018-02-13T03:11:14+00:00 aidanjacobhahn wrote:
Created attachment 274147
Disassembled ACPI table for HP Envy x360 15z (ryzen 5 2500u)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/6
------------------------------------------------------------------------
On 2018-02-13T07:18:43+00:00 g.fitch wrote:
(In reply to Aidan Hahn from comment #3)
> Which kernel are you using? I dont even get this output.
4.15-drm-next (fixes a nasty problem with 3 out of 5 boots locking up -
still get irritating lock-ups when using X, and especially anything
opengl).
I turned on i2c debugging to see the status messages that the i2c-hid,
elants_i2c etc. modules should be printing if they find the device but
have some other communications problem.
I'm new to this, so not sure what I'm looking at, but I think the
touchscreen only identifies itself through ACPI, as an i2c slave at its
own address, and drivers/i2c/i2c-core-slave.c can't enumerate that yet.
So the device node doesn't get created, and the hid drivers have nothing
to connect to.
I could be completely wrong, though - I'm good at being wrong :)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/7
------------------------------------------------------------------------
On 2018-02-13T20:45:06+00:00 aidanjacobhahn wrote:
(In reply to g.fitch from comment #7)
> (In reply to Aidan Hahn from comment #3)
>
> > Which kernel are you using? I dont even get this output.
>
> 4.15-drm-next (fixes a nasty problem with 3 out of 5 boots locking up -
> still get irritating lock-ups when using X, and especially anything opengl).
>
> I turned on i2c debugging to see the status messages that the i2c-hid,
> elants_i2c etc. modules should be printing if they find the device but have
> some other communications problem.
>
> I'm new to this, so not sure what I'm looking at, but I think the
> touchscreen only identifies itself through ACPI, as an i2c slave at its own
> address, and drivers/i2c/i2c-core-slave.c can't enumerate that yet. So the
> device node doesn't get created, and the hid drivers have nothing to connect
> to.
>
> I could be completely wrong, though - I'm good at being wrong :)
What model number are you running? I am using a 15-bq100.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/8
------------------------------------------------------------------------
On 2018-03-01T04:17:38+00:00 aidanjacobhahn wrote:
Not sure what more information I should provide,
If there is more information needed to troubleshoot this issue please let me know.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/11
------------------------------------------------------------------------
On 2018-03-16T07:15:27+00:00 aidanjacobhahn wrote:
Updated kernel to 4.16 (drm-next) and upon compile turned on some i2c
debugging features. Now when I boot I recieve the following:
[ 0.187816] i2c i2c-0: client [ELAN0732:00] registered with bus id i2c-ELAN0732:00
[ 1.301023] acpi ELAN0732:00: GPIO: looking up 0 in _CRS
(the second entry is repeated ad nauseum)
libwacom-list-local-devices still cannot see this device.
I have attached my new DMESG which still has the ACPI Errors, among some additional interesting output from the i2c subsystem.
Am I missing something? Have I sent this bug to the right place?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/14
------------------------------------------------------------------------
On 2018-03-16T07:16:09+00:00 aidanjacobhahn wrote:
Created attachment 274773
DMESG output after boot on 4.16 (drm-next)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/15
------------------------------------------------------------------------
On 2018-04-15T00:33:33+00:00 openproggerfreak wrote:
I recently bought the same laptop and tried to look deeper into the problem.
I'm not a kernel developer or have any knowledge in kernel subsystems but what I found so far is that the AMD GPIO driver doesn't support ACPI for x86 platforms.(Kernel 4.16)
On HP Envy x360(Ryzen) the GPIO device is detected as ACPI device with an interrupt resource.
The driver calls for this case the function acpi_get_irq which is only defined on ARM64. On other platforms it returns a hardcoded -EIVAL (error -22).
I tried to hack a workround and used acpi_dev_resource_interrupt to get the IRQ from ACPI. The driver prints some warnings but the probe was successful.
The next problem is the i2c device itself.
The i2c-hid module fails to reset the device(error -61).
As dirty hack I deleted the timeout error, just to create a hidraw device by hid-multitouch but it doesn't report any input(it's detected as HID Input device).
It's possible:
- That there is still something missing in the AMD GPIO driver(especially at the gpio interrupts)
- My hack with the ACPI IRQ is completly crap
- The i2c device needs some magic bits or something to start working
I saw threads and bug reports in the internet with this touchscreen device but there was never a solution for the -61 error.
Of course there are more posibilities but that are the things I found out so far.
Pls tell me if some more info or debug is required.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/22
------------------------------------------------------------------------
On 2018-04-15T00:37:33+00:00 openproggerfreak wrote:
Created attachment 275377
dmesg output from kernel 4.16(with hacks)
dmesg output from kernel with hacks included (the beginning is missing,
maybe a limit of busybox but the relevant output is visible)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/23
------------------------------------------------------------------------
On 2018-04-15T14:52:21+00:00 openproggerfreak wrote:
Created attachment 275381
possible fix for touchscreen
I think I found the problem.
There are 2 ACPI-related bugs which prevents the detection of the touchscreen.
1. As already mentioned, the AMD GPIO driver tries to get an IRQ for GPIO but the ACPI code is missing for x86.
2. The IRQ of the GPIO device is misconfigured. For some reason it sets the IRQ "edge, high" but in the ACPI table it's defined as "level, low".
I made a fix but it's only a temporary workround until someone who have more knowledge of the subsystems can implement it cleaner.
Could someone try this patch on a desktop enviroment? I just tested the output of hidraw which worked.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/24
------------------------------------------------------------------------
On 2018-04-15T17:12:09+00:00 g.fitch wrote:
Hi Lukas,
I tested it with KDE 5 (17.12.3) with one of the drm-next kernels:
Linux tau-ceti 4.16.0-rc7-gc5902206599d-dirty #4 SMP PREEMPT Sun Apr 15 17:37:13 BST 2018 x86_64 AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx AuthenticAMD GNU/Linux
Your patch works fine for the touchscreen on this laptop - touchscreen is detectable and usable with both finger and the supplied pen.
The relevant bit of dmesg is:
Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: ACPI slave is not supported yet
Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: Standard-mode HCNT:LCNT = 642:749
Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: Fast-mode HCNT:LCNT = 132:239
Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: GPIO lookup for consumer scl
Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: using ACPI for GPIO lookup
Apr 15 17:47:11 tau-ceti kernel: acpi AMDI0010:00: GPIO: looking up scl-gpios
Apr 15 17:47:11 tau-ceti kernel: acpi AMDI0010:00: GPIO: looking up scl-gpio
Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: using lookup tables for GPIO lookup
Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: lookup for GPIO scl failed
Apr 15 17:47:11 tau-ceti kernel: i2c-dev: adapter [Synopsys DesignWare I2C adapter] registered as minor 5
Apr 15 17:47:11 tau-ceti kernel: i2c i2c-5: adapter [Synopsys DesignWare I2C adapter] registered
Apr 15 17:47:11 tau-ceti kernel: acpi ELAN0732:00: GPIO: looking up 0 in _CRS
Apr 15 17:47:11 tau-ceti kernel: gpio gpiochip0: Persistence not supported for GPIO 89
Apr 15 17:47:11 tau-ceti kernel: i2c_hid i2c-ELAN0732:00: probe
Apr 15 17:47:11 tau-ceti kernel: i2c i2c-5: master_xfer[0] W, addr=0x10, len=2
Apr 15 17:47:11 tau-ceti kernel: i2c i2c-5: master_xfer[1] R, addr=0x10, len=30
Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: i2c_dw_xfer: msgs: 2
Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: enabled=0x1 stat=0x10
Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: enabled=0x1 stat=0x504
Apr 15 17:47:11 tau-ceti last message repeated 9 times
The patch creates one issue, which is that the following warning now
pops up at boot:
The battery in your keyboard ("ELAN0732:00 04F3:2537") is low, and the
device may turn itself off at any time. Please replace or charge the
battery as soon as possible.
However all other peripherals and buttons work fine, so it's a minor
nuisance.
Thank you for getting us this far!
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/25
------------------------------------------------------------------------
On 2018-04-15T18:37:53+00:00 g.fitch wrote:
Created attachment 275385
config for working system
4.16.0-rc7-gc5902206599d built against sources from
git://people.freedesktop.org/~agd5f/linux --branch drm-next-4.18-wip
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/26
------------------------------------------------------------------------
On 2018-04-15T19:03:18+00:00 openproggerfreak wrote:
(In reply to g.fitch from comment #15)
> Hi Lukas,
>
> I tested it with KDE 5 (17.12.3) with one of the drm-next kernels:
> Linux tau-ceti 4.16.0-rc7-gc5902206599d-dirty #4 SMP PREEMPT Sun Apr 15
> 17:37:13 BST 2018 x86_64 AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx
> AuthenticAMD GNU/Linux
>
>
> Your patch works fine for the touchscreen on this laptop - touchscreen is
> detectable and usable with both finger and the supplied pen.
>
> The relevant bit of dmesg is:
>
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: ACPI slave is
> not supported yet
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: Standard-mode
> HCNT:LCNT = 642:749
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: Fast-mode
> HCNT:LCNT = 132:239
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: GPIO lookup for
> consumer scl
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: using ACPI for
> GPIO lookup
> Apr 15 17:47:11 tau-ceti kernel: acpi AMDI0010:00: GPIO: looking up scl-gpios
> Apr 15 17:47:11 tau-ceti kernel: acpi AMDI0010:00: GPIO: looking up scl-gpio
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: using lookup
> tables for GPIO lookup
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: lookup for GPIO
> scl failed
> Apr 15 17:47:11 tau-ceti kernel: i2c-dev: adapter [Synopsys DesignWare I2C
> adapter] registered as minor 5
> Apr 15 17:47:11 tau-ceti kernel: i2c i2c-5: adapter [Synopsys DesignWare I2C
> adapter] registered
> Apr 15 17:47:11 tau-ceti kernel: acpi ELAN0732:00: GPIO: looking up 0 in _CRS
> Apr 15 17:47:11 tau-ceti kernel: gpio gpiochip0: Persistence not supported
> for GPIO 89
> Apr 15 17:47:11 tau-ceti kernel: i2c_hid i2c-ELAN0732:00: probe
> Apr 15 17:47:11 tau-ceti kernel: i2c i2c-5: master_xfer[0] W, addr=0x10,
> len=2
> Apr 15 17:47:11 tau-ceti kernel: i2c i2c-5: master_xfer[1] R, addr=0x10,
> len=30
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: i2c_dw_xfer:
> msgs: 2
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: enabled=0x1
> stat=0x10
> Apr 15 17:47:11 tau-ceti kernel: i2c_designware AMDI0010:00: enabled=0x1
> stat=0x504
> Apr 15 17:47:11 tau-ceti last message repeated 9 times
>
>
>
> The patch creates one issue, which is that the following warning now pops up
> at boot:
>
> The battery in your keyboard ("ELAN0732:00 04F3:2537") is low, and the
> device may turn itself off at any time. Please replace or charge the battery
> as soon as possible.
>
> However all other peripherals and buttons work fine, so it's a minor
> nuisance.
>
> Thank you for getting us this far!
It looks like upower/i2c-hid think the touchscreen has a battery (which
is false) and reports a invalid power value of 0. When I get a working
desktop I could take a look for it. Meanwhile switching
CONFIG_HID_BATTERY_STRENGTH off should silence the warning if you don't
rely on this feature.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/27
------------------------------------------------------------------------
On 2018-04-25T22:24:08+00:00 brauliobo wrote:
(In reply to Lukas Kahnert from comment #14)
> Created attachment 275381 [details]
> possible fix for touchscreen
>
> I think I found the problem.
> There are 2 ACPI-related bugs which prevents the detection of the
> touchscreen.
>
> 1. As already mentioned, the AMD GPIO driver tries to get an IRQ for GPIO
> but the ACPI code is missing for x86.
> 2. The IRQ of the GPIO device is misconfigured. For some reason it sets the
> IRQ "edge, high" but in the ACPI table it's defined as "level, low".
>
> I made a fix but it's only a temporary workround until someone who have more
> knowledge of the subsystems can implement it cleaner.
> Could someone try this patch on a desktop enviroment? I just tested the
> output of hidraw which worked.
Thanks Lukas, this makes it work!!!
BTW, are you getting hangs/freezes possibly related to the amdgpu
driver?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/28
------------------------------------------------------------------------
On 2018-04-25T22:25:44+00:00 brauliobo wrote:
Also Lukas, can you upstream this patch?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/29
------------------------------------------------------------------------
On 2018-04-26T15:30:47+00:00 openproggerfreak wrote:
@Bráulio I'm sorry but I'm not a kernel developer and this patch is just a dirty hack, which only works on this notebook. On other hardware it could make the system unbootable.
For upstream it needs a cleaner solution.
I already made a bugreport for the IRQ issue:
https://bugzilla.kernel.org/show_bug.cgi?id=199523
For the bug in the AMD GPIO driver it's a missing ACPI feature(I think).
My patch comments out this snippet which triggers the error but I'm
absolutely unsure if it represents a correct behaviour for
(all)x86/amd64 systems. As long the touchscreen and the other hardware
works ok, it should be safe for the notebook.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/30
------------------------------------------------------------------------
On 2018-04-30T10:30:40+00:00 public wrote:
Well, there is another temporary solution and that is fixing the ACPI
table.
I have seen this error for quite a long time, as the A10/A12 Envy X360
Notebooks made in 2016/2017 also have the same error.
Based on the Howto of https://wiki.archlinux.org/index.php/DSDT
you can extract the ACPI table, then increase the version (This number may be different on your installed firmware) number of the first row:
-DefinitionBlock ("", "DSDT", 2, "HPQOEM", "83C6 ", 0x01072009)
+DefinitionBlock ("", "DSDT", 2, "HPQOEM", "83C6 ", 0x01072010)
and change the AMDGPIO part:
@@ -4447,7 +4447,7 @@
{
Name (RBUF, ResourceTemplate ()
{
- Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, )
+ Interrupt (ResourceConsumer, Edge, ActiveHigh, Shared, ,, )
{
0x00000007,
}
If you inject that modified and recompiled ACPI, the same fix should
work for any kernel which supports the ELAN touch controller.
If that can be double checked by the owners, it would be a chance to
push this work back to HP to fix their ACPI table.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/31
------------------------------------------------------------------------
On 2018-04-30T10:40:04+00:00 public wrote:
Created attachment 275675
"Fixing" the ACPI Error the other way around: patching the acpi table
Instead of adding a temporary hack into the kernel, it is also possible
to patch the acpi table which is created by the HP Firmware. This should
work with all kernels and this would show that the main work to do is on
HPs side - not on the kernel developers side.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/32
------------------------------------------------------------------------
On 2018-05-02T14:06:31+00:00 m.kolesinski wrote:
(In reply to Daniel Andersen from comment #22)
> Created attachment 275675 [details]
> "Fixing" the ACPI Error the other way around: patching the acpi table
>
> Instead of adding a temporary hack into the kernel, it is also possible to
> patch the acpi table which is created by the HP Firmware. This should work
> with all kernels and this would show that the main work to do is on HPs side
> - not on the kernel developers side.
I can confirm that hand-patching the ACPI to change the GPIO interrupt
type/level eliminates the same GPIO error on my HP M6AR004DX laptop,
which has an FX-9800P. The ELAN0732 touchscreen still isn't working (on
to the next error)...with the patched ACPI:
[ 8.464309] i2c_hid i2c-ELAN0732:00: i2c-ELAN0732:00 supply vdd not found, using dummy regulator
[ 13.490200] i2c_hid i2c-ELAN0732:00: failed to reset device.
[ 19.676718] i2c_hid i2c-ELAN0732:00: failed to reset device.
[ 25.863360] i2c_hid i2c-ELAN0732:00: failed to reset device.
[ 32.050080] i2c_hid i2c-ELAN0732:00: failed to reset device.
[ 33.063523] i2c_hid i2c-ELAN0732:00: can't add hid device: -61
[ 33.063732] i2c_hid: probe of i2c-ELAN0732:00 failed with error -61
I've been trying to find information on how to fix this darned
touchscreen controller for about a year. The comments in this thread
are the first that have actually made any real progress forward, so
thank you to those that were able to dig into this.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/33
------------------------------------------------------------------------
On 2018-05-02T23:25:17+00:00 signitary wrote:
(In reply to m.kolesinski from comment #23)
> (In reply to Daniel Andersen from comment #22)
> > Created attachment 275675 [details]
> > "Fixing" the ACPI Error the other way around: patching the acpi table
> >
> > Instead of adding a temporary hack into the kernel, it is also possible to
> > patch the acpi table which is created by the HP Firmware. This should work
> > with all kernels and this would show that the main work to do is on HPs
> side
> > - not on the kernel developers side.
>
> I can confirm that hand-patching the ACPI to change the GPIO interrupt
> type/level eliminates the same GPIO error on my HP M6AR004DX laptop, which
> has an FX-9800P. The ELAN0732 touchscreen still isn't working (on to the
> next error)...with the patched ACPI:
>
> [ 8.464309] i2c_hid i2c-ELAN0732:00: i2c-ELAN0732:00 supply vdd not
> found, using dummy regulator
> [ 13.490200] i2c_hid i2c-ELAN0732:00: failed to reset device.
> [ 19.676718] i2c_hid i2c-ELAN0732:00: failed to reset device.
> [ 25.863360] i2c_hid i2c-ELAN0732:00: failed to reset device.
> [ 32.050080] i2c_hid i2c-ELAN0732:00: failed to reset device.
> [ 33.063523] i2c_hid i2c-ELAN0732:00: can't add hid device: -61
> [ 33.063732] i2c_hid: probe of i2c-ELAN0732:00 failed with error -61
>
> I've been trying to find information on how to fix this darned touchscreen
> controller for about a year. The comments in this thread are the first that
> have actually made any real progress forward, so thank you to those that
> were able to dig into this.
Hear hear! Glad to see some progress on this! I've been trying to
resolve the touchscreen issue since my purchase of the Envy x360 a few
weeks ago. Kudos to those of you working on it. I'll be monitoring and
look forward to a solution.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/34
------------------------------------------------------------------------
On 2018-05-07T07:20:35+00:00 suaefar wrote:
Lukas' patch works for me.
The touchscreen works with a patched Linux 4.17-rc3 on a HP ENVY x360
15-bq102ng with Ubuntu 18.04 :) Thank you so much!
Modifying the ACPI table gives me the same result that
m.kolesinski@gmail.com described.
I hope there there will be some generic solution that can be mainlined.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/35
------------------------------------------------------------------------
On 2018-05-11T01:34:46+00:00 signitary wrote:
Lukas' patch also worked for me. Ubuntu 18.04 patched to Linux kernel
4.17-rc4 on my HP Envy x360 15-bq100 Convertible. Thanks to all that
contributed to this issue!
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/36
------------------------------------------------------------------------
On 2018-05-13T02:02:15+00:00 sorace.n wrote:
Hello!
I think I managed to apply Daniel's ACPI table patch, but the
touchscreen still doesn't work. I now get this error in dmesg:
[ 2.284918] i2c_hid i2c-ELAN0732:00: HID over i2c has not been provided an Int IRQ
[ 2.286070] i2c_hid: probe of i2c-ELAN0732:00 failed with error -22
I don't really know what I'm doing (took me like two days to apply the
patch) so I'm sorry if I've done something dumb. I reaaally want to get
this touchscreen working.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/37
------------------------------------------------------------------------
On 2018-05-13T06:58:58+00:00 suaefar wrote:
(In reply to Nicola Sorace from comment #27)
> Hello!
>
> I think I managed to apply Daniel's ACPI table patch, but the touchscreen
> still doesn't work. I now get this error in dmesg:
>
> [ 2.284918] i2c_hid i2c-ELAN0732:00: HID over i2c has not been provided
> an Int IRQ
> [ 2.286070] i2c_hid: probe of i2c-ELAN0732:00 failed with error -22
>
> I don't really know what I'm doing (took me like two days to apply the
> patch) so I'm sorry if I've done something dumb. I reaaally want to get this
> touchscreen working.
The ACPI variant still does not work at the moment.
If you are using Ubuntu I can share the kernel image that I built with you.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/38
------------------------------------------------------------------------
On 2018-05-13T12:32:33+00:00 sorace.n wrote:
(In reply to Marc from comment #28)
> (In reply to Nicola Sorace from comment #27)
> > Hello!
> >
> > I think I managed to apply Daniel's ACPI table patch, but the touchscreen
> > still doesn't work. I now get this error in dmesg:
> >
> > [ 2.284918] i2c_hid i2c-ELAN0732:00: HID over i2c has not been provided
> > an Int IRQ
> > [ 2.286070] i2c_hid: probe of i2c-ELAN0732:00 failed with error -22
> >
> > I don't really know what I'm doing (took me like two days to apply the
> > patch) so I'm sorry if I've done something dumb. I reaaally want to get
> this
> > touchscreen working.
>
> The ACPI variant still does not work at the moment.
> If you are using Ubuntu I can share the kernel image that I built with you.
I'm running Arch unfortunately. Will I have to recompile the kernel with
Lukas' patch applied or is there another way?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/39
------------------------------------------------------------------------
On 2018-05-14T06:36:08+00:00 suaefar wrote:
(In reply to Nicola Sorace from comment #29)
> I'm running Arch unfortunately. Will I have to recompile the kernel with
> Lukas' patch applied or is there another way?
As far as I know, there is no other way, currently.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/40
------------------------------------------------------------------------
On 2018-05-15T18:40:48+00:00 sorace.n wrote:
Lukas' patch worked! Touchscreen worked immediately after booting into
new kernel. Thank you all so much!
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/41
------------------------------------------------------------------------
On 2018-06-17T14:40:17+00:00 ryanmcggg wrote:
Hoping to keep discussion of this issue alive. I can also confirm that
the patch works, though I found it very difficult to implement as
someone who has not done any kernel patching before. And since I am
trying to keep up with kernel updates in the hopes of solving various
other issues, this needs to be done repeatedly. Any hope of a permanent
solution?
I also made a question at AskUbuntu to discuss the other various issues with this laptop:
https://askubuntu.com/questions/1047374/hp-envy-x360-ryzen-5-status-of-known-issues
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/43
------------------------------------------------------------------------
On 2018-06-23T04:08:51+00:00 code.geek2004 wrote:
Is it possible for anyone to link to a compiled version of the kernel
with the fix installed? I am having a heck of a time figuring out how to
get it decompiled and the new code inserted.
Thanks ahead of time.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/44
------------------------------------------------------------------------
On 2018-06-30T05:16:04+00:00 robertdmunn wrote:
(In reply to ryanmcg from comment #32)
> Any hope of a permanent solution?
Someone will need to write a more permanent solution than Lukas' hack
and get it mainlined. Any HP or AMD kernel devs on this bug report? :-)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/45
------------------------------------------------------------------------
On 2018-08-09T22:09:18+00:00 kk1987 wrote:
I tried Lukas' patch on both the latest gen x360 15z and 13z (model is
13z-ag000), and while it sometimes work perfectly, on some boots I get a
"irq 7: nobody cared (try booting with the "irqpoll" option)" line
followed by a "Disabling IRQ #7" message in dmesg, and the touchscreen
stops working.
Booting with "irqpoll" does ensure a working touchscreen, but it seems
to have a negative impact on battery life due to there being 8-9k IRQs
per second constantly. Also, some new warning messages appeared in dmesg
once irqpoll is enabled: a "hpet1: lost 9601 rtc interrupts" message
repeats every 1-2 seconds ("hpet=disable" removes this, but doesn't help
with the high number of IRQs per second), and a "i2c_hid i2c-
ELAN0732:00: i2c_hid_get_input: incomplete report (67/65535)" warning
happens with every touchscreen event.
I have a dual-boot setup with Windows 10, and the issue seems to be
somehow affected by the other OS - rebooting from Windows 10 seems to
guarantee a non-working touchscreen; however, cold booting directly into
Linux (I tried Fedora 28 & Fedora Rawhide) does not guarantee a working
touchscreen.
Did anyone experience the same problem? Or have ideas what the root
cause or any workarounds might be?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/46
------------------------------------------------------------------------
On 2018-08-09T22:13:05+00:00 kk1987 wrote:
Created attachment 277793
DMESG with Lukas' patch and "irq 7: nobody cared" error
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/47
------------------------------------------------------------------------
On 2018-08-09T22:13:37+00:00 kk1987 wrote:
Created attachment 277795
DMESG with Lukas' patch and "irqpoll" option
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/48
------------------------------------------------------------------------
On 2018-08-09T22:50:45+00:00 public wrote:
Created attachment 277797
ACPI from the intel version of the Envy X360 15 (2018/2019 Model "15-CN)
Hi,
Just for comparison the ACPI Table of the 2018/2019 Model of the HP Envy
X360 15-CN0000 ( Intel 8th Gen CPU ). The ELAN config looks a bit more
sophisticated.
Amd 15-BQ Model: Device (TPNL)
Intel 15-CN Model: Device (TPL1)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/49
------------------------------------------------------------------------
On 2018-08-10T15:35:08+00:00 openproggerfreak wrote:
(In reply to kk1987 from comment #35)
> I tried Lukas' patch on both the latest gen x360 15z and 13z (model is
> 13z-ag000), and while it sometimes work perfectly, on some boots I get a
> "irq 7: nobody cared (try booting with the "irqpoll" option)" line followed
> by a "Disabling IRQ #7" message in dmesg, and the touchscreen stops working.
>
> Booting with "irqpoll" does ensure a working touchscreen, but it seems to
> have a negative impact on battery life due to there being 8-9k IRQs per
> second constantly. Also, some new warning messages appeared in dmesg once
> irqpoll is enabled: a "hpet1: lost 9601 rtc interrupts" message repeats
> every 1-2 seconds ("hpet=disable" removes this, but doesn't help with the
> high number of IRQs per second), and a "i2c_hid i2c-ELAN0732:00:
> i2c_hid_get_input: incomplete report (67/65535)" warning happens with every
> touchscreen event.
>
> I have a dual-boot setup with Windows 10, and the issue seems to be somehow
> affected by the other OS - rebooting from Windows 10 seems to guarantee a
> non-working touchscreen; however, cold booting directly into Linux (I tried
> Fedora 28 & Fedora Rawhide) does not guarantee a working touchscreen.
>
> Did anyone experience the same problem? Or have ideas what the root cause or
> any workarounds might be?
this behaviour occurs on my laptop when I reboot from windows. I need to
complete power off/cold boot to workround the irq-issue. Sometimes the
touchpad don't even get detected when I booted windows before. I think
Linux lacks of some reset features for the ACPI IRQs on HP Envy x360.
I'm sorry but I'm too busy for debug the issue. I still hope a kernel
developer comes and creates a real fix :)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/50
------------------------------------------------------------------------
On 2018-08-11T06:43:56+00:00 bram.coenen96 wrote:
Hej!
I'm new to how bug reporting works in Linux and have the same problem.
(Hence me being here) How do we get the attention of a kernel developer?
How can we find who to ask? Is there someone like a "package maintainer"
for this?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/51
------------------------------------------------------------------------
On 2018-08-11T17:12:54+00:00 kk1987 wrote:
(In reply to Lukas Kahnert from comment #39)
> (In reply to kk1987 from comment #35)
> > I tried Lukas' patch on both the latest gen x360 15z and 13z (model is
> > 13z-ag000), and while it sometimes work perfectly, on some boots I get a
> > "irq 7: nobody cared (try booting with the "irqpoll" option)" line followed
> > by a "Disabling IRQ #7" message in dmesg, and the touchscreen stops
> working.
> >
> > Booting with "irqpoll" does ensure a working touchscreen, but it seems to
> > have a negative impact on battery life due to there being 8-9k IRQs per
> > second constantly. Also, some new warning messages appeared in dmesg once
> > irqpoll is enabled: a "hpet1: lost 9601 rtc interrupts" message repeats
> > every 1-2 seconds ("hpet=disable" removes this, but doesn't help with the
> > high number of IRQs per second), and a "i2c_hid i2c-ELAN0732:00:
> > i2c_hid_get_input: incomplete report (67/65535)" warning happens with every
> > touchscreen event.
> >
> > I have a dual-boot setup with Windows 10, and the issue seems to be somehow
> > affected by the other OS - rebooting from Windows 10 seems to guarantee a
> > non-working touchscreen; however, cold booting directly into Linux (I tried
> > Fedora 28 & Fedora Rawhide) does not guarantee a working touchscreen.
> >
> > Did anyone experience the same problem? Or have ideas what the root cause
> or
> > any workarounds might be?
>
> this behaviour occurs on my laptop when I reboot from windows. I need to
> complete power off/cold boot to workround the irq-issue. Sometimes the
> touchpad don't even get detected when I booted windows before. I think Linux
> lacks of some reset features for the ACPI IRQs on HP Envy x360.
>
> I'm sorry but I'm too busy for debug the issue. I still hope a kernel
> developer comes and creates a real fix :)
Hey thanks for the reply and for writing the patch.
In case anyone had the same question, I realized why cold booting didn't
always work for me: it looks like the power cord must be unplugged at
least once when the laptop is powered off. I'm using a USB type-C power
adapter and haven't tried the original adapter, but I suspect it's the
same.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/52
------------------------------------------------------------------------
On 2018-08-14T15:08:56+00:00 killertofu wrote:
(In reply to Bram Coenen from comment #40)
> Hej!
>
> I'm new to how bug reporting works in Linux and have the same problem.
> (Hence me being here) How do we get the attention of a kernel developer? How
> can we find who to ask? Is there someone like a "package maintainer" for
> this?
Just a quick drive-by comment... The kernel has a "MAINTAINERS" file
(see https://www.kernel.org/doc/linux/MAINTAINERS) which lists the
people who maintain its various subsystems. Mika Westerberg might be a
good person to check with since he maintains the I2C ACPI bits.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/53
------------------------------------------------------------------------
On 2018-08-22T09:41:46+00:00 samuel.grahn wrote:
Does Lukas' patch work? with newer kernels?
How would I apply it? Does anyone have a precompiled version (or a
pkgbuild) for arch? Or Ubuntu?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/54
------------------------------------------------------------------------
On 2018-09-01T16:40:49+00:00 crab2313 wrote:
Created attachment 278229
turn on GSI on x86 platform
Can someone test this patch. I think the developer keep the config
disabled on x86 because the code is not well tested and may break the
kernel on some buggy firmware.
https://patchwork.kernel.org/patch/9474763/
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/55
------------------------------------------------------------------------
On 2018-09-02T19:37:12+00:00 maxime wrote:
drivers/acpi/irq.o: In function `acpi_gsi_to_irq':
irq.c:(.text+0x0): multiple definition of `acpi_gsi_to_irq'
arch/x86/kernel/acpi/boot.o:boot.c:(.text+0x1a0): first defined here
drivers/acpi/irq.o: In function `acpi_register_gsi':
irq.c:(.text+0x70): multiple definition of `acpi_register_gsi'
arch/x86/kernel/acpi/boot.o:boot.c:(.text+0x0): first defined here
drivers/acpi/irq.o: In function `acpi_unregister_gsi':
irq.c:(.text+0xf0): multiple definition of `acpi_unregister_gsi'
arch/x86/kernel/acpi/boot.o:boot.c:(.text+0x10): first defined here
drivers/acpi/irq.o:(.bss+0x0): multiple definition of `acpi_irq_model'
arch/x86/kernel/acpi/boot.o:(.bss+0x8): first defined here
make: *** [Makefile:1010: vmlinux] Error 1
After applying the patch I get the above on 4.18.5
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/56
------------------------------------------------------------------------
On 2018-09-03T03:31:59+00:00 Rhiyofromizal wrote:
I apologize if this is the wrong place to post this, but I've following
this thread for a while and it could be related.
I bios update was released on the 29th of August for Ryzen HP Envy x360
13.3 inch version. (I assume it's also Ryzen, though) In the notes it
says it fixes some issues with the touchscreen so I thought it might
help.
Now, I can't even install any flavour of linux (I've tried Ubuntu
18.04.1 and the latest version of Pop!_OS) because as soon as I choose
to boot from the install USB, it'll come up with the scrolling debug
text and then go to a blackscreen where I can do nothing. I assume it's
trying to access specific screen drivers and failing as the fans are
still intermittently speeding up suggesting it's going through the usual
process in the background.
Is there any way to troubleshoot this to find some specific errors?
Apologies if this is unrelated to the current issue at hand and deserves
it's own bug report.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/57
------------------------------------------------------------------------
On 2018-09-03T04:31:12+00:00 Rhiyofromizal wrote:
To be specific, the BIOS update that caused the issue was 'F.19 Rev.A'
It's patch notes list this fix: "Fixes an issue which causes the touch
screen to stop functioning properly'
I'll try and rollback to an earlier BIOS to see if this was my specific
issue.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/58
------------------------------------------------------------------------
On 2018-09-03T18:10:03+00:00 tmoer93 wrote:
@crab
I've added CONFIG_ACPI_GENERIC_GSI=y
to the config and just patched the low/high issue (without the patch of platform.c) and the touchscreen now works.
In theory it now should work with the acpi table modification and compiling with CONFIG_ACPI_GENERIC_GSI=y too.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/59
------------------------------------------------------------------------
On 2018-09-03T20:50:03+00:00 maxime wrote:
@Thomas
could you link the patch(es) you applied?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/60
------------------------------------------------------------------------
On 2018-09-03T22:49:12+00:00 tmoer93 wrote:
@Maxime
I've basically used Lukas' patch , but removed the upper part of it (the one modifying platform.c).
Patching the acpi table as described above does not work. The problem
seems to be that the values from the table are overwritten somehow, so
patching it seems useless?
Then I added the CONFIG_ACPI_GENERIC_GSI=y to the "config" file of the
Arch Linux source
(https://git.archlinux.org/svntogit/packages.git/tree/trunk/config?h=packages/linux).
I don't think that this file should be modified, since its header
comment says so. I think the clean way would be crab2313s way, however
this fails with the errors from above.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/61
------------------------------------------------------------------------
On 2018-09-04T07:38:21+00:00 somnium wrote:
@Sean This bug is not related to this report. But I can help you as I
run into the same problem with the same laptop. The bios update cannot
be reset. I tried and failed. The only way to get this working again is
to use the new Kernel 4.19 which is due for release in october. However
you can boot your linux with the command nomodeset instead of quiet
splash in your grub config (depends on your distro). After you boot
linux, you can install the RC-Version of Kernel 4.19. I use openSUSE
Tumbleweed and they have a certain repo for new Kernels.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/62
------------------------------------------------------------------------
On 2018-09-05T04:30:23+00:00 nosliwnayr wrote:
I was using Lukas' patch successfully until I also updated my BIOS
hoping the "Fixes an issue which causes the touch screen to stop
functioning properly" would fix having to patch the kernel. Now that I'm
on 4.19-rc2 I applied the patch as I had been and the touchscreen isn't
working again, I'm assuming they changed something in the new BIOS that
also breaks that workaround?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/63
------------------------------------------------------------------------
On 2018-09-05T05:56:47+00:00 tmoer93 wrote:
@Ryan, which device? I still can't find a newer bios than the F.17 for my 15-bq101ng .
Would you please provide your dmesg and dsdt?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/64
------------------------------------------------------------------------
On 2018-09-05T20:56:02+00:00 nosliwnayr wrote:
Created attachment 278325
Ryan 15m-cp0012dx F.19 Rev.A dmesg
I am using an Envy x360 15m-cp0012dx. The bios is version F.19 Rev.A
https://support.hp.com/us-en/drivers/selfservice/swdetails/hp-envy-15m-
cp0000-x360-convertible-pc/20270308/model/21925604/swItemId/ob-217449-1
I'm new to this site so I hope this is the right way to comment and
leave the attached files
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/65
------------------------------------------------------------------------
On 2018-09-05T20:57:12+00:00 nosliwnayr wrote:
Created attachment 278327
Ryan 15m-cp0012dx F.19 Rev.A dsdt.dat
Followed the instructions on the arch wiki to create this dsdt. let me
know if that's the wrong file.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/66
------------------------------------------------------------------------
On 2018-10-15T16:04:56+00:00 marco wrote:
Hi! I've been following a bit this discussion: it seems that those patches work, right?
Now, I've also noticed I'm not the only person who is a total noob with linux kernels and their compiling. What I would like to ask is if anyone can make a few steps guide on how to apply the patch and recompile the kernel (and how to install it since I don't think the output would be a standard .deb package, isn't it?).
Thanks a lot in advance!
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/67
------------------------------------------------------------------------
On 2018-10-15T16:19:02+00:00 nosliwnayr wrote:
I'm not too familiar with Ubuntu but https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel would be a good place to start.
In a more general sense you need to get the kernel source, build it while applying the patch, install it in your boot directory, and update your boot loader to point at the new image.
https://askubuntu.com/questions/724900/how-to-apply-kernel-
patches/724909#724909 Here is an example of how to patch the kernel in
more detail on Ubuntu.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/68
------------------------------------------------------------------------
On 2018-10-23T22:58:21+00:00 md1clv wrote:
I'm using a 13-ag0502sa.
When I was running BIOS version F.17 the touchscreen wouldn't work with
any of these patches. I've upgraded to BIOS F.20 and the touchscreen
works with Lukas' patch, but not with a modified DSDT and an unpatched
kernel.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/69
------------------------------------------------------------------------
On 2018-10-30T06:15:03+00:00 luya wrote:
After reading the report, I suggest the original reporter to assign to ACPI Component-table component bug because it is clearly an ACPI error preventing the touchscreen and by extent stylus that comes with HP Envy x360 Ryzen series.
I am adding one of ACPI maintainer on the list to check out.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/70
------------------------------------------------------------------------
On 2018-10-30T06:20:29+00:00 aidanjacobhahn wrote:
Created attachment 279245
attachment-20618-0.html
Would you please clarify which component you are suggesting I add this to?
I do not see one labelled "table"
On Mon, Oct 29, 2018 at 11:15 PM <bugzilla-daemon@bugzilla.kernel.org>
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=198715
>
> Luya Tshimbalanga (luya@fedoraproject.org) changed:
>
> What |Removed |Added
>
> ----------------------------------------------------------------------------
> CC| |lv.zheng@intel.com
>
> --- Comment #59 from Luya Tshimbalanga (luya@fedoraproject.org) ---
> After reading the report, I suggest the original reporter to assign to ACPI
> Component-table component bug because it is clearly an ACPI error
> preventing
> the touchscreen and by extent stylus that comes with HP Envy x360 Ryzen
> series.
> I am adding one of ACPI maintainer on the list to check out.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
> You reported the bug.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/71
------------------------------------------------------------------------
On 2018-10-30T06:21:16+00:00 aidanjacobhahn wrote:
My bad, I have assigned this bug properly.
Thank you!
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/72
------------------------------------------------------------------------
On 2018-10-30T15:59:52+00:00 m.kolesinski wrote:
(In reply to Luya Tshimbalanga from comment #59)
> After reading the report, I suggest the original reporter to assign to ACPI
> Component-table component bug because it is clearly an ACPI error preventing
> the touchscreen and by extent stylus that comes with HP Envy x360 Ryzen
> series.
> I am adding one of ACPI maintainer on the list to check out.
I want to be clear, this bug does not just affect Ryzen series
CPUs/APUs, it also affects the previous gen CPUs, including the FX9800P
in my x360, model m6-ar004dx. It looks like they share the same GPIO
config with respect to the i2c ELAN0734 touchscreen controller.
I would like to make sure whatever fix gets put in fixes all affected
platforms, not just Ryzen. I will gladly test driver/kernel patches
and/or ACPI/DSDT patches. I can also post my DSDT if it helps, it was
very similar with regard to this GPIO to the one already discussed.
I have two identical laptops I can test with.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/73
------------------------------------------------------------------------
On 2018-10-30T16:00:23+00:00 m.kolesinski wrote:
(In reply to Luya Tshimbalanga from comment #59)
> After reading the report, I suggest the original reporter to assign to ACPI
> Component-table component bug because it is clearly an ACPI error preventing
> the touchscreen and by extent stylus that comes with HP Envy x360 Ryzen
> series.
> I am adding one of ACPI maintainer on the list to check out.
I want to be clear, this bug does not just affect Ryzen series
CPUs/APUs, it also affects the previous gen CPUs, including the FX9800P
in my x360, model m6-ar004dx. It looks like they share the same GPIO
config with respect to the i2c ELAN0734 touchscreen controller.
I would like to make sure whatever fix gets put in fixes all affected
platforms, not just Ryzen. I will gladly test driver/kernel patches
and/or ACPI/DSDT patches. I can also post my DSDT if it helps, it was
very similar with regard to this GPIO to the one already discussed.
I have two identical laptops I can test with.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/74
------------------------------------------------------------------------
On 2018-10-30T17:19:11+00:00 luya wrote:
(In reply to m.kolesinski from comment #63)
> I want to be clear, this bug does not just affect Ryzen series CPUs/APUs, it
> also affects the previous gen CPUs, including the FX9800P in my x360, model
> m6-ar004dx. It looks like they share the same GPIO config with respect to
> the i2c ELAN0734 touchscreen controller.
>
Should the title renamed something like "Misconfigured ACPI config-table broke Elan touchscreen on HP Envy x360 series" for better clarification?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/75
------------------------------------------------------------------------
On 2018-10-31T07:24:13+00:00 aidanjacobhahn wrote:
Updated title to reflect that this bug affects multiple HP x360 machines
running AMD chips
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/76
------------------------------------------------------------------------
On 2018-11-03T09:56:59+00:00 luya wrote:
I just found a documentation for debugging:
https://www.kernel.org/doc/Documentation/acpi/debug.txt
Enable kernel debugging and add the parameter like
"acpi.debug_layer=0x000008 acpi.debug_level=0x4" to display table
information. Should there be a better parameter,please post it.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/comments/78
** Changed in: kernel
Status: Unknown => Confirmed
** Changed in: kernel
Importance: Unknown => Medium
** Bug watch added: github.com/linuxwacom/wacom-hid-descriptors/issues #12
https://github.com/linuxwacom/wacom-hid-descriptors/issues/12
** Bug watch added: Linux Kernel Bug Tracker #199523
https://bugzilla.kernel.org/show_bug.cgi?id=199523
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1752437
Title:
[HP ENVY x360 - 15-bq102ng] Touchscreen does not work
Status in linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
The touch screen on my HP ENVY x360 15-bq102ng does not work with
stock kernel or with mainline kernel 4.16-rc3.
marc@snapbug:~$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Video Bus id=8 [slave keyboard (3)]
↳ Power Button id=9 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
↳ HP Wireless hotkeys id=14 [slave keyboard (3)]
↳ HP WMI hotkeys id=15 [slave keyboard (3)]
↳ HP Wide Vision FHD Camera: HP I id=11 [slave keyboard (3)]
↳ HP Wide Vision FHD Camera: HP W id=10 [slave keyboard (3)]
WORKAROUND: Use the following patch with 4.17-rc3:
https://bugzilla.kernel.org/attachment.cgi?id=275381
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
Uname: Linux 4.16.0-041600rc2-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
BootLog:
No key available with this passphrase.
/dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 blocks
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 28 22:34:50 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device [103c:83c6]
InstallationDate: Installed on 2018-01-16 (42 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: HP HP ENVY x360 Convertible 15-bq1xx
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/26/2018
dmi.bios.vendor: AMI
dmi.bios.version: F.16
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 83C6
dmi.board.vendor: HP
dmi.board.version: 63.18
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Envy
dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.85-4~a~padoka0
version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel/+bug/1752437/+subscriptions
Комментариев нет:
Отправить комментарий