From owner-freebsd-current@FreeBSD.ORG Sat Mar 28 11:35:52 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 247A9106564A for ; Sat, 28 Mar 2009 11:35:52 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe12.tele2.se [212.247.155.97]) by mx1.freebsd.org (Postfix) with ESMTP id AEA828FC14 for ; Sat, 28 Mar 2009 11:35:51 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=96w21pq8z4AA:10 a=MXw7gxVQKqGXY79tIT8aFQ==:17 a=e9GxxH9P372UvzlkC0gA:9 a=MzVNTzRYKRghxnyvMwwA:7 a=6Ky5vKfIylXSPeOKZlv0ct5G7vwA:4 a=LY0hPdMaydYA:10 Received: from [62.113.132.61] (account mc467741@c2i.net HELO laptop) by mailfe12.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 1044459415; Sat, 28 Mar 2009 12:35:49 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Sat, 28 Mar 2009 12:38:19 +0100 User-Agent: KMail/1.9.7 References: <49CD4AB4.8080006@fgznet.ch> <200903272339.33763.hselasky@c2i.net> <835EFCB2-DBD3-4296-B5AC-EB6875781C78@lassitu.de> In-Reply-To: <835EFCB2-DBD3-4296-B5AC-EB6875781C78@lassitu.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200903281238.20633.hselasky@c2i.net> Cc: Andreas Tobler , Stefan Bethke Subject: Re: uhci doesn't work on VMware Fusion X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 28 Mar 2009 11:35:52 -0000 On Saturday 28 March 2009, Stefan Bethke wrote: > I've run into the same issue a couple of days ago. > > Loading uhci as a module is sufficient to trigger the messages. No > device was attached during the output below; in other tests I noticed > that uhci appears to not see any device that VMware has attached. > > This was working just fine with the old stack. Maybe it has got something to do with the new power save functionality, which maybe VMware does not support. Try: usbconfig power_on Then give a USB device to VM-ware. --HPS > > The controller appears as: > none3@pci0:2:3:0: class=0x0c0320 card=0x077015ad chip=0x077015ad > rev=0x00 hdr=0x00 > vendor = 'VMware Inc.' > class = serial bus > subclass = USB > >