Very Computer

by **I.R** » Thu, 04 Mar 1999 04:00:00

Hello,

I'd like to know if there's a FAQ/docu available that can help me configure
my /dev/ttyS1 for the use with chat and pppd.

I am currently using an "upgraded" RedHat4.2 with linux-2.2.2 kernel.
Surprisingly /dev/cua1 is no longer supported (results in some "Network down"
message, when you try it anyway).

One symptom is that, e.g. 'stty ispeed 115200 < /dev/ttyS1' or
'chat "" ATZ OK ATDT$NUMBER ... < /dev/ttyS1 > /dev/ttyS1' won't return.

I.R.

by **Villy Kru** » Fri, 05 Mar 1999 04:00:00

>Hello,

>I'd like to know if there's a FAQ/docu available that can help me configure
>my /dev/ttyS1 for the use with chat and pppd.

>I am currently using an "upgraded" RedHat4.2 with linux-2.2.2 kernel.
>Surprisingly /dev/cua1 is no longer supported (results in some "Network down"
>message, when you try it anyway).

>One symptom is that, e.g. 'stty ispeed 115200 < /dev/ttyS1' or
>'chat "" ATZ OK ATDT$NUMBER ... < /dev/ttyS1 > /dev/ttyS1' won't return.

Some of these utilities might not work for ttySx devices, but current
versions does. Try an upgraded chat utility. Probably should upgrade
everything to RH5.2 level, as the current chat also requires glibc,
which requires an upgraded ......

The stty command won't return until carrier is present from the modem,
and that is the expected behaviour from most unix versions as well.

Villy

by **I.R** » Fri, 05 Mar 1999 04:00:00

[...]

Quote:>Some of these utilities might not work for ttySx devices, but current
>versions does. Try an upgraded chat utility. Probably should upgrade
>everything to RH5.2 level, as the current chat also requires glibc,
>which requires an upgraded ......

Thanks, I will try that.

Quote:>The stty command won't return until carrier is present from the modem,
>and that is the expected behaviour from most unix versions as well.

Well all right, but that can't be the whole story. stty works perfectly with
my modem on cua1 (i.e. it returns). I always thought cua1 and ttyS1 show the
same behaviour. setserial -a says they are equally configured.

I.R.

by **Villy Kru** » Fri, 05 Mar 1999 04:00:00

>Well all right, but that can't be the whole story. stty works perfectly with
>my modem on cua1 (i.e. it returns). I always thought cua1 and ttyS1 show the
>same behaviour. setserial -a says they are equally configured.

That is because when you open the cua device before carrier is present and
the device is not otherwise busy, then the open will succeed. With ttyS
the open will suspend until carrier is present, unless you do a non-blocking
open. Dialer programs like chat must be programmed to do excactly that; or
they won't work.

If cua and ttyS showed the same behaviour, there would not have been any
reason to make a separate cua device in the first place.

If you have the mgetty package you might try to take a look at the
following file: (redhat 5.2)

/usr/doc/mgetty-1.1.14/ttyS-cua.txt

Villy

by **Doug DeJul** » Fri, 05 Mar 1999 04:00:00

>Well all right, but that can't be the whole story. stty works perfectly with
>my modem on cua1 (i.e. it returns). I always thought cua1 and ttyS1 show the
>same behaviour. setserial -a says they are equally configured.

The cua and ttyS ports have never shown the same behavior. The ttyS
port is POSIX compatible, and the cua one is not -- the differences
are basically for compatability with very old software that was
written before POSIX.
--

HKS, Incorporated | http://www.hks.net/~ddj/

Very Computer

/dev/ttyS1, /dev/cua1 and linux-2.2.2

/dev/ttyS1, /dev/cua1 and linux-2.2.2

/dev/ttyS1, /dev/cua1 and linux-2.2.2

/dev/ttyS1, /dev/cua1 and linux-2.2.2

/dev/ttyS1, /dev/cua1 and linux-2.2.2

/dev/ttyS1, /dev/cua1 and linux-2.2.2