b43 (H/W 4306 Rev. 03)

b43 (H/W 4306 Rev. 03)

[Ahmed Ammar]

As per my talk with st3 #bcm-users I have decided you e-mail you with
the details of my problem. I have this card:

02:07.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
Wireless LAN Controller (rev 03)

And whatever I do I can not get it to associate, I have tried with and
without encryption and below are two pastes of dmesg with and without
hwcrypto. I am not alone in this I have other people who have the same
problem and have to use this patch to get the card working on
b43legacy instead (http://url2cut.com?pwI)

no hwcrypto:
ACPI: PCI interrupt for device 0000:02:07.0 disabled
ACPI: PCI Interrupt 0000:02:07.0[A] -> Link [APC4] -> GSI 19 (level,
low) -> IRQ 19
ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x04, vendor 0x4243)
ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x05, vendor 0x4243)
ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x02, vendor 0x4243)
ssb: Core 3 found: V90 (cc 0x807, rev 0x02, vendor 0x4243)
ssb: Core 4 found: PCI (cc 0x804, rev 0x09, vendor 0x4243)
ssb: SPROM revision 1 detected.
ssb: Sonics Silicon Backplane found on PCI device 0000:02:07.0
b43-phy4: Broadcom 4306 WLAN found
b43-phy4 debug: Found PHY: Analog 2, Type 2, Revision 2
b43-phy4 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
phy4: Selected rate control algorithm 'pid'
Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ]
Broadcom 43xx driver loaded [ Features: PLID, Firmware-ID: FW10 ]
bonding: bond0: Adding slave wlan0.
b43-phy4: Loading firmware version 410.2160 (2007-05-26 15:32:10)
b43-phy4 debug: Chip initialized
b43-phy4 debug: 30-bit DMA initialized
Registered led device: b43-phy4::tx
Registered led device: b43-phy4::rx
b43-phy4 debug: Wireless interface started
b43-phy4 debug: Adding Interface type 2
bonding: bond0: enslaving wlan0 as an active interface with a down link.
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: authentication with AP 00:90:d0:f2:ad:7b timed out
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
b43-phy4: Radio turned off by software
b43-phy4 debug: Removing Interface type 2
b43-phy4 debug: Wireless interface stopped
b43-phy4 debug: DMA-30 0x0200 (RX) max used slots: 1/64
b43-phy4 debug: DMA-30 0x02A0 (TX) max used slots: 0/128
b43-phy4 debug: DMA-30 0x0280 (TX) max used slots: 0/128
b43-phy4 debug: DMA-30 0x0260 (TX) max used slots: 0/128
b43-phy4 debug: DMA-30 0x0240 (TX) max used slots: 0/128
b43-phy4 debug: DMA-30 0x0220 (TX) max used slots: 32/128
b43-phy4 debug: DMA-30 0x0200 (TX) max used slots: 0/128

with hwcrypto:
ACPI: PCI Interrupt 0000:02:07.0[A] -> Link [APC4] -> GSI 19 (level,
low) -> IRQ 19
ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x04, vendor 0x4243)
ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x05, vendor 0x4243)
ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x02, vendor 0x4243)
ssb: Core 3 found: V90 (cc 0x807, rev 0x02, vendor 0x4243)
ssb: Core 4 found: PCI (cc 0x804, rev 0x09, vendor 0x4243)
ssb: SPROM revision 1 detected.
ssb: Sonics Silicon Backplane found on PCI device 0000:02:07.0
b43-phy3: Broadcom 4306 WLAN found
b43-phy3 debug: Found PHY: Analog 2, Type 2, Revision 2
b43-phy3 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
phy3: Selected rate control algorithm 'pid'
Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ]
bonding: bond0: Adding slave wlan0.
b43-phy3: Loading firmware version 410.2160 (2007-05-26 15:32:10)
b43-phy3 debug: Chip initialized
b43-phy3 debug: 30-bit DMA initialized
Registered led device: b43-phy3::tx
Registered led device: b43-phy3::rx
b43-phy3 debug: Wireless interface started
b43-phy3 debug: Adding Interface type 2
bonding: bond0: enslaving wlan0 as an active interface with a down link.
b43-phy3 debug: Using hardware based encryption for keyidx: 0, mac:
ff:ff:ff:ff:ff:ff
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: authentication with AP 00:90:d0:f2:ad:7b timed out
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
b43-phy3: Radio turned off by software
b43-phy3 debug: Disabling hardware based encryption for keyidx: 0,
mac: ff:ff:ff:ff:ff:ff
b43-phy3 debug: Removing Interface type 2
b43-phy3 debug: Wireless interface stopped
b43-phy3 debug: DMA-30 0x0200 (RX) max used slots: 1/64
b43-phy3 debug: DMA-30 0x02A0 (TX) max used slots: 0/128
b43-phy3 debug: DMA-30 0x0280 (TX) max used slots: 0/128
b43-phy3 debug: DMA-30 0x0260 (TX) max used slots: 0/128
b43-phy3 debug: DMA-30 0x0240 (TX) max used slots: 0/128
b43-phy3 debug: DMA-30 0x0220 (TX) max used slots: 32/128
b43-phy3 debug: DMA-30 0x0200 (TX) max used slots: 0/128

Re: b43 (H/W 4306 Rev. 03)

[John W. Linville]

On Thu, Feb 21, 2008 at 12:44:15PM +0000, Ahmed Ammar wrote:
> As per my talk with st3 #bcm-users I have decided you e-mail you with
> the details of my problem. I have this card:
> 
> 02:07.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
> Wireless LAN Controller (rev 03)
> 
> And whatever I do I can not get it to associate, I have tried with and
> without encryption and below are two pastes of dmesg with and without
> hwcrypto. I am not alone in this I have other people who have the same
> problem and have to use this patch to get the card working on
> b43legacy instead (http://url2cut.com?pwI)

> Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ]

I wonder if you could try using the firmware from here instead (aka FW11):

	http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2

Does that improve the situation for you?

Thanks,

John
-- 
John W. Linville
linville@tuxdriver.com

Re: b43 (H/W 4306 Rev. 03)

[Ahmed Ammar]

> I wonder if you could try using the firmware from here instead (aka FW11):
>
>         http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2
>
>  Does that improve the situation for you?

Still no joy, I had to force b43-cutter to even extract the firmware:

b43-fwcutter --unsupported /usr/src/broadcom-wl-4.80.53.0/kmod/wl_apsta_mimo.o

Just so you know I am using the latest wireless-testing.git tree.

ACPI: PCI interrupt for device 0000:02:07.0 disabled
ACPI: PCI Interrupt 0000:02:07.0[A] -> Link [APC4] -> GSI 19 (level,
low) -> IRQ 19
ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x04, vendor 0x4243)
ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x05, vendor 0x4243)
ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x02, vendor 0x4243)
ssb: Core 3 found: V90 (cc 0x807, rev 0x02, vendor 0x4243)
ssb: Core 4 found: PCI (cc 0x804, rev 0x09, vendor 0x4243)
ssb: SPROM revision 1 detected.
ssb: Sonics Silicon Backplane found on PCI device 0000:02:07.0
b43-phy6: Broadcom 4306 WLAN found
b43-phy6 debug: Found PHY: Analog 2, Type 2, Revision 2
b43-phy6 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
phy6: Selected rate control algorithm 'pid'
Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ]
Broadcom 43xx driver loaded [ Features: PLID, Firmware-ID: FW10 ]
bonding: bond0: Adding slave wlan0.
b43-phy6: Loading firmware version 351.126 (2006-07-29 05:54:02)
b43-phy6 warning: You are using an old firmware image. Support for old
firmware will be removed in July 2008.
b43-phy6 warning: You must go to
http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and
download the latest firmware (version 4).
b43-phy6 debug: Chip initialized
b43-phy6 debug: 30-bit DMA initialized
Registered led device: b43-phy6::tx
Registered led device: b43-phy6::rx
b43-phy6 debug: Wireless interface started
b43-phy6 debug: Adding Interface type 2
bonding: bond0: enslaving wlan0 as an active interface with a down link.
b43-phy6 debug: Using hardware based encryption for keyidx: 0, mac:
ff:ff:ff:ff:ff:ff
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: authentication with AP 00:90:d0:f2:ad:7b timed out
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
b43-phy6: Radio turned off by software
b43-phy6 debug: Disabling hardware based encryption for keyidx: 0,
mac: ff:ff:ff:ff:ff:ff
b43-phy6 debug: Removing Interface type 2
b43-phy6 debug: Wireless interface stopped
b43-phy6 debug: DMA-30 0x0200 (RX) max used slots: 1/64
b43-phy6 debug: DMA-30 0x02A0 (TX) max used slots: 0/128
b43-phy6 debug: DMA-30 0x0280 (TX) max used slots: 0/128
b43-phy6 debug: DMA-30 0x0260 (TX) max used slots: 0/128
b43-phy6 debug: DMA-30 0x0240 (TX) max used slots: 0/128
b43-phy6 debug: DMA-30 0x0220 (TX) max used slots: 32/128
b43-phy6 debug: DMA-30 0x0200 (TX) max used slots: 0/128
bonding: bond0: releasing active interface wlan0
b43-phy7: Broadcom 4306 WLAN found
b43-phy7 debug: Found PHY: Analog 2, Type 2, Revision 2
b43-phy7 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
phy7: Selected rate control algorithm 'pid'
Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ]
bonding: bond0: Adding slave wlan0.
b43-phy7: Loading firmware version 351.126 (2006-07-29 05:54:02)
b43-phy7 warning: You are using an old firmware image. Support for old
firmware will be removed in July 2008.
b43-phy7 warning: You must go to
http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and
download the latest firmware (version 4).
b43-phy7 debug: Chip initialized
b43-phy7 debug: 30-bit DMA initialized
Registered led device: b43-phy7::tx
Registered led device: b43-phy7::rx
b43-phy7 debug: Wireless interface started
b43-phy7 debug: Adding Interface type 2
bonding: bond0: enslaving wlan0 as an active interface with a down link.
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: authentication with AP 00:90:d0:f2:ad:7b timed out
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
b43-phy7: Radio turned off by software
b43-phy7 debug: Removing Interface type 2
b43-phy7 debug: Wireless interface stopped
b43-phy7 debug: DMA-30 0x0200 (RX) max used slots: 1/64
b43-phy7 debug: DMA-30 0x02A0 (TX) max used slots: 0/128
b43-phy7 debug: DMA-30 0x0280 (TX) max used slots: 0/128
b43-phy7 debug: DMA-30 0x0260 (TX) max used slots: 0/128
b43-phy7 debug: DMA-30 0x0240 (TX) max used slots: 0/128
b43-phy7 debug: DMA-30 0x0220 (TX) max used slots: 32/128
b43-phy7 debug: DMA-30 0x0200 (TX) max used slots: 0/128

Re: b43 (H/W 4306 Rev. 03)

[Ahmed Ammar]

> > Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ]
>
>
> You are still using the same firmware.
>
>  Make sure you extracted the firmware to the right place.  You may have
>  to use the "-w" option to b43-fwcutter.  The proper firmware location
>  depends on the distribution.  For Fedora it is in /lib/firmware.
>

I am very sure. Do I need to reboot?  All I did was: rmmod b43 ssb

b33fb0x firmware # rm -rf b43
b33fb0x firmware # b43-fwcutter --unsupported
/usr/src/broadcom-wl-4.80.53.0/kmod/wl_apsta_mimo.o
This file is recognised as:
  filename   :  wl_apsta_mimo.o
  version    :  351.126
  MD5        :  722e2e0d8cc04b8f118bb5afe6829ff9
Extracting b43/ucode4.fw
Extracting b43/ucode5.fw
Extracting b43/ucode11.fw
Extracting b43/ucode13.fw
Extracting b43/pcm4.fw
Extracting b43/pcm5.fw
Extracting b43/b0g0initvals4.fw
Extracting b43/b0g0bsinitvals4.fw
Extracting b43/a0g0initvals4.fw
Extracting b43/a0g0bsinitvals4.fw
Extracting b43/b0g0initvals5.fw
Extracting b43/b0g0bsinitvals5.fw
Extracting b43/a0g0initvals5.fw
Extracting b43/a0g1initvals5.fw
Extracting b43/a0g0bsinitvals5.fw
Extracting b43/a0g1bsinitvals5.fw
Extracting b43/lp0initvals13.fw
Extracting b43/lp0bsinitvals13.fw
Extracting b43/b0g0initvals13.fw
Extracting b43/b0g0bsinitvals13.fw
Extracting b43/a0g1initvals13.fw
Extracting b43/a0g1bsinitvals13.fw
b33fb0x firmware # pwd
/lib/firmware
b33fb0x firmware # ls
b43  b43legacy  rt2561.bin  rt2561s.bin  rt2661.bin
ACPI: PCI interrupt for device 0000:02:07.0 disabled
ACPI: PCI Interrupt 0000:02:07.0[A] -> Link [APC4] -> GSI 19 (level,
low) -> IRQ 19
ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x04, vendor 0x4243)
ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x05, vendor 0x4243)
ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x02, vendor 0x4243)
ssb: Core 3 found: V90 (cc 0x807, rev 0x02, vendor 0x4243)
ssb: Core 4 found: PCI (cc 0x804, rev 0x09, vendor 0x4243)
ssb: SPROM revision 1 detected.
ssb: Sonics Silicon Backplane found on PCI device 0000:02:07.0
b43-phy8: Broadcom 4306 WLAN found
b43-phy8 debug: Found PHY: Analog 2, Type 2, Revision 2
b43-phy8 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
phy8: Selected rate control algorithm 'pid'
Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ]
bonding: bond0: Adding slave wlan0.
b43-phy8: Loading firmware version 351.126 (2006-07-29 05:54:02)
b43-phy8 warning: You are using an old firmware image. Support for old
firmware will be removed in July 2008.
b43-phy8 warning: You must go to
http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and
download the latest firmware (version 4).
b43-phy8 debug: Chip initialized
b43-phy8 debug: 30-bit DMA initialized
Registered led device: b43-phy8::tx
Registered led device: b43-phy8::rx
b43-phy8 debug: Wireless interface started
b43-phy8 debug: Adding Interface type 2
bonding: bond0: enslaving wlan0 as an active interface with a down link.
b43-phy8 debug: Using hardware based encryption for keyidx: 0, mac:
ff:ff:ff:ff:ff:ff
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: authentication with AP 00:90:d0:f2:ad:7b timed out
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
b43-phy8: Radio turned off by software
b43-phy8 debug: Disabling hardware based encryption for keyidx: 0,
mac: ff:ff:ff:ff:ff:ff
b43-phy8 debug: Removing Interface type 2
b43-phy8 debug: Wireless interface stopped
b43-phy8 debug: DMA-30 0x0200 (RX) max used slots: 1/64
b43-phy8 debug: DMA-30 0x02A0 (TX) max used slots: 0/128
b43-phy8 debug: DMA-30 0x0280 (TX) max used slots: 0/128
b43-phy8 debug: DMA-30 0x0260 (TX) max used slots: 0/128
b43-phy8 debug: DMA-30 0x0240 (TX) max used slots: 0/128
b43-phy8 debug: DMA-30 0x0220 (TX) max used slots: 32/128
b43-phy8 debug: DMA-30 0x0200 (TX) max used slots: 0/128

Re: b43 (H/W 4306 Rev. 03)

[John W. Linville]

On Thu, Feb 21, 2008 at 08:04:28PM +0000, Ahmed Ammar wrote:
> > > Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ]
> >
> >
> > You are still using the same firmware.
> >
> >  Make sure you extracted the firmware to the right place.  You may have
> >  to use the "-w" option to b43-fwcutter.  The proper firmware location
> >  depends on the distribution.  For Fedora it is in /lib/firmware.
> >
> 
> I am very sure. Do I need to reboot?  All I did was: rmmod b43 ssb

Hmmm...OK, my mistake.

> bonding: bond0: enslaving wlan0 as an active interface with a down link.

This looks a little odd.  Have you had this working in the past?
Can you try a setup using just wlan0 (i.e. without bonding)?

Thanks,

John
-- 
John W. Linville
linville@tuxdriver.com

Re: b43 (H/W 4306 Rev. 03)

[Ahmed Ammar]

>  > bonding: bond0: enslaving wlan0 as an active interface with a down link.
>
>
> This looks a little odd.  Have you had this working in the past?
>  Can you try a setup using just wlan0 (i.e. without bonding)?
>

I have tried with and without bonding, and bonding is definitely not
the issue here, I am pretty sure this is something wrong with the
driver/firmware.

I am willing to test any patches that will give you better debugging,
or even direct access to my box?

Re: b43 (H/W 4306 Rev. 03)

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 189 bytes --]


> I am willing to test any patches that will give you better debugging,
> or even direct access to my box?

Can you make a packet dump with a second card in monitor mode?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

Re: b43 (H/W 4306 Rev. 03)

[Ahmed Ammar]

> Can you make a packet dump with a second card in monitor mode?

I will try, but i have never used my second card in monitor mode and i
don't even know if it supports it.

Re: b43 (H/W 4306 Rev. 03)

[Michael Buesch]

On Friday 22 February 2008, Ahmed Ammar wrote:
> > Can you make a packet dump with a second card in monitor mode?
> 
> I will try, but i have never used my second card in monitor mode and i
> don't even know if it supports it.

Is the AP an IEEE 802.11b-only AP that doesn't support IEEE 802.11g?

Re: b43 (H/W 4306 Rev. 03)

[Ahmed Ammar]

> Is the AP an IEEE 802.11b-only AP that doesn't support IEEE 802.11g?
>

No, this is an IEEE 802.11g AP.

Re: b43 (H/W 4306 Rev. 03)

[Ahmed Ammar]

> Can you make a packet dump with a second card in monitor mode?
>

Used wireshark and my rt61pci card. The dump is attached.

Re: b43 (H/W 4306 Rev. 03)

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 273 bytes --]


On Sat, 2008-02-23 at 12:18 +0000, Ahmed Ammar wrote:
> > Can you make a packet dump with a second card in monitor mode?
> >
> 
> Used wireshark and my rt61pci card. The dump is attached.

Nope. And there's no need to CC such files to the list anyway.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

Re: b43 (H/W 4306 Rev. 03)

[Ahmed Ammar]

Also,
I've found out that this seems to be a pci only issue, other users
with the exact same PHY revision on cardbus report b43 working fine.

Re: b43 (H/W 4306 Rev. 03)

[Michael Buesch]

On Sunday 24 February 2008 13:03:15 Ahmed Ammar wrote:
> I've found out that this seems to be a pci only issue, other users
> with the exact same PHY revision on cardbus report b43 working fine.

So, can you tell us the revision?

-- 
Greetings Michael.

Re: b43 (H/W 4306 Rev. 03)

[Ahmed Ammar]

b43legacy-phy0 debug: Found PHY: Analog 2, Type 2, Revision 2

It was said before, earlier part of thread.

Re: b43 (H/W 4306 Rev. 03)

[Ahmed Ammar]

Hmm,

Well I can only blame the bad rt61pci drivers, I'm out of options now.

Re: b43 (H/W 4306 Rev. 03)

[Ivo Van Doorn]

Hi,

> Hmm,
>
>  Well I can only blame the bad rt61pci drivers, I'm out of options now.

Yes, rt61pci is known to be buggy in monitor mode, there seem
to be some inconsistencies regarding frame filtering inside the device
which causes rt61pci to incorrectly filter some frames out.

It is an issue being looked into, and I believe Adam Baker already has
some patches he will send in for rt2x00 soon (First some other TX/RX
bugs needed to be fixed).

Ivo

Re: b43 (H/W 4306 Rev. 03)

[Ahmed Ammar]

[-- Attachment #1: Type: text/plain, Size: 693 bytes --]

> Yes, rt61pci is known to be buggy in monitor mode, there seem
>  to be some inconsistencies regarding frame filtering inside the device
>  which causes rt61pci to incorrectly filter some frames out.
>
>  It is an issue being looked into, and I believe Adam Baker already has
>  some patches he will send in for rt2x00 soon (First some other TX/RX
>  bugs needed to be fixed).
>

Ok, well on that note I have updated my sources with latest
wireless-testing.git and rt2x00.git (as of today). I think I have a
better dump. But very few packets fom b43 are ever seen (I can only
guess the tx code for my revision is borked?). b43legacy seems to show
full output, but i might be wrong. Attached.

[-- Attachment #2: b43.cap --]
[-- Type: application/octet-stream, Size: 583075 bytes --]

[-- Attachment #3: b43legacy.cap --]
[-- Type: application/octet-stream, Size: 21269 bytes --]

Re: b43 (H/W 4306 Rev. 03)

[Michael Buesch]

On Tuesday 04 March 2008 17:55:07 Ahmed Ammar wrote:
> > Yes, rt61pci is known to be buggy in monitor mode, there seem
> >  to be some inconsistencies regarding frame filtering inside the device
> >  which causes rt61pci to incorrectly filter some frames out.
> >
> >  It is an issue being looked into, and I believe Adam Baker already has
> >  some patches he will send in for rt2x00 soon (First some other TX/RX
> >  bugs needed to be fixed).
> >
> 
> Ok, well on that note I have updated my sources with latest
> wireless-testing.git and rt2x00.git (as of today). I think I have a
> better dump. But very few packets fom b43 are ever seen (I can only
> guess the tx code for my revision is borked?). b43legacy seems to show
> full output, but i might be wrong. Attached.

I don't know what you are doing, but we certainly don't support
hacking b43 to work on legacy devices or hacking b43legacy
to work on new devices, which it seems you did, right?

If you have some actual problem with some unmodified driver
version, please show us the problem and we will address it.

-- 
Greetings Michael.

Re: b43 (H/W 4306 Rev. 03)

[Ahmed Ammar]

> I don't know what you are doing, but we certainly don't support
>  hacking b43 to work on legacy devices or hacking b43legacy
>  to work on new devices, which it seems you did, right?
>
>  If you have some actual problem with some unmodified driver
>  version, please show us the problem and we will address it.
>

Please read the full thread.

Re: b43 (H/W 4306 Rev. 03)

[Michael Buesch]

On Tuesday 04 March 2008 18:49:36 Ahmed Ammar wrote:
> > I don't know what you are doing, but we certainly don't support
> >  hacking b43 to work on legacy devices or hacking b43legacy
> >  to work on new devices, which it seems you did, right?
> >
> >  If you have some actual problem with some unmodified driver
> >  version, please show us the problem and we will address it.
> Please read the full thread.

You already told me to do so, still I can't really follow this thread.
It's in progress since several weeks, still you seem to fail to
provide a _short_ and to the point summary of what actually goes wrong
for you.
There's something about weird PCI-only issues and so on which I doubt
very much.

So can you please reinterate the problem you are seeing?
Please describe what does work and what does not, without adding
weird theories like the PCI-only stuff, for example. Please add
logging output as well.
And that all in one mail, please, that doesn't require me to
waste time by grepping the mail archives.

-- 
Greetings Michael.

Re: b43 (H/W 4306 Rev. 03)

[Ahmed Ammar]

> You already told me to do so, still I can't really follow this thread.
>  It's in progress since several weeks, still you seem to fail to
>  provide a _short_ and to the point summary of what actually goes wrong
>  for you.
>  There's something about weird PCI-only issues and so on which I doubt
>  very much.
>
>  So can you please reinterate the problem you are seeing?
>  Please describe what does work and what does not, without adding
>  weird theories like the PCI-only stuff, for example. Please add
>  logging output as well.
>  And that all in one mail, please, that doesn't require me to
>  waste time by grepping the mail archives.

I have forwarded you all the mail I have, now read it. I have also got
to say that you are very aggressive, I made some guesses and I never
said that i _know_ what is going on, otherwise I would've fixed it and
sent a patch.

Re: b43 (H/W 4306 Rev. 03)

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]


On Tue, 2008-03-04 at 19:04 +0000, Ahmed Ammar wrote:
> > You already told me to do so, still I can't really follow this thread.
> >  It's in progress since several weeks, still you seem to fail to
> >  provide a _short_ and to the point summary of what actually goes wrong
> >  for you.
> >  There's something about weird PCI-only issues and so on which I doubt
> >  very much.
> >
> >  So can you please reinterate the problem you are seeing?
> >  Please describe what does work and what does not, without adding
> >  weird theories like the PCI-only stuff, for example. Please add
> >  logging output as well.
> >  And that all in one mail, please, that doesn't require me to
> >  waste time by grepping the mail archives.
> 
> I have forwarded you all the mail I have, now read it. I have also got
> to say that you are very aggressive, I made some guesses and I never
> said that i _know_ what is going on, otherwise I would've fixed it and
> sent a patch.

Please also start a new thread so I'm not copied on all your crap.

Thanks,
johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

Re: b43 (H/W 4306 Rev. 03)

[Michael Buesch]

On Tuesday 04 March 2008 20:04:26 Ahmed Ammar wrote:
> > You already told me to do so, still I can't really follow this thread.
> >  It's in progress since several weeks, still you seem to fail to
> >  provide a _short_ and to the point summary of what actually goes wrong
> >  for you.
> >  There's something about weird PCI-only issues and so on which I doubt
> >  very much.
> >
> >  So can you please reinterate the problem you are seeing?
> >  Please describe what does work and what does not, without adding
> >  weird theories like the PCI-only stuff, for example. Please add
> >  logging output as well.
> >  And that all in one mail, please, that doesn't require me to
> >  waste time by grepping the mail archives.
> 
> I have forwarded you all the mail I have, now read it.

No.
As I said, I need a _summary_ of this.
I am not going to grep mail that is 864kb in size.

Please describe in one mail, without randomly adding forwards of
old mails, what's going wrong and what you expect it to do.
Then add one complete dmesg log please.

If you don't want to do this, I'll simply ignore this thread from then on.
That's fine for me as well. Maybe not for you, but hey... ;)

-- 
Greetings Michael.

Re: b43 (H/W 4306 Rev. 03)

[Ahmed Ammar]

The _first_ email in this thread covers exactly that. I don't
understand what else you need, the size of the entire thread is very
big because i was asked to get some packet dumps (which shouldn't have
been sent to the list). I find it pointless to copy and paste the
first e-mail to give you that information. If you don't want to fix
this bug then it's not a big problem for me.

Re: b43 (H/W 4306 Rev. 03)

[Michael Buesch]

On Tuesday 04 March 2008 20:17:23 Ahmed Ammar wrote:
> The _first_ email in this thread covers exactly that. I don't

I'm not sure how often I have to reiterate this:
I do _not_ understand your issue. Please _rephrase_ it.
Also, the dmesg logs from the mail are far from being complete.

Pointing to the same mails that I don't understand over and over again
does not help at all. Rewrite them please and try to make it more clear
what your problem is. And add complete dmesg output from _unmodified_
drivers. (modified drivers/logs are ignored).

> understand what else you need, the size of the entire thread is very
> big because i was asked to get some packet dumps (which shouldn't have
> been sent to the list). I find it pointless to copy and paste the
> first e-mail to give you that information. If you don't want to fix
> this bug then it's not a big problem for me.

Ok. Don't want help -> don't get help. Your choice.

-- 
Greetings Michael.