Visite Webhosting Latino, el site sobre alojamiento web.
Help with mgetty and linux - Mombu the Programming Forum
Mombu the Programming Forum sponsored links

Go Back   Mombu the Programming Forum > Programming > Help with mgetty and linux
User Name
REGISTER NOW! Mark Forums Read

sponsored links

1 18th April 15:27
External User
Posts: 1
Default Help with mgetty and linux

Hey everyone. I need some help. I am trying 2 set up my FC4 box for
dialin with windows clients. Mgetty has the modem answers the phone but
it only connects about 5% of the time, and when it does, it doesn't
properly get past the "verifying username and password" stage. The
longest we maintained a connection for was 17 seconds according to my
ppp.log. Normally the connection is never even handed off to ppp. It
only did one time out of about 50 tries. The next time it didn't even
get that far. Could someone help me figure out what's wrong here? Here
are my config files:


port /dev/ttyS0
debug 5
speed 11520
port-owner uucp
port-group uucp
port-mode 0660
toggle-dtr YES
toggle-dtr-waittime 500
data-only YES
modem-type auto
init-chat "" ATS0=0Q0&D3&C1 OK
modem-check-time 3600
rings 2
answer-chat "" ATA CONNECT \c \r
answer-chat-timeout 80
ringback NO
ignore-carrier false
issue-file /etc/issue


/AutoPPP/ - - /usr/sbin/pppd


default, everything commented out. I don't know how 2 use this file.


# inittab This file describes how the INIT process should set up
# the system in a certain run-level.
# Author: Miquel van Smoorenburg, <>
# Modified for RHS Linux by Marc Ewing and Donnie Barnes

# Default runlevel. The runlevels used by RHS are:
# 0 - halt (Do NOT set initdefault to this)
# 1 - Single user mode
# 2 - Multiuser, without NFS (The same as 3, if you do not have
# 3 - Full multiuser mode
# 4 - unused
# 5 - X11
# 6 - reboot (Do NOT set initdefault to this)

# System initialization.

l0:0:wait:/etc/rc.d/rc 0
l1:1:wait:/etc/rc.d/rc 1
l2:2:wait:/etc/rc.d/rc 2
l3:3:wait:/etc/rc.d/rc 3
l4:4:wait:/etc/rc.d/rc 4
l5:5:wait:/etc/rc.d/rc 5
l6:6:wait:/etc/rc.d/rc 6

ca::ctrlaltdel:/sbin/shutdown -t3 -r now

# When our UPS tells us power has failed, assume we have a few minutes
# of power left. Schedule a shutdown for 2 minutes from now.
# This does, of course, assume you have powerd installed and your
# UPS connected and working correctly.
pf:owerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting

# If power was restored before the shutdown kicked in, cancel it.
pr:12345owerokwait:/sbin/shutdown -c "Power Restored; Shutdown

# Run gettys in standard runlevels
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6

S0:2345:respawn:/sbin/mgetty ttyS0 -D /dev/ttyS0

# Run xdm in runlevel 5
x:5nce:/etc/X11/prefdm -nodaemon


asyncmap 0



09/02 13:13:41 yS0 mgetty: interim release 1.1.33-Apr10
09/02 13:13:41 yS0 check for lockfiles
09/02 13:13:41 yS0 locking the line
09/02 13:13:41 yS0 lowering DTR to reset Modem
09/02 13:13:42 yS0 send: \dATQ0V1H0[0d]
09/02 13:13:42 yS0 waiting for ``OK'' ** found **
09/02 13:13:42 yS0 send: ATS0=0Q0&D3&C1[0d]
09/02 13:13:42 yS0 waiting for ``OK'' ** found **
09/02 13:13:43 yS0 waiting...
09/02 13:16:40 yS0 wfr: waiting for ``RING''
09/02 13:16:40 yS0 send: ATA[0d]
09/02 13:16:40 yS0 waiting for ``CONNECT''
09/02 13:17:08 yS0 found action string: ``NO CARRIER''
09/02 13:17:08 ##### failed A_FAIL dev=ttyS0, pid=3080, caller='none',
conn='', name=''

Any help will be greatly appreciated. Thanx!!
  Reply With Quote

  sponsored links

2 18th April 15:27
External User
Posts: 1
Default Help with mgetty and linux

In the Usenet newsgroup alt.comp.os.linux, in article

Well, the first trick would be to post to an active newsgroup. This
group sees an average of less than 3 posts a day. Your question
is on topic in 'comp.os.linux.networking'. There are several posters
there who are authoritative on the subject.

Possible problem - which version of windoze? Some of them expect
a "CLIENT" or "CLIENT/SERVER" or "SERVER" dialog. No, that shouldn't
mess the basic modem "CONNECT" dialog.

Well, I see one typo

See the modem manual - I ALWAYS recommend initializing the modem to a
known state, preferable the manufacturer's default. This means the
init string should start with AT&F0 or AT&F1. NOTE: With some modems,
the AT&Fn command clears the command buffer, which means any following
commands are lost. If your modem does that, it means sending multiple
init strings to accomplish the same goal, or writing the desired
configuration to NVRAM, and then using an appropriate ATZn command to
activate that. Do not re-write NVRAM often, as it has a finite life of write cycles.

That is the default - this isn't needed.

If I read this correctly, the port speed is APPARENTLY compatible with
the modem, and you don't have an IRQ mis-match. However the first string
doesn't appear in your setup, and still isn't setting the modem to a
known starting point. You have duplicate ATQ0, and ATH0 is quite
useless (the modem really shouldn't be off-hook by default).

To start with, have you looked at the old ISP-Setup-RedHat-HOWTO?

-rw-rw-r-- 1 gferg ldp 70695 Jan 10 2001 ISP-Setup-RedHat-HOWTO

Obviously dated, but that shows one way. There is also material in the
even older PPP-HOWTO

-rw-rw-r-- 1 gferg ldp 183087 Jul 19 2000 PPP-HOWTO

Old guy
  Reply With Quote

Thread Tools
Display Modes

Copyright 2006 - Dies Mies Jeschet Boenedoesef Douvema Enitemaus -