Bug 412248 - Install Broadcom firmware during initial setup
Summary: Install Broadcom firmware during initial setup
Status: RESOLVED FIXED
: 470127 (view as bug list)
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: Network (show other bugs)
Version: Alpha 1
Hardware: i386 Other
: P3 - Medium : Enhancement (vote)
Target Milestone: ---
Assignee: Michal Zugec
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-25 16:04 UTC by Larry Finger
Modified: 2021-02-26 20:14 UTC (History)
1 user (show)

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
YaST log (8.65 MB, text/plain)
2008-08-10 20:07 UTC, Larry Finger 		Details
Output of echo '`Read(.probe.netcard)'|/usr/lib/YaST2/bin/y2base stdio scr (3.87 KB, text/plain)
2008-09-01 11:45 UTC, Helmut Schaa 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Larry Finger 2008-07-25 16:04:25 UTC 
With the inclusion of the script /usr/sbin/install_bcm43xx_firmware in 11.0, a major step was taken in the setup of BCM43xx devices. The next step is to run that script automatically during the initial setup if the host has both network access and a bcm43xx device is detected. This step would ease support for the BCM43xx wireless devices.
Comment 2 Michal Zugec 2008-08-04 13:24:57 UTC 
But this should work (already implemented). Could you provide YaST logs?
Comment 3 Larry Finger 2008-08-10 20:07:15 UTC 
Created attachment 232596 [details]
YaST log

I had the Ethernet connection in place when booting the Live CD and when installing. In both cases, the system tried to connect using the wireless, but ignores the Ethernet. Without firmware, there is an error box that pops up saying I have no network connection. I can make it manually, but it doesn't happen automatically.
Comment 4 Larry Finger 2008-08-31 19:24:56 UTC 
This still did not work with 11.1 alpha 2. In this case I installed from the DVD, not the Live CD. I had network access, but no firmware was installed. I still had to run the /usr/sbin/install_bcm43xx_firmware script manually.

Larry
Comment 5 Michal Zugec 2008-09-01 10:29:08 UTC 
This process is activated for driver "b43", but for your model is only "ssb" driver offered. Helmut, could you help here?


                      "active":true,
                      "bus":"pci",
                      "busid":"0000:04:00.0",
                      "dev_name":"wlan0",
                      "drivers":[
                                  $[
                                     "active":true,
                                     "modprobe":true,
                                     "modules":[
                                                 [
                                                   "ssb",
                                                   ""
                                                 ]
                                     ]
                                  ]
                      ],
                      "link":nil,
                      "mac":"00:19:7d:3c:92:51",
                      "modalias":"pci:v000014E4d00004312sv0000103Csd0000137Cbc02sc80i00",
                      "module":"ssb",
                      "name":"BCM4312 802.11a/b/g",
                      "num":0,
                      "options":"",
                      "requires":[

                      ],
                      "sysfs_id":"/devices/pci0000:00/0000:00:0d.0/0000:04:00.0",
                      "type":"wlan",
                      "udi":"/org/freedesktop/Hal/devices/pci_14e4_4312",
Comment 6 Helmut Schaa 2008-09-01 11:45:28 UTC 
Created attachment 236547 [details]
Output of echo '`Read(.probe.netcard)'|/usr/lib/YaST2/bin/y2base stdio scr

A special version of the ssb-module drives the b43 wireless cards. Hence ssb is associated to the network interface as module (and not b43). One difference between the normal ssb module and the b43-ssb module is the drivers name "b43-pci-bridge".

Attached is the output you've asked for :)
Comment 7 Michal Zugec 2009-11-11 17:20:14 UTC 
*** Bug 470127 has been marked as a duplicate of this bug. ***
Comment 8 Michal Zugec 2009-11-11 20:02:09 UTC 
problem fixed in yast2-network-2.18.59