On Sunday 25 January 2009 13:19:45 Michael Buesch wrote: > On Sunday 25 January 2009 04:45:20 Larry Finger wrote: > > Francesco Gringoli wrote: > > > > > > could you please be so kind to try the opensource firmware on that > > > 4311/2 card by renaming it ucode13 and report what happens? I suggest to > > > try monitor mode without associating first. > > > > I had already tried it in managed mode. The logged data are > > > > Jan 23 13:37:09 larrylap kernel: b43-phy0: Loading OpenSource firmware > > version 351.11970 > > Jan 23 13:37:09 larrylap kernel: b43-phy0 warning: You are using an > > old firmware image. Support for old firmware will be removed soon > > (official deadline was July 2008). > > Jan 23 13:37:09 larrylap kernel: b43-phy0 warning: You must go to > > http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and > > download the correct firmware for this driver version. Please > > carefully read all instructions on this website. > > Jan 23 13:37:09 larrylap kernel: b43-phy0 debug: Chip initialized > > Jan 23 13:37:09 larrylap kernel: b43-phy0 debug: 64-bit DMA initialized > > Jan 23 13:37:09 larrylap kernel: Registered led device: b43-phy0::tx > > Jan 23 13:37:09 larrylap kernel: Registered led device: b43-phy0::rx > > Jan 23 13:37:09 larrylap kernel: Registered led device: b43-phy0::radio > > Jan 23 13:37:09 larrylap kernel: b43-phy0 debug: Wireless interface > > started > > Jan 23 13:37:09 larrylap kernel: b43-phy0: Controller restarted > > Jan 23 13:37:25 larrylap kernel: b43-phy0 ERROR: MAC suspend failed > > Jan 23 13:37:29 larrylap kernel: b43-phy0 ERROR: MAC suspend failed > > Jan 23 13:37:30 larrylap kernel: b43-phy0 ERROR: MAC suspend failed > > Jan 23 13:37:30 larrylap kernel: b43-phy0 ERROR: MAC suspend failed > > Jan 23 13:37:30 larrylap kernel: b43-phy0 ERROR: MAC suspend failed > > Jan 23 13:37:31 larrylap kernel: b43-phy0 ERROR: MAC suspend failed > > Jan 23 13:37:31 larrylap kernel: b43-phy0 ERROR: MAC suspend failed > > Jan 23 13:37:31 larrylap kernel: b43-phy0 ERROR: MAC suspend failed > > Jan 23 13:37:32 larrylap kernel: b43-phy0 ERROR: MAC suspend failed > > Jan 23 13:37:32 larrylap kernel: b43-phy0 ERROR: MAC suspend failed > > Jan 23 13:37:40 larrylap kernel: b43-phy0 ERROR: Firmware watchdog: > > The firmware died! > > Jan 23 13:37:40 larrylap kernel: b43-phy0: Controller RESET (Firmware > > watchdog) ... > > Jan 23 13:37:41 larrylap kernel: b43-phy0 ERROR: MAC suspend failed > > Jan 23 13:37:41 larrylap kernel: b43-phy0 debug: Wireless interface > > stopped > > Jan 23 13:37:41 larrylap kernel: b43-phy0 debug: DMA-64 rx_ring: Used > > slots 0/64, Failed frames 0/0 = 0.0%, Average tries 0.00 > > Jan 23 13:37:41 larrylap kernel: b43-phy0 debug: DMA-64 tx_ring_AC_BK: > > Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00 > > Jan 23 13:37:41 larrylap kernel: b43-phy0 debug: DMA-64 tx_ring_AC_BE: > > Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00 > > Jan 23 13:37:41 larrylap kernel: b43-phy0 debug: DMA-64 tx_ring_AC_VI: > > Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00 > > Jan 23 13:37:41 larrylap kernel: b43-phy0 debug: DMA-64 tx_ring_AC_VO: > > Used slots 22/128, Failed frames 0/0 = 0.0%, Average tries 0.00 > > Jan 23 13:37:41 larrylap kernel: b43-phy0 debug: DMA-64 tx_ring_mcast: > > Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00 > > > > I haven't gotten to monitor mode yet, but if the firmware cannot > > suspend the MAC, I'm not optimistic. > > Well, there's a reason broadcom does different firmwares for different cores. > ;) > It turns out even rev9 runs with its own firmware now. I think that used to > run rev5 > firmware in the past.
Btw, I guess you know you guys know about the b43-fwdump utility found in b43-tools/debug. It provides a kernel-oops-like firmware register (and SHM) dump and a (pseudo-)backtrace for the current program counter of the firmware. It requires the b43 debugfs interface to be available. Very nice to debug this kind of "what the hell is happening" errors, as you can see what code the firmware does currently execute. For the pseudo-backtrace you must provide the .fw file to the b43-fwdump tool. (see b43-fwdump --help) -- Greetings, Michael. _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
