Re: [Mactel-linux-users] How to uninstall madwifi driver

[Tomás T. <tom...@gm...>]

El Sunday 28 December 2008 19:55:19 Justin P. Mattock escribió:
> Tomás Teijeiro wrote:
> > Hi everybody,
> >
> > I have a macbook (2,1) with Kubuntu Intrepid x86_64 installed. Since
> > wireless works out of the box with ath9k, I've installed the madwifi
> > driver (trunk r3878) because of better performance and network detection.
> > The problem is that if I want to go back to ath9k, no networks are found
> > and I'm unable to connect to anyone. What I did is to reinstall the
> > linux-generic package (at the moment 2.6.27-11-generic). The wmaster0 and
> > wlan0 interfaces are sucesfully created, but they don't work. No special
> > dmesg messages are shown. What can I do to recover wireless with ath9k?
> >
> > Thank you very much for your help,
> >
> > Tomas
> >
> > ------------------------------------------------------------------------
> >
> > -------------------------------------------------------------------------
> >-----
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Mactel-linux-users mailing list
> > Mac...@li...
> > https://lists.sourceforge.net/lists/listinfo/mactel-linux-users
>
> Hmm I experience the same issue,
> i.g. wpa_supplicant -Dwext -iath0(or wlan0) -c /etc/*
> seems to gives me nothing,
> but if I use NetworkManager both modules
> run fine.
> maybe try an older version of wpa_supplicant,
> or use NetworkManager, or wicd.
>
> regards;
>
> Justin P. Mattock


Thanks Justin,

But the problem is that the interfaces don't work properly. For example, if  I 
execute:
 iwlist wlan0 scan
No networks are found, although there is an AP with WEP encryption near the 
computer. Moreover, I'm using wicd as my network manager. On the other side, 
if I test a Kubuntu Intrepid live-CD, wifi works well with ath9k.

I think that the problem is that the madwifi installation has removed or 
replaced some key modules of ath9k, but is strange, because the problem 
remains after booting with different kernels.

Again, thank you very much for your help;

Tomas