[opensuse] Mouse movement Jerky!
Hello! I have just installed opensuse 10.2 on an older computer for my son and the mouse is jerky. I will describe my system and hardware for possible solutions. Processor Pentium III coppermine @ 667 Mhz VIA chipset ATI Radeon 7000 RV100 QY (Radeon 7000VE) System Memory 512 Mb Here is what I am experiencing, even on a desktop with nothing open if I move the mouse around the screen it will move with a sudden stop and then start moving again. It seems (I have not timed this) to stop about every 2 seconds with about a 0.5 second delay before it starts moving again. This I set the screen resolution to 1024x768 down from 1152x864 to see if that would make a difference but it would not. I have disabled just about everything thing that may run in the background with the exceptions of critical system components. I made sure the system had the correct settings in xorg.conf regarding dri subsection. I have looked at dmesg and messages but I do not see any blatant errors. Any thoughs would be appreciated, this is annoying but I would can at least use the machine. It just interferes with games like ppracer. That game plays fine except for the momentary system freezes. TIA John -- Registered Linux User 263680, get counted at http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 18 January 2007 21:56, John Pierce wrote:
Here is what I am experiencing, even on a desktop with nothing open if I move the mouse around the screen it will move with a sudden stop and then start moving again. It seems (I have not timed this) to stop about every 2 seconds with about a 0.5 second delay before it starts moving again.
Open a terminal window, then enter "top" and see what process is running that is eating your cpu time. Fred -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Open a terminal window, then enter "top" and see what process is running that is eating your cpu time.
Fred
I opened a terminal and ran top, under the %cpu the highest I saw in 5 minutes was 0.6. Under the PR field I see one process listed as RT and that is migration/0. John -- Registered Linux User 263680, get counted at http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Pierce wrote:
Hello!
I have just installed opensuse 10.2 on an older computer for my son and the mouse is jerky.
I will describe my system and hardware for possible solutions.
Processor Pentium III coppermine @ 667 Mhz VIA chipset ATI Radeon 7000 RV100 QY (Radeon 7000VE) System Memory 512 Mb
Here is what I am experiencing, even on a desktop with nothing open if I move the mouse around the screen it will move with a sudden stop and then start moving again. It seems (I have not timed this) to stop about every 2 seconds with about a 0.5 second delay before it starts moving again. This I set the screen resolution to 1024x768 down from 1152x864 to see if that would make a difference but it would not. I have disabled just about everything thing that may run in the background with the exceptions of critical system components.
I made sure the system had the correct settings in xorg.conf regarding dri subsection.
I have looked at dmesg and messages but I do not see any blatant errors.
Any thoughs would be appreciated, this is annoying but I would can at least use the machine. It just interferes with games like ppracer. That game plays fine except for the momentary system freezes.
That sounds exactly like beagle. I saw the same symptoms on a new install of 10.1, but after removing all traces of beagle, the system became silky smooth and responsive, and quake 3 arena ran like a scalded cat. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
That sounds exactly like beagle. I saw the same symptoms on a new install of 10.1, but after removing all traces of beagle, the system became silky smooth and responsive, and quake 3 arena ran like a scalded cat.
Joe
I do not have beagle or kerry either one installed. I even uninstalled zmd. I even suspected the mouse, but the problem even happens in init 3 with the keyboard. John -- Registered Linux User 263680, get counted at http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Pierce wrote:
That sounds exactly like beagle. I saw the same symptoms on a new install of 10.1, but after removing all traces of beagle, the system became silky smooth and responsive, and quake 3 arena ran like a scalded cat.
Joe
I do not have beagle or kerry either one installed. I even uninstalled zmd. I even suspected the mouse, but the problem even happens in init 3 with the keyboard.
Something might be funny with the hardware then. How much RAM do you have? is swap being used? Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 18 January 2007 18:56, John Pierce wrote:
I will describe my system and hardware for possible solutions.
Processor Pentium III coppermine @ 667 Mhz VIA chipset ATI Radeon 7000 RV100 QY (Radeon 7000VE) System Memory 512 Mb
Here is what I am experiencing, even on a desktop with nothing open if I move the mouse around the screen it will move with a sudden stop and then start moving again. It seems (I have not timed this) to stop about every 2 seconds with about a 0.5 second delay before it starts moving again.
This sounds suspiciously like the problems I had back in SUSE 8.mumble prior to acpi support being properly implemented. The solution finally settled upon was that if the bios date was after 2001 acpi would be attempted, but if earlier it would not be. However some machines with bios dates near 2001 either do or do not work well with / without acpi in contradiction to the rule. (jeeze what a mouth-full). Example: I have this dual celeron machine which needs me to add acpi=force to the boot command line because its bios is earlier than 2001, but it works much better with acpi turned on. Symptoms are sleeps in usb bus - making for pauses. So, long story short, read carefully thru /var/log/boot.msg for something like <3>ACPI: BIOS age (2000) fails cutoff (2001), acpi=force is required to enable ACPI And if found, try adding acpi=force to the boot prompt line, and if that improves things add it to the end of the line in /boot/grup/menu.lst: kernel /boot/vmlinuz root=/dev/hde1 vga=0x31a resume=/dev/hdf1 splash=silent showopts acpi=force Above is one long line..... -- _____________________________________ John Andersen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 18 January 2007 22:56, John Pierce wrote:
Hello!
I have just installed opensuse 10.2 on an older computer for my son and the mouse is jerky.
/snip/
Here is what I am experiencing, even on a desktop with nothing open if I move the mouse around the screen it will move with a sudden stop and then start moving again. It seems (I have not timed this) to stop about every 2 seconds with about a 0.5 second delay before it starts moving again. This I set the screen resolution to 1024x768 down from 1152x864 to see if that would make a difference but it would not. I have disabled just about everything thing that may run in the background with the exceptions of critical system components.
/snip/ I saw something like this in Windows once. It seems I had a 3-button mouse protocol installed, instead of a 2-button. (5-bit instead of 3-bit, if I remember correctly.) I don't know if there is this kind of option in Linux. Did you have the mouse connected when you did the install? Good luck--doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I have just installed opensuse 10.2 on an older computer for my son and the mouse is jerky.
Isn't mouse jerky like really really small? I like beef jerky, but it's much larger and you can chew on it for a while. Enquiring minds want to know! -- If a kid asks where rain comes from, I think a cute thing to tell him is "God is crying." And if he asks why God is crying, another cute thing to tell him is "Probably because of something you did." -- Jack Handy San Francisco, CA -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Okey dokey! I placed acpi=force in /boot/grub/menu.lst and the problem has gone away. Prior to placing that on the kernel options line I had only 1 reference to acpi in /var/log/boot.msg and that had to do with the BIOS failing the cutoff date. Now every thing works fine, but I have many references to acpi in the boot.msg file. But they are in notices about various things being initialized and those items are referencing the kernel boot line. Now, for the most inquiring minds, mouse jerky is quite tasty, but you do have to eat quite a bit more to be fully sated. John -- Registered Linux User 263680, get counted at http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 19 January 2007 18:35, John Pierce wrote:
I placed acpi=force in /boot/grub/menu.lst and the problem has gone away. Prior to placing that on the kernel options line I had only 1 reference to acpi in /var/log/boot.msg and that had to do with the BIOS failing the cutoff date.
Glad that worked out for you. Anybody with a machine bios date earlier than 2001 should (by a year or two) should try this option at least once. -- _____________________________________ John Andersen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 20 January 2007 12:07, John Andersen wrote:
On Friday 19 January 2007 18:35, John Pierce wrote:
I placed acpi=force in /boot/grub/menu.lst and the problem has gone away. Prior to placing that on the kernel options line I had only 1 reference to acpi in /var/log/boot.msg and that had to do with the BIOS failing the cutoff date.
Glad that worked out for you. Anybody with a machine bios date earlier than 2001 should (by a year or two) should try this option at least once.
Dear John, Your comment draw my attention. Could you explain why for older machines acpi=force is advised? What does it do and why is force necessary? Are there more thing to be forced on an old computer? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 21 January 2007 20:28, Contant Brouerius van Nidek wrote:
On Saturday 20 January 2007 12:07, John Andersen wrote:
On Friday 19 January 2007 18:35, John Pierce wrote:
I placed acpi=force in /boot/grub/menu.lst and the problem has gone away. Prior to placing that on the kernel options line I had only 1 reference to acpi in /var/log/boot.msg and that had to do with the BIOS failing the cutoff date.
Glad that worked out for you. Anybody with a machine bios date earlier than 2001 should (by a year or two) should try this option at least once.
Dear John, Your comment draw my attention. Could you explain why for older machines acpi=force is advised? What does it do and why is force necessary? Are there more thing to be forced on an old computer?
Well its because acpi was introduced during 2000 to 2001 time frame and did not become common until about 2001. So most distros error on the safe side and don't even try it on earlier machines. However, quality boards began shipping it in 2000 (actually as early as 1999) and those boards depended on it to get all perepharals working. Jerky mouse was a classic symptom, as was choppy sound. Once you turned on acpi on these boards they often work as intended. The kernel developers decided that 2001 was a reasonable cut off date because there were a number of machines that had broken acpi implementations which were manufactured prior to 2001. So its not ALWAYS advised. Just when you have symptoms, AND forcing it on fixes those symptoms. -- _____________________________________ John Andersen
On Monday 22 January 2007 12:49, John Andersen wrote:
On Sunday 21 January 2007 20:28, Contant Brouerius van Nidek wrote:
On Saturday 20 January 2007 12:07, John Andersen wrote:
On Friday 19 January 2007 18:35, John Pierce wrote:
I placed acpi=force in /boot/grub/menu.lst and the problem has gone away. Prior to placing that on the kernel options line I had only 1 reference to acpi in /var/log/boot.msg and that had to do with the BIOS failing the cutoff date.
Glad that worked out for you. Anybody with a machine bios date earlier than 2001 should (by a year or two) should try this option at least once.
Dear John, Your comment draw my attention. Could you explain why for older machines acpi=force is advised? What does it do and why is force necessary? Are there more thing to be forced on an old computer?
Well its because acpi was introduced during 2000 to 2001 time frame and did not become common until about 2001. So most distros error on the safe side and don't even try it on earlier machines.
However, quality boards began shipping it in 2000 (actually as early as 1999) and those boards depended on it to get all perepharals working. Jerky mouse was a classic symptom, as was choppy sound. Once you turned on acpi on these boards they often work as intended.
The kernel developers decided that 2001 was a reasonable cut off date because there were a number of machines that had broken acpi implementations which were manufactured prior to 2001.
So its not ALWAYS advised. Just when you have symptoms, AND forcing it on fixes those symptoms. Worked for me so I was wondering. My board falls in this period of time. Always wondered why my mice were going wild. Cleaned the bottom side regularly and never got it under control. Thanks for the tip. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
Contant Brouerius van Nidek -
Doug McGarrett -
J Sloan -
John Andersen -
John Pierce -
Michael Nelson -
Stevens