HELP!!!

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

well, where is the problem in your log file? The part that you have shown
shows two modem initializations, with an *outgoing* call in between.

So how should anybody read from this file that *incoming* calls don't work?

- anyway: if the modems do not connect ("NO CARRIER" instead of "CONNECT")
this might just be a generic "my modem doesn't like your modem" problem.
Zoom modems are not known for "high quality", more for "low price".

gert

edward.principe@sbaonline.gov wrote:
> 
> I can't fit the address to confirm I want to be on the mailing address
> in my mailer. So, I'm stuck.
> 
> Another thing is I don't have the file called BUGS. I just have info and
> man pages. I got mgetty on a CD-ROM with RedHat Linux, and I looked thru
> the packages and there are just man and info pages documenting mgetty.
> 
> Here's whats going on. I tested out mgetty by having someone call me.
> It'll pick up the phone and try to connect. It sounds like it's doing
> ok, and I get a real low tone, and it doesn't seam to be doing anything.
> 
> She is using Windows 3.1. probbally, or possibly DOS. She has a 14k
> modem (not quite sure what kind it is).
> 
> I'm using a 33.6k Zoom Modem. It's model # is 2805. I guese it's just a
> generic Zoom modem.
> 
> Here's my log:
> 
> --
> 10/29 01:05:55 yS3 mgetty: experimental test release 1.1.5-Apr16
> 10/29 01:05:55 yS3 check for lockfiles
> 10/29 01:05:55 yS3 checklock: stat failed, no file
> 10/29 01:05:55 yS3 locking the line
> 10/29 01:05:55 yS3 makelock(ttyS3) called
> 10/29 01:05:55 yS3 do_makelock: lock='/var/lock/LCK..ttyS3'
> 10/29 01:05:55 yS3 lock made
> 10/29 01:05:56 yS3 tio_get_rs232_lines: status: RTS CTS DSR DTR DCD
> 10/29 01:05:56 yS3 WARNING: DCD line still active, check modem settings (AT&Dx
> 10/29 01:05:56 yS3 lowering DTR to reset Modem
> 10/29 01:05:56 yS3 tss: set speed to 38400 (017)
> 10/29 01:05:56 yS3 tio_set_flow_control( HARD )
> 10/29 01:05:56 yS3 waiting for line to clear (VTIME), read:
> 10/29 01:05:56 yS3 send: ATE1Q0V1[0d]
> 10/29 01:05:56 yS3 waiting for ``OK''
> 10/29 01:05:56 yS3 got: ATE1Q0V1[0d][0d][0a]OK ** found **
> 10/29 01:05:56 yS3 send: AT&FS0=0&C1&D2W1[0d]
> 10/29 01:05:56 yS3 waiting for ``OK''
> 10/29 01:05:56 yS3 got: [0d][0a]AT&FS0=0&C1&D2W1[0d][0d][0a]OK ** found **
> 10/29 01:05:56 yS3 waiting for line to clear (VTIME), read: [0d][0a]
> 10/29 01:05:57 yS3 removing lock file
> 10/29 01:05:57 yS3 waiting...
> 10/29 01:59:31 yS3 checking lockfiles, locking the line
> 10/29 01:59:31 yS3 makelock(ttyS3) called
> 10/29 01:59:31 yS3 do_makelock: lock='/var/lock/LCK..ttyS3'
> 10/29 01:59:31 yS3 lock not made: lock file exists (pid=505)
> 10/29 01:59:31 yS3 lock file exists (dialout)!
> 10/29 01:59:31 yS3 lockfile found, pid=505
> 10/29 01:59:31 yS3 utmp + wtmp entry made
> 10/29 01:59:31 yS3 lockfile found, pid=505
> 10/29 01:59:41 yS3 lockfile found, pid=505
> 10/29 01:59:51 yS3 lockfile found, pid=505
> 10/29 02:00:01 yS3 lockfile found, pid=505
> 10/29 02:00:11 yS3 lockfile found, pid=505
> 10/29 02:00:21 yS3 lockfile found, pid=505
> 10/29 02:00:31 yS3 lockfile found, pid=505
> 10/29 02:00:41 yS3 lockfile found, pid=505
> 10/29 02:00:51 yS3 lockfile found, pid=505
> 10/29 02:01:01 yS3 lockfile found, pid=505
> 10/29 02:01:11 yS3 lockfile found, pid=505
> 10/29 02:01:21 yS3 checklock: stat failed, no file
> 10/29 02:01:26 yS3 checklock: stat failed, no file
> --
> 10/29 02:01:26 yS3 mgetty: experimental test release 1.1.5-Apr16
> 10/29 02:01:26 yS3 check for lockfiles
> 10/29 02:01:26 yS3 checklock: stat failed, no file
> 10/29 02:01:26 yS3 locking the line
> 10/29 02:01:26 yS3 makelock(ttyS3) called
> 10/29 02:01:26 yS3 do_makelock: lock='/var/lock/LCK..ttyS3'
> 10/29 02:01:26 yS3 lock made
> 10/29 02:01:27 yS3 tio_get_rs232_lines: status: RTS CTS DSR DTR DCD
> 10/29 02:01:27 yS3 WARNING: DCD line still active, check modem settings (AT&Dx
> 10/29 02:01:27 yS3 lowering DTR to reset Modem
> 10/29 02:01:27 yS3 tss: set speed to 38400 (017)
> 10/29 02:01:27 yS3 tio_set_flow_control( HARD )
> 10/29 02:01:27 yS3 waiting for line to clear (VTIME), read:
> 10/29 02:01:28 yS3 send: ATE1Q0V1[0d]
> 10/29 02:01:28 yS3 waiting for ``OK''
> 10/29 02:01:28 yS3 got: ATE1Q0V1[0d][0d][0a]OK ** found **
> 10/29 02:01:28 yS3 send: AT&FS0=0&C1&D2W1[0d]
> 10/29 02:01:28 yS3 waiting for ``OK''
> 10/29 02:01:28 yS3 got: [0d][0a]AT&FS0=0&C1&D2W1[0d][0d][0a]OK ** found **
> 10/29 02:01:28 yS3 waiting for line to clear (VTIME), read: [0d][0a]
> 10/29 02:01:28 yS3 removing lock file
> 10/29 02:01:28 yS3 waiting...
> 10/29 02:09:04 ##### failed dev=ttyS3, pid=514, got signal 15, exiting
> 
> I get the warning about the DCD line being active, after I use minicom
> usually.
> 
> - Eddie
> 
> 
> 


-- 
USENET is *not* the non-clickable part of WWW!
           //www.muc.de/~gert/
Gert Doering - Munich, Germany      gert@greenie.muc.de
fax: +49-89-3545980     gert.doering@physik.tu-muenchen.de
.