[Bug 1650895] Re: Several new Asus laptops are missing touchpad support
These messages come from the i2c_hid module, which is a module that sits between the hid-aus driver and the i2c driver. The message indicates that the i2c_hid module received an invalid INPUT report and has discarded it. The hid-asus driver is never made aware that this occurred. I can think of three possible causes: a) an electronic signalling issue; b) a firmware issue; or c) a proprietary function of the device There's little that can be done for a) or b) - it's effectively faulty (or poorly shielded) hardware. For c) - if there were documentation we might be able to do something. But it would likely require a quirk at the lower levels (i.e. the i2c_hid module). And given (in my experience) the minimal impact of these messages - that might be something the kernel maintainers would consider undesirable. You could investigate further by modifying the i2c_hid module to dump the contents of the discarded message. But since a recent change to the i2c_hid module (which put a sleep inbetween the POWER ON and RESET commands) I no longer seem to get these messages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650895 Title: Several new Asus laptops are missing touchpad support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650895] Re: Several new Asus laptops are missing touchpad support
I'm one of the authors for the patch used above and wanted to highlight that there was a bug in it that broke the existing keyboard support. It was later fixed in the kernel with commit c8b1b3dd89ea7b3f77a73e59c4c4495e16338e15. I've attached this as a patch (fix_keyboard.patch). This patch is required for the previous keyboard functionality to work again. Unfortunately I don't have the hardware to test any proposed kernel (or to provide any logs) but I wanted to bring this bug to your attention. There was also another issue that could occur during startup with these I2C Touchpad devices. This issue was fixed in commit a89af4abdf9b353cdd6f61afc0eaaac403304873. This commit is required for reliable Touchpad functionality. Both these commits are in v4.10 of the Kernel (thus in Ubuntu 17.04). ** Patch added: "fix_keyboard.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650895/+attachment/4863405/+files/fix_keyboard.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650895 Title: Several new Asus laptops are missing touchpad support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1052449] Re: corosync hangs due to missing pacemaker shutdown scripts
Please note that the installation scripts I meant to refer to are postinst and postrm (not postinst and preinst). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1052449 Title: corosync hangs due to missing pacemaker shutdown scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1052449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1052449] Re: corosync hangs due to missing pacemaker shutdown scripts
I got a bit confused reading through this bug and the comments so I'm
writing this in the hope it'll help future visitors.
Some of the comments are relevant to a work-around for this bug. But the
bug itself is about the missing update-rc.d command in the postinst (and
preinst) scripts of the install package.
The suggestion in the original bug report is to follow a pattern similar
to corosync where the update-rc.d is in the postinst and preinst scripts
but you still need to edit /etc/default/corosync to enable corosync to
start on boot.
The workaround in the meantime requires one to manually run update-rc.d.
When doing this - it's important that corosync starts before pacemaker
and shuts down after.
To do this, we can run:
sudo update-rc.d pacemaker defaults 99 00
I'm running 14.04.02 LTS - so:
#2 is no longer the case ('Required-Stop: corosync' is now in the
/etc/init.d/pacemaker script)
#5 won't be a problem as insserv has been disabled (by .legacy-bootordering in
/etc/init.d)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1052449
Title:
corosync hangs due to missing pacemaker shutdown scripts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1052449/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
