Skip site navigation (1)Skip section navigation (2) 
Date:      Tue, 14 Apr 2009 10:09:14 -0500
From:      "Schmehl, Paul L" <pauls@utdallas.edu>
To:        "mail.list freebsd-questions" <freebsd-questions@freebsd.org>
Subject:   Mouse stopped working in X
Message-ID:  <5DC00D3430370A428A709B1E8BF3566641DA99@UTDEVS20.campus.ad.utdallas.edu>
next in thread | raw e-mail | index | archive | help 

[-- Attachment #1 --]
I ran the perl upgrade and portupgrade, and now my mouse doesn't work in
Xorg running KDE.  Works fine in the console, and I haven't changed anything
in the xorg.conf file.  I generated a new one, and the mouse section is
identical to what I already have.

Section "InputDevice"
        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "auto"
        Option      "Device" "/dev/sysmouse"
        Option      "ZAxisMapping" "4 5 6 7"
EndSection

For some reason I now have a PS2 mouse being detected (there's no PS2 port
on this box and there's no PS2 mouse plugged in to it), and I think that's
the cause of the mouse failure in X.

# ls -l /dev/psm0
crw-rw-rw-  1 root  wheel    0,  64 Apr 14 09:33 /dev/psm0

But how do I track down what's causing this device to be loaded?

I also have the usb mouse:

# ls -l /dev/ums0
crw-r--r--  1 root  operator    0,  42 Apr 14 09:29 /dev/ums0

(**) |-->Input Device "Mouse0"
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or
'vmmouse' will be disabled.
(WW) Disabling Mouse0
(==) RADEONHD(0): Silken mouse enabled
(II) config/hal: Adding input device PS/2 Mouse
(II) LoadModule: "mouse"
(II) Loading /usr/local/lib/xorg/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
(**) PS/2 Mouse: Device: "/dev/psm0"
(==) PS/2 Mouse: Protocol: "Auto"
(**) PS/2 Mouse: always reports core events
(==) PS/2 Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) PS/2 Mouse: ZAxisMapping: buttons 4 and 5
(**) PS/2 Mouse: Buttons: 9
(**) PS/2 Mouse: Sensitivity: 1
(II) XINPUT: Adding extended input device "PS/2 Mouse" (type: MOUSE)
(**) PS/2 Mouse: (accel) keeping acceleration scheme 1
(**) PS/2 Mouse: (accel) filter chain progression: 2.00
(**) PS/2 Mouse: (accel) filter stage 0: 20.00 ms
(**) PS/2 Mouse: (accel) set acceleration profile 0
(II) PS/2 Mouse: SetupAuto: hw.iftype is 3, hw.model is 0
(II) PS/2 Mouse: SetupAuto: protocol is PS/2
(II) PS/2 Mouse: ps2EnableDataReporting: succeeded

Dmesg shows the device being loaded:

atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model Generic PS/2 mouse, device ID 0

But also shows the usb mouse being loaded:

ukbd0: <vendor 0x045e Microsoft Natural Keyboard Elite, class 0/0, rev
2.00/2.07, addr 3> on uhub3
kbd2 at ukbd0
ums0: <Logitech Optical USB Mouse, class 0/0, rev 2.00/3.40, addr 4> on
uhub3
ums0: 3 buttons and Z dir.

I have no idea where this PS2 mouse suddenly appeared from, but I think it's
clearly the cause of the problem.

Also, Ctrl-Alt-Bksp no longer restarts X, which is kind of weird.  I can
still switch to other ttys though.

Paul Schmehl (pauls@utdallas.edu)
Senior Information Security Analyst
University of Texas at Dallas
http://www.utdallas.edu/ir/security/


[-- Attachment #2 --]
0	*H
010	+0	*H
00l/`̈zF	[pl0
	*H
010	UUS10U
VeriSign, Inc.1<0:U3Class 2 Public Primary Certification Authority - G21:08U1(c) 1998 VeriSign, Inc. - For authorized use only10UVeriSign Trust Network0
980518000000Z
280801235959Z010	UUS10U
VeriSign, Inc.1<0:U3Class 2 Public Primary Certification Authority - G21:08U1(c) 1998 VeriSign, Inc. - For authorized use only10UVeriSign Trust Network00
	*H
0!t,<!ۗ_R,V,i,̙y9{,„,i	ǩB#OJ1lo'LxmFTįFZ0
l-mw0
	*H
r.qĞ^Q@h❽f/	+$`MD.-Ӯxiorlc70wI5؏ѾGsjT"4d-Y[QY:g2d^Fr'{D00AaaI0nCq0
	*H
010	UUS10U
VeriSign, Inc.1<0:U3Class 2 Public Primary Certification Authority - G21:08U1(c) 1998 VeriSign, Inc. - For authorized use only10UVeriSign Trust Network0
990331000000Z
120330235959Z01'0%U
The University of Texas System10UVeriSign Trust Network1;09U2Terms of use at https://www.verisign.com/rpa (c)991200U)Class 2 CA - OnSite Individual Subscriber1-0+U$The University of Texas at Dallas CA00
	*H
0
"zھ6p`0`S/5ɨ)=d}чTxxLIA
ҥ~BQNths]1)%c#Dj9FXúKzI#C200)U"0 010UPrivateLabel1-1400	`HB0DU =0;09`HE0*0(+https://www.verisign.com/RPA0U00U0
	*H
A\N>B*:da{53#X3 7`IsS
f&w	[x!}0S je(~9j
`eI.is;EHm0q0ڠ#MB3*xݼ0
	*H
01'0%U
The University of Texas System10UVeriSign Trust Network1;09U2Terms of use at https://www.verisign.com/rpa (c)991200U)Class 2 CA - OnSite Individual Subscriber1-0+U$The University of Texas at Dallas CA0
081009000000Z
091009235959Z01'0%U
The University of Texas System1-0+U$The University of Texas at Dallas CA1F0DU=www.verisign.com/repository/CPS Incorp. by Ref.,LIAB.LTD(c)9910UMail Stop - UTD10UPaul L Schmehl1!0	*H
	pauls@utdallas.edu00
	*H
0|o
A~wL6
#3gdڮ3{
M2z5W5ȎQKxc{pŏ@iS=O
kAY-Q܈wh=00	U00U0pauls@utdallas.edu0$U 00`HE00++https://www.verisign.com/rpa-kr0+0NOTICE: Private key may be recovered by VeriSign's customer who may be able to decrypt messages you send to certificate holder.  Use is subject to terms at https://www.verisign.com/rpa-kr (c)99.0	`HB0qUj0h0fdb`http://onsitecrl.verisign.com/TheUniversityofTexasSystemTheUniversityofTexasatDallasCA/LatestCRL0U0U%0++0
	*H
	\'p*`K.3:eg2.V,
a:	—;ڢ shحF=.[K>RoU3AHW(,LxzZrH݌Hk<0q0ڠ>PncM!D¼0
	*H
01'0%U
The University of Texas System10UVeriSign Trust Network1;09U2Terms of use at https://www.verisign.com/rpa (c)991200U)Class 2 CA - OnSite Individual Subscriber1-0+U$The University of Texas at Dallas CA0
081009000000Z
091009235959Z01'0%U
The University of Texas System1-0+U$The University of Texas at Dallas CA1F0DU=www.verisign.com/repository/CPS Incorp. by Ref.,LIAB.LTD(c)9910UMail Stop - UTD10UPaul L Schmehl1!0	*H
	pauls@utdallas.edu00
	*H
0[0A|XD;UW}ؿ[4r#4vz/E,e$ci!UMJ]30-,nxgK7P0HݱCۉTx>7m^_~00	U00U0pauls@utdallas.edu0$U 00`HE00++https://www.verisign.com/rpa-kr0+0NOTICE: Private key may be recovered by VeriSign's customer who may be able to decrypt messages you send to certificate holder.  Use is subject to terms at https://www.verisign.com/rpa-kr (c)99.0	`HB0qUj0h0fdb`http://onsitecrl.verisign.com/TheUniversityofTexasSystemTheUniversityofTexasatDallasCA/LatestCRL0U 0U%0++0
	*H
Re'5sC_󇢽{Rs5BxO3"#1{}Qa$(܊lHMl0ur[K.|V{1=X5̩vĩq)gkoen;10001'0%U
The University of Texas System10UVeriSign Trust Network1;09U2Terms of use at https://www.verisign.com/rpa (c)991200U)Class 2 CA - OnSite Individual Subscriber1-0+U$The University of Texas at Dallas CA#MB3*xݼ0	+0	*H
	1	*H
0	*H
	1
090414150915Z0#	*H
	1%-1I|f"t0g	*H
	1Z0X0
*H
0*H
0
*H
@0+0
*H
(0+0
*H
0	+71001'0%U
The University of Texas System10UVeriSign Trust Network1;09U2Terms of use at https://www.verisign.com/rpa (c)991200U)Class 2 CA - OnSite Individual Subscriber1-0+U$The University of Texas at Dallas CA>PncM!D¼0*H
	101'0%U
The University of Texas System10UVeriSign Trust Network1;09U2Terms of use at https://www.verisign.com/rpa (c)991200U)Class 2 CA - OnSite Individual Subscriber1-0+U$The University of Texas at Dallas CA>PncM!D¼0
	*H
'{Eވ
 $t	NDO~c,A~^ 'lfx&
Q2HAOvckC7i*y{&l@5_VzR>91bK*R_[]

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5DC00D3430370A428A709B1E8BF3566641DA99>