Ubuntu

cypress touchpad not being assigned to synaptics

Asked by GaryParr

I installed 64 bit 12.10 on a Dell XPS 12 and then added the Sputnik PPA and updated to the modified kernel which includes the Cypress touchpad support. Unfortunately, the touchpad tab is missing from the settings screen, apparently because the touchpad is not being assigned to the synaptics input module.

snip of Xorg.0.log
====================================================
[ 5.197] (**) Option "xkb_model" "pc105"
[ 5.197] (**) Option "xkb_layout" "us"
[ 5.197] (II) config/udev: Adding input device PS/2 Cypress Trackpad (/dev/input/event7)
[ 5.197] (**) PS/2 Cypress Trackpad: Applying InputClass "evdev pointer catchall"
[ 5.197] (II) Using input driver 'evdev' for 'PS/2 Cypress Trackpad'
[ 5.197] (**) PS/2 Cypress Trackpad: always reports core events
[ 5.197] (**) evdev: PS/2 Cypress Trackpad: Device: "/dev/input/event7"
[ 5.197] (--) evdev: PS/2 Cypress Trackpad: Vendor 0x2 Product 0x1
[ 5.197] (--) evdev: PS/2 Cypress Trackpad: Found 3 mouse buttons
[ 5.197] (--) evdev: PS/2 Cypress Trackpad: Found relative axes
[ 5.197] (--) evdev: PS/2 Cypress Trackpad: Found x and y relative axes
[ 5.197] (II) evdev: PS/2 Cypress Trackpad: Configuring as mouse
[ 5.198] (**) evdev: PS/2 Cypress Trackpad: YAxisMapping: buttons 4 and 5
[ 5.198] (**) evdev: PS/2 Cypress Trackpad: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 5.198] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event7"
[ 5.198] (II) XINPUT: Adding extended input device "PS/2 Cypress Trackpad" (type: MOUSE, id 12)
[ 5.198] (II) evdev: PS/2 Cypress Trackpad: initialized for relative axes.
[ 5.198] (**) PS/2 Cypress Trackpad: (accel) keeping acceleration scheme 1
[ 5.198] (**) PS/2 Cypress Trackpad: (accel) acceleration profile 0
[ 5.198] (**) PS/2 Cypress Trackpad: (accel) acceleration factor: 2.000
[ 5.198] (**) PS/2 Cypress Trackpad: (accel) acceleration threshold: 4
[ 5.198] (II) config/udev: Adding input device PS/2 Cypress Trackpad (/dev/input/mouse1)
[ 5.198] (II) No input driver specified, ignoring this device.
[ 5.198] (II) This device may have been added with another device file.
[ 5.199] (II) config/udev: Adding input device Dell WMI hotkeys (/dev/input/event4)
[ 5.199] (**) Dell WMI hotkeys: Applying InputClass "evdev keyboard catchall"
===================================================

The only information I can find is in the following comment to a related bug report:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/978807/comments/101

The synaptics module is installed on my system, the /etc/X11/xorg.conf.d/ directory does not exist, and /usr/share/X11/xorg.conf.d/50-synaptics.conf contains an input section identifed as touchpad catchall. I'm not quite sure what the remaining files in this directoy should be or contain to classify as "pristine" and also not quite sure if anything else is required in the 50-synaptics.conf file.

Anyone have suggestions on how to get Cypress assigned to the Synaptics module so I can enjoy two-finger scrolling and other touchpad goodies?

Thanks,
Gary Parr

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Kamal Mostafa
Solved:
Last query:
Last reply:
Revision history for this message
Jonathan Wright (jonathan.we7) said : 		#1

I've just installed 12.10 64-bit on my XPS 12 and I'm experiencing the same:

―― 17:57 jonathan@llyr
―― ~ » dmesg | grep Cypress
[ 2.886886] input: PS/2 Cypress Trackpad as /devices/platform/i8042/serio1/input/input7

Xorg.0.log:

[ 5.037] (II) config/udev: Adding input device PS/2 Cypress Trackpad (/dev/input/event7)
[ 5.037] (**) PS/2 Cypress Trackpad: Applying InputClass "evdev pointer catchall"
[ 5.037] (II) Using input driver 'evdev' for 'PS/2 Cypress Trackpad'
[ 5.037] (**) PS/2 Cypress Trackpad: always reports core events
[ 5.037] (**) evdev: PS/2 Cypress Trackpad: Device: "/dev/input/event7"
[ 5.037] (--) evdev: PS/2 Cypress Trackpad: Vendor 0x2 Product 0x1
[ 5.037] (--) evdev: PS/2 Cypress Trackpad: Found 3 mouse buttons
[ 5.037] (--) evdev: PS/2 Cypress Trackpad: Found relative axes
[ 5.037] (--) evdev: PS/2 Cypress Trackpad: Found x and y relative axes
[ 5.037] (II) evdev: PS/2 Cypress Trackpad: Configuring as mouse
[ 5.037] (**) evdev: PS/2 Cypress Trackpad: YAxisMapping: buttons 4 and 5
[ 5.037] (**) evdev: PS/2 Cypress Trackpad: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 5.037] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event7"
[ 5.037] (II) XINPUT: Adding extended input device "PS/2 Cypress Trackpad" (type: MOUSE, id 12)
[ 5.037] (II) evdev: PS/2 Cypress Trackpad: initialized for relative axes.
[ 5.037] (**) PS/2 Cypress Trackpad: (accel) keeping acceleration scheme 1
[ 5.037] (**) PS/2 Cypress Trackpad: (accel) acceleration profile 0
[ 5.037] (**) PS/2 Cypress Trackpad: (accel) acceleration factor: 2.000
[ 5.037] (**) PS/2 Cypress Trackpad: (accel) acceleration threshold: 4
[ 5.037] (II) config/udev: Adding input device PS/2 Cypress Trackpad (/dev/input/mouse1)
[ 5.037] (II) No input driver specified, ignoring this device.
[ 5.037] (II) This device may have been added with another device file.

Revision history for this message
GaryParr (gary-garyparr) said : 		#2

Jonathan, does your touch sreen work as expected (scrolling, resizing, etc)? Mine does not. It lists correctly for xinput (Atmel Atmel maXTouch Digitizer) but none of the multi-touch events work. I'm wondering if it is related (not being assigned to the correct input module) but I have no idea how to even check that or what it should be.

gary@gannett:~$ more /var/log/Xorg.0.log | grep Atmel
[ 307.041] (II) config/udev: Adding input device Atmel Atmel maXTouch Digitizer (/dev/input/event5)
[ 307.041] (**) Atmel Atmel maXTouch Digitizer: Applying InputClass "evdev touchscreen catchall"
[ 307.041] (II) Using input driver 'evdev' for 'Atmel Atmel maXTouch Digitizer'
[ 307.041] (**) Atmel Atmel maXTouch Digitizer: always reports core events
[ 307.041] (**) evdev: Atmel Atmel maXTouch Digitizer: Device: "/dev/input/event5"
[ 307.041] (--) evdev: Atmel Atmel maXTouch Digitizer: Vendor 0x3eb Product 0x8409
[ 307.041] (--) evdev: Atmel Atmel maXTouch Digitizer: Found absolute axes
[ 307.041] (--) evdev: Atmel Atmel maXTouch Digitizer: Found absolute multitouch axes
[ 307.041] (--) evdev: Atmel Atmel maXTouch Digitizer: Found x and y absolute axes
[ 307.041] (--) evdev: Atmel Atmel maXTouch Digitizer: Found absolute touchscreen
[ 307.041] (II) evdev: Atmel Atmel maXTouch Digitizer: Configuring as touchscreen
[ 307.041] (**) evdev: Atmel Atmel maXTouch Digitizer: YAxisMapping: buttons 4 and 5
[ 307.041] (**) evdev: Atmel Atmel maXTouch Digitizer: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 307.041] (II) XINPUT: Adding extended input device "Atmel Atmel maXTouch Digitizer" (type: TOUCHSCREEN, id 9)
[ 307.041] (II) evdev: Atmel Atmel maXTouch Digitizer: initialized for absolute axes.
[ 307.041] (**) Atmel Atmel maXTouch Digitizer: (accel) keeping acceleration scheme 1
[ 307.041] (**) Atmel Atmel maXTouch Digitizer: (accel) acceleration profile 0
[ 307.041] (**) Atmel Atmel maXTouch Digitizer: (accel) acceleration factor: 2.000
[ 307.041] (**) Atmel Atmel maXTouch Digitizer: (accel) acceleration threshold: 4
[ 307.042] (II) config/udev: Adding input device Atmel Atmel maXTouch Digitizer (/dev/input/mouse0)
gary@gannett:~$ dmesg | grep Atmel
[ 1.880973] usb 1-1.2: Product: Atmel maXTouch Digitizer
[ 1.880976] usb 1-1.2: Manufacturer: Atmel
[ 2.129031] hid-generic 0003:03EB:8409.0002: hiddev0,hidraw0: USB HID v1.11 Device [Atmel Atmel maXTouch Digitizer] on usb-0000:00:1a.0-1.2/input1
[ 2.149186] input: Atmel Atmel maXTouch Digitizer as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input5
[ 2.150742] hid-multitouch 0003:03EB:8409.0001: input,hiddev0,hidraw1: USB HID v1.11 Device [Atmel Atmel maXTouch Digitizer] on usb-0000:00:1a.0-1.2/input0

Revision history for this message
Jonathan Wright (jonathan.we7) said : 		#3

Gary, I am in the same situation. I think there's some underlying conflict between the two. When I was installing RubyMine, I couldn't use the trackpad to click on any of application (but could control the Window Manager border), but I could with the touchscreen.

But yeah, I've no multi-touch on either the trackpad or the touchscreen - just basic click and hold with a press on the screen, and no touch-to-click on the trackpad either.

Everything seams to be loading and recognized, but it's just not working together. :(

Revision history for this message
bjoern (kenonu) said : 		#4

All the same here with my XPS 12 - i disabled the Touchscreen because every time I touched the display the Touchpad wn work in Nautilus - but only when are in Symbol view - try the list view and it works.
But I can scroll or do any other gestures of the Touchpad. Do you have the Sputnik Kernel installed?

Revision history for this message
GaryParr (gary-garyparr) said : 		#5

I have the Sputnik kernel installed:

===
gary@gannett:~$ uname -a
Linux gannett 3.5.0-25-generic #38+kamal13~DellXPS-Ubuntu SMP Tue Feb 19 23:00:06 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
===

Touchpad does not provide scrolling or any multi-touch capabilties as a touch pad should. I'm convinced the problem is that the touchpad is not being assigned to the synaptics input module, so none of those features are available.

Revision history for this message
bjoern (kenonu) said : 		#6

same problem over there http://askubuntu.com/questions/218274/12-10-nautilus-on-dell-xps-12-does-not-work

Revision history for this message
GaryParr (gary-garyparr) said : 		#7

Eh, I think that nautilus issue is unrelated.

Revision history for this message
Jonathan Wright (jonathan.we7) said : 		#8

Agreed. The Nautilus issue (although affecting me too) is unrelated as that's an error in the Nautilus code for expecting a secondary part of the event.

We're suffering a more fundamental issue with the way the touch-screen and trackpad are interacting with the system together preventing both from working as they should.

Gary: I find it interesting that I did my install and updates yesterday (21st), yet I seam to have an older kernel than you:

―― 08:33 jonathan@llyr
―― ~ » uname -a
Linux llyr 3.5.0-24-generic #37+kamal13~DellXPS-Ubuntu SMP Thu Feb 14 20:12:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Well, anyway, I've updated and I'm running the same kernel as you. No change.

But, looking back at the Xorg.0.log file, the Atmel maXTouch section shows a similar progress as the Cypress lines:

[ 4.851] (II) config/udev: Adding input device Atmel Atmel maXTouch Digitizer (/dev/input/event5)
[ 4.851] (**) Atmel Atmel maXTouch Digitizer: Applying InputClass "evdev touchscreen catchall"
[ 4.851] (II) Using input driver 'evdev' for 'Atmel Atmel maXTouch Digitizer'
[ 4.851] (**) Atmel Atmel maXTouch Digitizer: always reports core events
[ 4.851] (**) evdev: Atmel Atmel maXTouch Digitizer: Device: "/dev/input/event5"
[ 4.851] (--) evdev: Atmel Atmel maXTouch Digitizer: Vendor 0x3eb Product 0x8409
[ 4.852] (--) evdev: Atmel Atmel maXTouch Digitizer: Found absolute axes
[ 4.852] (--) evdev: Atmel Atmel maXTouch Digitizer: Found absolute multitouch axes
[ 4.852] (--) evdev: Atmel Atmel maXTouch Digitizer: Found x and y absolute axes
[ 4.852] (--) evdev: Atmel Atmel maXTouch Digitizer: Found absolute touchscreen
[ 4.852] (II) evdev: Atmel Atmel maXTouch Digitizer: Configuring as touchscreen
[ 4.852] (**) evdev: Atmel Atmel maXTouch Digitizer: YAxisMapping: buttons 4 and 5
[ 4.852] (**) evdev: Atmel Atmel maXTouch Digitizer: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 4.852] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input5/event5"
[ 4.852] (II) XINPUT: Adding extended input device "Atmel Atmel maXTouch Digitizer" (type: TOUCHSCREEN, id 9)
[ 4.852] (II) evdev: Atmel Atmel maXTouch Digitizer: initialized for absolute axes.
[ 4.852] (**) Atmel Atmel maXTouch Digitizer: (accel) keeping acceleration scheme 1
[ 4.852] (**) Atmel Atmel maXTouch Digitizer: (accel) acceleration profile 0
[ 4.852] (**) Atmel Atmel maXTouch Digitizer: (accel) acceleration factor: 2.000
[ 4.852] (**) Atmel Atmel maXTouch Digitizer: (accel) acceleration threshold: 4
[ 4.852] (II) config/udev: Adding input device Atmel Atmel maXTouch Digitizer (/dev/input/mouse0)
[ 4.852] (II) No input driver specified, ignoring this device.
[ 4.852] (II) This device may have been added with another device file.

Both of these finish with the same last two lines when it comes to recognising it as a mouse0: No driver, ignoring device?

Revision history for this message
Jonathan Wright (jonathan.we7) said : 		#9

Partial success:

mkdir -p /etc/X11/xorg.conf.d/

Create 50-synaptics.conf with the following contents:

Section "InputClass"
        Identifier "Amtel maXTouch Touchscreen"
        Driver "synaptics"
        MatchDevicePath "/dev/input/mouse0"
EndSection

Section "InputClass"
        Identifier "PS/2 Cypress Touchpad"
        Driver "synaptics"
        MatchDevicePath "/dev/input/mouse1"
EndSection

The touch screen begings to work and I can do things like three-finger control (move, resize, etc.).

No luck with the touchpard yet - still not showing in 'Mouse and Touchpad'.

Revision history for this message
Jonathan Wright (jonathan.we7) said : 		#10

With the following in /etc/X11/xorg.conf.d/50-synaptics.conf (touchscreen still working even with this setup):

Section "InputClass"
        Identifier "Amtel maXTouch Touchscreen"
        Driver "evdev"
        MatchDevicePath "/dev/input/event5"
EndSection

Section "InputClass"
        Identifier "PS/2 Cypress Touchpad"
        Driver "evdev"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event7"
EndSection

Section "InputClass"
        Identifier "PS/2 Cypress Touchpad"
        Driver "synaptics"
        MatchDevicePath "/dev/input/mouse1"
EndSection

I see the following:

[ 1758.713] (II) config/udev: Adding input device PS/2 Cypress Trackpad (/dev/input/mouse1)
[ 1758.713] (**) PS/2 Cypress Trackpad: Applying InputClass "PS/2 Cypress Touchpad"
[ 1758.713] (II) LoadModule: "synaptics"
[ 1758.713] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 1758.713] (II) Module synaptics: vendor="X.Org Foundation"
[ 1758.713] compiled for 1.12.99.905, module version = 1.6.2
[ 1758.713] Module class: X.Org XInput Driver
[ 1758.713] ABI class: X.Org XInput driver, version 18.0
[ 1758.713] (II) Using input driver 'synaptics' for 'PS/2 Cypress Trackpad'
[ 1758.714] (**) PS/2 Cypress Trackpad: always reports core events
[ 1758.714] (**) Option "Device" "/dev/input/mouse1"
[ 1758.714] (EE) synaptics: PS/2 Cypress Trackpad: Synaptics driver unable to detect protocol
[ 1758.714] (EE) PreInit returned 11 for "PS/2 Cypress Trackpad"
[ 1758.714] (II) UnloadModule: "synaptics"

So synaptics is not running, but more telling:

[ 1983.164] (II) evdev: PS/2 Cypress Trackpad: Configuring as mouse

It seams something in evdev is not allowing this to work as a touchpad?

Revision history for this message
Jonathan Wright (jonathan.we7) said : 		#11

This is looking more-and-more like an issue within evdev:

From /usr/share/X11/xorg.conf.d/10-evdev.conf it can only match the InputClass where 'MatchIsPointer "on"' is set. It doesn't trigger on 'MatchIsTouchpad "on"' and if I disable the whole input section which has 'MatchIsPoint "on"' set, Xorg doesn't see or configure it at all.

I'll look more over the weekend I think.

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#12

I suggest you contact the PPA maintainer.

Revision history for this message
GaryParr (gary-garyparr) said : 		#13

Jonathan, when I first pulled in the Sputnik PPA I had the 3.5.0-24 kernel as well. When I started trying to figure this out I noticed the newer kernel in the PPA and pulled it down to see if it made a difference.

Andrew, I can try contacting the PPA maintainer but if Jonathan is right and this is an issue with evdev then it might not be anything they can control.

Revision history for this message
Best Kamal Mostafa (kamalmostafa) said : 		#14

Folks, we have a fix for the Cypress trackpad problem on XPS12 (unrelated to the touchscreen issue):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1103594

The fix to enable the Cypress PS/2 trackpad in the Dell XPS12 (and possibly other laptops) now appears in the standard Ubuntu Raring kernel (as of 3.8.0-7.15) and is pending inclusion upstream in the mainline Linux 3.9 kernel.

The fix will also be applied to the standard Ubuntu Precise (12.04) and Quantal (12.10) kernels in the near future. In the meantime, the fix for those Ubuntu versions will be available via the Sputnik Project kernel PPA. Sputnik kernel version "kamal14" (available within a few hours) enables the Cypress trackpad on the XPS12:

  https://launchpad.net/~canonical-hwe-team/+archive/sputnik-kernel

Revision history for this message
GaryParr (gary-garyparr) said : 		#15

Kamal, thanks for the information. I (and I'm sure Jonathan) will be eagerly awaiting your kernel release.

Revision history for this message
Jonathan Wright (jonathan.we7) said : 		#16

That's brilliant news! Many thanks for your work on that and I too look forward to trying it out.

Revision history for this message
GaryParr (gary-garyparr) said : 		#17

Now we just need to figure out the touch screen issues.

Revision history for this message
GaryParr (gary-garyparr) said : 		#18

Thanks Kamal Mostafa, that solved my question.

Revision history for this message
GaryParr (gary-garyparr) said : 		#19

The fix for the touch pad broke the workaround for the touch screen.

[ 516.632] (II) Using input driver 'synaptics' for 'Atmel Atmel maXTouch Digitizer'
[ 516.632] (**) Atmel Atmel maXTouch Digitizer: always reports core events
[ 516.632] (EE) synaptics: Atmel Atmel maXTouch Digitizer: Synaptics driver unable to detect protocol
[ 516.632] (EE) PreInit returned 11 for "Atmel Atmel maXTouch Digitizer"
(EE) [dix] Atmel Atmel maXTouch Digitizer: unable to find touch point 2

Kamal, would you happen to have any suggestions where we could go and look for a solution to this? Would this be a bug to file against the Sputnik kernel or something else?

Thanks!

Revision history for this message
Jonathan Wright (jonathan.we7) said : 		#20

Gary, did you remove all the configuration from /etc/X11/xorg.conf.d/ (should be empty)? I did that before I rebooted and my touchscreen is working fine (as is the touchpad now too) off the default configuration.

Revision history for this message
GaryParr (gary-garyparr) said : 		#21

That was the first thing I tried, but it didn't work for me. I have no multi-touch at all on the screen.

Revision history for this message
GaryParr (gary-garyparr) said : 		#22

Does your X log look different than this?

gary@gannett:~$ more /var/log/Xorg.0.log | grep Atmel
[ 5.047] (II) config/udev: Adding input device Atmel Atmel maXTouch Digitizer (/dev/input/event5)
[ 5.047] (**) Atmel Atmel maXTouch Digitizer: Applying InputClass "evdev touchscreen catchall"
[ 5.047] (II) Using input driver 'evdev' for 'Atmel Atmel maXTouch Digitizer'
[ 5.047] (**) Atmel Atmel maXTouch Digitizer: always reports core events
[ 5.047] (**) evdev: Atmel Atmel maXTouch Digitizer: Device: "/dev/input/event5"
[ 5.048] (--) evdev: Atmel Atmel maXTouch Digitizer: Vendor 0x3eb Product 0x8409
[ 5.048] (--) evdev: Atmel Atmel maXTouch Digitizer: Found absolute axes
[ 5.048] (--) evdev: Atmel Atmel maXTouch Digitizer: Found absolute multitouch axes
[ 5.048] (--) evdev: Atmel Atmel maXTouch Digitizer: Found x and y absolute axes
[ 5.048] (--) evdev: Atmel Atmel maXTouch Digitizer: Found absolute touchscreen
[ 5.048] (II) evdev: Atmel Atmel maXTouch Digitizer: Configuring as touchscreen
[ 5.048] (**) evdev: Atmel Atmel maXTouch Digitizer: YAxisMapping: buttons 4 and 5
[ 5.048] (**) evdev: Atmel Atmel maXTouch Digitizer: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 5.048] (II) XINPUT: Adding extended input device "Atmel Atmel maXTouch Digitizer" (type: TOUCHSCREEN, id 9)
[ 5.048] (II) evdev: Atmel Atmel maXTouch Digitizer: initialized for absolute axes.
[ 5.048] (**) Atmel Atmel maXTouch Digitizer: (accel) keeping acceleration scheme 1
[ 5.048] (**) Atmel Atmel maXTouch Digitizer: (accel) acceleration profile 0
[ 5.048] (**) Atmel Atmel maXTouch Digitizer: (accel) acceleration factor: 2.000
[ 5.048] (**) Atmel Atmel maXTouch Digitizer: (accel) acceleration threshold: 4
[ 5.048] (II) config/udev: Adding input device Atmel Atmel maXTouch Digitizer (/dev/input/mouse0)

Revision history for this message
bjoern (kenonu) said : 		#23

can agree works with the new kernel from kamal

Revision history for this message
bjoern (kenonu) said : 		#24

can agree works with the new kernel from kamal

Revision history for this message
GaryParr (gary-garyparr) said : 		#25

OK, on a whim I reinstalled 12.10 from scratch (accidentally wiped out my Win8 installation) and added the Sputnik PPA, performed an apt-update and apt-get dist-upgrade and same result. My touchpad is great but I have no multi-touch on the screen. Very odd.

Revision history for this message
GaryParr (gary-garyparr) said : 		#26

I had to use the Dell system restore disks to get Win8 back on here, which meant I had to reinstall Ubuntu (again). This time, I performed an update before adding the Sputnik PPA and pulling in the new kernel. This time, I have basic multi-touch on the screen (three finger resize). So, there appears to be an order-of-opertaions issue at play here. I still do not have two-finger scroll on the touchscreen, but I'm closer.

Revision history for this message
Jonathan Wright (jonathan.we7) said : 		#27

Interestingly, I've just had a similar experience myself - I rebooted the laptop after an update with 3.5.0-26-generic kernel and lost the touchpad but kept the touchscreen. Rebooting with 3.5.0-25-generic fixed that.

Whatever was fixed in 3.5.0-25 seams to now be broken again in 3.5.0-26.

Revision history for this message
GaryParr (gary-garyparr) said : 		#28

Jonathan, where did you get the 26 from? I don't see that in the main repository or the Sputnik PPA? Based on your experience I won't install it... just wondering where you pulled it from...

Revision history for this message
Jonathan Wright (jonathan.we7) said : 		#29

I don't know where I got it from - just came down one afternoon. In any respect, I've just pulled down the latest version:

―― 14:11 jonathan@llyr
―― ~ » uname -a
Linux llyr 3.5.0-26-generic #40+kamal15~DellXPS-Ubuntu SMP Mon Mar 4 19:08:34 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Everything's back to normal and and working again on this latest release.