Linked by Dedoimedo on Thu 17th Mar 2011 23:17 UTC
Permalink for comment 466645
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2005-06-29
Right you are, and I've had a similar experience with Debian 6. In fact, I'd say Slackware is now easier to install than Debian, and it still has the old school non-X installer. At least Slackware recognized both of my (fully supported in the kernel since 2.6.20-something) wireless cards, whereas Debian 6 choked on both.
I do the same; I have a USB wireless dongle based on an RaLink chipset with full support in the Linux kernel. For Windows and Mac OS, I keep the relevant installer files on a thumb drive I also carry everywhere.
You may be interested to know that current versions of the Linux kernel have built in support for virtually all wired network chipsets out there, as well as many of the most popular wireless cards today. Specifically the Atheros cards used in many laptops today, some of the RaLink cards in laptops and available in USB dongles, and some Intel chipsets. This is why I was so perplexed that Debian didn't recognize and autoconfigure a wireless card that Ubuntu picks up right away, and Slackware only requires me to issue two terminal commands to use.