[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hpux-admin
Subject:    [HPADM] re-connecting a mouse: SUMMERY
From:       rill () telecomm ! tadiran ! co ! il
Date:       1995-06-28 16:57:18
[Download RAW message or body]

On Sun, 25 Jun 1995 I asked:
> Is there a way to replace the mouse without rebooting the workstation?
> On my WS (HP-UX A.09.05 E 9000/712) the mouse stops working when I
> disconnect it, and stay dead after re-connecting it.
> The only way to re-activate the mouse is telnet in and "shutdown -r" !

Thanks to the many people who answered:

Shaul Frenkel <shaul@orbotech.co.il> wrote:
> Well, usually, I just kill the X-server (Shift-Ctrl-Break), and then the Vue
> restart the X-server, and everything gets synchronized

Chris Marble <cmarble@osiris.ac.hmc.edu> wrote:
> Log in with no windows.  Remove and replace the mouse.
> Log out.  Vue will restart and all should be fine.
> If the mouse has been removed and all is already dead
> then Control-Shift-Reset should get you a Console prompt.
> Log in and back out again and see how it goes.
> Next try would be to telnet in and change the run state to 2
> Log in, do a telinit 3 (or 4 if that's what you use)
> and log back out.

David Skinner <dskinner@xensei.com> wrote:
> In general terms, there must be a device file that controls the 
> mouse, and a getty that spawns the device file.  Presumably, it's set up 
> in gettydefs to respawn, so simply finding and killing the process should 
> solve the problem.  If there's no process for the mouse alone, and you're 
> working directly on the console, killing the console's getty would 
> probably freeze the machine anyway, so you might be stuck.

Michael Gerdts <gerdts@cae.wisc.edu> wrote:
> It seems as though shift-ctrl-break will restart VUE and bring your mouse
> back from the dead.

Mario Obejas <mobej@atc-1s.HAC.COM> wrote:
> Try just killing the Xserver .
> Shift-Ctrl-Break. or telnet in, find the X pid, and kill that pid.

Dr. Hubert Partl <partl@hp01.boku.ac.at> wrote:
> Rebooting the X-Server (there is some special key-stroke-combination
> to do so, but I forgot which one - I no longer have a 700 but a 800).

bs@betagraphics.nl (Bertus Stuiver) wrote:
> What you could do, is logout to the VUE-login screen, replace the mouse and 
> hit the CTRL-SHIFT-BREAK combination to reset the X-server.

Raj Manohar <raj@gtetel.com> wrote:
> Disconnecting and reconnecting the mouse should NOT need a reboot and the
> system should not hang. If it does, you can restart the X server, have users
> log out (if there are any users), close all applications and instead of 
> reboot take yr system ro run level 2 and bring it back to 4 (assuminmg that
> yr X server is restarted at run level 2).

Eric M. Boehm <Eric.M.Boehm@sch.ge.com> wrote:
> You need to restart the X server. You could try SHIFT-CTRL-RESET (HIL
> keyboards) or SHIFT-CTRL-PAUSE (AT Keyboards [i.e., 9000/712]). If that
> doesn't work, you need to telnet in and restart the server (either by
> killing vuelogin or by changing run-levels, e.g., telinit 2; telinit 4).
> You should see evidence of the mouse problem in /usr/vue/config/Xerrors.

Bruce Warrington <bruce@ancc.com> wrote:
> Restart X.  Telnet in, and kill the existing X client.  Upon restart,
> it usually re-reads the keyboard and mouse.  If it's only the mouse,
> and the mouse is the last thing in the HIL chain, try using
> <CTRL><Shift><Reset> to restart X.  This may be the easiest solution.

Mike Peterson <system@alchemy.chem.utoronto.ca> wrote:
> Make changes like this in a "No Windows" login (not VUE), and I think
> you'll find that it all works again when VUE starts again after you
> logout. The same things happen when you add/remove the HIL codeword
> module or the keyboard in a VUE session.

Andy Condliffe <andy_condliffe@studio.disney.com> wrote:
> You can normally get round this by just resetting the X 
> server (CNTRL-SHIFT-RESET).


Dion M. Sagez <boatmens!dion@uustar.starnet.net> wrote:
> I am assuming you are running some sort of X windowing gui.
> You could try restarting the X server.  We do this by holding down
> CTRL+SHIFT+Reset, or  CTRL+ALT+DEL, or telnet in and kill X.

Sean Reifschneider <sreifsc@sreifsc.uswc.uswest.com> wrote:
> Well, other than the obvious (not unplugging the mouse), I have found that
> I can unplug the mouse and connect a different one without problems
> as long as I'm not in X windows.  I was able to exit X then swap mice
> and restart X without problems.
> 
> I'm guessing that since you said you could only telnet in that you're
> also disconnecting your keyboard.  They keyboards don't tend to work
> after you've disconnected them.  The solution I've found is ... don't
> do that.


,_____.   ,_.  ,_.     ,_.           Y u v a l     O f e r
| ,--. \  | |  | |     | |        ___________________________  
| |__/ /  | |  | !__.  | !__.    <rill@telecomm.tadiran.co.il>
!_!  \_\  !_!  !____!  !____!    Rill: a small stream ("yuval")  
_________ diameter = 2.0 * radius; /* almost everywere */ _____



--
             ---> Please post QUESTIONS and SUMMARIES only!! <---
        To subscribe/unsubscribe to this list, contact majordomo@cv.ruu.nl
  Name: hpux-admin@cv.ruu.nl                 Owner: owner-hpux-admin@cv.ruu.nl
 Archive: (FTP, browse only):     ftp.cv.ruu.nl/pub/digests/hpux-admin 
          (Web, browse & search): http://hpux.ced.tudelft.nl/HPUX_ADMIN_ARCHIVE

[prev in list] [next in list] [prev in thread] [next in thread]