On Thu, 2007-01-18 at 21:13 -0600, Larry Finger wrote: > Daniel Gryniewicz wrote: > > Attached. It worked fine for a while, then just disassociated. I > > assume it's the transmit power problems, but I don't know. Let me know > > if you need something else. > > I think you have the correct answer. The 4318's don't have much power output.
Probably. It's not been consistently useful, ever. > > bcm43xx driver > > bcm43xx: Chip ID 0x4318, rev 0x2 > > bcm43xx: Number of cores: 4 > > bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243 > > bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243 > > bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243 > > bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243 > > bcm43xx: PHY connected > > bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7 > > bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8) > > bcm43xx: Radio turned off > > bcm43xx: Radio turned off > > bcm43xx: PHY connected > > bcm43xx: Microcode rev 0x123, pl 0x21 (2005-01-22 19:48:06) > > bcm43xx: Radio turned on > > bcm43xx: Radio disabled by hardware > > It is a hardware button, but was off when you started. If it's hardware, why did it never do anything before? I'm curious... Was the driver overriding it somehow? > > bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: > > drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair() > > bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: > > drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair() > > bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: > > drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair() > > bcm43xx: Chip initialized > > bcm43xx: 32-bit DMA initialized > > You only need the radio patch, not the DMA one. I was the original one to report the panics with > 1G of RAM, so I definitely need something... But, no panic now, so I'm happy either way. > Thanks for the data. No problem. Thanks for your work on the driver. Any info I can give to help (aside from code; our company has NDAs with Broadcom, even if I've never seen the data sheets, so I can be considered contaminated...) will be gladly given. Daniel _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
