From owner-freebsd-usb@FreeBSD.ORG Fri May 8 03:48:16 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12A9D10656DB for ; Fri, 8 May 2009 03:48:16 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25]) by mx1.freebsd.org (Postfix) with ESMTP id B42CF8FC17 for ; Fri, 8 May 2009 03:48:15 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: by qw-out-2122.google.com with SMTP id 3so843829qwe.7 for ; Thu, 07 May 2009 20:48:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:received:received :message-id:in-reply-to:references:date:subject:from:to:user-agent :mime-version:content-type:content-transfer-encoding:x-priority :importance; bh=IQyRsJZKr/KCekACCHZahfVZpxkbPLyP5aDzYxkIEes=; b=OrhajOgJPckbpRM5xpdoFmcRAeXPjCAMYpfLPicPv5VfJ3I3cpuf4xieNM81L7L/Kr QXSZ/ZlIcngvuSHuzXO7WCAZ6LlQTHUCUccieZt//ZQG0BBo6hTSKIBkUU2sjq3wQ6Sv 1GDsZ4dWxFroI+ygakjCGhKC/pNA6sZiYABvo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:in-reply-to:references:date:subject:from:to :user-agent:mime-version:content-type:content-transfer-encoding :x-priority:importance; b=SQy9mg6zR8VoFXvWewlW2Deg3OKpqPTpl0imX3w8jRQYyXJgvgEfYUDftborr6dc1N dlbQR1UrdgvPayGCoMeT+VfpqTG6WifX96pxKHU75E0P5L+UeIuDP5zo5ef/U/i87ROH nOEjZYNvPw8iiYG6n77rEnc5hHUGLX3gy/90A= Received: by 10.224.73.140 with SMTP id q12mr3367602qaj.293.1241754495013; Thu, 07 May 2009 20:48:15 -0700 (PDT) Received: from cygnus.homeunix.com ([189.71.40.240]) by mx.google.com with ESMTPS id 26sm840075qwa.16.2009.05.07.20.48.13 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 07 May 2009 20:48:14 -0700 (PDT) Sender: Nenhum_de_Nos Received: by cygnus.homeunix.com (Postfix, from userid 80) id BFF35B8143; Fri, 8 May 2009 00:48:09 -0300 (BRT) Received: from 10.1.1.80 (SquirrelMail authenticated user matheus) by 10.1.1.10 with HTTP; Fri, 8 May 2009 00:48:09 -0300 (BRT) Message-ID: <8b7a0de5bdfb4ef4657e69559b55d7ad.squirrel@10.1.1.10> In-Reply-To: <200905080313.n483DI6M094186@lava.sentex.ca> References: <200905051740.n45HeJAG075718@lava.sentex.ca> <200905052121.n45LLvvU076825@lava.sentex.ca> <200905070948.46720.nick@van-laarhoven.org> <200905071359.n47DxsRb090275@lava.sentex.ca> <200905080313.n483DI6M094186@lava.sentex.ca> Date: Fri, 8 May 2009 00:48:09 -0300 (BRT) From: "Nenhum_de_Nos" To: freebsd-usb@freebsd.org User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: ZTE MF636 USB u3g modem X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 May 2009 03:48:16 -0000 On Fri, May 8, 2009 00:14, Mike Tancsa wrote: > At 10:01 AM 5/7/2009, Mike Tancsa wrote: > >>>This is the real port. Could you dump the descriptors after unloading >>> the >>>driver and loading ugen? > > > I decided to give it a spin on HEAD, but not sure if the recent > changes to u3g in HEAD changed the behaviour, or its an issue with me > fiddling with the driver. > > Using > http://www.draisberghof.de/usb_modeswitch/usb_modeswitch-0.9.7.tar.bz2 > > I am able to make the device appear, but as /dev/cuaU0 and not > /dev/cuaU0.0 > > > u3g0: 2.00/0.00, addr 2> on usbus3 > umass0: 2.00/0.00, addr 2> on usbus3 > umass0: SCSI over Bulk-Only; quirks = 0x0000 > Root mount waiting for: usbus3 > umass0:0:0:-1: Attached to scbus0 > Root mount waiting for: usbus3 > (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error > (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition > (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 > (probe0:umass-sim0:0:0:0): Medium not present > (probe0:umass-sim0:0:0:0): Unretryable error > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-2 device > da0: 40.000MB/s transfers > da0: Attempt to query device size failed: NOT READY, Medium not presen > > da0 is the microSD drive hi all, does u3g already lives in piece with umass ? last time I tried use 3g and umass in kernel, I got a dead system right away. if I use u3g I can't use umass for me (Huawei E226) thanks, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style