*BSD News Article 32054


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!sol.ctr.columbia.edu!newsxfer.itd.umich.edu!zip.eecs.umich.edu!panix!not-for-mail
From: wpaul@panix.com (Bill Paul)
Newsgroups: comp.os.386bsd.questions
Subject: Re: getty Not working?
Date: 25 Jun 1994 21:22:16 -0400
Organization: The M00se Illuminati (bl00p!)
Lines: 75
Message-ID: <2uil88$idr@panix3.panix.com>
References: <2ui2nd$io@panix.com>
NNTP-Posting-Host: panix3.panix.com
X-Newsreader: TIN [version 1.2 PL2]

Daring to challenge the will of the almighty Leviam00se, 
Walter Polkosnik (banana@panix.com) had the courage to say:
: I've tried to set up my second serial port to accept a direct terminal
: (another PC). I edited my /etc/ttys to turn on getty for tty01, but
: there's never any response on the terminal. I've played with settings in
: gettytab and on the PC I'm using as a terminal, but nothing seems to help.

You don't say what OS you're using. I'm using FreeBSD 1.1 with a
terminal on tty02 (well, ttyd2 really... whatever).

Uhm... let's see here... quick rundown of steps:

1) Edit /etc/ttys and label the proper port as "on." You said you did
   that, so that's fine.

2) As root, type "kill -1 1" so that init actually spawns the getty
   process. You say later on that you have problems with SLIP when
   getty is running on tty01, so I'll take it for granted that you
   did this too and that a getty process is actually spawned.

3) A fundamental thing that a surprising number of people overlook:
   make sure you use a null modem when connecting the two machines
   together. If you don't have a null modem, all bets are off. :)

4) On the terminal side, use /dev/cua0? instead of /dev/tty0? to
   connect to the other computer. This isn't strictly necessary but
   it's the Right Thing to do.

I'm taking it as a given that both computers are trying to talk to
each other at the same baud rate.

: Also, it seem that when I have getty running on tty01, my slip on tty00
: hangs up the line more often than usual (very often).

This sounds like an IRQ conflict. (It could be line noise too, though.)
Some possibilities:

- You're using an internal modem on tty00 for your SLIP connection
  and it's set up to use the same IRQ as tty01. tty00 should be using
  IRQ4 and tty01 should be using IRQ3. Get out your modem's manual
  and check that this is the case.

- You're using an internal modem on tty00 and you didn't disable
  one of your computer's built-in serial ports that's configured
  for the same address. Turn off any existing serial port that
  might be set to the same I/O address as the modem.

- You're using an external modem and your serial ports are
  misconfigured. Refer to your computer's hardware manual (if
  these are built-in serial ports) or you I/O adapter's manual
  (if they're not built-in) and make sure they're using unique
  I/O addresses and IRQs, and that those settings match what your
  kernel expects them to be.

- The phase of the moon is wrong. Stick another pin in your Bill Gates
  doll and sacrifice an extra SIMM module to the computer gods. (If
  you're having trouble contacting the computer gods, you can pass the
  SIMM along to me and I'll make sure that they get it. Honest. ;)


Hope this helps.

: -- 
: Walter Polkosnik          banana@panix.com               

Hey, another Panix user! Damn, we're everywhere.

-Bill
--
 _      /\      _            Join the
/ \_/\_/  \_/\_/ \  .----.   M00se Illuminati   Bill Paul 
\_____/ () \_____/ (bl00p!)  Face it: wouldn't  <Big City M00se>
     /      \       `----'   you feel much      wpaul@panix.com   -or-
    /  \__/  \    --'        safer?             ghod@drycas.club.cc.cmu.edu
   /__________\