News for hackers. Stuff that matters.
Re:Major Linux Problems on the Desktop, 2020 edition by AsyncAwait on Sunday May 31, 2020 @07:13AM (#23368767)
> Because the proprietary Linux driver doesn't support Wayland.

Sure, so don't get NVIDIA hardware for Linux. People don't seem to compile long lists about how the Mac doesn't really have an NVIDIA option, it's considered that your hardware is restricted in that way on the Mac and so you're going into it knowing that. Well, Linux is the same way, just exclude NVIDIA from your list unless you're on a desktop, fine running X and fine with their proprietary driver.

This is not something we can reasonably fix without NVIDIA's direct involvement, so I see no point of including it. It's like complaining the Raspberry Pi can't run your favorite x86 programs.

Re:Major Linux Problems on the Desktop, 2020 edition by alerighi on Sunday May 31, 2020 @08:14AM (#23369043)
You can avoid computers with NVIDIA hardware, but imagine the average person that wants to switch to Linux from Windows, he already has a Windows computer that has an NVIDIA GPU, then tires Linux on it and nothing works, and goes back to Windows.

But the problem is not only NVIDIA, the problem is Xorg in general, is too old to support new hardware like HiDPI screens, and Wayland is not yet stable enough for me.

Re:Major Linux Problems on the Desktop, 2020 edition by AsyncAwait on Sunday May 31, 2020 @08:41AM (#23369195)
> he already has a Windows computer that has an NVIDIA GPU, then tires Linux on it and nothing works

He doesn't try installing macOS on his Windows PC, so perhaps we need to educate people to buy Linux hardware if they want to try Linux.

Also "nothing works" is hardly true. The proprietary driver works for your most common use case for such an user i.e. desktop, running X11 and mostly gaming, watching Netflix etc.

You run into problems on laptops with switchable graphics or if you are into the latest and greatest and want Wayland, but in that case one should seek Linux-specific hardware.

Regarding Wayland, I have various machines running amdgpu or Intel's i915 no problem, so tailoring your choice of hardware to what's well supported would help here.

Re:Major Linux Problems on the Desktop, 2020 edition by JoeAltmaier on Sunday May 31, 2020 @08:44AM (#23369209)
"Linux hardware" is meaningless? I don't think there's any such thing as "Windows hardware". The drivers are supposed to abstract that away.

If Linux doesn't work on hardware, its the usual reason that Linux receives little love in the market so drivers lag Windows drivers in coverage and features.

Re:Major Linux Problems on the Desktop, 2020 edition by laumars on Sunday May 31, 2020 @07:06PM (#23373795)
> I don't think there's any such thing as "Windows hardware". The drivers are supposed to abstract that away.

Microsoft disagrees with you[1][2], as do most online retailers of electronic goods who list supported OSs on their product pages and still include Windows in that list.

[1] https://docs.microsoft.com/en-us/windows-hardware/drivers/da...

[2] http://i1-news.softpedia-static.com/images/news2/Certified-f...

Re:Major Linux Problems on the Desktop, 2020 edition by AsyncAwait on Sunday May 31, 2020 @09:12AM (#23369363)
> I don't think there's any such thing as "Windows hardware".

The majority of laptops you can pick up at BestBuy are "Windows hardware" - they're indeed specifically manufactured to run Windows and hardly anything else. If you want to test this, try installing Windows on your ISP's router or on a TALOS II workstation and see how well Windows "abstracts that away".

> the usual reason that Linux receives little love in the market so drivers lag Windows drivers

Which is directly related to most PCs coming with Windows preinstalled, so most people being either unaware of Linux or seeing little reason to switch to Linux since Windows already runs their Chrome anyway.

What you're confusing is the fact that the majority of PCs are made with Windows in mind, if the majority of PCs came with Linux or BeOS or OS/2, Windows would be in a similar position, maybe even worse since companies would not get the benefit of open code, therefore even less reason to contribute to a minority OS.

If Linux was the standard, many people would be so familiar with it and happy enough to see little reason to switch to Windows, that is if they ever happen to have learned an alternative exists in the first place.

Re:Major Linux Problems on the Desktop, 2020 edition by JoeAltmaier on Sunday May 31, 2020 @10:00AM (#23369642)
So? This is the world we live in. Linux gets no love. Its less performant and less desirable on the desktop/laptop for this reason.
Re:Major Linux Problems on the Desktop, 2020 edition by AsyncAwait on Sunday May 31, 2020 @10:23AM (#23369751)
Performance is entirely dependent on use-case, there are many where Linux outperforms Windows, especially if you're a developer, but as to why it is less "desirable" has mainly to do with what comes per-installed on 99% of Walmart PCs.

Pre-installed is king, if there's extra step involved for the competition, it's not a game one can easily win.

Re:Major Linux Problems on the Desktop, 2020 edition by diamondo25 on Sunday May 31, 2020 @09:53AM (#23369595)
The main reason stuff is mostly windows compatible is due to the fact that driver management is a mess (different distros with different drivers and/or linux kernel versions). The ABI/API issues that are complained about are not helping this.

Even if there are drivers, most of the time they are developed by external people that only wanted to get it working _to a certain level_. Manufacturers dont care about Linux, most of the times, because its hard to develop an installer that is compatible with _Linux_.

I have a story about a friend of mine that tried to make a led driver for the Beaglebone Black. He looked for the documentation, and there was some stuff about an old, deprecated way of toggling GPIOs (pass pin ID) and a new interface (gpiod, using pinctrl and identifier). The documentation was also talking about ACPI, which was totally unrelated[1]. He tried to use "the right way" (using the latest and gratest API), but it was not clear on how to implement this api, as he was experienced with switching registers manually, the embedded way, and had little experience with the Device Tree.

Eventually he wanted to use iomap to just do the gpio toggle _manually_ because it was better documented (read chip documentation and done). He got this idea from when he went to this Korean school as an exchange student, and it was _common practice_ to do this by teachers!

Small example about the gpio madness, google for "linux gpio kernel": 1. A generated page of the API, but also some implementation documentation. [2] 2. Readme file from the kernel, telling you that this is not the documentation you are looking for (old api). [3] 3. An actual article that explains the old and new interface, but still all userspace [4] 4. LWN docu from 2013 using the old api [5]

[1] https://www.kernel.org/doc/html/v4.17/driver-api/gpio/board....

[2] https://www.kernel.org/doc/html/v4.17/driver-api/gpio/index.... [3] https://www.kernel.org/doc/Documentation/gpio/sysfs.txt [4] https://embeddedbits.org/new-linux-kernel-gpio-user-space-in... [5] https://lwn.net/Articles/532714/

Re:Major Linux Problems on the Desktop, 2020 edition by laumars on Sunday May 31, 2020 @07:29PM (#23373996)
Your argument is rather muddled there to say the least. You start off talking about consumer hardware then bring up an anecdote about a developer writing userland software against a developer board (ie non-consumer hardware) and use that as an argument that the Linux kernel is hard to develop against despite there being nothing in your anecdote discussing kernel development.

"Anacdata" is always going to be pretty sketchy in any technical debate but here it seems especially so since this isn't even your own first hand experiences (let alone relevant to the point you were trying to prove).

Re:Major Linux Problems on the Desktop, 2020 edition by AsyncAwait on Sunday May 31, 2020 @10:13AM (#23369710)
The main reason is, as I stated, because Windows is where the market is.

You're categorically wrong about hardware vendors not supporting Linux, in fact many of Linux developers are employed by these companies, be it Intel, AMD, Linaro, Qualcomm etc.

The problem usually is that one needs the right combination of components for things to work well "out of the box" and so for example avoiding certain GPUs or WiFi chipsets, (others work fine).

This is not up to the individual component manufacturers who are already contributing upstream, but up to the OEMs assembling the complete machines to avoid the ones who don't and many do not simply consider Linux when doing so, because customers are accustomed to Windows and they get a good deal on it from Microsoft anyway, so why bother.

In recent years, DELL has stepped up on this front, Lenovo is coming around and you even have dedicated vendors like System76 selling good hardware with Linux pre-installed.

Your "story" is a problem with a specific vendor (Beaglebone) and then ARM in general, which is a bit of a wild west compared to x86, but that's the nature of ARM that Linux tries to accommodate for, not a Linux problem specifically.

I do wonder why your friend did not install Windows on the Beaglebone and did not interact with the hardware that way? It seems like the experience there is so much better.

What is that? The Beaglebone does not support Windows at all? Well, I guess Windows hardware support is rather poor then.

Re:Major Linux Problems on the Desktop, 2020 edition by diamondo25 on Sunday May 31, 2020 @11:19AM (#23370090)
Its the other way around for Beaglebone support. TI has apparently used their own interrupt logic, and Windows IoT Core doesn't seem to support that. ( https://blogs.msmvps.com/dvescovi/2018/01/20/beaglebone-and-... ).

I was mainly talking about how development on Linux Kernel can be tedious, the adoption of the drivers is usually limited and thus the gains are too low. How come that Realtek is one huge manufacturer of network chips, but their drivers on linux are still crap? Everybody knows that, and if they dont yet know, they usually get bitten by it one day, use google, and _accept their faith_. Users are easy to accept how things are and dont bother to improve because its too hard/complicated/not rewarding.

People that are in control of these issues are the developers. The only thing I hear about Intel/Nvidia from Linux people is complaints about how shitty they are, and why they dont open up their stuff. One key thing might be that debugging of kernel things is not easy on Linux, as listed on the Original Post url? Crash a windows box, hook a debugger on it and off you go. If you dont know enough, im sure windows will help you get it running when you pay them. Oh? Linux doesnt work that way? Bummer.

Maybe the abstractions of Linux's core is at the same time its main weak point. Theres nobody governing a stable api and theres not enough telemetry to detect regressions. Yes, i said it. 99% of the people don't care if theres telemetry reported if it can improve the product. As a developer myself, I would _love_ to have _real world issues_ reported to me, automatically.

anyhow. Nothing is perfect. Linux could be better if there was a team behind it that want to get it "production ready". Like, maybe tell the user why something doesnt work, instead of shouting on the internet that they should buy "linux compatible hardware", which is telling the regular user to buy blinker fluid.

Re:Major Linux Problems on the Desktop, 2020 edition by AsyncAwait on Sunday May 31, 2020 @12:07PM (#23370429)
> was mainly talking about how development on Linux Kernel can be tedious, the adoption of the drivers is usually limited

You literally provided an example that does not work in your favor to prove your point.

> Realtek is one huge manufacturer of network chips, but their drivers on linux are still crap?

That's not the case for years, rehashing the same arguments you had a decade ago, or simply being this clueless does not help your case.

> the only thing I hear about Intel/Nvidia from Linux people is complaints about how shitty they are, and why they dont open up their stuff.

You don't really know what you're talking about and it shows. Intel is fine, they have dedicated developers supporting Linux with open-source code, the problem is an Intel+NVIDIA laptop combo and this is due to NVIDIA, not Intel.

NVIDIA support is crap, because NVIDIA wants it to be crap, since they sell enough GeForce GPUs to gamers not to care, nothing Linux can really do about that, it seems that Intel and AMD have no problem shipping a kernel driver. It's a culture thing, more than anything.

And yes, we want the driver to be open, caring about free software is one of the major reasons to go with Linux.

> One key thing might be that debugging of kernel things is not easy on Linux, as listed on the Original Post url?

Much, much easier than on Windows, you even get DTrace, get to inspect the code etc. That's not the issue. Anyone who wants to provide a driver has no problem providing one.

ARM is its own beast, but as I said earlier, this is mostly due to there not being a standard way to i.e. probe hardware like there is on x86 and that's ARM, not Linux at fault here.

Does Linux have problems, sure. But as someone who had family members with Windows 10 call me that they lost their files after an update and the internet is full about the latest macOS being the new Vista, I wouldn't be too sure the competition fares better.

> Yes, i said it. 99% of the people don't care if theres telemetry reported if it can improve the product.

Maybe they don't care, but I'd argue they seldom even know about it or understand the implications.

> As a developer myself, I would _love_ to have _real world issues_ reported to me, automatically.

Part of the free software movement is about equality between users and developers because developers have unquestionably more power. This is more of an ideological thing than anything. Nobody's saying telemetry isn't useful, just that one should be up-front, opt-in, full disclosure about it.

A large part of us care about that, about privacy and the future of unrestricted, general-purpose computing.

I am sure many don't and for them Windows and macOS are there. If Linux doesn't work well for you, that's fine, what I find annoying is pretending that Windows/macOS are somehow way less annoying to use, when every time I use them, I come across crappy behavior.

Re:Major Linux Problems on the Desktop, 2020 edition by gsich on Sunday May 31, 2020 @08:43AM (#23369205)
>Sure, so don't get NVIDIA hardware for Linux.

This is one of the excuses people make, it's condensending. Most of the time you already have the hardware before you want to try Linux. Users don't care whos at fault here (Kernel/distro/x11/nvidia) the end result is that it doesn't work as opposed to Windows.

Re:Major Linux Problems on the Desktop, 2020 edition by AsyncAwait on Sunday May 31, 2020 @08:49AM (#23369240)
I have said this many times, but it's worth repeating; people don't seem to have a problem with not being able to run macOS well on their Windows PC.

It's condescending to the Linux community to always have to deal with users who don't even put in the minimal amount of effort to get Linux compatible hardware and only install it on crap machines Windows doesn't work well for them on anymore.

I find that extremely disrespectful of the community and my time and do not wish to support such users. A large part of us do this in our free time out of passion, asking the user to put in the minimum amount of effort necessary really isn't much.

Proprietary companies who don't care one bit about their customers get the benefit of the doubt and people buy only supported hardware, but Linux is always supposed to care about some second rate hardware of users who don't care about anything, but "free as in beer".

This may not be the most popular thing to say, but I honestly don't care about such users anymore.

Re:Major Linux Problems on the Desktop, 2020 edition by gsich on Sunday May 31, 2020 @08:56AM (#23369277)
>I have said this many times, but it's worth repeating; people don't seem to have a problem with not being able to run macOS well on their Windows PC.

Well, Apple does not provide an official release for those PCs, so the analogy is not apt.

>This may not be the most popular thing to say, but I honestly don't care about such users anymore.

And as a result Linux still only has 0.x% market share. "Fuck you Nvidia" and public shame might help more.

Re:Major Linux Problems on the Desktop, 2020 edition by AsyncAwait on Sunday May 31, 2020 @09:25AM (#23369441)
"Linux" does not provide an "official" release for your crappy PC either. If it's x86, it happens to be compatible, but guess what? macOS's x86 as well, hence the whole Hackintosh community.

The difference being, Hackintoshers seem to know they need specifically supported hardware if they want to have a good experience.

> Linux still only has 0.x% market share

Linux will have that marketshare regardless, because 99% of Walmart PCs Karin buys simply come with Windows. If the reverse was true, guess what marketshare Windows would have?

> "Fuck you Nvidia"

It's not like NVIDIA wasn't endlessly approached nicely first, offered assistance by the community etc. So at this point, fuck NVIDIA indeed.

I've been running Linux for close to two decades full time and it has worked sufficiently well for me for all that time, but anyone for who that's not the case, I am willing to help to an extent, provided there was some good faith effort on their part as well, since I am donating my free time.

If not, be my guest with your bug free Windows 10[1] and the well liked macOS Catalina[2].

1 - https://www.tomsguide.com/uk/news/what-the-hell-windows-10-u...

2 - https://www.macworld.co.uk/news/mac-software/problems-macos-...

Re:Major Linux Problems on the Desktop, 2020 edition by gsich on Sunday May 31, 2020 @11:44AM (#23370245)
You can try to compare it to macOS all you want, the comparison is still wrong. For starters, I can't just go to Apples website to download an image that will boot on my PC.

"Linux" (as in Kernel) no. Distributions yes. Just look at their websites when downloading.

>Linux will have that marketshare regardless, because 99% of Walmart PCs Karin buys simply come with Windows. If the reverse was true, guess what marketshare Windows would have?

Still Windows. But this is a purely hypothetical question, nobody knows if the software world would have developed differently if Windows would not be preinstalled.

Re:Major Linux Problems on the Desktop, 2020 edition by AsyncAwait on Sunday May 31, 2020 @01:43PM (#23371138)
> For starters, I can't just go to Apples website to download an image that will boot on my PC.

Are you auguring about licensing here? macOS's obviously not open-source so you cannot just download it off their website for free but you can absolutely boot in on your PC, there's an entire Hackintosh community around it.

If what you're trying to say is that a Hackintosh is not a supported configuration, there are entire databases with supported hardware for Linux. If you have an incompatible component, you're running an unsupported configuration.

But moving onto Windows, the hardware there needs to be compatible too, it's just that going into Walmart you're likely to run into PCs designed with Windows in mind, due to the whole IBM/MS pact of the 80s and the resulting IBM PC clone industry preinstalling Microsoft software ever since. Linux came after MS was already preinstalled on most PCs, so you have to specifically seek it out.

Pretending that this isn't the case, the playing field was fair and "Windows" just won is dishonest at best.

> But this is a purely hypothetical question, nobody knows if the software world would have developed differently if Windows would not be preinstalled.

If you're telling me that in a world where 99% of PCs are Linux preinstalled, kids are familiar with Linux from school and nonetheless people are going out of their way to manually install Windows on them, I think you're selling me a bridge.

I don't see people demanding the ability to install Windows onto a Raspberry Pi for example, (yes there's Windows for IoT, not the same).

Re:Major Linux Problems on the Desktop, 2020 edition by gsich on Sunday May 31, 2020 @07:34PM (#23374036)
>Are you auguring about licensing here? macOS's obviously not open-source so you cannot just download it off their website for free but you can absolutely boot in on your PC, there's an entire Hackintosh community around it.

Yes. But that's not from Apple directly and not really the point here. macOS on PCs is for the hardcore, the 1%, the people who like to tinker with their system. Not as an alternative to Windows. There is no guarantee that the next update will survive a reboot.

>If you're telling me that in a world where 99% of PCs are Linux preinstalled, kids are familiar with Linux from school and nonetheless people are going out of their way to manually install Windows on them, I think you're selling me a bridge.

Ideally there would have been no OS preinstalled and you had to chose yourself. But again, hypothetical example. Would Winodws still be dominant in this example? My guess is yes, based purely on how GUI friendly the OS is.

Re:Major Linux Problems on the Desktop, 2020 edition by atemerev on Sunday May 31, 2020 @07:22AM (#23368807)
It is possible to run NVIDIA cards on Mac Pro (or with eGPU hardware). There is no alternative to NVIDIA for many software engineers working with HPC and/or simulations / deep learning tasks; many applications and libraries require CUDA, and there is no alternative for CUDA (OpenCL and ROCm are much lower-level).

I personally use Linux with NVIDIA cards, it works reasonably well, and some desktop environments now even work with Wayland (as of 2020).

Re:Major Linux Problems on the Desktop, 2020 edition by vetinari on Sunday May 31, 2020 @09:58AM (#23369627)
> some desktop environments now even work with Wayland (as of 2020).

Wayland compositors themselves work. What is a problem is sharing GPU resources between different applications using different APIs.

I.e., you have your compositor using OpenGL and your application using Vulkan. The application renders itself into a buffer and sends it to the compositor, to render the desktop.

If the compositor and application cannot share buffers, the application has to read it from GPU, put into system RAM and share with compositor via SHM. The compositor then writes it back to VRAM. (Obviously, when application renders itself via software-only, this is not an issue.)

When the compositor and application can share buffer, the application just send the buffer handle to compositor, done.

This sharing on Linux is done via dma-buf. AMD and Intel drivers use dma-buf, so it is not a problem. Nvidia proprietary driver doesn't, it uses it's own EGLStreams, so it is incompatible with compositors. It is similar, as if Nvidia drivers for Windows started ignoring WDDM and started doing their own thing, complete with their own display server. It would also become incompatible with the rest of system. For some reason, Nvidia thinks it is fine to do that in Linux something, that they would not dare to do in Windows.

Re:Major Linux Problems on the Desktop, 2020 edition by swiley on Sunday May 31, 2020 @07:27AM (#23368834)
Regardless this is an NVIDIA problem and not a Linux one.
Re:Major Linux Problems on the Desktop, 2020 edition by jcelerier on Sunday May 31, 2020 @07:47AM (#23368934)
> It is possible to run NVIDIA cards on Mac Pro (or with eGPU hardware).

only very select cards. I used to have a GTX 690 and could absolutely never get a hackintosh to get hardware acceleration through it.