Just to add to this. One issue I found with trying to
run Dyne on my company laptop (IBM Thinkpad T41) was
that the driver exists but the Wifi card (Intel Pro
Wireless 2100) requires a firmware load and I think
the firmware is proprietary. As such it is illegal to
include it in the distro for licensing reasons. What
I do is keep the firmware on the same USB drive as my
nest and just "modprobe -r" the driver module, copy
the firmware to it's correct location then "modprobe"
the driver again. After that, the card shows up in
the "Wireless" configuration tool where I can tell it
my SSDI/WEP key.
--- Dan Conklin <danconklin@???> wrote:

> It's because no one will pay the hardware
> manufacturers enough money to open the source code
> of their wireless chipsets' drivers.There are many,
> many chipsets. However, there are a few which have
> drivers that do exist, and work very well.One of
> them is Atheros with the madwifi drivers. These are
> the best IMHO, and give a wide range of
> control.Another is anything that uses the Prism2 or
> Prism52 drivers, but you need to look at the
> hardware compatibility lists to find which they
> are.Orinoco works well too, but I think you need to
> buy an older card.Some of the Broadcom sets work
> with the latest kernels, but you may still need
> Ndiswrapper. Ndiwswrapper developers try their level
> bestto keep up, but the manufacturers try their best
> to keep ahead, so don't blame them.The answer will
> come when people like you get very rich and give a
> lot of money to open source development




____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com