From owner-freebsd-questions@FreeBSD.ORG Mon Dec 7 13:17:14 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1756C106566C; Mon, 7 Dec 2009 13:17:14 +0000 (UTC) (envelope-from 482254ac@razorfever.net) Received: from ironport2-out.pppoe.ca (ironport2-out.teksavvy.com [206.248.154.183]) by mx1.freebsd.org (Postfix) with ESMTP id B35768FC12; Mon, 7 Dec 2009 13:17:13 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmkJAJ6PHEtMCrCL/2dsb2JhbACBSxqXL758hDMEih4 X-IronPort-AV: E=Sophos;i="4.47,355,1257138000"; d="scan'208";a="50892827" Received: from 76-10-176-139.dsl.teksavvy.com (HELO server.razorfever.net) ([76.10.176.139]) by ironport2-out.pppoe.ca with ESMTP/TLS/DHE-RSA-AES256-SHA; 07 Dec 2009 08:17:08 -0500 Received: from [192.168.0.197] ([192.168.0.197]) by server.razorfever.net (8.13.8/8.13.8) with ESMTP id nB7DDVVd047142; Mon, 7 Dec 2009 08:13:33 -0500 (EST) (envelope-from 482254ac@razorfever.net) Message-ID: <4B1D0054.4060406@razorfever.net> Date: Mon, 07 Dec 2009 08:17:08 -0500 From: "Derek (freebsd lists)" <482254ac@razorfever.net> User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Ian Smith References: <20091128113000.BBDF410656E6@hub.freebsd.org> <20091205212857.H34611@sola.nimnet.asn.au> In-Reply-To: <20091205212857.H34611@sola.nimnet.asn.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.95.2 at server.razorfever.net X-Virus-Status: Clean Cc: freebsd-questions@freebsd.org, Randi Harper Subject: Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Dec 2009 13:17:14 -0000 Ian Smith wrote: > Very long story short: googled for ages and found a forum thread about > this very problem, in which someone suggested Options / Rescan Devices > then trying again. The OP there said it didn't work for him, but it > sure did for me! > > Options / Rescan Devices fixed it for me. Maybe it will for Derek > and/or maybe provide another clue? Indeed this works for me. I've added a follow-up to the PR. Thanks for the tip! - Derek