Good doc on this. Including pin outs, uucp devices etc.
---------------------------
Cannot CU out to the modem
The following is a list of responses the system may give other than
Connected when you enter cu -ml tty1 on the command line.
NOTE: We will use tty1 and a baud of 9600 for our examples in this text.
Type the following from the command line:
cu -ml tty1
(Response should read "CONNECTED"
The message Connection Closed -m flag not valid may occur on
OS levels below 3.2.5. The -m flag tells the system to ignore
missing CD and open the port. Lower OS levels do not have
the -m flag option so we will need to use the Dialers file to send
the modem the set up string of at commands.
1.Open /etc/uucp/Dialers in vi or any other file editor.
Go to the bottom of the file and enter this line on a new line by itself:
set^^=,-,^^^"" at&c1&d2q1s0=1&w ""
(the "^" represent spaces)
Save the file.
2.Open /etc/uucp/Devices in vi or any other file editor.
Rather than a Direct line entry for the tty, enter the following on its own line:
ACU tty1 - 9600 set
Comment out all other tty entries by putting a pound sign at the front of each line.
3.Save the file.
4.Run the following command:
cu -d 123
This will produce on-line debugging and you can see the steps of the
cu command on the screen. The command will find the line ACU tty1 - 9600
set in the Devices file. Then it will go to the Dialers file and find the set
chat script we entered. You will see on the screen a series of expect,
gotit, send them lines. It then sends the at string to the modem
and then hangs because the script was not programmed to dial
the bogus phone number 123.
5.In the cu session to get back to the command prompt, type the
following command:
~[tilde].[period]
The modem has now been programmed. Edit /etc/uucp/Devices file
and restore to original condition.
The "cu -ml tty1" command returns "No Devices Available"
The cu command response should be No Devices Available. This means
the /etc/uucp/Devices file either does not contain the
line, Direct tty1 - 9600 direct or the line is there, but it has a
typo in it. The line must be exactly as follows:
Direct tty1 - 9600 direct
^ ^ ^ ^
(the "^" represent spaces)
If the line appears correct, there may be some non-printable typos in it.
Delete the line and then add it again as previously
outlined by typing:
The "cu -ml tty1" command returns "Cannot Access Device" or "Device Locked"
The response will be Cannot Access Device or Device Locked. This means
some other process has control of the tty. To find
out what the process is, type from the command line:
ps -ef | grep tty1
If the process is a getty, run pdisable tty1.
If it is determined that the process should not be running,
kill the process.
NOTE: Some processes must not be stopped with the -9 option
(i.e. slattach), take the appropriate steps to kill the process
and free the port.
In the case of slattach for example you would first run:
ifconfig sl(x) detach
kill # (# is process id of slattach)
If no process is returned except the grep itself, the port is hung and
must be cleared.
The "cu -ml tty1" command returns "CU" not found
The response from the system should be cu not found This indicates a missing uucp file set.
Run the following command:
lslpp -h *uucp*
If the system responds and the uucp fileset is not found on the system. Install the file set.
For a 3.2 system install 'bosext1.uucp.obj'.
For a 4.x system install 'bos.net.uucp'.
For a 5.x system install 'bos.net.uucp'.
After the installation of the fileset, return to normal mode to set up procedure.
