ubuntu-x-swat team mailing list archive
-
ubuntu-x-swat team
-
Mailing list archive
-
Message #94887
[Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
First, thanks to all those working on the nw_fermi module.
But I'm afraid I'm getting nothing from either cat or evtest.
With vanilla 10.04.1 64 bit with all updates plus nvidia driver and the xserver-xorg-input-evtouch package.
and nwfermi-0.2_i386.deb recompiled as per message by Jeff Bower post #74 omitting the seds as running 2.6.32-25-generic
running on a Sony Vaio all in one VPCL12M1E
from /var/log/messages
.
Oct 13 17:37:28 ubuntuvaio kernel: [ 2.959812] generic-usb 0003:1926:0065.0003: hiddev97,hidraw2: USB HID v1.11 Device [NextWindo
w Touchscreen] on usb-0000:00:1a.2-2/input1
.
.
Oct 13 17:37:28 ubuntuvaio kernel: [ 10.346964] input: Nextwindow Fermi Touchscreen as /devices/virtual/input/input9
Oct 13 17:37:28 ubuntuvaio kernel: [ 10.347064] nwfermi 5-2:1.0: NextWindow Fermi device now attached to nwfermi-192
Oct 13 17:37:28 ubuntuvaio kernel: [ 10.347092] usbcore: registered new interface driver nwfermi
.
sudo lsinput
/dev/input/event9
bustype : (null)
vendor : 0x0
product : 0x0
version : 0
name : "Nextwindow Fermi Touchscreen"
bits ev : EV_SYN EV_KEY EV_ABS
lsusb gives:-
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 002: ID 046d:c52f Logitech, Inc.
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 1926:0065
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 0489:e00f Foxconn / Hon Hai
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 054c:0374 Sony Corp.
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 05ca:18b5 Ricoh Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
As per Peter Adamka post #76 I have only the nvidia config.
xorg log:-
(II) config/udev: Adding input device Nextwindow Fermi Touchscreen (/dev/input/event9)
(**) Nextwindow Fermi Touchscreen: Applying InputClass "evdev pointer catchall"
(**) Nextwindow Fermi Touchscreen: always reports core events
(**) Nextwindow Fermi Touchscreen: Device: "/dev/input/event9"
(II) Nextwindow Fermi Touchscreen: Found 3 mouse buttons
(II) Nextwindow Fermi Touchscreen: Found absolute axes
(II) Nextwindow Fermi Touchscreen: Found x and y absolute axes
(II) Nextwindow Fermi Touchscreen: Configuring as mouse
(**) Nextwindow Fermi Touchscreen: YAxisMapping: buttons 4 and 5
(**) Nextwindow Fermi Touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Nextwindow Fermi Touchscreen" (type: MOUSE)
(II) Nextwindow Fermi Touchscreen: initialized for absolute axes.
(II) config/udev: Adding input device Nextwindow Fermi Touchscreen (/dev/input/js1)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device Nextwindow Fermi Touchscreen (/dev/input/mouse3)
(II) No input driver/identifier specified (ignoring)
Any pointers on what I may have missed would be much appreciated as it is very frustrating to be so close yet dis-functional.
Note I have not used newer nwfermi as thought that they might only work on newer kernels.
Thanks.
--
Handling NextWindow Touchscreen (multitouch)
https://bugs.launchpad.net/bugs/379313
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in ubuntu.
References