TROUBLE SHOOTING


1. If the wl driver loads but doesn't seem to do anything: the ssb module may be the cause. Sometimes blacklisting ssb may not be enough to prevent it from loading and it loads anyway. (This is mostly seen on Ubuntu/Debian systems). From HERE

Check to see if ssb, wl or b43 is loaded:

lsmod | grep"b43\|ssb\|wl"

If any of these are installed, remove them:

sudo rmmod b4

sudo rmmod ssb

sudo rmmod wl

Back up the current boot ramfs and generate a new one.

sudo cp /boot/initrd.img-`uname -r` /path/to/somewheresafe

sudo update-initramfs -u

Reboot



2. The driver fails to load at boot.

Perform this command in a terminal

sudo echo wl >> /etc/modules

If that alone does not allow the driver to load when the system is booted, create a file

gksudo /etc/modprobe.d/00local

and add the line

install wl /bin/true

The driver should load upon reboot.

Note that"If the file /etc/modprobe.conf exists, all contents of /etc/modprobe.d/ are ignored by default."

I read that after looking at Antis link from the LMDE site. Maybe it will help you.


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://community.linuxmint.com/tutorial/view/218"
linktext was:"http://community.linuxmint.com/tutorial/view/218"
====================================

Thx for that, I read it is but it is not matching as long as I get that FATAL error about the wl module I reported in my previous post.

I had a similar problem to yours. Here's a script I wrote to deal with that

#!/bin/sh

#to load wl.ko module for broadcom chip
su -c modprobe lib80211

modprobe lib80211
insmod /home/pedro/hybrid_wl/wl.ko
ifdown eth0
ifup eth0

exit 0


Obviously, you need to list your location for the driver so replace /home/pedro/hybrid with your path. You need to insert the module into the kernel with the insmod command. Also, remember you will need to change the ifdown/ifup commands to your actual card (it's eth0 in my system; might be different in yours).

I would suggest that you try the commands first, as root. If they work then set up the script which you can type at boot up.

I hope this helps.

Regards,

Pedro

Thx Pedro for your script. Unfortunately I have to configure the device first (eth1) but the device is not available in ceni (because the driver is not loaded)

This morning a received another frustrating blow from antiX:
Being frustrated and confused I plugged in my USB key with the antiX iso to do a fresh install on harddisk, I had the impression that there was too much chaos after all my attempts. This time (in Live mode and without setting anything before except language & time zone) I opened the control center -> Network and started ceni. In the first screen it already showed the wifi device, this time with the wl driver! All I had to do is
- accepting the defaults,
- let it scan and find my network,
- fill in the password, leaving all other options on default settings
Connected! __{{emoticon}}__

Being happy I started the harddisk installation from this same session. In the screen of services to be started it listed"wicd - wireless connection". Installation was fast, I rebooted and now:
No network connection. Opening ceni I see the device but with the wrong driver (b43)! Back to start! __{{emoticon}}__

How can that be that in Live mode the system selects the wl driver and after configuring the device and testing successfully the system installs the wrong driver? As the system uses the wl driver in Live mode this driver must be available in the iso, so no downloading and installing should be necessary!

Could anybody give a logic explanation for that?
I'm not far from looking elsewhere, I'm not used to a system pulling my leg.

While running live and with wifi connected and working, copy /etc/network/interfaces.

anticapitalista wrote:While running live and with wifi connected and working, copy /etc/network/interfaces.

Started Live, configured the iface (working) and then mounted /mnt/sda1 (the installed system). The files /etc/network/interfaces are identical, no difference. The problem is not the configuration, it is the driver (Live = wl, Harddisk = br43). There must be a file where this is set and I wonder why it is different between Live and installed system.