Technical article 111067

How to set up an SCO OpenServer 5.0.x modem.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6OpenServer 5.0.7

Written · Last revised

Problem

What steps do I take to set up a modem under SCO OpenServer 5.0.x?

Solution

This article describes two methods for setting up a modem under SCO OpenServer 5. While SCO recommends installing your modem through the 'Modem Manager' utility (detailed immediately below), an additional method for installation is also provided.

Modem Manager:

1. To access the Modem Manager, type the following at the command line prompt:

# scoadmin modem manager

2. Double-click on the 'System Administration' icon on the Desktop, then on 'Networks', and finally on 'Modem Manager'.

NOTE: For more information on how to configure a modem, see Chapter 24, "Adding modems," in the online documentation for SCO OpenServer, at:

http://osr5doc.xinuos.com:457/HANDBOOK/CONTENTS.html

or in the "SCO OpenServer Handbook" manual, Chapter 24, "Adding modems."

Alternative Method:
NOTE: The steps below should apply for most modem configurations.
However, there might be modems that require different initialization
strings.  Please refer to the manual for your modem for more
information regarding initialization strings.

1. Edit /usr/lib/uucp/default/<Modem_Interface_Script> and make it look like this:

MDM_SETUP=ATE1V1Q0S0=1
MDM_SPEAKER=ATL1M1
MDM_DIALCMD=ATDT
MDM_HANGUP=ATH0
MDM_QUIET=ATQ0

where "<Modem_Inteface_Script>" is the name of the interface that is used for the configuration of the modem. For example:

Standard_Modem

See your modem manual for an explanation of the 'AT' modem commands.

2. It is important that you manually create the symbolic link between:

/usr/lib/uucp/atdialer file
and
/usr/lib/uucp/<Modem_Interface_Script>
by using this command:
ln -s /usr/lib/uucp/atdialer /usr/lib/uucp/<Modem_Interface_Script>

3. Edit /etc/conf/init.d/sio (or the specific init.d file for your particular third-party driver) and change gettydef for port to 'm' as follows:

- uppercase port should say 'respawn' if the port is enabled - lowercase port should be 'off' if the port is disabled

This change should happen automatically when the ports are enabled or disabled.

After editing, the file should look like this:

Se1a:234:off:/etc/getty tty1a m
Se1A:234:respawn:/etc/getty -t60 tty1A m

After editing the /etc/conf/init.d/sio file, check the /etc/inittab file. Both files should look the same. In this example, the /etc/itittab file would look like:

Se1a:234:off:/etc/getty tty1a m
Se1A:234:respawn:/etc/getty -t60 tty1A m
If the gettydefs lines are not the same, follow step 3 again to
make the necessary changes for /etc/inittab.

4. Edit the /usr/lib/uucp/Devices file. The 'ACU' line must precede the 'Direct' line. Change the fifth field of the ACU line to '<Modem_Interface_Script>', and change both baud rates to 9600 (Direct and ACU lines). The file should look like this after editing:

.
.
.
  (more lines above)
.
.

ACU tty1A - 9600 <Modem_Interface_Script> Direct tty1a - 9600 direct

5. Disable the non-modem control port(s) and enable the modem port (uppercase). For example:

disable ttynn (non-modem port)
where "ttynn" can be tty1a.
                      ^^
       enable ttynn (modem port)
where "ttynn" can be tty1A.
                      ^^

If you are going to dial out, make sure that the serial port is owned by 'uucp' after the modem port was enabled, using this command:

cd /dev
ls -l |grep ttynn (where ttynn is your modem port like tty1A)
This should return:
crw-r-----   1 uucp     uucp       5,128 May  9 10:53 tty1A
The ownership of the device /dev/ttynn is set automatically when
the port is enabled.  The /etc/getty will check the
/usr/lib/uucp/Devices file for a dialer that is associated with
the port.  If a dialer was found, the ownership of the /dev/ttynn
is set to 'uucp:uucp'; otherwise, it will set it to 'bin:terminal'.
If you do not see the above line, check the Devices file before
you manually set the port ownership.

If you do not see the above line, use this command to manually set the ownership of the port:

chown uucp /dev/ttynn
chgrp uucp /dev/ttynn
where ttynn can be tty1A.
NOTES:    Once the modem is correctly configured, the baud rate can be
          increased as required.

To increase the baud rate, follow step 3 (changing the 'm' with the corresponding letter for a higher baud rate) and step 4 (changing the baud rate to a higher one) listed above.

See /etc/gettydefs file to change the baud rate in step 3.

Example of what the /etc/gettydefs file looks like:

m # B9600 HUPCL # B9600 CS8 SANE HUPCL TAB3 ECHOE IXANY #\r\nlogin: # m

n # B19200  HUPCL # B19200  CS8 SANE HUPCL TAB3 IXANY #\r\nlogin: # n
o # B38400  HUPCL # B38400  CS8 SANE HUPCL TAB3 IXANY #\r\nlogin: # o
p # B57600  HUPCL # B57600  CS8 SANE HUPCL TAB3 IXANY #\r\nlogin: # p
q # B115200  HUPCL # B115200  CS8 SANE HUPCL TAB3 IXANY #\r\nlogin: # q
r # B76800  HUPCL # B76800  CS8 SANE HUPCL TAB3 IXANY #\r\nlogin: # r
s # B230400  HUPCL # B230400  CS8 SANE HUPCL TAB3 IXANY #\r\nlogin: # s
t # B460800  HUPCL # B460800  CS8 SANE HUPCL TAB3 IXANY #\r\nlogin: # t
u # B921600  HUPCL # B921600  CS8 SANE HUPCL TAB3 IXANY #\r\nlogin: # u
NOTES:    In addition, any application of 'getty' that requires that DCD
          should not be dropped at startup should add the hidden -r option to
          getty arguments; this tells it not to change line modes or drop
          carrier.

See also

Manual pages: cu(C), uucp(C), atdialer(C), enable(C), disable(C), Devices(F)

ta104210, "An easy way to configure Hayes-compatible modems using Dialers file."

ta105854, "I'm getting getty errors on my modem port; how can I debug my modem initialization string? Cable configuration for modem control."

ta109301, "Using cu(C) with high speed modems on SCO OpenServer
5.0.4."

ta109341, "Screen hangs when configuring a modem in the character screen."

From the Xinuos technical article database, record 111067. Reproduced with permission. The original is at www.sco.com/ta/111067, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.