[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
@Chase, Thanks for the info. My xorg input module has a touch helper to detect right clicks etc (like the tablet pc service in windows), I am trying to get permission to convert this into a patch for possible inclusion into xorg evdev. I saw your evdev hooks into grails and have been testing the same with my driver but in the future hope to be able to use evdev directly. @Bryce, cheers @All, I am closing this bug now. Please feel free to log individual questions or issues: - https://bugs.launchpad.net/nwfermi - https://answers.launchpad.net/nwfermi ** Changed in: nwfermi Status: New = Won't Fix -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
Has anyone been able to get this to work on 10.04-1 x64? I had it working in 32 mode, but now I can't seem to get it to work on the Sony VAIO VPCL135FX. My Xorg.log shows: (II) config/udev: Adding input device Nextwindow Fermi Touchscreen (/dev/input/event10) (**) Nextwindow Fermi Touchscreen: Applying InputClass evdev pointer catchall (**) Nextwindow Fermi Touchscreen: Applying InputClass nw fermi (II) LoadModule: nextwindow (II) Loading /usr/lib/xorg/modules/input/nextwindow_drv.so (II) Module nextwindow: vendor=X.Org Foundation compiled for 1.9.0, module version = 0.0.1 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 11.0 (WW) module ABI major version (11) doesn't match the server's version (7) (**) Option Device /dev/input/event10 (II) Nextwindow Fermi Touchscreen: Using device /dev/input/event10. (**) Option UseTouchHelp 1 (II) Nextwindow Fermi Touchscreen: Using touch help. (**) Option DragThreshold 10 (**) Option RightClickTimeout 1200 (**) Option DoubleClickTimeout 500 (**) Nextwindow Fermi Touchscreen: always reports core events (II) XINPUT: Adding extended input device Nextwindow Fermi Touchscreen (type: TOUCHSCREEN) (II) Nextwindow Fermi Touchscreen: On. (II) config/udev: Adding input device Nextwindow Fermi Touchscreen (/dev/input/js0) (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) (II) config/udev: Adding input device Macintosh mouse button emulation (/dev/input/event2) (**) Macintosh mouse button emulation: Applying InputClass evdev pointer catchall (**) Macintosh mouse button emulation: always reports core events (**) Macintosh mouse button emulation: Device: /dev/input/event2 (II) Macintosh mouse button emulation: Found 3 mouse buttons (II) Macintosh mouse button emulation: Found relative axes (II) Macintosh mouse button emulation: Found x and y relative axes (II) Macintosh mouse button emulation: Configuring as mouse (**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5 (**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (II) XINPUT: Adding extended input device Macintosh mouse button emulation (type: MOUSE) (II) Macintosh mouse button emulation: initialized for relative axes. (II) config/udev: Adding input device Macintosh mouse button emulation (/dev/input/mouse0) (II) No input driver/identifier specified (ignoring) (II) config/udev: Adding input device Sony Vaio Jogdial (/dev/input/event9) (II) No input driver/identifier specified (ignoring) (II) config/udev: Adding input device Sony Vaio Jogdial (/dev/input/mouse2) (II) No input driver/identifier specified (ignoring) but nothing seems to work. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
Ubuntu, and Ubuntu but how about Gentoo? How i can run this driver on other Linux based operating systems for desktop x86/amd64 computers? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
djp, For full multitouch support both in Ubuntu 10.10 and future releases, the X evdev input module should be used. In 10.10 this will enable support for the uTouch stack, and in 11.04 this will allow for multitouch support through the X window system. One should not need to use a different X input module. If you are using a different X input module, please provide more information so we can figure out the best way forward. Just to clarify, Ubuntu 10.10 desktop edition has uTouch support as well, but the only package with uTouch integration is the Unity window manager. Since Unity doesn't come with 10.10 by default, it seems like uTouch is missing even though it's still there :). Natty will have more integration across multiple apps, and the desktop edition will ship Unity by default too. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
Moving this bug report from 'xorg' to the new 'nwfermi' project. At this time this driver is not shipped with the ubuntu distribution but rather provided by a PPA, so support will be at https://bugs.launchpad.net/nwfermi/ and the Ubuntu distro task is a 'Wont Fix'. (Actually, maybe some day it will be included in ubuntu once distribution terms are sorted and so on, but that bridge can be crossed in its own time.) I would recommend people file reports about new issues as new bugs rather than adding to this bug report. I expect djp will prefer to close this bug report now that the issues can be handled individually, but I'll leave that to him. :-) https://bugs.launchpad.net/nwfermi/+filebug ** Also affects: nwfermi Importance: Undecided Status: New ** Changed in: xorg (Ubuntu) Status: In Progress = Won't Fix -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
I tested nwfermi0.5 on Ubuntu and Gentoo Linux but multi-touch is still not working. My device: Bus 001 Device 008: ID 1926:0086 NextWindow 1950 HID Touchscreen I just see single mouse, cant touch more than one point on screen - its looks like single touch. On Ubuntu i just installed package and restarted computer, on Gentoo Linux i copied all files, built kernel module, modified xorg configuration - it should work but it isn't. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
Same as WebNuLL, on Ubuntu Lucid after installing package and restarted computer, multitouch don't work. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
Here is /var/log/Xorg.0.log Xorg recognizing device, but i think it not classifying it as multi- touch capable. ** Attachment added: xorg-nw-fermi https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/379313/+attachment/1797024/+files/xorg-nw-fermi -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
I tried many combinations of input xorg settings in 70-nwfermi.conf but it still doesn't work. Any help? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
Im not a C programmer but i debugged the code, and found that kernel module is always handling touchscreen as mouse. ** Attachment added: fermi-debug https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/379313/+attachment/1797040/+files/fermi-debug -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
As far as I know the X included with ubuntu does not handle multitouch input directly. Ubuntu has a multitouch framework called uTouch (not installed on the desktop edition by default (https://wiki.ubuntu.com/Multitouch). If you want to relatively easily test if the kernel multitouch information is being supplied a good example is the PyMT demo (https://wiki.ubuntu.com/Multitouch/PyMT). Although my X input driver might be blocking the gesture daemon somehow... Anyhow post bug reports at https://bugs.launchpad.net/nwfermi -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
A annoncement for anyone who was waiting for multitouch support. There is now a new release (0.5) at https://launchpad.net/nwfermi/trunk/nwfermi0.5 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
Ok I have created a launchpad project for nwfermi (https://launchpad.net/nwfermi). Future nwfermi releases will be posted there and anyone interested should be able to post bug reports, questions, etc. I havent made much progress with creating a source package for the ppa yet (the various different tools and methods are overwhelming me!) but should have a multitouch release ready shortly. Cheers again for all the help Bryce. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
On Fri, Dec 24, 2010 at 02:28:50AM -, djp wrote: @Bryce, cheers that is helpful I will try to make a PPA early next year. I do have one question, is it possible to put a EULA type agreement (do not sue us etc) into a deb or PPA? You can put it into the deb. The PPA has a description field, but it's purely informational and doesn't support click-thru-agreement type behavior. It's good for putting directions or caveats. Regarding EULAs in debs, I've never done this myself, but you can put a question into the preinst script. Some more info (and a tutorial): http://stackoverflow.com/questions/2154352/including-license-agreement-in-deb-file Not sure how that'd work in conjunction with a PPA, so you'll want to test it. IIRC, it just does a text prompt on the command line, but hopefully that'll get you in the right direction. Some packages like mscorefonts and iirc some java packages include install-time eula agreements, which might be worth studying. Fwiw I think fglrx and nvidia do *not* require click thru's, but I'm not sure how they handle the EULA agreement - perhaps the way they solved it would be worth looking at as an alternate approach. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
Alright, I'm going to move this bug report off -evdev and back to just xorg for now (actually I think it really should belong to the kernel, but we'll continue tracking it with X for now). It sounds like this package will be requiring an EULA, which makes me doubtful it's something we can distribute with Ubuntu itself. Thus I'll decline the nominations and drop the natty tag for now. ** Package changed: xserver-xorg-input-evdev (Ubuntu) = xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
djp, I would recommend that you create a nwfermi project in launchpad for tracking the driver. You can do this here: https://launchpad.net/projects/+new It's pretty easy, and I'd do it for you but I think you'd be better as the owner of it so you have full control. Once you have a project set up, you can attach one or more PPAs to it, and we can move this bug report over to it. It will have its own bug tracker, and you can add public or private mailing lists if you'd like. It should be straightforward but if you have any questions, feel free to contact me directly. ** Tags removed: jaunty maverick natty needs-retested-on-lucid-by-june patch -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
I compiled kernel module, copied to /lib/modules/2.6.36-gentoo-r5/kernel/drivers/usb/nw-fermi.ko where i had old module. killall nwfermi_daemon -9 rmmod nw-fermi modprobe nw-fermi The mouse automaticaly is moving fastly from down right to up left corner very fast when i touch some point on screen i got old calibration and screen working normally without any changes on calibration. I will try today on Ubuntu (i have dualboot with Gentoo) to check whats wrong. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
What is the purpose of the user space daemon (nwfermi_daemon) since driver already uses event interface? As I am trying to use Dell touch screen monior with ARM dev board, it won't work for me because I can't find the armel daemon. djp, can you also release armel deb? Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
What is the purpose of the user space daemon (nwfermi_daemon) since driver already uses event interface? As I am trying to use Dell touch screen monior with ARM dev board, it won't work for me because I can't find the armel daemon. djp, can you also release armel deb? Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
@Bryce, cheers that is helpful I will try to make a PPA early next year. I do have one question, is it possible to put a EULA type agreement (do not sue us etc) into a deb or PPA? @Mathijs, there will a multitouch release in January, I havent seen nwtool but I will take a look @WebNuLL @ Aymeric, we already have a calibration facility, I will explain how to use it in this new release I am attaching fermi 0.4.5, the main fixes here are: - nwfermi_daemon udev coldboot doesnt always work - configuration settings are available via named pipe To start the calibration procedure run the following command: ‘echo -e C\x02\x21\x01 /tmp/nwfermi0-tl-in’ The cursor will move to four locations around the screen and to complete calibration you just need to touch and hold at the cursor positions untill they move to the next location. Upon successful calibration settings will be saved to /etc/nextwindow/nw- fermi/_XX_DriverSettings.dat, you can delete this file to return to factory defaults. I hope this is helpful you all. Cheers, Dan ** Attachment added: nwfermi-0.4.5_i386.deb https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/379313/+attachment/1774978/+files/nwfermi-0.4.5_i386.deb -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
** Attachment added: nwfermi-0.4.5_amd64.deb https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/379313/+attachment/1774979/+files/nwfermi-0.4.5_amd64.deb -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
After installing the nwfermi package on Ubuntu 10.04 my Samsung 22” Lapfit Touchscreen Monitor (LD220Z) work with the touchscreen. Like #118 it's not calibrated, I can touch the left corners but not the right. From the documentation of my screen, it seem to be multi-touch, but I don't know what application I can use to know if multi-touch work or not, so it's untested. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
Im now using NextWindow touchscreen on Gentoo Linux and it works fine. Its not callibrated (on Ubuntu too) - i can touch all but corners of screen. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
Hi, @djp: Can you perhaps give a status update of the nw-fermi driver that includes mutlitouch capabilities? @djp: have you also looked at the nwtool? It says it is able to set modes and save settings, (like those modes described in the Windows API). You can find nwtool here: https://patchwork.kernel.org/patch/64411/ Regards, Mathijs -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
djp, can you also add calibration possibility via xinput? I can calibrate eGalax touchscreen in Samsung Q1 Tablet PC with this command: xinput set-int-prop Touchkit HID-USB Touchscreen Evdev Axis Calibration 32 80 3950 150 3900 It works perfectly, can it be possible with nwfermi? Im installing Gentoo today, i dont know nwfermi will works correctly on it, can you implement calibration function to driver? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver
Hi djp, Since PPAs require uploading source packages rather than pre-built debs, what you'll need to do is create a wrapper source package, that contains the precompiled binaries. The build process for this package would merely copy the appropriate binary into place. I don't know if there is official documentation for doing this, but here's a guide that explains it with examples: http://www.debian-administration.org/articles/529 Hope this helps, let me know if you have more questions. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
@Bryce,
Yes some pointers on PPA packaging would be appreciated.
I will check what the distribution terms are and get back to you.
Thanks a lot,
Dan
On Fri, Dec 3, 2010 at 1:47 PM, Bryce Harrington
379...@bugs.launchpad.netwrote:
djp, you mentioned earlier an interest in posting this to a PPA. Do you
need help with this? Do you have a plan in place for how you want to be
distributing it to go into the PPA?
I think once that is sorted out, it would make it straightforward for us
to even consider incorporating this into multiverse with other closed
source drivers, which would make it even easier for Ubuntu users to
install it. I'm not sure what the process is for getting additional
closed source drivers accepted there, so that may or may not be
feasible, but once it's packaged for PPA I'd be willing to investigate
for you, if you'd like.
** Summary changed:
- Handling NextWindow Touchscreen (multitouch)
+ Handling NextWindow Touchscreen (multitouch) via the nwfermi
(proprietary) driver
--
You received this bug notification because you are a direct subscriber
of the bug.
https://bugs.launchpad.net/bugs/379313
Title:
Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary)
driver
Status in “xserver-xorg-input-evdev” package in Ubuntu:
Triaged
Bug description:
Binary package hint: xserver-xorg-input-evdev
Ubuntu 9.04/8.10 and probably other.
The NextWindow touch screen is used on the HP TouchSmart systems however
doesn't work out of the box on 8.10 or 9.04.
Firstly it is allocated to a synaptic touchpad driver initially which is
wrong, but can be overcome with the appropriate HAL fdi to change to evdev.
Secondly (and this is a most likely a problem of either the hardware or X),
it reports X, Y values using ABS_RX, ABS_Z rather than the expected ABS_X,
ABS_Y. The evtouch driver will work because it accepts these as
alternatives.
Lastly, because the system is multi-touch aware it reports to the xserver
that it has buttons. This causes it to be misclassified by evdev as a
touchpad rather than a touchscreen.
The following patch fixes the problem for me but is obviously not a general
solution. This is against packaged version 1:2.1.1-1ubuntu4:
--- src/evdev.c.orig2010-05-22 16:08:14.0 +1000
+++ src/evdev.c 2009-05-22 16:09:30.0 +1000
@@ -382,10 +382,12 @@
case EV_ABS:
switch (ev.code) {
+case ABS_Z:
case ABS_X:
pEvdev-abs_x = value;
abs = 1;
break;
+case ABS_RX:
case ABS_Y:
pEvdev-abs_y = value;
abs = 1;
@@ -1368,11 +1370,11 @@
xf86Msg(X_INFO, %s: Found x and y absolute axes\n, pInfo-name);
pEvdev-flags |= EVDEV_ABSOLUTE_EVENTS;
if (TestBit(BTN_TOUCH, key_bitmask)) {
-if (num_buttons) {
+/* if (num_buttons) {
xf86Msg(X_INFO, %s: Found absolute touchpad\n,
pInfo-name);
pEvdev-flags |= EVDEV_TOUCHPAD;
pEvdev-old_x = pEvdev-old_y = -1;
-} else {
+} else */ {
xf86Msg(X_INFO, %s: Found absolute touchscreen\n,
pInfo-name);
pEvdev-flags |= EVDEV_TOUCHSCREEN;
pEvdev-flags |= EVDEV_BUTTON_EVENTS;
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: xserver-xorg-input-evdev 1:2.1.1-1ubuntu4 [modified:
usr/lib/xorg/modules/input/evdev_drv.so]
ProcEnviron:
LANG=en_AU.UTF-8
SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-11-generic (bui...@crested) (gcc version
4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009
SourcePackage: xserver-xorg-input-evdev
Uname: Linux 2.6.28-11-generic x86_64
To unsubscribe from this bug, go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/379313/+subscribe
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in ubuntu.
https://bugs.launchpad.net/bugs/379313
Title:
Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary)
driver
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Dnia 2010-12-01, śro o godzinie 20:24 +, djp pisze: On Thu, Dec 2, 2010 at 1:31 AM, WebNuLL babciast...@gmail.com wrote: Question to author of this driver - there is any progress to bring multi-touch on this driver? Yes, this is going to be my priority now over the next few weeks Thank you, im waiting for it. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Thanks Chase. It sounds like support on the open source has some blockers, so for this bug report let's focus on the nwfermi driver. @djp, thanks for posting the .debs. It appears this contains a GPL'd kernel driver installable via dkms, and a closed binary nwfermi_daemon which is invoked using udev. Can you specify what the distribution terms are for nwfermi_daemon? Is it permissible for us to package and ship it in Ubuntu as a closed source driver? Because this driver does not depend on anything particular on the X side, I guess xserver-xorg-input-evdev is not the best component for it to be filed against, but I'm not certain of what package would be better (linux?) so will leave it here for now. ** Changed in: xserver-xorg-input-evdev (Ubuntu) Importance: Medium = Wishlist ** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
djp, you mentioned earlier an interest in posting this to a PPA. Do you need help with this? Do you have a plan in place for how you want to be distributing it to go into the PPA? I think once that is sorted out, it would make it straightforward for us to even consider incorporating this into multiverse with other closed source drivers, which would make it even easier for Ubuntu users to install it. I'm not sure what the process is for getting additional closed source drivers accepted there, so that may or may not be feasible, but once it's packaged for PPA I'd be willing to investigate for you, if you'd like. ** Summary changed: - Handling NextWindow Touchscreen (multitouch) + Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in ubuntu. https://bugs.launchpad.net/bugs/379313 Title: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Question to author of this driver - there is any progress to bring multi-touch on this driver? -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
On Thu, Dec 2, 2010 at 1:31 AM, WebNuLL babciast...@gmail.com wrote: Question to author of this driver - there is any progress to bring multi-touch on this driver? Yes, this is going to be my priority now over the next few weeks -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
On Wed, Dec 1, 2010 at 9:24 PM, djp 379...@bugs.launchpad.net wrote: On Thu, Dec 2, 2010 at 1:31 AM, WebNuLL babciast...@gmail.com wrote: Question to author of this driver - there is any progress to bring multi-touch on this driver? Yes, this is going to be my priority now over the next few weeks 2 weeks ago I asked NextWindow and they answered me here: http://twitter.com/#!/NextWindow/status/5389587354484736 i -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
This bug has a lot of data and comments in it. Could someone provide a summary of where things stand? What does this bug represent at this point? Is this bug really against 11.04 now, or are people looking for support for previous Ubuntu releases? 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
On Tue, Nov 30, 2010 at 05:56:35PM -, Chase Douglas wrote: This bug has a lot of data and comments in it. Could someone provide a summary of where things stand? What does this bug represent at this point? Is this bug really against 11.04 now, or are people looking for support for previous Ubuntu releases? Well, I'm mainly interested in what the support situation for this hardware should be in 11.04 and going forward, as I doubt any of this would qualify for SRU. Chase, key comments to look at here appear to be: Proprietary driver: #31 (original) and 89-90 (latest) evdev patches: #81 I'm not sure what the restrictions are on the proprietary driver as far as redistribution and so on, but the question is whether the MT work you're doing will cover this hardware sufficiently by itself? If not, then what would you need from the hardware vendor to include support in evdev/linux? If including support in the open does not look feasible for now, do you have any thoughts on the proprietary driver? ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Thanks Bryce! The MT work in X has taken a different form from what was proposed in the message linked in comment #31. However, we are getting near to having an XI 2.1 protocol extension for MT set. I hope to introduce some of the MT work into Natty soon. Kernel drivers need to be written for the MT evdev protocol to work properly. Either the slotted or non-slotted protocol will work, though slotted is better. If the kernel presents working MT evdev data, it will work with the X MT solution. It sounds like the NextWindow proprietary driver does not handle MT data quite yet though. The proprietary nature of the driver will have no affect on its ability to function in the MT stack in ubuntu. Proprietary MT drivers will always be a second class citizen on Ubuntu because they are not installed by default. In fact, this is the first time I've ever heard of a proprietary MT driver being used in Ubuntu. I would strongly recommend NextWindow to open the code or even just the specifications of the hardware so users have the best experience possible. In short: Yes, the proprietary driver will work when it is updated for MT support. Nothing extra will be needed in evdev or elsewhere. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Chase - could you take a look at this bug report and let us know how it fits with the multitouch development efforts? ** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: Incomplete = Confirmed -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
** Tags added: natty -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
http://www.youtube.com/watch?v=Z7djhhEjxJ0 -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Working on 2.6.37-2 kernel -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Yes ! I thought I tried with nw-fermi, but maybe I did something wrong, it's working perfectly know ! Thanks to you and djp to provide us this driver. Do you think my grandfather will be able to use multi-touch on his first computer anytime soon or is it to difficult to implement ? :) -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Im waiting for multi-touch too. But i think its difficult to implement. It can take a long time to bring multi-pointer support to this driver. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
insmod /lib/modules/$(uname -r)/updates/dkms/nw-fermi.ko or more simple: modprobe nw-fermi But this second works only if you update module dependencies (depmod -a) -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Hello there I'm trying to get touch work on dell inspiron one, I followed your instructions and everything goes fine until sudo insmod /lib/modules/$(uname -r)/updates/dkms which gives me the error insmod: can't read '/lib/modules/2.6.35-22-generic/updates/dkms/': Is a directory so I guess sudo depmod -a Doesn't do anything... And I'm new to this king of manipulations, what should we do next ? Just a modprob ? And it's supposed to work instantaneously ? 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
I installed 2.6.36-1 kernel from repository and nw-fermi was compiled successfully on this kernel. But module does not compiled automatically. ** Attachment added: nw-fermi-on-linux-2.6.36-1 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/379313/+attachment/1709640/+files/nw-fermi-on-linux-2.6.36-1 -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Try: sudo /usr/sbin/nwfermi_daemon It will not demonize the process, you will see the output but i think there will be no output if device/driver is not working. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
I think it is supported.
webn...@webnull-desktop:/$ cat /usr/src/nwfermi-0.4.2/nw-fermi.c |grep 0064
{ USB_DEVICE(0x1926, 0x0064) }
Your device is on supported list i think - /* table of devices that
work with this driver */.
--
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.
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Try: sudo modprobe nw-fermi sudo /usr/sbin/nwfermi_daemon /daemon -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Thanks for the quick response. The modprobe command didn't do anything, since lsmod shows that the nwfermi module is already loaded. I don't understand what the daemon line does, but when I typed it in, it responded with daemonizing process! Afterward, I didn't see any change in behavior from evtest. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Hi everyone, I'm trying to use a Dell SX2210Tb touch monitor on Maverick 64-bit using nwfermi-0.4.2. The touch device reports as 1926:0064, and is listed as /dev/input/event5. I've followed the steps from post #31, but I'm not seeing any activity from evtest. Is this device supported by nwfermi? Thanks, Dave -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
In ArchLinux i had the same problem, udev really not worked. I executed /usr/sbin/ConsoleDriver but there was no reaction too, and nw-fermi was loaded. I dont know what happened but i changed OS from Arch Linux to Ubuntu because of this situation with udev kernel. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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-: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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Maybe you need /usr/sbin/ConsoleDriver to run? I think your udev is not loading ConsoleDriver. Just try it. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
djp, thanks - im really waiting for this feature, i recently bought the LCD with touchscreen and i never used multi-touch on it.. Can you make a PPA(Package repository for Ubuntu on launchpad) for nw- fermi? I will look into it, I havent made a PPA before but in the long term I guess it will help ease distribution -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Maybe you need /usr/sbin/ConsoleDriver to run? I think your udev is not loading ConsoleDriver. Just try it. WebNull, could be correct (check ps -e | grep ConsoleDriver). There should be a udev rules file (/etc/udev/rules/40-nw-fermi.rules) which starts ConsoleDriver, you could try changing the udev logging (udevcontrol log_priority) to see if it is executing properly when nw-fermi probes. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
A quick update to fix driver compilation on newer kernels ** Attachment added: nwfermi-0.4.2_i386.deb https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/379313/+attachment/1691815/+files/nwfermi-0.4.2_i386.deb -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
** Attachment added: nwfermi-0.4.2_amd64.deb https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/379313/+attachment/1691816/+files/nwfermi-0.4.2_amd64.deb -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
djp, thanks - im really waiting for this feature, i recently bought the LCD with touchscreen and i never used multi-touch on it.. Can you make a PPA(Package repository for Ubuntu on launchpad) for nw- fermi? To help you with distribution of your driver i can make repository with nw-fermi on Gentoo and Arch Linux. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
On Sat, Oct 9, 2010 at 9:56 PM, WebNuLL babciast...@gmail.com wrote: Can i use multi-touch function using this driver? nwfermi does not support linux multi-touch yet, but I hope to include this in a future release -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
** Tags added: maverick -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Can i use multi-touch function using this driver? Bus 001 Device 005: ID 1926:0086 NextWindow 1950 HID Touchscreen Single touch works with nw-fermi-0.2, but now im installing nw-fermi-0.4 and i will test it after X restart. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
I found some patches for evdev, but i dont know how to test these patches. http://lists.x.org/archives/xorg-devel/2010-June/009471.html The patches brings multitouch functions to evdev, i checked my evdev from Maverick and i dont have these patches applied. So there is a question; does nw-fermi supports multitouch? If it supports i think there is possibility to run multitouch by patching evdev to support more than one pointer. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
I also tested the driver on Gentoo, but i cannot calibrate my screen at now, if i will find some free time i will try again with it. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Here is the deb ready for Maverick both i386 and amd64 ** Attachment added: nwfermi-0.4-1_all.deb https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/379313/+attachment/1678506/+files/nwfermi-0.4-1_all.deb -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Hi guys, thanks for all the feedback so far it has been really useful. Here is a new release (nwfermi 0.4): - support for more devices (3XXX model touchscreens) - support for api changes in Linux 2.6.34 (thanks again for the feedback here on this) - 64 bit package - support for multiple devices Cheers to all, Dan ** Attachment added: nwfermi-0.4_i386.deb https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/379313/+attachment/1676026/+files/nwfermi-0.4_i386.deb -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
** Attachment added: nwfermi-0.4_amd64.deb https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/379313/+attachment/1676027/+files/nwfermi-0.4_amd64.deb -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
djdvant: Thanks, driver compiles fine on maverick 64b. Also devices are created well and X identifies it. But, when trying to 'evtest' the device, i got no response. In xorg.conf, I got only conf for nvidia. Are there some aditional steps needed? -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Hi Everyone, I have updated the package to run on Maverick. The sed patches above have already been run. ** Attachment added: nwfermi-0.2-1_all.deb https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/379313/+attachment/1605825/+files/nwfermi-0.2-1_all.deb -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
By doing a dpkg -i --force-architecture which was the lazy way of doing it I should have done it properly by usingar to extract the deb, then extract the data.tar.gz then compile the kernel module like in post #71. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
However, unless you're running a very new kernel you can probably omit the sed lines if you're just compiling for 64-bit. This should work as a quick step-by-step: wget https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/379313/+attachment/1455604/+files/nwfermi-0.2_i386.deb ar x nwfermi-0.2_i386.deb tar -zxmvf data.tar.gz cd usr/src/nwfermi-0.2 # Only uncomment if running Maverick or you get USB-related compiler errors #sed -i 's/usb_buffer_alloc/usb_alloc_coherent/g' nw-fermi.c #sed -i 's/usb_buffer_free/usb_free_coherent/g' nw-fermi.c make sudo cp nw-fermi.ko /lib/modules/$(uname -r)/updates/dkms sudo insmod /lib/modules/$(uname -r)/updates/dkms sudo depmod -a -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
djdvant, i have the same computer than yours. Can you explain me the way you make your touchsmart work? I have a 64 bits 10.04 ubuntu installation. Thank in advance, and sorry about my english. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
In order to run on the Maverick Beta kernel, you'll need to manually compile the module. First extract the .deb contents somewhere (I use /tmp/nwfermi as an example) and run the following: cd /tmp/nwfermi/usr/src/nwfermi-0.2 sed -i 's/usb_buffer_alloc/usb_alloc_coherent/g' nw-fermi.c sed -i 's/usb_buffer_free/usb_free_coherent/g' nw-fermi.c make sudo cp nw-fermi.ko /lib/modules/$(uname -r)/updates/dkms sudo insmod /lib/modules/$(uname -r)/updates/dkms sudo depmod -a Sadly, no uTouch support seems to be available. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
I have installed NW Fermi Touchscreen Driver 0.2, compiled nw-fermi for 64 bit system. All is working fine. I would like to ask: ConsoleDriver is 32 bit?!! A strange thing is that, at boot, after ..populating dev... I have three messages similar to this (I had to write down with my pen): Translib[1252]: !WARNING! _Process_Stream missed packet /home/daniel/projects/1950_driver/Driver/Translib/Parser.c; LINE 94; etc. daniel??? -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
I conform that it works on HP 600-1050 with 10.04 perfectly! Thanx Daniel! -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
works perfectly on my HP Touchsmart 300 with Lucid 32bit ! Thank you very much -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Thank you very much, it works perfectly on my HP Touchsmart 300 with Lucid 64bit. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Thanks @djp, this new release works great on my HP Touchsmart 600-1005xt! Any hope that 1) it will be possible to create a 64-bit version and 2) it can be included in the Ubuntu release? Barring 2, I'd love to see it in a custom repository somewhere so I can make sure to nab any updates. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
I have attached a new release of nwfermi (0.2). updates include: - new device ids - fixed bug in usb completion routine (was using GFP_KERNEL instead of GFP_ATOMIC) - /rawmouse command line parameter to ConsoleDriver daemon to disable mouse filtering (right click, drag thresholds etc) - support for new kfifo api in post 2..6.33 kernels Hopefully this should result in a more stable driver for all users of nwfermi. Cheers Daniel ** Attachment added: NW Fermi Touchscreen Driver 0.2 http://launchpadlibrarian.net/51962826/nwfermi-0.2_i386.deb -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Some early open source work to support multi-touch in the evdev input driver is described at http://www.phoronix.com/scan.php?page=news_itempx=ODMxMw -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
I did a clean install of Lucid and I get the same messages as Jamie, showing that everything is ok, but I get the messages as above on #59 So, should I start an new bug report for that or may we keep this one ?? -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
[This is an automatic notification.] Hi Jamie, This bug was reported against an earlier version of Ubuntu, can you test if it still occurs on Lucid? Please note we also provide technical support for older versions of Ubuntu, but not in the bug tracker. Instead, to raise the issue through normal support channels, please see: http://www.ubuntu.com/support If you are the original reporter and can still reproduce the issue on Lucid, please run the following command to refresh the report: apport-collect 379313 If you are not the original reporter, please file a new bug report, so we can work with you as the original reporter instead (you can reference bug 379313 in your report if you think it may be related): ubuntu-bug xorg If by chance you can no longer reproduce the issue on Lucid or if you feel it is no longer relevant, please mark the bug report 'Fix Released' or 'Invalid' as appropriate, at the following URL: https://bugs.launchpad.net/ubuntu/+bug/379313 ** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: Incomplete = New ** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: New = Incomplete ** Tags added: needs-retested-on-lucid-by-june -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
hey all, just did a fresh install of lucid (32bit) and touch screen is working out of the box. According to above message i should probably close it but not sure if i should as others are still having problems. relevant dmesg: [2.498018] input: NextWindow Touchscreen as /devices/pci:00/:00:1d.0/usb5/5-1/5-1:1.0/input/input3 [2.498118] input: NextWindow Touchscreen as /devices/pci:00/:00:1d.0/usb5/5-1/5-1:1.0/input/input4 [2.498170] generic-usb 0003:1926:0003.0001: input,hidraw0: USB HID v1.00 Keyboard [NextWindow Touchscreen] on usb-:00:1d.0-1/input0 [2.501024] generic-usb 0003:1926:0003.0002: hiddev96,hidraw1: USB HID v1.00 Device [NextWindow Touchscreen] on usb-:00:1d.0-1/input1 [2.509986] input: NextWindow Touchscreen as /devices/pci:00/:00:1d.0/usb5/5-1/5-1:1.2/input/input5 [2.510107] input: NextWindow Touchscreen as /devices/pci:00/:00:1d.0/usb5/5-1/5-1:1.2/input/input6 [2.510751] generic-usb 0003:1926:0003.0003: input,hiddev97,hidraw2: USB HID v1.00 Mouse [NextWindow Touchscreen] on usb-:00:1d.0-1/input2 relevant Xorg.log: (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/event3) (**) NextWindow Touchscreen: Applying InputClass evdev keyboard catchall (**) NextWindow Touchscreen: always reports core events (**) NextWindow Touchscreen: Device: /dev/input/event3 (II) NextWindow Touchscreen: Found keys (II) NextWindow Touchscreen: Configuring as keyboard (II) XINPUT: Adding extended input device NextWindow Touchscreen (type: KEYBOARD) (**) Option xkb_rules evdev (**) Option xkb_model pc105 (**) Option xkb_layout us (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/event4) (II) No input driver/identifier specified (ignoring) (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/event5) (**) NextWindow Touchscreen: Applying InputClass evdev pointer catchall (**) NextWindow Touchscreen: always reports core events (**) NextWindow Touchscreen: Device: /dev/input/event5 (II) NextWindow Touchscreen: Found 3 mouse buttons (II) NextWindow Touchscreen: Found scroll wheel(s) (II) NextWindow Touchscreen: Found relative axes (II) NextWindow Touchscreen: Found absolute axes (II) NextWindow Touchscreen: Found x and y absolute axes (II) NextWindow Touchscreen: Configuring as mouse (**) NextWindow Touchscreen: YAxisMapping: buttons 4 and 5 (**) NextWindow Touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (II) XINPUT: Adding extended input device NextWindow Touchscreen (type: MOUSE) (EE) NextWindow Touchscreen: failed to initialize for relative axes. (II) NextWindow Touchscreen: initialized for absolute axes. (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/js0) (II) No input driver/identifier specified (ignoring) (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/mouse1) (II) No input driver/identifier specified (ignoring) (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/event6) (**) NextWindow Touchscreen: Applying InputClass evdev tablet catchall (**) NextWindow Touchscreen: always reports core events (**) NextWindow Touchscreen: Device: /dev/input/event6 (II) NextWindow Touchscreen: Found absolute axes (II) NextWindow Touchscreen: Found x and y absolute axes (II) NextWindow Touchscreen: Found absolute tablet. (II) NextWindow Touchscreen: Configuring as tablet (**) NextWindow Touchscreen: YAxisMapping: buttons 4 and 5 (**) NextWindow Touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (II) XINPUT: Adding extended input device NextWindow Touchscreen (type: TABLET) (II) NextWindow Touchscreen: initialized for absolute axes. (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/mouse2) (II) No input driver/identifier specified (ignoring) -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
** Attachment added: lshal.txt http://launchpadlibrarian.net/48240333/lshal.txt -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
I couldn't figure anything out and got disappointed that I couldn't use the functionality of the machine, so I put win7 back on. Tried ubuntu as guest in virtualbox, and it all works great. OK, so that's not the best answer for here, so I'll keep an ubuntu partition and keep trying. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Don't give up... It seems that the driver blocks the whole usb controller. The bad thing is that no input is possible when the driver is active, so it is not possible to find out why... I think that the input devices are in conflict somehow... I didn't change my xorg.conf as after the first reboot it worked just fine, but for a couple of minutes before the input was lost... My question is: if I install nw-fermi.deb will evtest show on what input device is connected to the touchscreen or a reboot is defently needed?? -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
OK, I did a more extended search. I installed nw-fermi.deb and rebooted into recovery mode to check which input event is assigned to the touchscreen using evtest. The results are: Nor eth or wlan managed to start and the a usb stick I plugged did not even get power!!! Seconds after getting into prompt the screen filled up with BUG: scheduling while atomic: swapper/0/0x10010 sometimes (the time was not the same) I got BUG: scheduling while atomic: rsyslogd/917/0x1001 or BUG: scheduling while atomic: rsyslogd/922/0x1001 and the system freezed, propably a kernel panic. I tried to get a dmesg and the results started after 100' and the same message was repeated: [ 100.656521] [ 100.656521] Pid: 0, comm: swapper Tainted: P C (2.6.32-21-generic-pae #32-Ubuntu) VN421AA-ABU 600-1050uk [ 100.656521] EIP: 0060:[c03a799b] EFLAGS: 0282 CPU: 0 [ 100.656521] EIP is at acpi_idle_enter_simple+0x117/0x148 [ 100.656521] EAX: c0882b4c EBX: 05c6 ECX: 0017 EDX: 02d82000 [ 100.656521] ESI: EDI: f761944c EBP: c078df48 ESP: c078df28 [ 100.656521] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 100.656521] CR0: 8005003b CR2: 097ee810 CR3: 32a88000 CR4: 000406f0 [ 100.656521] DR0: DR1: DR2: DR3: [ 100.656521] DR6: 0ff0 DR7: 0400 [ 100.656521] Call Trace: [ 100.656521] [c03a76b1] acpi_idle_enter_bm+0xc7/0x29a [ 100.656521] [c04c359a] cpuidle_idle_call+0x7a/0x100 [ 100.656521] [c0108634] cpu_idle+0x94/0xd0 [ 100.656521] [c059dbf8] rest_init+0x58/0x60 [ 100.656521] [c07e08fd] start_kernel+0x351/0x357 [ 100.656521] [c07e03d8] ? unknown_bootoption+0x0/0x19e [ 100.656521] [c07e00bb] i386_start_kernel+0xaa/0xb1 [ 101.441533] BUG: scheduling while atomic: swapper/0/0x1001 [ 101.445522] Modules linked in: snd_hda_codec_realtek uvcvideo nw_fermi fbcon tileblit font bitblit softcursor joydev btusb bluetooth videodev v4l1_compat lirc_mceusb lirc_dev video output snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device psmouse serio_raw snd usblp nvidia(P) vga16fb vgastate rt3090sta(C) soundcore snd_page_alloc i2c_nforce2 agpgart lp parport usbhid hid usb_storage ahci forcedeth Finally, I managed the a evtest and found out that the touchscreen is assigned to event5. So I'll try creating a new xorg.conf to force touchscreen connect to event5. The above patch is only for 2.6.33.2 kernel or not? I may try newer kernels to see if this bug insists... -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
I confirm the same issue with robireland on an 600-1050... It seems that almost none driver is working, as the network (wired and wireless) is down also! -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
I forgot: It's a new installation with 10.04 and no calibration was needed... -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Does not work well at all on a 64 bit kernel: Apr 12 22:05:59 kim-touch kernel: [ .966242] BUG: scheduling while atomic: swapper/0/0x1001 Apr 12 22:05:59 kim-touch kernel: [ .966250] Modules linked in: nw_fermi nfs lockd nfs_acl auth_rpcgss sunrpc binfmt_misc ppdev snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi fbcon tileblit snd_seq_midi_event font bitblit softcursor edac_core snd_seq fglrx(P) vga16fb vgastate pl2303 video lp edac_mce_amd usbserial shpchp output snd_timer rt3090sta (C) joydev i2c_piix4 snd_seq_device parport psmouse serio_raw uvcvideo videodev snd soundcore snd_page_alloc v4l1_compat usbhid v4l2_compat_ioctl32 hid lirc_mceusb lirc_dev usb_storage r8169 mii ahci Apr 12 22:05:59 kim-touch kernel: [ .966338] CPU 0: Apr 12 22:05:59 kim-touch kernel: [ .966342] Modules linked in: nw_fermi nfs lockd nfs_acl auth_rpcgss sunrpc binfmt_misc ppdev snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi fbcon tileblit snd_seq_midi_event font bitblit softcursor edac_core snd_seq fglrx(P) vga16fb vgastate pl2303 video lp edac_mce_amd usbserial shpchp output snd_timer rt3090sta (C) joydev i2c_piix4 snd_seq_device parport psmouse serio_raw uvcvideo videodev snd soundcore snd_page_alloc v4l1_compat usbhid v4l2_compat_ioctl32 hid lirc_mceusb lirc_dev usb_storage r8169 mii ahci Apr 12 22:05:59 kim-touch kernel: [ .966422] Pid: 0, comm: swapper Tainted: P C 2.6.32-20-generic #29-Ubuntu NY758AA-ABG 300-1040a Apr 12 22:05:59 kim-touch kernel: [ .966427] RIP: 0010:[81038acb] [81038acb] native_safe_halt+0xb/0x10 Apr 12 22:05:59 kim-touch kernel: [ .966445] RSP: 0018:8178bea8 EFLAGS: 0246 Apr 12 22:05:59 kim-touch kernel: [ .966449] RAX: RBX: 8178bea8 RCX: Apr 12 22:05:59 kim-touch kernel: [ .966455] RDX: c9000108 RSI: 0086 RDI: 0086 Apr 12 22:05:59 kim-touch kernel: [ .966460] RBP: 81013b0e R08: 817b8740 R09: 0001 Apr 12 22:05:59 kim-touch kernel: [ .966465] R10: R11: R12: 810934c0 Apr 12 22:05:59 kim-touch kernel: [ .966470] R13: 8178be48 R14: R15: Apr 12 22:05:59 kim-touch kernel: [ .966476] FS: 7faac4d31710() GS:88002820() knlGS:f6c1db70 Apr 12 22:05:59 kim-touch kernel: [ .966482] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b Apr 12 22:05:59 kim-touch kernel: [ .966487] CR2: 0237f5ec CR3: 0001003bc000 CR4: 06f0 Apr 12 22:05:59 kim-touch kernel: [ .966492] DR0: DR1: DR2: Apr 12 22:05:59 kim-touch kernel: [ .966497] DR3: DR6: 0ff0 DR7: 0400 Apr 12 22:05:59 kim-touch kernel: [ .966502] Call Trace: Apr 12 22:05:59 kim-touch kernel: [ .966513] [81092c5c] ? clockevents_notify+0x4c/0x160 Apr 12 22:05:59 kim-touch kernel: [ .966523] [8101b6cd] ? default_idle+0x3d/0x90 Apr 12 22:05:59 kim-touch kernel: [ .966531] [8101b7ba] ? c1e_idle+0x9a/0x120 Apr 12 22:05:59 kim-touch kernel: [ .966539] [81011e73] ? cpu_idle+0xb3/0x110 Apr 12 22:05:59 kim-touch kernel: [ .966548] [8152c0db] ? rest_init+0x6b/0x80 Apr 12 22:05:59 kim-touch kernel: [ .966556] [81849dcc] ? start_kernel+0x368/0x371 Apr 12 22:05:59 kim-touch kernel: [ .966566] [8184933a] ? x86_64_start_reservations+0x125/0x129 Apr 12 22:05:59 kim-touch kernel: [ .966575] [81849438] ? x86_64_start_kernel+0xfa/0x109 -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
I ported nw-fermi to 2.6.33.2 in the attached patch; just a few kfifo API adjustments, and I put the 007a device by default. For those using nw-fermi, did you calibrate the screen? Did you modify your xorg.conf? ** Patch added: Patch for nw-fermi on 2.6.33 http://launchpadlibrarian.net/44150544/nw-fermi-2.6.33.patch -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
No, I didn't need to calibrate the screen or modify xorg.conf, it worked perfectly after the steps on #31. -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
** Tags added: patch -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
For the time that it does work, it works great. What I have found is that when I reboot, it works without crashing on the login screen. It crashes when I login and then touch the display. If I logout, it will then crash on the next login screen when I touch the display. does anyone know how I can find out what devices I might be able to disable to find out whether there is a clash? -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
My last comment is incorrect. It does stop working on the login screen, it just takes a lot longer for that to happen. I've just found out that ubuntu doesn't crash but continues to work away. The power button works, but plugging in any usb device doesn't . -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
Sure, I'll attach some outputs. I'm still a noob and trying to get my head around this stuff, so I haven't made much sense of it. It's tantalisingly great while it works. Wobbly windows is perfect for touch screen. ** Attachment added: Crash Report http://launchpadlibrarian.net/44029764/crash%20report.txt -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
** Attachment added: hwinfo http://launchpadlibrarian.net/44029838/hwinfo.txt -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
** Attachment added: dmseg http://launchpadlibrarian.net/44029799/dmesg.txt -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
** Attachment added: lsmod http://launchpadlibrarian.net/44029859/lsmod.txt -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
thanks again ** Attachment added: lsusb http://launchpadlibrarian.net/44029916/lsusb.txt -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch)
I'm not sure if that crash report was the correct one. I tried it again and a couple more appeared that seem different. ** Attachment added: crash report 2 http://launchpadlibrarian.net/44031478/crash%20report%202.txt -- 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. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
