A new patch series posted today to the Linux kernel mailing list would block kernel modules/drivers from TUXEDO Computers from accessing GPL-only symbols in the kernel.
TUXEDO Computers maintains a set of kernel drivers currently out-of-tree for their various laptops for additional functionality around power profiles, keyboard backlight controls, WMI, sensor monitoring, the embedded controller, and other functionality. They have said they want to eventually mainline these drivers but in the name of allowing for rapid hardware support they maintain them out-of-tree and ship them with their Ubuntu-based TUXEDO OS and also have the driver sources available via GitLab.
The issue at hand though is that these kernel drivers marked as GPLv3+ and that conflicts with the upstream Linux kernel code licensed as GPLv2. There was a commit to change the driver license from GPLv3 to GPL(v2) but was reverted by TUXEDO Computers on the basis of “until the legal stuff is sorted out.”
Imagine having such a hard-on for letting corporations exploit your work in abusive Tivoized products that you stoop to retaliation against a company that’s actually trying to protect their customers.
one of the awesome things about buying a linux laptop from a linux company like tuxedo is that you don’t have to worry about things like this since they have paid developers who maintain their own distro to “take care” of things like this and buying one of these linux laptops has made my experience smooth and thought free as a mac user.
it’s a double edge sword however: lemmy has taught me that smooth sailing with linux laptops keeps you unaware of the trouble that lurks beneath the surface and that’s disconnected me from the general linux user experience and has gated me from understanding the common themes and problems they encounter; i’ve started a new linux build and this time i’m going to do it the same way everyone here does, with a windows laptop.
that’s disconnected me from the general linux user experience
are we romanticizing having a broken system?
@bunitor @eldavi yeah, why? This just shows that, if more hardware companies actively supported linux, there would be no issues left for non-tech end users, which would be awesome.
Please buy laptops and desktops from tuxedo, system76, framework, etc, and recommend them. They’re doing a great job and do deserve the support.
Please buy laptops and desktops from tuxedo, system76, framework, etc, and recommend them. They’re doing a great job and do deserve the support.
amen. i’ll continue to buy from them for the things that i depend on (eg low cost personal servers and high end work laptops); but i plan to use a generic low-spec windows laptop for daily driving to teach me what the general linux user experience is like these days since lemmy is showing me that i still get something out of helping other people while i simultaneously get to leverage my knowledge and experience in an arena that’s been enabling my life for these last 3 decades to do so.
it’s bit like the mandates that i get from my management as an individual contributor; but more “WTF” and the “TIL’s” that i get from it makes it more fun for me.
Preferably the drivers and quirks of the hardware would all be patched upstream so that you don’t need to use a distro with the fixes patched in.
very much so in addition to creating a new project for myself that’s exciting; that’s a big deal to me because i can’t remember the last time in decades that i felt any excitement over any linux based project.
i learn best by challenging my knowledge and it teaches me where i’m ignorant and i can use that specify which areas to focus my self education.
i have a regular desktop computer and a very smooth user experience here, no complaints.
laptops can be hit or miss because of all the custom proprietary crud in them.
laptops can be hit or miss because of all the custom proprietary stuff in them.
my experience is the same and that’s why i’m going with a laptop; i wonder if the skills i’ve picked up since the last time i tried are going to help any since they’re the kind of skills that get you paid in the linux world.
selfhosting is more like that tbh. unless you mean cherrypicking and adapting drivers for your kernel and this sort of stuff… general desktop troubleshooting helps to a point imo
Agreed it’s great that they provide firmware support and (hopefully) upstream it eventually. But I also hope they have well documented steps somewhere on how to install it on another distro, because it’s likely many people install their own anyways.
i’m glad you brought that up; lemmy has taught me that people will use those linux company distros w/o the support and it blows my mind and makes me agree that they should be upstreaming it; i know that system76 does (eventually) and i wonder if tuxedo or anyone else does as well.
laroyê
What are you talking about? I run (atomic) fedora and I have a smooth experience.
You could easily sell your mac and buy a normal computer to have a smooth experience if the mac results in lots of problems
i don’t have a mac anymore; but this exactly why i’m pursing this project: the last time i did this fedora atomic didn’t exist and i’m likely to encounter that it’s more rock solid than the fedora distros that i used to daily drive with before buying a linux laptop directly from the linux factory.
why would they use the gplv3 in the first place? didn’t they know it’s incompatible with v2?
They know it’s better than v2.
So, gpl3 is apparently not GPL and is somehow proprietary. Sure, makes perfect sense. Idk where they even find those geniuses.
GPL3 has extra restrictions banning patients etc. So yeah a lot of GPL 2 code written by companies that open software but not hardware. Would have legal questions about running with GPL 3
GPL 3 was created to be more restrictive to non-open hardware.
GPLv3 is less proprietary than GPLv2, in the sense that it does a better job at protecting end-users from being abused by device makers that would try to close up their Linux-based system.
Only if those device makers are willing to use it. And that has always been the tightrope linux has walked.
Its very history as a x86 platform means it has needed to develop drivers where hardware providers did not care. So that code needed to run on closed hardware.
It was bloody rare in the early days that any manufacturer cared to help. And still today its a case of rare hardware that needs no non free firmware.
Free hardware is something I’ll support. But it is stallman et als fight not the linux kernel developers. They started out having to deal with patented hardware before any one cared.
Yeah, but dudes there are kinda pissed off about semantics, IMO. Like, unless there’s a PR from tuxedo using the same v3, I don’t think it should concern them in the slightest… And instead of saying “keep in mind it’s not upstreamable” they go out of their way to mark tuxedo’s patches as proprietary 🤨
proprietary
Well related to the owner is the very definition of proprietary. So as far as upstream vs not available for upstream is concerned. That is what the term is used for in linux.
So yep by its very definition while a manufacture is using a licence that other distributions cannot embed with their code. Marking it proprietary is how the linux kernal tree was designed to handle it.
EDIT: The confusion sorta comes from the whole history of IBM and the PC.
Huge amounts of PC hardware (and honestly all modern electronics) are protected by hardware patients. Its inbuilt into the very history of IBMs bios being reverse engineered in the 1980s.
So as Linux for all its huge hardware support base today. It was originally designed as a x86(IBM PC) compatible version of Unix.
As such when Stallman created GPL 3 in part as a way of trying to end hardware patients. Linux was forced to remain on GPL 2 simply because it is unable to exist under GPL 3 freedom orientated restrictions.
The proprietary title is not seen as an insult. But simply an indication that it is not in the control of the developers labelling it.
Ah, okay, thanks for clarification
You wanna get tivoized? Ha? Because that’s how you get tivoized.
