I’m already locked up in apt hell.
I was sentenced to 0.10 minor kernel versions before I get out.
I still have to click separately at login to load wayland-mode in kde version 5.pre-enlightenment - like a massive kloser.
Otherwise I’m stuck with a pretty much indistinguishably different user experience.
As a Debian user (for two servers) and a Kubuntu user (because literally nothing else that ships with KDE supports my machine’s 5G modem), I’m sorry but I’m going to have to kill you. Nothing personal, you see, but we’ve had a vote and well, it was quite strongly in favor for your demise due to the statements you’ve made.
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.
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.
Debian is a joke, it is so far out of date it is unusable for anything except cave-painting or maybe a stone circle.
Ubuntu is way better.
Low effort bait
I could have you arrested for that comment.
I’m already locked up in apt hell. I was sentenced to 0.10 minor kernel versions before I get out.
I still have to click separately at login to load wayland-mode in kde version 5.pre-enlightenment - like a massive kloser. Otherwise I’m stuck with a pretty much indistinguishably different user experience.
I really can’t decide if this is serious or a joke
deleted by creator
That’s why noe one likes your jokes.
As a Debian user (for two servers) and a Kubuntu user (because literally nothing else that ships with KDE supports my machine’s 5G modem), I’m sorry but I’m going to have to kill you. Nothing personal, you see, but we’ve had a vote and well, it was quite strongly in favor for your demise due to the statements you’ve made.
Terribly sorry about this. bang
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.
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!