wicd doesn't work
NoOp
glgxg at sbcglobal.net
Wed Apr 1 16:31:54 UTC 2009
On 04/01/2009 08:32 AM, Robert Holtzman wrote:
> On Wed, 1 Apr 2009, Shannon McMackin wrote:
>
>> Thanks for reminding Karl that in most cases you must blacklist the
>> ath5k driver which Ubuntu tries to use by default and install the
>> madwifi driver. That is if the backports module for your kernel doesn't
>> fix your issues.
>
> I can't remember ever running across the concept of blacklisting
> drivers. Could someone elaborate on the mechanics?
>
> Thanks.
>
<http://www.google.com/search?complete=0&hl=en&q=ubuntu+%2Bblacklist+ath5k&btnG=Search>
https://help.ubuntu.com/community/WifiDocs/Driver/Atheros
https://help.ubuntu.com/search.html?&q=blacklist&sa=Search
[click the search button]
Basically, when you do not want a driver to load on boot, you can
'blacklist' the driver via /etc/modprobe.d/blacklist.
$ cat /etc/modprobe.d/blacklist
will show you what it blacklisted.
More information about the ubuntu-users
mailing list