[SOLVED] fedora 16 3.1.0-7.fc16.x86_64

[robiro]

Hello guys, I am new to fedora.
I have just installed Fedora KDE spin 64 .

I realized that it is not picking my broadcom 4313 network adapter, thus I don't have wireless connection.

after issuing uname -r in terminal I got this
3.1.0-7fc16.x86_64 and network adapter is Broadcom 4313 82.11 b/g/n .

Please, help me install the necessary drivers!!!

thanks a lottt!!!

[DBelton]

try reading through this thread and see if it answers your questions

http://forums.fedoraforum.org/showthread.php?t=239922

[hadrons123]

if that is too confusing

https://wiki.archlinux.org/index.php/Wireless_Setup

try this...

[Mariusz W]

Originally Posted by hadrons123

if that is too confusing

http://<b>https://wiki.archlinux.org...less_Setup</b>

try this...

You gave a reference to perhaps a wonderfully written piece of documentation but it is going to be confusing to a new Fedora user as hell! Several utilities, daemons etc described on the Arch Linux wiki page are not even part of a default Fedora installation.

[fdrake]

Originally Posted by robiro

Hello guys, I am new to fedora.
I have just installed Fedora KDE spin 64 .

I realized that it is not picking my broadcom 4313 network adapter, thus I don't have wireless connection.

after issuing uname -r in terminal I got this
3.1.0-7fc16.x86_64 and network adapter is Broadcom 4313 82.11 b/g/n .

Please, help me install the necessary drivers!!!

thanks a lottt!!!

plug in the adapter and type in the terminal:

lsusb
lshw -c network
ifconfig
iwconfig
rfkill list all

post the outputs , and will start from there.

edit:
i just checked now http://forums.fedoraforum.org/showthread.php?t=239922 (DBelton's link) and that is pretty self explainatory , i highly suggest it to you , but first i want to check ifyour adapter shows up in the hardware list.

[hadrons123]

hi Mariusz W,
you are probably right.But i wasted too much time while i was new to fedora with Dbelton's link.
the arch's wiki page was lot easier for me at that time.

that's why supplemented another link.

[DBelton]

it's fairly clear once you determine what broadcom chip you have, and then exclude the portions of the guide for the other chipsets.

If you don't know exactly what chipset your adapter has and try to take in the entire guide, then, yes, it can be very confusing.

Actually, the OP has already determined that he has the broadcom 4313, so he need to use only the portion of the guide for the broadcom-wl driver.

[robiro]

thanks a lot guys... I haven't had the chance of going through the process of checking and downloading today... I will do it tomorrow I will get back to you...
Thanks everyone, again!!!!

[robiro]

this is my outpout


[robiro@robiro ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 5986:0149 Acer, Inc
[robiro@robiro ~]$ lshw -c network
bash: lshw: command not found
[robiro@robiro ~]$ ifconfig
em1 Link encap:Ethernet HWaddr 3C:4A:927:67:4C
inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::3e4a:92ff:fec7:674c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:40445 errors:0 dropped:0 overruns:0 frame:0
TX packets:22857 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:58500220 (55.7 MiB) TX bytes:1878554 (1.7 MiB)
Interrupt:42 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:167 errors:0 dropped:0 overruns:0 frame:0
TX packets:167 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11779 (11.5 KiB) TX bytes:11779 (11.5 KiB)

[robiro@robiro ~]$ iwconfig
lo no wireless extensions.

em1 no wireless extensions.

[robiro@robiro ~]$ rfkill list all
bash: rfkill: command not found
[robiro@robiro ~]$

Originally Posted by fdrake

plug in the adapter and type in the terminal:

lsusb
lshw -c network
ifconfig
iwconfig
rfkill list all

post the outputs , and will start from there.

edit:
i just checked now http://forums.fedoraforum.org/showthread.php?t=239922 (DBelton's link) and that is pretty self explainatory , i highly suggest it to you , but first i want to check ifyour adapter shows up in the hardware list.

[DBelton]

lspci should tell you what wireless card you have, in case you were not certain when you said it was a broadcom 4313.

lspci

[robiro]

yes it is 4313
how shall i proceed afterwards??

Originally Posted by DBelton

lspci should tell you what wireless card you have, in case you were not certain when you said it was a broadcom 4313.

lspci

[fdrake]

you did not get very promising results from your last post, some due to not installed programs. Follow the post about "lspci" command and post here. also i would suggest you to install the other programs for future troubleshooting. Quick question: Is yours an USb- dapter, or not?

sudo yum install rfkill lshw

[solo2101]

if you already install the drivers with:

yum install akmod-wl

try

lsmod | sort

if you dont see a "wl", that meas that the "service" as not been started

try

su
echo "modprobe wl" >> /etc/rc.local

and then reboot.

[jeffjohnson123]

OMG! Just installed Fedora 16. Horrible !! Absolutely the worst upgrade of Fedora ever! (I've been using since FC2).
Too much influence from IBM it appears.
RIP Fedora.

[DBelton]

How do you figure it was influence from IBM?

From what I can tell, when some of these changes hit RHEL, IBM is going to drop it like a hot potato (along with just about all of the US govt. systems as well)