https://bugzilla.novell.com/show_bug.cgi?id=747485 https://bugzilla.novell.com/show_bug.cgi?id=747485#c1 Petr Tomeš changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ptomes@gmail.com --- Comment #1 from Petr Tomeš 2012-02-17 04:31:25 UTC --- I can confirm this bug on Fedora 17 development release (rawhide) with GNOME (see my submitted bugreport https://bugzilla.redhat.com/show_bug.cgi?id=790978) and on openSUSE 12.2 M1 too. openSUSE 12.1 LiveCD GNOME and KDE works well without the issue. -- 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=747485 https://bugzilla.novell.com/show_bug.cgi?id=747485#c3 --- Comment #3 from Neil Rickert 2012-03-09 14:52:40 UTC --- Created an attachment (id=480742) --> (http://bugzilla.novell.com/attachment.cgi?id=480742) The full output of "lspci -xxxnnvv" on the affected system The command "lspci -xxxnnvv > nwr.lspci" was run shortly after bootup on the affected system. -- 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=747485 https://bugzilla.novell.com/show_bug.cgi?id=747485#c5 Joey Lee changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |nrickert@ameritech.net --- Comment #5 from Joey Lee 2012-03-10 00:02:50 UTC --- (In reply to comment #4)

Created an attachment (id=480743) --> (http://bugzilla.novell.com/attachment.cgi?id=480743) [details] Full output from dmesg shortly after boot

The command "dmesg > nwr.dmesg" was run shortly after bootup.

Please help to enable b43 debug log like this: # modprobe -r b43 # modprobe b43 verbose=3 Then attach dmesg on here. If cann't remove b43, then please kindly add verbose=3 to /etc/modprobe.d for b43 driver. Thanks -- 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=747485 https://bugzilla.novell.com/show_bug.cgi?id=747485#c7 Larry Finger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Larry.Finger@lwfinger.net --- Comment #7 from Larry Finger 2012-03-12 16:24:10 UTC --- This device uses the bcma interconnect. In kernels 3.1 and 3.2 (openSUSE 12.1 and 12.2 MS1), such devices is handled by code that is internal to the brcm80211 drivers. In 3.2, the kernel configuration contained a bug that prevents the building of brcmsmac whenever bcma is built. As your posting shows that bcma-pci-bridge is controlling your device, it follows that brcmsmac, the driver you need, is not a part of your system. In 12.2 MS2, the kernel has been changed to 3.3-rcX where the problem has been fixed. Now brcmsmac uses bcma. In addition, b43 has been updated to drive the BCM4313. If you really want to use 12.2 MS1, you will need to generate your own kernel, or build bleeding-edge compat-wireless for it. -- 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=747485 https://bugzilla.novell.com/show_bug.cgi?id=747485#c9 --- Comment #9 from Matt Chen 2012-03-13 15:33:17 CST --- (In reply to comment #7)

This device uses the bcma interconnect. In kernels 3.1 and 3.2 (openSUSE 12.1 and 12.2 MS1), such devices is handled by code that is internal to the brcm80211 drivers. In 3.2, the kernel configuration contained a bug that prevents the building of brcmsmac whenever bcma is built. As your posting shows that bcma-pci-bridge is controlling your device, it follows that brcmsmac, the driver you need, is not a part of your system.

In 12.2 MS2, the kernel has been changed to 3.3-rcX where the problem has been fixed. Now brcmsmac uses bcma. In addition, b43 has been updated to drive the BCM4313.

If you really want to use 12.2 MS1, you will need to generate your own kernel, or build bleeding-edge compat-wireless for it.

Yes, The driver for broadcom wifi [14e4 4727][1] should be brcmsmac. Try to run the follow commands as root account in console. 1. modprobe -r b43 2. modprobe -v brcmsmac. Then see if the wifi can work. Another driver is proprietary which from broadcom official website released. See : http://www.broadcom.com/support/802.11/linux_sta.php -- 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=747485 https://bugzilla.novell.com/show_bug.cgi?id=747485#c11 Larry Finger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #11 from Larry Finger 2012-03-13 17:05:02 UTC --- That result is to be expected. In kernel 3.2, brcmsmac cannot be built is module bcma is enabled. As stated in comment #7, that is a bug that has been fixed in 3.3. -- 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.