Scott Mitchell wrote: > On Sat, Apr 10, 2004 at 05:57:35PM +0100, Pete Carss wrote: > >>Scott Mitchell wrote: >> >>>On Sat, Apr 10, 2004 at 03:19:22PM +0100, Pete Carss wrote: >>> >>>Can you boot with hw.pccard.debug=1 and hw.pccard.cis_debug=1 (you'll need >>>to break into the loader at boot time and set them there) and send me the >>>resulting output (should end up in /var/run/dmesg.boot)? >> >>I think I've done what you asked....at the kernel prompt I "set" the >>hw... values....here's the result: > > > Hi Pete, > > That was exactly what I asked for, but not exactly what I wanted to see... > Could you try booting again without the Aironet card plugged in, then: > # sysctl hw.xe.debug=2 > and plug in the Aironet? You should get a lot of new debug output from the > xe driver that will hopefully tell us why it thinks it owns this card. > Apologies for not asking for everything the first time around. > > Cheers, > > Scott > This is what I got - note I assumed you meant not to set the two variables I set previously?? ******************** xe0: pccard_match xe0: pccard_product_match xe0: <Cisco Systems 340 Series Wireless LAN Adapter> at port 0x100-0x13f irq 10 function 0 config 5 on pccard1 xe0: pccard_probe xe0: vendor = 0x015f xe0: product = 0x0007 xe0: prodext = 0x00 xe0: vendor_str = Cisco Systems xe0: product_str = 340 Series Wireless LAN Adapter xe0: cis3_str = (null) xe0: cis4_str = (null) device_probe_and_attach: xe0 attach returned 19 ********************Received on Sat Apr 10 2004 - 12:47:57 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:50 UTC