[Bug 464385] New: Driver for wi-fi Broadcom BCM4318 does not work
https://bugzilla.novell.com/show_bug.cgi?id=464385 Summary: Driver for wi-fi Broadcom BCM4318 does not work Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: vojta.sc@seznam.cz QAContact: qa@suse.de Found By: --- In openSUSE 11, wi-fi card Broadcom BCM 4318 worked good with driver from package bcm43xx from Packman's repository. This package is no longer available for 11.1. Afetr fresh instlation of openSUSE, YaST tried to use kernel module ssb as driver for the card. It did not worked. After I installed kernel module broadcom-wl-kmp-pae from Packman's repository, I have available modules b43 and b43legacy, but they do not work. When I set using YaST network module driver to b43 or b43legacy, the network device dissappears completely from list of active devices... -- 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=464385 Vojtech Zeisek <vojta.sc@seznam.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- Found By|--- |Customer OS/Version|Other |openSUSE 11.1 Priority|P5 - None |P2 - High Platform|Other |i686 -- 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=464385 User rvojcik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464385#c1 Robert Vojcik <rvojcik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |vojta.sc@seznam.cz --- Comment #1 from Robert Vojcik <rvojcik@novell.com> 2009-01-13 09:25:14 MST --- Hello, you can use kernel driver b43 which is already in the kernel. This driver need firmware extracted from original drivers, so you must install b43-fwcutter. This is tool for extract firmware from original driver. Firmware you can download from here: http://linuxwireless.org/en/users/Drivers/b43#devicefirmware If you will be successful close this bug. 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=464385 User andrescimmarusti@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464385#c2 Andres Cimmarusti <andrescimmarusti@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |andrescimmarusti@yahoo.com Info Provider|vojta.sc@seznam.cz | Severity|Normal |Major --- Comment #2 from Andres Cimmarusti <andrescimmarusti@yahoo.com> 2009-01-26 22:47:29 MST --- I agree with Vojtech. But the problem is deeper. I recently installed a fresh copy of OpenSuSe 11.1 32-bits on my laptop HP Pavilion dv5035nr equipped with a broadcom 4318 chipset. Since I have no wired internet connection I could NOT do this: sudo /usr/sbin/install_bcm43xx_firmware So I followed the instructions outlined here: http://linuxwireless.org/en/users/Drivers/b43#devicefirmware I downloaded the 'broadcom-wl-4.150.10.5.tar.bz2' source package from another computer and did the following: tar xjf broadcom-wl-4.150.10.5.tar.bz2 cd broadcom-wl-4.150.10.5/driver/ sudo b43-fwcutter -w "/lib/firmware" wl_apsta_mimo.o After rebooting, the device started working. I was able to connect to my wireless network and to surf the net (slow speed), but only briefly. The connection was lost and it wouldn't connect back or simply I could get no transmission at all. Its behavior was extremely erratic. Naturally I was NOT able to get updates using yast. Because I had some experience using Ubuntu with the older firmware version (broadcom-wl-4.80.53.0) I decided to download this source package and install it by using b43-fwcutter. The result was fabulous. I am now able to connect to distinct wireless connections with ease. The transmission is stable and does not get lost. This is what I did: tar xjf broadcom-wl-4.80.53.0.tar.bz2 cd broadcom-wl-4.4.80.53.0/kmod/ sudo b43-fwcutter -w "/lib/firmware" wl_apsta.o then reboot For the record, this problem with bcm4318 is present in several distros. As far as I know the problem exists in Ubuntu 8.10, OpenSuSe 11.1 and Fedora 10 (from what I've gathered from their forums and bug reports). it remains to be seen if the newer driver is flawed or is conflicting in some way. -- 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=464385 User andrescimmarusti@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464385#c3 --- Comment #3 from Andres Cimmarusti <andrescimmarusti@yahoo.com> 2009-01-26 22:57:43 MST --- Here is my post in opensuse forums: http://forums.opensuse.org/network-internet/wireless/405678-bcm4318-opensuse... it has the outputs of commands such as lspci, dmesg and iwconfig, all of which show no problem what so ever with the newer firmware. Nevertheless, the wireless connection behaved as I have described before -- 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=464385 User vojta.sc@seznam.cz added comment https://bugzilla.novell.com/show_bug.cgi?id=464385#c4 --- Comment #4 from Vojtech Zeisek <vojta.sc@seznam.cz> 2009-01-27 01:53:53 MST --- I was successful with install_bcm43xx_firmware and it works fine. But, driver from Packman's repository is broken (I know this is not Packman's bugzilla, but, might be here are people from Packman:-) and it is difficult for beginners to search for information in system log (it appears there when you try to use it), where they can find direct link to linuxwireless.org. It could ask user if he would like to install it (like in Ubuntu). It would be much more comfortable. And also, why YaST Network Module tries to use kernel module ssb as a driver? It was default setting. Not working at all :-) So I would not close it for now. -- 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=464385 User chrubis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464385#c5 Cyril Hrubis <chrubis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chrubis@novell.com Component|Network |Kernel AssignedTo|bnc-team-screening@forge.pr |kernel-maintainers@forge.pr |ovo.novell.com |ovo.novell.com --- Comment #5 from Cyril Hrubis <chrubis@novell.com> 2009-03-02 09:11:13 MST --- Okay do not report multiple issues into one report. Please open separate report for YaST. I'll move this bug to kernel maintainers as it seems that kernel driver doesn't work with newer 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=464385 Greg Kroah-Hartman <gregkh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |jbenc@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=464385 User jbenc@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464385#c6 Jiri Benc <jbenc@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #6 from Jiri Benc <jbenc@novell.com> 2009-03-02 09:56:57 MST --- The b43 driver is based on reverse-engineering and has been written without any support from Broadcom. It is still work in progress, not everything about the cards is known yet. An interface between the driver and the firmware is slightly different between different firmware revisions; the exact amount of success often depends both on the actual hardware and the actual firmware revision. There is also a binary driver from Broadcom but it is poorly written - expect hangs and strange occasional conflicts with other drivers if you decide to use it (and don't report it to openSUSE bugzilla as we cannot fix anything if a closed source driver is loaded). We won't ship this driver, it violates the Linux kernel license and makes the system unsupportable and unstable. Sorry, we cannot do anything here. You can contact Broadcom and try to push them to opensource their driver or release their specs; however, that approach has been ineffective so far. I suggest to vote with your dollars and buy wifi cards from other vendors. -- 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