John Andersen wrote:
On Sun, May 25, 2008 at 8:32 PM, Joe Sloan <joe@tmsusa.com> wrote:
John Andersen 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,
On Sun, May 25, 2008 at 1:04 PM, Dominique Leuenberger <Dominique.Leuenberger@tmf-group.com> wrote: 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 --
"HE" didn't want to be pure, but Dominique seemed to want him to be.
"HE" just wanted it to work, and the BCM driver was not working for him with his chipset. Ndiswrapper has worked for him in the past.
If he could get rid of the non-working but "perfectly good" (says you) BCM driver he could get the ndiswrapper working again and be back to an operational machine before the BCM driver improved the hell out of it.
Even the BCM driver needs to load firmware, so there is really no point in getting all high and mighty about free software when it comes to wifi drivers from broadcom.
I'm not sure who's getting "high and mighty", but that's beside the point. It sounds like the OP needed to load the bcm firmware. So, maybe it's just me, but my first thought would be "load the bcm firmware", rather than "install a wrapper program to enable to use of a wireless driver written for a different platform". In my experience, things work better when they are all of a piece. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org