Dear All,
I'm trying to configure wireless card on a Dell Vostro 1540.
I had a look at this site :
http://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom?action=show
wireless card :# /sbin/lspci | grep Broadcom
12:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless
LAN Controller (rev 01)
I decided to follow the ELrepo instructions suggested on the site :
http://elrepo.org/tiki/wl-kmod
because it would give me a clear and present rpm that I can use on different
machines and that will survive kernel updates.
This all goes down without error messages.
After installing, there is a new entry in
/etc/udev/rules.d/70-persistent-net.rules :
# PCI device 0x14e4:0x4727 (wl)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="94:39:e5:dc:3a:cf", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth1"
and there is now a blacklist-Broadcom.conf in /etc/modprobe.d/:
blacklist b43
blacklist b43legacy
blacklist bcm43xx
blacklist ssb
So I think the driver works and the blacklist - issue that is reported on
different sites is ok.
I then made an entry in /etc/sysconfig/network-scripts:
vi ifcfg-eth1
DEVICE="eth1"
#BOOTPROTO="dhcp"
HWADDR="94:39:e5:dc:3a:cf"
NM_CONTROLLED="yes"
ONBOOT="yes"
TYPE=Wireless
*The problem is* I'm not seeing any wireless networks.
Eth1 seems to try to get an adress via dhcp and then exits.
And it is listed in the gui as wired network...
[root at wduerloo ~]# dmesg | tail -n15
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
wl: module license 'unspecified' taints kernel.
Disabling lock debugging due to kernel taint
wl 0000:12:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
wl 0000:12:00.0: setting latency timer to 64
lib80211_crypt: registered algorithm 'TKIP'
eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller 5.100.82.112
eth1: no IPv6 routers present
eth1: no IPv6 routers present
eth1: no IPv6 routers present
eth1: no IPv6 routers present
eth1: no IPv6 routers present
on restarting network manager this is in /var/log/messages :
Nov 8 07:45:54 wduerloo dhclient[11719]: DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 6 (xid=0x3c613d0e)
Nov 8 07:46:00 wduerloo dhclient[11719]: DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 12 (xid=0x3c613d0e)
Nov 8 07:46:12 wduerloo dhclient[11719]: DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 14 (xid=0x3c613d0e)
Nov 8 07:46:26 wduerloo dhclient[11719]: DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 12 (xid=0x3c613d0e)
Nov 8 07:46:33 wduerloo NetworkManager[11711]:<warn> (eth1): DHCPv4
request timed out.
Nov 8 07:46:33 wduerloo NetworkManager[11711]:<info> (eth1): canceled
DHCP transaction, DHCP client pid 11719
Nov 8 07:46:33 wduerloo NetworkManager[11711]:<info> Activation (eth1)
Stage 4 of 5 (IP4 Configure Timeout) scheduled...
Nov 8 07:46:33 wduerloo NetworkManager[11711]:<info> Activation (eth1)
Stage 4 of 5 (IP4 Configure Timeout) started...
Nov 8 07:46:33 wduerloo NetworkManager[11711]:<info> Activation (eth1)
Stage 5 of 5 (IP Configure Commit) scheduled...
Nov 8 07:46:33 wduerloo NetworkManager[11711]:<info> Activation (eth1)
Stage 4 of 5 (IP4 Configure Timeout) complete.
Nov 8 07:46:33 wduerloo NetworkManager[11711]:<info> Activation (eth1)
Stage 5 of 5 (IP Configure Commit) started...
Nov 8 07:46:33 wduerloo NetworkManager[11711]:<info> Activation (eth1)
Stage 5 of 5 (IP Configure Commit) failed (no IP configuration found)
Nov 8 07:46:33 wduerloo NetworkManager[11711]:<info> (eth1): device
state change: 7 -> 9 (reason 5)
Nov 8 07:46:33 wduerloo NetworkManager[11711]:<info> Marking connection
'Auto eth1' invalid.
Nov 8 07:46:33 wduerloo NetworkManager[11711]:<warn> Activation (eth1)
failed.
Nov 8 07:46:33 wduerloo NetworkManager[11711]:<info> Activation (eth1)
Stage 5 of 5 (IP Configure Commit) complete.
Nov 8 07:46:33 wduerloo NetworkManager[11711]:<info> (eth1): device
state change: 9 -> 3 (reason 0)
Nov 8 07:46:33 wduerloo NetworkManager[11711]:<info> (eth1):
deactivating device (reason: 0).
I think I need to configure something else.
I know a lot of you guys don't like NetworkManager but because it's a
laptop I would like to use it.
I hope I gave enough info, any help would be greatly appreciated.
greetings, James.
Centos is here to stay, I'm sure.
P.S. I don't have an English spell checker on this machine, sorry for
language mistakes :=)
Johan Vermeulen
IT-medewerker
Caw De Kempen
johan.vermeulen at cawdekempen.be
0479.82.01.41
Opensource Software is the future.
Ljubomir Ljubojevic
2011-Nov-08 10:59 UTC
[CentOS] Fwd: centos Wireless - Broadcom BCM4313
Vreme: 11/08/2011 07:59 AM, Johan Vermeulen pi?e:> Dear All, > > I'm trying to configure wireless card on a Dell Vostro 1540. > > I had a look at this site : http://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom?action=show > > wireless card :# /sbin/lspci | grep Broadcom > 12:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01) > > I decided to follow the ELrepo instructions suggested on the site : > > http://elrepo.org/tiki/wl-kmod > > because it would give me a clear and present rpm that I can use on different machines and that will survive kernel updates.This is good choice many of us recommend as best solution. Question: This is CentOS 6? i386 or x86_64?> > This all goes down without error messages.You downloaded appropriate firmware and compiled all of it?> > After installing, there is a new entry in /etc/udev/rules.d/70-persistent-net.rules : > > # PCI device 0x14e4:0x4727 (wl) > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="94:39:e5:dc:3a:cf", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" > > and there is now a blacklist-Broadcom.conf in /etc/modprobe.d/: > > blacklist b43 > blacklist b43legacy > blacklist bcm43xx > blacklist ssb > > So I think the driver works and the blacklist - issue that is reported on different sites is ok.What does "iwlist" command give you? Have you installed all other packages needed for wireless?> > I then made an entry in /etc/sysconfig/network-scripts: > > vi ifcfg-eth1Change the name to ifcfg-wlan0> > DEVICE="eth1"Change to DEVICE="wlan0"> #BOOTPROTO="dhcp" > HWADDR="94:39:e5:dc:3a:cf" > NM_CONTROLLED="yes" > ONBOOT="yes" > TYPE=WirelessAdd this: USERCTL=yes IPV6INIT=no Why is BOOTPROTO disabled?> > *The problem is* I'm not seeing any wireless networks. ><snip>> > I think I need to configure something else.wpa-suplicant?> > I know a lot of you guys don't like NetworkManager but because it's a laptop I would like to use it. > > I hope I gave enough info, any help would be greatly appreciated. > > greetings, James. > > Centos is here to stay, I'm sure. > > P.S. I don't have an English spell checker on this machine, sorry for language mistakes :=)Do not worry about it, most native speaking English don't bother to write correctly. -- Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe Google is the Mother, Google is the Father, and traceroute is your trusty Spiderman... StarOS, Mikrotik and CentOS/RHEL/Linux consultant