Results of dmesg: $ dmesg | grep bcm bcm43xx driver bcm43xx: Chip ID 0x4311, rev 0x2 bcm43xx: Number of cores: 4 bcm43xx: Core 0: ID 0x800, rev 0x13, vendor 0x4243 bcm43xx: Core 1: ID 0x812, rev 0xd, vendor 0x4243 bcm43xx: Unsupported 80211 core revision 13 bcm43xx: Core 2: ID 0x817, rev 0x4, vendor 0x4243 bcm43xx: Core 3: ID 0x820, rev 0x5, vendor 0x4243 bcm43xx: PHY connected bcm43xx: Detected PHY: Analog: 4, Type 2, Revision 9 bcm43xx: Invalid PHY Revision 9 bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) bcm43xx: Radio turned off bcm43xx: Radio turned off bcm43xx: PHY connected bcm43xx: Microcode rev 0x127, pl 0xe (2005-04-18 02:36:27) bcm43xx: Radio turned on bcm43xx: Radio enabled by hardware bcm43xx: Chip initialized bcm43xx: 64-bit DMA initialized bcm43xx: Keys cleared bcm43xx: Selected 802.11 core (phytype 2) bcm43xx: FATAL ERROR: BCM43xx_IRQ_XMIT_ERROR bcm43xx: MAC suspend failed bcm43xx: MAC suspend failed
did you need any further? Gary On 9/22/07, Larry Finger <[EMAIL PROTECTED]> wrote: > > Gmail Collector wrote: > > Howdy, > > > > Just joined a few minutes ago and was wondering if there was a search > > mechanism on the archives that I may have missed. I would like to find > > out more about an error of "bcm43xx: FATAL ERROR: > > BCM43xx_IRQ_XMIT_ERROR" in my dmesg output. I am unable to locate a > > method to search the bodies of the messages, and could find no matches > > in the subjects. > > I don't know about searching the archives, but that error usually means a > problem with the firmware. > Has this interface worked in the past, or are you just getting started? > > Please post the results of 'dmesg | grep bcm'. > > Larry >
_______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
