[plug] wireless nic setup problem

William Kenworthy billk at iinet.net.au
Sun Dec 3 21:13:58 WST 2006


ipw2200 based, or even the broadcom (they have in-kernel drivers, but I
am using ndiswrapper att) far outperformed the netgear card.  Steer
clear of atheros based chipsets (of course).

I have used both the sourceforge and in-kernel drivers for the ipw2200,
and other than not being able to use in-kernel a few versions back, they
are nice and stable now.

I also have a dlink G650+ and thats another to steer clear of.  It has
resource issues on many laptops I try it on.

BillK




On Mon, 2006-12-04 at 12:03 +0800, Jon Miller wrote:
> Any suggesstion for a good card?
> 
> Jon
> 
> >>> billk at iinet.net.au 12/03/06 12:56 PM >>>
> Rather than using the madwifi sources (which can be a real nightmare),
> you should be looking at your distros packages which will take much of
> the pain and uncertainty out of the process.
> 
> I was using this card for a year or so - what a piece of crap!
> 
> BillK
> 
> On Sun, 2006-12-03 at 12:55 +0800, Richard Meyer wrote:
> > On Sun, 2006-12-03 at 10:52 +0800, Jon Miller wrote:
> > > I'm having problems setting up my netgear WG511T 108Mbps wireless nic on my IBM ThinkPad A22m.  It uses the atheros chipset.  I'm using SUSE 10.0 OSS, YAST sees and cofigure the nic but it does not get an IP Address from the SpeedStream modem.  Although another laptop with the NetGear WG511v2 54Mbps on a Windows XP system is working fine.  Not that this proves a lot other than the DHCP is working.
> > > I went to the website madwifi.org to check ut the document Newbie HowTo for wireless nic setup I ran into problems in the conpiling of the program.  Stating that 'cc: command not found
> > > and only kernel versions 2.4.x and above are supported although the kernel version of this laptop is 2.6.13.
> > > 
> > > Any advice would be greatly appreciated.
> > > 
> > > Jon
> > 
> > Well, first of all, you need to install GCC to get a compiler. ;-) Then
> > you should probably also install the kernel source so that the driver
> > can find the header files it needs.
> > 
> > I have no idea about Wifi and chipsets, though, so that's probably as
> > far as I can help.
> > > 
> > > _______________________________________________
> > > PLUG discussion list: plug at plug.org.au
> > > http://www.plug.org.au/mailman/listinfo/plug
> > > Committee e-mail: committee at plug.linux.org.au
-- 
William Kenworthy <billk at iinet.net.au>
Home!



More information about the plug mailing list