In your previous comment you set that linux-image-4.14.0-997-generic_4.14.0-997.201712022100_amd64.deb is working, now you say that 4.14.0-041400rc7 is the latest working, and that 4.14 final does not work? linux-image-4.14.0-997-generic_4.14.0-997.201712022100_amd64.deb sounds like it is a final (non rc) build?
Note I'm not an Ubuntu developer, so I don't know how Ubuntu's kernel versioning scheme works.
If the generic kernel builds broke between 4.14-rc7 and 4.14.0 final then it should be easy (I hope) to pinpoint the problem. Also note that some people say rebooting is an issue so you should probably do a poweroff and then a cold boot for each test.
Also it is interesting to see if things don't work if doing a manual rmmod i2c-hid; modprobe i2c-hid helps.
Hi Bart,
In your previous comment you set that linux-image- 4.14.0- 997-generic_ 4.14.0- 997.20171202210 0_amd64. deb is working, now you say that 4.14.0-041400rc7 is the latest working, and that 4.14 final does not work? linux-image- 4.14.0- 997-generic_ 4.14.0- 997.20171202210 0_amd64. deb sounds like it is a final (non rc) build?
Note I'm not an Ubuntu developer, so I don't know how Ubuntu's kernel versioning scheme works.
If the generic kernel builds broke between 4.14-rc7 and 4.14.0 final then it should be easy (I hope) to pinpoint the problem. Also note that some people say rebooting is an issue so you should probably do a poweroff and then a cold boot for each test.
Also it is interesting to see if things don't work if doing a manual rmmod i2c-hid; modprobe i2c-hid helps.
Regards,
Hans