Danesh Daroui wrote:

Yes I used YaST. My wireless card exists there too. I changed the module name to "ndiswrapper". Thats all I did. My wireless card is Broadcom. You will need to add "blacklist bcm43xx" to /etc/modprobe.d/blacklist so it doesn't try to load that module to use ndiswrapper.

-- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 6/3/07, Jerry Feldman wrote:

There is a Broadcom driver in 10.2 bcm43xx.ko. It needs firmware. You don't need NDISWRAPPER. You can use bcm43xx-fwcutter to cut the firmware out of the Windows Broadcom .sys file. Works much better than NDISWRAPPER.

If I were to grab the bcm43xx.ko file out of 10.2, would it work in 10.1/SLED 10? peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

I had tried fwcutter before and "ndiswrapper" worked better. Anyway, I had to add my wireless card again (because it was already detected by YaST) and it now works fine. D. Jerry Feldman wrote:

On Sun, 03 Jun 2007 13:40:47 +0200 Danesh Daroui wrote:

...

Hi,

Yes I used YaST. My wireless card exists there too. I changed the module name to "ndiswrapper". Thats all I did. My wireless card is Broadcom.

There is a Broadcom driver in 10.2 bcm43xx.ko. It needs firmware. You don't need NDISWRAPPER. You can use bcm43xx-fwcutter to cut the firmware out of the Windows Broadcom .sys file. Works much better than NDISWRAPPER.

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

On Sunday 03 June 2007, Jerry Feldman wrote:

On Sun, 03 Jun 2007 13:40:47 +0200

Danesh Daroui wrote:

...

Hi,

Yes I used YaST. My wireless card exists there too. I changed the module name to "ndiswrapper". Thats all I did. My wireless card is Broadcom.

There is a Broadcom driver in 10.2 bcm43xx.ko. It needs firmware. You don't need NDISWRAPPER. You can use bcm43xx-fwcutter to cut the firmware out of the Windows Broadcom .sys file. Works much better than NDISWRAPPER.

However this is not much better than Ndiswrapper. You still need the windows binary blob, and you need to find the right version of fwcutter for the specific .sys file you have. Fwcutter always lags the release of new drivers, often by some months. Ndiswrapper just runs the windows drivers and you are usually up and running in no time. If Fwcutter got you free of binary blobs it might be attractive, but untill it does I just don't see the advantage. -- _____________________________________ John Andersen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org