How to configure modem in 11.31 with SMH?

[dictum9]

Have a 4640 running 11.31, would like to configure the modem connected to it.

Don't see the options in SMH.

[Torsten. · Accepted solution]

I don't think there is an option in SMH.

You need to configure manually.

Do you like MP access or OS access only?

[dictum9]

That's what I thought after looked at SMH.

I just need dial-out capability, how do I do it?

[Steven Schweda]

Would you like to configure the (unspecified)
modem, or the (unspecified) serial port where
the modem is connected?

[dictum9]

Hardware: 4640 running 11.31

The modem is: MultiTech Systems MultiModem MT2834 Series 33.6Kbps

It's connected to the DB9 serial port "remote".

I need assistance creating the device file for it and connecting to it.

[dictum9]

Trying to create the device file but not able to connect to the modem.
Did I create the device file correctly?


#: /usr/sbin/mksf -d asio0 -H 0/0/1/1 -a0 -i -v
making cua1p0 c 1 0x010000
#
a2nnmi:/var/tmp#: lssf /dev/cua1p0
asio0 card instance 1 port 0 hardwired at address 0/0/1/1 /dev/cua1p0
a2nnmi:/var/tmp#:
a2nnmi:/var/tmp#: /usr/bin/cu -s2400 -lcua1p0 dir Connect failed: Requested device/system name not known

a2nnmi:/var/tmp#: /usr/bin/cu -l cua1p0
Connect failed: Requested device/system name not known

[Steven Schweda]

> a2nnmi:/var/tmp#: /usr/bin/cu -s2400 -lcua1p0 dir
> Connect failed: Requested device/system name not known
>
> a2nnmi:/var/tmp#: /usr/bin/cu -l cua1p0
> Connect failed: Requested device/system name not known

I know nothing, but if the device name is
"/dev/cua1p0", then why not try that?

man cu

Look for "EXAMPLES"?

[dictum9]

Doesn't like it:


#: /usr/bin/cu -s 19200 -l cua1p0 Connect failed: Requested device/system name not known

#: lssf /dev/cua1p0
asio0 card instance 1 port 0 hardwired at address 0/0/1/1 /dev/cua1p0
#:

[Steven Schweda]

> I know nothing, but if the device name is
> "/dev/cua1p0", then why not try that?

> Doesn't like it:
>
> #: /usr/bin/cu -s 19200 -l cua1p0 [...]

Which part of "/dev/" wasn't clear?

> man cu
>
> Look for "EXAMPLES"?

Look again?

[dictum9]

The same thing:

#: /usr/bin/cu -s 19200 -l /dev/cua1p0 Connect failed: Requested device/system name not known

[Steven Schweda]

> The same thing:

Ok. Apparently, you need an entry in the
"Devices" file before "cu" will do anything
useful. I added a couple of lines to mine,
and things seemed to improve:

dyi # tail -4 /etc/uucp/Devices
# NOTE: blank lines and lines that begin with a , , or # are ignored
serial0 tty0p0 - 9600 direct
serial1 tty1p0 - 9600 direct

dyi #


Before:

dyi # cu -l tty1p0
Connect failed: Requested device/system name not known


After:

dyi # cu -l tty1p0
Connected
I'm typing this on another system which
is connected to this serial port.
And things I type here appear there.
[...]


So, the "/dev/" stuff isn't needed, showing
how much I don't know. (Lower bound,
anyway.) On the bright side, you can
apparently specify the (default) line speed
there, saving some "cu" command-line work
later.


It might be wise to avoid the serial port
being used for the console terminal, if
you're using a serial port for the console.


The diagnostic technique was to use "truss":

truss cu -l

which shows that it looks at that "Devices"
file, and then dies, which suggested that
that file's contents could be more important
than one might have expected.

[dictum9]

I got much farther. I modified the /etc/uucp/Devices file like this.
But the cu command now fails in this way:


Direct cul1p0 - 9600 direct
Direct cul1p1 - 9600 direct



#: /usr/bin/cu -s9600 -lcul1p0
Connect failed: line problem
#:

[Steven Schweda]

> Connect failed: line problem

Sounds like a line (cable) problem. I'm away
from my hardware at the moment, so I can't
check much. As I recall, my MultiTech modems
all had 25-pin D connectors (female, DCE),
and I'd guess that the computer's 9-pin
connector would be male and DTE, so I'd
expect some normal 9-to-25-pin adapter to be
all you'd need. (_Not_ a null modem cable.
(Or else two null modems.))

> [...] connected to it.

Not a very detailed description of the cable
being used.

I'd throw a voltmeter at the modem and the
cable you're connecting to it, and try to see
if outputs are going to inputs. You could
also try to loop TXD back to RXD (pins 2 and
3), which I'd expect to let you see what you
type.

Possibly informative:

stty -a < /dev/whatever

I wouldn't bet on it, but you could have
some exotic flow-control stuff set.