http://bugzilla.opensuse.org/show_bug.cgi?id=906026 --- Comment #2 from robert spitzenpfeil --- Created attachment 614111 --> http://bugzilla.opensuse.org/attachment.cgi?id=614111&action=edit Xorg logfile after cold-boot -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |CONFIRMED Assignee|bnc-team-xorg-bugs@forge.pr |xorg-maintainer-bugs@forge. |ovo.novell.com |provo.novell.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 http://bugzilla.opensuse.org/show_bug.cgi?id=906026#c4 pier andre changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pier_andreit@yahoo.it --- Comment #4 from pier andre --- after boot touchpad works well, after resume from suspend tu RAM it stops to works. if it can help: this discussion https://forums.opensuse.org/showthread.php/509103-touchpad-doesn-t-work-afte... I made some try: always after resume it stops to works, sometimes after logout and login again touchpad works often after resume if I login with another user (two users active) on the second user touchpad works and the first not sometimes with no-working touchpad if I suspend to RAM and resume again also keyboard don't works when touchpad works xinput list gives this: procuste@linux-eros1:~> xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ MOON AND id=11 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPad id=13 [slave pointer (2)] ⎜ ↳ DualPoint Stick id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Sony Vaio Keys id=8 [slave keyboard (3)] ↳ Power Button id=9 [slave keyboard (3)] ↳ Sony Visual Communication Camer id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)] procuste@linux-eros1:~> and theese commands work procuste@linux-eros1:~> xinput disable "AlpsPS/2 ALPS DualPoint TouchPad" procuste@linux-eros1:~> xinput enable "AlpsPS/2 ALPS DualPoint TouchPad" after resume when touchpad don't works it disappear also from xinput list and the above commands don't work manythanks for your efforts to solve :-) ciao :-) pier HARDWARE INFO PC=sony vaio VPCEH2N1E, RAM=4Gb, GPU=intel 1366×768, CPU=ntel 4 Core i5-2430M @ 2.40GHz, HD=500Gb OS=opensuse "13.2" KDE=4.14.9 hwinfo gives this for touchpad: linux-eros1:/home/eros # hwinfo --mouse ... 34: PS/2 00.0: 10500 PS/2 Mouse [Created at input.249] Unique ID: AH6Q.5+smWHVjPI3 Hardware Class: mouse Model: "AlpsPS/2 ALPS DualPoint TouchPad" Vendor: 0x0002 Device: 0x0008 "AlpsPS/2 ALPS DualPoint TouchPad" Compatible to: int 0x0210 0x0003 Device File: /dev/input/mice (/dev/input/mouse1) Device Files: /dev/input/mice, /dev/input/mouse1, /dev/input/event2, /dev/input/by-path/platform-i8042-serio-1-event-mouse, /dev/input/by-path/platform-i8042-serio-1-mouse Device Number: char 13:63 (char 13:33) Driver Info #0: Buttons: 3 Wheels: 0 XFree86 Protocol: explorerps/2 GPM Protocol: exps2 Config Status: cfg=no, avail=yes, need=no, active=unknown ... linux-eros1:/home/eros # -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 http://bugzilla.opensuse.org/show_bug.cgi?id=906026#c6 --- Comment #6 from robert spitzenpfeil --- I will get the data next Saturday. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 http://bugzilla.opensuse.org/show_bug.cgi?id=906026#c8 --- Comment #8 from robert spitzenpfeil --- Created attachment 657196 --> http://bugzilla.opensuse.org/attachment.cgi?id=657196&action=edit available events before suspend to ram -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 http://bugzilla.opensuse.org/show_bug.cgi?id=906026#c10 --- Comment #10 from robert spitzenpfeil --- Created attachment 657198 --> http://bugzilla.opensuse.org/attachment.cgi?id=657198&action=edit lsusb -v before STR -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 http://bugzilla.opensuse.org/show_bug.cgi?id=906026#c12 --- Comment #12 from robert spitzenpfeil --- I ran 'evtest' on the touchpad after suspend to ram. The thing is dead, nothing. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 http://bugzilla.opensuse.org/show_bug.cgi?id=906026#c14 Oliver Neukum changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(oneukum@suse.com) | --- Comment #14 from Oliver Neukum --- (In reply to Egbert Eich from comment #13)

However the comment #12 indicates that this is either an USB issue or a kernel input driver issue.

@Oliver: Could this be a USB issue?

The device is attached over i2c, so this is not a USB issue. A loading cycle on every i2c module might clarify the issue. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 http://bugzilla.opensuse.org/show_bug.cgi?id=906026#c16 --- Comment #16 from Egbert Eich --- Also, Robert, are you sure that attachment #657196 is the output of my little script after a fresh reboot and before any suspend - ie. when the touchpad is still working? It doesn't list any touchpad or PS/2 device at all. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 http://bugzilla.opensuse.org/show_bug.cgi?id=906026#c18 --- Comment #18 from Egbert Eich --- The Alps touch pad should be a PX/2 device. We will probably know more if you run the little script and 'hwinfo --mouse' right after the other after a reboot and without rebooting in between (each reboot reenumerates the devices in a different order). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 http://bugzilla.opensuse.org/show_bug.cgi?id=906026#c20 Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jdelvare@suse.com Summary|[AlpsPS/2, touchpad] |[i2c, touchpad] |non-responsive after |non-responsive after |suspend-to-ram or |suspend-to-ram or |suspend-to-disk |suspend-to-disk Flags|needinfo?(madworm_de.novell |needinfo?(pier_andreit@yaho |@spitzenpfeil.org) |o.it) --- Comment #20 from Egbert Eich --- (In reply to robert spitzenpfeil from comment #19)

What do you mean by "IF"?

The output of that script is in my previous comments.

As I said, the device enumeration may differ between boots (and may even change after a resume). I was not sure whether you ran the script and did the output test within the same boot cycle.

The touch-pad is listed as "event 9". Before STR 'evtest' spits out a heck of a lot of data when touching it, after STR nothing at all.

In this case, the touchpad really is an i2c device. I did not realize that comment #4 was done by a different user with a different issue. @pier andre: please file a separate ticket if you still see this problem. I would like to solicit the opinion of our i2c expert on this. @Jean, could you please have a look? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 http://bugzilla.opensuse.org/show_bug.cgi?id=906026#c22 Jean Delvare changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(madworm_de.novell | |@spitzenpfeil.org) --- Comment #22 from Jean Delvare --- Robert, these suspicious syslog entries you mention in comment #7, do you see them when you boot the machine? After a suspend-to-ram cycle? After a suspend-to-disk cycle? The complete kernel log for each of these cases would be useful. I would also like to see the contents of /sys/bus/i2c/drivers and /sys/bus/i2c/devices when the touchpad works, and if it is different, when it does not. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 http://bugzilla.opensuse.org/show_bug.cgi?id=906026#c24 --- Comment #24 from robert spitzenpfeil --- Created attachment 662943 --> http://bugzilla.opensuse.org/attachment.cgi?id=662943&action=edit syslog before & after STR -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 http://bugzilla.opensuse.org/show_bug.cgi?id=906026#c26 --- Comment #26 from robert spitzenpfeil --- Created attachment 662945 --> http://bugzilla.opensuse.org/attachment.cgi?id=662945&action=edit sys-bus-i2c after STR -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 http://bugzilla.opensuse.org/show_bug.cgi?id=906026#c28 --- Comment #28 from robert spitzenpfeil --- Created attachment 662947 --> http://bugzilla.opensuse.org/attachment.cgi?id=662947&action=edit i2c-ELAN after STR -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 http://bugzilla.opensuse.org/show_bug.cgi?id=906026#c30 --- Comment #30 from Egbert Eich --- (In reply to robert spitzenpfeil from comment #29)

I've made yet another interesting observation:

AFTER STR the touchpad is completely dead as far as Xorg is concerned. 'evtest' shows no data whatsoever.

Do you still see it listed in the device list after an STR when you call evtest as root and without arguments? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 http://bugzilla.opensuse.org/show_bug.cgi?id=906026#c32 Jean Delvare changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jkosina@suse.com Flags|needinfo?(jdelvare@suse.com | |) | --- Comment #32 from Jean Delvare --- If the BIOS update doesn't help, the following 3 upstream kernel commits may be worth trying: commit 109571cf3ec78a39477eedd6b11927f52cbcb1e8 Author: Andrew Duggan Date: Fri Jul 11 16:34:18 2014 -0700 HID: i2c-hid: call the hid driver's suspend and resume callbacks commit af4739c281621017a8a84dd6ba3471bba2dd6c6a Author: Gabriele Mazzotta Date: Tue Jul 7 21:58:02 2015 +0200 HID: i2c-hid: Call device suspend callback before disabling irq commit d1c48038b849e9df0475621a52193a62424a4e87 Author: Andrew Duggan Date: Thu Jul 30 14:49:00 2015 -0700 HID: i2c-hid: Only disable irq wake if it was successfully enabled during suspend -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 http://bugzilla.opensuse.org/show_bug.cgi?id=906026#c34 --- Comment #34 from robert spitzenpfeil --- (In reply to Jean Delvare from comment #31)

Your laptop is running BIOS version 1.02. According to the vendor's web site, updates are available. In particular, BIOS version 1.04 has the following changelog entry which seems quite relevant:

Unfortunately the BIOS files are dos executables (UPX compressed). I tried to run these in a 32-bit XP VM command prompt, to no avail. "ZYL_105.exe: MS-DOS executable, COFF for MS-DOS, DJGPP go32 DOS extender, UPX compressed" I tried to decompress the .exe with UPX, but the resulting file is way too small and doesn't run either. I don't have any other version of winblows, so I can't go any further with this as of now. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 http://bugzilla.opensuse.org/show_bug.cgi?id=906026#c36 --- Comment #36 from Jean Delvare --- I understand your hesitation, and I would not insist if the changelog did not look so promising. In the past I had very good results flashing BIOS using the FirmwareUpdateKit package. I suggest you give it a try. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=906026 http://bugzilla.opensuse.org/show_bug.cgi?id=906026#c38 Jean Delvare changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |NORESPONSE --- Comment #38 from Jean Delvare --- OK, closing it. Feel free to reopen if you ever update the BIOS and the problem persist. BTW don't be too afraid of BIOS updates. I must have done a dozen since I started tinkering with computers and all worked fine. -- You are receiving this mail because: You are on the CC list for the bug.