>My systems administrator has just hooked up a modem to the serial port of an
>HP 9000. When he enables the port thru /etc/inittab he constantly receives
>'getty responding too fast' from the system. When he lowers the baud rate
>in /etc/inittab things work slightly better, but the system refuses to
>respond to any incoming calls.
You probably mean 'getty respawning too fast'. This means that getty gives
up on the modem line, a new getty is started by init, does the same etc. Init
notices this and after a while it stops the offending process to save system
resources. Check the following:
- The modem is configured to follow DTR and DCD follows carrier
(Hayes: AT &C1 &D3)
- The modem cable is correct (flow control, DTR, DCD etc). This can be
troublesome on some HP systems.
- You use the right port. For dialin. I _though_ it was something like
(for example) /dev/ttyd2p0, while the dialout port (physically the same)
is /dev/cua2p0. This is all from memory, though :)
- Modem echo is off. (Hayes: AT E0). Otherwise login gets caught in a loop.
- Save modem settings in non volatile ram (hayes: at&w).
> The modem does answer/connect.
> You can connect from the system to the modem and send commands (AT).
> When a terminal is connected to the port, no login is ever received.
This may sound amateuristic, but it isn't. Get the serial FAQ for Linux, or
any other FAQ that mentions connecting a modem to your system for dial in.
The method of doing this is almost the same, if not identical. It might
solve your problems. (ftp to rtfm.mit.edu).
| Miquel van Smoorenburg | "I know one million ways, to always pick |