this post was submitted on 27 Sep 2024
618 points (98.3% liked)
linuxmemes
21615 readers
449 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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!
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.
A bit of ranting about this machine:
This is my first TP machine (X13 Gen 2, Intel) and while it is fine as a very-overpriced business unit (seriously, it should cost half the asking price - and then I paid for 5y of top tier warranty and support on top of that, as it's my first TP and I don't trust past praise to equal future quality), I was surprised, annoyed, to find that there is absolutely no Linux support for it. Like yeah, it shipped with win 10 pro, but several similar machines have at least Ubuntu and something else officially supported, can't remember off the top of my head. My suspicion is that it's due to the (lack) of cell modems in those units. I don't think Lenovo wants these units with, I guess 'potential liability', getting unlocked and used in non-Windows environments. That might be all bullshit but they sure as fuck aren't going to give an honest answer about it.
I went with the TP because it was offered through my cell carrier, so compatability was guaranteed, and because everyone is like 'woo ThinkPad!' but... it's fine, but it's not this steamrolling, ass-kicking, blazing machine and experience that I was foretold. Hell, the battery has had to be replaced just 6 months into ownership, it would last 30 minutes full to empty with mere web browsing. The replacement, now a year later, is reporting like 88% life. I use this machine suuuuper lightly, as a glorified hotspot and web browser when I'm away at conventions and stuff. If they've cheaper out brutally hard on something as obvious as the battery, what else have they cheapest out on?
Anyway lol. Just venting.