Update on using b43 with PCI ID 14e4:4315

[Akoellh]

Originally Posted by -Riffer-

Hmm... no progress in this thread.

Maybe the wrong platform for discussing development stuff.

Originally Posted by -Riffer-

Is anyone reading this who could work on the problems we have?

Larry did, he even answered.

Originally Posted by -Riffer-

Else I think it would be a good idea to inform the official maintainer of the bleeding edge drivers.

Of course (btw. Larry is one of them).

Such stuff should always be discussed at the place where you will reach most people actually developing the drivers, so use the respective mailing list(s).

[-Riffer-]

Thanks in advance - I will turn to their mailing lists now.

[growbag]

I just noticed that my bcm 4312 runs a lot slower under Linux than it does under windows, in the region of 20% of the speed .

Is there any way of speeding it up at all?

I'm running kernel 2.6.31-41-default from the "Kernel of the Day" repo if that makes any difference.

[malcolmlewis]

Originally Posted by growbag

I just noticed that my bcm 4312 runs a lot slower under Linux than it
does under windows, in the region of 20% of the speed .

Is there any way of speeding it up at all?

I'm running kernel 2.6.31-41-default from the "Kernel of the Day" repo
if that makes any difference.

Hi
have you tried changing the speed from the CLI with iwconfig command? I
think Larry posted some information a while back on how to do it.

--
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.27.29-0.1-default
up 0:22, 2 users, load average: 0.61, 0.27, 0.18
GPU GeForce 8600 GTS Silent - CUDA Driver Version: 190.18

[growbag]

It reports that it is running at 54mbps -

iwconfig shows -

wmaster0  no wireless extensions.

wlan0     IEEE 802.11bg  ESSID:"FRITZ!Box"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:1C:4A:D5:3D:36
          Bit Rate=54 Mb/s   Tx-Power=20 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=58/70  Signal level=-52 dBm  Noise level=-67 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

I'm not complaining, I'm happy that it works, but it would be nice to get some more speed out of it if possible .

[malcolmlewis]

Originally Posted by growbag

It reports that it is running at 54mbps -

iwconfig shows -


Code:
--------------------
wmaster0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:"FRITZ!Box"
Mode:Managed Frequency:2.437 GHz Access Point: 00:1C:4A5:3D:36
Bit Rate=54 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thrff Fragment thrff
Power Managementff
Link Quality=58/70 Signal level=-52 dBm Noise level=-67 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
--------------------


I'm not complaining, I'm happy that it works, but it would be nice to
get some more speed out of it if possible .

Hi
Scan for other AP's that may be on the same frequency and change yours?
Play with the antenna(s) and see if you can get the link quality higher?

--
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.27.29-0.1-default
up 1:24, 2 users, load average: 0.11, 0.08, 0.02
GPU GeForce 8600 GTS Silent - CUDA Driver Version: 190.18

[lwfinger]

growbag wrote:
>
>
> I'm not complaining, I'm happy that it works, but it would be nice to
> get some more speed out of it if possible .

At the moment, no power control code has been coded. As such, it is
lucky that we get the 15 Mb/s transmit speed that we do. The
performance will improve, but not until the full implementation is
completed. I have no idea as to when that will be. Remember - I am not
permitted to code for the device as I have seen details of the
Broadcom code while doing the reverse engineering. I only prepare the
specs.

[-Riffer-]

Thank you for this information. That makes things much more clear to me :-)

In addition I can tell to the thread that the driver from 27th of september does again work for my system. The bug I reported seems to be fixed.

[lwfinger]

-Riffer- wrote:
> Thank you for this information. That makes things much more clear to me
> :-)
>
> In addition I can tell to the thread that the driver from 27th of
> september does again work for my system. The bug I reported seems to be
> fixed.

Yes, there was a bug in the cfg80211 code that prevented connection
with WPA or WPA2 encryption. I didn't learn of the problem until quite
late as I was visiting my daughter, and she uses WEP encryption.