https://bugzilla.novell.com/show_bug.cgi?id=631062 https://bugzilla.novell.com/show_bug.cgi?id=631062#c1 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |mzugec@novell.com InfoProvider| |Vojtech.Zeisek@opensuse.org --- Comment #1 from Michal Zugec 2010-08-19 13:33:41 UTC --- Discussed with reporter: next time on running system it works as expected (when switch to ifup and configure device again). Requested for yast logs ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=631062 https://bugzilla.novell.com/show_bug.cgi?id=631062#c Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|vbotka@novell.com |mzugec@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=631062 https://bugzilla.novell.com/show_bug.cgi?id=631062#c4 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mzugec@novell.com |kernel-maintainers@forge.pr | |ovo.novell.com --- Comment #4 from Michal Zugec 2010-09-06 12:23:38 UTC --- Reproduced with similar result. YaST correctly executed install_bcm43xx_firmware script, in dmesg output I can see that firmware is loaded (so YaST part works fine) but device doesn't work: dhcp8:~ # iwlist wlan0 scan wlan0 Interface doesn't support scanning : Network is down dhcp8:~ # ip link set wlan0 up RTNETLINK answers: Unknown error 132 After reboot it works fine without error. Problem is somewhere in kernel (driver/firware/whatever) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=631062 https://bugzilla.novell.com/show_bug.cgi?id=631062#c Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |jslaby@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=631062 https://bugzilla.novell.com/show_bug.cgi?id=631062#c7 --- Comment #7 from Rafał Miłecki 2011-04-25 20:58:01 UTC --- (In reply to comment #6)

Via email from Lulyis

Everytime that I start my computer, I have to apply this commands:

modprobe -rv b43 rfkill block wifi rfkill unblock wifi modprobe b43

Then, I open the knetworkmanagement and I can enable wireless network and my wireless is working.

This is unrelated. Please create new bug report, including at least "dmesg" and "lspci -vnn"! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=631062 https://bugzilla.novell.com/show_bug.cgi?id=631062#c9 --- Comment #9 from Larry Finger 2011-04-25 21:21:28 UTC --- That would be easy. I need to submit an update to the latest fwcutter and I'll make the modprobe -r b43 modprobe b43 be part of the script. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=631062 https://bugzilla.novell.com/show_bug.cgi?id=631062#c Rafał Miłecki changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Working driver for Broadcom |System installs |bcm43 is missing, but |b43-fwcutter, but after |system behaves like it |firmware installation b43 |would be present |is not reloaded -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=631062 https://bugzilla.novell.com/show_bug.cgi?id=631062#c11 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |zajec5@gmail.com --- Comment #11 from Jiri Slaby 2011-04-26 12:35:26 UTC --- (In reply to comment #5)

b43 tries to load firmware on bringing interface up. If it fails to load firmware, it doesn't retry itself. Network should be restarted after installing firmware.

Thanks for the analysis. So is this a problem in the kernel or in the fw loader? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=631062 https://bugzilla.novell.com/show_bug.cgi?id=631062#c13 Larry Finger changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jslaby@novell.com |Larry.Finger@lwfinger.net --- Comment #13 from Larry Finger 2011-04-26 14:54:02 UTC --- As stated in Comment #12, this is neither a bug in the driver nor in the firmware loading mechanism. The driver checks for firmware when it is first loaded. When the firmware is installed later, there is no mechanism to notify the driver that it should retry. The fix is to modify the script in /usr/sbin/install_bcm43xx_firmware to unload and reload the driver after the firmware has been installed. The only downside is that both b43 and b43legacy will be loaded once this is done. @Jiri: I have reassigned this one to me. As I said in Comment #9, there are additional changes to be done in this area. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.