mouse klicks bei X-server gehen nicht richtig

D

darmon

Well-Known Member
hi,

bei meinem x-server hab ich probleme mit miener maus,
udn zwar wenn ich fenster mit dem linken mouseknopf öffnen will, dann dauert des immer eine zeitlang oder der klick wird nicht registriert.
nun meine frage, wo kann ich die mouse so konfigurieren, dass der knopfdruck sofort übernommen wird? muss ich eventuell änderungen in der XF86config datei vornehmen????


gruss
andi
 
Hast du schon das gleiche mit einer anderen Maus versucht?
Wenn ja und gleiches Problem => Dose oder Treiber/XFree/Programm hat Problem;
wenn ja und kein Problem => Maus defekt.
 
wie dose????

hab zwei verschiedene mäuse hingehängt ,aber selbes problem.

hab aber auch auf auto detect gestellt. kanns daran liegen
 
Kann deine Maus auch sicher das ps2 Protokoll?
Nicht alle USB mäuse kann man mit Adapter an einem ps2 Port hängen.
 
die maus funktioniert ja, mein problem is nur das ich beim xserver, wenn ich z.b im browser unterwegs bin und einen button dort drücken will dieser sich nicht sofort öffnet, ich muss sehr lange auf dem mouseknopf bleiben ,dann gehts.
hab mir gedacht vielleicht kann ich die reaktionszeit der mouseknöpfe oder ähnliches verändern.....
 
Schau mal unter:
http://www.freebsd.org/cgi/man.cgi?query=moused&sektion=8

Configuring Mouse Daemon
The first thing you need to know is the interface type of the mouse you
are going to use. It can be determined by looking at the connector of
the mouse. The serial mouse has a D-Sub female 9- or 25-pin connector.
The bus and InPort mice have either a D-Sub male 9-pin connector or a
round DIN 9-pin connector. The PS/2 mouse is equipped with a small,
round DIN 6-pin connector. Some mice come with adapters with which the
connector can be converted to another. If you are to use such an
adapter, remember the connector at the very end of the mouse/adapter pair
is what matters. The USB mouse has a flat rectangular connector.

The next thing to decide is a port to use for the given interface. For
the bus, InPort and PS/2 mice, there is little choice: the bus and InPort
mice always use /dev/mse0, and the PS/2 mouse is always at /dev/psm0.
There may be more than one serial port to which the serial mouse can be
attached. Many people often assign the first, built-in serial port
/dev/cuaa0 to the mouse. You can attach multiple USB mice to your system
or to your USB hub. They are accessible as /dev/ums0, /dev/ums1, and so
on. ~ You may want to create a symbolic link /dev/mouse pointing to the
real port to which the mouse is connected, so that you can easily distin-
guish which is your ``mouse'' port later.

The next step is to guess the appropriate protocol type for the mouse.
The moused utility may be able to automatically determine the protocol
type. Run the moused utility with the -i option and see what it says.
If the command can identify the protocol type, no further investigation
is necessary on your part. You may start the daemon without explicitly
specifying a protocol type (see EXAMPLES).

The command may print sysmouse if the mouse driver supports this protocol
type.

Note that the type and model printed by the -i option do not necessarily
match the product name of the pointing device in question, but they may
give the name of the device with which it is compatible.

If the -i option yields nothing, you need to specify a protocol type to
the moused utility by the -t option. You have to make a guess and try.
There is rule of thumb:

1. The bus and InPort mice always use busmouse protocol regardless of
the brand of the mouse.
2. The ps/2 protocol should always be specified for the PS/2 mouse
regardless of the brand of the mouse.
3. You must specify the auto protocol for the USB mouse.
4. Most 2-button serial mice support the microsoft protocol.
5. 3-button serial mice may work with the mousesystems protocol. If it
does not, it may work with the microsoft protocol although the third
(middle) button will not function. 3-button serial mice may also
work with the mouseman protocol under which the third button may
function as expected.
6. 3-button serial mice may have a small switch to choose between
``MS'' and ``PC'', or ``2'' and ``3''. ``MS'' or ``2'' usually mean
the microsoft protocol. ``PC'' or ``3'' will choose the
mousesystems protocol.
7. If the mouse has a roller or a wheel, it may be compatible with the
intellimouse protocol.

To test if the selected protocol type is correct for the given mouse,
enable the mouse pointer in the current virtual console,

vidcontrol -m on

start the mouse daemon in the foreground mode,

moused -f -p _selected_port_ -t _selected_protocol_

and see if the mouse pointer travels correctly according to the mouse
movement. Then try cut & paste features by clicking the left, right and
middle buttons. Type ^C to stop the command.

HTH,
lars.
 
danke lars,

für deine hilfe!!!!!

hab die probleme mit meiner maus gelöst indem ich auf die BSD version 5.1 aufgestockt habe. frag mich nicht warum aber der xserver lief unter 4.6 nicht so richtig gut, mousedelay und andere merkwürdigkeiten, jetzt läuft aber alles wunderbar........
 
Du musst dich einloggen oder registrieren, um hier zu antworten.
Zurück
Oben