Very Computer

I have downloaded the 0.96 release from tsx, and have the 0.95a release
of the rootimage. Also, x386 from banjo.

After the usual iterations of fixing the /dev/tty0 problem, I am stuck
right now at the screen displaying wierd lines and patterns. Then I
have to do a reset and start all over again! Sigh....

My configuration is 486/33 , w/ 512k cache,
                    16 Meg ram,
                    60Meg partition for Linux
                    STB Powergraph ERGO w/ 1Meg
                    Mitsubishi Diamond Scan Monitor
                    Dexxa 3 button Mouse (Logitech compatible I
                                                   presume? :-) )

From the vga.dbase I was thrilled to find the info for the video card,
but no luck with the Monitor. I tried using the Tutorial to come up
with some numbers and no luck...

Finally, I switched to a Nanao Flexscan 9070U monitor AND a Microsoft
mouse (to eliminate any problems with the Logitech mice people have
mentioned, (which reminds me - WHERE can I find stty????? )). Still NO
LUCK!!! What am I doing wrong???? I could reproduce the Xconfig
settings I have for the vga 256 section if needed. I do have the
"Vendor hiclock" setting. The rest is as per the database....

Can some kind soul guide me here?

Thanx in advance!

Ramesh "so close yet so far" Sharma

P.S. But for the X problem, everything works great! Thanx a billion
Linus and Co....
--
..............................................................................
Local  : 104D, Bldg 17A               Ma Bell  : 205 730 7194(W) 464 0806(H)
USNail : Intergraph Corp.,MS IW17A3   Fax      : 205 730 7296
         One Madison Industrial Park  UUCP     : uunet!ingr!b17a!guru!ramesh

..............................................................................

|> After the usual iterations of fixing the /dev/tty0 problem, I am stuck
|> right now at the screen displaying wierd lines and patterns. Then I
|> have to do a reset and start all over again! Sigh....

I posted yesterday with the same problem. Only one reply so far, but
I also downloaded timings.zip from archsci.arch.su.oz.au and ran the
timings program, which is supposed to generate the monitor part of the
Xconfig file. *Sigh* - nothing seems to work: all I get is a completely
unsync-ed mess. I've used the clocks that X386 gives me, and the (factor
of 2 higher) ones from DMODE.

The only other information I have is that X seems to be*. It doesn't
seem to respond to Cntrl-Alt-+ or Cntrl-Alt-Backspace. I can't ^C out. However,
I *can* log in on another VT and do things (pity I can't see anything meaningful
on the screen), but nothing very useful (apart from sync!). But at least linux
is still up! If I redirect errors, all I seem to get is "interrupted system call",
which is probably from the ^C sequences I am trying to kill it with. If I don't
do that, I don't get any output (not surprisingly) after the reboot.

HELP!

rab
--
------------------------------------------------------------------------

School of Physics                 | Phone : +61 3 344 5081
University of Melbourne           | Fax   : +61 3 347 4783
Parkville Victoria AUSTRALIA 3052 | Telex : AA35185

: |> After the usual iterations of fixing the /dev/tty0 problem, I am stuck
: |> right now at the screen displaying wierd lines and patterns. Then I
: |> have to do a reset and start all over again! Sigh....
:
: I posted yesterday with the same problem. Only one reply so far, but
: I also downloaded timings.zip from archsci.arch.su.oz.au and ran the
: timings program, which is supposed to generate the monitor part of the
: Xconfig file. *Sigh* - nothing seems to work: all I get is a completely
: unsync-ed mess. I've used the clocks that X386 gives me, and the (factor
: of 2 higher) ones from DMODE.
:
: The only other information I have is that X seems to be*. It doesn't
: seem to respond to Cntrl-Alt-+ or Cntrl-Alt-Backspace. I can't ^C out. However,
If this is the case, then X very likely isn't running. :)

try doing 'startx >& xout' and then logging in the other term, syncing,
and rebooting. Then see what is in the file.

: I *can* log in on another VT and do things (pity I can't see anything
: meaningful
: on the screen), but nothing very useful (apart from sync!). But at
: least linux
: is still up! If I redirect errors, all I seem to get is
: "interrupted system call",
: which is probably from the ^C sequences I am trying to kill it with.
: If I don't
: do that, I don't get any output (not surprisingly) after the reboot.
:
: HELP!
:
: rab

|> try doing 'startx >& xout' and then logging in the other term, syncing,
|> and rebooting. Then see what is in the file.
|>

I did that. If I don't ^C to X, then I don't get any output. If I ^C, then I
get "Interrupted system call". Not very useful. I think something is*
before the server can come up properly. Unfortunately, my ps no longer works
with 0.96, and after installing gcc 2.11b yesterday, I can no longer compile
things! (See my other posting).

HELP!! HELP!!

rab
--
------------------------------------------------------------------------

School of Physics                 | Phone : +61 3 344 5081
University of Melbourne           | Fax   : +61 3 347 4783
Parkville Victoria AUSTRALIA 3052 | Telex : AA35185

|> |> After the usual iterations of fixing the /dev/tty0 problem, I am stuck
|> |> right now at the screen displaying wierd lines and patterns. Then I
|> |> have to do a reset and start all over again! Sigh....
|>
|> I posted yesterday with the same problem. Only one reply so far, but
|> I also downloaded timings.zip from archsci.arch.su.oz.au and ran the
|> timings program, which is supposed to generate the monitor part of the
|> Xconfig file. *Sigh* - nothing seems to work: all I get is a
|> completely

I did the same thing and timings.exe doesn't seem to help either.

[chomp...chomp]

|> The only other information I have is that X seems to be*. It doesn't
|> seem to respond to Cntrl-Alt-+ or Cntrl-Alt-Backspace. I can't ^C

Ditto for me, too.

|> out. However, I *can* log in on another VT and do things (pity I
|> can't see anything meaningful on the screen), but nothing very
|> useful (apart from sync!). But at least linux is still up! If I

In my case, however, linux seems to be dead, i.e., I can't switch to
another virtual console either. How else to find out??

[chomp...chomp]

|>
|> HELP!
|>

Me Too! Does anybody out in netland using Linux have a Mitsubishi
Diamond Scan Monitor, AND a working X386??? Pl. help! ;-) (This is
assuming that the info for the STB Powergraph ERGO graphics card in
the vga.dbase is correct...) It is really so frustrating to be unable
to run X when there are so many others running it successfully....

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
   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?

b) fontpaths not set correctly

Any other reasons for the continued problems??

|> rab
|> --

Thanx in advance!

Ramesh "aaaaaaaaarrrrrgggghhhhhh" Sharma
--
..............................................................................
Local  : 104D, Bldg 17A               Ma Bell  : 205 730 7194(W) 464 0806(H)
USNail : Intergraph Corp.,MS IW17A3   Fax      : 205 730 7296
         One Madison Industrial Park  UUCP     : uunet!ingr!b17a!guru!ramesh

..............................................................................

Yep, I've got a 5 year old DiamondScan that works fine (or rather, the screen
works fine, but my Logitech mouse still has a mind of its own). I'm using the
800x600 VESA settings from the vga database (for the monitor) and the
Prodesigner II 800x600 (virtual 1024x1024) settings for my ProII.
I got it to work on the first try! Now if I could just get my mouse to
be reasonable. (I've got a C7) I'll try again tonight...

+-=-=-=-=-=-=-=-=-=-=-=-+-=-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
| Rob McNamara          | Happy! Happy! |  Lankhmar BBS                     |

| LBL EE CAD/CAE        |               |  1200/2400/9600/14.4k HST/v.32bis |
+-=-=-=-=-=-=-=-=-=-=-=-+-=-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+

|> 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*. 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*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
--
------------------------------------------------------------------------

School of Physics                 | Phone : +61 3 344 5081
University of Melbourne           | Fax   : +61 3 347 4783
Parkville Victoria AUSTRALIA 3052 | Telex : AA35185

From what I could tell trying to get X running, it is not the kind of mouse
being used but that there must be a valid (i.e. existing) device specified.
In the second example above, /dev/ttys2 must be a valid entry in /dev and
there must be a serial port associated with the device.  X does not seem
to mind if there is no mouse or any other object connected to the port,
just that the port functions correctly.

As to which one to use, you need to specify the device to which your
mouse is connected.  I believe that /dev/mouse is used for the logitec
bus mouse (when apropriate kernel patches to support it are applied) and
/dev/ttys2 and /dev/tty65 are both names that people use for the second com
port.  I don't know what the major/minor numbers for com ports are off
of the top of my head.

One other note:  I was not able to get a stable screen display until I
trimmed the virtual size of the screen to be the same as the physical
size (i.e. 640 x 480 or 800 x 600).  This was for an Orchid ProDesigner
card, ET3000 chipset.

Mark

I have an STB powergraph, (I don't think its an ERGO), and a 16" diamond scan
monitor.  I finally got a stable X picture last night.  I got my timings from
the timings program.  Yoou have to make sure that you feed timings a mode
number that corresponds to a mode with the same resolution as the one you
want.  If you want I can mail you what I ended up with.  My numbers are at home
though.  Feel free to email with questions, I'll try to help.
Cntrl-Alt-+ and - hand my system to (actually, crash it).   I did get a
mousesystems mouse working though.

|> |> |> After the usual iterations of fixing the /dev/tty0 problem, I am stuck
|> |> |> right now at the screen displaying wierd lines and patterns. Then I
|> |> |> have to do a reset and start all over again! Sigh....
|> |>
|> |> I posted yesterday with the same problem. Only one reply so far, but
|> |> I also downloaded timings.zip from archsci.arch.su.oz.au and ran the
|> |> timings program, which is supposed to generate the monitor part of the
|> |> Xconfig file. *Sigh* - nothing seems to work: all I get is a
|> |> completely
|>
|> I did the same thing and timings.exe doesn't seem to help either.
|>
|> [chomp...chomp]
|>
|>
|> |> The only other information I have is that X seems to be*. It doesn't
|> |> seem to respond to Cntrl-Alt-+ or Cntrl-Alt-Backspace. I can't ^C
|>
|> Ditto for me, too.
|>
|> |> out. However, I *can* log in on another VT and do things (pity I
|> |> can't see anything meaningful on the screen), but nothing very
|> |> useful (apart from sync!). But at least linux is still up! If I
|>
|> In my case, however, linux seems to be dead, i.e., I can't switch to
|> another virtual console either. How else to find out??
|>
|> [chomp...chomp]
|>
|> |>
|> |> HELP!
|> |>
|>
|> Me Too! Does anybody out in netland using Linux have a Mitsubishi
|> Diamond Scan Monitor, AND a working X386??? Pl. help! ;-) (This is
|> assuming that the info for the STB Powergraph ERGO graphics card in
|> the vga.dbase is correct...) It is really so frustrating to be unable
|> to run X when there are so many others running it successfully....
|>
|> 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
|>    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?
|>
|> b) fontpaths not set correctly
|>
|> Any other reasons for the continued problems??
|>
|> |> rab
|> |> --
|>
|> Thanx in advance!
|>
|> Ramesh "aaaaaaaaarrrrrgggghhhhhh" Sharma
|> --
|> ..............................................................................
|> Local  : 104D, Bldg 17A                 Ma Bell  : 205 730 7194(W) 464 0806(H)
|> USNail : Intergraph Corp.,MS IW17A3   Fax      : 205 730 7296
|>            One Madison Industrial Park  UUCP     : uunet!ingr!b17a!guru!ramesh

|> ..............................................................................
|>
|>
|>

--

My views, thoughts, opinions and spelling errors are definitely my own!