the same bug if i upgrade/fresh install utopic...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/1180881
Title:
Touchscreen only works after suspend/resume on Lenovo
The precise patch came in via a stable upstream commit.
** Tags removed: verification-needed-precise
** Tags added: verification-done-precise
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
** Changed in: hwe-next/saucy
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/1180881
Title:
Touchscreen only works after
** Tags removed: verification-needed-saucy
** Tags added: verification-done-saucy
** Changed in: hwe-next/saucy
Status: Confirmed = Fix Committed
** Changed in: hwe-next/trusty
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
saucy' to 'verification-done-saucy'.
If verification is not done by 5 working days from
This bug was fixed in the package linux - 3.12.0-1.3
---
linux (3.12.0-1.3) trusty; urgency=low
[ Andy Whitcroft ]
* [Config] arm64 -- add arch to the configuration handlers
* [Config] arm64 -- add generic flavour
* [Config] arm64 -- default config
* [Config] arm64 -- fix
** Also affects: hwe-next
Importance: Undecided
Status: New
** Changed in: hwe-next
Assignee: (unassigned) = AceLan Kao (acelankao)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
Patches were sent to:
http://www.spinics.net/lists/linux-usb/msg94777.html
http://www.spinics.net/lists/linux-usb/msg94778.html
** Changed in: hwe-next
Status: New = Confirmed
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
The fix you provided works perfectly with my touchscreen indeed !
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/1180881
Title:
Touchscreen only works after
unix25,
Good to know that.
I'll build a patch for your device, so that linux kernel can support the SiS
touchscreen.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
Those 2 patches had submitted
** Patch added: 0002-HID-usbhid-quirk-for-SiS-Touchscreen.patch
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+attachment/3856404/+files/0002-HID-usbhid-quirk-for-SiS-Touchscreen.patch
** Changed in: xserver-xorg-input-evdev
** Patch added: 0001-HID-usbhid-quirk-for-Synaptics-Large-Touchccreen.patch
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1180881/+attachment/3856403/+files/0001-HID-usbhid-quirk-for-Synaptics-Large-Touchccreen.patch
--
You received this bug notification because you
The attachment 0001-HID-usbhid-quirk-for-Synaptics-Large-
Touchccreen.patch seems to be a patch. If it isn't, please remove the
patch flag from the attachment, remove the patch tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by
My touch screen ID isn't listed above. Here's the line in the kernel log
file :
[12420.825654] input: USBest Technology SiS HID Touch Controller as
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input1150
[12420.825889] hid-multitouch 0003:0457:1013.0474: input,hiddev0,hidraw0:
Hi unix25, thanks a lot.
But, looks like your touchscreen chip is not Synaptics, I don't know if the
solution apply to SiS' chip.
I got a new way to test.
# cat /etc/modprobe.d/usbhid.conf
options usbhid quirks=0x06cb:0x0af8:0x2000
# sudo update-initramfs -u
# sudo reboot
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: Confirmed = In Progress
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Assignee: (unassigned) = AceLan Kao (acelankao)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Using wireshark to monitor the usb traffic, we'll find the touchscreen becomes
abnormal after systems sends the IDLE command to it.
But the touchscreen could revive after sending some other commands, such as
GET_DESCRIPTOR.
I'll build a test driver soon, but I need to build a list for the
The above test result is wrong, the touchscreen function is not always
working.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/1180881
Title:
Touchscreen only works
add the following lines in /etc/rc.local could wake up the touch screen, it
works every time after booting up.
Or, you can run it manually to check if the commands work.
sudo rmmod hid_multitouch ; sudo modprobe hid-multitouch ; find
/sys/bus/usb/devices/2-3 -name control | xargs -I '{}' sudo
It's confirmed that it's a Synaptics firmware bug, and the new firmware can fix
it.
It works for my device, the usb id is 06CB:0AF8
I'm not sure if it'll work or damage other devices, so use it at your own risk.
** Attachment added: PR1507220.zip
More finding, if suspend/resume doesn't work for you, try the following steps
cd /sys/devices/pci:00
find -name control | xargs -I '{}' sudo sh -c echo on '{}'
sudo pm-suspend
It will turn on the power for all devices, more precisely you can just turn on
the usb host chip's power
** Tags added: blocks-hwcert-enablement
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/1180881
Title:
Touchscreen only works after suspend/resume on Lenovo ideapad
Sep 4 20:18:21 ryan-Lenovo-IdeaPad-Z400-Touch kernel: [ 22.961633]
hid-multitouch 0003:06CB:1D10.0001: usb_submit_urb(ctrl) failed: -1
Sep 4 20:18:21 ryan-Lenovo-IdeaPad-Z400-Touch kernel: [ 22.961647]
hid-multitouch 0003:06CB:1D10.0001: timeout initializing reports
Sep 4 20:18:21
New Z400 laptop here with the i5 2.6ghz processor, same issue ubuntu
13.04 clean install.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/1180881
Title:
Touchscreen
Same problem on an Asus X202E. When starting up off a cold boot, xinput --list
won't show the touchscreen device. However, after getting out of suspend mode,
the touchscreen appears according to xinput --list.
When I take a look at the log files, I get pretty much the same lines as
gravity.
It
Problem noticed in Lenovo Z400 touch. If you need any testing or
diagnostic work ask me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/1180881
Title:
Touchscreen
Doesn't seem to have anything to do with KVM. After turning on
virtualization in BIOS to get kvm working the problem persists. Also
updated to the latest kernel 3.9.7 and the problem persists. I don't
consistently get functionality after suspending, and sometimes the
touchscreen works immediately.
[ 25.722697] hid-multitouch 0003:06CB:1D10.0001: usb_submit_urb(ctrl) failed:
-1
[ 25.722747] hid-multitouch 0003:06CB:1D10.0001: timeout initializing reports
[ 25.722816] input: SYNAPTICS Synaptics Large Touch Screen as
/devices/pci:00/:00:14.0/usb3/3-2/3-2:1.0/input/input12
[
Same problem with my Lenovo Ideapad P400 Touch. Could this have
something to do with KVM? Ubuntu always report a error in KVM when
loading.
The closing the lid/suspending trick also worked with me.
Since P400 is a version made from Lenovo to BestBuy from Z400, it is
probably that users of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
It may also be related (of note possibly) that the setting for the
touchPAD disabling feature appears to re-enable itself when coming out
of suspend/sleep mode also. Not sure if the devices are being
reactivated in an awakening method in some way, therefore turning the
touchscreen back on.
If
http://askubuntu.com/questions/291571/touchscreen-recognized-but-not-
working-in-13-04
Two users with similar 'inconsistent' behavior until we discovered that
closing the lid (therefore, for that user, going into 'Suspend' mode) or
a manual 'Suspend,' was resolving the issue.
--
You received
33 matches
Mail list logo
