--On Tuesday, April 14, 2009 19:21:34 +0300 Manolis Kiagias <sonic200...@gmail.com> wrote:

Schmehl, Paul L wrote:
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 (pa...@utdallas.edu)
Senior Information Security Analyst
University of Texas at Dallas
http://www.utdallas.edu/ir/security/



The fact that CTRL+ALT+BACKSPACE does not work indicates that you
probably upgraded to Xorg 7.4

Try inserting the following in your xorg.conf to fix keyboard/mouse
problems:

Section "ServerFlags"
        Option "AutoAddDevices" "false"
        Option "AllowEmptyInput" "false"
        Option "DontZap" "false"
EndSection

(DontZap will restore the previous CTRL+ALT+BKSP behaviour)



Thanks. I had already figured out that I needed to add AllowEmptyInput false, and the mouse is now working. But I'll add the other two as well.

Apparently this is a change introduced by 7.4?

--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*******************************************
Check the headers before clicking on Reply.

_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Reply via email to