> There's a completely different set of directions at
> http://www.tuxmagazine.com/node/1000167
> This approach uses ndiswrapper to translate between a windows driver
> and the operating system. I've tried installing it and I successfully
> loaded the module into the kernel. Everything went OK until the
> section entitled "Set up networking." I used the "Network Settings"
> GUI, which takes a long time but eventually says that the wireless
> interface is active. When I say "ifup eth2" to the terminal, it says
> "interface eth2 already configured." However, this doesn't solve the
> ESSID and Access Point problems, and the directions don't help.
I think you need to be using wlan0 or similar rather than eth2.
FWIW, straight Debian is a PITA to configure wireless on. I prefer the
Debian stable derivative SimplyMEPIS, that has all the desktop
enhancements baked in. Life's too short.
MEPIS is KDE. If you prefer Gnome, Ubuntu or Mint would good alternatives.
--
Mark Warner
MEPIS Linux
Registered Linux User #415318
_______________________________________________
BLUG mailing list
BLUG@linuxfan.com
http://mailman.cs.indiana.edu/mailman/listinfo/blug
No comments:
Post a Comment