Description of problem: during the Distribution Upgrade the Broadcom BCM4311 wifi is disconnected from the network. as a result the upgrade stops. the encryption mode has been changed from *WPA/WPA2 Pre-Shared Key* to *open WEP*. resetting the encryption mode back to *WPA/WPA2 Pre-Shared Key* allows reconnection to the network, and the upgrade can continue. after the upgrade has completed and the system is rebooted, the Broadcom BCM4311 wifi will not connect to the network again. This time, removing the 3 x broadcom rpms ( broadcom-wl-common, dkms-broadcom-wl and ?) and then re-installing broadcom-wl-common 6.30.223.271-46.mga6.nonfree, dkms-broadcom-wl 6.30.223.271-46.mga6.nonfree allows the network to be re-configured. upgrade is initialised from fully updated M5.1 (all DE, servers and workstations less development and network computer(client)) and KDE desktop. upgrade is initialised by invoking a terminal as user and $ killall mgaapplet $ mgaapplet --testing Version-Release number of selected component (if applicable): How reproducible:both i586 and x86_64 Steps to Reproduce: 1.create and update a Mga5.1 system (all DE, servers and workstations less development and network computer(client)) 2.invoke the *Distribution Upgrade* applet from KDE desktop 3. during the upgrade, reset the Broadcom wifi encryption settings 4. after reboot, reset broadcom Wifi as above
Keywords: (none) => 6RCSource RPM: (none) => networkmanager 1.62-4mga6 (maybe)
Created attachment 9249 [details] log.txt.xz this log at 1st reboot. at approx 5:43 I connect a wifi usb and time changes to 17:43. after this remove and reinstall the broadcom rpms
Created attachment 9253 [details] at approx april 30 14:49:02 wifi connection to network is lost wifi network connection is re-initialised at approx april 30: 15:00:00
(In reply to ben mcmonagle from comment #1) > Created attachment 9249 [details] > log.txt.xz I think the logs in attachment #9249 [details] were fetched as user instead of as root. (In reply to ben mcmonagle from comment #2) > Created attachment 9253 [details] Attachment #9253 [details] contains more information :-) (I'm puzzled about the logs, I thought that either NetworkManager.service OR network.service should handle the connection, but it seems it's handled by systemd-networkd) > at approx april 30 14:49:02 wifi connection to network is lost > It seems that was a bit earlier: Apr 30 14:40:58 localhost.localdomain [RPM][5991]: erase broadcom-wl-kernel-desktop-latest-6.30.223.271-11.mga5.nonfree.x86_64: success Apr 30 14:40:58 localhost.localdomain [RPM][5991]: erase dkms-broadcom-wl-6.30.223.271-5.mga5.nonfree.x86_64: success Apr 30 14:43:21 localhost.localdomain [RPM][5991]: install dkms-broadcom-wl-6.30.223.271-46.mga6.nonfree.x86_64: success Apr 30 14:44:31 localhost.localdomain [RPM][5991]: erase broadcom-wl-kernel-desktop-latest-6.30.223.271-11.mga5.nonfree.x86_64: success Apr 30 14:44:32 localhost.localdomain systemd-networkd[1018]: wlp1s0 : lost carrier Apr 30 14:45:44 localhost.localdomain [RPM][5991]: erase dkms-broadcom-wl-6.30.223.271-5.mga5.nonfree.x86_64: success Apr 30 14:48:14 localhost.localdomain [RPM][5991]: install dkms-broadcom-wl-6.30.223.271-46.mga6.nonfree.x86_64: success > wifi network connection is re-initialised at approx april 30: 15:00:00 gained carrier 4 times in between 15:03:20 and 15:03:45 in attachment 9253 [details] there are 29 kernel Call Traces: $ xzcat 20764Blog.txt.xz | grep "kernel: Call Trace" | wc -l 29 @ kernel & drivers maintainers I guess you n separate bug report for them? Apart from that, there are 11 segfaults in libpthread-2.22.so and 4 segfaults in libgobject-2.0.so.0.5200.1 which'll probably need separate bug reports, too :-/
CC: (none) => marja11Assignee: bugsquad => kernelSource RPM: networkmanager 1.62-4mga6 (maybe) => broadcom-wl-6.30.223.271-46.mga6.nonfree
Created attachment 9261 [details] log of install (as root this time)
Attachment 9249 is obsolete: 0 => 1
Attachment 9261 description: log of install ( as root => log of install (as root this time)
hi Marja. it seems that the wifi needs to be reconfigured at every boot. the encryption mode changes back to "Open WEP" at every boot. it makes no difference if I use the built in Broadcom wifi or an Atheros wifi usb that I have.