Dell lattitude D620 cant connect [Solved]

[Fitzcarraldo]

0c:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)

^There's your WiFi controller. Do the following:

1, Add the line "blacklist wl" (without the quotes) to the file /etc/modprobe.d/blacklist.conf
(Either log-in as root user and use the command "nano /etc/modprobe.d/blacklist.conf" (without the quotes) to edit the file, or alternatively use the command "kdesu kwrite /etc/modprobe.d/blacklist.conf" (without the quotes) from your own user account and enter the root user's password when prompted.)

2. Log in as root user and install the package b43-firmware:

Code: Select all

equo install b43-firmware

3. Log in as root user and enter the command "rmmod wl" (without the quotes) to unload the wl module.

4. Log in as root user and enter the command "modprobe b43" (without the quotes) to load the b43 module.

If wireless begins working after you loaded the module, to make it load automatically at start-up in future edit the file /etc/conf.d/modules and add the module name to the list of modules in the line modules="<a list of modules>". (NOTE: A hash (#) symbol at the beginning of a line denotes it as a comment, which is therefore ignored by Linux.) So, for example, if you wanted to load the modules vboxdrv, vboxnetflt, vboxnetadp and b43 at start-up, then the contents of the file /etc/conf.d/modules would look like this:

Code: Select all

modules="vboxdrv vboxnetflt vboxnetadp b43"

If you only wanted to load the b43 module, the line would look like this instead:

Code: Select all

modules="b43"

Ref.: Long pause at 'Waiting for uevents to be processed' [Solved].

[niknik242]

It says module wl is in use

[niknik242]

Nevermind, got it

[niknik242]

Thanks! You helped me and you stopped my dad from returning to ubuntu!

[Fitzcarraldo]

You're welcome.

Something to bear in mind: Sometimes, when you 'roll' the distribution forwards (equo update && equo upgrade && equo conf update) you may find that the file /etc/modprobe.d/blacklist.conf has been overwritten by a new version. In that case you'll need to re-blacklist the wl module.

Regarding unloading a module that is in use, it is possible to use the --force (-f) parameter:

Code: Select all

rmmod -f wl