From owner-freebsd-questions Sat Apr 8 13:55: 8 2000 Delivered-To: freebsd-questions@freebsd.org Received: from sulima.sulima.com (sulima.sulima.com [207.8.235.2]) by hub.freebsd.org (Postfix) with ESMTP id 50A8037B543 for ; Sat, 8 Apr 2000 13:54:48 -0700 (PDT) (envelope-from sulima@sulima.com) Received: from abu (abu.sulima.net [207.8.235.5]) by sulima.sulima.com (8.9.2/8.9.3) with SMTP id QAA04113; Sat, 8 Apr 2000 16:59:48 -0400 (EDT) (envelope-from sulima@sulima.com) Message-ID: <004a01bfa19c$77d856a0$05eb08cf@sulima.com> From: "Sulima Internet" To: Cc: , Subject: Dialin Service - Help Request Date: Sat, 8 Apr 2000 16:53:14 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0047_01BFA17A.EE9CD1C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0047_01BFA17A.EE9CD1C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Guys; I have been following Kelly's instruction very closely I think, to setup = com2 on FreeBSD 3.1 box to enable me to dial into the server on a = courier sportster 33.6 and or cardinal 33.6 - both are external modems = trying each at a time. It seems I have covered lots of grounds in the = past couple of weeks to get to where I am now but the problem remains it = seems "Carrier Detect" or something close to that. On either of the = modems, CD and TR are not lighting up. I had previously used both modems = on PM2 without problem. They have also been tested by dialing out into = another system. Now I want any of them to receive call(s) for me just as = they did on PM2 ...:) I have done a ps ax with these results: (1) 0:00.01 /usr/libexec/getty Pc ttyv1 (2) 0:00.01 /usr/libexec/getty Pc ttyv2 (3) 0:00.01 /usr/libexec/getty std.57600 I have no idea how "Pc ttyv1 and ttyv2" on lines 1 and 2 got in there. I = have attached /etc/gettytab and /etc/ttys files if a kind GURU can look = at these for me for possible conflict I am not able to see.. Thanks Guys .. <=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D> Sulima Internet http://www.sulima.com http://www.sulima.net Email: sulima@sulima.com ------=_NextPart_000_0047_01BFA17A.EE9CD1C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Guys;
 
I have been following Kelly's instruction very = closely I=20 think, to setup com2 on FreeBSD 3.1 box to enable me to dial into the = server on=20 a courier sportster 33.6 and or cardinal 33.6 - both are external modems = trying=20 each at a time. It seems I have covered lots of grounds in the past = couple of=20 weeks to get to where I am now but the problem remains it seems "Carrier = Detect"=20 or something close to that. On either of the modems, CD and TR are not = lighting=20 up. I had previously used both modems on PM2 without problem. They have = also=20 been tested by dialing out into another system. Now I want any of them = to=20 receive call(s) for me just as they did on PM2 ...:)
 
I have done a ps ax with these = results:
 
(1) 0:00.01 /usr/libexec/getty Pc = ttyv1
(2) 0:00.01 /usr/libexec/getty Pc = ttyv2
 
(3) 0:00.01 /usr/libexec/getty = std.57600
 
I have no idea how "Pc ttyv1 and ttyv2" on lines = 1 and 2=20 got in there. I have attached /etc/gettytab and /etc/ttys files if a = kind GURU=20 can look at these for me for possible conflict I am not able to=20 see..
 
Thanks Guys ..
 
 
<Saffa>
 
<=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= >
Sulima=20 Internet  http://www.sulima.com =20 http://www.sulima.net
Email: sulima@sulima.com
------=_NextPart_000_0047_01BFA17A.EE9CD1C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message