Launchpad has imported 76 comments from the remote bug at https://bugzilla.novell.com/show_bug.cgi?id=404881.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2008-06-29T12:48:08+00:00 pkunjapur wrote: I installed openSUSE 11 on a Dell XPS M1530 laptop. It has Intel Core 2 Duo CPU T5750 @ 2.00 GHz, 3 GB Dual channel DDR2 RAM, 256 MB NVIDIA GeForce 8600M GT video card and 250 GB SATA Hard Disk. It came with Windows Vista Home Premium preinstalled. There's no way you can buy this laptop without having Windows Vista preinstalled. It had two partitions - C drive with Vista @ 110 GB and D drive with recovery at 10 GB. There was remaining unallocated space. I tried to dual-boot Vista with openSUSE 11 installed in the unallocated space but Yast said "cannot shrink the partitions due to inconsistent filesystems." So I formatted the hard disk clean with Gparted. Then allocated 30 GB for root and 6 GB for swap and installed the complete openSUSE 11 with all options on the DVD to the system. The complete installation took 45 minutes. My problem is as soon as I move the cursor through the touchpad in any desktop environment GNOME, KDE 3, KDE 4 or Xfce, the cursor automatically moves randomly in all directions and adds extra panels, opens different applications and stops. If I move the cursor again it again goes on displaying the same erratic behaviour. Then I killed the X server in all desktop environments by pressing CTRL, ALT, Backspace twice and rebooted. I went to the failsafe mode of openSUSE from Grub and booted in all the desktop environments and closed all those panels and applications. In failsafe mode, the cursor behaves normally like in any other laptop. But when I go back and boot the main openSUSE 11 kernel and into any of the desktop environments, the cursor again starts displaying that erratic behaviour. So what should I do now to stop this erratic behaviour of the cursor? This problem is not specific to openSUSE 11. The cursor displays the same erratic behaviour in Knoppix 5, NimbleX 2007, Slax server edition also. Interestingly when I run the openSUSE 10.3 Live DVD in Live mode in either GNOME or KDE 3, the cursor behaves normally. I didn't install openSUSE 10.3 since I wanted to try the new openSUSE 11. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/4 ------------------------------------------------------------------------ On 2008-06-29T12:53:44+00:00 pkunjapur wrote: Due to such erratic behaviour of the cursor I cannot use openSUSE 11.0 at all on my laptop. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/5 ------------------------------------------------------------------------ On 2008-06-30T19:38:30+00:00 Sreeves wrote: Start with this against kernel as it works in failsafe mode. Also moving to critical as you can't really block a shipped product. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/6 ------------------------------------------------------------------------ On 2008-06-30T20:14:08+00:00 Sndirsch-u wrote: So it works with X11 configuration from installation. Question is, do you simply don't see the cursor or does your mouse create events like mad. Please attach /etc/X11/xorg.conf and /var/log/Xorg.0.log from a non-failsafe run. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/7 ------------------------------------------------------------------------ On 2008-07-01T13:08:05+00:00 pkunjapur wrote: I can see the cursor. But my mouse creates events like mad. I am new to Linux. so kindly please tell me how to attach /etc/X11/xorg.conf and /var/log/Xorg.0.log from a non-failsafe run. Please provide the detailed steps for those configuration and log files. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/8 ------------------------------------------------------------------------ On 2008-07-01T13:31:30+00:00 Sndirsch-u wrote: First boot into normal mode, then reboot into failsafe mode in runlevel 3 (specify "3" on the boot command line), copy both files to a safe location. Reboot into failsafe mode and attach the files you copied before. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/9 ------------------------------------------------------------------------ On 2008-07-01T14:59:06+00:00 pkunjapur wrote: "First boot into normal mode, then reboot into failsafe mode in runlevel 3 (specify "3" on the boot command line), copy both files to a safe location. Reboot into failsafe mode and attach the files you copied before." I rebooted in failsafe mode in runlevel 3, then created a new directory "mkdir praveen" in "/root" directory. Then did "cd /etc/" , then "cd /X11", then did "cp xorg.conf /root/praveen" Again I did "cd /var", then "cd log" then "cp Xorg.0.log /root/praveen". Then i rebooted into failsafe mode. You asked to "attach the files you copied before". Attach from where to where? Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/10 ------------------------------------------------------------------------ On 2008-07-01T15:16:01+00:00 Sndirsch-u wrote: Attach from your system to Bugzilla. What else? Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/11 ------------------------------------------------------------------------ On 2008-07-02T08:55:21+00:00 pkunjapur wrote: Created attachment 225495 File 1 Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/12 ------------------------------------------------------------------------ On 2008-07-02T08:57:03+00:00 pkunjapur wrote: Created attachment 225497 xorg.conf file. (the previous one i.e "file 1" is Xorg.0.log) Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/13 ------------------------------------------------------------------------ On 2008-07-02T08:58:07+00:00 pkunjapur wrote: So there are my files in comment 8 and 9 :) Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/14 ------------------------------------------------------------------------ On 2008-07-02T09:35:39+00:00 Sndirsch-u wrote: > Current Operating System: Linux linux-gdzm 2.6.25.5-1.1-pae #1 SMP [...] [...] (EE) NV(0): vm86() syscall generated signal 11. (II) NV(0): EAX=0x0000004f, EBX=0x00008114, ECX=0x00000000, EDX=0x00000000 (II) NV(0): ESP=0x00001000, EBP=0x00000000, ESI=0x00000000, EDI=0x00000000 (II) NV(0): CS=0x0000, SS=0x0100, DS=0x0040, ES=0x0000, FS=0x0000, GS=0x0000 (II) NV(0): EIP=0x00000600, EFLAGS=0x00033202 (II) NV(0): code at 0x00000600: f4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 This sounds weird. I'm not sure if it's the culprit here. Please try fbdev driver instead by booting into failsafe mode and let me know if this fixes the issue. Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/15 ------------------------------------------------------------------------ On 2008-07-02T11:36:16+00:00 pkunjapur wrote: What are the detailed steps to try the fbdev driver in failsafe mode? Do I need to enter the parameter "fbdev" at boot prompt of failsafe mode before booting into failsafe mode? Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/16 ------------------------------------------------------------------------ On 2008-07-02T11:49:59+00:00 Sndirsch-u wrote: Simply select failsafe mode. Then a fbdev driver based X11 configuration will be used instead of a nv driver based one. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/17 ------------------------------------------------------------------------ On 2008-07-02T13:57:41+00:00 pkunjapur wrote: I booted into failsafe mode. It fixes the issue. In all desktop environments i.e GNOME, KDE 3, KDE4, Xfce the cursor behaves normally like in other laptops. Though in failsafe mode instead of selecting 1280*800 resolution, it detects my screen resolution as 800*600 in all desktop environments. I filed bug for these resolution issues (Bug id no. 405680 and bug id no. - 405685). Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/18 ------------------------------------------------------------------------ On 2008-07-02T14:34:18+00:00 Sndirsch-u wrote: failsafe runs in the same mode as installation. It's a failsafe mode. No need to file bugreports for this. Anyway, could you install kernel- default and try in normal mode with this "default" kernel? vm86 looks like a kernel issue, which might happen only with pae kernel. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/19 ------------------------------------------------------------------------ On 2008-07-04T18:50:11+00:00 pkunjapur wrote: I installed kernel-default and booted in normal mode of "kernel- default." It doesn't fix the problem. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/20 ------------------------------------------------------------------------ On 2008-07-04T19:24:23+00:00 Sndirsch-u wrote: Nevertheless please attach /var/log/Xorg.0.log once more. This time when kernel-default is running. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/21 ------------------------------------------------------------------------ On 2008-07-05T13:19:23+00:00 pkunjapur wrote: Created attachment 226109 kernel-default's /var/log/Xorg.0.log file Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/22 ------------------------------------------------------------------------ On 2008-07-05T19:48:51+00:00 Sndirsch-u wrote: (In reply to comment #16 from Praveen Kunjapur) > I installed kernel-default and booted in normal mode of "kernel-default." It > doesn't fix the problem. But this time the vm86() syscall does not generate a signal 11. Compare attachment of comment #8 and comment #18. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver-synaptics/+bug/93897/comments/23 ------------------------------------------------------------------------ On 2008-07-06T05:32:23+00:00 pkunjapur wrote: I am sorry. I don't have that deep technical knowledge of Linux. So unfortunately, I cannot compare attachments of comment 8 and comment 18. So please tell me what do I do now? Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/24 ------------------------------------------------------------------------ On 2008-07-06T06:07:19+00:00 Sndirsch-u wrote: Create a fbdev configuration for your favorite resolution. Run 'sax2 -r -m 0=fbdev". Reboot (to activate this kernel framebuffer mode). Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/25 ------------------------------------------------------------------------ On 2008-07-06T10:54:17+00:00 pkunjapur wrote: I ran 'sax2 -r -m 0=fbdev" in failsafe mode of both pae-kernel and kernel-default. I chose the screen resolution of 1280*800 and 24 bit colors. Then tested the new configuration and after testing saved that configuration. Then I rebooted into failsafe mode of both kernels and also rebooted in the normal mode of both kernels. Then also it doesn't fix the problem. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver-synaptics/+bug/93897/comments/26 ------------------------------------------------------------------------ On 2008-07-06T11:08:44+00:00 Sndirsch-u wrote: Could you attach the new /etc/X11/xorg.conf and /etc/X11/xorg.conf.install? Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/27 ------------------------------------------------------------------------ On 2008-07-06T11:52:36+00:00 pkunjapur wrote: Created attachment 226140 kernel-default's xorg.conf file Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/28 ------------------------------------------------------------------------ On 2008-07-06T11:53:42+00:00 pkunjapur wrote: Created attachment 226141 kernel-default's xorg.conf.install file Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/29 ------------------------------------------------------------------------ On 2008-07-06T12:33:44+00:00 Sndirsch-u wrote: In xorg.conf replace InputDevice "Mouse[1]" "CorePointer" InputDevice "Mouse[5]" "SendCoreEvents" with InputDevice "Mouse[5]" "CorePointer" If this helps, the synaptics driver is the culprit here. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/30 ------------------------------------------------------------------------ On 2008-07-06T12:55:18+00:00 pkunjapur wrote: In my xorg.file I can see the following. Section "InputDevice" Driver "synaptics" Identifier "Mouse[1]" Option "AccelFactor" "0.10" Option "BottomEdge" "300" Option "Buttons" "5" Option "CircScrollDelta" "0.1" Option "CircScrollTrigger" "2" Option "CircularScrolling" "1" Option "Device" "/dev/input/mice" Option "EdgeMotionMaxSpeed" "15" Option "EdgeMotionMinSpeed" "15" Option "Emulate3Buttons" "on" Option "EmulateMidButtonTime" "75" Option "FingerHigh" "40" Option "FingerLow" "30" Option "HorizScrollDelta" "30" Option "InputFashion" "Mouse" Option "LeftEdge" "100" Option "MaxSpeed" "0.90" Option "MaxTapMove" "100" Option "MinSpeed" "0.15" Option "Name" "ALPS;Touchpad" Option "Protocol" "auto-dev" Option "RightEdge" "1100" Option "SHMConfig" "on" Option "SendCoreEvents" "on" Option "TapButton1" "1" Option "TapButton2" "3" Option "TapButton3" "2" Option "TopEdge" "50" Option "UpDownScrolling" "1" Option "Vendor" "Sysp" Option "VertScrollDelta" "25" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" Driver "synaptics" Identifier "Mouse[3]" Option "AccelFactor" "0.10" Option "BottomEdge" "300" Option "Buttons" "5" Option "CircScrollDelta" "0.1" Option "CircScrollTrigger" "2" Option "CircularScrolling" "1" Option "Device" "/dev/input/mice" Option "EdgeMotionMaxSpeed" "15" Option "EdgeMotionMinSpeed" "15" Option "Emulate3Buttons" "on" Option "EmulateMidButtonTime" "75" Option "FingerHigh" "40" Option "FingerLow" "30" Option "HorizScrollDelta" "30" Option "InputFashion" "Mouse" Option "LeftEdge" "100" Option "MaxSpeed" "0.90" Option "MaxTapMove" "100" Option "MinSpeed" "0.15" Option "Name" "ALPS;Touchpad" Option "Protocol" "auto-dev" Option "RightEdge" "1100" Option "SHMConfig" "on" Option "SendCoreEvents" "on" Option "TapButton1" "1" Option "TapButton2" "3" Option "TapButton3" "2" Option "TopEdge" "50" Option "UpDownScrolling" "1" Option "Vendor" "Sysp" Option "VertScrollDelta" "25" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" Driver "mouse" Identifier "Mouse[5]" Option "Buttons" "5" Option "Device" "/dev/input/mice" Option "Name" "ImPS/2 Generic Wheel Mouse" Option "Protocol" "explorerps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection Could you please tell me where to edit the file in the above list? I can see "Input device" Mouse 1, but no "corepointer" in that section. As I was afraid i could damage my system, I didn't edit the file. One more thing - my laptop had Nvidia video card. Just before u asked me to replace "the mouse pointer", I downloaded and installed Nvidia drivers from opensuse.org to enable desktop effects. Could the installation of those nvidia drivers changed the xorg.conf file and that's why I cannot locate "Corepointer" in "Input Device Mouse [1]"? Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver-synaptics/+bug/93897/comments/31 ------------------------------------------------------------------------ On 2008-07-06T14:02:17+00:00 Sndirsch-u wrote: It's in ' Section "ServerLayout" '. The official openSUSE RPMs available from NVIDIA don't touch this section. BTW, it's a mouse/touchpad driver issue, so installing the NVIDIA driver won't help here. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/32 ------------------------------------------------------------------------ On 2008-07-06T14:29:20+00:00 pkunjapur wrote: Thanks for the Nvidia info. I deleted both these lines InputDevice "Mouse[1]" "CorePointer" InputDevice "Mouse[5]" "SendCoreEvents" and replaced the above two lines with this line InputDevice "Mouse[5]" "CorePointer" Still, it doesn't solve the problem yet. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/33 ------------------------------------------------------------------------ On 2008-07-06T15:47:42+00:00 Sndirsch-u wrote: That's weird. Remove also Option "Buttons" "5" Option "ZAxisMapping" "4 5" from Section "InputDevice" Driver "mouse" Identifier "Mouse[5]" Option "Buttons" "5" Option "Device" "/dev/input/mice" Option "Name" "ImPS/2 Generic Wheel Mouse" Option "Protocol" "explorerps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver-synaptics/+bug/93897/comments/34 ------------------------------------------------------------------------ On 2008-07-06T16:28:46+00:00 pkunjapur wrote: I removed Option "Buttons" "5" Option "ZAxisMapping" "4 5" from Section "InputDevice" Driver "mouse" Identifier "Mouse[5]" Option "Buttons" "5" Option "Device" "/dev/input/mice" Option "Name" "ImPS/2 Generic Wheel Mouse" Option "Protocol" "explorerps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection The problem is still present. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/35 ------------------------------------------------------------------------ On 2008-07-06T17:15:54+00:00 Sndirsch-u wrote: You restarted the Xserver after changing the config file, didn't you? Just to make sure ... Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/36 ------------------------------------------------------------------------ On 2008-07-06T17:58:10+00:00 pkunjapur wrote: I rebooted into normal mode of default-kernel and pae-kernel to see if the problem has been solved....of course...it didn't get solved...anyways, I will give you a detailed steps of the procedure from nowonwards... As I am reporting this comment to you, I installed vlc media player for openSUSE 11.0 (1-click install) from vlc web site. Hope it doesn't change xorg.conf file...the thing is I played video (mpeg and movie file) for the first time on openSUSE and I believe first time on Linux and am very happy for that coz it gives me confidence to show more people how easy it is to use openSUSE which comes free of cost rather than using illegal pirated OS... Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/37 ------------------------------------------------------------------------ On 2008-07-06T18:00:07+00:00 pkunjapur wrote: yes after changing config file I rebooted into normal mode of kernel- default and pae-kernel. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/38 ------------------------------------------------------------------------ On 2008-07-06T18:25:23+00:00 Sndirsch-u wrote: vlc doesn't change xorg.conf. I have no idea why your mouse/touchpad still doesn't work. You're now using the exact same mouse configuration as in failsafe mode. I need to give up at that point. Maybe it's really a kernel problem. I don't know. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/39 ------------------------------------------------------------------------ On 2008-07-06T18:52:56+00:00 pkunjapur wrote: I have openSUSE 10.3 live cd iso of both gnome and kde with me. When I installed openSuSE 10.3, it gave no such problems. Shall I attach the xorg.conf file of openSUSE 10.3 of my laptop so that you will have more idea as to where the problem really occurs? Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/40 ------------------------------------------------------------------------ On 2008-07-06T19:06:08+00:00 pkunjapur wrote: BTW, I first edited the configuration files (In xorg.conf replace InputDevice "Mouse[1]" "CorePointer" InputDevice "Mouse[5]" "SendCoreEvents" with InputDevice "Mouse[5]" "CorePointer") in failsafe mode of pae-kernel and then checked out the xorg.conf file on kernel-default. The kernel-default xorg.conf file displayed the "edited" parameters of pae-kernel. Then for the second time (Remove also Option "Buttons" "5" Option "ZAxisMapping" "4 5" from Section "InputDevice" Driver "mouse" Identifier "Mouse[5]" Option "Buttons" "5" Option "Device" "/dev/input/mice" Option "Name" "ImPS/2 Generic Wheel Mouse" Option "Protocol" "explorerps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" " EndSection) I edited the xorg.conf file in failsafe mode of kernel-default and rebooted into failsafe mode of pae-kernel. The pae-kernel xorg.conf file showed the "edited" xorg.conf parameters of kernel-default. Then I booted into normal mode of both the kernels and it didn't solve the problem. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/41 ------------------------------------------------------------------------ On 2008-07-23T16:30:07+00:00 Jeffm-9 wrote: "Failsafe" no longer applies just to kernel parameters. With 11.0, there is an "x11failsafe" option which isn't a kernel parameter. Can you try booting in normal mode but append x11failsafe to the command line? I've seen similar problems before, but it's usually been a result of having the mouse incorrectly configured, not a kernel problem. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/42 ------------------------------------------------------------------------ On 2008-08-07T05:59:31+00:00 pkunjapur wrote: I can boot in normal mode. But I can't use the GUI under any desktop environment because the cursor behaves very erratically. I booted in failsafe mode GNOME and opened it's terminal and typed "x11failsafe" and pressed enter. But it gives an error saying "no such command." I booted into normal mode and pressed ctrl+alt+f1 to revert to terminal mode and there also i entered "x11failsafe" but it gave me the same error again. Can you please give me detailed steps of how to append x11failsafe to the command line in normal mode? Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/43 ------------------------------------------------------------------------ On 2008-08-14T16:14:10+00:00 pkunjapur wrote: I got to notify to you that Damn Small Linux runs perfectly in my laptop since it uses Xvesa instead of XORG. So what does that mean? Only Puppy Linux, Damn Small Linux, Vector Linux 5.8 and openSUSE 10.3 (the promo DVD ones) run on my laptop. I did get that strange mouse behaviour once in openSUSE 10.3, but I killed the X server and rebooted. Then it became normal. Hope openSUSE 11.1 solves this problem. I can't alpha/beta test the openSUSE 11.1 iso due to very slow and unreliable internet connection. Anyways, thanks for being with me till now! Keep up the good work! Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/44 ------------------------------------------------------------------------ On 2008-09-11T12:30:33+00:00 carlos rogerio tonussi wrote: For me, the same problem has begun after updating to kernel 2.6.18 in opensuse 10.3. Until that time 10.3 was simply perfect to my Acer aspire 5710, thus I even glued an "designed for SUSE" label on it! But, unfortunately, I clicked yes for that update available message that morning.... After this, my touchpad came crazy. Even the failsafe mode was affected. I tried update the system to OS 11, but like the brother Praveen has told above, these touchpad disease came to stay. In another bug report, I found a suggestion to try the boot options i8042.reset and i8042.nomux. Like the drug haloperidol for schizofrenics, these single words got the touchpad crazy behavior under control. But, also as the drug, they did not cure the touchpad, which is still somewhat "lazy". BTW, it is not impossible to work without an external mouse, now. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/45 ------------------------------------------------------------------------ On 2008-10-07T18:13:33+00:00 Jpr-novell wrote: Moving to the kernel team to resurrect based on #41. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/49 ------------------------------------------------------------------------ On 2008-10-13T09:08:56+00:00 Sndirsch-u wrote: *** Bug 434334 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/51 ------------------------------------------------------------------------ On 2008-10-13T09:11:14+00:00 Sndirsch-u wrote: Praveen still stumbles across the same issue on openSUSE 11.1 Beta2. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/52 ------------------------------------------------------------------------ On 2008-10-13T14:33:06+00:00 Jkosina-d wrote: Is the problem mitigated on your system by using i8042.nomux i8042.reset kernel command line parameter? Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/53 ------------------------------------------------------------------------ On 2008-10-13T17:02:38+00:00 carlos rogerio tonussi wrote: By using these boot options the touchpad is usable. But there is still an annoying, random, delay to get the cursor moving after you start scratching the touchpad. In addition, 2-touch is not working as one click in the left button. Its behavior was perfect under kernel before 2.6.18 (or .12, I did forget). Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/54 ------------------------------------------------------------------------ On 2008-10-13T22:48:17+00:00 pkunjapur wrote: The problem is completely mitigated on my system when using i8042.nomux i8042.reset kernel command line parameter in openSUSE 11.1 KDE4 Beta 2 Live CD. So I could install the OS in my laptop. But after installation from the Live CD, on first boot the erratic mouse behavior did occur and only when I entered the i8042.nomux i8042.reset kernel command line parameter on second boot did the problem got completely mitigated. Unlike Carlos, I didn't experience any annoying, random, delay to get the cursor moving after you start scratching the touch pad. For me, the cursor actually worked as it would work normally in other pcs. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver-synaptics/+bug/93897/comments/55 ------------------------------------------------------------------------ On 2008-10-14T12:24:58+00:00 Jkosina-d wrote: (In reply to comment #47 from Praveen Kunjapur) > The problem is completely mitigated on my system when using > > i8042.nomux i8042.reset Thanks. Could you please test whether only i8042.nomux is sufficient? Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/56 ------------------------------------------------------------------------ On 2008-10-14T13:14:15+00:00 carlos rogerio tonussi wrote: I have already done this, and only nomux option seems to be enough. But another thing I have found is that I can get 2-touch as one mouse click, but the 2-touch interval must be really fast. Impossible to get it by one finger only. At least in my case....I need to quickly tambour the touchpad with several fingers to get an object selected. I know, it is ridiculous. I tried to modify the settings of the mouse behaviour in the KDE, but I did not succeed to get it better, and it was worse to the external mouse. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/57 ------------------------------------------------------------------------ On 2008-10-14T13:18:15+00:00 Jkosina-d wrote: (In reply to comment #49 from Carlos Tonussi) > I have already done this, and only nomux option seems to be enough. Could you please attach the output of 'dmidecode' command on the affected system? I can add your system to blacklist, so that kernel uses the 'nomux' option automatically on the system you have. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver-synaptics/+bug/93897/comments/58 ------------------------------------------------------------------------ On 2008-10-14T13:34:52+00:00 carlos rogerio tonussi wrote: Created attachment 245433 dmidecode acer aspire 5710-6139 Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/59 ------------------------------------------------------------------------ On 2008-10-14T13:37:20+00:00 carlos rogerio tonussi wrote: Created attachment 245434 dmidecode acer aspire 5710-6139 Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/60 ------------------------------------------------------------------------ On 2008-10-14T15:31:18+00:00 Jkosina-d wrote: Thanks Carlos, I have added the patch which makes the 'nomux' automatic on Acer Aspire 5710, so you shouldn't need to specify it explicitly on the command line with the future kernels. Praveen, if just 'i8042.nomux' also helps on your system, could you please also attach dmidecode output? Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/61 ------------------------------------------------------------------------ On 2008-10-14T16:06:33+00:00 pkunjapur wrote: I can see the output of 'dmidecode' on my terminal. What are the detailed steps/commands required to attach 'dmidecode' output to Bugzilla? Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/62 ------------------------------------------------------------------------ On 2008-10-14T21:25:18+00:00 pkunjapur wrote: Jiri, the kernel parameter, which is just 'i8042.nomux' does help my system. All I need now is detailed steps/commands as to how I should bring the output of 'dmidecode' on my terminal and attach that to bugzilla? I mean, the previous attachments which I submitted i.e of x.org conf file, the x.org conf file was in some directory so I could use the command 'cp' to copy the x.org conf file from it's native directory to the directory "Desktop' and then upload it to bugzilla. When I enter the command 'dmidecode' in the terminal, it gives output, but how am I supposed to save that output and copy it to the directory "Desktop' from where I can upload that output to bugzilla? Also, Jiri, since I believe we are coming close to fixing this bug within a day, could you please request the release team to release the Beta 3 after fixing this bug so that I can test Beta 3 with the updated kernel without worrying about this bug? Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/63 ------------------------------------------------------------------------ On 2008-10-15T15:19:08+00:00 pkunjapur wrote: Created attachment 245708 dmidecode Dell XPS M1530 Jiri, No Worries! Here's my 'dmidecode' attachment. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/64 ------------------------------------------------------------------------ On 2008-10-15T15:30:29+00:00 Jkosina-d wrote: Could please all of you who are seeing the problem try to reproduce with the kernels that can be obtained from http://labs.suse.cz/jikos/download/bug-404881/ they include the patch that could fix the interrupt storm on EC, causing this behavior, even without the 'nomux' parameter. Please let me know the results. Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/65 ------------------------------------------------------------------------ On 2008-10-15T15:31:39+00:00 Jkosina-d wrote: Created attachment 245713 ACPI: fix EC interrupt storm ACPI: fix EC interrupt storm patch Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/66 ------------------------------------------------------------------------ On 2008-10-16T13:39:05+00:00 carlos rogerio tonussi wrote: Well, I need to retract me here. I said above that only .nomux parameter was fine, but there is an exception. It is not enough when the system is started after its complete turn off. So, after a "cold start" of the machine, I need to restart it again to get the tochpad working fine. This do not occur when I use the i8042.reset option together. I tested it several times, and I never got the touchpad working fine at the first system start. Thus, at least for my system, the two parameters are needed. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/67 ------------------------------------------------------------------------ On 2008-10-16T14:35:13+00:00 pkunjapur wrote: (In reply to comment #57 from Jiri Kosina) > Could please all of you who are seeing the problem try to reproduce with the > kernels that can be obtained from > > http://labs.suse.cz/jikos/download/bug-404881/ > > they include the patch that could fix the interrupt storm on EC, causing this > behavior, even without the 'nomux' parameter. Please let me know the results. > Thanks. I installed all the three kernels - default, base, extra but each time it gives me error. 1) The error for default is: Package /var/tmp/kdecache-praveen/krun/5111.0.kernel- default-2.6.27-19.1.i586.rpm could not be installed. Details: Subprocess failed. Error. RPM failed: error: Failed dependencies: kernel-default-base = 2.6.27-19.1 is needed by kernel-default-2.6.27-19.1.i586 kernel-default = 2.6.27-12.1 is needed by (installed) kernel-default-extra-2.6.27-12.1.i586 2) The error for kernel base is: Package /tmp/kernel-default-base-2.6.27-19.1.i586-1.rpm could not be installed. Details: Subprocess failed. Error. RPM failed: error: Failed dependencies: kernel(default:drivers_usb_core) = 687d64d385f5fd68 is needed by (installed) wlan-ng-kmp-default-0.2.8_2.6.27_12.1-121.8.i586 kernel(default_usb_core) = 687d64d385f5fd68 is needed by (installed) ndiswrapper-kmp-default-1.53_2.6.27_12.1-1.12.i586 kernel(default:vmlinux) = 224dfc9ff54119b3 is needed by (installed) wlan-ng-kmp-default-0.2.8_2.6.27_12.1-121.8.i586 kernel(default:vmlinux) = 224dfc9ff54119b3 is needed by (installed) ndiswrapper-kmp-default-1.53_2.6.27_12.1-1.12.i586 kernel-default-base = 2.6.27-12.1 is needed by (installed) kernel-default-2.6.27.1.i586 3) The error for kernel extra is: Package /tmp/kernel-default-extra-2.6.27-19.1.i586.rpm could not be installed. Details: Subprocess failed. Error: RPM failed: error: Failed dependencies: kernel-default = 2.6.27-19.1 is needed by kernel-default-extra-2.6.27-19.1.i586 Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver-synaptics/+bug/93897/comments/68 ------------------------------------------------------------------------ On 2008-10-16T15:36:13+00:00 pkunjapur wrote: (In reply to comment #59 from Carlos Tonussi) > I said above that only .nomux parameter was fine, but there is an exception. > It > is not enough when the system is started after its complete turn off. > > So, after a "cold start" of the machine, I need to restart it again to get the > tochpad working fine. This do not occur when I use the i8042.reset option > together. > > I tested it several times, and I never got the touchpad working fine at the > first system start. If I enter .nomux with .reset parameter, it doesn't work once I reboot the machine and I need to again give both parameters after reboot. I also need to give both parameters after a "cold start" to make my touchpad work fine. If I enter just the .nomux parameter, here also it doesn't work if I reboot and I need to enter the .nomux parameter after reboot to make my touchpad work fine. Once I enter .nomux parameter, even after a "cold start", I need to again give the .nomux parameter to make my touchpad work fine. I too tested both options: 1) .nomux with .reset 2) just .nomux several times. But as you can see, only the .nomux parameter is enough for my system. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/69 ------------------------------------------------------------------------ On 2008-10-16T15:42:31+00:00 pkunjapur wrote: (In reply to comment #57 from Jiri Kosina) > Could please all of you who are seeing the problem try to reproduce with the > kernels that can be obtained from > > http://labs.suse.cz/jikos/download/bug-404881/ > > they include the patch that could fix the interrupt storm on EC, causing this > behavior, even without the 'nomux' parameter. Please let me know the results. I double-clicked on "acpi-fix-interrupt-storm.patch" from your website to install it in my kernel like the kernel rpms, but instead it opens a text file with all the detailed information of the fix. Sorry, I am new to Linux. So, could you please direct me how to install that patch in my system. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/70 ------------------------------------------------------------------------ On 2008-10-17T13:47:22+00:00 Jkosina-d wrote: (In reply to comment #60 from Praveen Kunjapur) > I installed all the three kernels - default, base, extra but each time it > gives > me error. > 1) The error for default is: > > Package > /var/tmp/kdecache-praveen/krun/5111.0.kernel-default-2.6.27-19.1.i586.rpm > could > not be installed. You have to install them all at once, i.e. rpm -ivh kernel*2.6.27-19.1*rpm Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver-synaptics/+bug/93897/comments/71 ------------------------------------------------------------------------ On 2008-10-17T13:48:31+00:00 Jkosina-d wrote: (In reply to comment #62 from Praveen Kunjapur) > I double-clicked on "acpi-fix-interrupt-storm.patch" from your website to > install it in my kernel like the kernel rpms, but instead it opens a text file > with all the detailed information of the fix. > Sorry, I am new to Linux. So, could you please direct me how to install that > patch in my system. That patch was attached just for reference, so that we can keep track of the patches that have been tried. You don't have to bother with this specific patch, it is contained in the provided kernel RPMs. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver-synaptics/+bug/93897/comments/72 ------------------------------------------------------------------------ On 2008-10-25T09:57:42+00:00 pkunjapur wrote: (In reply to comment #57 from Jiri Kosina) > Could please all of you who are seeing the problem try to reproduce with the > kernels that can be obtained from > > http://labs.suse.cz/jikos/download/bug-404881/ > > they include the patch that could fix the interrupt storm on EC, causing this > behavior, even without the 'nomux' parameter. Please let me know the results. > Thanks. I downloaded Beta 3 KDE Live CD. I had to use .nomux parameter to install beta3 to hard disk and once again I had to enter .nomux paramter to use the installed beta 3. I downloaded the kernels when I logged in as a normal user and "not" as root. So I used the "su" command and installed all three kernels by using the command: rpm -ivh kernel*2.6.27-19.1*rpm After which I got the following output: Preparing... ########################################### [100%] package kernel-default-base-2.6.27.1-2.1.i586 (which is newer than kernel-default-base-2.6.27-19.1.i586) is already installed package kernel-default-2.6.27.1-2.1.i586 (which is newer than kernel-default-2.6.27-19.1.i586) is already installed package kernel-default-extra-2.6.27.1-2.1.i586 (which is newer than kernel-default-extra-2.6.27-19.1.i586) is already installed Well, that doesn't solve the problem either :( Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/73 ------------------------------------------------------------------------ On 2008-10-30T15:25:33+00:00 Jkosina-d wrote: You can use --oldpackage option to RPM to install thge older package than what is already installed. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/74 ------------------------------------------------------------------------ On 2008-11-03T05:45:45+00:00 pkunjapur wrote: I used "--oldpackage" option. But it still doesn't solve the irregular touchpad problem. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/75 ------------------------------------------------------------------------ On 2008-11-03T12:00:22+00:00 carlos rogerio tonussi wrote: hello folks! I've updated to the last kernel version and as I've highlighted in #59, I still need to use the I8042.reset option on boot time to get the touchpad working fine for the first time. Case not, it always must be restarted after a system "cold start". Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/76 ------------------------------------------------------------------------ On 2008-12-17T19:12:11+00:00 robert wrote: Hi all, I have had a similar problem with my touchpad but this fixes it completely. I have a Dell Vostro 1510. Initially both the keyboard and touchpad never worked well. The irqpoll option on the kernel line sorted out the keyboard permanently but not the touchpad. I played with variations of the acpi=something option which worked intermittently but recently the touchpad basically died completely. I first found the i8042.reset option mentioned elsewhere, I tried it and the touchpad worked but it never allowed me to configure it, e.g. to disable the extremely annoying scrolling functions. I have now added the i8042.nomux option as well and all is ok so far. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver-synaptics/+bug/93897/comments/77 ------------------------------------------------------------------------ On 2008-12-17T19:13:33+00:00 robert wrote: Hi all, I have had a similar problem with my touchpad but this fixes it completely. I have a Dell Vostro 1510. Initially both the keyboard and touchpad never worked well. The irqpoll option on the kernel line sorted out the keyboard permanently but not the touchpad. I played with variations of the acpi=something option which worked intermittently but recently the touchpad basically died completely. I first found the i8042.reset option mentioned elsewhere, I tried it and the touchpad worked but it never allowed me to configure it, e.g. to disable the extremely annoying scrolling functions. I have now added the i8042.nomux option as well and all is ok so far. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver-synaptics/+bug/93897/comments/78 ------------------------------------------------------------------------ On 2008-12-18T11:39:01+00:00 Jkosina-d wrote: Robert, could you please provide output of 'dmidecode' command on your system, so that we can add it to the kernel blacklist, so that 'nomux' is applied automatically on Dell Vostro 1510 systems? Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/79 ------------------------------------------------------------------------ On 2008-12-18T13:37:28+00:00 robert wrote: Created attachment 260853 dmidecode command output for vostro 1510 Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/80 ------------------------------------------------------------------------ On 2009-01-04T22:41:57+00:00 Jkosina-d wrote: (In reply to comment #72 from Robert Kiwanuka) > Created an attachment (id=260853) [details] > dmidecode command output for vostro 1510 Thanks Robert, I have submitted the corresponding patch upstream, so that Dell Vostro 1510 has 'nomux' applied automatically (I have CCed you on the patch submission). Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/81 ------------------------------------------------------------------------ On 2009-01-22T12:11:23+00:00 Jkosina-d wrote: Also submitted to our kernel repository Thu Jan 22 11:29:54 CET 2009 - [email protected] - patches.fixes/input-add-nomux-dell-vostro-1510.patch: Input: add Dell Vostro 1510 to nomux list (bnc#404881). Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/82 ------------------------------------------------------------------------ On 2009-02-18T11:30:54+00:00 carlos rogerio tonussi wrote: Hi all, I've installed OS 11.1 and for my surprise the touchpad is working better than under 11.0! I still need to give the option i8042.reset option on boot, but the final behaviour is very nice! Even the "2-touches" on the pad are being recognised properly, and the cursor starts moving precisely after scratching the pad. best regards Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-driver- synaptics/+bug/93897/comments/83 ** Changed in: xorg-driver-synaptics (openSUSE) Importance: Unknown => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/93897 Title: Alps touchpad problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-driver-synaptics/+bug/93897/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
