Linux should simply adopt Android as default UI.
The sad state of Linux Wi-Fi
81–90 of 274 posts
Re: The sad state of Linux Wi-Fi
#82It only gets worse on headless/embedded/arm machines. The RPi list of Wi-Fi adapters gives something of a picture: http://elinux.org/RPi_USB_Wi-Fi_Adapters Note the number of ones which require some additional configuration steps, downloads, patches, or other monkeying around. And don't even get me started on connman and wicd.
wicd is pretty dead. It uses deprecated kernel features that will be removed at some point and with no maintainer for wicd, it will just stop working.
Would you care to list those deprecated features, or provide a source? I know wicd is a dead or dying project, but I didn't know it was that critical.
Re: The sad state of Linux Wi-Fi
#83If you're using NetworkMangler, God help you. Shit's never worked right for me... even connecting to my home wifi it gets way fewer bars than it should, and keeps making and breaking the association.
Using just wpa_supplicant and dhclient, I've had far fewer problems, particularly with Intel wireless chipsets.
Linux would benefit from a bit of expectations management. Some of us neither want nor need a less expensive Windows, and Linux in general tends to function a whole lot better if you don't treat it as such.
Re: The sad state of Linux Wi-Fi
#84One of a handful reasons I don't have Linux on my laptop anymore, even though I like so many things about Linux so much more. I'm not sure about this point, though: > Connection time. I dislike OS X pretty deeply and think that many of its technical merits are way overblown, but it's got one thing going for it; it connects to an AP fast. I remember Linux being slow (and unreliable) at this, but OSX is pretty slow too…
This is one of the reasons I've stopped running Linux 'bare metal' and have instead always just used an OS with good drivers to serve as a VM host. Every time I fire up a Linux VM it makes me feel a little guilty (after all, if everyone does what I'm doing there's essentially 0 reason for hardware providers to think about Linux drivers), but I've consigned myself to the fact that Linux's server roots are always going to show.
Re: The sad state of Linux Wi-Fi
#85when linux works, it's wonderful; when not, it's a pain in the a*^
Re: The sad state of Linux Wi-Fi
#86Copy paste, printing and networking. Biggest usability misses of Linux. I don't consider these technical issues...but usability issues. Things like insisting on keeping the install ISO at 750 mb, leaves seamless driver support out of the todo list because...hey, there are no drivers anyway. I'm really surprised there is not a paid version of Linux with these features baked in. I would GLADLY pay for all these (as wel…
Sound isn't too great either. The BlueZ developers for example decided to drop HSF/HSP support in BlueZ 5.x [1], which means there is no way to get a bluetooth headset (with a microphone) working on Linux anymore; there's just no way. Although it's not like sound is great on Windows either. [1] http://www.freedesktop.org/wiki/Software/PulseAudio/Notes/5....
The irony of this to me is that I started using Linux back in 1998 or so (though I've used it off and on for the past 15 years, I'm far from an expert, just a hobbyist)
But in 1998, Sound on Linux was almost impossible to get working correctly (that's hyperbole, but it wasn't too far off)
It's gotten better, but not by much. But considering 15 years have gone by, that's faint praise indeed.
Re: The sad state of Linux Wi-Fi
#87Imho wifi on Linux should also be taken care of by the Core Infrastructure Initiative - wifi is critical today
http://www.linuxfoundation.org/programs/core-infrastructure-...
Re: The sad state of Linux Wi-Fi
#88Linux should simply adopt Android as default UI.
I feel you don't clearly understand what linux is
Re: The sad state of Linux Wi-Fi
#89Thanks god you use an Intel card. When I bought a Thinkpad, it came with a Realtek card. I'm still connecting through ethernet; never managed to make it work.
I have a thinkpad wired into a wifi bridge. Since it almost never moves nowadays, it's a pert-near ideal setup and sure beats the naff kernel support for the thing's internal rtl8192se chipset.
Re: The sad state of Linux Wi-Fi
#90I stopped using NetworkManager years ago, I just use wpa_supplicant and dhcpcd directly (well I use the systemd services for these so they're started automatically). I also always name the 2.4GHz and 5GHz networks differently, and connect explicitly to the one I want. Yes it would be great if NetworkManager did the right things automatically, but the task might be impossible due to hardware and driver quirks. WiFi ch…
Same here, I kind of never got NetworkManager to do any good, I just gave up, so mii-tool, dhcpcd, iwconfig, wpa_supplicant are well used tools, basically it works fine, when I actually have the drivers. These tools dont bail out on me or try to hide complexities behind more complex abstractions like NetworkManager does. If im going to be troubleshooting anything, its going to be the networking issue and not dbus to…
So basically you need four different tools to set up networking? Well, it sure sounds like the complexities are there and in plain sight then. I can't help but wonder though if it isn't possible to get rid of some of these complexities and make life simpler?