03-30-2001
Got It
Just to anyone who was wondering the solution:
I gave up on SAM and decided to go manual. used ioscan to find the hardware path of the modem - ioscan -C tty -fn. Then I made the relevant device files using mkfs, a separate command line for dial out and dial in device files:
# /usr/sbin/mksf -d asio0 -H <hardware path> -a1 -v
# /usr/sbin/mksf -d asio0 -H <hardware path> -a2 -v
1 and 2 states here define dial out/in status.
I then manually entered an inittab entry to respawn the uugetty process (uugetty and not getty because of dial out capacity):
a0:3:respawn:/usr/lbin/uucp/uugetty -r -t 60 -h ttyd0p7 19200M
The baud rate on the end is NOT the baud rate of the modem, but the one to be set for those dialling in - this is important if you need to set the baud and parity on your connecting client. I say parity because the next step involved creating a specific entry in /etc/gettydefs to correspond to this inittab process, and hence this modem. This was for 19200M - and all the flags that go with it (man on stty will show you) - just to note take out PARENB to disable parity checking, and set the data bits (CSx) to 8.
Once this is done run
# /etc/getty -c /etc/gettydefs | more
Then look for the entry you created and make sure it parsed without errors. ps for the getty process, and kill it. init q to reload the inittab and then kill the getty process again to make sure it respawns. Dial in, and presto, one working dial in modem, one happy manager and one tires system admin.
Spread the wealth by spreading knowledge and experience.
Regards.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I've spent enough time trying to put on work Lucent Winmodem in my armada M300 (compaq laptop) I use Mandrake 8.0 but as soon as i get connected
and prompmts appears modem shutsdown.
Does any one had a similar situation, solved it?
cheers (2 Replies)
Discussion started by: alex blanco
2 Replies
2. UNIX for Dummies Questions & Answers
Hi!
I have a little prob with dialing up to the internet... When I try connect, it says "Sorry, modem is busy"...
Specs:
Laptop
56K modem
Slackware 8.0
Kernel 2.4.5
Cheers;) (4 Replies)
Discussion started by: satan404
4 Replies
3. UNIX for Dummies Questions & Answers
Specs:
Dlink DFE-560EL external modem.
RedHat 7.1
How do you turn off the modem volume? I am getting annoyed of it beeping everytime I use it but there is no switch on the hardware to tune down the volume.
I have tried using minicom and use the following commands:
ATL0
ATM0
Next, I... (2 Replies)
Discussion started by: arz
2 Replies
4. UNIX for Dummies Questions & Answers
Pleaseee... Helpppp.... !!!
I am using SCO Open Server 5.05. Recently, i have upgraded the system which means transfer all apps and data to the new system. Everything work well except one thing. On my old system i have an external modem which to dial out. Now that i use the same modem on... (4 Replies)
Discussion started by: jackpotp
4 Replies
5. UNIX for Dummies Questions & Answers
I have got Suse 8.0 by using a modem (US Robotics 56K Faxmodem Ext).
During connection i got the error 16. I tried it under RedHat and Mandrake too.....same problem. What can i do ?
Thanx...a lot...
Logfile:
SuSE Meta pppd (smpppd), Version 0.73 on zuhause.
wwwoffle not is running ... (1 Reply)
Discussion started by: Pennywize
1 Replies
6. UNIX for Dummies Questions & Answers
Ok. I tried following the directions from some of the other threads, but I've hit a road block.
I have red hat 7.3 and I installed the hcf package:
hcfpcimodem-0.99lnxtbeta03042700k2.4.18_3-1rh.i386.rpm
It installed ok, no errors, but I still can't get linux to find my modem. I've tried... (2 Replies)
Discussion started by: lawadm1
2 Replies
7. UNIX for Dummies Questions & Answers
Im using Kinternet with a Lucent modem on Suse 9.0
Ive installed the ltmodem driver and suse says the device is ready and configured. Ive configured it at /dev/ttyS0
This is the log that Kinternet gives after trying to connect:
SuSE Meta pppd (smpppd-ifcfg), Version 1.06 on linux.
Status... (0 Replies)
Discussion started by: Synbios
0 Replies
8. Solaris
Hi all,
Is there any difference between a null modem cable or a modem cable ?
i assume that a null modem cable is a normal cable that i used from cpu serial ports to a modem for dialup.
please correct if i am wrong,
thks (2 Replies)
Discussion started by: waterbear
2 Replies
9. Solaris
hi folks,
i am looking for a analog modem to use it with a solaris9 sparc mashine. as far as i know, solaris communicates with the modem using AT-commands. so do i need a special modem for solaris or just a modem? i am open for everything. PCI-modem, seriell modem, usb modem. what are you using? i... (1 Reply)
Discussion started by: pressy
1 Replies
10. IP Networking
How to get information that where is my modem configured in /dev.
I have two modems configured in my device .. one is USB and other is PCI modem.. USB is detected as /dev/USB0. but how to see about PCI modem? (0 Replies)
Discussion started by: s123.radha
0 Replies
dial(3NSL) Networking Services Library Functions dial(3NSL)
NAME
dial, undial - establish an outgoing terminal line connection
SYNOPSIS
cc [ flag... ] file... -lnsl [ library... ]
#include <dial.h>
int dial(CALL call);
void undial(int fd);
DESCRIPTION
The dial() function returns a file-descriptor for a terminal line open for read/write. The argument to dial() is a CALL structure (defined
in the header <dial.h>).
When finished with the terminal line, the calling program must invoke undial() to release the semaphore that has been set during the allo-
cation of the terminal device.
CALL is defined in the header <dial.h> and has the following members:
struct termio *attr; /* pointer to termio attribute struct */
int baud; /* transmission data rate */
int speed; /* 212A modem: low=300, high=1200 */
char *line; /* device name for out-going line */
char *telno; /* pointer to tel-no digits string */
int modem; /* specify modem control for direct lines */
char *device; /* unused */
int dev_len; /* unused */
The CALL element speed is intended only for use with an outgoing dialed call, in which case its value should be the desired transmission
baud rate. The CALL element baud is no longer used.
If the desired terminal line is a direct line, a string pointer to its device-name should be placed in the line element in the CALL struc-
ture. Legal values for such terminal device names are kept in the Devices file. In this case, the value of the baud element should be set
to -1. This value will cause dial to determine the correct value from the <Devices> file.
The telno element is for a pointer to a character string representing the telephone number to be dialed. Such numbers may consist only of
these characters:
0-9 dial 0-9
* dail *
# dail #
------------------------------wait for secondary dial tone
- delay for
approximately 4 seconds
The CALL element modem is used to specify modem control for direct lines. This element should be non-zero if modem control is required. The
CALL element attr is a pointer to a termio structure, as defined in the header <termio.h>. A NULL value for this pointer element may be
passed to the dial function, but if such a structure is included, the elements specified in it will be set for the outgoing terminal line
before the connection is established. This setting is often important for certain attributes such as parity and baud-rate.
The CALL elements device and dev_len are no longer used. They are retained in the CALL structure for compatibility reasons.
RETURN VALUES
On failure, a negative value indicating the reason for the failure will be returned. Mnemonics for these negative indices as listed here
are defined in the header <dial.h>.
INTRPT -1 /* interrupt occurred */
D_HUNG -2 /* dialer hung (no return from write) */
NO_ANS -3 /* no answer within 10 seconds */
ILL_BD -4 /* illegal baud-rate */
A_PROB -5 /* acu problem (open() failure) */
L_PROB -6 /* line problem (open() failure) */
NO_Ldv -7 /* can't open Devices file */
DV_NT_A -8 /* requested device not available */
DV_NT_K -9 /* requested device not known */
NO_BD_A -10 /* no device available at requested baud */
NO_BD_K -11 /* no device known at requested baud */
DV_NT_E -12 /* requested speed does not match */
BAD_SYS -13 /* system not in Systems file*/
FILES
/etc/uucp/Devices
/etc/uucp/Systems
/var/spool/uucp/LCK..tty-device
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|MT-Level |Unsafe |
+-----------------------------+-----------------------------+
SEE ALSO
uucp(1C), alarm(2), read(2), write(2), attributes(5), termio(7I)
NOTES
Including the header <dial.h> automatically includes the header <termio.h>. An alarm(2) system call for 3600 seconds is made (and caught)
within the dial module for the purpose of ``touching'' the LCK.. file and constitutes the device allocation semaphore for the terminal
device. Otherwise, uucp(1C) may simply delete the LCK.. entry on its 90-minute clean-up rounds. The alarm may go off while the user program
is in a read(2) or write(2) function, causing an apparent error return. If the user program expects to be around for an hour or more, error
returns from read()s should be checked for (errno==EINTR), and the read() possibly reissued.
This interface is unsafe in multithreaded applications. Unsafe interfaces should be called only from the main thread.
SunOS 5.10 30 Dec 1996 dial(3NSL)