Results 21 to 24 of 24
I feel the original poster's pain. The problem is not with Linux software in general, but with device driver support in particular, and most especially networking devices. The instructions for ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 10-19-2005 #21
- Join Date
- Oct 2005
Consider these wireless USB installation instructions from http://zd1211.ath.cx/zd1211:
* Make sure you have your kernel sources in /usr/src/linux
* Make sure your kernel is compiled with wireless extensions (CONFIG_NET_WIRELESS) and USB support
* Make sure iwconfig is installed (Debian: wireless-tools package)
* Download latest drivers
* untar, make, make install
* insmod zd1211
* ifconfig wlan0 up
* iwconfig wlan0 essid youressid
* dhclient wlan0
In other words, to install this piece of hardware you have to compile and install a new kernel (not an easy feat in it's own right, if only because of the dependency dance), install a new package, run a bunch of commands, all which may fail for one reason or another. Even if done successfully there is no hint as to how to get this to work every time the computer starts up - the user will have to teach themselves about the bootup procedure and adjust accordingly.
It's not clear to me that D-Link or Hawking could have eliminated this process. Assuming they wrote a driver, and distributed an install script to be run as root, how would they have dealt with kernels without "CONFIG_NET_WIRELESS"? Would they have redistributed iwconfig? In what form? For which distribution?
This is not a rhetorical question. If there is a silver bullet I'd like to know about it.
- 10-19-2005 #22Originally Posted by digitaljoshRegistered Linux user #270181
TechieMoe's Tech Rants
- 10-19-2005 #23Originally Posted by fyrephlieDesktop: Dual Xeon 2.8 GHz 1.5 GB RAM Ubuntu/XP Pro
Laptop: Macbook 2 GHz C2Duo 3 GB RAM OS X/ Ubuntu/ XP Pro
Linux Registration #396559
- 10-19-2005 #24
- Join Date
- Oct 2005
As a quick follow up: I'm a long time Linux user, but I've always been "lucky" with my installs. Things have run flawlessly, and I never had to recompile a kernel or finagle with strange configuration files. Networking has always worked flawlessly. I didn't bother helping those with hardware problems because I figured, eh, they must have done something stupid.
Not so. A problematic piece of hardware, especially networking hardware, is a whole new ball game. When something goes wrong on Linux, it is almost always fixable, but it requires a huge level of system administration ability. For most people, learning those skills is somewhat wasted, as it will be used for one install and then forgotten.