From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Aljo=C5=A1a?= Subject: Re: ASUS G752VS Touchpad does not work Date: Mon, 26 Jun 2017 08:44:40 +0200 Message-ID: <3a7a1774cf0693bd9e083da76905d463@cromalternativemoney.org> References: <005e01d2c4bb$6961c7f0$3c2557d0$@emc.com.tw> <003e01d2c54f$4f8acb30$eea06190$@emc.com.tw> <005601d2c554$64578df0$2d06a9d0$@emc.com.tw> <2e065dd76a3fff10b9dc3f55d85cdbd5@cromalternativemoney.org> <015801d2dad1$c271e5b0$4755b110$@emc.com.tw> <003901d2de68$92cf2620$b86d7260$@emc.com.tw> <783da09eba0db262a9b57ccfef48a70e@cromalternativemoney.org> Reply-To: aljosa@cromalternativemoney.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Return-path: Received: from vmi82135.contabo.host ([79.143.182.173]:40845 "EHLO vmi82135.contabo.host" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751092AbdFZGok (ORCPT ); Mon, 26 Jun 2017 02:44:40 -0400 In-Reply-To: Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Kai-Heng Feng Cc: Chris Chiu , =?UTF-8?Q?=E5=BB=96=E5=B4=87=E6=A6=AE?= , linux-input@vger.kernel.org, =?UTF-8?Q?=E9=BB=83?= =?UTF-8?Q?=E4=B8=96=E9=B5=AC_=E7=B6=93=E7=90=86?= Just installed new kernel 4.12-rc7, my ELAN touchpad is still completely dead. Please find attached the dmesg output file here (comment #74): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653456 [ 5.320298] i2c_hid i2c-ELAN1203:00: i2c-ELAN1203:00 supply vdd not found, using dummy regulator [ 5.581767] hid-multitouch 0018:04F3:3043.0007: Ignoring the extra HID_DG_INPUTMODE [ 5.581851] input: ELAN1203:00 04F3:3043 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input16 [ 5.581967] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00 Additionally, my wifi stopped working too: [4.542384] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8000C-30.ucode failed with error -2 [4.542606] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8000C-29.ucode failed with error -2 [4.542617] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8000C-28.ucode failed with error -2 [4.542626] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8000C-27.ucode failed with error -2 [4.542704] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8000C-26.ucode failed with error -2 [4.542714] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8000C-25.ucode failed with error -2 [4.542723] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8000C-24.ucode failed with error -2 [4.542732] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8000C-23.ucode failed with error -2 [4.542816] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8000C-22.ucode failed with error -2 [4.542817] iwlwifi 0000:02:00.0: no suitable firmware found! [4.542836] iwlwifi 0000:02:00.0: minimum version required: iwlwifi-8000C-22 [4.542853] iwlwifi 0000:02:00.0: maximum version supported: iwlwifi-8000C-30 [4.542870] iwlwifi 0000:02:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git and I'm also getting the following "Firmware Bug" message: [4.440279] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80 [4.440343] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80 On 2017-06-20 12:06, Kai-Heng Feng wrote: > On Tue, Jun 20, 2017 at 5:53 PM, AljoĊĦa > 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.