@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
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:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/379313
Title:
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
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
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/379313
Title:
Handling NextWindow Touchscreen
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/379313
Title:
Handling NextWindow Touchscreen
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
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/379313
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
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
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
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
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
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
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
@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 @
** 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
Bugs, which is subscribed to Ubuntu.
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/379313
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:
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
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
@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
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
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
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
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
Bugs, which is subscribed to Ubuntu.
--
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)
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
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
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
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
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
** 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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 ? :)
--
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
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
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
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
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
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)
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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
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
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
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
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
Bugs, which is subscribed to
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
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
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)
** 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
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
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)
** 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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)
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
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
Bugs,
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)
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
** 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
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)
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
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)
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
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
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
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):
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
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.
--
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)
-
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
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)
[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
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
** 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
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.
--
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
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
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
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
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
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
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
Bugs, which is subscribed to
** 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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
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
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
** 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
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
Bugs, which is subscribed to Ubuntu.
--
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)
1 - 100 of 144 matches
Mail list logo
