Re: 4.7 -> 5.0 Pccard problems (more info)

Kirill Bezzubets <[email protected]>
Newsgroups gmane.os.freebsd.devel.mobile
Message-ID <[email protected]>
On Thu, Dec 26, 2002 at 06:21:10AM -0800, Pat Lathem wrote:

> >>cbb0: <TI1410 PCI-CardBus Bridge> irq 11 at device 6.0 on pci2
> >>cardbus0: <CardBus bus> on cbb0
> >>pccard0: <16-bit PCCard bus> on cbb0
> >>   
> The card is a supported IBM 56k modem (I also have been expirementing 
> with a Linksys wireless card). The kernel does not say anything when I 
> insert or remove it (with GENERIC), which is why I assumed it was not 
> being detected properly. Since I posted the, I have reverted to the 
> kernel OLDCARD. After the computer boots, I can run 'pccardc power 0 1' 
> and it starts to initialize the card, but fails to read the correct 
> vendor string from the pccard. I'm currently changing the hints file (at 
> the advice of Greg Smith) to see if it can work. My question is this: Is 
> this is a regression? In 4.7-stable I only had to add to /etc/rc.conf 
> "pccard_enable="YES"'  and reboot (or start pccardd) to get my cards 
> working. Was I just lucky that it just worked the first time, or is 
> there a problem?

One more thing from your dmesg output (sorry, just noticed..):

cbb0: Unsupported card type detected

I guess it's a kind of bug with TI1410 (???), not sure though.
Because mine is TI1131 PCI-CardBus Bridge and everything works well
with both 16bit(PCCard) and 32bit(CardBus) cards using NEWCARD.
Also it did work in 4-STABLE since 4.3 with PCCards.

My FreeBSD is 5.0-RC1.

Are you using 5-CURRENT or 5.0-RC1? Btw, dmesg from "boot -v" could help
much more to determine what the problem is.

-- 
BR,
Kirill Bezzubets                                CASE-RIPE CASE-RIPN
Senior Administrator, Technical Department      mailto:[email protected]
Solaris ISP & Telecommunications Co. Ltd        http://www.solaris.ru

To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-mobile" in the body of the message
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.