support for Proxim Silver wifi card
Sam Leffler
sam at errno.com
Thu Mar 27 08:54:47 PDT 2008
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 at 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 at kloboucek ~]# sysctl -w hw.cardbus.cis_debug=1
> hw.cardbus.cis_debug: 0 -> 1
> [root at kloboucek ~]# sysctl -w hw.cardbus.debug=1
> hw.cardbus.debug: 0 -> 1
> [root at kloboucek ~]#
> cardbus0: CIS pointer is 0x5001
> cardbus0: CIS in BAR 0x10
> cardbus0: Expecting link target, got 0x0
> cardbus0: Warning: Bogus CIS ignored
> ath0: <Atheros 5212> 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.
Sam
More information about the freebsd-hardware
mailing list