Bug#521083: b43-fwcutter: Lots of "b43-phy0 ERROR: PHY transmission error"

[Julien Valroff <julien@kirya.net>]

Le mercredi 25 mars 2009 à 21:16 +0100, Rene Engelhard a écrit :
> reassign 521083 linux-2.6
> retitle 521083 Lots of b43-phy0 ERROR: PHY transmission error
> forcemerge 505252 521083
> thanks
> 
> Hi,
> 
> Julien Valroff wrote:
> > Using kernel 2.6.28 and latest b43-fwcutter from Lenny, I get a lot of
> > "b43-phy0 ERROR: PHY transmission error" lines in my syslog.
> 
> And it's a probably a driver problem. Already on the kernel buglist
> as #505252....

Thanks, I haven't been able to find it. However, this report doesn't
mention the errors I see in my logs, hence *maybe* not the same issue.

> > Head of dmesg | grep b43 gives:
> > [    2.407936] b43-pci-bridge 0000:02:03.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> > [   11.363081] b43-phy0: Broadcom 4318 WLAN found
> > [   19.366913] input: b43-phy0 as /devices/virtual/input/input8
> > [   19.476093] b43 ssb0:0: firmware: requesting b43/ucode5.fw
> > [   19.550248] b43 ssb0:0: firmware: requesting b43/pcm5.fw
> > [   19.578587] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
> > [   19.604072] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
> > [   19.744094] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
> > 
> > I am quite surprised to see a firmware dated of 2007 is loaded (I have tried and run
> > again install_bcm43xx_firmware.sh very recently, just to be sure I have the right firmware installed).
> 
> That's the firmware you want to have. See the Homaepage. It says
> you want 4.150.10.5 for >= 2.6.25, and 2.6.28 is >= 2.6.25.

And I see 410.2160 in my log, how am I supposed to know that it is the
correct version?!

> Don't file bugs against s simple tool whose purpose is just to extract
> the firmware files from binary files but against the actual *driver*
> if there's a driver problem 8and that's be the kernel.). Can this be so hard?

I was refering to bug #480053 in which the exact same error was
reported, and fixed by installing another firmware.

Sorry, but I cannot understand why you react as you do. Can this be so
hard to be a bit more patient with users reporting bugs, even not
against the right package?

Cheers,
Julien