I followed the directions from the wireless sticky, at least as far as I could, here are my results. i tried this before in version 11.0 and I got to the same spot and then had no luck. I have the device that lwfinger mention in his post regarding a driver he developed so I’m hoping things will go easy.Thx for the help
On 11/18/2009 03:06 AM, Jimbo G wrote:
>
> This might not help that much, but did you see this thread? ‘Brodcom
> 4312 firmware installation problem. - openSUSE Forums’
> (http://tinyurl.com/ygj9jok)
You need the broadcom-wl package or the 2.6.32-rc7 kernel.
Thx for the help, I have the aforementioned kernel and installed the firmware. However I know its stupid question but I dont know how to install or load the drivers, assuming I need to because my system still doesnt detect my card. I have a question, so that maybe I can understand and I’m not just doing stuff and have no idea why.So as I understand to resolve my problem I can do (broadcom-wl package) U (2.6.32 kernel) U (ndiswrapper). Now by updating to the new kernel, it just includes the broadcom drivers from the package. So the difference between choice 1 and 2 is just a matter of if I want to run that new kernel? After I install the drivers for my device and if my device is detected its just a matter of setting up the connection as instructed in the stickies for this forum? thx
On 11/18/2009 05:06 PM, quietthought wrote:
>
> Thx for the help, I have the aforementioned kernel and installed the
> firmware. However I know its stupid question but I dont know how to
> install or load the drivers, assuming I need to because my system still
> doesnt detect my card. I have a question, so that maybe I can
> understand and I’m not just doing stuff and have no idea why.So as I
> understand to resolve my problem I can do (broadcom-wl package) U
> (2.6.32 kernel) U (ndiswrapper). Now by updating to the new kernel, it
> just includes the broadcom drivers from the package. So the difference
> between choice 1 and 2 is just a matter of if I want to run that new
> kernel? After I install the drivers for my device and if my device is
> detected its just a matter of setting up the connection as instructed in
> the stickies for this forum? thx
If you use the 2.6.32 kernel, it should load the b43 driver and work as long as
the firmware is installed. Those drivers are built-in and do not need installing.
Please boot the 2.6.32 kernel and post hte ooutput of ‘dmesg | grep b43’. The
initial 2.6.32 kernels built by openSUSE failed to enable the BCM4312. I posted
a bug that has been marked as CLOSED, but I don’t know how long it takes to
propagate through the system.
I just noticed the kernel I booted into begins debug-- opensuse 11.2 2.6.32-rc7-21 dont know exactly what the debug means or if it matters or even if its the correct kernel
On 11/18/2009 09:06 PM, quietthought wrote:
>
> One more thing
>
> I just noticed the kernel I booted into begins debug-- opensuse 11.2
> 2.6.32-rc7-21 dont know exactly what the debug means or if it matters or
> even if its the correct kernel
It is the correct kernel; however, the openSUSE people have not yet set the
correct options, thus the 4312 is not yet enabled. Your options are the
Broadcom-wl driver, or building your own kernel from the sources.
On 11/19/2009 06:56 PM, quietthought wrote:
>
> /usr/sbin/iwconfig
>
>
> lo no wireless extensions.
>
> eth1 IEEE 802.11bg ESSID:""
> Mode:Managed Frequency:2.412 GHz Access Point:
> Not-Associated
> Bit Rate:54 Mb/s Tx-Power:32 dBm
> Retry min limit:7 RTS thr:off Fragment thr:off
> Power Managementmode:All packets received
>
> eth0 no wireless extensions.
>
> /usr/sbin/iwlist scan
>
>
> eth1 Scan completed :
> Cell 01 - Address: 00:24:B2::C8
> ESSID:“comcast”
> Mode:Managed
> Frequency:2.412 GHz (Channel 1)
> Quality:1/5 Signal level:-81 dBm Noise level:-92
> dBm
> IE: Unknown: DD8A0050F
> IE: WPA Version 1
>
> Group Cipher : TKIP
>
> Pairwise Ciphers (1) : TKIP
>
> Authentication Suites (1) : PSK
>
> Encryption key:on
>
> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18
> Mb/s
> 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
>
> 12 Mb/s; 48 Mb/s
>
> Cell 02 - Address: 6F
>
> ESSID:“hamlet”
>
> Mode:Managed
>
> Frequency:2.437 GHz (Channel 6)
>
> Quality:4/5 Signal level:-63 dBm Noise level:-92
> dBm
> Encryption key:on
>
> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
>
> 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36
> Mb/s
> 48 Mb/s; 54 Mb/s
>
> I can see my network(hamlet) but in Yast i still dont see my device, should I?
I presume this is with the wl driver. From the NM applet, click on “Manage
Connections” and “Add” a new one. Enter the ESSID and WEP hex key for your network.