Trouble with BRCM 4313 b/g/n wireless on F17 in WPA2.

[indian11]

Hi,

I have a Samsung NP305-U1A laptop. It is an AMD Brazon E-450 machine with BRCM 4313 b/g/n wireless.

When I tried the liveCD for Fedora 17 Beta-2 AMD64 on this machine, it failed to connect to my wireless router leaving me without wireless. I am able to see the access points in the neighbourhood on the Network Manager GUI, and also with iwlist wlan0 scan. The Network Manager keeps popping up the "type access phrase" dialog, and giving the correct WPA2 phrase does not work.

My router is configured with broadcast ESSID and WPA2 personal, TKIP/AES. It works perfectly with my 2+ year old Ubuntu install on another machine.

lsmod shows the brcmsmac driver loaded and not the broadcom-wl or b43 or older.

Any help would be greatly appreciated.


Regards/Indian.

[bbfuller]

Hello indian11

There have been times since the "brcmsmac" driver was released that it has been broken. This may be one of those times.

The usual advice is to update the install or to go with the broadcom-wl driver. I can't guarantee that the "brcmsmac" will work after update in any case. The broadcom-wl, if you can get it for F17 should.

That's going to be a bit of a pain running off the live CD as you'll loose any changes you make on reboot.

[oALIASo]

I tried to install broadcom-wl after a fresh install of F17...

# yum install broadcom-wl
Loaded plugins: langpacks, presto, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package broadcom-wl.noarch 0:5.100.82.112-2.fc17.1 will be installed
--> Processing Dependency: wl-kmod >= 5.100.82.112 for package: broadcom-wl-5.100.82.112-2.fc17.1.noarch
--> Running transaction check
---> Package kmod-wl.x86_64 0:5.100.82.112-2.fc17.4 will be installed
--> Processing Dependency: kmod-wl-3.3.2-8.fc17.x86_64 >= 5.100.82.112-2.fc17.4 for package: kmod-wl-5.100.82.112-2.fc17.4.x86_64
--> Running transaction check
---> Package kmod-wl-3.3.2-8.fc17.x86_64.x86_64 0:5.100.82.112-2.fc17.4 will be installed
--> Processing Dependency: kernel-uname-r = 3.3.2-8.fc17.x86_64 for package: kmod-wl-3.3.2-8.fc17.x86_64-5.100.82.112-2.fc17.4.x86_64
--> Running transaction check
---> Package kernel.x86_64 0:3.3.2-8.fc17 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

=============================================================================================================================================================
 Package                                   Arch                 Version                                Repository                                       Size
=============================================================================================================================================================
Installing:
 broadcom-wl                               noarch               5.100.82.112-2.fc17.1                  rpmfusion-nonfree-updates-testing                16 k
Installing for dependencies:
 kernel                                    x86_64               3.3.2-8.fc17                           fedora                                           25 M
 kmod-wl                                   x86_64               5.100.82.112-2.fc17.4                  rpmfusion-nonfree-updates-testing               9.9 k
 kmod-wl-3.3.2-8.fc17.x86_64               x86_64               5.100.82.112-2.fc17.4                  rpmfusion-nonfree-updates-testing               678 k

Transaction Summary
=============================================================================================================================================================
Install  1 Package (+3 Dependent packages)

Total size: 26 M
Installed size: 116 M
Is this ok [y/N]: y
Downloading Packages:
Running Transaction Check
Running Transaction Test


Transaction Check Error:
  package kernel-3.3.4-1.fc17.x86_64 (which is newer than kernel-3.3.2-8.fc17.x86_64) is already installed

Error Summary
-------------

so I...

# uname -r
3.3.4-1.fc17.x86_64

I cant find a fix

Found a fix...

Originally Posted by dd_wizard

If it's Bug 815091, all you have to do is turn the wireless off and back on in Network Settings. I'm sure a patched NetworkManager is in the works.

dd_wizard