because literally nothing else that ships with KDE supports my machine’s 5G modem…
Why not just take that module, build it yourself, add the firmware package as well, repackage it and install it on whatever distro you like. I know, it sounds like a lot of work, but you only have to do it once… or maybe twice, depending on what is removed/added in future kernels.
I tried a slew of distros - some recognize the modem, but nothing more, most don’t even see/interact with it. It took hours of combing through outdated forums, mailing lists, wiki, etc to find commands that would not only see the modem, but unlock it and connect successfully. This was found on the Debian unstable wiki, and the system would install but fail to boot on stable, so I have no idea if the instructions work for Debian. Kubuntu however, boots successfully on that machine (a ThinkPad) and the modem “works” (is seen) ootb and can be unlocked + used successfully with the rest of the commands in that wiki page.
The fact that I tried nearly a dozen distros, and I tinkerer with it for a literal month, I’m not touching shit. I didn’t want to go Ubuntu for this machine, but cell connectivity (and hotspot hosting) is a 100% requirement, so I’m using what works.
I’m a moderate nix user but fuck packaging my own drivers and figuring out what software packages are needed to enable the modem. 20 years ago, sure. Now, fuck no, it should “just work”. PTSD from wifi not working, requiring windows drivers in a wrapper, etc. I’m not diving into that again, nope nope nope.
The fact that I tried nearly a dozen distros, and I tinkerer with it for a literal month, I’m not touching shit.
Lol 😂, yeah, I can understand that. You just want things to work, totally understandable.
Now, fuck no, it should “just work”.
Agreed. I can understand things not just working 20 years ago, but in this day and age, yes, they should just work.
I think money is the main issue… for most of the devs working on Linux, this is a fun side project, not an actual job. So, they dedicate spare time to this, nothing more. It’s the sad truth I’m afraid.
You don’t have to make it a part of the kernel, it could be an external module, like the firmware. I’ve done it before, it’s not as scary at it sounds. Yes, at a certain point, it will stop to work and you’d have to recompile with a new compiler (if that doesn’t work, code changes need to be implemented), but in most cases, you don’t have to change a thing, except download the new source for the driver and build it again.
It usually works for about a year or two, then you have to rebuild, so it’s not that big of an issue.
Why not just take that module, build it yourself, add the firmware package as well, repackage it and install it on whatever distro you like. I know, it sounds like a lot of work, but you only have to do it once… or maybe twice, depending on what is removed/added in future kernels.
I tried a slew of distros - some recognize the modem, but nothing more, most don’t even see/interact with it. It took hours of combing through outdated forums, mailing lists, wiki, etc to find commands that would not only see the modem, but unlock it and connect successfully. This was found on the Debian unstable wiki, and the system would install but fail to boot on stable, so I have no idea if the instructions work for Debian. Kubuntu however, boots successfully on that machine (a ThinkPad) and the modem “works” (is seen) ootb and can be unlocked + used successfully with the rest of the commands in that wiki page.
The fact that I tried nearly a dozen distros, and I tinkerer with it for a literal month, I’m not touching shit. I didn’t want to go Ubuntu for this machine, but cell connectivity (and hotspot hosting) is a 100% requirement, so I’m using what works.
I’m a moderate nix user but fuck packaging my own drivers and figuring out what software packages are needed to enable the modem. 20 years ago, sure. Now, fuck no, it should “just work”. PTSD from wifi not working, requiring windows drivers in a wrapper, etc. I’m not diving into that again, nope nope nope.
Lol 😂, yeah, I can understand that. You just want things to work, totally understandable.
Agreed. I can understand things not just working 20 years ago, but in this day and age, yes, they should just work.
I think money is the main issue… for most of the devs working on Linux, this is a fun side project, not an actual job. So, they dedicate spare time to this, nothing more. It’s the sad truth I’m afraid.
Because who wants to do this every time they upgrade kernels, let alone once?
You don’t have to make it a part of the kernel, it could be an external module, like the firmware. I’ve done it before, it’s not as scary at it sounds. Yes, at a certain point, it will stop to work and you’d have to recompile with a new compiler (if that doesn’t work, code changes need to be implemented), but in most cases, you don’t have to change a thing, except download the new source for the driver and build it again.
It usually works for about a year or two, then you have to rebuild, so it’s not that big of an issue.
Ain’t nobody got time for that!