make API=WEXT
CC /home/xxx/packages/driver/wl.mod.o
LD [M] /home/xxx/packages/driver/wl.ko.unsigned
NO SIGN [M] /home/xxx/packages/driver/wl.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.32-431.el6.x86_64′
3.安装
# make install
install -D -m 755 wl.ko /lib/modules/`uname -r`/kernel/drivers/net/wireless
4.加载新的驱动程序
# modprobe lib80211
# insmod wl.ko
5.重新启动网络服务
# service network restart
Shutting down interface p5p1: Device state: 3 (disconnected)
[ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
参考来源,从这里看到编译参数,谢谢!:http://weiruoyu.blog.iyunv.com/951650/1193257
-------------------------------------------------------------------------------------------------------
经过实践,上述方法不是太好使,新方法正在寻找。
---------------------------------------------------------------------------------------------------------------------------
终于找到新方法了,发现这个是好使的,真牛叉.
链接如下:http://elrepo.org/tiki/wl-kmod
原文如下: Please note: The current Broadcom closed-source Linux drivers when built according to the instructions provided here have provided functional wireless capability to some users, but have failed for other users.
Broadcom Corp. provides closed-source IEEE 802.11a/b/g/n Linux drivers for use with Broadcom's BCM4311, BCM4312, BCM4313, BCM4321, BCM4322, BCM4352, BCM43142, BCM43224, BCM43225, BCM43227 and BCM43228 wireless chipsets. We (ELRepo) cannot create and redistribute binary RPMS for these drivers due to the Broadcom licensing restrictions (i.e., liability issues). However, we do make available no-source SRPMS (.nosrc.rpm) which contain the framework required to build the binaries,but lack the proprietary code and are not subject to Broadcom's licensing restrictions.
These no-source SRPMS can be used by the end user to build kABI-compatible binary drivers for local use. These kABI-compatible binaries should be usable after future kernel updates, so there is no need to recompile them for each new kernel. Please note that the nosrc.rpm package does not build kmod-wl for kernel-xen and kmod-wl cannot be built on a system running kernel-xen.
To build a kmod-wl binary, you will need to (1) configure a build tree, (2) download the wl-kmod*nosrc.rpm for your EL release, (3) download theclosed-source tarball from Broadcom for your architecture (i.e., 32-bitvs 64-bit) into the build tree and (4) initiate the kmod-wl build. For convenience, the kernel development package for the running kernel will be used in the build process, as opposed to our normal policy of building against an older kernel development package.
The kmod-wl package can be built on any system running the same EL release/architecture as the target system. If you are building on the target system and lack network connectivity, then the downloads can be made onto a USB flash drive and copied onto your system.
Below are the detailed instructions on how to build the binary packages.If you are already familiar with using rpmbuild to build packages, thenthis process should only take you 5-10 minutes to complete.
Build and install kmod-wl for EL5/6/7 (Note: This page is currently being modified and instructions may be incomplete)
- For 64-bit: # yum install kernel-devel-$(uname -r)
1b) EL6:
# yum groupinstall 'Development Tools'
# yum install redhat-lsb kernel-abi-whitelists
# yum install kernel-devel-$(uname -r)
EL6 Note: Due to a bug in redhat-rpm-config-9.0.3-42.el6, a modification is required to fix the
kabi-whitelist target in /usr/lib/rpm/redhat/find-requires.ksyms before you build kmod-wl.
EL7 Note: Due to a bug in redhat-rpm-config-9.1.0-63.el7, a modification is required to fix the
kabi-whitelist target in /usr/lib/rpm/redhat/find-requires.ksyms before you build kmod-wl.