From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 4 19:00:27 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 748B5B93 for ; Tue, 4 Dec 2012 19:00:27 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 4F2968FC18 for ; Tue, 4 Dec 2012 19:00:27 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 7A7345081A for ; Tue, 4 Dec 2012 11:00:20 -0800 (PST) To: freebsd-hardware@freebsd.org Subject: VIA VL8xx USB 3.0 controller supported? Date: Tue, 04 Dec 2012 11:00:20 -0800 Message-ID: <66805.1354647620@tristatelogic.com> From: "Ronald F. Guilmette" X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Dec 2012 19:00:27 -0000 I just recently purchased one of these: http://www.ianker.com/anker-uspeed-use-3.0-pci-express-card/product/68UPPCIE-2S20PU Given that the ads for it say that it is 100% compatible with the Intel xHCI specification, I kind-of had some hope that it would just work with FreeBSD... if not older versions then at least with the 9.1-RC3 install that I happen to have on one system here at the moment. Alas, as far as I can tall, the presence of the thing in the system in question is not even noticed by the kernel. There are no startup dmesg messages that seem to even vaguely relate to the thing. It's like it just isn't physically there. So what gives? Are these VIA VL8xx controllers supported by/in FreeBSD or not? And while we are on the subject, how come most other man pages for most other drivers for "controller" type things actually do list the specific hardware controllers that they are known to work with, and yet _none_ of the USB-related driver man pages (xhci(4), ehci(4), ohci(4), uhci(4)) apparently bother to do this? Regards, rfg P.S. It is of course possible that I just simply got a bad card. I'll be plugging in into a Windows system I have here soon to try to be sure about that, one way or the other. P.P.S. Oddly, ArchLinux (LiveCD) didn't appear to see the thing either.