Jacob (Mettavihari)
On Tue, 20 Apr 1999, Ray Olszewski wrote:
> To check your setup, go through the basics (I'm sure you have already done
> much of this, but look through the list just to see if anything slipped your
> mind):
> 1. Verify (using ps -ax) that uugetty is actually running and watching ttyS1.
I found the file mgetty and set that in inittab,
but it would not come up when rebooting.
When I mannually install it with the command
/sbin/mgetty /dev/modem -s 38400 vt100
then it get up and ps -ax finds it.
and I am able to login at 19200
My string in inittab is as below
s1:45:respawn:/sbin/mgetty 38400 /dev/modem /etc/ppp/conf.mgetty.ttyS1
vt100
> 2. Verify that the modem is connected to ttyS1.
There is a link in /dev/modem pointing to cua1
but not pointing to ttyS1
> 3. Verify that, prior to CONNECT, the modem and the serial port are running
> at the same speed. (Otherwise, uugetty will never see the RING message as
> line noise.) Since the modem is a 28.8, I doubt its default speed is 19.2 --
> 38.4 is more likely. (This is a consideration for after you connect as well.
> Try changing F19200 to F38400 in the inittab entry.)
I have now managed to connect manually with mgetty and with the speed set
to 19200 or 38400 I get the same result "connect speed 19200"
> 4. You checked modem operation through minicom. Check minicom to see what
> modem init string it sends, and change your conf.uugetty.ttyS1 script to
> send the same init string.
I shall do that next
but it seems to be at the level of inittab that I have a problem
> But my real advice is to change from this system to one that sets the modem
> to auto answer, rather than using a server process to watch for a RING
> message. I know this can be done with agetty or mgetty;
If we get mgetty to do the work that should be ok with me.
This is my full inittab file
===========================
#
# inittab This file describes how the INIT process should set up
# the system in a certain run-level.
#
# Author: Miquel van Smoorenburg, <[EMAIL PROTECTED]>
# 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 networking)
# 3 - Full multiuser mode
# 4 - unused
# 5 - X11
# 6 - reboot (Do NOT set initdefault to this)
#
id:3:initdefault:
# System initialization.
si::sysinit:/etc/rc.d/rc.sysinit
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
# Things to run in every runlevel.
ud::once:/sbin/update
# Trap CTRL-ALT-DELETE
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::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down"
# If power was restored before the shutdown kicked in, cancel it.
pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled"
s1:456:respawn:/sbin/mgetty /dec/modem /etc/ppp/conf.mgetty.ttyS1 vt100
# Run gettys in standard runlevels
1:12345: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
# Run xdm in runlevel 5
x:5:respawn:/usr/bin/X11/xdm -nodaemon
