| 1 |
if you load at boot bcm43xx as hal should do, you have to unload them before |
| 2 |
using ndiswrapper. if you want to stop them from loading put: |
| 3 |
|
| 4 |
blacklist bcm43xx in this file: |
| 5 |
/etc/modprobe.d/blacklist |
| 6 |
and remember that you need also the firmware in /lib/firmware if you're |
| 7 |
using the bcm43xx modules. |
| 8 |
|
| 9 |
for the scripts i don't know what you mean since i didn't find anything on |
| 10 |
the forum. the only script that could be done is the one that adds the |
| 11 |
modules needed for bcm43xx in the kernel, then compile the kernel, then |
| 12 |
install it, then download and cut the firmware, then install the firmware to |
| 13 |
/lib/firmware and then ask you to reboot. since these steps aren't difficult |
| 14 |
for a user to do, i think that there's no need for a script version. |
| 15 |
using wpa_supplicant is easy; just install networkmanager and nm-applet if |
| 16 |
you're using gnome or knetworkmanager if you're using kde and you have a |
| 17 |
fully working utility for wpa managing. you may only have some problems with |
| 18 |
non-standard wpa_enterprise networks and knetworkmanager since it disables |
| 19 |
some configuration options which are disabled from the standard network |
| 20 |
settings. the only thing that you need to do when using networkmanager is to |
| 21 |
delete /etc/init.d/net.eth0 and /etc/init.d/net.eth1 for the first and |
| 22 |
second network interfaces and then do a rc-update add NetworkManager |
| 23 |
default. this will change your network manager from the old ifconfig to the |
| 24 |
new networkmanager. |
| 25 |
|
| 26 |
2007/10/8, Mark Haney <mhaney@××××××××××××.org>: |
| 27 |
> |
| 28 |
> Beso wrote: |
| 29 |
> > just compile these modules: |
| 30 |
> > |
| 31 |
> |
| 32 |
> Well after all is said and done, there was a new ndiswrapper ebuild |
| 33 |
> sitting in portage this morning, so I emerged it and now everything |
| 34 |
> works fine. |
| 35 |
> |
| 36 |
> But, I've got the bcm43xx modules up and running although I've not tried |
| 37 |
> them yet. The reason I mention this is because there was some mention on |
| 38 |
> the forum posts about Gentoo's net scripts and wpa_supplicant that |
| 39 |
> supposedly makes the bcm43xx setup really easy, does anyone know exactly |
| 40 |
> what that means? |
| 41 |
> |
| 42 |
> |
| 43 |
> |
| 44 |
> |
| 45 |
> -- |
| 46 |
> Recedite, plebes! Gero rem imperialem! |
| 47 |
> |
| 48 |
> |
| 49 |
> Mark Haney |
| 50 |
> Sr. Systems Administrator |
| 51 |
> ERC Broadband |
| 52 |
> (828) 350-2415 |
| 53 |
> |
| 54 |
> Call (866) ERC-7110 for after hours support |
| 55 |
> -- |
| 56 |
> gentoo-amd64@g.o mailing list |
| 57 |
> |
| 58 |
> |
| 59 |
|
| 60 |
|
| 61 |
-- |
| 62 |
dott. ing. beso |
Archives