Colin Johnstone, in order to allow additional upstream developers to examine
the issue, at your earliest convenience, could you please test the latest
upstream kernel available from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind
the following:
1) The one to test is at the very top line at the top of the page (not the
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was
released upstream.
4) Install instructions are available at
https://wiki.ubuntu.com/Kernel/MainlineBuilds .
If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.
If the latest kernel did not allow you to test to the issue (ex. you couldn't
boot into the OS) please make a comment in your report about this, and continue
to test the next most recent kernel version until you can test to the issue.
Once you've tested the upstream kernel, please comment on which kernel version
specifically you tested. If this issue is fixed in the mainline kernel, please
add the following tags by clicking on the yellow circle with a black pencil
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ
Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.
If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ
Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.
Also, you don't need to apport-collect further unless specifically
requested to do so.
It is most helpful that after testing of the latest upstream kernel is
complete, you mark this report Status Confirmed.
Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.
Thank you for your help.
** Tags added: bios-outdated-f11
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1609601
Title:
i2c_hid: probe of i2c-ELAN0732:00 failed with error -61
Status in linux package in Ubuntu:
Incomplete
Bug description:
I'm using an HP Envy x360 M6-ar004dx with an AMD 7th-gen FX APU, and
the touchscreen will not work. Dmesg shows i2c_hid reporting multiple
"failed to reset device" error messages before finally failing to add
it as an HID device with error -61. As far as I can tell, it's being
detected as an ELAN touchscreen. I've seen reports that this error can
be fixed in newer kernels, as the touchscreen uses GPIO interrupts
which are fixed in versions 4.6 and later. Most of the information I
can find indicates that 4.7 includes improved AMD support, but the
mainline kernel build appears to be missing the AMD GPIO drivers,
since I get a "failed to get GPIO interrupt" error. I've compiled my
own 4.7 kernel from the mainline GIT, including the patches used in
kernel-ppa/mainline and setting the right config flags for AMD GPIO,
but that just gets me the same errors I'm seeing in 4.4.0-31-generic.
For additional info, I'm attaching my dmesg output in its entirety.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified:
boot/vmlinuz-4.4.0-31-generic]
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: colin 3591 F.... pulseaudio
/dev/snd/controlC0: colin 3591 F.... pulseaudio
CurrentDesktop: GNOME
Date: Wed Aug 3 21:51:47 2016
HibernationDevice: RESUME=UUID=1875834b-d1ff-4b97-a9b8-44afb056c592
InstallationDate: Installed on 2016-08-03 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160720)
MachineType: HP HP ENVY x360 m6 Convertible
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-4.4.0-31-generic N/A
linux-backports-modules-4.4.0-31-generic N/A
linux-firmware 1.157.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/29/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81AA
dmi.board.vendor: HP
dmi.board.version: 59.42
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.10:bd06/29/2016:svnHP:pnHPENVYx360m6Convertible:pvrType1ProductConfigId:rvnHP:rn81AA:rvr59.42:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY x360 m6 Convertible
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609601/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
