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/0x100100000 sometimes (the time was not the same) I got BUG: scheduling while atomic: rsyslogd/917/0x10010000 or BUG: scheduling while atomic: rsyslogd/922/0x10010000 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: 00000282 CPU: 0 [ 100.656521] EIP is at acpi_idle_enter_simple+0x117/0x148 [ 100.656521] EAX: c0882b4c EBX: 000005c6 ECX: 00000017 EDX: 02d82000 [ 100.656521] ESI: 00000000 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: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000 [ 100.656521] DR6: ffff0ff0 DR7: 00000400 [ 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/0x10010000 [ 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
