[LBo] Re: Re: new system setup, progress and questions
Anita Lewis
ajlewis2 at gmail.com
Thu Nov 2 03:39:07 CET 2006
On Wed, 01 Nov 2006 08:24:49 -0700, Ray Still wrote:
> the wireless network is one of the Broadcom 43xx cards, this list indicated
> that the built in broadcom drivers didn't work, and I needed to switch to
> ndiswrapper. the links provided by the list all had parts that didn't work
> with KDE or Kubuntu. example a gnome utility or a file that was a little
> different name or location that I wasn't smart enough to correct for.
> Because of your direction I was able to find a walk through that did work.
> any way, I'm running ndiswrapper and 'lsmod |grep ath' returns absolutly
> nothing. one thing I did notice, mentioned from before, is that the wireless
> card is eth1, not wlan0. does this mean anything?
> thanks,
> Ray
I don't think it matters if the card is eth1. It means that this name
needs to be used in any configuration, though.
I don't really know much about this topic. How are you attempting to
connect? Since you have Kubuntu, I assume you are using the network
configuration GUI there and that this is where you are seeing the card as
eth1. Your wired network card is eth0, I guess.
Maybe if we saw the output of 'ifconfig' it would help us see something.
The other possibly helpful file might be /etc/network/interfaces which
lists the connection possibilities.
It may be that the problem I'm having with connecting in Edgy is not the
madwifi driver after all, but something else. And that might be the same
thing that is happening to you. In my case, I do not see the Access Point
being associated. I don't know why that is or how the system should work
other than that there should be a number listed for the Access Point. I
have this with kernel 2.6.15 but not with the newer kernel. I assumed
that this had to do with the new madwifi driver, but maybe not. Sorry I
can't be of much help.
Anita
More information about the QnA
mailing list