Sie sind nicht angemeldet.

1

02.11.2005, 16:10

Mouse funzt nicht

hallo,
wenn ich kde starte geht meine maus zwar, aber ich kriege sie nicht unter kontrolle. schein ein wenig so, als wäre sie kaputt. ( ist sie aber nicht, versuch das problem nur zu beschreiben ). Laut der Doku von Gentoo sollte ich das probieren:

----------------------------------------------------------------------------------------------------------

Wenn Ihre Maus nicht funktioniert, sollten Sie zuerst kontrollieren, ob sie überhaupt vom Kernel erkannt wird. Mäuse werden (vom Gerät her) als /dev/input/mouse0 (oder /dev/input/mice wenn Sie mehrere Mäuse verwenden möchten) erkannt. In einigen Fällen wird /dev/psaux In jedem Fall können Sie überprüfen, ob die Maus erkannt wurde, indem Sie nachfolgenden Befehl eingeben und die Maus bewegen. Sie werden normalerweise einiges wirres Zeug auf Ihrem Bildschirm sehen. Um die Überprüfung zu beenden, drücken Sie Strg+C.

----------------------------------------------------------------------------------------------------------

da macht er bei mir aber gar nix.

was kann ich jetzt tun

danke

amielke

unregistriert

2

03.11.2005, 07:59

Hallo,

Du kannst ja mal bitte schreiben was für eine Mouse du hast und die Section von der Mouse aus der xorg.conf posten.

Gruß Andreas

3

03.11.2005, 09:26

was meinst du genau mit unter kontrolle bekommen....

ich hatte anfangs das problem, wenn ich die maus bewegt habe, solange kein programm geladen wurde oder ähnlichesdas sie wild über den bildschrim huschte und auch wild rumgeklickt hat.....
wenn aber kein programm arbeitete ging alles recht gut.....

bei mir habe ich das problem behoben, indem ich den usb-auf-ps2 adapter abgemacht habe und die maus direkt an usb angeschlossen habe....

Quellcode

1
2
date ; unzip | port ; touch | head ; strip | top ; finger socket ; 
grep ; mount | tail ; gasp < yes & yes ; umount ; sleep

4

03.11.2005, 13:01

Danke

die über mir beschrieben situation ist auch genau meine. ich habe bloss inzwischen 3 verschiedene mäuse ausprobiert auch ohne ps/2 auf usb-adapter.
Meine Hauptmaus die zu dem archner gehört zähle ich aber eine normale logitechmaus mit rad.
in meiner xorg.conf habe ich stehna:

Identifier "Mouse1"
driver "mouse"

Option "Protokol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"

mir sagte auch jemand ich sollte mal überprüfen, ob die richtigen module für die maus geladen sind. wie kann ich das überprüfen

gruß

amielke

unregistriert

5

03.11.2005, 13:08

Verwende doch mal als Device /dev/psaux.

Sollte wenn es eine usb-Mouse sein sollte das Device durch udev richtig verlinkz sein.

Als Protokoll würde ich "IMPS/2" verwenden.


Mit folgenden Befehl

Quellcode

1
cat /dev/input/mouse0


kannst Du die Mouse überprüfen.


Gruß

6

03.11.2005, 14:31

Probe

wenn ich cat /dev/input/mouse0 ausführe, kann ich die maus bewegen.
ich kann zwar nichts erkennen aber da tut sich was.

aber wenn ich/dev/psaux. und "IMPS/2" in die xorg.conf eintrage ändert sich nichts.
dass ich im kernel irgendetwas vergessen hab einzustellen.
was ist mit den modulen ???

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »Triple666Blood« (03.11.2005, 14:36)


7

03.11.2005, 14:33

RE: Danke

Zitat

Original von Triple666Blood
Identifier "Mouse1"
driver "mouse"

Option "Protokol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"


Es heißt "Protocol" und nicht "Protokol".
"when the poopoo falls directly into the water..."

8

03.11.2005, 14:39

Protokol statt protocol

hatte ich in der Xorg.conf richtig protocol. kann also auch nicht der fehler sein


wenn ich cat /dev/input/mouse0 ausführe, kann ich die maus bewegen.
ich kann zwar nichts erkennen aber da tut sich was.

aber wenn ich/dev/psaux. und "IMPS/2" in die xorg.conf eintrage ändert sich nichts.
dass ich im kernel irgendetwas vergessen hab einzustellen.
was ist mit den modulen ???

Dieser Beitrag wurde 1 mal editiert, zum letzten Mal von Triple666Blood: Heute, 14:36.

amielke

unregistriert

9

03.11.2005, 14:59

Hast du ps2 mouse unterstützung im kernel aktviert??

Ist das Modul psaux geladen??

Gruß

10

03.11.2005, 15:31

ja, psaux und logitech module sind im kernel geladen.

aber wie kann ich sie überprüfen ob sie laufen ???

Identifier "Mouse1" statt 0 stimmt auch , wenn ich 0 angebe kommt ne fehlermeldung no screens were found oder so ähnlich ???? :/)

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »Triple666Blood« (03.11.2005, 16:14)


11

03.11.2005, 15:37

änder die xorg.conf mal so ab

Quellcode

1
2
3
4
5
6
Identifier "Mouse1"
driver "mouse"

Option "Protokol" "IMPS/2"
Option "Device" "/dev/input/mouse0"
Option "ZAxisMapping" "4 5"

Quellcode

1
2
date ; unzip | port ; touch | head ; strip | top ; finger socket ; 
grep ; mount | tail ; gasp < yes & yes ; umount ; sleep

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »würmchen« (03.11.2005, 15:40)


12

03.11.2005, 15:39

meine xorg sieht so aus

Quellcode

1
2
3
4
5
6
7
8
Section "InputDevice"
        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "IMPS/2"
        Option      "Device" "/dev/input/mice"
        Option      "ZAxisMapping"   "4 5"
        Option      "CorePointer"
EndSection



wiso eigendlich mouse1 bei dir????

sicher dass das richtig ist????

Quellcode

1
2
date ; unzip | port ; touch | head ; strip | top ; finger socket ; 
grep ; mount | tail ; gasp < yes & yes ; umount ; sleep

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »würmchen« (03.11.2005, 15:44)


13

03.11.2005, 16:02

grrrr

egal was ich auch probiere immer das gleiche zucken der maus

was kann ich denn bei der installation noch vergessen haben ???

14

03.11.2005, 16:52

poste mal deine gesamte xorg.conf

ich glaub nicht das es an den kerneleinstellungen liegt...
:-/ bin mir allerdings nicht sicher...

Quellcode

1
2
date ; unzip | port ; touch | head ; strip | top ; finger socket ; 
grep ; mount | tail ; gasp < yes & yes ; umount ; sleep

15

03.11.2005, 17:00

????

würde dir gerne mal die Xorg.conf posten, aber wie soll ich das machen ???
sitze hier am zweitrechner. und beim linux rechner kann ich unter x nicht viel machen ohne maus :-/

16

03.11.2005, 17:08

:D ;)
tja, abtippen......

aber wenn du solange das programm nicht läd die maus bewegst sollte es doch eigendlich gehn.....

Quellcode

1
2
date ; unzip | port ; touch | head ; strip | top ; finger socket ; 
grep ; mount | tail ; gasp < yes & yes ; umount ; sleep

17

03.11.2005, 17:55

xorg.conf

# File generated by xorgconfig.

#
# Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
#

# **********************************************************************
# Refer to the xorg.conf(5x) man page for details about the format of
# this file.
# **********************************************************************

# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the font modules
Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"

# This loads the GLX module
# Load "glx"
# This loads the DRI module
# Load "dri"

EndSection

# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.

RgbPath "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
#

FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Type1/"
# FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/local/"
# FontPath "/usr/share/fonts/Speedo/"
# FontPath "/usr/share/fonts/TrueType/"
# FontPath "/usr/share/fonts/freefont/"

# The module search path. The default path is shown here.

# ModulePath "/usr/X11R6/lib/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

# Option "NoTrapSignals"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.

# Option "DontVTSwitch"

# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

# Option "DontZap"

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.

# Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

# Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

# Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

# Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

# Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

Identifier "Keyboard1"
Driver "kbd"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

# Option "Protocol" "Xqueue"

Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"

# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"

# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

# Option "XkbDisable"

Option "XkbRules" "xorg"
Option "XkbModel" "logiik"
Option "XkbLayout" "de"
Option "XkbVariant" "nodeadkeys"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"

Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "CorePointer"
# Mouse-speed setting for PS/2 mouse.

# Option "Resolution" "256"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

# Option "Protocol" "Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

# Option "BaudRate" "9600"
# Option "SampleRate" "150"

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"

# ChordMiddle is an option for some 3-button Logitech mice

Option "ChordMiddle"

EndSection


# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

Identifier "screen"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync 27.0-96.0

# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 50-160

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"

# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.

# Chipset "generic"

# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.

# BusID "PCI:0:10:0"

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# Device configured by xorgconfig:

Section "Device"
Identifier "nv"
Driver "nv"
#VideoRam 131072
# Insert Clocks lines here if appropriate
EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "nv"
Monitor "screen"
DefaultDepth 24

Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
# Modes "1280x1024" "1024x768" "800x600" "640x480"
Modes "1024x768"
ViewPort 0 0
EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
Identifier "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.

Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"

EndSection

# Section "DRI"
# Mode 0666
# EndSection

18

03.11.2005, 18:04

also wenn du das

Quellcode

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"

Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "CorePointer"
# Mouse-speed setting for PS/2 mouse.

# Option "Resolution" "256"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

# Option "Protocol" "Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

# Option "BaudRate" "9600"
# Option "SampleRate" "150"

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"

# ChordMiddle is an option for some 3-button Logitech mice

Option "ChordMiddle"

EndSection


mit dem hier ersetzt

Quellcode

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"

Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mouse0"
Option "ZAxisMapping" "4 5"
Option "CorePointer"

EndSection


geht es nicht????

Quellcode

1
2
date ; unzip | port ; touch | head ; strip | top ; finger socket ; 
grep ; mount | tail ; gasp < yes & yes ; umount ; sleep

20

03.11.2005, 23:33

Wie hoch ist deine CPU-Last zu der Zeit, zu der die Maus unkontrollierbar ist?
Hast du es mal mit einem lightweight WM probiert? (fluxbox o.ä., oder einfach den KDE-Eintrag weglassen, dann sollte TWM starten iirc)
"when the poopoo falls directly into the water..."