[Bug 631062] New: Working driver for Broadcom bcm43 is missing, but system behaves like it would be present
http://bugzilla.novell.com/show_bug.cgi?id=631062 http://bugzilla.novell.com/show_bug.cgi?id=631062#c0 Summary: Working driver for Broadcom bcm43 is missing, but system behaves like it would be present Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: Vojtech.Zeisek@opensuse.org QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=382904) --> (http://bugzilla.novell.com/attachment.cgi?id=382904) HW configuration of the notebook User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; cs-CZ; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-0.1.1 Firefox/3.6.8 I have Dell Vostro 1220 equipped with Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01) wireless card. It is recognized and package b43-fwcutter is installed. I also can see in dmesg message to use install_bcm43xx_firmware. OK, but if I do not do it and go directly to YaST > Network devices, the wi-fi card looks configured and working (it uses driver ssb), but it does not work. After installation, I'd expect (1) it works (the system would automatically perform the operation with download of the firmware), or (2) it does not work and system cries the driver is missing and tells me in user-friendly way what is missing and what to do (something like it is done in Ubuntu). Now, it looks like it works, but id does not. And it is bad. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=631062 http://bugzilla.novell.com/show_bug.cgi?id=631062#c yang xiaoyu <xyyang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |vbotka@novell.com |ovo.novell.com | -- Configure bugmail: http://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#c1 Michal Zugec <mzugec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |mzugec@novell.com InfoProvider| |Vojtech.Zeisek@opensuse.org --- Comment #1 from Michal Zugec <mzugec@novell.com> 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#c2 Vojtech Zeisek <Vojtech.Zeisek@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|Vojtech.Zeisek@opensuse.org | --- Comment #2 from Vojtech Zeisek <Vojtech.Zeisek@opensuse.org> 2010-08-19 15:41:16 CEST --- Created an attachment (id=384161) --> (http://bugzilla.novell.com/attachment.cgi?id=384161) Complete 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 <mzugec@novell.com> 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#c3 --- Comment #3 from Michal Zugec <mzugec@novell.com> 2010-08-19 14:24:29 UTC --- I need such hardware to provide tests during installation -- 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 <mzugec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mzugec@novell.com |kernel-maintainers@forge.pr | |ovo.novell.com --- Comment #4 from Michal Zugec <mzugec@novell.com> 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#c5 Rafał Miłecki <zajec5@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zajec5@gmail.com --- Comment #5 from Rafał Miłecki <zajec5@gmail.com> 2011-02-05 18:39:46 UTC --- 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. -- 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 <jeffm@novell.com> 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#c6 --- Comment #6 from Jeff Mahoney <jeffm@novell.com> 2011-04-25 19:02:15 UTC --- Via email from Lulyis <lulyis@gmail.com> 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. -- 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 <zajec5@gmail.com> 2011-04-25 20:58:01 UTC --- (In reply to comment #6)
Via email from Lulyis <lulyis@gmail.com>
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#c8 Rafał Miłecki <zajec5@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Larry.Finger@lwfinger.net --- Comment #8 from Rafał Miłecki <zajec5@gmail.com> 2011-04-25 21:03:52 UTC --- Christopher, Larry: could you modify install_bcm43xx_firmware to reload b43 after installing firmware? This should resolve this bug report. -- 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 <Larry.Finger@lwfinger.net> 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#c10 --- Comment #10 from Rafał Miłecki <zajec5@gmail.com> 2011-04-25 21:23:41 UTC --- (In reply to comment #9)
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.
Remember about b43legacy please. -- 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 <zajec5@gmail.com> 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#c Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|NEW |ASSIGNED -- 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 <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |zajec5@gmail.com --- Comment #11 from Jiri Slaby <jslaby@novell.com> 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#c12 Rafał Miłecki <zajec5@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|zajec5@gmail.com | --- Comment #12 from Rafał Miłecki <zajec5@gmail.com> 2011-04-26 13:05:58 UTC --- (In reply to comment #11)
(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?
None. Kernel driver is fine. Firmware loader which is part of the kernel is also fine. Normally you have to install firmware manually and reload driver. Distro provides install_bcm43xx_firmware which is here to simplify this process. This distro addon lack reloading driver. -- 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 <Larry.Finger@lwfinger.net> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jslaby@novell.com |Larry.Finger@lwfinger.net --- Comment #13 from Larry Finger <Larry.Finger@lwfinger.net> 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.
https://bugzilla.novell.com/show_bug.cgi?id=631062 https://bugzilla.novell.com/show_bug.cgi?id=631062#c14 --- Comment #14 from Rafał Miłecki <zajec5@gmail.com> 2011-08-10 08:58:08 UTC --- (In reply to comment #13)
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.
Larry? Ping? Could you update install_bcm43xx_firmware for 12.1 release? -- 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.
participants (1)
-
bugzilla_noreply＠novell.com