From owner-freebsd-current@FreeBSD.ORG Wed Jun 5 19:11:34 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D4CECE5; Wed, 5 Jun 2013 19:11:34 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by mx1.freebsd.org (Postfix) with ESMTP id 46DBE1BD1; Wed, 5 Jun 2013 19:11:34 +0000 (UTC) Received: by mail-we0-f180.google.com with SMTP id w56so1601204wes.39 for ; Wed, 05 Jun 2013 12:11:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=7TQ4xB/LhGoeoFsdBdM79AsrXJOSG4ES7PD6W8t03eA=; b=tBa57zvWiz6KNf5hNB2K7bj8MjWJl8Sd/t6LMeZFherg2e+cS1LSi+rGNSsqbgn3hO OMKlUKwWEh8blpGc7+JJSXFvobe1AM8wvVCLpUelcZEIQomm5QjqhVrkZEDN+uuUjjdO 8uo//bEFXPZp8iP5m8hHnSvZIklKXenWNhGHYEZ5H1dCNYQFxXGdAzfdVLc23Qx4kZvR /UMRqQjXaugVpRlUGK21HUA8IUzT9PUBSSB+czVp/R+voRsq6W4DokwdYn4o1aZpyHwO GmDB58zxSHORYw9w3fOQPP2YwmoWlbQavXKE+KgW8iGH+yaGN3uPGafI7rSAwnAoxNKr 6fiw== X-Received: by 10.194.110.133 with SMTP id ia5mr30380605wjb.35.1370459493501; Wed, 05 Jun 2013 12:11:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.24.202 with HTTP; Wed, 5 Jun 2013 12:11:13 -0700 (PDT) In-Reply-To: <20130605184545.GH1716@glenbarber.us> References: <20130605034534.GA1716@glenbarber.us> <1891799322-1370404467-cardhu_decombobulator_blackberry.rim.net-1954407922-@b2.c8.bise7.blackberry> <20130605180800.GE1716@glenbarber.us> <1083380125-1370457728-cardhu_decombobulator_blackberry.rim.net-464670310-@b2.c8.bise7.blackberry> <20130605184545.GH1716@glenbarber.us> From: Miguel Clara Date: Wed, 5 Jun 2013 20:11:13 +0100 Message-ID: Subject: Re: Memstick Images not working (mountroot prompt) To: Glen Barber Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Wed, 05 Jun 2013 19:24:44 +0000 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jun 2013 19:11:34 -0000 Done: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D179342 On Wed, Jun 5, 2013 at 7:45 PM, Glen Barber wrote: > Ok. Please open a PR as Adrian suggested, so we can properly track > this. > > Glen > > On Wed, Jun 05, 2013 at 06:42:05PM +0000, miguelmclara@gmail.com wrote: >> >> Sadly it doesn't... Just two ports in the back and in the same controlle= r. >> >> Its an Intel Panter Point controller, but I'll add that info to the PR a= s soon has my girlfriend get out of farmville and let's me use her laptop x= D >> >> Note: I also tried "sysctl hw.xhci.xhci_port_route=3D-1" and =3D1 has I = wasn't sure what would be correct but none of those helped! >> >> Thanks >> Enviado a partir do meu smartphone BlackBerry=AE www.blackberry.com >> >> -----Original Message----- >> From: Glen Barber >> Date: Wed, 5 Jun 2013 14:08:00 >> To: Miguel Clara >> Cc: >> Subject: Re: Memstick Images not working (mountroot prompt) >> >> On Wed, Jun 05, 2013 at 03:52:44PM +0100, Miguel Clara wrote: >> > Forgot to CC the list, sorry! >> > >> > In the meantime I upgrade from 9.1 using the base and kernel tarballs, >> > I could boot and I have wireless supported! >> > >> > I have my ssd encrypted and the hdd too, the hdd is encrypted with >> > passphrase + key, and this key is in a usb stick (a different one form >> > the other two already tried). >> > >> > The USB stick is not working to, and I also tried a USB Western >> > Digital 500GB disk, no luck either! >> > >> > So no usb support basically... >> > >> > dmesg output after connecting the device: >> > >> > xhci_do_comand: Command timeout! >> > usb_alloc_device: device init 2 failed (USB_ERR_TIMEOUT, ignored) >> > usbgen0.2: at usbus0 (disconnected) >> > usb_reattach_port: could not allocate new device >> > >> > >> > Also note that usbus0 is a 3.0 as dmesg shows after boot: >> > usbus0: waiting for BIOS to give up control >> > usbus0 on xhci0 >> > usbus0: 5.0Gpbs Super Speed USB v 3.0 >> > .... >> > >> > So I guess this is indeed a problem in the 10.0-current kernel, not >> > sure what it could be or what more can I do to debug though... >> > >> > Please advice, >> > >> >> Hmm. Can you please try with a USB 2.0 port on the laptop? (Hopefully >> it has at least one non-USB-3.0 port...) >> >> Glen >> >>