still you cannot use them at the same time you're using ndiswrapper for
what i know you cannot use bcm43xx or any other linux modules and
ndiswrapper with the same wireless interface at the same time but i
still may be wrong
2007/10/9, Mark Haney <[EMAIL PROTECTED]>:
>
> Beso wrote:
>
Beso wrote:
if you load at boot bcm43xx as hal should do, you have to unload them before
using ndiswrapper. if you want to stop them from loading put:
blacklist bcm43xx in this file:
/etc/modprobe.d/blacklist
and remember that you need also the firmware in /lib/firmware if you're
using the bcm43
if you load at boot bcm43xx as hal should do, you have to unload them before
using ndiswrapper. if you want to stop them from loading put:
blacklist bcm43xx in this file:
/etc/modprobe.d/blacklist
and remember that you need also the firmware in /lib/firmware if you're
using the bcm43xx modules.
f
Beso wrote:
just compile these modules:
Well after all is said and done, there was a new ndiswrapper ebuild
sitting in portage this morning, so I emerged it and now everything
works fine.
But, I've got the bcm43xx modules up and running although I've not tried
them yet. The reason I menti
Mark Haney wrote:
Nuitari wrote:
One of the problems I had with ndiswrapper is that it would just suck
100% of the CPU and literally do nothing. iwlist scan would show
nothing.
I just tried bcm43xx and it worked, so I never tried to get
ndiswrapper back
On Sat, 6 Oct 2007, Beso wrote:
O
Nuitari wrote:
One of the problems I had with ndiswrapper is that it would just suck
100% of the CPU and literally do nothing. iwlist scan would show nothing.
I just tried bcm43xx and it worked, so I never tried to get ndiswrapper
back
On Sat, 6 Oct 2007, Beso wrote:
Okay, I'm game, can y
From: Beso <[EMAIL PROTECTED]>
Reply-To: gentoo-amd64@lists.gentoo.org
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] latest kernel and ndiswrapper
1. if you don't have a 4318 and you won't need to connect to wpa_enterprise
networks with ca certs and so on swit
1. if you don't have a 4318 and you won't need to connect to wpa_enterprise
networks with ca certs and so on switch to the kernel drivers. are a lot
better than ndiswrapper. the only things that fails is the 4318 module when
trying to connect to a wpa_enterprise network that don't broadcast essid,
I just upgraded to 2.6.22-r8 and when I booted into it (after
re-emerging ndiswrapper) I got a hardware error saying it couldn't set
the device up (wlan0). I figured something was flaky with ndiswrapper,
so I booted back into -r5 and tried loading my wireless again and I got
the same error. I
