[Bug 1683508] Re: touchpad not working (elan_i2c invalid report id data)

2017-11-30 Thread Kai-Heng Feng
@vasilj-davidovic, Yours seems to be the same one as LP: #1732056. @teodor-sobczak, If yours is not 15ABR, file a separate bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683508 Title:

[Bug 1683508] Re: touchpad not working (elan_i2c invalid report id data)

2017-11-30 Thread Teodor Sobczak
I can confirm that this bug affects kernels up to 4.13.0-17 but it is a little better on that one. Tested it on Ubuntu 16.04.3, Ubuntu Mate 17.10 and Linux Mint 18.3. I have: Lenovo Ideapad 320 (very similar to @Vasilj). Today I tried to fix this bug with different methods with no results. I

[Bug 1683508] Re: touchpad not working (elan_i2c invalid report id data)

2017-10-26 Thread Kai-Heng Feng
I don't know. Maybe just install Ubuntu to local disk and install the kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683508 Title: touchpad not working (elan_i2c invalid report id data) To

[Bug 1683508] Re: touchpad not working (elan_i2c invalid report id data)

2017-10-26 Thread Vasilj Davidović
correction info for workaround, it doesn't work every time output of product name is 80XS (it is lenovo 320-15ABR notebook with AMD FX-9800P, and 8 GBram) Can you help me how to replace kernel on live usb disk (created with startap disk creator from 17.10 iso image) -- You received this bug

[Bug 1683508] Re: touchpad not working (elan_i2c invalid report id data)

2017-10-22 Thread Kai-Heng Feng
What's the output of `cat /sys/class/dmi/id/product_name`? Also, please try kernel here: http://people.canonical.com/~khfeng/lp1683508/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683508 Title:

[Bug 1683508] Re: touchpad not working (elan_i2c invalid report id data)

2017-10-21 Thread Vasilj Davidović
used livecd (usb stick) of 17.10 this time edited command before boot cat /proc/cmdline BOOT_IMAGE=/casper/vmlinuz.efi elan_i2c.dyndbg=+p file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- last few lines (time > 1000) i tried sudo rmmod elan_i2c sudo modprobe elan_i2c the workaround

[Bug 1683508] Re: touchpad not working (elan_i2c invalid report id data)

2017-10-21 Thread Kai-Heng Feng
Hi, can you add "elan_i2c.dyndbg=+p" to kernel parameter, and attach dmesg here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683508 Title: touchpad not working (elan_i2c invalid report id data)

[Bug 1683508] Re: touchpad not working (elan_i2c invalid report id data)

2017-10-20 Thread Vasilj Davidović
** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683508 Title: touchpad not working (elan_i2c invalid report id data) To manage

[Bug 1683508] Re: touchpad not working (elan_i2c invalid report id data)

2017-10-20 Thread Vasilj Davidović
Same thing with 17.10 elan_i2c i2c-ELAN060B:00: invalid report id data (ff) same fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683508 Title: touchpad not working (elan_i2c invalid report id

[Bug 1683508] Re: touchpad not working (elan_i2c invalid report id data)

2017-06-17 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683508

[Bug 1683508] Re: touchpad not working (elan_i2c invalid report id data)

2017-04-18 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11