<div dir="ltr"><div><div>I don't know how to make a reply here but I realized I had to install kmod*wl*, it was contained in /rpmbuild/RPMS/. I did it without error:<br><br>[root@dhcp121-83 x86_64]# rpm -Uvh /home/dafh/rpmbuild/RPMS/x86_64/kmod-wl-6_30_223_271-2.el7.local.x86_64.rpm <br>Preparing... ################################# [100%]<br>Updating / installing...<br> 1:kmod-wl-6_30_223_271-2.el7.local ################################# [100%]<br>Working. This may take some time ...<br>Done.<br><br></div>but at the moment I try to modprobe wl, <br><br>[root@dhcp121-83 x86_64]# modprobe wl<br>insmod: ERROR: could not load module /lib/modules/3.10.0-327.4.4.el7.x86_64/kernel/lib/wl.ko: No such file or directory<br>modprobe: ERROR: Error running install command for wl<br>modprobe: ERROR: could not insert 'wl': Operation not permitted<br><br></div>Is it weird?<br></div><div class="gmail_extra"><br><div class="gmail_quote">2016-01-18 14:33 GMT-03:00 Diego Farias <span dir="ltr"><<a href="mailto:dnfarias@uc.cl" target="_blank">dnfarias@uc.cl</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi everyone; I'm new CentOS user<br><br>CentOS Linux release 7.2.1511 (Core) <br><br> and new at elrepo. I'm thankful for all the things you've done to make us easy some problems that I would fail to solve by myself.<br></div><br>'ve spent several weeks now trying to get my wireless working <br><br>06:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 0) <br><br> following <a href="http://elrepo.org/tiki/wl-kmod" target="_blank">http://elrepo.org/tiki/wl-kmod</a> with kernel version<br><br>3.10.0-327.4.4.el7.x86_64<br><br>but I always get stuck here (at installing):<br><div><div><br>[root@dhcp121-83 dafh]# rpm -Uvh /home/dafh/Downloads/wl-kmod-6_30_223_271-2.el7.elrepo.nosrc.rpm <br>warning: /home/dafh/Downloads/wl-kmod-6_30_223_271-2.el7.elrepo.nosrc.rpm: Header V4 DSA/SHA1 Signature, key ID baadae52: NOKEY<br>Updating / installing...<br> 1:wl-kmod-6_30_223_271-2.el7.elrepo################################# [100%]<br>warning: user tindall does not exist - using root<br>warning: group tindall does not exist - using root<br>warning: user tindall does not exist - using root<br>warning: group tindall does not exist - using root<br>warning: user tindall does not exist - using root<br>warning: group tindall does not exist - using root<br>warning: user tindall does not exist - using root<br>warning: group tindall does not exist - using root<br>[root@dhcp121-83 dafh]# modprobe wl<br>insmod: ERROR: could not load module /lib/modules/3.10.0-327.4.4.el7.x86_64/kernel/lib/wl.ko: No such file or directory<br>modprobe: ERROR: Error running install command for wl<br>modprobe: ERROR: could not insert 'wl': Operation not permitted<br><br></div><div>At building, I also have the same issue (warning: user tindall etc..) and this:<br><br>********************************************************************************<br>*********************** KERNEL ABI COMPATIBILITY WARNING ***********************<br>********************************************************************************<br>The following kernel symbols are not guaranteed to remain compatible with<br>future kernel updates to this RHEL release:<br><br> PDE_DATA<br> __dev_kfree_skb_any<br> __fentry__<br> __ieee80211_get_channel<br> __stack_chk_fail<br> __tasklet_schedule<br> cfg80211_connect_result<br> cfg80211_disconnected<br> cfg80211_get_bss<br> cfg80211_gtk_rekey_notify<br> cfg80211_ibss_joined<br> cfg80211_inform_bss_width<br> cfg80211_inform_bss_width_frame<br> cfg80211_michael_mic_failure<br> cfg80211_put_bss<br> cfg80211_report_wowlan_wakeup<br> cfg80211_roamed<br> cfg80211_scan_done<br> filp_close<br> filp_open<br> generic_file_llseek<br> ieee80211_channel_to_frequency<br> ieee80211_frequency_to_channel<br> kernel_read<br> kernel_stack<br> kmemdup<br> pci_read_config_dword<br> pci_write_config_dword<br> pv_lock_ops<br> remove_proc_entry<br> tasklet_init<br> tasklet_kill<br> wiphy_free<br> wiphy_new_nm<br> wiphy_register<br> wiphy_unregister<br> x86_dma_fallback_dev<br><br>Red Hat recommends that you consider using only official kernel ABI symbols<br>where possible. Requests for additions to the kernel ABI can be filed with<br>your partner or customer representative (component: driver-update-program).<br><br></div><div>I have tried other ways for doing this but til today nothing works. I would like you to help me if you can.<br><br></div><div>Thanks,<br><br></div><div>Diego<br></div></div></div>
</blockquote></div><br></div>