Just installed wifi driver, internet is really choppy and I'm not sure why.

Didier Spaier · 09-26-2013, 03:33 PM

Thanks for the info. Please complete your answer though, as I added questions to my previous post while you were answering it.

slacker_ · 09-26-2013, 03:35 PM

Quote:

Originally Posted by Didier Spaier

Thanks for the info. Please complete your answer though, as I added questions to my previous post while you were answering it.

done

Didier Spaier · 09-26-2013, 04:00 PM

I had a look at the source package b43-fwcutter_015-14.1.debian.tar.gz for Wheezy and in file firmware-b43-installer.postinst, for your card [14e4:4328] it says to use firmware broadcom-wl-5.100.138.tar.bz2, which is exactly the same used to build the package on Slackware. So I still don't understand this difference in behaviors.

Didier Spaier · 09-26-2013, 04:24 PM

In this page you device is told to have a PHY version N (r2).

In the same page I see as Feature "not working yet":
5GHz for N-PHY cards

So I'd suggest you try again to use the braodcom sta/wl driver instead. Other than that some people recommend to pass the options pio=0 and qos=0 to the driver but I'm not sure that will help for your device.

If you want to try you could use this command as root:

Code:

echo "options b43 pio=1 qos=0" > /etc/modprobe.conf/b43.conf

Correction: I should have written

Code:

echo "options b43 pio=1 qos=0" > /etc/modprobe.d/b43.conf

PS Re-reading this thread I don't see a full output of "lsmod". please provide it (with the card plugged-in, of course).

PPS When you had the "exec format error", are you sure you built the wl module for your ARCH (32bit vs 64bit)?

slacker_ · 09-26-2013, 05:08 PM

Quote:

Originally Posted by Didier Spaier

In this page you device is told to have a PHY version N (r2).

In the same page I see as Feature "not working yet":
5GHz for N-PHY cards

So I'd suggest you tray again to use the braodcom sta/wl driver instead.

Hm. perhaps I had the wl module in debian then. I could have sworn it was the b43, because I followed that page's instructions for the b43 and fw cutter. I'm not sure what would have happened.

Quote:

Originally Posted by Didier Spaier

Other than that some people recommend to pass the options pio=0 and qos=0 to the driver but I'm not sure that will help for your device.

If you want to try you could use this command as root:

Code:

echo "options b43 pio=1 qos=0" > /etc/modprobe.conf/b43.conf

Tried that, didn't net any noticeable result.

Quote:

Originally Posted by Didier Spaier

PS Re-reading this thread I don't see a full output of "lsmod". please provide it (with the card plugged-in, of course).

Thought I had provided that. Oh well, here it is.

Quote:

Originally Posted by Didier Spaier

PPS When you had the "exec format error", are you sure you built the wl module for your ARCH (32bit vs 64bit)?

I am positive. I can rebuild a wl module for 32bit though, see what happens.

Didier Spaier · 09-26-2013, 05:46 PM

Quote:

Originally Posted by slacker_

I can rebuild a wl module for 32bit though, see what happens.

Yes.

slacker_ · 09-26-2013, 07:31 PM

Quote:

Originally Posted by Didier Spaier

Yes.

I can't load the module before I blacklist things. Problem is, blacklisting didn't do anything. I set up the file the way it said it should be on the slackbuilds site and it didn't work. File is in /etc/modprobe.d/blacklist and this is what it looks like:

Code:

blacklist b43
blacklist b43legacy
blacklist brcmsmac
blacklist bcma
blacklist ssb

It's a good bit longer than it should be but it shouldn't interfere with wl.ko should it?

Didier Spaier · 09-27-2013, 02:27 AM

Quote:

Originally Posted by slacker_

File is in /etc/modprobe.d/blacklist

Files in /etc/modprobe.d should have a name ending in .conf to be scanned. So rename it /etc/modprobe.d/blacklist.conf (or /etc/rc.d/blacklist_b43.conf if you prefer, whatever :-) To know more: "man modprobe.d"

slacker_ · 09-27-2013, 02:53 AM

Quote:

Originally Posted by Didier Spaier

Files in /etc/modprobe.d should have a name ending in .conf to be scanned. So rename it /etc/modprobe.d/blacklist.conf (or /etc/rc.d/blacklist_b43.conf if you prefer, whatever :-) To know more: "man modprobe.d"

Yeah I can't believe I over looked that one. It's almost 0400 on the east coast of North America, so I'll be testing the wl once more later on today and will update the thread accordingly.

Didier Spaier · 09-27-2013, 03:01 AM

Sorry, in a previous post instead of:

Code:

echo "options b43 pio=1 qos=0" > /etc/modprobe.conf/b43.conf

I should have written:

Code:

echo "options b43 pio=1 qos=0" > /etc/modprobe.d/b43.conf

slacker_ · 09-27-2013, 01:57 PM

Quote:

Originally Posted by Didier Spaier

Sorry, in a previous post instead of:

Code:

echo &quot;options b43 pio=1 qos=0&quot; > /etc/modprobe.conf/b43.conf

I should have written:

Code:

echo &quot;options b43 pio=1 qos=0&quot; > /etc/modprobe.d/b43.conf

That's fine, I knew what you meant.

Tried to build the wl module but it kicked back an error. I can't understand the error, so I'll be posting it *HERE* in just a moment. If you don't see it hyperlinked, try again in a few minutes.

turtleli · 09-27-2013, 02:40 PM

If it's for kernel 3.10.x then you'll need to patch the wl code. See this thread.

slacker_ · 09-27-2013, 03:16 PM

what file am I patching? It's kicking back "can't find file to patch at input line 4"

Edit** nevermind, I had to use -p2... my mistake.

slacker_ · 09-27-2013, 03:19 PM

When I try to load the module it says

Code:

Error: could not insert module wl.ko: Unknown symbol in module

Haven't seen that before, any inight?

Edit: Also, I'm using the latest version of the driver which is 6.30.223.141

Didier Spaier · 09-27-2013, 03:21 PM

You could spare yourself some hassle simply using the kernel shipped with Slackware-14.0. I did that and had no problem building the driver and inserting it.

But don't forget to run as root "depmod -a" after installation.