From owner-freebsd-hardware@FreeBSD.ORG Sat Mar 29 06:19:55 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 796E6106566C for ; Sat, 29 Mar 2008 06:19:55 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 3C6398FC13 for ; Sat, 29 Mar 2008 06:19:55 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id m2T6J3uE094951; Sat, 29 Mar 2008 00:19:04 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 29 Mar 2008 00:19:45 -0600 (MDT) Message-Id: <20080329.001945.-432837066.imp@bsdimp.com> To: sam@errno.com From: "M. Warner Losh" In-Reply-To: <47EBC345.8010600@errno.com> References: <47E15497.7060900@errno.com> <001101c88f2f$a98b6960$fca23c20$@muni.cz> <47EBC345.8010600@errno.com> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (AKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: hopet@ics.muni.cz, freebsd-hardware@freebsd.org Subject: Re: support for Proxim Silver wifi card X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Mar 2008 06:19:55 -0000 In message: <47EBC345.8010600@errno.com> Sam Leffler writes: : Petr Holub wrote: : >> broken with the PCCARD slot rather than the card. Can that be : >> because it's dual PCMCIA/ExpressCard slot? Any hints for further : >> debugging of the problem? : >> : > : > I've just tried the following, if it is of any help: : > : > [root@kloboucek ~]# sysctl -a | fgrep -i cardbus : > hw.cardbus.cis_debug: 0 : > hw.cardbus.debug: 0 : > dev.cbb.0.%desc: RF5C476 PCI-CardBus Bridge : > dev.cardbus.%parent: pci : > dev.cardbus.0.%desc: CardBus bus : > dev.cardbus.0.%driver: cardbus : > dev.cardbus.0.%parent: cbb0 : > [root@kloboucek ~]# sysctl -w hw.cardbus.cis_debug=1 : > hw.cardbus.cis_debug: 0 -> 1 : > [root@kloboucek ~]# sysctl -w hw.cardbus.debug=1 : > hw.cardbus.debug: 0 -> 1 : > [root@kloboucek ~]# : > cardbus0: CIS pointer is 0x5001 : > cardbus0: CIS in BAR 0x10 : > cardbus0: Expecting link target, got 0x0 : > cardbus0: Warning: Bogus CIS ignored : > ath0: mem 0xbfeb0000-0xbfebffff irq 16 at device 0.0 on : > cardbus0 : > ath0: [ITHREAD] : > ath0: unable to attach hardware; HAL status 13 : > device_attach: ath0 attach returned 6 : > : : I believe this is a cardbus issue. As I've said before I have at least : one bridge+card combo that doesn't work in HEAD because of an apparent : regression in the cardbus code. I'm not familiar enough w/ the cardbus : code to suggest where to dig but if you boot another system on the same : hard and the card is properly identified then you can sift register : settings for a clue. What does sysctl hw.cbb show? The card clearly is powering up, but we're not finding the CIS for some reason. I don't think that's fatal, and the fact that we attach the ath card means we have aren't hitting the bus issue. The fact that we see it means we're not hitting the power issue. Warner