Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The sad state of Linux Wi-Fi

blog.sesse.net

Post reply on HN
Print view View original

241–250 of 274 posts

Re: The sad state of Linux Wi-Fi

#241

Post by anon4 »

clarry wrote: post #94
antocv wrote: post #77

Earlier quoted context omitted.

PulseAudio still requires you to be a hacker to get sound over network - something it promised to do well, but oh doesnt.

If you aren't blessed with luck, one might say that PulseAudio still requires you to be a hacker to get sound. Over and over again. Every time you think it's fixed for good, it'll prove you wrong.

Or if you're even less lucky, PulseAudio still requires you to mute the "system sounds" thing because once skype starts, you get persistent noise out of the audio jack, after which you try to email Lennart following the guide on his page, only to receive no reply.

Re: The sad state of Linux Wi-Fi

#242

Post by clarry »

andor wrote: post #237
rphlx wrote: post #231

Earlier quoted context omitted.

Unnecessarily complex daemon; three lines in /etc/network/interfaces and a few shell scripts will suffice, thank you very much.

What's good for you might not be the best option for the majority of people. Making things that "just work" means handling complexity for users, and leads to somewhat complex code. Debian's static network configuration is great for servers and okay for desktops that never move. But it's nothing that you should put on laptops operated by enterprise users (the people that pay for Linux desktop development). Imagine use…

Handling complexity by piling more complexity on top is sadly very common, even so common that people think it's inevitable. But it's not the only way. The other way can sometimes be harder, and it tends to take more thought, but in the end you may actually solve and get rid of complexity.

Re: The sad state of Linux Wi-Fi

#243

Post by Nursie »

freehunter wrote: post #98
krakensden wrote: post #39

Earlier quoted context omitted.

I haven't had trouble with printing in years- in fact, I can basically print on everything with no configuration, and people with OS X and Windows laptops seem to have lots of problems.

My Lexmark X4850 begs to differ. No drivers, doesn't work, period. Lexmark doesn't care, and apparently no Linux driver developers have this printer, so no one has made support for it yet.

Lexmark have historically been badly supported in Linux because of their DRM shenanigans and their lack of interest.

Don't buy Lexmark, basically.

Re: The sad state of Linux Wi-Fi

#244

Post by jaseemabid »

rasz_pl wrote: post #240
deathanatos wrote: post #186

Earlier quoted context omitted.

I disagree. It's possible to get advanced output from various command line tools in Linux, and it's possible to get networking information. It's much more difficult to do that on other OSs, especially Windows. I loathe debugging network troubles in Windows, because there is essentially no information. OS X has most of your standard tools, though some in some odd places, e.g., printing the routing table not being done…

>I disagree. It's possible to get advanced output from various command line tools in Linux dont worry, Lennart Poettering (systemD/pulseaudio) is working to solve this problem

Sarcasm?

Re: The sad state of Linux Wi-Fi

#245

Post by jaseemabid »

zanny wrote: post #175

Right here: https://wikidevi.com/wiki/Atheros_AR5B22 This thing works. I just buy them in bulk. I can get one for $13 off ebay. Any device I run Linux on, I replace whatever half size mpcie card it has with one. I don't fuck with the realtek or broadcom chips I get, because ath9k is all-open, no proprietary firmware, works out of the box. Drivers are in any kernel since the 3 series started, the bluetooth is just a g…

That was some valuable tip. Thank you.

Re: The sad state of Linux Wi-Fi

#246

Post by scjody »

pwnna wrote: post #140
yellowapple wrote: post #125

Earlier quoted context omitted.

Depends on the programs you use, and whether or not you're running a full DE or a bare WM. Most programs use Ctrl+X/C/V, Shift+Delete/Shift+Insert/Control+Insert, and/or highlight/middle-click in various unpredictable combinations. I've found this to be less of a problem in modern desktop environments (especially KDE, in my experience), since most DEs nowadays feature their own clipboard/buffer management.

Huh. Interesting. I only ever use C-x C-c C-v, and then C-Shift-c C-shift-v in my terminal emulator so I never notice these issues.

For me even that's annoying enough. On a mac it's consistently command-x command-c command-v everywhere, whereas in Linux I have to think "oh, I'm in a terminal now, use shift", and if you get it wrong things screw up (e.g. C-shift-v opens the inspector in Firefox if memory serves).

Re: The sad state of Linux Wi-Fi

#247

Post by andor »

clarry wrote: post #242
andor wrote: post #237

Earlier quoted context omitted.

What's good for you might not be the best option for the majority of people. Making things that "just work" means handling complexity for users, and leads to somewhat complex code. Debian's static network configuration is great for servers and okay for desktops that never move. But it's nothing that you should put on laptops operated by enterprise users (the people that pay for Linux desktop development). Imagine use…

Handling complexity by piling more complexity on top is sadly very common, even so common that people think it's inevitable. But it's not the only way. The other way can sometimes be harder, and it tends to take more thought, but in the end you may actually solve and get rid of complexity.

Complexity can be caused by the developers of the software, and in that case it is unwarranted. But my assumption is that NetworkManager developers are reasonably competent, and take good decisions in all the trade-offs they have to make.

In their case, they need to support lots of features, and make all of them work seamlessly: multiple Ethernet, Wifi and VPN interfaces, IPv4/IPv6 configuration, modems, firewall policies, and so on. n^m different states. To get rid of this complexity, you'd need to remove options at the bottom of the stack, e.g. only allow communication via serial port at a fixed rate.

Re: The sad state of Linux Wi-Fi

#248

Post by noisy_boy »

slacka wrote: post #192
zanny wrote: post #173

Earlier quoted context omitted.

If those are really under GPL, nothing should stop you from converting them into a kmod using the kernel 802.11 architecture and pushing them upstream. I'd imagine that since it hasn't happened yet there is something else at work impeding it.

They ARE GPLv2. See for yourself. 4.0.2_9000: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langi... Converting them to the latest kernel driver interface is beyond my skills and pvaret's rtl8192cu-fixes. Pvaret's remarks on github indicate it's a hack to just get them running and someone with Linux networking internals experience is needed to do a proper port. I'd be willing to test and file bug reports. Yo…

> Is there anything I can do to help? What steps do I need to do?

Normally I would agree with you but zanny's reply was perfectly legitimate for your above question. I don't see any attitude from his/her side.

Re: The sad state of Linux Wi-Fi

#250

Post by driverdan »

sandGorgon wrote: post #27

Copy 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…

You completely forgot the many GPU issues that still exist.
Post reply on HN