I have a Broadcom 802.11b/g hardware on my dual-boot laptop. Note first that in the WinXP partition, the wifi makes DHCP connections to my router with no problem. Since this was not working in my new CentOS 6 partition, and remembering that there was a driver problem with the old Fedora partition it replaced, I followed instructions founs at:
http://repecka.net/en/2011/04/19/install-broadcom-bcm4311-802-11bg-wlan- drivers-on-centos/
and
http://www.broadcom.com/docs/linux_sta/README.txt
modifying for that fact that I use wlan0 rather than eth1. The wifi is now dead-in-the-water. The wlan light now remains red, and neither ifconfig nor iwconfig show any sign of wlan0 (contra to the situation before I installed the new driver). It still works in the WinXP partition.
Suggestions for my next step in fixing this would be most welcome.
Thank, Mike.
On Mon, 2011-09-05 at 17:27 +0000, Michael D. Berger wrote:
I have a Broadcom 802.11b/g hardware on my dual-boot laptop. Note first that in the WinXP partition, the wifi makes DHCP connections to my router with no problem. Since this was not working in my new CentOS 6 partition, and remembering that there was a driver problem with the old Fedora partition it replaced, I followed instructions founs at:
http://repecka.net/en/2011/04/19/install-broadcom-bcm4311-802-11bg-wlan- drivers-on-centos/
and
http://www.broadcom.com/docs/linux_sta/README.txt
modifying for that fact that I use wlan0 rather than eth1. The wifi is now dead-in-the-water. The wlan light now remains red, and neither ifconfig nor iwconfig show any sign of wlan0 (contra to the situation before I installed the new driver). It still works in the WinXP partition.
Suggestions for my next step in fixing this would be most welcome.
Thank, Mike.
Maybe you need to install the firmware? My laptop still uses the b43 driver but not entirely w/o issue.
# yum search b43
<snip> ================================= Matched: b43 ================================= b43-fwcutter.x86_64 : Firmware extraction tool for Broadcom wireless driver b43-tools.x86_64 : Tools for the Broadcom 43xx series WLAN chip b43-openfwwf.noarch : Open firmware for some Broadcom 43xx series WLAN chips compat-db43.i686 : The Berkeley DB database 4.3.29 compatibility library compat-db43.x86_64 : The Berkeley DB database 4.3.29 compatibility library
HTH
B.J. CentOS Linux release 6.0 (Final)
On Mon, 05 Sep 2011 13:47:43 -0400, b.j. mcclure wrote:
[...]
Maybe you need to install the firmware? My laptop still uses the b43 driver but not entirely w/o issue.
# yum search b43
[...]
The instructions mentioned above include removing b43 and replacing it with something downloaded from Broadcom.
Mike.
On Mon, 2011-09-05 at 17:58 +0000, Michael D. Berger wrote:
On Mon, 05 Sep 2011 13:47:43 -0400, b.j. mcclure wrote:
[...]
Maybe you need to install the firmware? My laptop still uses the b43 driver but not entirely w/o issue.
# yum search b43
[...]
The instructions mentioned above include removing b43 and replacing it with something downloaded from Broadcom.
Mike.
Yes, I'm aware of that, however, the driver is useless without the firmware installed. Whether the native CentOS 6 firmware package will work with your driver is a question I cannot answer. I see no reference in the link you posted about firmware but since it discusses removing and blacklisting the b43 driver I would guess the are assuming the firmware is installed.
I would start with native packages in CentOS 6 and if operation is unsatisfactory then seek another solution.
Just my $0.02.
CentOS Linux release 6.0 (Final)
On Mon, 05 Sep 2011 14:11:21 -0400, b.j. mcclure wrote:
[...]
I would start with native packages in CentOS 6 and if operation is unsatisfactory then seek another solution.
Yes, the native packages didn't work and I am mow seeking "another solution". They did show the presence of wlan0, but they would not connect.
Mike.
On Mon, 2011-09-05 at 18:26 +0000, Michael D. Berger wrote:
On Mon, 05 Sep 2011 14:11:21 -0400, b.j. mcclure wrote:
[...]
I would start with native packages in CentOS 6 and if operation is unsatisfactory then seek another solution.
Yes, the native packages didn't work and I am mow seeking "another solution". They did show the presence of wlan0, but they would not connect.
Mike.
Could you please post the output of the following:
rpm -qa | grep fwcutter
lspci
lsmod
Thanks.
B.J.
CentOS Linux release 6.0 (Final)
On Mon, 05 Sep 2011 14:59:28 -0400, b.j. mcclure wrote:
On Mon, 2011-09-05 at 18:26 +0000, Michael D. Berger wrote:
On Mon, 05 Sep 2011 14:11:21 -0400, b.j. mcclure wrote:
[...]
I would start with native packages in CentOS 6 and if operation is unsatisfactory then seek another solution.
Yes, the native packages didn't work and I am mow seeking "another solution". They did show the presence of wlan0, but they would not connect.
Mike.
Could you please post the output of the following:
rpm -qa | grep fwcutter
lspci
lsmod
Thanks.
B.J.
Thanks for your interest. I hope it is not more than you expected.
rpm -qa | grep fwcutter: b43-fwcutter-012-2.2.el6.i686
lspci: 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 02) 00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (rev 02) 00:1d.0 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 02) 00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02) 00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02) 00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 02) 02:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01) 05:05.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller 05:05.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19) 05:05.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 01) 05:05.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a) 05:05.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05) 05:08.0 Ethernet controller: Intel Corporation PRO/100 VE Network Connection (rev 02)
lsmod: Module Size Used by sit 8292 0 tunnel4 2089 1 sit sunrpc 197617 1 cpufreq_ondemand 8454 2 acpi_cpufreq 7416 1 nf_conntrack_ipv4 7700 29 nf_defrag_ipv4 1013 1 nf_conntrack_ipv4 ipt_REJECT 1905 1 ipt_LOG 4835 9 xt_iprange 1842 2 iptable_filter 2147 1 ip_tables 9541 1 iptable_filter ip6t_REJECT 3961 2 nf_conntrack_ipv6 16198 2 xt_state 1006 31 nf_conntrack 66010 3 nf_conntrack_ipv4,nf_conntrack_ipv6,xt_state ip6table_filter 2219 1 ip6_tables 10809 1 ip6table_filter ipv6 264890 37 sit,ip6t_REJECT,nf_conntrack_ipv6 dm_mirror 11620 0 dm_region_hash 10127 1 dm_mirror dm_log 8520 2 dm_mirror,dm_region_hash wmi 5189 0 e100 27825 0 mii 4289 1 e100 sg 24778 0 i2c_i801 9222 0 iTCO_wdt 9324 0 iTCO_vendor_support 2382 1 iTCO_wdt wl 2635904 0 lib80211 4858 1 wl snd_hda_codec_conexant 28491 1 snd_hda_intel 21333 3 snd_hda_codec 70277 2 snd_hda_codec_conexant,snd_hda_intel snd_hwdep 5320 1 snd_hda_codec snd_seq 46091 0 snd_seq_device 5354 1 snd_seq snd_pcm 67225 2 snd_hda_intel,snd_hda_codec snd_timer 18308 2 snd_seq,snd_pcm snd 52754 14 snd_hda_codec_conexant,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer soundcore 6460 1 snd snd_page_alloc 7080 2 snd_hda_intel,snd_pcm ext4 322671 3 mbcache 5918 1 ext4 jbd2 73876 1 ext4 aes_i586 7208 2 aes_generic 26803 1 aes_i586 xts 1907 1 gf128mul 7923 1 xts dm_crypt 10848 1 firewire_ohci 21090 0 firewire_core 42630 1 firewire_ohci crc_itu_t 1343 1 firewire_core sdhci_pci 5714 0 sdhci 17819 1 sdhci_pci mmc_core 61320 1 sdhci sr_mod 14187 0 cdrom 34036 1 sr_mod sd_mod 33344 3 crc_t10dif 1191 1 sd_mod ata_generic 2555 0 pata_acpi 2487 0 ata_piix 19016 2 i915 290879 2 drm_kms_helper 29029 1 i915 drm 163291 3 i915,drm_kms_helper i2c_algo_bit 4600 1 i915 i2c_core 25799 5 i2c_i801,i915,drm_kms_helper,drm,i2c_algo_bit video 16662 1 i915 output 1779 1 video dm_mod 63827 14 dm_mirror,dm_log,dm_crypt
[...]
I note that if I do: /etc/init.d/network restart wlan0 is does not appear in the output.
Mike.
On Mon, 05 Sep 2011 19:55:40 +0000, Michael D. Berger wrote:
[...]
I note that if I do: /etc/init.d/network restart wlan0 is does not appear in the output.
Mike.
But if I modify ifcfg-wlan0 so that wlan0 should start on boot, /etc/init.d/network restart results in "...wlan0:...No suitable device found..."
Mike.
On Mon, 2011-09-05 at 19:28 +0000, Michael D. Berger wrote:
On Mon, 05 Sep 2011 14:59:28 -0400, b.j. mcclure wrote:
On Mon, 2011-09-05 at 18:26 +0000, Michael D. Berger wrote:
On Mon, 05 Sep 2011 14:11:21 -0400, b.j. mcclure wrote:
[...]
I would start with native packages in CentOS 6 and if operation is unsatisfactory then seek another solution.
Yes, the native packages didn't work and I am mow seeking "another solution". They did show the presence of wlan0, but they would not connect.
Mike.
Could you please post the output of the following:
rpm -qa | grep fwcutter
lspci
lsmod
Thanks.
B.J.
Thanks for your interest. I hope it is not more than you expected.
rpm -qa | grep fwcutter: b43-fwcutter-012-2.2.el6.i686
lspci: 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 02) 00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (rev 02) 00:1d.0 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 02) 00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02) 00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02) 00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 02) 02:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01) 05:05.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller 05:05.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19) 05:05.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 01) 05:05.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a) 05:05.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05) 05:08.0 Ethernet controller: Intel Corporation PRO/100 VE Network Connection (rev 02)
lsmod: Module Size Used by sit 8292 0 tunnel4 2089 1 sit sunrpc 197617 1 cpufreq_ondemand 8454 2 acpi_cpufreq 7416 1 nf_conntrack_ipv4 7700 29 nf_defrag_ipv4 1013 1 nf_conntrack_ipv4 ipt_REJECT 1905 1 ipt_LOG 4835 9 xt_iprange 1842 2 iptable_filter 2147 1 ip_tables 9541 1 iptable_filter ip6t_REJECT 3961 2 nf_conntrack_ipv6 16198 2 xt_state 1006 31 nf_conntrack 66010 3 nf_conntrack_ipv4,nf_conntrack_ipv6,xt_state ip6table_filter 2219 1 ip6_tables 10809 1 ip6table_filter ipv6 264890 37 sit,ip6t_REJECT,nf_conntrack_ipv6 dm_mirror 11620 0 dm_region_hash 10127 1 dm_mirror dm_log 8520 2 dm_mirror,dm_region_hash wmi 5189 0 e100 27825 0 mii 4289 1 e100 sg 24778 0 i2c_i801 9222 0 iTCO_wdt 9324 0 iTCO_vendor_support 2382 1 iTCO_wdt wl 2635904 0 lib80211 4858 1 wl snd_hda_codec_conexant 28491 1 snd_hda_intel 21333 3 snd_hda_codec 70277 2 snd_hda_codec_conexant,snd_hda_intel snd_hwdep 5320 1 snd_hda_codec snd_seq 46091 0 snd_seq_device 5354 1 snd_seq snd_pcm 67225 2 snd_hda_intel,snd_hda_codec snd_timer 18308 2 snd_seq,snd_pcm snd 52754 14 snd_hda_codec_conexant,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer soundcore 6460 1 snd snd_page_alloc 7080 2 snd_hda_intel,snd_pcm ext4 322671 3 mbcache 5918 1 ext4 jbd2 73876 1 ext4 aes_i586 7208 2 aes_generic 26803 1 aes_i586 xts 1907 1 gf128mul 7923 1 xts dm_crypt 10848 1 firewire_ohci 21090 0 firewire_core 42630 1 firewire_ohci crc_itu_t 1343 1 firewire_core sdhci_pci 5714 0 sdhci 17819 1 sdhci_pci mmc_core 61320 1 sdhci sr_mod 14187 0 cdrom 34036 1 sr_mod sd_mod 33344 3 crc_t10dif 1191 1 sd_mod ata_generic 2555 0 pata_acpi 2487 0 ata_piix 19016 2 i915 290879 2 drm_kms_helper 29029 1 i915 drm 163291 3 i915,drm_kms_helper i2c_algo_bit 4600 1 i915 i2c_core 25799 5 i2c_i801,i915,drm_kms_helper,drm,i2c_algo_bit video 16662 1 i915 output 1779 1 video dm_mod 63827 14 dm_mirror,dm_log,dm_crypt
Your firmware appears to be installed and the wl driver you compiled appears to be loaded. If the driver and firmware are compatible then I would check that Network Manager is running and Networking and Wireless Networking are enabled in the NM applet. Network Manager should create an auto-<ssid_of_accesspoint> configuration file in /etc/sysconfig/network-scripts.
If that all looks o.k. I'll have to pass the baton to someone that may have experience with your driver.
The stock driver (b43) does work on my machine although on some routers dhcp does not work and I have had to configure a static IP to get a connection. ymmv.
B.J.
CentOS Linux release 6.0 (Final)
On Mon, 05 Sep 2011 16:54:59 -0400, b.j. mcclure wrote: [...]
Your firmware appears to be installed and the wl driver you compiled appears to be loaded. If the driver and firmware are compatible then I would check that Network Manager is running and Networking and Wireless Networking are enabled in the NM applet. Network Manager should create an auto-<ssid_of_accesspoint> configuration file in /etc/sysconfig/network-scripts.
If that all looks o.k. I'll have to pass the baton to someone that may have experience with your driver.
The stock driver (b43) does work on my machine although on some routers dhcp does not work and I have had to configure a static IP to get a connection. ymmv.
B.J.
CentOS Linux release 6.0 (Final)
My NetworkManager doesn't work (that's another problem, but low priority), and it is my intention to use wpa_supplicant and dhclient from the command line. But obviously, if I can't see anything with ifconfig, I can't do that. ifconfig did work before I made the changes. With regard do compatibility between the firmware and the driver, I could not say. Maybe that is the problem.
Thanks for your help. Mike.
Michael D. Berger wrote:
On Mon, 05 Sep 2011 16:54:59 -0400, b.j. mcclure wrote: [...]
Your firmware appears to be installed and the wl driver you compiled appears to be loaded. If the driver and firmware are compatible then I would check that Network Manager is running and Networking and Wireless Networking are enabled in the NM applet. Network Manager should create an auto-<ssid_of_accesspoint> configuration file in /etc/sysconfig/network-scripts.
If that all looks o.k. I'll have to pass the baton to someone that may have experience with your driver.
The stock driver (b43) does work on my machine although on some routers dhcp does not work and I have had to configure a static IP to get a connection. ymmv.
B.J.
CentOS Linux release 6.0 (Final)
My NetworkManager doesn't work (that's another problem, but low priority), and it is my intention to use wpa_supplicant and dhclient from the command line. But obviously, if I can't see anything with ifconfig, I can't do that. ifconfig did work before I made the changes. With regard do compatibility between the firmware and the driver, I could not say. Maybe that is the problem.
Thanks for your help. Mike.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Mike,
from what I can see in one of your earlier e-mails, you appear to be dealing with BCM4311, which is in my experience one of least problematic - worked out of the box on CentOS 6, however, ymmv. Anyway, it would be useful if we could see the output of:
lspci -nn
just to confirm the exact Broadcom chip.
Now, the manual at CentOS wiki used to be sufficent to make the WiFi work (as eth1 or wlan0, regardless - although I always configured it as eth1), sadly, this is not entirely true anymore. To be more precise, the latest driver from Broadcom site doesn't work at all on CentOS 5 (tested it not a month ago with BCM4311). So, in order to avoid paying to DriverGuide.com, I can either send you a older version of a driver, or you can download one from here:
https://launchpad.net/ubuntu/maverick/+source/broadcom-sta/5.10.91.9.3-3
(I haven't tested the latter), and go through the installation manual step by step. I haven't read Gytis' manual, but it should work in pretty much the same was as the one on CentOS Broadcom Wiki - as he contributed to the Wiki :-)
Hopefully, I'll perform some more testing soon and remedy obsoleted parts of the Wiki page as soon as the time permits.
P.S: And yes, you should leave NetworkManger manage your network connections for start, and stop meddling with wpa_supplicant and manual wireless configuration - it'll save you time and nervs. So, just run:
service network stop service NetworkManager start chkconfig network off chkconfig NetworkManager on
On Tue, 06 Sep 2011 00:49:11 +0200, Milos Blazevic wrote:
Michael D. Berger wrote:
On Mon, 05 Sep 2011 16:54:59 -0400, b.j. mcclure wrote: [...]
Your firmware appears to be installed and the wl driver you compiled appears to be loaded. If the driver and firmware are compatible then I would check that Network Manager is running and Networking and Wireless Networking are enabled in the NM applet. Network Manager should create an auto-<ssid_of_accesspoint> configuration file in /etc/sysconfig/network-scripts.
If that all looks o.k. I'll have to pass the baton to someone that may have experience with your driver.
The stock driver (b43) does work on my machine although on some routers dhcp does not work and I have had to configure a static IP to get a connection. ymmv.
B.J.
CentOS Linux release 6.0 (Final)
My NetworkManager doesn't work (that's another problem, but low priority), and it is my intention to use wpa_supplicant and dhclient from the command line. But obviously, if I can't see anything with ifconfig, I can't do that. ifconfig did work before I made the changes. With regard do compatibility between the firmware and the driver, I could not say. Maybe that is the problem.
Thanks for your help. Mike.
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Mike,
from what I can see in one of your earlier e-mails, you appear to be dealing with BCM4311, which is in my experience one of least problematic
- worked out of the box on CentOS 6, however, ymmv. Anyway, it would be
useful if we could see the output of:
lspci -nn
just to confirm the exact Broadcom chip.
Now, the manual at CentOS wiki used to be sufficent to make the WiFi work (as eth1 or wlan0, regardless - although I always configured it as eth1), sadly, this is not entirely true anymore. To be more precise, the latest driver from Broadcom site doesn't work at all on CentOS 5 (tested it not a month ago with BCM4311). So, in order to avoid paying to DriverGuide.com, I can either send you a older version of a driver, or you can download one from here:
https://launchpad.net/ubuntu/maverick/+source/broadcom-sta/5.10.91.9.3-3
(I haven't tested the latter), and go through the installation manual step by step. I haven't read Gytis' manual, but it should work in pretty much the same was as the one on CentOS Broadcom Wiki - as he contributed to the Wiki :-)
Hopefully, I'll perform some more testing soon and remedy obsoleted parts of the Wiki page as soon as the time permits.
P.S: And yes, you should leave NetworkManger manage your network connections for start, and stop meddling with wpa_supplicant and manual wireless configuration - it'll save you time and nervs. So, just run:
service network stop service NetworkManager start chkconfig network off chkconfig NetworkManager on
Milos,
My NetworkManager doesn't. As I mentioned on another thread, when I go to: System Settings > Network Settings > Network Settings I get a window that says "Your Platform is Not Supported" and offers me a list of Linus systems, none of which are appropriate. Since I should be able to run from the command line, I have given it a low priority. But I would reconsider if a fix is suggested.
I will download from the link you provided and try again. The data you asked for are appended
Thanks for your help. Mike.
lspci -nn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03) 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/ GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/ GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) 00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 02) 00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 1 [8086:27d0] (rev 02) 00:1c.1 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 2 [8086:27d2] (rev 02) 00:1d.0 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 [8086:27c8] (rev 02) 00:1d.1 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 [8086:27c9] (rev 02) 00:1d.2 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 [8086:27ca] (rev 02) 00:1d.3 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 [8086:27cb] (rev 02) 00:1d.7 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller [8086:27cc] (rev 02) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev e2) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge [8086:27b9] (rev 02) 00:1f.2 IDE interface [0101]: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller [8086:27c4] (rev 02) 00:1f.3 SMBus [0c05]: Intel Corporation N10/ICH 7 Family SMBus Controller [8086:27da] (rev 02) 02:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g WLAN [14e4:4311] (rev 01) 05:05.0 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] 05:05.1 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/ MSPro Host Adapter [1180:0822] (rev 19) 05:05.2 System peripheral [0880]: Ricoh Co Ltd R5C843 MMC Host Controller [1180:0843] (rev 01) 05:05.3 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter [1180:0592] (rev 0a) 05:05.4 System peripheral [0880]: Ricoh Co Ltd xD-Picture Card Controller [1180:0852] (rev 05) 05:08.0 Ethernet controller [0200]: Intel Corporation PRO/100 VE Network Connection [8086:1092] (rev 02)
On Tue, 06 Sep 2011 00:49:11 +0200, Milos Blazevic wrote: [...]
Mike,
from what I can see in one of your earlier e-mails, you appear to be dealing with BCM4311, which is in my experience one of least problematic
- worked out of the box on CentOS 6, however, ymmv. Anyway, it would be
useful if we could see the output of:
lspci -nn
just to confirm the exact Broadcom chip.
Now, the manual at CentOS wiki used to be sufficent to make the WiFi work (as eth1 or wlan0, regardless - although I always configured it as eth1), sadly, this is not entirely true anymore. To be more precise, the latest driver from Broadcom site doesn't work at all on CentOS 5 (tested it not a month ago with BCM4311). So, in order to avoid paying to DriverGuide.com, I can either send you a older version of a driver, or you can download one from here:
https://launchpad.net/ubuntu/maverick/+source/broadcom-sta/5.10.91.9.3-3
(I haven't tested the latter), and go through the installation manual step by step. I haven't read Gytis' manual, but it should work in pretty much the same was as the one on CentOS Broadcom Wiki - as he contributed to the Wiki :-)
Hopefully, I'll perform some more testing soon and remedy obsoleted parts of the Wiki page as soon as the time permits.
P.S: And yes, you should leave NetworkManger manage your network connections for start, and stop meddling with wpa_supplicant and manual wireless configuration - it'll save you time and nervs. So, just run:
service network stop service NetworkManager start chkconfig network off chkconfig NetworkManager on
Downloading from the location that you suggest (which is an Ubunto location), I got: broadcom-sta_5.10.91.9.3.orig.tar.gz and running it:
# pwd /root/broadcom/driver/broadcom-sta/i386 # make KBUILD_NOPEDANTIC=1 make -C /lib/modules/`uname -r`/build M=`pwd` make[1]: Entering directory `/usr/src/kernels/2.6.32-71.29.1.el6.i686' LD /root/broadcom/driver/broadcom-sta/i386/built-in.o CC [M] /root/broadcom/driver/broadcom-sta/i386/src/wl/sys/wl_linux.o /root/broadcom/driver/broadcom-sta/i386/src/wl/sys/wl_linux.c: In function ‘wl_free’: /root/broadcom/driver/broadcom-sta/i386/src/wl/sys/wl_linux.c:705: error: implicit declaration of function ‘schedule’ make[2]: *** [/root/broadcom/driver/broadcom-sta/i386/src/wl/sys/ wl_linux.o] Error 1 make[1]: *** [_module_/root/broadcom/driver/broadcom-sta/i386] Error 2 make[1]: Leaving directory `/usr/src/kernels/2.6.32-71.29.1.el6.i686' make: *** [all] Error 2
So what is this ‘schedule’ thing?
Thanks, Mike.
----- Original Message ----- | On Tue, 06 Sep 2011 00:49:11 +0200, Milos Blazevic wrote: | [...] | > Mike, | > | > from what I can see in one of your earlier e-mails, you appear to be | > dealing with BCM4311, which is in my experience one of least | > problematic | > - worked out of the box on CentOS 6, however, ymmv. Anyway, it would | > be | > useful if we could see the output of: | > | > lspci -nn | > | > just to confirm the exact Broadcom chip. | > | > Now, the manual at CentOS wiki used to be sufficent to make the WiFi | > work (as eth1 or wlan0, regardless - although I always configured it | > as | > eth1), sadly, this is not entirely true anymore. To be more precise, | > the | > latest driver from Broadcom site doesn't work at all on CentOS 5 | > (tested | > it not a month ago with BCM4311). So, in order to avoid paying to | > DriverGuide.com, I can either send you a older version of a driver, | > or | > you can download one from here: | > | > https://launchpad.net/ubuntu/maverick/+source/broadcom-sta/5.10.91.9.3-3 | > | > (I haven't tested the latter), and go through the installation | > manual | > step by step. I haven't read Gytis' manual, but it should work in | > pretty | > much the same was as the one on CentOS Broadcom Wiki - as he | > contributed | > to the Wiki :-) | > | > Hopefully, I'll perform some more testing soon and remedy obsoleted | > parts of the Wiki page as soon as the time permits. | > | > | > P.S: | > And yes, you should leave NetworkManger manage your network | > connections | > for start, and stop meddling with wpa_supplicant and manual wireless | > configuration - it'll save you time and nervs. So, just run: | > | > service network stop | > service NetworkManager start | > chkconfig network off | > chkconfig NetworkManager on | | Downloading from the location that you suggest (which is an Ubunto | location), I got: | broadcom-sta_5.10.91.9.3.orig.tar.gz | and running it: | | # pwd | /root/broadcom/driver/broadcom-sta/i386 | # make | KBUILD_NOPEDANTIC=1 make -C /lib/modules/`uname -r`/build M=`pwd` | make[1]: Entering directory `/usr/src/kernels/2.6.32-71.29.1.el6.i686' | LD /root/broadcom/driver/broadcom-sta/i386/built-in.o | CC [M] /root/broadcom/driver/broadcom-sta/i386/src/wl/sys/wl_linux.o | /root/broadcom/driver/broadcom-sta/i386/src/wl/sys/wl_linux.c: In | function ‘wl_free’: | /root/broadcom/driver/broadcom-sta/i386/src/wl/sys/wl_linux.c:705: | error: | implicit declaration of function ‘schedule’ | make[2]: *** [/root/broadcom/driver/broadcom-sta/i386/src/wl/sys/ | wl_linux.o] Error 1 | make[1]: *** [_module_/root/broadcom/driver/broadcom-sta/i386] Error 2 | make[1]: Leaving directory `/usr/src/kernels/2.6.32-71.29.1.el6.i686' | make: *** [all] Error 2 | | So what is this ‘schedule’ thing? | | Thanks, | Mike. | | _______________________________________________ | CentOS mailing list | CentOS@centos.org | http://lists.centos.org/mailman/listinfo/centos
You can use the rpmforge version or compile it yourself. I've used this one with success using the details described earlier.
http://www.broadcom.com/support/802.11/linux_sta.php
I did however have to patch it with
http://www.broadcom.com/docs/linux_sta/5_100_82_38.patch
the driver built and installed fine. In fact, I'm using it on my laptop as we speak.
Michael D. Berger wrote:
I have a Broadcom 802.11b/g hardware on my dual-boot laptop. Note first that in the WinXP partition, the wifi makes DHCP connections to my router with no problem. Since this was not working in my new CentOS 6 partition, and remembering that there was a driver problem with the old Fedora partition it replaced, I followed instructions founs at:
http://repecka.net/en/2011/04/19/install-broadcom-bcm4311-802-11bg-wlan- drivers-on-centos/
and
http://www.broadcom.com/docs/linux_sta/README.txt
modifying for that fact that I use wlan0 rather than eth1. The wifi is now dead-in-the-water. The wlan light now remains red, and neither ifconfig nor iwconfig show any sign of wlan0 (contra to the situation before I installed the new driver). It still works in the WinXP partition.
Suggestions for my next step in fixing this would be most welcome.
maybe here: http://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom?action=show
good luck
On Mon, 05 Sep 2011 20:39:48 +0200, Nicolas Thierry-Mieg wrote:
[...]
maybe here: http://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom?action=show
good luck
Thanks, but no luck so far. Mike.
[...]
I note that instructions indicated that I should modify
/etc/modprobe.conf
to contain:
alias eth1 wl
Since I don't have that file, I grepped around and decided that the file to use is probably:
/etc/modprobe.d/dist.conf
So in that file I put:
alias wlan0
With regard to the library, I tried several things, the latest being:
alias iee80211_crypt_tkip lib80211
Might there be a problem herein?
Thanks, Mike.
On Mon, 05 Sep 2011 20:22:23 +0000, Michael D. Berger wrote:
[...]
I note that instructions indicated that I should modify
/etc/modprobe.conf
to contain:
alias eth1 wl
Since I don't have that file, I grepped around and decided that the file to use is probably:
/etc/modprobe.d/dist.conf
So in that file I put:
alias wlan0
With regard to the library, I tried several things, the latest being:
alias iee80211_crypt_tkip lib80211
Might there be a problem herein?
Thanks, Mike.
Correction (typeo): alias wlan0 wl
I didn't read the whole thread but you should make sure you blacklist the b43, bcm43xx and ssb drivers
vi /etc/modprobe.d/broadcom-wl.conf
blacklist b43 blacklist bcm43xx blacklist ssb
and also add intel_iommu=off to the kernel line in your grub configuration. That works for my broadcom adapter
----- Original Message ----- | I have a Broadcom 802.11b/g hardware on my dual-boot laptop. | Note first that in the WinXP partition, the wifi makes DHCP | connections to my router with no problem. Since this | was not working in my new CentOS 6 partition, and | remembering that there was a driver problem with the | old Fedora partition it replaced, I followed instructions | founs at: | | http://repecka.net/en/2011/04/19/install-broadcom-bcm4311-802-11bg-wlan- | drivers-on-centos/ | | and | | http://www.broadcom.com/docs/linux_sta/README.txt | | modifying for that fact that I use wlan0 rather than eth1. | The wifi is now dead-in-the-water. The wlan light now | remains red, and neither ifconfig nor iwconfig show any | sign of wlan0 (contra to the situation before I installed | the new driver). It still works in the WinXP partition. | | Suggestions for my next step in fixing this would be most | welcome. | | Thank, | Mike. | | _______________________________________________ | CentOS mailing list | CentOS@centos.org | http://lists.centos.org/mailman/listinfo/centos
On Tue, 06 Sep 2011 02:28:03 -0700, James A. Peltier wrote:
I didn't read the whole thread but you should make sure you blacklist the b43, bcm43xx and ssb drivers
vi /etc/modprobe.d/broadcom-wl.conf
blacklist b43 blacklist bcm43xx blacklist ssb
and also add intel_iommu=off to the kernel line in your grub configuration. That works for my broadcom adapter
I don't have a file /etc/modprobe.d/broadcom-wl.conf . I do have /etc/modprobe.d/blacklist.conf in which I put what you suggest. Do you think that will do, to should I add a new file?
Thanks, Mike.
----- Original Message ----- | On Tue, 06 Sep 2011 02:28:03 -0700, James A. Peltier wrote: | | > I didn't read the whole thread but you should make sure you | > blacklist | > the b43, bcm43xx and ssb drivers | > | > vi /etc/modprobe.d/broadcom-wl.conf | > | > blacklist b43 | > blacklist bcm43xx | > blacklist ssb | > | > and also add intel_iommu=off to the kernel line in your grub | > configuration. That works for my broadcom adapter | > | | I don't have a file /etc/modprobe.d/broadcom-wl.conf . | I do have /etc/modprobe.d/blacklist.conf in which I put | what you suggest. Do you think that will do, to should | I add a new file? | | Thanks, | Mike.
create it with the contents I listed and reboot. If running SELinux in enforcing mode you may need to run restorecon on it.
On Tue, 06 Sep 2011 08:10:51 -0700, James A. Peltier wrote:
----- Original Message ----- | On Tue, 06 Sep 2011 02:28:03 -0700, James A. Peltier wrote: | | > I didn't read the whole thread but you should make sure you | > blacklist | > the b43, bcm43xx and ssb drivers | > | > vi /etc/modprobe.d/broadcom-wl.conf | > | > blacklist b43 | > blacklist bcm43xx | > blacklist ssb | > | > and also add intel_iommu=off to the kernel line in your grub | > configuration. That works for my broadcom adapter | > | | I don't have a file /etc/modprobe.d/broadcom-wl.conf . | I do have /etc/modprobe.d/blacklist.conf in which I put | what you suggest. Do you think that will do, to should | I add a new file? | | Thanks, | Mike.
create it with the contents I listed and reboot. If running SELinux in enforcing mode you may need to run restorecon on it.
Done, still no action. Note that at present, ifconfig does not list wlan0. I am getting close to reinstalling the system (but because of travels related to my daughter's upcoming marriage, I probably won't be able to do that for several weeks).
Mike.
Michael D. Berger wrote:
On Tue, 06 Sep 2011 08:10:51 -0700, James A. Peltier wrote:
create it with the contents I listed and reboot. If running SELinux in enforcing mode you may need to run restorecon on it.
Done, still no action. Note that at present, ifconfig does not list wlan0. I am getting close to reinstalling the system (but because of travels related to my daughter's upcoming marriage, I probably won't be able to do that for several weeks).
Is it worth all the effort? I too have this hardware in an acer extensa notebook, but I am using a well working pcmcia wlan card with 54mbit. Once I have had the BCM94311 working, but only with 24mbit on wpa2. http://marc.info/?l=centos&m=123610324013833&w=2
regards Olaf
On 9/6/2011 10:06 AM, Michael D. Berger wrote:
On Tue, 06 Sep 2011 02:28:03 -0700, James A. Peltier wrote:
I didn't read the whole thread but you should make sure you blacklist the b43, bcm43xx and ssb drivers
vi /etc/modprobe.d/broadcom-wl.conf
blacklist b43 blacklist bcm43xx blacklist ssb
and also add intel_iommu=off to the kernel line in your grub configuration. That works for my broadcom adapter
I don't have a file /etc/modprobe.d/broadcom-wl.conf . I do have /etc/modprobe.d/blacklist.conf in which I put what you suggest. Do you think that will do, to should I add a new file?
Thanks, Mike.
Hi Mike,
I noticed the one question that hasn't been asked is, "is it plugged in?" In other words is the wpa_supplicant service enabled, starting at boot-time and running?
The reason I ask is because when I first loaded C6 on my Inspiron wireless worked out of the box, however then there were a few updates and it stopped working. When all the dust settled I took a look through the services and noticed that the above mentioned service was diabled and not running. So, I enabled it, started it and wireless came right back up.
-
b.j. mcclure -
James A. Peltier -
Mark Weaver -
Michael D. Berger -
Milos Blazevic -
Nicolas Thierry-Mieg -
Olaf Mueller