bcm43227 problem, wireless is on but cannot scanning or connect any wifi

My laptop is Acer 4752G, OS is suse-12.2-xen, followings are what I did.
First. show some information.

linux-jxf2:/home/haha # uname -a
Linux linux-jxf2.site 3.4.6-2.10-xen #1 SMP Thu Jul 26 09:36:26 UTC 2012 (641c197) x86_64 x86_64 x86_64 GNU/Linux
linux-jxf2:/home/haha # ifconfig -a
eth0      Link encap:Ethernet  HWaddr 20:6A:8A:7E:62:81  
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:13077 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9196 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:12433973 (11.8 Mb)  TX bytes:1085213 (1.0 Mb)
          Interrupt:19 

eth1      Link encap:Ethernet  HWaddr C0:18:85:08:95:99  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:17 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:3025 (2.9 Kb)  TX bytes:3025 (2.9 Kb)
linux-jxf2:/home/haha # iwconfig
eth0      no wireless extensions.

eth1      IEEE 802.11abg  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=200 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          
lo        no wireless extensions.

linux-jxf2:/home/haha # lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09)
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09)
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09)
00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04)
00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 04)
00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b4)
00:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 [8086:1c12] (rev b4)
00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b4)
00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 04)
00:1f.0 ISA bridge [0601]: Intel Corporation HM65 Express Chipset Family LPC Controller [8086:1c49] (rev 04)
00:1f.2 IDE interface [0101]: Intel Corporation 6 Series/C200 Series Chipset Family 4 port SATA IDE Controller [8086:1c01] (rev 04)
00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller [8086:1c22] (rev 04)
00:1f.5 IDE interface [0101]: Intel Corporation 6 Series/C200 Series Chipset Family 2 port SATA IDE Controller [8086:1c09] (rev 04)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GeForce GT 630M [10de:0de9] (rev a1)
03:00.0 Network controller [0280]: Broadcom Corporation BCM43227 802.11b/g/n [14e4:4358]
04:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM57785 Gigabit Ethernet PCIe [14e4:16b5] (rev 10)
04:00.1 SD Host controller [0805]: Broadcom Corporation NetXtreme BCM57765 Memory Card Reader [14e4:16bc] (rev 10)
04:00.2 System peripheral [0880]: Broadcom Corporation Device [14e4:16be] (rev 10)
04:00.3 System peripheral [0880]: Broadcom Corporation Device [14e4:16bf] (rev 10)
linux-jxf2:/home/haha # lspci -nnk|grep -iA2 net
03:00.0 Network controller [0280]: Broadcom Corporation BCM43227 802.11b/g/n [14e4:4358]
    Subsystem: Foxconn International, Inc. Device [105b:e040]
    Kernel driver in use: wl
04:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM57785 Gigabit Ethernet PCIe [14e4:16b5] (rev 10)
    Subsystem: Acer Incorporated [ALI] Device [1025:0500]
    Kernel driver in use: tg3
04:00.1 SD Host controller [0805]: Broadcom Corporation NetXtreme BCM57765 Memory Card Reader [14e4:16bc] (rev 10)
    Subsystem: Acer Incorporated [ALI] Device [1025:0500]
    Kernel driver in use: sdhci-pci
linux-jxf2:/home/haha # rfkill list
0: acer-wireless: Wireless LAN
    Soft blocked: no
    Hard blocked: no
1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no

I installed broadcom_wl with zypper in broadcom_wl AND firmware with zypper in b43-firmware. And manually installed hybrid_wl which is drivers for old broadcom cards.
I even changed kde to gnome and shifted from ifup to NetworkManager to test if it was the problem, however after all this I only got the followings.

linux-jxf2:/home/haha # iwlist eth1 scanning essid Dlink-ag
eth1      Interface doesn't support scanning : Invalid argument

The networkmanager just cannot find any exisiting wifi signals.


linux-jxf2:/home/haha # dmesg |grep error
   27.225407] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
   27.226580] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
   47.004421] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
   77.004614] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  117.002316] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  167.002673] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  227.002501] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  287.002963] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
  347.002948] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)

And manually add wireless network cannot connect successfully.

What is the problem ? Was it because all the drivers didn’t suit to the xen kernel ? Then where can I find the proper driver for it?

12.2 is at kernel 3.4.47 now. And the Packman packages are built for that kernel, so I’m not sure if they’ll work with 3.4.6.
So either update your system or try to download 3.4.47 from the update repo manually and install it.
http://download.opensuse.org/update/12.2/x86_64/kernel-xen-3.4.47-2.38.1.x86_64.rpm

Was it because all the drivers didn’t suit to the xen kernel ? Then where can I find the proper driver for it?

Well, what driver package did you install in the first place?
On Packman there is a xen kmp package as well:
PackMan :: Informationen zum Paket broadcom-wl

You would need broadcom-wl and broadcom-wl-kmp-xen from there.
And better remove that manually installed hybrid_wl driver, it could interfere.

If you do have internet access (wired?) then just add the Packman repo and install those two packages with zypper:

sudo zypper ar http://packman.inode.at/ Packman
sudo zypper in -f  broadcom-wl broadcom-wl-kmp-xen

But better uninstall the already installed broadcom-wl package first.

After re-reading your post again, I think you already added the Packman repo, but just didn’t install the package “broadcom-wl-kmp-xen”. So “zypper in broadcom-wl-kmp-xen” may be all you need (after maybe updating the kernel).

Yeah, I forgot to mention that I intalled the brroadcom-wl-kmp-xen. Nevertheless, I do update the kernel to 3.4.47 as you said, unistalled and reinstalled the broadcom-wl and broadcom-wl-kmp-xen. However, the problem stays the same. The wireless card just cannot scan for wifi. BTW, the update didn’t change the bootloader which cause a break of booting. I fixed the boot problem by manually change the 3.4.6-10 to 3.4.47-38 everytime it reboots. If you guys got a solution to fix it permanently please tell me.

And have you removed that hybrid_wl driver? As I said it could interfere.<br>
<br>Are you still using NetworkManager now?<br>
<br>In your first post the wlan interface shows up as eth1.<br>
Is this still the case? That would be strange, it should be wlan0.<br>
<br>Maybe you are missing the blacklist file /etc/modprobe.d//50-broadcom-wl-blacklist.conf?<br>
<br>
And please post the output of “lspci -nnk”, that should show which driver is actually in use.

Yes, I removed the hybrid_wl, and still using NetworkManager. The wlan interface still shows up as eth1.

linux-jxf2:/home/haha/Downloads/libvmi-0.10.1 # lspci -nnk
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09)
    Subsystem: Acer Incorporated [ALI] Device [1025:0506]
    Kernel driver in use: agpgart-intel
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09)
    Kernel driver in use: pcieport
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09)
    Subsystem: Acer Incorporated [ALI] Device [1025:0507]
    Kernel driver in use: i915
00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
    Subsystem: Acer Incorporated [ALI] Device [1025:0506]
    Kernel driver in use: mei
00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04)
    Subsystem: Acer Incorporated [ALI] Device [1025:0506]
    Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 04)
    Subsystem: Acer Incorporated [ALI] Device [1025:0506]
    Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b4)
    Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 [8086:1c12] (rev b4)
    Kernel driver in use: pcieport
00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b4)
    Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 04)
    Subsystem: Acer Incorporated [ALI] Device [1025:0506]
    Kernel driver in use: ehci_hcd
00:1f.0 ISA bridge [0601]: Intel Corporation HM65 Express Chipset Family LPC Controller [8086:1c49] (rev 04)
    Subsystem: Acer Incorporated [ALI] Device [1025:0506]
00:1f.2 IDE interface [0101]: Intel Corporation 6 Series/C200 Series Chipset Family 4 port SATA IDE Controller [8086:1c01] (rev 04)
    Subsystem: Acer Incorporated [ALI] Device [1025:0506]
    Kernel driver in use: ata_piix
00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller [8086:1c22] (rev 04)
    Subsystem: Acer Incorporated [ALI] Device [1025:0506]
00:1f.5 IDE interface [0101]: Intel Corporation 6 Series/C200 Series Chipset Family 2 port SATA IDE Controller [8086:1c09] (rev 04)
    Subsystem: Acer Incorporated [ALI] Device [1025:0506]
    Kernel driver in use: ata_piix
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GeForce GT 630M [10de:0de9] (rev a1)
    Subsystem: Acer Incorporated [ALI] Device [1025:0507]
    Kernel driver in use: nouveau
03:00.0 Network controller [0280]: Broadcom Corporation BCM43227 802.11b/g/n [14e4:4358]
    Subsystem: Foxconn International, Inc. Device [105b:e040]
    Kernel driver in use: wl
04:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM57785 Gigabit Ethernet PCIe [14e4:16b5] (rev 10)
    Subsystem: Acer Incorporated [ALI] Device [1025:0500]
    Kernel driver in use: tg3
04:00.1 SD Host controller [0805]: Broadcom Corporation NetXtreme BCM57765 Memory Card Reader [14e4:16bc] (rev 10)
    Subsystem: Acer Incorporated [ALI] Device [1025:0500]
    Kernel driver in use: sdhci-pci
04:00.2 System peripheral [0880]: Broadcom Corporation Device [14e4:16be] (rev 10)
    Subsystem: Acer Incorporated [ALI] Device [1025:0500]
04:00.3 System peripheral [0880]: Broadcom Corporation Device [14e4:16bf] (rev 10)
    Subsystem: Acer Incorporated [ALI] Device [1025:0500]

I’m now trying to update the whole system and see if it works.

After updating the whole system, the problem still exists. I am now considering abort the wireless card since there’s no solution…Or should I use a usb wireless card ? Things just don’t go right.

Hm. So the wl driver is in use, why does it show up as eth1 then? :
I think because of that NetworkManager might confuse it with an ethernet adapter and control it incorrectly, causing your WLAN not to work.

An idea struck my mind:
Maybe you have an udev rule that renames the wlan interface to eth1?
Could you please post the file /etc/udev/rules.d/70-persistent-net.rules ?

linux-jxf2:/home/haha # cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program,run by the persistent-net-generator.rules rules file.
#
# You can modify it,as long as you keep each rule on a single
# line,and change only the value of the NAME= key.
# PCI device 0x14e4:/sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0 (tg3)
# This file was automatically generated by the /lib/udev/write_net_rules
# program,run by the persistent-net-generator.rules rules file.
#
# You can modify it,as long as you keep each rule on a single
# line,and change only the value of the NAME= key.
# PCI device 0x14e4:/sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0 (tg3)
# This file was automatically generated by the /lib/udev/write_net_rules
# program,run by the persistent-net-generator.rules rules file.
#
# You can modify it,as long as you keep each rule on a single
# line,and change only the value of the NAME= key.
# PCI device 0x14e4:/sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0 (tg3)
# This file was automatically generated by the /lib/udev/write_net_rules
# program,run by the persistent-net-generator.rules rules file.
#
# You can modify it,as long as you keep each rule on a single
# line,and change only the value of the NAME= key.
# PCI device 0x14e4:/sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0 (tg3)
# This file was automatically generated by the /lib/udev/write_net_rules
# program,run by the persistent-net-generator.rules rules file.
#
# You can modify it,as long as you keep each rule on a single
# line,and change only the value of the NAME= key.
# PCI device 0x14e4:/sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0 (tg3)
# This file was automatically generated by the /lib/udev/write_net_rules
# program,run by the persistent-net-generator.rules rules file.
#
# You can modify it,as long as you keep each rule on a single
# line,and change only the value of the NAME= key.
# PCI device 0x14e4:/sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0 (tg3)
# PCI device 0x14e4:/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0 (wl)
# USB device 0x148f:0x5370 (usb)
# PCI device 0x14e4:/sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0 (tg3)
# USB device 0x148f:0x5370 (usb)
# PCI device 0x14e4:/sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0 (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="20:6a:8a:7e:62:81", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

Can’t see eth1.

sorry for everyone, its my stupidness that I forgot to turn on the physical switch. It takes me almost three days to find the problem which concludes to a lesson: the nearer you see, the easier to be cheat.
Thanks, everybody!

On 10/17/2013 03:46 AM, fangtuo90 wrote:
>
> sorry for everyone, its my stupidness that I forgot to turn on the
> physical switch. It takes me almost three days to find the problem which
> concludes to a lesson: the nearer you see, the easier to be cheat.
> Thanks, everybody!

Glad you found the switch. The stickies should probably be rewritten to
emphasize checking the switch. They are now quite old, but I have no time for that.

By the way, NetworkManager does not care what the interface is named. A wireless
device can be called wlan0, eth1, or even xyzuvw9, as long as its driver
registers the wireless capability with the kernel. Only if you use ifup is the
name really important as that decides what configuration file to use in
/etc/sysconfig/network/. Of course, using ifup to control wireless should only
be used if really needed, and you know what you are doing.