Just posting my results -- seems like a value of "4" did it for me. 2 and 3 returned errors just as did "1". The only error I'm getting now is: "cbb0: Unsupported card type detected" -- but I'm guessing this has to do with the card that's in the pcmcia slot, not the bus itself(?), which is some progress. Walter Venable >From: "Walter Venable" <weaseal_at_hotmail.com> >To: avb_at_reis.zp.ua >CC: freebsd-current_at_freebsd.org >Subject: Re: cardbus activation failed. >Date: Wed, 12 May 2004 18:01:18 -0400 > >I assume this will only require a kernel rebuild, and not the whole world? >Giving it a try now, thanks. > >Walter Venable > >>From: Andrew Baurin <avb_at_reis.zp.ua> >>To: Walter Venable <weaseal_at_hotmail.com> >>Subject: Re: cardbus activation failed. >>Date: Wed, 12 May 2004 22:08:43 +0300 >> >> Hello, Walter Venable! >> >>On Wed, May 12, 2004 at 02:02:03PM -0400 >>weaseal_at_hotmail.com wrote about "cardbus activation failed.": >> > Onto the next problem arising in my -CURRENT from 5/11/2004. I >>actually >> > have had cardbus troubles since 5.2-RELEASE. Before that it didn't >>spit >> >>I solve that problems with latest patch to sys/dev/pccbb/pccbb.c from imp_at_ >>just change curr_bus_number to 2 or 3 or 4, it works for me with 2 >> >> > out any errors, however the error was only about the first 7 lines of >>this >> > current one. I am running a Dell Inspiron 8200. >> > >> > uname -a: FreeBSD walt.weaseal.com 5.2-CURRENT FreeBSD 5.2-CURRENT #0: >>Wed >> > May 12 03:47:54 EDT 2004 >> > root_at_walt.weaseal.com:/usr/obj/usr/src/sys/MYKERNEL i386 >> > >> > dmesg spits out the following error: >> > >> > bash-2.05b$ dmesg | grep cardbus >> > cardbus0: <CardBus bus> on cbb0 >> > cardbus1: <CardBus bus> on cbb1 >> > cardbus2: <CardBus bus> on cbb2 >> > cardbus0: Expecting link target, got 0xff >> > cardbus0: Resource not specified in CIS: id=10, size=200 >> > cardbus0: Resource not specified in CIS: id=14, size=100 >> > cardbus0: Resource not specified in CIS: id=18, size=400 >> > cardbus0: <network> at device 0.0 (no driver attached) >> > cardbus0: Expecting link target, got 0xff >> > cardbus0: Resource not specified in CIS: id=10, size=200 >> > cardbus0: Resource not specified in CIS: id=14, size=100 >> > cardbus0: Resource not specified in CIS: id=18, size=400 >> > cardbus0: <network> at device 0.1 (no driver attached) >> > cardbus0: Expecting link target, got 0xff >> > cardbus0: Resource not specified in CIS: id=10, size=200 >> > cardbus0: Resource not specified in CIS: id=14, size=100 >> > cardbus0: Resource not specified in CIS: id=18, size=400 >> > cardbus0: <network> at device 0.2 (no driver attached) >> > cardbus0: Expecting link target, got 0xff >> > cardbus0: Resource not specified in CIS: id=10, size=200 >> > cardbus0: Resource not specified in CIS: id=14, size=100 >> > cardbus0: Resource not specified in CIS: id=18, size=400 >> > cardbus0: <network> at device 0.3 (no driver attached) >> > cardbus0: Expecting link target, got 0xff >> > cardbus0: Resource not specified in CIS: id=10, size=200 >> > cardbus0: Resource not specified in CIS: id=14, size=100 >> > cardbus0: Resource not specified in CIS: id=18, size=400 >> > cardbus0: <network> at device 0.4 (no driver attached) >> > cardbus0: Expecting link target, got 0xff >> > cardbus0: Resource not specified in CIS: id=10, size=200 >> > cardbus0: Resource not specified in CIS: id=14, size=100 >> > cardbus0: Resource not specified in CIS: id=18, size=400 >> > cardbus0: <network> at device 0.5 (no driver attached) >> > cardbus0: Expecting link target, got 0xff >> > cardbus0: Resource not specified in CIS: id=10, size=200 >> > cardbus0: Resource not specified in CIS: id=14, size=100 >> > cardbus0: Resource not specified in CIS: id=18, size=400 >> > cardbus0: <network> at device 0.6 (no driver attached) >> > cardbus0: Expecting link target, got 0xff >> > cardbus0: Resource not specified in CIS: id=10, size=200 >> > cardbus0: Resource not specified in CIS: id=14, size=100 >> > cardbus0: Resource not specified in CIS: id=18, size=400 >> > cardbus0: <network> at device 0.7 (no driver attached) >> > >> > Has anyone else had this problem and resolved it? I'd really like to >>try >> > out ndis with my wireless card. >> > >> > Walter Venable >> > >> > _________________________________________________________________ >> > Getting married? Find tips, tools and the latest trends at MSN Life >>Events. >> > http://lifeevents.msn.com/category.aspx?cid=married >> > >> > _______________________________________________ >> > freebsd-current_at_freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-current >> > To unsubscribe, send any mail to >>"freebsd-current-unsubscribe_at_freebsd.org" >> >>-- >>AVB-RIPE > >_________________________________________________________________ >Best Restaurant Giveaway Ever! Vote for your favorites for a chance to win >$1 million! http://local.msn.com/special/giveaway.asp > >_______________________________________________ >freebsd-current_at_freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" _________________________________________________________________ FREE pop-up blocking with the new MSN Toolbar – get it now! http://toolbar.msn.com/go/onm00200415ave/direct/01/Received on Wed May 12 2004 - 14:11:44 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:53 UTC