modem not responding to mgetty
malcolm.kay at internode.on.net
Tue Jan 4 20:28:07 PST 2005
On Wed, 5 Jan 2005 04:27 am, Timothy Luoma wrote:
> I have been attempting to setup mgetty (installed from ports) to allow
> me to dial IN to my FreeBSD 5.3 machine.
> $ mgetty -V
> mgetty+sendfax by Gert Doering
> experimental test release 1.1.31-Jul24
> log file written to '/var/log/mgetty.<ttyX>'
> config file read from '/usr/local/etc/mgetty+sendfax/mgetty.config'
> (FWIW, the modem works under WinXP for dialing *out*. XP reports it as:
> "PCI Slot 2 PCI Bus 1, Device 1, function 0" on "COM3")
> FreeBSD seems to see it:
> $ dmesg|grep "^sio"
> sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
> sio0: type 16550A
> (it is /dev/cuaa0 on FreeBSD)
This looks like the standard serial port known as COM1 in windows.
(cuua0 is for outgoing connections -- incoming would normally be on ttyd0)
You probably want cuua2 or ttyd2 and may need to do something with the
device.hints file to get these to appear.
> However, it will not respond to calls. Checking the mgetty log, I see
> 01/04 12:46:55 aa0 mgetty: experimental test release 1.1.31-Jul24
> 01/04 12:46:55 aa0 check for lockfiles
> 01/04 12:46:55 aa0 locking the line
> 01/04 12:46:56 aa0 WARNING: DSR is off - modem turned off or bad cable?
> 01/04 12:46:56 aa0 lowering DTR to reset Modem
> 01/04 12:46:57 aa0 send: ATS0=0Q0&D3&C1[0d]
> 01/04 12:46:57 aa0 waiting for ``OK''
> 01/04 12:47:17 aa0 timeout in chat script, waiting for `OK'
> 01/04 12:47:17 aa0 init chat timed out, trying force-init-chat
> 01/04 12:47:17 aa0 send: \d\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
> 01/04 12:47:21 aa0 waiting for ``OK''
> 01/04 12:47:41 aa0 timeout in chat script, waiting for `OK'
> 01/04 12:47:41 aa0 init chat failed, exiting...: Interrupted system
> 01/04 12:47:41 ##### failed in mg_init_data, dev=cuaa0, pid=6780
Certainly appears that mgetty is not looking at the modem port but an ordinary
I don't believe you should need mgetty for basic modem login -- getty should work.
Set ttyd2 to "on" in /etc/ttys.
However listen to what others have to say -- I don't claim to be expert in this area
-- especially not with the new features of 5.x
More information about the freebsd-questions