gigabyte t1132 cando capacitive touchscreen not recognized at all

[Ray-Ven]

Hey,

I'm running ubuntu precise on my gigabyte t1132, but the cando capacitive
touchscreen is not recognized at all:
Device works flawless in windows: 2087:0b03
There are drivers for this device in ubuntu, but the device doesn't show up
anywhere.

neither hwinfo, lsusb, or lsinput are listing this device.
Windows lists it as a usb-hid device

Please help me out!

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.37
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: annalisa 2055 F.... pulseaudio
 /dev/snd/controlC0: annalisa 2055 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xf7700000 irq 50'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,14581132,00100004'
   Controls : 24
   Simple ctrls : 13
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xf5080000 irq 17'
   Mixer name : 'Nvidia GPU 1c HDMI/DP'
   Components : 'HDA:10de001c,00000000,00100100'
   Controls : 12
   Simple ctrls : 2
Date: Sun May 20 09:29:40 2012
HibernationDevice: RESUME=UUID=78a2d3b5-303e-44d3-9f14-bbd73517807b
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
MachineType: GIGABYTE T1132
ProcEnviron:
 LANGUAGE=de_DE
 TERM=xterm
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=28b8f116-6099-427f-8730-101a85903f7e ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-24-generic N/A
 linux-backports-modules-3.2.0-24-generic N/A
 linux-firmware 1.79
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: T1132.F04
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: T1132
dmi.board.vendor: GIGABYTE
dmi.board.version: F04
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT1132.F04:bd01/18/2012:svnGIGABYTE:pnT1132:pvrF04:rvnGIGABYTE:rnT1132:rvrF04:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: T1132
dmi.product.version: F04
dmi.sys.vendor: GIGABYTE

[Ray-Ven (ray-ven)]

further info

[Ray-Ven (ray-ven)]

further info

[Ray-Ven (ray-ven)]

further info

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/

[Ray-Ven (ray-ven)]

Upstream/Mainline Kernel didn't help

used the folowing kernel:
 http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/linux-headers-3.4.0-030400-generic_3.4.0-030400.201205210521_amd64.deb
 http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/linux-image-3.4.0-030400-generic_3.4.0-030400.201205210521_amd64.deb
 http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/linux-headers-3.4.0-030400_3.4.0-030400.201205210521_all.deb

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[pommessemmel (pommessemmel)]

I have the same problem (T1132N and linux) and already did a huge amount of research on it. Some of the correspondence can be found here:

http://comments.gmane.org/gmane.linux.usb.general/64015
http://comments.gmane.org/gmane.linux.usb.general/64016

Also I wrote up this summary:

I have a very specific issue found in a series of notebooks (Gigabyte T1132N) which I would like to resolve. It seems like the device enumeration of the USB Host Controller is failing to find the attached touchscreen. Through windows I got most of the information like the vendor/product ID (2087 0b03) and host controller where the device is attached at. The host controller is recognized in linux and all the attached devices other than the touchscreen work flawlessly. Also the driver for the specific type of touchscreen exists but the device is just not found.

To start the enumeration manually I tried creating a module using the Host Controller API but as I understand modules can only use the USB Core API. (Compilation didn't work) The USB Core API doesn't support enumeration.

Using a USB sniffer in windows I received some output that suggests that the touchscreen might be turned off (power state D2) but I can't figure out how to influence power states in usb devices in linux.

Attached you will find the output of dmesg from kernel 2.6.35.13 (amd64) compiled with the CONFIG_USB_DEBUG option enabled.

Here some things I already know/did:

Windows indicates that the touchscreen is connected to the same host controller as the USB Wheel mouse and the Card reader so that is usb2.

Unfortunately I can't unplug the touchscreen because it is attached to the notebook. And opening the notebook would probably void the warranty.

I tried multiple kernel versions (all amd64):
2.6.32-5
2.6.35.13
3.0.0-17
3.2.0-0.bpo.1
3.2.0-24
I tried distributions debian and kubuntu (oneiric & precise)

The notebook also has a touchpad (which is working flawlessly) in addition to the touchscreen. But this doesn't even come from the same vendor nor is it attached to the usb port.

--------------------------------------------------

The guys from the usb mailing list say that this is not a usb issue. It's more like the touch screen is not even connected to the usb host controller. So there needs to be some kind of software switch to make it visible to the host controller in the first place. One last thing that I want to test is if the touchscreen is visible in other windows versions than the preinstalled one. (I assume not)

[pommessemmel (pommessemmel)]

I found one way to activate the touch screen:

- On computer start press F2 to enter the BIOS setup

- under Main set 'User SETUP Options' to 'advanced'

- under Advanced go to Onboard Device Configuration and set 'SmartCharge' to 'Always Off'

I assume that changing that option lessens the power efficiency of the computer.
Windows 7 is still able to use the touch screen with the 'SmartCharge' enabled and linux and other windows versions don't.

[Ray-Ven (ray-ven)]

great! Really works - will mark as solved