Re: Mouse stopped working in X
On Sat, 09 Jun 2012 06:06:49 +0200, Bernt Hansson wrote: 2012-05-22 10:44, Polytropon skrev: On Tue, 22 May 2012 10:17:16 +0200, Bernt Hansson wrote: There is a second way of doing this stunt. Start X When X is up and running press CTRL+ALT+F3 or any F* frpm F3 up to F8 then you get to the console Su to root in the console and type in /usr/local/etc/rc.d/dbus restart /usr/local/etc/rc.d/hald restart Then press ALT+F9 to get back to X So if that is the _solution_ It is not near any solution. I do not think this issue have anything to do with hal or dbus. I didn't claim it was a solution, I just wanted to make the therapy more elegant; see the difference between therapy (treating symptoms) and the actual cure of a disease (removing the cause). As I'm only running old-fashioned stuff here, I can't be more specific regarding the newest inventions of why X stopped acting as expected. In the past, simply removing HAL and DBUS altogether and using a xorg.conf file to make the required settings has worked at least for me. My idea of automating the manual step of restarting HAL and DBUS (which _seems_ to have treated the symptoms of a non-working mouse) was to put that into the X initialisation file: sudo /usr/local/etc/rc.d/dbus restart sudo /usr/local/etc/rc.d/hald restart. Of couse that doesn't even remotely touch a possible problem caused elsewhere. And does it look totally stupid? Sure it does. It looks so wrong, but sometimes the wrongest thing just works (TM). :-) My machine at the office running the same hal and X as the one at home does not have this kind of problems. That might be a good indicator that there actually is something different in those machines, and this difference causes the problem. Maybe it's something simple, and really not related to HAL. As I said, I'm not sure, as I'm not using it. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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
Re: Mouse stopped working in X
On Tue, May 22, 2012 at 10:44 AM, Polytropon free...@edvax.de wrote: On Tue, 22 May 2012 10:17:16 +0200, Bernt Hansson wrote: There is a second way of doing this stunt. Start X When X is up and running press CTRL+ALT+F3 or any F* frpm F3 up to F8 then you get to the console Su to root in the console and type in /usr/local/etc/rc.d/dbus restart /usr/local/etc/rc.d/hald restart Then press ALT+F9 to get back to X So if that is the _solution_, why not try to automate it? Not tested, just a suggestion: Make this the last-1 line in ~/.xinitrc (or ~/.xsession depending on actual setup), before the exec call to the WM / DE, maybe like this: #!/bin/sh [ -f ~/.xmodmaprc ] xmodmap ~/.xmodmaprc xterm xsetroot -solid rgb:3b/4c/7a xset b 100 1000 15 xset r rate 250 30 xset s off xset -dpms - sudo /usr/local/etc/rc.d/dbus restart sudo /usr/local/etc/rc.d/hald restart exec wmaker It should happen when X is running, and it should be back to normal when the WM or DE is launched (and all background programs have fully started). Yep, that's a good idea... as well as switching to a text console, issue the commands there, and then go back to X. But IMHO, the *real* solution is to fix hald (or its config), so that it tries /dev/sysmouse, or whatever mouse is configured in Xorg.conf, instead of automatically picking some wrong mouse device. I guess the problem stems from the fact, that when moused is running, it has already grabbed the real mouse device (e.g. /dev/psm0) and provides the virtual device /dev/sysmouse. When hald starts the first time, it tries to grab the real mouse device too... and fails because that mouse is already used by moused, and is therefore locked. Only when hald tries to load /dev/sysmouse the second time it is started, will it succeed. Unfortunatly, hald config is pretty black magic to me. I wouldn't touch that with a 10 ft. pole. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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
Re: Mouse stopped working in X
012-05-20 14:17, C. P. Ghost skrev: On Fri, May 18, 2012 at 2:27 PM, Bernt Hanssonb...@bananmonarki.se wrote: 2012-05-18 13:49, J. W. Ballantine skrev: Hi, Before the update of x11 on 4/21/2012, X was working fine, but now when I startx, my usb and touchpad mouse are no longer found. The mouse works in terminal mode, and hald and dbus are started in /etc/rc.conf. I have exactly the same problem. What windowmanager are you using? I'm using xfce4, I have a workaround for that. 1. start X 2. when it comes up press alt+F2, the start program dialog comes up 3. type in xterm or your terminal of choice 4. in your terminal su to root then type /usr/local/etc/rc.d/dbus restart /usr/local/etc/rc.d/hald restart wait a few seconds and the mouse should work again. There is a second way of doing this stunt. Start X When X is up and running press CTRL+ALT+F3 or any F* frpm F3 up to F8 then you get to the console Su to root in the console and type in /usr/local/etc/rc.d/dbus restart /usr/local/etc/rc.d/hald restart Then press ALT+F9 to get back to X I have the same problem but with a ps/2 mouse. Restarting dbus and hald from within an xterm is a workable workaround. Since I'm using fluxbox, I start an xterm in ~/.xinitrc in the background to get a terminal before exec-ing fluxbox. Luckily, this xterm has already the focus. This is the relevant part of /var/log/Xorg.0.log regarding the mouse: (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 compiled for 1.7.7, module version = 1.7.1 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 7.0 (WW) PS/2 Mouse: No Device specified, looking for one... (II) PS/2 Mouse: Setting Device option to /dev/psm0 (--) PS/2 Mouse: Device: /dev/psm0 (==) PS/2 Mouse: Protocol: Auto (**) PS/2 Mouse: always reports core events (**) Option Device /dev/psm0 (EE) xf86OpenSerial: Cannot open device /dev/psm0 Device busy. (EE) PS/2 Mouse: cannot open input device (II) UnloadModule: mouse (EE) PreInit returned NULL for PS/2 Mouse (EE) config/hal: NewInputDeviceRequest failed (8) After restarting hald: (II) config/hal: Adding input device PS/2 Mouse (WW) PS/2 Mouse: No Device specified, looking for one... (II) PS/2 Mouse: Setting Device option to /dev/sysmouse (--) PS/2 Mouse: Device: /dev/sysmouse (==) PS/2 Mouse: Protocol: Auto (**) PS/2 Mouse: always reports core events (**) Option Device /dev/sysmouse (==) PS/2 Mouse: Emulate3Buttons, Emulate3Timeout: 50 (**) PS/2 Mouse: ZAxisMapping: buttons 4 and 5 (**) PS/2 Mouse: Buttons: 9 (II) XINPUT: Adding extended input device PS/2 Mouse (type: MOUSE) Interestingly, the first time Xorg tries to access the mouse, it opens /dev/psm0, and the second time after manually restarting hald, it accesses /dev/sysmouse... which is the driver that I always use in /etc/X11/xorg.conf: Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection Shouldn't Xorg use /dev/sysmouse all the time then? Why does it try to open /dev/psm0? I hope this problem will get fixed soon. ;-) Thanks for the good workaround. Regards, -cpghost. ___ 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
Re: Mouse stopped working in X
On Tue, 22 May 2012 10:17:16 +0200, Bernt Hansson wrote: There is a second way of doing this stunt. Start X When X is up and running press CTRL+ALT+F3 or any F* frpm F3 up to F8 then you get to the console Su to root in the console and type in /usr/local/etc/rc.d/dbus restart /usr/local/etc/rc.d/hald restart Then press ALT+F9 to get back to X So if that is the _solution_, why not try to automate it? Not tested, just a suggestion: Make this the last-1 line in ~/.xinitrc (or ~/.xsession depending on actual setup), before the exec call to the WM / DE, maybe like this: #!/bin/sh [ -f ~/.xmodmaprc ] xmodmap ~/.xmodmaprc xterm xsetroot -solid rgb:3b/4c/7a xset b 100 1000 15 xset r rate 250 30 xset s off xset -dpms - sudo /usr/local/etc/rc.d/dbus restart sudo /usr/local/etc/rc.d/hald restart exec wmaker It should happen when X is running, and it should be back to normal when the WM or DE is launched (and all background programs have fully started). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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
Re: Mouse stopped working in X
2012-05-22 10:44, Polytropon skrev: On Tue, 22 May 2012 10:17:16 +0200, Bernt Hansson wrote: There is a second way of doing this stunt. Start X When X is up and running press CTRL+ALT+F3 or any F* frpm F3 up to F8 then you get to the console Su to root in the console and type in /usr/local/etc/rc.d/dbus restart /usr/local/etc/rc.d/hald restart Then press ALT+F9 to get back to X So if that is the _solution_, why not try to automate it? Not tested, just a suggestion: Make this the last-1 line in ~/.xinitrc (or ~/.xsession depending on actual setup), before the exec call to the WM / DE, maybe like this: #!/bin/sh [ -f ~/.xmodmaprc ] xmodmap ~/.xmodmaprc xterm xsetroot -solid rgb:3b/4c/7a xset b 100 1000 15 xset r rate 250 30 xset s off xset -dpms - sudo /usr/local/etc/rc.d/dbus restart sudo /usr/local/etc/rc.d/hald restart exec wmaker It should happen when X is running, and it should be back to normal when the WM or DE is launched (and all background programs have fully started). We don't use sudo, only su. But I guess it work for those that use sudo. ___ 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
Re: Mouse stopped working in X
On Fri, May 18, 2012 at 2:27 PM, Bernt Hansson b...@bananmonarki.se wrote: 2012-05-18 13:49, J. W. Ballantine skrev: Hi, Before the update of x11 on 4/21/2012, X was working fine, but now when I startx, my usb and touchpad mouse are no longer found. The mouse works in terminal mode, and hald and dbus are started in /etc/rc.conf. I have exactly the same problem. What windowmanager are you using? I'm using xfce4, I have a workaround for that. 1. start X 2. when it comes up press alt+F2, the start program dialog comes up 3. type in xterm or your terminal of choice 4. in your terminal su to root then type /usr/local/etc/rc.d/dbus restart /usr/local/etc/rc.d/hald restart wait a few seconds and the mouse should work again. I have the same problem but with a ps/2 mouse. Restarting dbus and hald from within an xterm is a workable workaround. Since I'm using fluxbox, I start an xterm in ~/.xinitrc in the background to get a terminal before exec-ing fluxbox. Luckily, this xterm has already the focus. This is the relevant part of /var/log/Xorg.0.log regarding the mouse: (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 compiled for 1.7.7, module version = 1.7.1 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 7.0 (WW) PS/2 Mouse: No Device specified, looking for one... (II) PS/2 Mouse: Setting Device option to /dev/psm0 (--) PS/2 Mouse: Device: /dev/psm0 (==) PS/2 Mouse: Protocol: Auto (**) PS/2 Mouse: always reports core events (**) Option Device /dev/psm0 (EE) xf86OpenSerial: Cannot open device /dev/psm0 Device busy. (EE) PS/2 Mouse: cannot open input device (II) UnloadModule: mouse (EE) PreInit returned NULL for PS/2 Mouse (EE) config/hal: NewInputDeviceRequest failed (8) After restarting hald: (II) config/hal: Adding input device PS/2 Mouse (WW) PS/2 Mouse: No Device specified, looking for one... (II) PS/2 Mouse: Setting Device option to /dev/sysmouse (--) PS/2 Mouse: Device: /dev/sysmouse (==) PS/2 Mouse: Protocol: Auto (**) PS/2 Mouse: always reports core events (**) Option Device /dev/sysmouse (==) PS/2 Mouse: Emulate3Buttons, Emulate3Timeout: 50 (**) PS/2 Mouse: ZAxisMapping: buttons 4 and 5 (**) PS/2 Mouse: Buttons: 9 (II) XINPUT: Adding extended input device PS/2 Mouse (type: MOUSE) Interestingly, the first time Xorg tries to access the mouse, it opens /dev/psm0, and the second time after manually restarting hald, it accesses /dev/sysmouse... which is the driver that I always use in /etc/X11/xorg.conf: Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection Shouldn't Xorg use /dev/sysmouse all the time then? Why does it try to open /dev/psm0? I hope this problem will get fixed soon. ;-) Thanks for the good workaround. Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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
Mouse stopped working in X
Hi, Before the update of x11 on 4/21/2012, X was working fine, but now when I startx, my usb and touchpad mouse are no longer found. The mouse works in terminal mode, and hald and dbus are started in /etc/rc.conf. I rebuilt x11, but that had no effect, any ideas on what I might do to get the mouse working again? Here is the tail of the Xorg log. (**) Option Protocol standard (**) Option XkbRules base (**) Option XkbModel pc105 (**) Option XkbLayout us (II) XINPUT: Adding extended input device AT Keyboard (type: KEYBOARD) (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 compiled for 1.7.7, module version = 1.7.1 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 7.0 (WW) PS/2 Mouse: No Device specified, looking for one... (II) PS/2 Mouse: Setting Device option to /dev/psm0 (--) PS/2 Mouse: Device: /dev/psm0 (==) PS/2 Mouse: Protocol: Auto (**) PS/2 Mouse: always reports core events (**) Option Device /dev/psm0 (EE) xf86OpenSerial: Cannot open device /dev/psm0 Device busy. (EE) PS/2 Mouse: cannot open input device (II) UnloadModule: mouse (EE) PreInit returned NULL for PS/2 Mouse (EE) config/hal: NewInputDeviceRequest failed (8) (II) UnloadModule: kbd Thanks Jim Ballantine ___ 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
Re: Mouse stopped working in X
I'm running Gnome2 on a 9-stable system. On May 18, 2012, at 8:27 AM, Bernt Hansson wrote: 2012-05-18 13:49, J. W. Ballantine skrev: Hi, Before the update of x11 on 4/21/2012, X was working fine, but now when I startx, my usb and touchpad mouse are no longer found. The mouse works in terminal mode, and hald and dbus are started in /etc/rc.conf. I have exactly the same problem. What windowmanager are you using? I'm using xfce4, I have a workaround for that. 1. start X 2. when it comes up press alt+F2, the start program dialog comes up 3. type in xterm or your terminal of choice 4. in your terminal su to root then type /usr/local/etc/rc.d/dbus restart /usr/local/etc/rc.d/hald restart wait a few seconds and the mouse should work again. ___ 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
Re: Mouse stopped working in X
I'll try after the current build finishes, and I'll let you know what happens. Thanks On May 18, 2012, at 8:56 AM, Bernt Hansson wrote: 2012-05-18 14:45, James Ballantine skrev: I'm running Gnome2 on a 9-stable system. Can you get a terminal running in gnome, without a mouse, then I guess my workaround should work for you to. On May 18, 2012, at 8:27 AM, Bernt Hansson wrote: I have exactly the same problem. What windowmanager are you using? I'm using xfce4, I have a workaround for that. 1. start X 2. when it comes up press alt+F2, the start program dialog comes up 3. type in xterm or your terminal of choice 4. in your terminal su to root then type /usr/local/etc/rc.d/dbus restart /usr/local/etc/rc.d/hald restart wait a few seconds and the mouse should work again. ___ 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
Re: Mouse stopped working in X
On Fri, 18 May 2012, J. W. Ballantine wrote: Before the update of x11 on 4/21/2012, X was working fine, but now when I startx, my usb and touchpad mouse are no longer found. The mouse works in terminal mode, and hald and dbus are started in /etc/rc.conf. I rebuilt x11, but that had no effect, any ideas on what I might do to get the mouse working again? (EE) xf86OpenSerial: Cannot open device /dev/psm0 Device busy. (EE) PS/2 Mouse: cannot open input device (II) UnloadModule: mouse (EE) PreInit returned NULL for PS/2 Mouse (EE) config/hal: NewInputDeviceRequest failed (8) (II) UnloadModule: kbd For a test, comment out the mouse InputDevice section and the entry in the ServerLayout section. X doesn't need them. ___ 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
Re: Mouse stopped working in X
Warren, I did as you suggested and I still have the same problem Jim On May 18, 2012, at 9:14 AM, Warren Block wrote: On Fri, 18 May 2012, J. W. Ballantine wrote: Before the update of x11 on 4/21/2012, X was working fine, but now when I startx, my usb and touchpad mouse are no longer found. The mouse works in terminal mode, and hald and dbus are started in /etc/rc.conf. I rebuilt x11, but that had no effect, any ideas on what I might do to get the mouse working again? (EE) xf86OpenSerial: Cannot open device /dev/psm0 Device busy. (EE) PS/2 Mouse: cannot open input device (II) UnloadModule: mouse (EE) PreInit returned NULL for PS/2 Mouse (EE) config/hal: NewInputDeviceRequest failed (8) (II) UnloadModule: kbd For a test, comment out the mouse InputDevice section and the entry in the ServerLayout section. X doesn't need them. ___ 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
Re: Mouse stopped working in X
Bernt, I tried what you suggested, and after discovering that dbus was not installed correctly and rebuilding and reinstalling, your suggestion worked. So at least there is a work around until the real cause is found and fixed. Thanks Jim On May 18, 2012, at 8:27 AM, Bernt Hansson wrote: 2012-05-18 13:49, J. W. Ballantine skrev: Hi, Before the update of x11 on 4/21/2012, X was working fine, but now when I startx, my usb and touchpad mouse are no longer found. The mouse works in terminal mode, and hald and dbus are started in /etc/rc.conf. I have exactly the same problem. What windowmanager are you using? I'm using xfce4, I have a workaround for that. 1. start X 2. when it comes up press alt+F2, the start program dialog comes up 3. type in xterm or your terminal of choice 4. in your terminal su to root then type /usr/local/etc/rc.d/dbus restart /usr/local/etc/rc.d/hald restart wait a few seconds and the mouse should work again. ___ 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
Mouse stopped working in X
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 wheel0, 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 operator0, 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/ smime.p7s Description: S/MIME cryptographic signature
Re: Mouse stopped working in X
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 wheel0, 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 operator0, 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) ___ 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
Re: Mouse stopped working in X
--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 wheel0, 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 operator0, 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
Re: Mouse stopped working in X
Could you tell me please where the changes to the xorg.conf file which are necessitated by 7.4 are documented? Thank you. Richard On Tue, Apr 14, 2009 at 12:19 PM, Paul Schmehl pschmehl_li...@tx.rr.comwrote: --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 wheel0, 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 operator0, 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 ___ 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
Re: Mouse stopped working in X
On Tue, 14 Apr 2009 13:22:34 -0500, Richard DeLaurell richard.delaur...@gmail.com wrote: Could you tell me please where the changes to the xorg.conf file which are necessitated by 7.4 are documented? I think they are mentioned in /usr/ports/UPDATING - I haven't updated my X yet due to the trouble it seems to cause... :-) -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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
Re: Mouse stopped working in X
On Tue, 14 Apr 2009 13:22:34 -0500, Richard DeLaurell [1]richard.delaur...@gma il.com wrote: Could you tell me please where the changes to the xorg.conf file which are necessitated by 7.4 are documented? I think they are mentioned in /usr/ports/UPDATING - I haven't updated my X yet due to the trouble it seems to cause... :-) Actually I had this problem awhile ago and then it just went away. KDE4 seemed to freeze if there is no input, literally not doing anything untill I move the mouse. So I commented out that option (which I had to add to use mouse in the first place) and all started working all right. Another WTF moment. Thought there was a couple of xorg updates since the problem appeared, it might gave been fixed. References 1. mailto:richard.delaur...@gmail.com ___ 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
Re: Mouse stopped working in X
--On Tuesday, April 14, 2009 15:42:19 -0500 Eugene L. root1...@gmail.com wrote: Actually I had this problem awhile ago and then it just went away. KDE4 seemed to freeze if there is no input, literally not doing anything untill I move the mouse. So I commented out that option (which I had to add to use mouse in the first place) and all started working all right. Another WTF moment. Thought there was a couple of xorg updates since the problem appeared, it might gave been fixed. According to UPDATING the problem was fixed for most users. I guess I'm not one of them, but then radeonhd is an experimental drive anyway. -- 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
Re: Mouse stopped working in X
On Tue, 14 Apr 2009, Polytropon wrote: On Tue, 14 Apr 2009 13:22:34 -0500, Richard DeLaurell richard.delaur...@gmail.com wrote: Could you tell me please where the changes to the xorg.conf file which are necessitated by 7.4 are documented? The most recent change to xorg-server-1.6 are only in xorg.conf(5). That would be DontZap defaulting to On. Oh, and a black root window instead of black/white grid. I think they are mentioned in /usr/ports/UPDATING Not the most recent ones, and the older ones (AllowEmptyInput/AutoAddDevices are only needed sometimes. - I haven't updated my X yet due to the trouble it seems to cause... :-) Remember what Mark Twain said about cats and stoves. At present, ati/radeon should be pretty good. Intel maybe not as good, no idea about nVidia or others. Last night, I posted a sample xorg.conf here: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=91549+0+current/freebsd-x11 It may be helpful to use it as a minimal example of the way things can be configured now. Although I did forget to point out the use of hal eliminates the need for input driver declarations, so I'll do it here: That xorg.conf is set for dbus_enable=YES and hald_enable=YES in /etc/rc.conf. I also use moused_enable=YES. xorg-server can be built without hal support. If you do that to avoid needing hal, well, then you need those input device sections in xorg.conf again. -Warren Block * Rapid City, South Dakota USA ___ 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
