It seems that I have insmod wl.ko in the kernel,but the wireless card still not working.

Discussion in 'General Linux' started by cenyebin, Dec 23, 2013.

  1. cenyebin

    cenyebin New Member

    Messages:
    24
    Likes Received:
    2
    Trophy Points:
    3
    My computer is lenovo G 480 with centos6.4 system .The code following is my step of installing driver.Please read it patiently and help me analy what happend. It seem like that the wl module have been compiled in the kernel .But ,unfortunately it doesn't work
    What's wrong with it .I have been disturbed about the problem for a few days ,and google many times.
    Any one can tell me how to solve it ,appreciate very much.


    Code:
    [root@localhost hybrid-32bit]#make API=WEXT (want to use make command to compile ,but it apeared errors)
    
    KBUILD_NOPEDANTIC=1 make -C /lib/modules/`uname -r`/build M=`pwd`
    make[1]: Entering directory `/usr/src/kernels/2.6.32-358.el6.i686'
    Wireless Extension API specified in command line
    Using Wireless Extension API
      LD      /home/cenyebin/Downloads/hybrid-32bit/built-in.o
      CC [M]  /home/cenyebin/Downloads/hybrid-32bit/src/shared/linux_osl.o
      CC [M]  /home/cenyebin/Downloads/hybrid-32bit/src/wl/sys/wl_linux.o
      CC [M]  /home/cenyebin/Downloads/hybrid-32bit/src/wl/sys/wl_iw.o
      CC [M]  /home/cenyebin/Downloads/hybrid-32bit/src/wl/sys/wl_cfg80211.o
      LD [M]  /home/cenyebin/Downloads/hybrid-32bit/wl.o
    WARNING: modpost: missing MODULE_LICENSE() in /home/cenyebin/Downloads/hybrid-32bit/wl.o
    see include/linux/module.h for more information
      Building modules, stage 2.
    Wireless Extension API specified in command line
    Using Wireless Extension API
      MODPOST 1 modules
    WARNING: modpost: missing MODULE_LICENSE() in /home/cenyebin/Downloads/hybrid-32bit/wl.o
    see include/linux/module.h for more information
      CC      /home/cenyebin/Downloads/hybrid-32bit/wl.mod.o
      LD [M]  /home/cenyebin/Downloads/hybrid-32bit/wl.ko.unsigned
      NO SIGN [M] /home/cenyebin/Downloads/hybrid-32bit/wl.ko
    make[1]: Leaving directory `/usr/src/kernels/2.6.32-358.el6.i686'
    [root@localhost hybrid-32bit]#lsmod  | grep "brcmsmac\|b43\|ssb\|bcma\|wl"
    [root@localhost hybrid-32bit]#echo "blacklist bcma" >> /etc/modprobe.d/blacklist.conf
    
    [root@localhost hybrid-32bit]# rmmod wl
    [root@localhost hybrid-32bit]# lsmod  | grep "brcmsmac\|b43\|ssb\|bcma\|wl"
    [root@localhost hybrid-32bit]# modprobe lib80211
    [root@localhost hybrid-32bit]# modprobe cfg80211
    [root@localhost hybrid-32bit]# insmod wl.ko
    [root@localhost hybrid-32bit]# lsmod | grep "80211\|wl"
    wl                  2432555  0
    cfg80211              163939  0
    rfkill                14794  1 cfg80211
    lib80211_crypt_tkip    8490  0
    lib80211                4066  2 wl,lib80211_crypt_tkip
    
    [root@localhost hybrid-32bit]# lspci -vxx
    03:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)
        Subsystem: Broadcom Corporation Device 051b
        Flags: bus master, fast devsel, latency 0, IRQ 17
        Memory at db400000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
        Capabilities: [58] Vendor Specific Information: Len=78 <?>
        Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [d0] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [13c] Virtual Channel
        Capabilities: [160] Device Serial Number 00-00-23-ff-ff-65-68-94
        Capabilities: [16c] Power Budgeting <?>
        Kernel driver in use: wl
        Kernel modules: wl, bcma
    [root@localhost hybrid-32bit]# ifconfig
    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:20 errors:0 dropped:0 overruns:0 frame:0
              TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:1126 (1.0 KiB)  TX bytes:1126 (1.0 KiB)
    
    virbr0    Link encap:Ethernet  HWaddr 52:54:00:64:10:BD
              inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
              UP BROADCAST RUNNING 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:0
              RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
    
    DevynCJohnson likes this.
  2. Squaw Pendragon

    Squaw Pendragon New Member

    Messages:
    10
    Likes Received:
    5
    Trophy Points:
    3
    I can see you are using Centos. I guess it is because you have an IBM laptop. As a former IT Technician, I recommend to make sure the wireless adapter works. I noticed that my Toshiba Portege had an issue with the wireless switching circuit and I blamed it on the previous owner that busted it. I had to go to an external wireless adapter and had to blacklist the internal wireless driver.
  3. lobo

    lobo Active Member

    Messages:
    134
    Likes Received:
    81
    Trophy Points:
    28
    You've blacklisted bcma but it's still getting loaded, perhaps you haven't unloaded it or rebooted? Also blacklist brcmsmac
    Code:
    # echo "blacklist brcmsmac" >> /etc/modprobe.d/blacklist.conf
    Reboot.

    If it's still no good, you may be better off using a newer kernel e.g. 3.2 and the brcmsmac driver which is included in the kernel. brcmsmac will support the BCM4313 in a newer kernel.
  4. GrumpyOldMan

    GrumpyOldMan Member

    Messages:
    72
    Likes Received:
    27
    Trophy Points:
    18
    Look in dmesg to see if the driver reported any issues there. Check just after running modprobe or insmod, so that the output you will be looking for will be in the tail of the log.
  5. cenyebin

    cenyebin New Member

    Messages:
    24
    Likes Received:
    2
    Trophy Points:
    3
    thanks for your reply any way.It still does't work.

    Dmesg is
    Code:
    Atheros(R) AR8131/AR8151/AR8152/AR8161 PCI-E Ethernet Network Driver - version 2.0.0.6
    Copyright (c) 2007 - 2011 Atheros Corporation
    alx 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    alx 0000:02:00.0: DMA to 64-BIT addresses.
    alx 0000:02:00.0: setting latency timer to 64
    alx_hw: alf_init_hw_callbacks: HW Flags = 0x10
    alx_hw: alf_reset_phy: reset PHY, pws = 1, az = 0, ptp = 0
    alx_hw: alf_setup_phy_link: speed = 0x2f, autoneg = 1
      alloc irq_desc for 34 on node -1
      alloc kstat_irqs on node -1
    alx 0000:02:00.0: irq 34 for MSI/MSI-X
    alx: Atheros Gigabit Network Connection
    udev: renamed network interface eth0 to eth1
    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:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    wl 0000:03:00.0: setting latency timer to 64
    lib80211_crypt: registered algorithm 'TKIP'
    eth0: Broadcom BCM4727 802.11 Hybrid Wireless Controller 5.100.82.112
    
  6. cenyebin

    cenyebin New Member

    Messages:
    24
    Likes Received:
    2
    Trophy Points:
    3
    thanks for your reply ,and the dmesg is below
    Code:
    Atheros(R) AR8131/AR8151/AR8152/AR8161 PCI-E Ethernet Network Driver - version 2.0.0.6
    Copyright (c) 2007 - 2011 Atheros Corporation
    alx 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    alx 0000:02:00.0: DMA to 64-BIT addresses.
    alx 0000:02:00.0: setting latency timer to 64
    alx_hw: alf_init_hw_callbacks: HW Flags = 0x10
    alx_hw: alf_reset_phy: reset PHY, pws = 1, az = 0, ptp = 0
    alx_hw: alf_setup_phy_link: speed = 0x2f, autoneg = 1
      alloc irq_desc for 34 on node -1
      alloc kstat_irqs on node -1
    alx 0000:02:00.0: irq 34 for MSI/MSI-X
    alx: Atheros Gigabit Network Connection
    udev: renamed network interface eth0 to eth1
    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:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    wl 0000:03:00.0: setting latency timer to 64
    lib80211_crypt: registered algorithm 'TKIP'
    eth0: Broadcom BCM4727 802.11 Hybrid Wireless Controller 5.100.82.112
    
  7. cenyebin

    cenyebin New Member

    Messages:
    24
    Likes Received:
    2
    Trophy Points:
    3
    Yes ,thanks. I will think about going to an external wireless adapter if the driver still doesn't work.
  8. lobo

    lobo Active Member

    Messages:
    134
    Likes Received:
    81
    Trophy Points:
    28
    As I said, build a 3.2 kernel and you will be able to use the FOSS brcmsmac driver.

    wl is noted for being problematic
  9. cenyebin

    cenyebin New Member

    Messages:
    24
    Likes Received:
    2
    Trophy Points:
    3
    Do you mean you advise me to upgrade the kernel with centos 6.4 to 3.2 kernel ? Is it possible? you see "
    Kernel driver in use: wl
    Kernel modules: wl, bcma
    "
    I think wl conflicts with bcma ,but I hava get bcma into blacklists before insmod
    wl.ko . How to remove to bcma module from system.
  10. lobo

    lobo Active Member

    Messages:
    134
    Likes Received:
    81
    Trophy Points:
    28
    Yes it is possible to upgrade the kernel.

    If you blacklist bcma and reboot, it should not load unless another module (which you have not blacklisted) is loading it. Thus it's likely that another (conflicting) module is loading bcma.

    bcma is included in the kernel. You don't need to remove it, just blacklist it and reboot.

    You should provide a full lsmod output and the contents of your module blacklist(s) if you want help in searching for conflicting modules.
    livina likes this.
  11. DevynCJohnson

    DevynCJohnson Super Moderator Staff Member Staff Writer

    Messages:
    951
    Likes Received:
    848
    Trophy Points:
    93
    I strongly agree with @lobo. Instead of trying to make your own driver, upgrade your kernel. The CentOS developers test their kernels/modules, so you will have less problems.
    Haider92 likes this.
  12. cenyebin

    cenyebin New Member

    Messages:
    24
    Likes Received:
    2
    Trophy Points:
    3
    I installed a new 3.2.53kernel,boot failed boot. I have google a day, it let me change /etc/selinux/config file like that selinux=disabled. But it doesn't work.
    Code:
    kernel panic - not syncing: Attempted to kill int!
    pid: 1 ,comm :init not  tainted 3.2.53 #2
    Call Trace
    [<c085bf25>] ?panic+0x57/0x158
    .................................
  13. cenyebin

    cenyebin New Member

    Messages:
    24
    Likes Received:
    2
    Trophy Points:
    3
    I installed a new 3.2.53kernel,boot failed boot. I have google a day, it let me change /etc/selinux/config file like that selinux=disabled. But it doesn't work.
    Code:
    kernel panic - not syncing: Attempted to kill int!
    pid: 1 ,comm :init not  tainted 3.2.53 #2
    Call Trace
    [<c085bf25>] ?panic+0x57/0x158
    .................................
  14. lobo

    lobo Active Member

    Messages:
    134
    Likes Received:
    81
    Trophy Points:
    28
    How did you build your kernel?
  15. DevynCJohnson

    DevynCJohnson Super Moderator Staff Member Staff Writer

    Messages:
    951
    Likes Received:
    848
    Trophy Points:
    93
    For this kernel v3.2.53, did you build it or did it come from an upgrade?
    Haider92 and livina like this.
  16. cenyebin

    cenyebin New Member

    Messages:
    24
    Likes Received:
    2
    Trophy Points:
    3
    I must say sorry to you that I have no time to reply you ,because I am busy with

    my exam. And , I have installed the kernel today ,but there are some error info during installing kernel . Then I reboot from the new kernel, the wireless still didn't
    work. oh ,my god.
    Code:
    sh /home/cenyebin/Downloads/linux-3.2.53/arch/x86/boot/install.sh 3.2.53 arch/x86/boot/bzImage \
     
    System.map "/boot"
    ERROR: modinfo: could not find module wl
    
    ERROR: modinfo: could not find module lpc_ich
    
    ERROR: modinfo: could not find module xhci_hcd
    
    
    
    ERROR: modinfo: could not find module ipt_MASQUERADE
    
    ERROR: modinfo: could not find module iptable_nat
    
    ERROR: modinfo: could not find module nf_nat
    
    ERROR: modinfo: could not find module wl
    
    ERROR: modinfo: could not find module uvcvideo
    
    ERROR: modinfo: could not find module videodev
    
  17. DevynCJohnson

    DevynCJohnson Super Moderator Staff Member Staff Writer

    Messages:
    951
    Likes Received:
    848
    Trophy Points:
    93
  18. cenyebin

    cenyebin New Member

    Messages:
    24
    Likes Received:
    2
    Trophy Points:
    3
    I have knew the reason that the NetworkManager is stopped after installing the centos ,and i started it so I can see my wireless card eth0. I am early to be happy that it can not access my AP in my home. The
    warning is that Passwords or encryption keys are required to access the wireless network 'cenyebin'.

    The step of my installtion driver is below:

    make API=WEXT
    rmmod bcma

    modprobe lib80211
    modprobe cfg80211
    insmod wl.ko

    Code:
    eth0      Link encap:Ethernet  HWaddr 68:94:23:65:14:3C 
              inet6 addr: fe80::6a94:23ff:fe65:143c/64 Scope:Link
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:66
              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
    
  19. GrumpyOldMan

    GrumpyOldMan Member

    Messages:
    72
    Likes Received:
    27
    Trophy Points:
    18
    Usually, eth0 is a wired ethernet NIC, not wireless. What is there besides eth0 and lo?
  20. cenyebin

    cenyebin New Member

    Messages:
    24
    Likes Received:
    2
    Trophy Points:
    3
    Thanks for your reply . eth0 is indeed a wireless card,I can scan AP and find my AP.
    Code:
    eth0      Link encap:Ethernet  HWaddr 68:94:23:65:14:3C 
              inet6 addr: fe80::6a94:23ff:fe65:143c/64 Scope:Link
              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
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:44 errors:0 dropped:0 overruns:0 frame:0
              TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:2560 (2.5 KiB)  TX bytes:2560 (2.5 KiB)
    
    virbr0    Link encap:Ethernet  HWaddr 52:54:00:19:BA:B2 
              inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
              UP BROADCAST RUNNING 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:0
              RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
    

Share This Page