Bug 4500

Hello,

Thanks for reporting this issue.

In order to try to determine what the possible reasons of your issue are, I wonder if you could please provide (by adding an attachment) the result of the command lines below typed in a root console (using sudo may be requested) just after you log in:

dmesg
cat /var/log/messages
cat /usr/lib/modprobe.d/broadcom-wl-blacklist.conf
lsmod
rpm -qa | grep -e broadcom -e kmod-wl -e kernel
rfkill list
dmidecode -t 1

For the last one (dmidecode) remove all personal information (serial number,
UUID, etc), just keep the necessary things that can identify your laptop
manufacturer, model, family, etc.

For my part with a BCM4313, first reboot with a 4.10.x kernel lead in a little problem. The module was loaded (lsmod listed), but was nonoperational. I had to "modprobe -r wl" and "modprobe wl" to get it working. Since this episode nothing noticeable about this module, just working as usual.

Please, feel free to make any comment about this issue and your attempts to try to catch it, I'll try to help you as much as possible of my ability in this area.

Cordially,


-- 
NVieville

Created attachment 1765 [details]
Transcript

I've added the transcript you requested. Note that I don't have /var/log/messages, perhaps you meant some journalctl command?

Hello,

Thanks for your response.

Nothing obvious jumped to my eyes in your logs apart that the wl module is not loaded (lsmod command).

Maybe you should rebuild the the kmod-wl package through the akmods command, but before maybe it would be worth removing the actual kmod-wl package.

Please try in a root console:

dnf remove kmod-wl-4.10.8-200.fc25.x86_64-6.30.223.271-7.fc25.x86_64
akmods --kernel 4.10.8-200.fc25.x86_64
modprobe wl

Then see if wl appears in the list of the loaded modules with lsmod command.
If wl module is listed, then reboot to see if it keeps loading at boot time.

If the wl module doesn't load and wireless connection isn't back, then you could provide the file dump-of-journalctl.txt generated by the command:

journalctl -b > dump-of-journalctl.txt

in replacement of the /var/log/messages. Maybe it would be necessary to compact it (gzip or bzip2) to attach it to your message.
 
Please, feel free to make any comment about this issue.

Cordially,


-- 
NVieville

(In reply to NVieville from comment #4)
> dnf remove kmod-wl-4.10.8-200.fc25.x86_64-6.30.223.271-7.fc25.x86_64
> akmods --kernel 4.10.8-200.fc25.x86_64
> modprobe wl

These steps worked perfectly.

Thank you for your prompt help! I'm not sure what would make this upgrade fail, when so many others have succeeded, but hopefully my bit of trouble can help triangulate the cause.

(In reply to Daniel Farina from comment #5)
> (In reply to NVieville from comment #4)
> > dnf remove kmod-wl-4.10.8-200.fc25.x86_64-6.30.223.271-7.fc25.x86_64
> > akmods --kernel 4.10.8-200.fc25.x86_64
> > modprobe wl
> 
> These steps worked perfectly.

Glad to see your wireless device is back again.

> Thank you for your prompt help! I'm not sure what would make this upgrade
> fail, when so many others have succeeded, but hopefully my bit of trouble
> can help triangulate the cause.

I also experienced this issue intermittently on some machines but not all, and for the moment I didn't catch where the problem occurs.

Thanks for reporting the issue.

Cordially,


-- 
NVieville

RPMFusion is no longer 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.