All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aljoša <aljosa@cromalternativemoney.org>
To: 廖崇榮 <kt.liao@emc.com.tw>
Cc: "'Kai-Heng Feng'" <kai.heng.feng@canonical.com>,
	"'Chris Chiu'" <chiu@endlessm.com>,
	linux-input@vger.kernel.org, "'黃世鵬 經理'" <phoenix@emc.com.tw>
Subject: Re: ASUS G752VS Touchpad does not work
Date: Tue, 11 Jul 2017 17:35:46 +0200	[thread overview]
Message-ID: <7d052e4c4a490eafac3ac7ff53379a69@cromalternativemoney.org> (raw)
In-Reply-To: <00a201d2f3e7$71e0ab70$55a20250$@emc.com.tw>

*
Ubuntu 17.10 daily build (2017-07-10), kernel 4.10.0-19
Booted from Live USB, without USB mouse connected: ELAN touhpad doesn't 
work at all, but al least touchpad cursor is visible all the time. I've 
tried to disable/enable the touchpad via system settings, but nothing 
changes.
After that, I suspended my Asus G752VS laptop via shutdown/suspend menu 
and then I disconnected the USB mouse. After waking up from suspend, my 
ELAN touhpad magically became fully functional - everything works 
fabulously.

*
Fedora Workstation 26, kernel 4.11.8
Booted from Live USB, without USB mouse connected: ELAN touhpad doesn't 
work at all, but al least touchpad cursor is visible all the time. With 
the USB mouse connected, I've tried to disable/enable the touchpad via 
system settings, but nothing changes.
After that, I pressed the power button to suspend my Asus G752VS laptop 
and then I disconnected the USB mouse. After pressing once again the 
power button to wake up from suspend, my ELAN touhpad magically became 
fully functional - everything works fabulously.

*
As reported here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653456/comments/76
the trick should work also with Ubuntu 17.04 but that's not my case. My 
current Ubuntu 17.04 was installed while it was still in development - 
so I will perform a new clean installation (without Windows) in the next 
few days.


On 2017-07-03 12:30, 廖崇榮 wrote:
> Chris thinks touchpad works fine but display card issue in previous 
> mail.
> Could anyone help to check it?
> 
> -----Original Message-----
> From: Aljoša [mailto:aljosa@cromalternativemoney.org]
> Sent: Monday, July 03, 2017 5:03 PM
> To: Kai-Heng Feng
> Cc: Chris Chiu; 廖崇榮; linux-input@vger.kernel.org; 黃世鵬 經理
> Subject: Re: ASUS G752VS Touchpad does not work
> 
> Hello,
> I have just installed the new Linux 4.12 kernel.
> My ELAN touchpad is still completely dead.
> Please find attached the complete dmesg output file here (comment #75):
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653456
> 
> 
> On 2017-06-20 12:06, Kai-Heng Feng wrote:
>> On Tue, Jun 20, 2017 at 5:53 PM, Aljoša
>> <aljosa@cromalternativemoney.org> wrote:
>>> Currently I'm using 4.11.0-5.10 kernel compiled by Kai-Heng Feng:
>>> http://people.canonical.com/~khfeng/asus-hid/
>> 
>> FWIW,
>> 
>>> 1. verify the return value of irq_get_trigger_type()
>> [    4.478815] i2c_hid i2c-ELAN1203:00: Trigger type: 0
>> 
>>> 2. Force the trigger type to IRQ_TYPE_EDGE_FALLING with
>>> irqd_set_trigger_type() before request_threaded_irq() 3. reboot with
>>> your own kernel to see if it works.
>> 
>> I also set the type to IRQ_TYPE_EDGE_FALLING. But looks like it didn't
>> work for the user.

  parent reply	other threads:[~2017-07-11 15:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04  7:58 ASUS G752VS Touchpad does not work Kai-Heng Feng
2017-05-04  9:47 ` 廖崇榮
2017-05-04  9:54   ` Kai-Heng Feng
2017-05-05  3:25     ` 廖崇榮
     [not found]       ` <CAB4CAwdV0fUOARAZ13TY00s2kxVCw+QzOKd9k2P0m7fBPmhY0w@mail.gmail.com>
     [not found]         ` <005601d2c554$64578df0$2d06a9d0$@emc.com.tw>
2017-05-05  6:41           ` Chris Chiu
2017-05-05  7:42             ` Kai-Heng Feng
2017-05-05 13:05               ` Chris Chiu
2017-05-08  6:49                 ` Kai-Heng Feng
2017-05-23  9:31                   ` Aljoša
2017-05-29 11:04                   ` Aljoša
2017-06-01 12:22                     ` 廖崇榮
2017-06-01 12:58                       ` Chris Chiu
2017-06-01 16:42                         ` Aljoša
2017-06-05 10:39                         ` Aljoša
2017-06-06  1:59                           ` 廖崇榮
2017-06-07  9:30                             ` Chris Chiu
2017-06-08  8:55                               ` Kai-Heng Feng
2017-06-19 18:38                                 ` Aljoša
     [not found]                                 ` <ef1052e44792273269cd51f48e7f2c99@cromalternativemoney.org>
2017-06-20  4:07                                   ` Chris Chiu
     [not found]                                     ` <783da09eba0db262a9b57ccfef48a70e@cromalternativemoney.org>
2017-06-20 10:06                                       ` Kai-Heng Feng
2017-06-26  6:44                                         ` Aljoša
2017-07-03  9:03                                         ` Aljoša
2017-07-03 10:30                                           ` 廖崇榮
2017-07-04  9:06                                             ` Aljoša
2017-07-06  8:40                                             ` Aljoša
2017-07-11 15:35                                             ` Aljoša [this message]
2017-09-22 15:49                                         ` Aljoša

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7d052e4c4a490eafac3ac7ff53379a69@cromalternativemoney.org \
    --to=aljosa@cromalternativemoney.org \
    --cc=chiu@endlessm.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=kt.liao@emc.com.tw \
    --cc=linux-input@vger.kernel.org \
    --cc=phoenix@emc.com.tw \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.