From owner-freebsd-mobile@FreeBSD.ORG Sat Nov 5 13:50:21 2005 Return-Path: X-Original-To: freebsd-mobile@freebsd.org Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 724DF16A41F for ; Sat, 5 Nov 2005 13:50:21 +0000 (GMT) (envelope-from rehsack@liwing.de) Received: from moby.liwing.de (www.liwing.de [82.97.68.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FFD843D6D for ; Sat, 5 Nov 2005 13:50:15 +0000 (GMT) (envelope-from rehsack@liwing.de) Received: from [80.64.176.27] (helo=[10.62.10.4]) by moby.liwing.de with esmtp (Exim 4.52 (FreeBSD)) id 1EYOUz-000LSM-L4; Sat, 05 Nov 2005 13:54:25 +0000 Message-ID: <436CBAB6.6050406@liwing.de> Date: Sat, 05 Nov 2005 13:59:18 +0000 From: Jens Rehsack User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050819) X-Accept-Language: en-us, en MIME-Version: 1.0 To: guru@Sisis.de References: <20051105080405.GA2814@rebelion.Sisis.de> In-Reply-To: <20051105080405.GA2814@rebelion.Sisis.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Cc: "Rehsack Jens \(ext\)" , freebsd-mobile@freebsd.org Subject: Re: Help getting Option N.V. Fusion UMTS Quad-GPRS run X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 13:50:21 -0000 guru@Sisis.de wrote: > El d=EDa Friday, November 04, 2005 a las 05:43:03PM +0100, Rehsack Jens= (ext) escribi=F3: >=20 > ... >=20 >>I tried using minicom set the Pin and it always return "ERROR", >>even if I tried to request whether the Pin is enabled or not. >=20 > the Option N.V. Fusion card has the problem that you can't set > the PIN twice with at+cpin=3D"xxxxxxx" (as noted in my config file); I know, but it even didn't work first time ... Neither getting the pin request status worked. >>Maybe it's a hardware-defect on the pin-card... >=20 > I don't think so; I hope you're right. I double check the pppd.conf you submitted and try i= t out. >>On monday I get a windows-pc and we will check whether it works there >>or not. But maybe someone sees the error ... before that ;-) >=20 > the ppp.log you provided shows that you are subscribed to the > network (ie. the card has got the PIN successfully) and there is > somehow a PPP negotiating problem, no IP addr is negotiated > before you interrupted the PPP proc; that's all; Yeah, but in the 2min's it had every chance to do that ^^ I'm not sure (no idea) why it wont worked ... Jens