Nick Holland kirjoitti viestissddn (ldhetysaika maanantai, 13. huhtikuuta 2009
02:59:47):
> Aapo Lehtinen wrote:
> > Hello
> >
> > I'm trying to get Sun Fire V100 working using old ultra 1 machine
> > (obsd4.4/sparc64) as terminal. I'm using tip(1). The problem is
> > connection dies easily with "Lost Carrier. [EOT]". Now, I'm bit new to
> > using serial connections so I've only tried tweaking /etc/ttys by
> > changing type from sun to vt100, and comments from local to rtscts to
> > softcar.
>
> It is unclear what machine you are changing, but changing /etc/ttys is
> definitely wrong.  Restore them to stock before doing ANYTHING else.
> All you are doing here is breaking things.  You do not need to change any
> files to get a tip(1) session going with a Sun machine.
>
> If you are getting a "lost carrier" response, you need to look at the
> machine you are getting that from -- i.e., your terminal machine.
>
> What command are you using to try to establish the connection?
>
> Nick.

I've used 'tip -9600 ttya' and 'cu -l ttya', both have the same effect. If I
log into ALOM/OpenBoot I can tweak settings for 10-20 secods before hangup.
Connection stays up during diagnostics etc. (i.e lots of output)

So there is some setting I should set up that prevents connection dying when
there is no output, I suppose.

Aapo

Reply via email to