I'm curious - if we can sense and determine the Broadcom chip during system setup, why then can we not add the install_bcm43xx_firmware to the setup, or to "first-boot"? Sort of like we do with the MS fonts? Of course, since we ARE dealing with network drivers, there's always the "chicken and egg" problem. Crap. Jonathon M. Robison Infrastructure Architect, Research Ford Motor Company -----Original Message----- From: Larry Finger [mailto:larry.finger@gmail.com] On Behalf Of Larry Finger Sent: Sunday, September 27, 2009 11:05 PM To: Bernhard Wiedemann Cc: opensuse-testing@opensuse.org Subject: Re: [opensuse-testing] installation report Bernhard Wiedemann wrote:
wontfix: b43 (WLAN) firmware missing -> install_bcm43xx_firmware helps
Just for clarity: This is a "cannot fix" rather than a "won't fix". The copyright on the firmware files is held by Broadcom and they will not give permission to distribute them. The script /usr/sbin/install_bcm43xx_firmware is the most we can do. It downloads driver files that Broadcom had to supply when they were caught in a GPL violation, then extracts the firmware from those files. There is a group in Italy that is working on open-source firmware for the Broadcom chips. Once that package is available, then this whole issue will be avoided. -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org