driver not loaded in ubuntu 12.04 64 bits
My used Ubuntu version is 12.04.1 64 bits. US locales
Kernel: 3.2.0-34-generic
The hardware platform is a Intel i3 Mobile with 2Gbyte memory.
On the site: https:/
Deu to no documentation there I have found this site with explanation how to install (assuming they are correct):
http://
Or is there other documentation available witch I have not found.
I have applied in the rc.local these information:
sh -c "echo 1926 0266 > /sys/bus/
usr/sbin/
The rest is the same.
Have used the latest versions from the PPA and nwfermi. Deu to 64 bits
installation I also installed the ia32-libs needed for installing the
nwfermi deb.
I can see the deamon running in the background but Xorg.0.log says this:
[ 518.359] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/event2)
[ 518.359] (II) No input driver specified, ignoring this device.
[ 518.359] (II) This device may have been added with another device file.
[ 518.359] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/event3)
[ 518.359] (**) NextWindow Touchscreen: Applying InputClass "evdev pointer catchall"
[ 518.359] (II) Using input driver 'evdev' for 'NextWindow Touchscreen'
[ 518.359] (II) Loading /usr/lib/
[ 518.359] (**) NextWindow Touchscreen: always reports core events
[ 518.359] (**) evdev: NextWindow Touchscreen: Device: "/dev/input/event3"
[ 518.359] (--) evdev: NextWindow Touchscreen: Vendor 0x1926 Product 0x266
[ 518.359] (--) evdev: NextWindow Touchscreen: Found 3 mouse buttons
[ 518.359] (--) evdev: NextWindow Touchscreen: Found absolute axes
[ 518.359] (--) evdev: NextWindow Touchscreen: Found x and y absolute axes
[ 518.359] (--) evdev: NextWindow Touchscreen: Found absolute touchscreen
[ 518.359] (II) evdev: NextWindow Touchscreen: Configuring as touchscreen
[ 518.359] (**) evdev: NextWindow Touchscreen: YAxisMapping: buttons 4 and 5
[ 518.359] (**) evdev: NextWindow Touchscreen: EmulateWheelButton: 4, EmulateWheelIne
[ 518.359] (**) Option "config_info" "udev:/
[ 518.359] (II) XINPUT: Adding extended input device "NextWindow Touchscreen" (type: TOUCHSCREEN, id 9)
[ 518.359] (II) evdev: NextWindow Touchscreen: initialized for absolute axes.
[ 518.359] (**) NextWindow Touchscreen: (accel) keeping acceleration scheme 1
[ 518.359] (**) NextWindow Touchscreen: (accel) acceleration profile 0
[ 518.359] (**) NextWindow Touchscreen: (accel) acceleration factor: 2.000
[ 518.359] (**) NextWindow Touchscreen: (accel) acceleration threshold: 4
[ 518.360] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/js0)
[ 518.360] (II) No input driver specified, ignoring this device.
[ 518.360] (II) This device may have been added with another device file.
[ 518.360] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/mouse0)
[ 518.360] (II) No input driver specified, ignoring this device.
[ 518.360] (II) This device may have been added with another device file.
xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ NextWindow Touchscreen id=9 [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)]
↳ Power Button id=8 [slave keyboard (3)]
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 003: ID 1926:0266 NextWindow
It looks like the 70-nw-fermi.conf match does not work and the normal
evdev is used. Even using the devices hardcoded the multi-touch does not
work.
I have used this application for testing:
https:/
mouse=hidinput,
What can I do or find more information about this?
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- nwfermi Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Johan Smits
- Solved:
- Last query:
- Last reply: