Re: [opensuse] persistent bcm43xx ..



On Mon, 2008-05-26 at 08:16 +0200, Dominique Leuenberger wrote:
On 26.05.2008 at 03:11, "John Andersen" <jsamyth@xxxxxxxxx> wrote:
On Sun, May 25, 2008 at 1:04 PM, Dominique Leuenberger
<Dominique.Leuenberger@xxxxxxxxxxxxx> wrote:
On 25-05-2008 at 09:57, Sampsa Riikonen <sampsa.riikonen@xxxxxx> wrote:
Dear List,

I had my wireless working OK few months ago in my hp tx1000
laptop. The wireless card in this pc is broadcom bcm4312.

.. now it suddenly stopped working (maybe because upgrading
regularly with the updater applet?).

In yast => network devices => etc. => wireless => configure => hardware,
the list of kernel modules does not offer anything (just a blank line)
.. it used to offer ndiswrapper.

I suppose this might be because of the bcm43xx driver.
Well, I have blaclisted it in several files..

Why would you prefer ndiswrapper ove the native bcm43xx driver?
I'd say there is no need to wrap if you have a correctly working, native
linux driver available.

ndiswrapper is meant for wlan cards that do not have linux drivers (yet).

Dominique

Maybe he likes it ndiswrapper because it works and bcm does not work with
his card. You know, basic stuff like that? For many, the need to be pure
is less important than the need to get on line.


That's a nice 'maybe' sentence you can produce here, without any real content. He did
not write so far that bcm does not work. I simply suggested to use the native driver
that is working for so many people.

It's 'purely' amazing what an attitude of 'stcuk-upness' some people have on this
list. I'm really sorry for everybody that has to read such mailing lists. And for sure
our new fellows will be scared away when they have to go through the ML archives, in
hope to find some help.

Can't we just stick to the topics of the questions? Answer our fellow friends,
give them advises? You can follow almost every thread here and they carry on
for ever, with all sort comments that are not at all related to what the original question was.

Think about this for a few minutes!

lspci gives..
---------------------
03:00.0 Network controller: Broadcom Corporation BCM4312 802.11a/b/g
(rev 02)
----------------------
And according to linuxwireless.org ..
"The 802.11a part of the 4309 and 4312 is not supported"
-----------------------
So I suppose I must use ndiswrapper. As you can see from my previous
e-mail, the ndiswrapper installs correctly, but yast does not offer
me any kernel modules. .. just wondering if it is because
of that bcm43xx that refuses to disappear or what?

Sampsa


--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx



Relevant Pages

  • Re: Howto configure Wireless Card in FC5
    ... If the card is plugged in, and there is a native driver ... If there's no native driver, then the next step is up to you. ... I've gone the ndiswrapper route for cards that don't have native drivers ... You obtain the ndiswrapper source and install the wireless-tools package ...
    (Fedora)
  • Re: [SLE] new at wireless configuration
    ... using ndiswrapper for the linksys card to work. ... in /etc/sysconfig/kernel to have the driver loaded during boot. ... Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 ... Thus I have added the network card by using YaST>Network Devices>Network ...
    (SuSE)
  • Re: wireless still
    ... to get ndiswrapper to display bcmw15 driver present, ... We don't know which card you are talking about... ... I had a Belkin F5D7001, ...
    (alt.os.linux.suse)
  • Re: [opensuse] cannot see wireless networks (Suse 10.0)
    ... ndiswrapper -r driver_name ... >> Have a Linksys wireless card using the ndiswrapper for the driver. ... For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx ...
    (SuSE)
  • Re: [opensuse] persistent bcm43xx ..
    ... I had my wireless working OK few months ago in my hp tx1000 ... The wireless card in this pc is broadcom bcm4312. ... I suppose this might be because of the bcm43xx driver. ... Why would you prefer ndiswrapper ove the native bcm43xx driver? ...
    (SuSE)