[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)
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)
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)
I've just installed 9.10 on the new HP Touchsmart 600-1050, facing the same problem, though the touchscreen is pointed as 1926:0006 on bus 003 device 004 (usb). Also no input is connected to the device and no device is created. I also tried newer kernel (2.6.32.2) but with no success... ** Attachment added: outputs.tar.gz http://launchpadlibrarian.net/37343712/outputs.tar.gz -- 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
