[elrepo] wl-kmod error at installing

[Diego Farias]

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:

[root at dhcp121-83 x86_64]# rpm -Uvh
/home/dafh/rpmbuild/RPMS/x86_64/kmod-wl-6_30_223_271-2.el7.local.x86_64.rpm
Preparing...                          #################################
[100%]
Updating / installing...
   1:kmod-wl-6_30_223_271-2.el7.local #################################
[100%]
Working. This may take some time ...
Done.

but at the moment I try to modprobe wl,

[root at dhcp121-83 x86_64]# modprobe wl
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
modprobe: ERROR: Error running install command for wl
modprobe: ERROR: could not insert 'wl': Operation not permitted

Is it weird?

2016-01-18 14:33 GMT-03:00 Diego Farias <dnfarias at uc.cl>:

> Hi everyone; I'm new CentOS user
>
> CentOS Linux release 7.2.1511 (Core)
>
> 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.
>
> 've spent several weeks now trying to get my wireless working
>
> 06:00.0 Network controller [0280]: Broadcom Corporation BCM43142
> 802.11b/g/n [14e4:4365] (rev 0)
>
> following http://elrepo.org/tiki/wl-kmod with kernel version
>
> 3.10.0-327.4.4.el7.x86_64
>
> but I always get stuck here (at installing):
>
> [root at dhcp121-83 dafh]# rpm -Uvh
> /home/dafh/Downloads/wl-kmod-6_30_223_271-2.el7.elrepo.nosrc.rpm
> warning: /home/dafh/Downloads/wl-kmod-6_30_223_271-2.el7.elrepo.nosrc.rpm:
> Header V4 DSA/SHA1 Signature, key ID baadae52: NOKEY
> Updating / installing...
>    1:wl-kmod-6_30_223_271-2.el7.elrepo#################################
> [100%]
> warning: user tindall does not exist - using root
> warning: group tindall does not exist - using root
> warning: user tindall does not exist - using root
> warning: group tindall does not exist - using root
> warning: user tindall does not exist - using root
> warning: group tindall does not exist - using root
> warning: user tindall does not exist - using root
> warning: group tindall does not exist - using root
> [root at dhcp121-83 dafh]# modprobe wl
> 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
> modprobe: ERROR: Error running install command for wl
> modprobe: ERROR: could not insert 'wl': Operation not permitted
>
> At building, I also have the same issue (warning: user tindall etc..) and
> this:
>
>
> ********************************************************************************
> *********************** KERNEL ABI COMPATIBILITY WARNING
> ***********************
>
> ********************************************************************************
> The following kernel symbols are not guaranteed to remain compatible with
> future kernel updates to this RHEL release:
>
>     PDE_DATA
>     __dev_kfree_skb_any
>     __fentry__
>     __ieee80211_get_channel
>     __stack_chk_fail
>     __tasklet_schedule
>     cfg80211_connect_result
>     cfg80211_disconnected
>     cfg80211_get_bss
>     cfg80211_gtk_rekey_notify
>     cfg80211_ibss_joined
>     cfg80211_inform_bss_width
>     cfg80211_inform_bss_width_frame
>     cfg80211_michael_mic_failure
>     cfg80211_put_bss
>     cfg80211_report_wowlan_wakeup
>     cfg80211_roamed
>     cfg80211_scan_done
>     filp_close
>     filp_open
>     generic_file_llseek
>     ieee80211_channel_to_frequency
>     ieee80211_frequency_to_channel
>     kernel_read
>     kernel_stack
>     kmemdup
>     pci_read_config_dword
>     pci_write_config_dword
>     pv_lock_ops
>     remove_proc_entry
>     tasklet_init
>     tasklet_kill
>     wiphy_free
>     wiphy_new_nm
>     wiphy_register
>     wiphy_unregister
>     x86_dma_fallback_dev
>
> Red Hat recommends that you consider using only official kernel ABI symbols
> where possible. Requests for additions to the kernel ABI can be filed with
> your partner or customer representative (component: driver-update-program).
>
> I have tried other ways for doing this but til today nothing works. I
> would like you to help me if you can.
>
> Thanks,
>
> Diego
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.elrepo.org/pipermail/elrepo/attachments/20160118/3135a9cb/attachment.html>