Re: [SLE] Strange Mouse Problem
From: Robert Morrison (orbert_at_orbert.net)
To: email@example.com Date: Mon, 14 Nov 2005 16:50:06 -0600
On Monday 14 November 2005 15:53, Jerry Feldman wrote:
> First, exactly what mouse hardware do you have.
It's a Dell USB Optical Wheel mouse. The base says "M/N: M-UVDEL1",
which may or may not be the model number.
I get the following from KInfoCenter:
=== BEGIN KInfoCenter ===
Optical USB Mouse
Class 0 ((Defined at Interface level))
USB Version 2.00
Vendor ID 0x46d (Logitech, Inc.)
Product ID 0xc016 (Optical Mouse)
Speed 1.5 Mbit/s
Max. Packet Size 0
=== END KInfoCenter ===
I get similar info from Yast's "Hardware Information" tool.
Note that this is probably not exactly correct (since the
mouse pointer still jumps ...)
> Do you have a KVM or are you direct connect.
> Note that unplugging and reinserting the mouse into a PS/2 port is not
I understand, sorry I was not explicit about this being a USB mouse.
> Most of the time you should not have a problem.
> Some things to look at:
> Do you have gpm running. GPM is the tool that allows you to use your mouse
> in console mode. If it is currently running turn it off.
Yast says gpm is installed, but when I mark it for deletion Yast
complains that 23 packages depend on it. Some of them I'd be
worried about deleting. When I go to "System Services (Runlevel)"
it says gpm is NOT enabled. Is that sufficient?
> I suggest that you go to the Graphics and Display and set both the display
> and the mouse at the same time.
Sorry to be dense, I don't understand. I see:
Yast -> HW -> Graphics Card and Monitor
which gives me the options to "change" and "reprobe". Clicking
"change" brings up SaX2 and a whole other series of dialogs.
When I click "finalize" I get an error dialog complaining:
Monitor (0) with ID: undefined
Option "NoDDC" not found
and an option to manually configure. But I'm not sure what I can
safely change. And all of this is separate from
Yast -> HW -> Mouse Model
so I'm not sure how to approach this so the changes will be
applied "at the same time."
> This will force the rewrite of the
> xorg.conf (/etc/X11/xorg.conf you might check this manually).
I've been watching this file. A lot of the google results for
mouse (pointer OR cursor) (jump OR jumping) corner suse
point to that file, and I've been looking at it. Just haven't found
the right magical incantations yet. And besides, most of the suggested
solutions involve editing the file directly, but it says:
# SaX generated X11 config file
# Created on: 2005-11-14T12:49:16-0600.
# Automatically generated by [ISaX] (4.8)
# PLEASE DO NOT EDIT THIS FILE!
which makes me worried about changing it manually.
> Once you do
> this, shut down your computer to a full power off. This will force a reset
> on all the boards. Then, after the reboot, check the mouse operation before
> you log in.
I've gone through multiple power cycles during this process. (I've
been working on this on and off for over a week.) The mouse
does not work at all, either before or after login, until I run
Yast as I described in my previous message.
> Then check it after you log in. if the mouse's operation is ok
> before you log in to KDE or GNOME but not afterwards, then the problem may
> be in the KDE or GNOME controls not with X itself.
Thanks for your help.
-- Check the headers for your unsubscription address For additional commands send e-mail to firstname.lastname@example.org Also check the archives at http://lists.suse.com Please read the FAQs: email@example.com