From: duty@ariel.ucs.unimelb.edu.au (Duty Programmer) Subject: Re: X video problems - More info with pre-0.96 cf 0.96 !! Date: 22 May 1992 04:23:39 GMT
In article <1992May20.195602.1444@gdk.b17a.ingr.com>, ramesh@guru.b17a.ingr.COM (V. Ramesh Sharma) writes:
|> In article <2419@ariel.its.unimelb.EDU.AU>, duty@ariel.ucs.unimelb.edu.au (Duty Programmer) writes:
|> I did the same thing and timings.exe doesn't seem to help either.
|>
|> |> The only other information I have is that X seems to be hanging. It doesn't
|> |> seem to respond to Cntrl-Alt-+ or Cntrl-Alt-Backspace. I can't ^C
|>
|> Ditto for me, too.
OK, Now that I have been assured that the DMODE clocks are the correct ones
(although I'm still not sure if I sure use integral values or not ...), I
have rerun TIMINGS.EXE and put all the values in.
This immediately stopped my screen going haywire, but X386 just seemed to lock
up without changing video mode at all. No error messages. I can still login
by another VT. At this stage, I tried booting on pre-0.96 rather than 0.96.
Same thing, but NOW I get an error message from X386!!! It says:
"expecting horizontal scan" or something like that, so there seems to be
a syntax error in my Xconfig file... but I have teh resolution, the clock,
and the 8 timings - it looks just like the supplied file in format... what's
going on ???
|>
|> There seems to be the view that your screen could be messed up not
|> only because of the video settings but it could be due to
|> a) the kind of mouse being used (logitech or Microsoft). In this
Is this really true ? That an incorrect MOUSE entry can screw up your
display ? Doesn't seem to make sense to me...
|> regard, some people seem to be using
|>
|> Logitech "/dev/tty65"
|> or
|> Logitech "/dev/ttys2"
|> or
|> Logitech "/dev/mouse"
|> or .........
|>
|> Which is the right one, or is it immaterial? How does one find out?
|> On the other hand everyone seems to use "/dev/ttys2" for a Microsoft
|> mouse, can someone pl. explain?
tty65 was the old name for the serial port. ttys2 should be used for port 2.
I presume /dev/mouse refers to a bus mouse driver (advertised on the net a few
days ago). i.e. If you have a serial mouse in COM2, use ttys2.
rab
-- ======================================================================== Richard Brown | E-mail: rab@tauon.ph.unimelb.EDU.AU School of Physics | Phone : +61 3 344 5081 University of Melbourne | Fax : +61 3 347 4783 Parkville Victoria AUSTRALIA 3052 | Telex : AA35185