Since the rest of the install went so well I am thinking this must be a case of pilot error. Using Sax2 to try to set up X I have run into a problem. When I fire up Sax2 the mouse (Intellimouse/serial) goes away completely. What has worked to recover it so far is to bail out of sax2 and restart the x server. Away from the house but thinking I'll fire up sax2 without hardware detection when I get back home. In the mean time any one else have any ideas? Allen
Le Mercredi 22 Mai 2002 16:57, ozy@landofoz.org a écrit :
Since the rest of the install went so well I am thinking this must be a case of pilot error.
Using Sax2 to try to set up X I have run into a problem. When I fire up Sax2 the mouse (Intellimouse/serial) goes away completely. What has worked to recover it so far is to bail out of sax2 and restart the x server.
Away from the house but thinking I'll fire up sax2 without hardware detection when I get back home. In the mean time any one else have any ideas?
I had the same problem with ps2 MS Intellimouse Explorer and SüSE 8.0 on two installations ! Solution for me : run SaX2 again on runlevel 3 (without X) and it was solved ! Francis
Salut Francis et Ozy. J'ai eu des problems semblables avec SaX2, depuis (au moins) SuSE 7.x, utilisant MS ou Logitech, PS/2 ou USB. Ok, I'll stop trying to speak French... sorry... :-) I find that sometimes the mouse control goes nuts without provocation, but that is relatively rare for me. More often, what causes it to happen reliably is: a) if I test a video setting that SaX2 (or X?) doesn't like, when I return from the test, the mouse is likely to be sick or b) if I "Abort", rather than using another method of escaping from a SaX2 option. Using "Next" or "Back" or whatever other choice is available does not make the mouse sick during an X configuration session, but (for me) clicking "Abort" in SaX2 is the same as selecting the "Kill Your Mouse?" button. or c) if I try to improve mouse setup beyond whatever was auto-detected... as soon as I save the settings, the mouse pointer goes nuts. It doesn't matter if I make no actual change, or if I pick an appropriate model of mouse from the available list. When I attempt to save... blooey! Not 100%, perhaps, but very frequent. Usually, I would be trying to add a fourth button, just 'cause I hate to waste the function of a perfectly good button. This occurs on several different computers (two very old ones, one modern tower, and one not-too-old laptop). So, I have learned to install SuSE and to configure X without EVER touching the detected/default mouse settings. Apparently, since you two and I are the only three people who ever had mouse-scrambling trouble with SaX2, it's not a priority to fix... (who me? sarcastic? never!) I've had the problem with MS mice and with Logitech. Probably with Kensington trackball, too, but it's been a while since I've used that one, so I may be mis-remembering. /kevin On Wednesday 22 May 2002 15:00, Francis Allouchery wrote:
Le Mercredi 22 Mai 2002 16:57, ozy@landofoz.org a écrit :
Since the rest of the install went so well I am thinking this must be a case of pilot error.
Using Sax2 to try to set up X I have run into a problem. When I fire up Sax2 the mouse (Intellimouse/serial) goes away completely. What has worked to recover it so far is to bail out of sax2 and restart the x server.
Away from the house but thinking I'll fire up sax2 without hardware detection when I get back home. In the mean time any one else have any ideas?
I had the same problem with ps2 MS Intellimouse Explorer and SüSE 8.0 on two installations !
Solution for me : run SaX2 again on runlevel 3 (without X) and it was solved !
Francis
On Thursday 23 May 2002 12:29, Kevin McLauchlan wrote:
I find that sometimes the mouse control goes nuts without provocation, but that is relatively rare for me.
It was a first for me which is the only reason I really took note of the problem. I've been using the same mouse for quite a while and sax2 since its incarnation.
I had the same problem with ps2 MS Intellimouse Explorer and SüSE 8.0 on two installations !
Solution for me : run SaX2 again on runlevel 3 (without X) and it was solved !
This works as did starting sax2 without hardware detection (# sax2 -q). Starting sax2 without hardware detection left me with a workng mouse right up intil I saved the current configuration and exited. At that point the mouse died again and a restart of X got it back. More a minor annoyance than a problem, one of those "if we get time bugs". I just wanted to confirm that I wasn't alone before submitting a report. Thanks, Allen -- Time is the best teacher. Unfortunately it kills all it's students.
On Thursday 23 May 2002 21.09, Allen Carpenter wrote:
On Thursday 23 May 2002 12:29, Kevin McLauchlan wrote:
I find that sometimes the mouse control goes nuts without provocation, but that is relatively rare for me.
It was a first for me which is the only reason I really took note of the problem. I've been using the same mouse for quite a while and sax2 since its incarnation.
I had the same problem with ps2 MS Intellimouse Explorer and SüSE 8.0 on two installations !
Starting sax2 without hardware detection left me with a workng mouse right up intil I saved the current configuration and exited. At that point the mouse died again and a restart of X got it back.
More a minor annoyance than a problem, one of those "if we get time bugs". I just wanted to confirm that I wasn't alone before submitting a report.
Try, sax2 -t imps2 The intellimouse/ps2 is not reliably auto-detected. I have always needed to use that to setup my X, until I changed to USB for the mouse. /Stefan
Bonjour; I am looking for a specimen of such a XF86Config. sax2 sees this card as a AGP. I could not use it with SuSE 7.2 and I cant with SuSE 8.0. Merci d'avance. O. L.
On Thursday 23 May 2002 15:42, Stefan Nilsen wrote:
Try,
sax2 -t imps2
The intellimouse/ps2 is not reliably auto-detected. I have always needed to use that to setup my X, until I changed to USB for the mouse.
Interesting. I'll mess around with that when I get home. Thanks. I believe I recall using USB mouse for a while, but then giving it up and returning to PS/2 because mouse control was not available until late in the loading process when it was USB connected. /kevin
participants (6)
-
Allen Carpenter -
Francis Allouchery -
Kevin McLauchlan -
ozy＠landofoz.org
-
Stefan Nilsen -
»»» Ulysses