| Summary: | Cannot enable BCM4331 wifi on 2011 Macbook Pro | ||
|---|---|---|---|
| Product: | Fedora | Reporter: | mobile.harvey |
| Component: | broadcom-wl | Assignee: | NVieville <nicolas.vieville> |
| Status: | RESOLVED EXPIRED | ||
| Severity: | normal | ||
| Priority: | P1 | ||
| Version: | 26 | ||
| Hardware: | x86_64 | ||
| OS: | GNU/Linux | ||
| namespace: | |||
| Attachments: | 6.30.223.271-9-for-4.11.0-0.rc4.git0.1.fc26.x86_64.failed.log | ||
|
Description
mobile.harvey
2017-04-06 12:06:25 CEST
Hello, Thanks for reporting this issue. As a new package have been build in koji including a patch for kernel 4.11, maybe you should give it a try - RPMS available here: https://koji.rpmfusion.org/koji/buildinfo?buildID=3699 or you could wait for these new akmod-wl packages been pushed in F26 repositories. Feel free to make any comment about this issue. Cordially, -- NVieville Hi. Thanks for making the change. I manually installed the new akmods package using 'rpm -U' but initially I could not get 'akmods --force' to build the module again. Looking at the logs it was failing with a missing dependency of 'elfutils-libelf-devel'. I then installed this using 'dnf install elfutils-libelf-devel' and re-ran 'akmods --force', and I now have working wifi! I'd assume if I was installing directly from the rpmfusion repo then this dependency would be automatically taken care of. If this therefore is the expected behaviour then I would say this bug could be closed. Thanks again Nick Hello, (In reply to mobile.harvey from comment #2) > Thanks for making the change. I manually installed the new akmods package > using 'rpm -U' but initially I could not get 'akmods --force' to build the > module again. Looking at the logs it was failing with a missing dependency > of 'elfutils-libelf-devel'. I then installed this using 'dnf install > elfutils-libelf-devel' and re-ran 'akmods --force', and I now have working > wifi! Thanks for pointing this dependency issue. You should normally install the akmod-wl package without the need to manually and previously install the required dependencies. > I'd assume if I was installing directly from the rpmfusion repo then this > dependency would be automatically taken care of. If this therefore is the > expected behaviour then I would say this bug could be closed. You are right when you say that this dependency should be automatically taken care of, but it was not the case. As I updated the last akmod-wl package for rawhide and F-26 to take care of this dependency issue, I wonder if you don't mind testing this new package? In case you accept it, please could you remove the elfutils-libelf-devel package before proceeding? Here is the commands you should type in a root console in order to accomplish the test (be careful some lines are wrapped): dnf remove elfutils-libelf-devel dnf install http://koji.rpmfusion.org/kojifiles/packages/wl-kmod/6.30.223.271/11.fc26/x86_64/akmod-wl-6.30.223.271-11.fc26.x86_64.rpm The last command should install the new akmod-wl package and its dependencies including elfutils-libelf-devel package. Please, could you post the result if this is not the case in order to correct the package? The URL of the akmod-wl package for F-26 was taken from this link: http://koji.rpmfusion.org/koji/buildinfo?buildID=3705 Thanks again for your comments, and feel free to make any ones you think useful. Cordially, -- NVieville Hi - I've just tried this following your instructions and the new package installed no problem pulling-in the dependencies automatically. So looks good to me! Thanks again Nick Hello Nick, Thank you for your feedback. I'll let this bug report opened for a while, hoping it would be useful for people hitting the same issue. Cordially, -- NVieville Fedora 26 will be EOL this coming Friday. Once that happens, RPMFusion will stop releasing updates for this version of Fedora. This bug will be set to RESOLVED:EXPIRED next week to reflect this. If the problem persists after upgrading to the latest version of Fedora, please update the version field of this bug (and re-open it if it has been closed). Closing this bug with the EXPIRED resolution since Fedora no longer ships updates for this version of Fedora. Please set the Version field to a supported version of Fedora if you re-open this bug. |