From owner-freebsd-current@FreeBSD.ORG Fri Mar 12 14:33:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 627DF16A54C; Fri, 12 Mar 2004 14:33:27 -0800 (PST) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D76D43D31; Fri, 12 Mar 2004 14:33:26 -0800 (PST) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id 4AD54530E; Fri, 12 Mar 2004 23:33:25 +0100 (CET) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id E444A530A; Fri, 12 Mar 2004 23:33:19 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 2602) id C325F33CA6; Fri, 12 Mar 2004 23:33:19 +0100 (CET) To: anton@nikiforov.ru References: <40522FB6.2080105@nikiforov.ru> From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) Date: Fri, 12 Mar 2004 23:33:19 +0100 In-Reply-To: <40522FB6.2080105@nikiforov.ru> (Anton Nikiforov's message of "Sat, 13 Mar 2004 00:46:30 +0300") Message-ID: User-Agent: Gnus/5.090024 (Oort Gnus v0.24) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on flood.des.no X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.63 cc: freebsd-current@freebsd.org cc: freebsd-hardware@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: Unknown hardware X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Fri, 12 Mar 2004 22:33:27 -0000 Anton Nikiforov writes: > Looks like this should be a Connexant 56K MiniPCI modem, but what > should i do to have a /dev/cuaaX and /dev/ttyX to access this modem? > pci0: at device 8.0 (no driver attached) We don't support WinModems. > This is WiFi adapter (if i'm right) it should be Boardcom 802.11b/g > MiniPCI but ath driver is not working with it. > pci0: at device 9.0 (no driver attached) You have to use the Windows driver for that one (-CURRENT has NDIS support). > I cannon understand what is this. I have uhci and ohci devices > compiled into the kernel and two usb buses (3 connectors) are working > just fine, but what is this for? > pci0: at device 11.2 (no driver attached) USB 2.0 (ehci) > And acpi that cannot correctly show battery/power status. Hrmf, I'd say try -CURRENT; if that still doesn't help, post your DSDT. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no