bcm 4312 b/g dell wireless 1395

Hi guys, I’m new to the OpenSUSE forums. I’m having trouble with my dell wireless card. I got the driver from Broadcom.com - 802.11 Linux STA driver.
I’m using this one because the stable one doesn’t support may card . My problem is when I extract it and run the make command, it says there is no makefile found. I’m in the directory with the makefile. I think I need kernel headers but I don’t know where to get them. Thnx guys.

On 10/24/2009 05:06 PM, danotto wrote:
>
> Hi guys, I’m new to the OpenSUSE forums. I’m having trouble with my dell
> wireless card. I got the driver from ‘Broadcom.com - 802.11 Linux STA
> driver’ (http://www.broadcom.com/support/802.11/linux_sta.php).
> I’m using this one because the stable one doesn’t support may card . My
> problem is when I extract it and run the make command, it says there is
> no makefile found. I’m in the directory with the makefile. I think I
> need kernel headers but I don’t know where to get them. Thnx guys.

Are you using the standard kernel? If so, why not add the appropriate
Broadcom wl package from the Packman repo?

If you really must compile your own, then you need the kernel headers
package!

but when i install it with yast nothing happens. what do i do from there? do i have to utilize the firmware cutter?

On 10/24/2009 10:06 PM, danotto wrote:
>
> but when i install it with yast nothing happens. what do i do from
> there? do i have to utilize the firmware cutter?

The firmware cutter is only used for b43. The Broadcom drivers,
whether wl or the Windows drivers, have the firmware embedded in the
driver.

What does the command below show?

dmesg | egrep “ssb|wl”

well now that i rebooted it works, my linksys comes up, but it wont connect successfully. our linksys has a password, which i know, but it wont ask for it, and it fails to connect. im using knetworkmanager. not yast.

our linksys has a password, which i know, but it wont ask for it, and it fails to connect. im using knetworkmanager. not yast.

Have you tried editing the connection? It should be possible to configure so that it parses your password.

I have warious broadcom 43xx wireless cards and my home wireless is linksys too (n/g). I think your problem can be:

  1. You have no router…ony a modem and and a access-point (linksys-n), for linux it is important to have all this componetnts (modem/router/acesspoint).

  2. It can be that you have a WPA-Key…i dont know wy, but the WPA support in linux with Broadcomcips is bad. Cange the Key in WEP-128bit. If you dont know how, use the way how you made it first time or take a wired cable and tip in your firefox-browser the adress (its in your linksysmanual) for a browserbased configuration…you have then the screen of your linksys-linux in your browser…its easy! Only click-ing, no commands…:wink:

  3. It can be, that you dont know how to use knetworkmanager…its not so easy like in gnome…make new connection…then tip your password in and then click to new connection. You cant connect at first and then waiting for passwordquestion…

On 10/25/2009 05:16 AM, Caleb IX wrote:
>
> deano_ferrari;2055363 Wrote:
>> Have you tried editing the connection? It should be possible to
>> configure so that it parses your password.
>
> I have warious broadcom 43xx wireless cards and my home wireless is
> linksys too (n/g). I think your problem can be:
>
> 1. You have no router…ony a modem and and a access-point (linksys-n),
> for linux it is important to have all this componetnts
> (modem/router/acesspoint).
>
> 2. It can be that you have a WPA-Key…i dont know wy, but the WPA
> support in linux with Broadcomcips is bad. Cange the Key in WEP-128bit.

This is BS. All the drivers for Broadcom chips handle WPA/WPA2.
Changing the encryption to the vastly inferior WEP method is NOT the
answer.

> If you dont know how, use the way how you made it first time or take a
> wired cable and tip in your firefox-browser the adress (its in your
> linksysmanual) for a browserbased configuration…you have then the
> screen of your linksys-linux in your browser…its easy! Only click-ing,
> no commands…:wink:
>
> 3. It can be, that you dont know how to use knetworkmanager…its not
> so easy like in gnome…make new connection…then tip your password in
> and then click to new connection. You cant connect at first and then
> waiting for passwordquestion…

You do need to “make a new connection”. That is the only advice in
this post that I would advise following!

thnx guys the knetworkmanager connects to my network. i just added the pacman rep in yast and got the broadcom-wl packages. reboot, it works.

also i click on my connection knetworkmanager, edit connections, set it to WPA personal, but my password in shared key, save and connect, and wala! solved

On 10/25/2009 04:16 PM, danotto wrote:
>
> also i click on my connection knetworkmanager, edit connections, set it
> to WPA personal, but my password in shared key, save and connect, and
> wala! solved

That is exactly the way it should be. Congratulations.

The simple way is best way!
Have fun!