Broadcom Drivers and Firmware, 11.4 M5

Alright, now that I got OpenSuse 11.4 M5 installed on my EeePC 1015PEM (after the installation media of 11.3 failed, due to the Broadcom issue), I wonder if I could get the WLAN to work.

As I’ve learned from…

Getting Your Wireless to Work

…there’s more than just a driver one must load for these devices to work: firmware. Didn’t ever think about something like this, but well, we’ve never learned enough :wink:

Getting device details:

linux-aqkk:/home/Kovu # lspci -vnn
00:00.0 Host bridge [0600]: Intel Corporation N10 Family DMI Bridge [8086:a010] (rev 02)
        Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
        Flags: bus master, fast devsel, latency 0
        Capabilities: [e0] Vendor Specific Information: Len=08 <?>
        Kernel driver in use: agpgart-intel

00:02.0 VGA compatible controller [0300]: Intel Corporation N10 Family Integrated Graphics Controller [8086:a011] (rev 02) (prog-if 00 [VGA controller])
        Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
        Flags: bus master, fast devsel, latency 0, IRQ 41
        Memory at f7e00000 (32-bit, non-prefetchable) [size=512]
        I/O ports at dc00 [size=8]
        Memory at d0000000 (32-bit, prefetchable) [size=256]
        Memory at f7d00000 (32-bit, non-prefetchable) [size=1]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Power Management version 2
        Kernel driver in use: i915

00:02.1 Display controller [0380]: Intel Corporation N10 Family Integrated Graphics Controller [8086:a012] (rev 02)
        Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
        Flags: bus master, fast devsel, latency 0
        Memory at f7e80000 (32-bit, non-prefetchable) [size=512]
        Capabilities: [d0] Power Management version 2

00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 02)
        Subsystem: ASUSTeK Computer Inc. Device [1043:841c]
        Flags: bus master, fast devsel, latency 0, IRQ 42
        Memory at f7cf8000 (64-bit, non-prefetchable) [size=16]
        Capabilities: [50] Power Management version 2
        Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
        Capabilities: [100] Virtual Channel
        Capabilities: [130] Root Complex Link
        Kernel driver in use: HDA Intel

00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 1 [8086:27d0] (rev 02) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
        I/O behind bridge: 0000f000-0000ffff
        Memory behind bridge: fea00000-febfffff
        Prefetchable memory behind bridge: 00000000fe800000-00000000fe9fffff
        Capabilities: [40] Express Root Port (Slot+), MSI 00
        Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
        Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
        Capabilities: [a0] Power Management version 2
        Capabilities: [100] Virtual Channel
        Capabilities: [180] Root Complex Link

00:1c.1 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 2 [8086:27d2] (rev 02) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=02, subordinate=03, sec-latency=0
        I/O behind bridge: 0000b000-0000bfff
        Memory behind bridge: f8000000-fbffffff
        Prefetchable memory behind bridge: 00000000f0000000-00000000f6ffffff
        Capabilities: [40] Express Root Port (Slot+), MSI 00
        Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
        Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
        Capabilities: [a0] Power Management version 2
        Capabilities: [100] Virtual Channel
        Capabilities: [180] Root Complex Link

00:1c.3 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 4 [8086:27d6] (rev 02) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: 0000e000-0000efff
        Memory behind bridge: f7f00000-f7ffffff
        Prefetchable memory behind bridge: 00000000fe600000-00000000fe7fffff
        Capabilities: [40] Express Root Port (Slot+), MSI 00
        Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
        Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
        Capabilities: [a0] Power Management version 2
        Capabilities: [100] Virtual Channel
        Capabilities: [180] Root Complex Link

00:1d.0 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 [8086:27c8] (rev 02) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
        Flags: bus master, medium devsel, latency 0, IRQ 23
        I/O ports at d400 [size=32]
        Kernel driver in use: uhci_hcd

00:1d.1 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 [8086:27c9] (rev 02) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
        Flags: bus master, medium devsel, latency 0, IRQ 19
        I/O ports at d480 [size=32]
        Kernel driver in use: uhci_hcd

00:1d.2 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 [8086:27ca] (rev 02) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
        Flags: bus master, medium devsel, latency 0, IRQ 18
        I/O ports at d800 [size=32]
        Kernel driver in use: uhci_hcd

00:1d.3 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 [8086:27cb] (rev 02) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
        Flags: bus master, medium devsel, latency 0, IRQ 16
        I/O ports at d880 [size=32]
        Kernel driver in use: uhci_hcd

00:1d.7 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller [8086:27cc] (rev 02) (prog-if 20 [EHCI])
        Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
        Flags: bus master, medium devsel, latency 0, IRQ 23
        Memory at f7cf7c00 (32-bit, non-prefetchable) [size=1]
        Capabilities: [50] Power Management version 2
        Capabilities: [58] Debug port: BAR=1 offset=00a0
        Kernel driver in use: ehci_hcd

00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev e2) (prog-if 01 [Subtractive decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=05, subordinate=05, sec-latency=32
        Capabilities: [50] Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]

00:1f.0 ISA bridge [0601]: Intel Corporation NM10 Family LPC Controller [8086:27bc] (rev 02)
        Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
        Flags: bus master, medium devsel, latency 0
        Capabilities: [e0] Vendor Specific Information: Len=0c <?>

00:1f.2 SATA controller [0106]: Intel Corporation N10/ICH7 Family SATA AHCI Controller [8086:27c1] (rev 02) (prog-if 01 [AHCI 1.0])
        Subsystem: ASUSTeK Computer Inc. Device [1043:83ad]
        Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 40
        I/O ports at d080 [size=8]
        I/O ports at d000 [size=4]
        I/O ports at cc00 [size=8]
        I/O ports at c880 [size=4]
        I/O ports at c800 [size=32]
        Memory at f7cf7800 (32-bit, non-prefetchable) [size=1]
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [70] Power Management version 2
        Capabilities: [a8] SATA HBA v1.0
        Kernel driver in use: ahci

01:00.0 Ethernet controller [0200]: Atheros Communications AR8132 Fast Ethernet [1969:1062] (rev c0)
        Subsystem: ASUSTeK Computer Inc. Device [1043:838a]
        Flags: bus master, fast devsel, latency 0, IRQ 43
        Memory at f7fc0000 (64-bit, non-prefetchable) [size=256]
        I/O ports at ec00 [size=128]
        Capabilities: [40] Power Management version 3
        Capabilities: [48] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [58] Express Endpoint, MSI 00
        Capabilities: [6c] Vital Product Data
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [180] Device Serial Number ff-6f-37-a0-20-cf-30-ff
        Kernel driver in use: atl1c

02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
        Subsystem: AzureWave Device [1a3b:2047]
        Flags: fast devsel, IRQ 17
        Memory at fbffc000 (64-bit, non-prefetchable) [size=16]
        Capabilities: [40] Power Management version 3
        Capabilities: [58] Vendor Specific Information: Len=78 <?>
        Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [d0] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [13c] Virtual Channel
        Capabilities: [160] Device Serial Number 00-00-60-ff-ff-2a-48-5d
        Capabilities: [16c] Power Budgeting <?>

YaST shows no entry for Wireless LAN, but the Broadcom Network controller is available in the PCI portion. The module loaded is “brcm80211”:

29: PCI 200.0: 0280 Network controller
  [Created at pci.318]
  Unique ID: B35A.HnhErYJK491
  Parent ID: qTvu.2laDbfeI21D
  SysFS ID: /devices/pci0000:00/0000:00:1c.1/0000:02:00.0
  SysFS BusID: 0000:02:00.0
  Hardware Class: network
  Model: "Broadcom Network controller"
  Vendor: pci 0x14e4 "Broadcom"
  Device: pci 0x4727 
  SubVendor: pci 0x1a3b 
  SubDevice: pci 0x2047 
  Revision: 0x01
  Memory Range: 0xfbffc000-0xfbffffff (rw,non-prefetchable)
  IRQ: 17 (no events)
  Module Alias: "pci:v000014E4d00004727sv00001A3Bsd00002047bc02sc80i00"
  Driver Info #0:
    Driver Status: brcm80211 is active
    Driver Activation Cmd: "modprobe brcm80211"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #19 (PCI bridge)

Now, looking for the firmware, dmesg says:

Kovu@linux-aqkk:~> dmesg | grep firmware
    2.043860] elantech: assuming hardware version 2, firmware version 20.1.0
   12.988725] brcm80211: fail to load firmware brcm/bcm43xx-0.fw
   12.988736] brcm80211: Failed to find firmware usually in /lib/firmware/brcm
Kovu@linux-aqkk:~> 

I’ve tried to search for bcm43xx-0.fw on the internet, but didn’t find anything downloadble that would match. Further, I’m not sure how sensible this firmware thing is… can I be sure that if the system asks for that firmware file it wouldn’t either harm my hardware or break my system (which, of course, could be fixed through the LiveCD system)?

Another thing I’ve tried is “sudo /usr/sbin/install_bcm43xx_firmware”, but it didn’t provide me with anything I seem to be needing.[/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size]

b43 - Linux Wireless

shows your device: brcm80211 - Linux Wireless

…meaning what exactly? The corresponding module is loaded (at least as far as I can see)… but where would I get the firmware file from?

On 12/22/2010 03:36 PM, KovuTN wrote:

> 02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
> Subsystem: AzureWave Device [1a3b:2047]
>
> --------------------
>
>
> YaST shows no entry for Wireless LAN, but the Broadcom Network
> controller is available in the PCI portion. The module loaded is
> “brcm80211”:

That will not appear until the driver finishes loading. That step needs firmware.

>
> Code:
> Now, looking for the firmware, dmesg says:
>
> Code:
> --------------------
> Kovu@linux-aqkk:~> dmesg | grep firmware
> 2.043860] elantech: assuming hardware version 2, firmware version 20.1.0
> 12.988725] brcm80211: fail to load firmware brcm/bcm43xx-0.fw
> 12.988736] brcm80211: Failed to find firmware usually in /lib/firmware/brcm
> Kovu@linux-aqkk:~>
>
> --------------------
>
>
> I’ve tried to search for bcm43xx-0.fw on the internet, but didn’t find
> anything downloadble that would match. Further, I’m not sure how
> sensible this firmware thing is… can I be sure that if the system asks
> for that firmware file it wouldn’t either harm my hardware or break my
> system (which, of course, could be fixed through the LiveCD system)?
>
> Another thing I’ve tried is “sudo /usr/sbin/install_bcm43xx_firmware”,
> but it didn’t provide me with anything I seem to be needing.

The script you ran in the paragraph above loaded the firmware needed by drivers
b43 and b43legacy, but they don’t handle your device.

You need to add the repository
http://download.opensuse.org/repositories/driver:/wireless/openSUSE_Factory/ and
add package “brcm80211-firmware”.

FYI, firmware is the name for the code that runs in the CPU that is built into
the device. For relatively simple cases, that code is included in ROM, but for
anything as complicated as a modern wireless device, the probability of change
in the code is very high, thus the vendors build in some mechanism for loading
this code into the on-board memory and a way to boot that CPU. If the firmware
is not available, no harm will come to your device, but it will not run. It is
like your main CPU without an operating system.

BTW, a Google search of “brcm80211 firmware” led me directly to the source of
the firmware.

Hmm… there’s no such package in said repository.

Here
Index of /repositories/driver:/wireless/openSUSE_11.3

Ah, cool. There it is :wink:

WLAN is up and running now. Thank you again :slight_smile: .

Great - well done

[quote="“KovuTN,post:5,topic:60004”]

Hmm… there’s no such package in said repository.[/QUOTE]

So should KovuTN make a bug-report (low level <- easy workaround)
or is someone who has written on or read this thread
able (as I am not :frowning: ) and willing to fix that thing with the
missing broadcom firmware for Broadcom BRCM 4313
with PCI Vendor ID/Device ID 0x14e4 0x4727
in the Factory / openSUSE 11.4 repositories
e. g. after Christmas?

And by the way:
@KovuTN, you are now on the cutting edge of development.
But to make the probability of been cut by the edge while updating a bit lower
you may be interesting in
the repository
factory-tested
(the new semi-stable rolling release based on openSUSE Factory).
But before that (and a fortiori before updating to the untested Factory/11.4 repository)
you might be watching the current problems (see: openQA.opensuse.org , [opensuse-testing] factory-tested status](http://lists.opensuse.org/opensuse-testing/2010-12/msg00008.html) and openQA.opensuse.org ) and for indications that they would have disappeared.

Have a lot of luck and fun!
pistazienfresser

On 12/23/2010 04:06 AM, pistazienfresser wrote:
>
> So should KovuTN make a bug-report (low level <- easy workaround)
> or is someone who has written on or read this thread
> able (as I am not :frowning: ) and willing to fix that thing with the
> missing broadcom firmware for Broadcom BRCM 4313
> with PCI Vendor ID/Device ID 0x14e4 0x4727
> in the Factory / openSUSE 11.4 repositories
> e. g. after Christmas?
>
> And by the way:
> @KovuTN, you are now on the cutting edge of development.
> But to make the probability of been cut by the edge while updating a
> bit lower
> you may be interesting in
> the repository
> 'factory-tested ’ (http://en.opensuse.org/openSUSE:Factory-tested)
> (the new semi-stable rolling release based on openSUSE Factory).
> But before that (and a fortiori before updating to the untested
> Factory/11.4 repository)
> you might be watching the current problems (see: ‘openQA.opensuse.org
> (http://openqa.opensuse.org/) , ‘[opensuse-testing] factory-tested
> status’
> (http://lists.opensuse.org/opensuse-testing/2010-12/msg00008.html) and
> ‘openQA.opensuse.org’ (http://openqa.opensuse.org/results/) ) and for
> indications that they would have disappeared.

No bug report is needed. The updated firmware is already queued for inclusion in
11.4 and backported to 11.3. The OP just got caught in the middle.

BTW:

This is exactly the reason why there was no package for Factory (and very often I don’t package such stuff for Factory on purpose).

I didn’t know this would happen when packaging this firmware for driver:wireless, but considering the source where the files are from, there was at least a chance this would happen, so I decided to block building for Factory avoiding the result of having two packages with exactly the same files and nice, little warnings from zypper because of that.

In a nutshell, I am very reluctant to package something for Factory, especially backported stuff, as sooner or later it will become obsolete and cause conflicts with stuff already inside the main distro.

As Factory changes rapidly, this is not worth the effort (at least in my opinion), especially for firmware and drivers in staging.

P.S.

If there is any package in driver:wireless present for released versions and not present for Factory, please don’t report this as a bug unless you have a very good reason to do so (and especially for binary-only firmware packages, there isn’t one).

Thanks to both of you for the clarification.

Regards
pistazienfresser

Hello,

I am new on this forum and new user for open Suse distribution. I love Ubuntu but I love the KDE interface and I think this distribution is the better to use with KDE.

I have some issue with my wifi connection due to my broadcom card: BCM4322

My question is simple: do you think I have a problem with my card or this error is it due to the current kernel version (11.4 M5, it is not the final version). In my opinion fixes will arrive in the next week.

Could you confirm my opinion or do you think, reading my copy/paste commands, I have an another problem who will not be fixed with the future updates ?

It is not a problem for me to wait few days considering I can temporary connect an ethernet cable.

linux-ayw1:/home/yoyo # /sbin/lspci
0c:00.0 Network controller: Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)

linux-ayw1:/home/yoyo # /usr/bin/lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 064e:8100 Suyin Corp.
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 413c:8140 Dell Computer Corp. Wireless 360 Bluetooth
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

linux-ayw1:/home/yoyo # /sbin/lspci -n
0c:00.0 0280: 14e4:432b (rev 01)

linux-ayw1:/home/yoyo # dmesg
8.474305] b43-phy0: Broadcom 4322 WLAN found (core revision 16)
8.520190] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 8, Type 4, Revision 4)
8.520231] b43: probe of ssb0:0 failed with error -95
8.520255] Broadcom 43xx driver loaded Features: PMLS, Firmware-ID: FW13 ]

Thanks a lot

yoyoMC

I’m fairly sure this device will work in 11.3 with the ‘wl’ driver from packman
Install Broadcom Drivers from Packman

Info
b43 - Linux Wireless

Thanks for your response. I am agree with you about the 11.3, but I am currently using the 11.4 M5 and if I add repositories from 11.3, I have a conflict.

That’s why my question is to understand if it is better to wait the 11.4 final version, or if I must to manually activate this driver if you don’t think the 11.4 will not fix this issue.

yoyomc

On 01/06/2011 11:06 AM, yoyomc wrote:
>
> Hello,
>
> I am new on this forum and new user for open Suse distribution. I love
> Ubuntu but I love the KDE interface and I think this distribution is the
> better to use with KDE.
>
> I have some issue with my wifi connection due to my broadcom card:
> BCM4322
>
> My question is simple: do you think I have a problem with my card or
> this error is it due to the current kernel version (11.4 M5, it is not
> the final version). In my opinion fixes will arrive in the next week.
>
> Could you confirm my opinion or do you think, reading my copy/paste
> commands, I have an another problem who will not be fixed with the
> future updates ?
>
> It is not a problem for me to wait few days considering I can temporary
> connect an ethernet cable.
>
> linux-ayw1:/home/yoyo # /sbin/lspci
> 0c:00.0 Network controller: Broadcom Corporation BCM4322 802.11a/b/g/n
> Wireless LAN Controller (rev 01)
>
> linux-ayw1:/home/yoyo # /usr/bin/lsusb
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 002: ID 064e:8100 Suyin Corp.
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 003 Device 002: ID 413c:8140 Dell Computer Corp. Wireless 360
> Bluetooth
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>
>
> linux-ayw1:/home/yoyo # /sbin/lspci -n
> 0c:00.0 0280: 14e4:432b (rev 01)
>
>
> linux-ayw1:/home/yoyo # dmesg
> 8.474305] b43-phy0: Broadcom 4322 WLAN found (core revision 16)
> 8.520190] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 8, Type 4,
> Revision 4)
> 8.520231] b43: probe of ssb0:0 failed with error -95
> 8.520255] Broadcom 43xx driver loaded Features: PMLS,
> Firmware-ID: FW13 ]

The Broadcom 802.11n devices, including your BCM4322, will not be supported by
b43 until kernel 2.6.38, which is why you get the “UNSUPPORTED PHY” message.
That kernel will not be in openSUSE until the release AFTER 11.4. You need to
install the Broadcom wl hybrid driver from the Packman repository. The necessary
packages are “broadcom-wl” and “broadcom-wl-kmp-XXXXX”, where XXXXX is
“default”, “pae”, “xen”, or “desktop”, depending on which kernel you run.

I also have a BCM4322 and I am running a 2.6.37 kernel from the wireless-testing
git tree that has the latest b43 code. In fact, I am connected with it right
now, and it never loses the connection. The main problems are that OFDM rates
are not yet implemented, thus the transmission rates cannot exceed 11 Mb/s, and
the device has trouble connecting with WPA/WPA2 encryption. I think I know the
reason for the failure of OFDM rates - that should soon be fixed, and I think
that will also fix the WPA/WPA2 difficulties.

Oki thanks ! I am going to try to install with the wl drivers.

But what I do not understand is the 11.4 should have support for broadcom drivers, as specified in the documentation. Perhaps it is not the same drivers ?

Perhaps it is an easy question for you, but I do not understand the procedure to follow.

I am currently running with the Kernel 2.6.37 and using the packman repository (from 11.3), I have to respect the dependency using the 2.6.34 kernel. If I not respect this dependency, I can not install the two wl drivers.

What do you suggest ?

Thanks a lot !

On 01/06/2011 01:36 PM, yoyomc wrote:
>
> Perhaps it is an easy question for you, but I do not understand the
> procedure to follow.
>
> I am currently running with the Kernel 2.6.37 and using the packman
> repository (from 11.3), I have to respect the dependency using the
> 2.6.34 kernel. If I not respect this dependency, I can not install the
> two wl drivers.

I messed up the part about using Packman with 11.4M5. It will not have a wl
module for your kernel. You will need to install the kernel headers and make
sure that /lib/modules/uname -r/build is a link that points to the location of
the “include” directory that contains those headers. You will also need to
install make and gcc. At that point, you can get the hybrid source/binary from
the Broadcom website (Google for Broadcom hybrid driver) and build your own
module using the instructions that they provide. One step they leave out - after
the “sudo make install” step, you also need a “sudo depmod -a”, otherwise there
is a module that will not be found.

On 01/06/2011 01:06 PM, yoyomc wrote:
>
> Oki thanks ! I am going to try to install with the wl drivers.
>
> But what I do not understand is the 11.4 should have support for
> broadcom drivers, as specified in the documentation. Perhaps it is not
> the same drivers ?\

What documentation?