From owner-freebsd-newbies@FreeBSD.ORG Mon Feb 2 03:04:12 2004 Return-Path: Delivered-To: freebsd-newbies@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E321A16A4CE for ; Mon, 2 Feb 2004 03:04:12 -0800 (PST) Received: from pursued-with.net (adsl-66-125-9-242.dsl.sndg02.pacbell.net [66.125.9.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id E172943D1F for ; Mon, 2 Feb 2004 03:04:10 -0800 (PST) (envelope-from groups@pursued-with.net) Received: from [192.168.168.101] (fffinch [192.168.168.101]) by pursued-with.net (Postfix) with ESMTP id CFCAB9E05F; Mon, 2 Feb 2004 03:04:36 -0800 (PST) In-Reply-To: <200402021253180219.00DB57F4@smtp.trimail.co.za> References: <200402021253180219.00DB57F4@smtp.trimail.co.za> Mime-Version: 1.0 (Apple Message framework v612) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <8A0FC2FC-556F-11D8-B748-000A959CEE6A@pursued-with.net> Content-Transfer-Encoding: 7bit From: Kevin Stevens Date: Mon, 2 Feb 2004 03:04:15 -0800 To: antonrb@tridan.co.za X-Mailer: Apple Mail (2.612) cc: freebsd-newbies@freebsd.org Subject: Re: Modem Trouble X-BeenThere: freebsd-newbies@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Gathering place for new users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 11:04:13 -0000 On Feb 2, 2004, at 02:53, Anton Bester wrote: > I'm using a external Rockwell 56K modem on Freebsd 5.1. When starting > up, the modem is quiried by freebsd (the DT light comes on just before > the Login prompt is displayed), if I do a ps -aux it seems if the > modem is up > > ns3# ps -aux > root 476 0.0 1.4 1232 832 ?? I 11:26AM 0:00.03 /usr/libexec/getty > VH57600 ttyd0 > > but when I run cu -lttyd0 the connection just hangs > > ns3# cu -lttyd0 > Connected > > At this point I cannot do any thing and have to cancel cu out of a > different session. Ah, the joys of async communications! The most common problem that matches those symptoms is a bps mismatch - doesn't cu default to 9600? Try a command-line option to force it to 57600 (or whatever that modem definition defaults to). I don't know what you are trying to do, but your first task is to get the modem to respond to an "AT" command - getting an "OK" back confirms your communication path. There are several other things it could be, but that is the most obvious/common. Assumption is that the modem and cable are known good - if not, validate them on another machine first. > I also have the following errors in /var/log/message > > Feb 2 11:25:52 ns3 kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 > on isa0 > Feb 2 11:25:52 ns3 kernel: sio0: type 16550A > Feb 2 11:25:52 ns3 kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 > Feb 2 11:25:52 ns3 kernel: sio1: type 16550A Those aren't errors, just informational messages indicating your serial ports were detected and installed as devices. > Feb 2 11:25:52 ns3 kernel: vga0: at port 0x3c0-0x3df > iomem 0xa0000-0xbffff on isa0 > Feb 2 11:25:52 ns3 kernel: unknown: can't assign resources > (port) > Feb 2 11:25:52 ns3 kernel: unknown: can't assign resources > (port) > Feb 2 11:25:52 ns3 kernel: unknown: can't assign resources > (port) > Feb 2 11:25:52 ns3 kernel: unknown: can't assign resources > (port) > Feb 2 11:25:52 ns3 kernel: unknown: can't assign resources > (port) Those have nothing to do with your issue. KeS