BroadCom BCM 4312 in Slackware 64 13

Alexvader · 11-22-2009, 02:30 PM

Hi forum

I have read a few topics on Installing the BCM 43xx thing in Slackware 13...

For the previous driver there was a need for some patch provided by broadcom for compatibility issues with kernel 2.6.29...

Broadcom no longer releases this patch, because the current version of the driver solved this issue, in fact, there is a SlackBuild for the sta driver based onthe current released driver version from Broadcom, from SlackBuilds org, which I built, and installed...

Then How com that after having successfully installed the built driver, if I

#ifconfig wlan0 up, nothing shows up and it complanits about a non existing device, or incorrect flags ( I am not sure of the exatc message ), yet, my Broadcom is correctly displayed in lspci listing...?

BRGDS

Alex

ckt1g3r · 11-22-2009, 03:30 PM

hi , take a look at readme.txt and follow the steps http://www.broadcom.com/support/802.11/linux_sta.php

Alexvader · 11-22-2009, 03:41 PM

Hi ckt1g3r

I will do this and report back here tomorrow...

Thkz a lot :-)

BRGDS

Alex

escaflown · 11-22-2009, 05:02 PM

Check out if your wlan0 is not detected as eth1. It happened to me with my BCM 4312.

Quote:

Originally Posted by Alexvader

Hi forum

I have read a few topics on Installing the BCM 43xx thing in Slackware 13...

For the previous driver there was a need for some patch provided by broadcom for compatibility issues with kernel 2.6.29...

Broadcom no longer releases this patch, because the current version of the driver solved this issue, in fact, there is a SlackBuild for the sta driver based onthe current released driver version from Broadcom, from SlackBuilds org, which I built, and installed...

Then How com that after having successfully installed the built driver, if I

#ifconfig wlan0 up, nothing shows up and it complanits about a non existing device, or incorrect flags ( I am not sure of the exatc message ), yet, my Broadcom is correctly displayed in lspci listing...?

BRGDS

Alex

Alexvader · 11-23-2009, 09:20 AM

Hi Escaflown

Indeed this happened...

I managed to Install the driver, and wlan0 shows up as eth0... when I run ifconfig

I configured my ethernet to work as DHCP, and it remains undetected, so I ran netconfig so as to set ethernet to be activated at boot time with fixed IP adress, and show up as eth0... no way...

I guess I shall have to reinstall Slackware and set my Ethernet to be activated at boot time with fixed IP, and then, install the BCM thing so as to pop it up as wlan0, ( or eth1...)

How did you solve your issue...?

BRGDS

Alex

escaflown · 11-23-2009, 08:09 PM

Well, I didn't really fixed it. I tried to make some changes in /etc/udev/rules.d/70-persistent-net.rules but it didn't help as it got back to eth1 once I rebooted. So I finally gave up and, instead, in the preferences of wicd, I simply declared my wireless interface as eth1.

Alexvader · 11-24-2009, 09:47 AM

Hi Escaflown

Thkz for your reply,

One of these days I will reinstall Slackware 64 13 in the same machine, only in an USB HDD, I will try to change the settings of my eth0, from DHCP to fixed IP at Install time, so that when the OS "awakes" it can see eth0, and then I will install BCM 4312 stuff, and see how it gets...

I will post back here as soon as I get some new answers... :-)

Thks a lot

BRGDS

Alex

Joe of Loath · 01-14-2010, 11:36 AM

Got any updates? Fedora just took a dump on my dell laptop and I just want to go for it and use slackware

piratesmack · 01-14-2010, 01:19 PM

If you prefer wlan0 instead of eth1, here's a patch for the broadcom-sta driver.

Code:

--- src/wl/sys/wl_linux.c	2009-09-10 12:21:58.000000000 -0600
+++ src/wl/sys/wl_linux.c.edit	2010-01-10 00:35:23.414267044 -0700
@@ -204,7 +204,7 @@ module_param(piomode, int, 0);
 static int nompc = 0;
 module_param(nompc, int, 0);
 
-static char name[IFNAMSIZ] = "eth%d";
+static char name[IFNAMSIZ] = "wlan%d";
 module_param_string(name, name, IFNAMSIZ, 0);
 
 #ifndef	SRCBASE

doomey · 01-14-2010, 03:28 PM

i have the same wireless chipset and i had to dig a bit. before slackbuilding the driver i slackbuilt fwcutter, installed, built firmware, installed, built driver, installed. only then it worked correctly for me.

as for the naming of the wireless card, kernel 2.6.29.6 sees it as eth1, but kernel 2.6.32.2 sees it as wlan0. i don't know if i did a stupid thing but i symlinked the wlan0 to eth1 in the newer kernel in order to have naming consistency

. and it works with no hiccups.