John Andersen wrote:
On Sun, May 25, 2008 at 1:04 PM, Dominique Leuenberger <Dominique.Leuenberger@tmf-group.com> wrote:
On 25-05-2008 at 09:57, Sampsa Riikonen <sampsa.riikonen@iki.fi> 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.
I don't think his question is about "being pure", whatever that means, but why someone go to all the trouble of running a wrapper around a windoze driver, when there is a perfectly good native linux driver. I've got an HP compaq v6000 laptop, running hardy heron with the native linux bcm driver, and since everything works perfectly, with no need to futz around with windoze drivers and ndiswrapper, I'd tend to have the same question. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org