Launchpad has imported 165 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=199911.
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-06-03T17:46:08+00:00 soundhermit wrote:
Razer Blade 15 2018 touchpad support [1532:0233]
Bus 001 Device 005: ID 1532:0233 Razer USA, Ltd
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1532 Razer USA, Ltd
idProduct 0x0233
bcdDevice 2.00
iManufacturer 1 Razer
iProduct 2 Razer Blade
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0054
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 1 Keyboard
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 61
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0
bInterfaceProtocol 1 Keyboard
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 159
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 94
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 1
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0000
(Bus Powered)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/0
------------------------------------------------------------------------
On 2018-06-24T18:56:55+00:00 soundhermit wrote:
Created attachment 276785
Files collected during investigation
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/1
------------------------------------------------------------------------
On 2018-06-24T18:57:54+00:00 soundhermit wrote:
Investigation done by alkersan
-----------------------------------
The touchpad of the Razer Blade 15 (2018) laptop is unresponsive after
boot.
After shallow investigation of hardware identifiers, the touchpad seems
to be present the USB and I2C buses.
The USB part is visible as a HID device and includes a mouse interface, but it probably handles just the keys of the laptop, including the keyboard, media/function buttons and RGB backlight programming.
The detailed output of lsusb is attached. It has an ID [1532:0233] where 1532 stands for Razer Inc. and 0233 is a yet unknown device. Similarly to 0232, which Openrazer project identifies as a keybard of the previous 2017 Blade laptop (https://github.com/openrazer/openrazer/blob/master/driver/razerkbd_driver.h#L143). Thus a USB HID part is probably out of interest for now.
The i2c interface is presumably responsible for the touch positioning.
It's mentioned in the dmesg.log surrounded with the vdd supply and
interrupt errors of the so called i2c-1A582000 device. The i2c bus tree
and the i2cdetect output is attached.
Another interesting detail lies in the touchpad behavior in the Windows
OS. The laptop is bundled with a plenty of drivers and is fully
functional from the factory. But after the clean Windows installation -
touchpad is unresponsive also. The required driver to enable the
touchpad is an Intel Serial IO Driver
(http://drivers.razersupport.com//index.php?_m=downloads&_a=viewdownload&downloaditemid=2878&nav=0,350,765,766).
It's comprised of 4 parts: GPIO, I2C, SPI and UART. Only GPIO and I2C
are required for the touchpad to become responsive without reboot (INF
files of these drivers are attached). Right after installation Windows
detects the touchpad as an I2C HID Device and HID-Complaint touch pad
(the device manager screenshots are attached). Both devices has a id
1A58:2000, appeared previosly in the kernel log.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/2
------------------------------------------------------------------------
On 2018-06-24T19:07:05+00:00 soundhermit wrote:
Created attachment 276789
dmesg
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/3
------------------------------------------------------------------------
On 2018-06-24T19:07:28+00:00 soundhermit wrote:
Created attachment 276791
i2cdetect
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/4
------------------------------------------------------------------------
On 2018-06-24T19:07:56+00:00 soundhermit wrote:
Created attachment 276793
i2c_hw_id
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/5
------------------------------------------------------------------------
On 2018-06-24T19:08:25+00:00 soundhermit wrote:
Created attachment 276795
windows_gpio2_inf
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/6
------------------------------------------------------------------------
On 2018-06-24T19:08:42+00:00 soundhermit wrote:
Created attachment 276797
windows_i2c_inf
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/7
------------------------------------------------------------------------
On 2018-06-24T19:08:56+00:00 soundhermit wrote:
Created attachment 276799
lsusb
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/8
------------------------------------------------------------------------
On 2018-06-24T19:09:15+00:00 soundhermit wrote:
Created attachment 276801
touchpad_hw_id
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/9
------------------------------------------------------------------------
On 2018-06-29T06:13:22+00:00 soundhermit wrote:
Created attachment 277029
acpi dump
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/10
------------------------------------------------------------------------
On 2018-06-29T10:01:53+00:00 mika.westerberg wrote:
Can you also attach content of /sys/kernel/debug/pinctrl/INT3450:00/pins
and /sys/kernel/debug/pinctrl/INT3450:00/gpio-ranges?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/11
------------------------------------------------------------------------
On 2018-06-29T13:32:09+00:00 soundhermit wrote:
Created attachment 277051
pins
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/12
------------------------------------------------------------------------
On 2018-06-29T13:32:26+00:00 soundhermit wrote:
Created attachment 277053
gpio-ranges
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/13
------------------------------------------------------------------------
On 2018-06-29T13:32:45+00:00 soundhermit wrote:
added pins and gpio-ranges
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/14
------------------------------------------------------------------------
On 2018-06-29T14:13:57+00:00 mika.westerberg wrote:
Created attachment 277055
Add more debugging to gpiolib-acpi.c
Can you try the attached patch and then attach dmesg again? It should
print the GPIO number we get from the BIOS.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/15
------------------------------------------------------------------------
On 2018-06-29T14:34:05+00:00 soundhermit wrote:
Created attachment 277057
dmesg_with gpiolib-acpi_patch
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/16
------------------------------------------------------------------------
On 2018-06-29T16:12:37+00:00 soundhermit wrote:
pin = 100
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/17
------------------------------------------------------------------------
On 2018-07-02T23:12:17+00:00 andy.shevchenko wrote:
This pin is configured by BIOS as GPIO direct interrupt to IOAPIC (SCI mode).
So, there is coupled GpioInt() and Interrupt() resources. If I read DSDT correctly the IRQ resource, which must be used, depends on the setting of some internal variable. My understanding that, since the pin is configured to generate SCI, the driver should respect BIOS settings.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/18
------------------------------------------------------------------------
On 2018-07-03T01:44:45+00:00 andy.shevchenko wrote:
Okay, more investigation on the message "flag is output". It seems that
in the driver we missed the fact of IRQ to pin translation in one case.
That's why we are actually talking to hadrware pin 100 (ACPI 129)
instead of pin 79 (ACPI 100). And that pin is indeed configured as
output.
But I need to confirm this, because it's early morning and I even
managed to send a patch to mailing list (related to this, but not
fixing) with a completely wrong commit message. Need some sleep for
sure.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/19
------------------------------------------------------------------------
On 2018-07-03T01:45:41+00:00 andy.shevchenko wrote:
Take the bug as it seems to be related to our GPIO/pinctrl driver.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/20
------------------------------------------------------------------------
On 2018-07-03T01:59:53+00:00 soundhermit wrote:
Let me know if you need me to try out anything.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/21
------------------------------------------------------------------------
On 2018-07-03T23:50:25+00:00 andy.shevchenko wrote:
(In reply to jamir from comment #21)
> Let me know if you need me to try out anything.
Can you add to the top of gpiochip_lock_as_irq() the following hack and
try to boot again (we need dmesg with 'ignore_loglevel' added to the
kernel command line):
if (offset == 100)
offset = 79;
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/22
------------------------------------------------------------------------
On 2018-07-04T00:02:32+00:00 soundhermit wrote:
Created attachment 277159
dmesg with overriding pin 100 with 79
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/23
------------------------------------------------------------------------
On 2018-07-04T00:07:15+00:00 soundhermit wrote:
the touchpad is still not functional I have attached the dmesg after the
change.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/24
------------------------------------------------------------------------
On 2018-07-04T00:27:17+00:00 soundhermit wrote:
The error code is different this time though -
i2c_hid: probe of i2c-1A582000:00 failed with error -1 instead of -22
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/25
------------------------------------------------------------------------
On 2018-07-06T11:14:52+00:00 mika.westerberg wrote:
Created attachment 277217
Skip ACPI check in pintctrl driver
Can you try the attached patch and see if anything changes? Then attach
dmesg again.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/26
------------------------------------------------------------------------
On 2018-07-06T14:07:21+00:00 soundhermit wrote:
Created attachment 277227
dmesg_skip_acpi_check_pinctrl
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/27
------------------------------------------------------------------------
On 2018-07-06T14:43:41+00:00 andy.shevchenko wrote:
(In reply to jamir from comment #27)
> Created attachment 277227 [details]
> dmesg_skip_acpi_check_pinctrl
Thanks, it looks like we missed to ask you to apply both
- patch from comment #22, AND
- patch from comment #26
together and try.
Sorry it takes more effort than we assumed.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/28
------------------------------------------------------------------------
On 2018-07-06T15:04:07+00:00 soundhermit wrote:
gpiochip_lock_as_irq() doesn't exist in gpiolib-acpi.c anymore on rc3.
Do you know where this function moved to? I see a call from the gpiolib-
acpi.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/29
------------------------------------------------------------------------
On 2018-07-06T15:07:35+00:00 soundhermit wrote:
found it I think its in gpiolib.c
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/30
------------------------------------------------------------------------
On 2018-07-06T15:14:56+00:00 soundhermit wrote:
Created attachment 277229
dmesg with 22 and 26 - works
Wow, the touchpad is working!!!
Touchpad mouse movement functional.
Touchpad left mouse button functional.
Touchpad right mouse button functional.
Touchpad 2 finger scroll functional.
Touchpad tap to click, not functional, don't see a setting on gnome settings to enable that.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/31
------------------------------------------------------------------------
On 2018-07-06T22:47:17+00:00 andy.shevchenko wrote:
There are two issues at once that's why two hacks. But to see picture better, can you please attach cat /proc/interrupt output after just boot, and after a bit so events, like touching, doing some gestures?
Also attach a pins file again with driver loaded.
All above from _working_ case, thanks!
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/32
------------------------------------------------------------------------
On 2018-07-06T23:15:14+00:00 joe wrote:
Can these patches be backported to 4.17 or are there other things in
4.18 that are necessary for the fix?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/33
------------------------------------------------------------------------
On 2018-07-07T00:22:55+00:00 soundhermit wrote:
Created attachment 277261
Interrupts after boot
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/34
------------------------------------------------------------------------
On 2018-07-07T00:23:23+00:00 soundhermit wrote:
Created attachment 277263
Interrupts after mouse events
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/35
------------------------------------------------------------------------
On 2018-07-07T00:23:55+00:00 soundhermit wrote:
Created attachment 277265
Pins with driver loaded
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/36
------------------------------------------------------------------------
On 2018-07-07T00:24:10+00:00 soundhermit wrote:
(In reply to Andy Shevchenko from comment #32)
> There are two issues at once that's why two hacks. But to see picture
> better, can you please attach cat /proc/interrupt output after just boot,
> and after a bit so events, like touching, doing some gestures?
> Also attach a pins file again with driver loaded.
>
> All above from _working_ case, thanks!
done.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/37
------------------------------------------------------------------------
On 2018-07-07T00:48:45+00:00 soundhermit wrote:
More observations:
I see lockups sometimes when restarting just before X starts (I have
seen it now 4 times). I have to hold the power button and reboot and
then the next time it detects the touchpad fine.
When it is locks up I see "supply vdd not found, using dummy regulator"
message.
When I enable wayland in GDM (custom.conf) and gnome shell I see the option "tap to click" and enabling it enables the tap to click.
I was xorg for two reasons mutter/clutter caps the refresh rate to 60.
and open broadcasting app doesn't record wayland composited desktop
(shows black screen).
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/38
------------------------------------------------------------------------
On 2018-07-07T02:48:52+00:00 soundhermit wrote:
one more data point.
The lockup only seems to occur when I reboot the laptop. If I shutdown
and power it back on I've been able to successfully start the OS like 7
times in a row without lockup.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/39
------------------------------------------------------------------------
On 2018-07-09T09:20:34+00:00 mika.westerberg wrote:
So I think the touchpad locking is most likely not related and for that
you should file another bugzilla entry.
Regarding the touchpad interrupt via GPIO we have two issues:
- BIOS has configured the pin incorrectly to be owned by ACPI. Regardless it
seems that we can just skip checking for that bit in Linux driver as well
because interrupts still work (we may want to log something to dmesg about
this, though).
- We do not map hwirq correctly in gpiochip_lock_as_irq() when
get_direction() is called.
We will work a proper fix for the two but it may take some time as I
will be on vacation next 3 weeks.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/40
------------------------------------------------------------------------
On 2018-07-09T13:58:56+00:00 soundhermit wrote:
Sounds good.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/41
------------------------------------------------------------------------
On 2018-07-23T12:39:51+00:00 andy.shevchenko wrote:
Summon Hans WRT https://bugzilla.redhat.com/show_bug.cgi?id=1543769#c117
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/43
------------------------------------------------------------------------
On 2018-07-24T21:04:46+00:00 andy.shevchenko wrote:
Created attachment 277483
Translation fix for gpiochip_lock_as_irq()
@jamir, can you, please, test this patch instead of one in comment #22
(you still need another one from comment #26!)?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/44
------------------------------------------------------------------------
On 2018-07-25T01:29:51+00:00 soundhermit wrote:
Created attachment 277485
dmesg after translation fix
The touchpad is functional after the translation fix.
dmesg captured with only patch applied to the pinctrl-intel.c.
Started with a clean tree without the below hack.
if (offset == 100)
offset = 79;
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/45
------------------------------------------------------------------------
On 2018-07-25T09:13:14+00:00 andy.shevchenko wrote:
Let me understand, you applied the only translation patch _without_ one
from comment #26 and everything still works?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/46
------------------------------------------------------------------------
On 2018-07-25T12:59:12+00:00 soundhermit wrote:
I applied the translation and skipping ACPI check both.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/47
------------------------------------------------------------------------
On 2018-07-25T15:16:25+00:00 mika.westerberg wrote:
Just to be sure. You only have one patch applied and it is the
translation from from Andy in comment #43? You don't have the patch in
comment #26 applied?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/48
------------------------------------------------------------------------
On 2018-07-25T15:24:57+00:00 soundhermit wrote:
Created attachment 277507
Patch file used to test.
I am attaching the patch file I used to test.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/49
------------------------------------------------------------------------
On 2018-07-25T15:41:35+00:00 andy.shevchenko wrote:
(In reply to jamir from comment #48)
> Created attachment 277507 [details]
> Patch file used to test.
>
> I am attaching the patch file I used to test.
Thanks for your patience! Now it's clear.
The translation patch has been sent to upstream today (we expect
maintainer take it soon). The ACPI hack needs to be thought about a bit
longer. We are waiting for some elaboration internally from other team.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/50
------------------------------------------------------------------------
On 2018-07-25T16:54:34+00:00 2009 wrote:
Hello
Andy Shevchenko said in a thread on redhat bugtracker that this could
maybe also the solution for my problem:
The Hardware is different:
ASUS GL703GE Laptop
if you need more data i will be pleased to submit logfiles or whatever
needet. i could also open a teamviewer session or something like that if
this helps resolving the problem on my hardware.
in windows and bios the touchpad works but not on linux, not on debian,
not on fedora, not on ubuntu...
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/51
------------------------------------------------------------------------
On 2018-07-25T16:59:45+00:00 andy.shevchenko wrote:
(In reply to Marc Landolt from comment #50)
> if you need more data i will be pleased to submit logfiles or whatever
> needet.
Provide the same set of data we asked from @jamir, i.e. gpio-ranges,
pins, and /proc/interrupts files.
Meanwhile try to apply just one patch @jamir attached in comment #48.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/52
------------------------------------------------------------------------
On 2018-07-25T17:15:03+00:00 2009 wrote:
Created attachment 277509
Hardware ID
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/53
------------------------------------------------------------------------
On 2018-07-25T17:17:26+00:00 2009 wrote:
Created attachment 277511
dmesg from ASUS GL703GE
with modifications
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/54
------------------------------------------------------------------------
On 2018-07-25T17:17:50+00:00 2009 wrote:
Created attachment 277513
dmesg from ASUS GL703GE
without modifications
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/55
------------------------------------------------------------------------
On 2018-07-25T17:18:24+00:00 2009 wrote:
Created attachment 277515
i2cdetect from ASUS GL703GE
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/56
------------------------------------------------------------------------
On 2018-07-25T17:19:44+00:00 2009 wrote:
how to generate the gpio-ranges file?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/57
------------------------------------------------------------------------
On 2018-07-25T17:35:13+00:00 2009 wrote:
Created attachment 277517
/proc/interrupts from ASUS GL703GE
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/58
------------------------------------------------------------------------
On 2018-07-25T17:40:24+00:00 2009 wrote:
Created attachment 277519
inteltool from ASUS GL703GE
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/59
------------------------------------------------------------------------
On 2018-07-25T17:51:54+00:00 andy.shevchenko wrote:
(In reply to Marc Landolt from comment #56)
> how to generate the gpio-ranges file?
It's under /sys/kernel/debug/pinctrl/INT3450:00/ There also most
important one called pins. You need to mount debugged before looking for
them.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/60
------------------------------------------------------------------------
On 2018-07-25T18:27:55+00:00 2009 wrote:
Created attachment 277527
gpio pins from GL703GE
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/61
------------------------------------------------------------------------
On 2018-07-25T18:28:20+00:00 2009 wrote:
Created attachment 277529
gpio ranges from GL703GE
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/62
------------------------------------------------------------------------
On 2018-07-25T18:28:45+00:00 2009 wrote:
the 4.18.rc6 with the patch you said is compiled now, boots but no
touchpad
[ 13.206001] idma64 idma64.0: Found Intel integrated DMA 64-bit
[ 13.209068] cannonlake-pinctrl INT3450:00: pin 225 for irq (hwirq=297)
[ 13.209126] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator
[ 13.210398] gpio gpiochip0: (INT3450:00): gpiochip_lock_as_irq: tried to flag a GPIO set as output for IRQ
[ 13.210424] cannonlake-pinctrl INT3450:00: unable to lock HW IRQ 225 for IRQ
[ 13.210440] genirq: Failed to request resources for ELAN1200:00 (irq 138) on irqchip intel-gpio
[ 13.210468] i2c_hid i2c-ELAN1200:00: Could not register for ELAN1200:00 interrupt, irq = 138, ret = -22
[ 13.210486] i2c_hid: probe of i2c-ELAN1200:00 failed with error -22
[ 13.212565] mei_me 0000:00:16.0: enabling device (0000 -> 0002)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/63
------------------------------------------------------------------------
On 2018-07-25T18:47:49+00:00 andy.shevchenko wrote:
(In reply to Marc Landolt from comment #62)
> the 4.18.rc6 with the patch you said is compiled now, boots but no touchpad
>
> [ 13.206001] idma64 idma64.0: Found Intel integrated DMA 64-bit
> [ 13.209068] cannonlake-pinctrl INT3450:00: pin 225 for irq (hwirq=297)
> [ 13.209126] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not
> found, using dummy regulator
> [ 13.210398] gpio gpiochip0: (INT3450:00): gpiochip_lock_as_irq: tried to
> flag a GPIO set as output for IRQ
> [ 13.210424] cannonlake-pinctrl INT3450:00: unable to lock HW IRQ 225 for
> IRQ
> [ 13.210440] genirq: Failed to request resources for ELAN1200:00 (irq 138)
> on irqchip intel-gpio
> [ 13.210468] i2c_hid i2c-ELAN1200:00: Could not register for ELAN1200:00
> interrupt, irq = 138, ret = -22
> [ 13.210486] i2c_hid: probe of i2c-ELAN1200:00 failed with error -22
> [ 13.212565] mei_me 0000:00:16.0: enabling device (0000 -> 0002)
Thanks.
What we need is the output file of `acpidump -o table.dat` and output of
the command `grep -H 15 /sys/bus/acpi/devices/*/status`. Also, please,
check BIOS settings: if anything has choice between linux and windows,
choose windows.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/64
------------------------------------------------------------------------
On 2018-07-25T18:49:03+00:00 2009 wrote:
Created attachment 277531
acpidump -o table.dat from GL703GE
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/65
------------------------------------------------------------------------
On 2018-07-25T18:49:48+00:00 2009 wrote:
Created attachment 277533
grep -H 15 /sys/bus/acpi/devices/*/status from GL703GE
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/66
------------------------------------------------------------------------
On 2018-07-26T14:09:32+00:00 andy.shevchenko wrote:
Created attachment 277553
Fix community ordering for H variant
Another patch for Cannonlake PCH-H.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/67
------------------------------------------------------------------------
On 2018-07-26T14:12:07+00:00 andy.shevchenko wrote:
(In reply to Marc Landolt from comment #64)
> Created attachment 277531 [details]
> acpidump -o table.dat from GL703GE
Thanks, that is helpful.
Can you test another patch from comment #66 (on top of the one from comment #48) and share the
- output of `cat /proc/interrupts /proc/iomem`
- *gpio-ranges* and *pins* files
?
@jamir, if you can test that patch as well to see it doesn't break your
case. Thanks!
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/68
------------------------------------------------------------------------
On 2018-07-26T16:30:35+00:00 2009 wrote:
(In reply to Andy Shevchenko from comment #66)
> Created attachment 277553 [details]
> Fix community ordering for H variant
>
> Another patch for Cannonlake PCH-H.
Yay, GREAT, Andy you're a Genius, the Touchpad is working :)
After Downloading Kernel 4.18.RC6, patching with
https://bugzilla.kernel.org/attachment.cgi?id=277507&action=diff and
https://bugzilla.kernel.org/attachment.cgi?id=277553&action=diff it's
working.
-Tap to click works
-2 Finger scroll works (only Natural Scrolling, always on)
-2 Finger right click works
-left mouse button works
-right mouse button does not work but with 2 finger click it works
-Edge Scrolling does not work
-it disconects from time to time (rmmod -r hid-multitouch && modprobe hid-multitouch helps)
shall I test other patches and do you still need the outputs from
Comment 67 (interrupts, iomem, ranges, pins?
With kind regards and many thanks so far
Marc Landolt
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/69
------------------------------------------------------------------------
On 2018-07-26T16:46:24+00:00 andy.shevchenko wrote:
(In reply to Marc Landolt from comment #68)
> (In reply to Andy Shevchenko from comment #66)
> > Created attachment 277553 [details]
> > Fix community ordering for H variant
> >
> > Another patch for Cannonlake PCH-H.
>
> Yay, GREAT, Andy you're a Genius, the Touchpad is working :)
Sorry it wasn't working from the day 1.
> shall I test other patches
Nothing to test for now. There are three problems in your case and one
of them doesn't clear yet (in a sense of root cause). That's, we are
discussing internally and will come up with workaround / solution later
on.
> and do you still need the outputs from Comment 67
> (interrupts, iomem, ranges, pins?
Yes, please.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/70
------------------------------------------------------------------------
On 2018-07-26T16:55:18+00:00 2009 wrote:
Created attachment 277555
Interrupts after working patch from ASUS GL703GE
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/71
------------------------------------------------------------------------
On 2018-07-26T16:55:39+00:00 2009 wrote:
Created attachment 277557
iomem after working patch from ASUS GL703GE
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/72
------------------------------------------------------------------------
On 2018-07-26T16:56:02+00:00 2009 wrote:
Created attachment 277559
gpio-pins after working patch from ASUS GL703GE
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/73
------------------------------------------------------------------------
On 2018-07-26T16:56:27+00:00 2009 wrote:
Created attachment 277561
gpio-ranges after working patch from ASUS GL703GE
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/74
------------------------------------------------------------------------
On 2018-07-26T19:16:55+00:00 2009 wrote:
There are still some issues, I guess it are the same issues that are
also on the GL503VS and maybe in a different part of the kernel (not
sure):
Problems:
-random lockups
-disconnection (workaround rmmod && insmod hid-multitouch)
-the physical button (the whole touchpad) is not debounced, if you click once it does multiple clicks (workaround: use tap to click)
False Acused Problems:
-non-natural 2 finger scrolling works after reboot
please tell me if i shall test other things on my GL703GE...
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/75
------------------------------------------------------------------------
On 2018-07-26T19:50:04+00:00 andy.shevchenko wrote:
(In reply to Marc Landolt from comment #74)
> please tell me if i shall test other things on my GL703GE...
Marc, this bug is solely about GPIO issue. As Mika stated in comment
#40, please create another one, or find if it's already created against
HID subsystem.
Check what @jamir has, it perhaps similar to what you are esperiencing.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/76
------------------------------------------------------------------------
On 2018-07-26T23:04:15+00:00 2009 wrote:
ok, I did not find jamir's but so I opened one here:
https://bugzilla.kernel.org/show_bug.cgi?id=200663
thank you for your help :)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/77
------------------------------------------------------------------------
On 2018-08-05T14:55:56+00:00 gschram wrote:
(In reply to Andy Shevchenko from comment #49)
> (In reply to jamir from comment #48)
> > Created attachment 277507 [details]
> > Patch file used to test.
> >
> > I am attaching the patch file I used to test.
>
> Thanks for your patience! Now it's clear.
>
> The translation patch has been sent to upstream today (we expect maintainer
> take it soon). The ACPI hack needs to be thought about a bit longer. We are
> waiting for some elaboration internally from other team.
This patch also fixes the touchscreen (and pen) and touchpad (only works
after a hibernation) on the newly released hp zbook studio x360
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/78
------------------------------------------------------------------------
On 2018-08-08T23:01:23+00:00 simon.detheridge wrote:
I have an almost-identical problem with a Tong Fang GK5CN5Z laptop
(branded as a PC Specialist Recoil II)
The symptoms appear very similar, but using the patches here the
touchpad still does not work, although the error message changes.
I got a very similar "cannonlake-pinctrl" "pin x cannot be used as IRQ"
message. I installed 4.18_rc8 and applied the patches here, but I now
get a different error and the device still does not show up.
I see:
[ 6.813578] usbhid 1-6:1.0: couldn't find an input interrupt endpoint
and
[ 20.468857] i2c_hid i2c-UNIW0001:00: failed to reset device.
...
[ 39.741876] i2c_hid i2c-UNIW0001:00: can't add hid device: -61
Not sure what further information is required, but I'll attach the full
dmesg output.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/79
------------------------------------------------------------------------
On 2018-08-08T23:02:17+00:00 simon.detheridge wrote:
Created attachment 277765
post-patch dmesg output for GK5CN5Z
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/80
------------------------------------------------------------------------
On 2018-08-09T08:35:50+00:00 mika.westerberg wrote:
To me this looks like a different issue (HID reset does not get
through). Can you attach /proc/interrupts and /sys/kernel/debug/gpio
here just that we can check whether it is related to GPIO at all?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/81
------------------------------------------------------------------------
On 2018-08-09T09:33:11+00:00 simon.detheridge wrote:
OK, I shall add these. I'll also add the dmesg from before the patch for
reference... The error line is:
[ 15.386072] cannonlake-pinctrl INT3450:00: pin 208 cannot be used as
IRQ
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/82
------------------------------------------------------------------------
On 2018-08-09T09:34:39+00:00 simon.detheridge wrote:
Created attachment 277783
pre-patch dmesg output for GK5CN5Z
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/83
------------------------------------------------------------------------
On 2018-08-09T09:35:23+00:00 simon.detheridge wrote:
Created attachment 277785
/proc/interrupts on GK5CN5Z
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/84
------------------------------------------------------------------------
On 2018-08-09T09:36:05+00:00 simon.detheridge wrote:
Created attachment 277787
/sys/kernel/debug/gpio on GK5CN5Z
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/85
------------------------------------------------------------------------
On 2018-08-09T12:30:19+00:00 simon.detheridge wrote:
If it helps, I tried using the laptop buttons to enable/disable the
touchpad. Nothing happens, but dmesg says this:
[ 254.890450] i801_smbus 0000:00:1f.4: BIOS is accessing SMBus registers
[ 254.890459] i801_smbus 0000:00:1f.4: Driver SMBus register access inhibited
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/86
------------------------------------------------------------------------
On 2018-08-09T16:14:32+00:00 andy.shevchenko wrote:
(In reply to Simon Detheridge from comment #81)
> OK, I shall add these. I'll also add the dmesg from before the patch for
> reference... The error line is:
>
> [ 15.386072] cannonlake-pinctrl INT3450:00: pin 208 cannot be used as IRQ
Can you attach /sys/kernel/debug/pinctrl/INT3450:00/pins for *patched*
version?
P.S. For now it looks like the GPIO problem gone, but please attach the
file to make us sure. If it's the case, you would need to create another
bug regarding to HID device communication issue.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/87
------------------------------------------------------------------------
On 2018-08-09T16:29:00+00:00 simon.detheridge wrote:
Created attachment 277791
/sys/kernel/debug/pinctrl/INT3450:00/pins on GK5CN5Z post-patch
Sure, here's the output
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/88
------------------------------------------------------------------------
On 2018-08-09T16:43:36+00:00 andy.shevchenko wrote:
(In reply to Simon Detheridge from comment #87)
> Created attachment 277791 [details]
> /sys/kernel/debug/pinctrl/INT3450:00/pins on GK5CN5Z post-patch
>
> Sure, here's the output
Thanks. I don't see any issues with GPIO now.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/89
------------------------------------------------------------------------
On 2018-08-10T13:14:58+00:00 simon.detheridge wrote:
Raised as bug #200787 - if there's anything else I should add to that
let me know, I'm not really sure what I'm doing with this.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/90
------------------------------------------------------------------------
On 2018-08-21T21:22:18+00:00 jon.snow wrote:
I'm facing the same exact problem as Simon with the Tong Fang GK5CN5Z
model on Ubuntu 18.04. Is there any update concerning the fix? Thanks!
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/91
------------------------------------------------------------------------
On 2018-08-21T21:40:16+00:00 simon.detheridge wrote:
@Jon are you comfortable building your own kernel? It would be good to
know if your experience is the same as mine in bug #200787 once the
patches from this bug are applied.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/92
------------------------------------------------------------------------
On 2018-08-24T10:53:48+00:00 ameynarkhede02 wrote:
(In reply to Marc Landolt from comment #68)
> (In reply to Andy Shevchenko from comment #66)
> > Created attachment 277553 [details]
> > Fix community ordering for H variant
> >
> > Another patch for Cannonlake PCH-H.
>
> Yay, GREAT, Andy you're a Genius, the Touchpad is working :)
>
> After Downloading Kernel 4.18.RC6, patching with
> https://bugzilla.kernel.org/attachment.cgi?id=277507&action=diff and
> https://bugzilla.kernel.org/attachment.cgi?id=277553&action=diff it's
> working.
>
> -Tap to click works
> -2 Finger scroll works (only Natural Scrolling, always on)
> -2 Finger right click works
> -left mouse button works
> -right mouse button does not work but with 2 finger click it works
> -Edge Scrolling does not work
> -it disconects from time to time (rmmod -r hid-multitouch && modprobe
> hid-multitouch helps)
>
> shall I test other patches and do you still need the outputs from Comment 67
> (interrupts, iomem, ranges, pins?
>
> With kind regards and many thanks so far
> Marc Landolt
For me on Asus FX504 laptop with ELAN1200 touchpad tap to click doesn't
work.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/95
------------------------------------------------------------------------
On 2018-08-24T11:17:21+00:00 mika.westerberg wrote:
If your touchpad works in general (the device can be used somehow) and
does not fail with "GPIO can't be used as IRQ" error, it is most
probably not related to this bug. Please file a separate bug about it.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/96
------------------------------------------------------------------------
On 2018-08-26T13:31:54+00:00 jon.snow wrote:
@Simon: Thanks for the info, you did lots of hard work. I had a look on
the other ticket too. I've never compiled by own kernel, so I have not
tried the patch.
I'm a bit surprised to see that we need a separate ticket for "Razer
Blade 15" and "Recoil II" given that both of them are actually "Tong
Fang GK5CN5". I also don't undertand why the above patch "works" on
Razer does not on Recoil. That's my understanding from your messages,
can you confirm?
If you do find a patch that more-or-less works for Recoil, please give
me a shout. I'll try to test it on my side too. I just want to avoid
compiling my own kernel given that I have no idea what I'm doing without
expecting any positive outcome from that. On the other hand, if you want
someone else to confirm something on a similar system, I'm more than
happy to do it. Just be descriptive of what you want me to do. (I know
how to code but never hacked the kernel)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/97
------------------------------------------------------------------------
On 2018-08-26T13:35:08+00:00 jon.snow wrote:
Also FYI, Razer says they are working into bringing a Linux Driver for
the touchpad here: https://insider.razer.com/index.php?threads/razer-
blade-15-ubuntu-18-04-trackpad-not-working.35999/#post-447134
Not sure what's the progress with that and whether this will cover not
only Razers but any Tong Fang GK5CN5 based laptop. I would love an
update if anyone from Razer is on the thread. Cheers! :)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/98
------------------------------------------------------------------------
On 2018-08-26T14:17:48+00:00 soundhermit wrote:
Razer released a recently 1.05 BIOS update that fixes the touchpad
problem.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/99
------------------------------------------------------------------------
On 2018-08-26T14:23:31+00:00 soundhermit wrote:
Created attachment 278089
dsdt_before_after
Adding DSDT for Razer Blade 15 2018 before and after the 1.05 update.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/100
------------------------------------------------------------------------
On 2018-08-26T23:21:27+00:00 bbriniotis wrote:
I'm facing the same problem on a Recoil II which is a similar but not
identical model to Razers' (both are based on TongFang models).
@Simon: I also read your details on Bug #200787. The two problems seem
related so I tried the patches listed here for the pinctrl module (did
not recompile the entire kernel, just the module) but that did not work
unfortunately.
Shameless plug: I appreciate that debugging drivers is not the most
pleasant coding exercise, so the hero who will solve the problem on the
GK5CN5Z model can claim this bounty:
https://www.bountysource.com/issues/62633122-touchpad-on-tong-fang-
gk5cn5z It's not much but others are welcome to pitch in. :)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/101
------------------------------------------------------------------------
On 2018-09-02T14:49:26+00:00 ameynarkhede02 wrote:
@Mika Westerberg Well that was a mistake on my part. I forgot to put
30-touchpad.conf for enabling tap to click. Hope the patch would improve
a little to fix random disconnects and make it in mainline kernel.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/106
------------------------------------------------------------------------
On 2018-09-05T20:31:39+00:00 2009 wrote:
(In reply to Andy Shevchenko from comment #69)
> (In reply to Marc Landolt from comment #68)
> > (In reply to Andy Shevchenko from comment #66)
> > > Created attachment 277553 [details]
> > > Fix community ordering for H variant
> > >
> > > Another patch for Cannonlake PCH-H.
> >
> > Yay, GREAT, Andy you're a Genius, the Touchpad is working :)
>
> Sorry it wasn't working from the day 1.
>
> > shall I test other patches
>
> Nothing to test for now. There are three problems in your case and one of
> them doesn't clear yet (in a sense of root cause). That's, we are discussing
> internally and will come up with workaround / solution later on.
>
> > and do you still need the outputs from Comment 67
> > (interrupts, iomem, ranges, pins?
>
> Yes, please.
helly Andy Shevchenko,
the patch you wrote for me does not work on Kernel 4.19-rc2 anymore, so
the touchpad does not work in kernel 4.19-rc2 because i can not apply
https://bugzilla.kernel.org/attachment.cgi?id=277507&action=diff since
someone has changed something in pinctrl-intel.c, so the patch works
only with 4.18-rc6. my question is, this fix did not went into mainline?
with kind regards
Marc Landolt
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/107
------------------------------------------------------------------------
On 2018-09-05T22:03:49+00:00 andy.shevchenko wrote:
(In reply to Marc Landolt from comment #100)
> the patch you wrote for me does not work on Kernel 4.19-rc2 anymore, so the
> touchpad does not work in kernel 4.19-rc2 because i can not apply
> https://bugzilla.kernel.org/attachment.cgi?id=277507&action=diff since
> someone has changed something in pinctrl-intel.c, so the patch works only
> with 4.18-rc6. my question is, this fix did not went into mainline?
To be clear, there are three patches, two of which are part of v4.19-rc1.
The only piece is missed in upstream is pin ownership check W/A, that is effectively is a middle of the attachment #277507.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/108
------------------------------------------------------------------------
On 2018-09-05T23:33:12+00:00 2009 wrote:
Hello Andy
i added now lines 1016, 1021 and 1022 from
https://bugzilla.kernel.org/attachment.cgi?id=277507&action=diff to the
/drivers/pinctrl/intel/pinctrl-intel.c from kernel 4.19-rc2 and now the
touchpad works again, i guess if (intel_pad_acpi_mode(pctrl, pin))
evaluates to false and then it returns and does not do the rest of the
function. But I'm not a C Coder, i know very little about C or Kernel
things.
I will now test the things you said in thread and tell you the results
in the thread https://bugzilla.kernel.org/show_bug.cgi?id=200663#c6
with kind regards
Marc Landolt
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/109
------------------------------------------------------------------------
On 2018-09-06T02:39:50+00:00 mrhieu059 wrote:
I'm Using Asus Fx504GD (Elan1200) should to apply these patch?
Someone suggest me this link, so i'm a little confuse.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/110
------------------------------------------------------------------------
On 2018-09-06T04:17:54+00:00 mrhieu059 wrote:
I patched and boot correctly but in xinput it's still doesn't recognized
my touchpad, and also my mouse (Mouse worked well on preview kernel).
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/111
------------------------------------------------------------------------
On 2018-09-13T13:07:33+00:00 trave5 wrote:
any new about this bug? tongfang gk5cn6z
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/113
------------------------------------------------------------------------
On 2018-09-17T06:55:49+00:00 simon.detheridge wrote:
@Hieu Cao you could try the additional patch from Bug #200787 - if your
touchpad is connected the same ways as mine then it could be the
problem.
@trave5 yes, I managed to get it working, see above
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/114
------------------------------------------------------------------------
On 2018-09-17T10:43:12+00:00 mrhieu059 wrote:
(In reply to Simon Detheridge from comment #106)
> @Hieu Cao you could try the additional patch from Bug #200787 - if your
> touchpad is connected the same ways as mine then it could be the problem.
I'm glad to hear this sound. Today I'll try to install a Linux again on
my computer (I already remove it and replaced by windows). Does it work
the same thing on virtual machine? Because I still not getting how to
manage dual boot effectly.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/115
------------------------------------------------------------------------
On 2018-09-17T12:05:16+00:00 simon.detheridge wrote:
@Hieu Cao - I don't know for sure that the patch will fix your problem
in this case, I just figured it might be worth a shot. It may not be
worth reformatting your computer for though.
You shouldn't need any of this stuff for Linux on a VM, as your
hypervisor will be virtualising your mouse pointer anyway, so it won't
be seeing the gpio directly.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/116
------------------------------------------------------------------------
On 2018-09-17T13:59:13+00:00 mrhieu059 wrote:
(In reply to Simon Detheridge from comment #108)
> @Hieu Cao - I don't know for sure that the patch will fix your problem in
> this case, I just figured it might be worth a shot. It may not be worth
> reformatting your computer for though.
>
> You shouldn't need any of this stuff for Linux on a VM, as your hypervisor
> will be virtualising your mouse pointer anyway, so it won't be seeing the
> gpio directly.
Thank for your advice. I kinda love to use Arch and I3wm. It friendly but now I using the Windows it becomes harder for me, I can not do anything without mouse or touchpad. And the Cli on Windows it does not have a friendly command :(
I think I should waiting when this project is complete for a stable patch.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/117
------------------------------------------------------------------------
On 2018-09-17T22:33:20+00:00 2009 wrote:
(In reply to Hieu Cao from comment #103)
> I'm Using Asus Fx504GD (Elan1200) should to apply these patch?
> Someone suggest me this link, so i'm a little confuse.
Hello Hieu
i can not tell for Fx504GD, for GL703GE you need to add these 3 lines
from https://bugzilla.kernel.org/show_bug.cgi?id=199911#c102 i
mentioned, otherwise the touchpad does not work at all...
if the Fx504GD has the same hardware as GL703GE then you have at least a
functioning touchpad except that it crashes sometimes and then you need
to rmmod and insmod hid-multitouch that it works again...
Try to kindly ask Andy Shevchenko he helped me to make my touchpad
working. He Patched a lot, but this 3 lines i mentioned went not to
mainline and without this 3 lines my touchpad does not work
with kind regards
Marc Landolt
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/118
------------------------------------------------------------------------
On 2018-09-18T04:12:14+00:00 mrhieu059 wrote:
(In reply to Marc Landolt from comment #110)
> (In reply to Hieu Cao from comment #103)
> > I'm Using Asus Fx504GD (Elan1200) should to apply these patch?
> > Someone suggest me this link, so i'm a little confuse.
>
> Hello Hieu
>
> i can not tell for Fx504GD, for GL703GE you need to add these 3 lines from
> https://bugzilla.kernel.org/show_bug.cgi?id=199911#c102 i mentioned,
> otherwise the touchpad does not work at all...
>
> if the Fx504GD has the same hardware as GL703GE then you have at least a
> functioning touchpad except that it crashes sometimes and then you need to
> rmmod and insmod hid-multitouch that it works again...
>
> Try to kindly ask Andy Shevchenko he helped me to make my touchpad working.
> He Patched a lot, but this 3 lines i mentioned went not to mainline and
> without this 3 lines my touchpad does not work
>
> with kind regards
> Marc Landolt
I trying to install arch and patch it again, but now I got an error when try to patch it.
https://pastebin.com/1aRfSJy4
It look like the new kernel I download from kernel.org was add these patch.
What I need to do now?
Or these patch are not compatible with the newest kernel?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/119
------------------------------------------------------------------------
On 2018-09-18T04:22:09+00:00 mrhieu059 wrote:
Opps, my bad.
I copied wrong patch so right now the patch is applied well.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/120
------------------------------------------------------------------------
On 2018-09-18T04:29:10+00:00 mrhieu059 wrote:
After i patched 2 patch, And I search in the direction
(/drivers/pinctrl/intel/pinctrl-intel.c) these patch there. What i need
to do now?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/121
------------------------------------------------------------------------
On 2018-09-18T04:35:53+00:00 mrhieu059 wrote:
3 lines you said to add to the /drivers/pinctrl/intel/pinctrl-intel.c it
already there.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781879/comments/122
------------------------------------------------------------------------
On 2018-09-18T10:31:46+00:00 mika.westerberg wrote:
You only need this workaround:
+#if 0
if (intel_pad_acpi_mode(pctrl, pin)) {
dev_warn(pctrl->dev, "pin %u cannot be used as IRQ\n", pin);
return -EPERM;
}
+
Комментариев нет:
Отправить комментарий