No wireless Dell Inspiron

[clueless]

Hi,

I read Stoat's guide and before upgrading from FC14 to FC16 it worked well using kmod wl PAE. I had it up and running just after the first install. When I couldn't get Gnome 3 running I started playing with other desktops and killed my GUI. I re-installed FC16 and Gnome 3 appeared(weird). Why not the first time? That said my wireless wont work now. I have the BCM4312 chipset with the manual little slider on the side. It has been very temperamental in the past working and then not. I haven't had that luck this time.

Sean

[solo2101]

I had the same problem on my BCM4313...
I notice that the module does not load automacally on the kernel 3.x (at least on my case)


so I had to start it manually as suggested in the guide with the command
su
modprobe wl
why don't you wive it a try... it may work on your BCM4312.

[clueless]

Solo,

I tried it and got nothing back.

Sean

[solo2101]

do you have the driver installed?

[clueless]

Yep, I think so.Package kmod-wl-PAE-5.100.82.112-1.fc16.7.i686 already installed and latest version
Nothing to do

Sean

[amodkarmarkar]

yum install akmod-wl

restart

[clueless]

amodkarmarkar,

I have installed it and it still didn't work. Should I remove kmod though and try again?

Sean

[solo2101]

# lsmod | grep -i wl

is it even running?

[clueless]

Solo,

This is what I got back.


lsmod | grep -i wl
wl 2434512 0
lib80211 4418 1 wl


Sean

[solo2101]

do the su
modprobe wl
then do:

lsmod | grep -i wl


---------- Post added at 12:49 PM ---------- Previous post was at 12:48 PM ----------

sorry dint see that previous post

---------- Post added at 02:07 PM ---------- Previous post was at 12:49 PM ----------

try:

rmmod wl
rmmod bcma
modprobe wl

[clueless]

I am a little confused, though i have done this already. Anyway here goes.

[root@davis ~]# su
[root@davis ~]# modprobe wl
[root@davis ~]# lsmod | grep -i wl
wl 2434512 0
lib80211 4418 1 wl
[root@davis ~]#


Sean

[solo2101]

sorry for that...

try:

rmmod wl
rmmod bcma
modprobe wl

[clueless]

No problem, as you can tell, I don't know how to fix this. Here it is:


[root@davis ~]# rmmod wl
[root@davis ~]# rmmod wl
ERROR: Module wl does not exist in /proc/modules
[root@davis ~]# rmmod bcma
ERROR: Module bcma does not exist in /proc/modules
[root@davis ~]# modprobe wl


Sean

[amodkarmarkar]

clueless,
What error do you get when you click your wifi.
1: missing firmware
2: you dont see any wireless device
regards

amod

[clueless]

Amod,

I don't see any device. When I tried to configure one, I wont let me save the settings.

Sean

[amodkarmarkar]

Clueless.
remove both kmod-wl as well as akmod-wl.
yum remove kmod-wl*
yum remove akmod-wl*
restart

on restarting check weather you get the error missing firmware. (GUI)
if yes
yum install akmod-wl ...... only.
This should help

Regards

Amod.

[stoat]

You've already demonstrated in post #9 that the wl module was loaded at that moment and the wireless wasn't working. If the chipset is the BCM4312 as reported in post #1, then I would consider conflicting modules that may be listed by lsmod (several are known). Also consider rfkill (http://fedoraforum.org/forum/showthread.php?t=249577). And don't overlook a physical on-off switch for the wireless. That's not a slap in the face, it happens all the time.

[clueless]

Stoat,

I followed the advice posted by Akmod, I always check the slap in the face when I do a network restart. I did yours:

[root@davis ~]# lsmod
Module Size Used by
ppdev 6899 0
parport_pc 18302 0
lp 7646 0
parport 29655 3 ppdev,parport_pc,lp
fuse 60799 3
lockd 67393 0
nf_conntrack_ipv4 7530 2
nf_defrag_ipv4 1173 1 nf_conntrack_ipv4
ip6t_REJECT 3946 2
nf_conntrack_ipv6 7101 2
nf_defrag_ipv6 7759 1 nf_conntrack_ipv6
xt_state 1022 4
nf_conntrack 64156 3 nf_conntrack_ipv4,nf_conntrack_ipv6,xt_state
ip6table_filter 1283 1
ip6_tables 11164 1 ip6table_filter
wl 2434512 0
uvcvideo 58462 0
videodev 83008 1 uvcvideo
media 10319 2 uvcvideo,videodev
snd_hda_codec_idt 56263 1
snd_hda_intel 23025 4
snd_hda_codec 84779 2 snd_hda_codec_idt,snd_hda_intel
snd_hwdep 5396 1 snd_hda_codec
snd_seq 48285 0
snd_seq_device 5441 1 snd_seq
snd_pcm 74013 3 snd_hda_intel,snd_hda_codec
dell_wmi 1381 0
sparse_keymap 3290 1 dell_wmi
uinput 5946 0
joydev 7780 0
dell_laptop 7623 0
rfkill 14452 2 dell_laptop
dcdbas 6464 1 dell_laptop
microcode 11746 0
b44 24916 0
ssb 47433 1 b44
i2c_i801 8657 0
mii 4091 1 b44
r852 9553 0
sm_common 6672 1 r852
r592 10933 0
nand 43353 2 r852,sm_common
nand_ids 3822 1 nand
nand_ecc 3700 1 nand
mtd 27904 2 sm_common,nand
memstick 7951 1 r592
iTCO_wdt 10460 0
iTCO_vendor_support 2203 1 iTCO_wdt
snd_timer 17660 2 snd_seq,snd_pcm
snd 55194 15 snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_ hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer
soundcore 5892 1 snd
snd_page_alloc 6769 2 snd_hda_intel,snd_pcm
lib80211 4418 1 wl
sunrpc 191650 2 lockd
firewire_ohci 27130 0
sdhci_pci 8150 0
firewire_core 47789 1 firewire_ohci
sdhci 23308 1 sdhci_pci
crc_itu_t 1287 1 firewire_core
mmc_core 79378 2 ssb,sdhci
nouveau 688327 3
ttm 51896 1 nouveau
drm_kms_helper 26252 1 nouveau
drm 173005 5 nouveau,ttm,drm_kms_helper
i2c_algo_bit 4724 1 nouveau
i2c_core 23599 6 videodev,i2c_i801,nouveau,drm_kms_helper,drm,i2c_a lgo_bit
mxm_wmi 1395 1 nouveau
wmi 8357 2 dell_wmi,mxm_wmi
video 10744 1 nouveau
[root@davis ~]#

bash: rfkill: command not found...
[root@davis ~]#


I would love feedback.

Sean

[stoat]

Well, since wl is in the lsmod list, you can forget about all that yum this and yum that business IMO. The driver is installed and loaded. Something is stopping it from working. I mentioned a few possibilities earlier. For example, some people have had to blacklist the ssb driver for wl to work. You can try that, but know that the b44 module in your list depends on ssb which means blacklisting ssb will bust the wired NIC.

Next, you gave up too soon on the rfkill idea. As shown in the link I posted, you need to install that package to use it. I would install that and run those commands in that linked thread.

[Gödel]

blacklisting ssb will just mean you need to do 'modprobe b44' manually before you use the wired nic, if this is infrequent then it should not be a problem.

i've got this in /etc/modprobe.d/blacklist.conf

blacklist b43-pci-bridge
blacklist ssb
blacklist b44

try that, then on reboot wl should work with the wireless device. (you may not need to blacklist all three modules but this has worked for me since ~F11)

there is an alternative fix to enable both b44 and wl to load automatically, see http://forums.fedoraforum.org/showthread.php?t=230669

[amodkarmarkar]

Then may be selinux.
Once i had the same problem. it gor solved as i made selinux permissive. Still dont know why.

regards

Amod

[clueless]

Well, since wl is in the lsmod list, you can forget about all that yum this and yum that business IMO. The driver is installed and loaded. Something is stopping it from working. I mentioned a few possibilities earlier. For example, some people have had to blacklist the ssb driver for wl to work. You can try that, but know that the b44 module in your list depends on ssb which means blacklisting ssb will bust the wired NIC.

Next, you gave up too soon on the rfkill idea. As shown in the link I posted, you need to install that package to use it. I would install that and run those commands in that linked thread.

Stoat,
I missed that you actually had left a link to a previous post. I have installed it and I think that the reply is what is desired.

Complete!
[root@davis ~]# rfkill list
0: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no

That said, I am beginning to think more and more that I need to go back and learn Linux the right way. Reading some from the ground up literature that I can fill in the gaps I have(many). When I read Godel's post and his solution I felt out of my depth. I have never installed the wrapper and it worked briefly in FC16 using kmod-wl-PAE. I appreciate the feedback.

Sean

P.S. On a related note, I fall foul of, "my box works more than 99% of the time". I love the stability speed and absence of viruses(and its free). But being a school teacher in a windows environment, I have little time to learn a new language be competent and fluent. I would love your advice on the literature anyhow.

[stoat]

[root@davis ~]# rfkill list
0: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: noSo it's not that.



When I read Godel's post and his solution I felt out of my depth.Well, try testing the idea with a simple experiment...su
modprobe -r ssb
systemctl restart NetworkManagerWait a several seconds for NM to react. Check NM for available networks.


P.S.: If that didn't help either, then take a moment to describe exactly what is wrong. I started reading again from the beginning of this thread, and it isn't exactly clear or specific about what the problem is. Are there no networks listed in NM when some are known to be in range? Are there networks listed, but you can't connect? Is it connecting, but not staying connected very long? Is the wireless connected to the access point, but you can't navigate to a web site with Firefox? You know, things like that.

[Colors]

Try installing b43-openfwwf packet and remove kmod-wl then restart.

[clueless]

So it's not that.

Well, try testing the idea with a simple experiment...su
modprobe -r ssb
systemctl restart NetworkManagerWait a several seconds for NM to react. Check NM for available networks.


P.S.: If that didn't help either, then take a moment to describe exactly what is wrong. I started reading again from the beginning of this thread, and it isn't exactly clear or specific about what the problem is. Are there no networks listed in NM when some are known to be in range? Are there networks listed, but you can't connect? Is it connecting, but not staying connected very long? Is the wireless connected to the access point, but you can't navigate to a web site with Firefox? You know, things like that.

Stoat,

Thank you for the reply. Herewith a brief summary and a reply to the code and surprise another question. I installed FC16 and got the wl working with kmod-wl-PAE right from the start. It showed the adapter let me configure etc but it never actually connected. It did sow everyone in the neighbour hood too. Since I was in Gnome fall back, I started messing with some other environments and killed my GUI. Since it was just day two of my install, I simply did a fresh install again. To my complete surprise my second install Gnome 3 was up but no wl.

[root@davis ~]# su
[root@davis ~]# modprobe -r ssb
FATAL: Module ssb is in use.
[root@davis ~]# systemctl restart NetworkManager
Failed to issue method call: Unit name NetworkManager is not valid.
[root@davis ~]#

I have tried removing kmod with the remove and erase command in yum but can't.

[root@davis ~]# yum remove kmod-wl
Loaded plugins: langpacks, presto, refresh-packagekit
Setting up Remove Process
No Match for argument: kmod-wl
No Packages marked for removal
[root@davis ~]# yum erase kmod-wl-PAE
Loaded plugins: langpacks, presto, refresh-packagekit
Setting up Remove Process
No Match for argument: kmod-wl-PAE
No Packages marked for removal
[root@davis ~]# yum erase kmod-wl
Loaded plugins: langpacks, presto, refresh-packagekit
Setting up Remove Process
No Match for argument: kmod-wl
No Packages marked for removal

Sean

[stoat]

First, don't bother trying that b43-openfwwf package as suggested above. That is firmware for the kernel's b43 wireless driver module. It would do no harm to install it, but according to the OpenFWWF website (http://www.ing.unibs.it/~openfwwf/), it isn't known to work with your BCM4312 chipset. The b43 driver does work with the BCM4312 if you use firmware extracted from a proprietary driver. But for now, I recommend that you continue on with broadcom-wl. You've already proven that broadcom-wl works with the adapter, so I would stay with it until the bitter hopeless end. Then it would be a good idea to change course and try b43.

Next, based on those failed attempts to uninstall the driver, I now wonder if the thing is even installed. Anyway, it happens all the time after a kernel update. Take a moment to establish what is and is not installed and version of the running kernel...rpm -qa | grep -e kernel -e kmod-wl -e broadcom-wl | sort
uname -r

[clueless]

Stoat,

[root@davis ~]# rpm -qa | grep -e kernel -e kmod-wl -e broadcom-wl | sort

abrt-addon-kerneloops-2.0.7-2.fc16.i686
broadcom-wl-5.100.82.112-2.fc16.noarch
kernel-headers-3.1.6-1.fc16.i686
kernel-PAE-3.1.5-2.fc16.i686
kernel-PAE-3.1.5-6.fc16.i686
kernel-PAE-3.1.6-1.fc16.i686
kernel-PAE-devel-3.1.5-2.fc16.i686
kernel-PAE-devel-3.1.5-6.fc16.i686
kernel-PAE-devel-3.1.6-1.fc16.i686
kmod-wl-3.1.5-2.fc16.i686.PAE-5.100.82.112-1.fc16.6.i686
kmod-wl-3.1.5-6.fc16.i686.PAE-5.100.82.112-1.fc16.7.i686
kmod-wl-3.1.6-1.fc16.i686.PAE-5.100.82.112-1.fc16.8.i686
libreport-plugin-kerneloops-2.0.8-3.fc16.i686
[root@davis ~]# uname -r
3.1.5-6.fc16.i686.PAE


Sean

[bbfuller]

Hello clueless,

According to your list, you are missing a package.

You should have:

kmod-wl-PAE-5.100.82.112-1.fc16.i686.rpm

installed as well.

The command:

yum install kmod-wl-PAE

should have brought in three packages.

Two you already have installed:

broadcom-wl-5.100.82.112-2.fc16.noarch
kmod-wl-3.1.5-6.fc16.i686.PAE-5.100.82.112-1.fc16.7.i686

and the one I've listed above.

[clueless]

bbfuller,

I have and still no joy. I even restarted.

Sean

[solo2101]

I would start fresh again... maybe removing every package that this command shows:

#rpm -qa | grep -e kmod-wl -e broadcom

#kmod-wl-Blah.Blah.Blah
#bradcom-wl-Blah.Blah.Blah
#more-blah.blah.blah


then:

#rpm -e <package name>

[bbfuller]

That's a possibility.

You might also try:

lsmod | grep wl

to assure us that the "wl" module is loading, and if it is:

dmesg | grep wl

and

dmesg | grep wireless

to see if we can trap any error messages as the driver tries to load.

I've had people who expect those commands to make the card work. They won't. They are only diagnostics designed to provide information.

I assume from your previous post:

I have and still no joy.

That you actually installed:

kmod-wl-PAE-5.100.82.112-1.fc16.i686.rpm

somehow? You're not very clear on that.

[clueless]

[root@davis Desktop]# lsmod | grep wl
wl 2434512 0
lib80211 3955 1 wl


[root@davis Desktop]# dmesg | grep wl
[ 28.489827] wl: module license 'MIXED/Proprietary' taints kernel.


[root@davis Desktop]# dmesg | grep wireless
[root@davis Desktop]# dmesg | grep wireless
[root@davis Desktop]#


Package kmod-wl-PAE-5.100.82.112-1.fc16.8.i686 already installed and latest version
Nothing to do


I hope that helps. I am interested in the tainted bit.
Sean

[bbfuller]

Hello clueless,

The "tainted" message you are seeing is nothing to be concerned about. It just means that the module being loaded is a proprietary module and not completely free.

I don't actually have a broadcom-wl installation to play with at the moment, but I would have half expected more output from the "dmesg" command. I'll see if I can run up something to compare later today.

Meanwhile, I see that you have a module "dell_wmi" loading.

There was a time about six months back that a similar module "acer_wmi" was having all sorts of odd effects on wireless.

It might be worth trying editing the file:

/etc/modprobe.d/blacklist.conf

and adding:

blacklist dell_wmi

at the end of it. Reboot and see what happens.

If you are going to do that though, make sure you are happy editing that file at the command line so that you can take the line out if it has unintended consequences.

Also remove it if it doesn't do any good. These changes we make can sometimes have unintended, cumulative, consequences if left in place.

Incidentally, I don't think anyone has asked, but does:

iwconfig

show a wireless interface being formed?

---------- Post added at 11:47 AM ---------- Previous post was at 10:47 AM ----------

I've just tried:

yum install akmod-wl

and it's working perfectly.

Thing is though, when it installed it wrote a blacklist file that specifically blacklisted the "ssb" module among others.

I see that in your output from lsmod the ssb module is still in place.

So, how did you install these broadcom-wl packages, and do you have a file:

broadcom-wl-blacklist.conf

in the folder:

/etc/modprobe.d

[clueless]

bbfuller,

I got a little confused with your post since it had an addition. Herewith an answer to some of it.


[root@davis Desktop]# iwconfig
lo no wireless extensions.

em1 no wireless extensions.

I am not sure if you saw in some previous posts I have been unable to remove kmod-wl, so I am wondering what will happen if I install the akmod. Also, I just want to make sure, you say

"If you are going to do that though, make sure you are happy editing that file at the command line so that you can take the line out if it has unintended consequences.

Also remove it if it doesn't do any good. These changes we make can sometimes have unintended, cumulative, consequences if left in place."
I guess I can do it and change back. So really, my question is about the existing driver and removing it and if I understood your editing in the command line question.

Sean

[solo2101]

rpm -e broadcom-wl-5.100.82.112-2.fc16.noarch
rpm -e kmod-wl-3.1.6-1.fc16.i686.PAE-5.100.82.112-1.fc16.8.i686
rpm -e kmod-wl-3.1.5-6.fc16.i686.PAE-5.100.82.112-1.fc16.7.i686
rpm -e kmod-wl-3.1.5-2.fc16.i686.PAE-5.100.82.112-1.fc16.6.i686
that will remove the packages, I got that from one of your posts, to make sure you are removing every wireless related package run:
rpm -qa | grep -e kmod-wl -e broadcom

[clueless]

solo,

I assume there is no point to following Verndogs blacklist advice if I have removed the packages you suggested. Sad news however, it is still not working with akmod. I just restarted.

Sean

[solo2101]

you can always reinstall

[clueless]

Solo,

Reinstall what ? The whole bangshoot FC 16 fresh install?

Sean

[solo2101]

the drivers

[clueless]

Solo,

Where would you start and what would you install?
Sean

[bbfuller]

Hello clueless,

My earlier posts would have been best if the forum software would have left them as two separate posts. Unfortunately, it insists on amalgamating them.

The point of it was that I had a little spare time so I did an install of the broadcom-wl driver for myself.

No consolation for you that it worked easily on my machine.

However what mystifies me is that in your post #18 0n 24 December the output of lsmod clearly shows the "ssb" module loading.

The installation of the kmod-wl package is supposed to create a blacklist file to stop that happening.

My question was, do you have the blacklist file in place:

/etc/modprobe.d/broadcom-wl-blacklist.conf

and I suppose, if you do, what are the lines in it?

[clueless]

bbfuller,

I am now well lost and confused.


[root@davis ~]# /etc/modprobe.d/broadcom-wl-blacklist.conf
-bash: /etc/modprobe.d/broadcom-wl-blacklist.conf: Permission denied
[root@davis ~]# /etc/modprobe.d
-bash: /etc/modprobe.d: Is a directory
[root@davis ~]#


Sean

[bbfuller]

Hello clueless,

Nowhere did I say try to run that as a command.

Firstly you should be using a file manager and looking in the folder specified to see if the file is there.

If it is you should be using a text editor to look into the file and see what is there.

[clueless]

bbfuller,

the clueless moniker wasn't for nothing. It was the third txt document

# modules blacklisted for broadcom-wl
blacklist ssb
blacklist bcma
blacklist b43
blacklist brcmsmac

Sean