About 90% of what I know about ssh, terminal multiplexing, scripting, and diagnostic programs grew from an optimization project.
I had a vague desire to build a one-stop dashboard where I could monitor, update, and control a half-dozen linux computers at once. It was just for fun, but it kept me reading through the manpages for weeks.
I didn’t, but only because my solution wasn’t novel or generalized for other people. I made a script to fire up tmux on a ‘primary’ computer with key-based access to my other computers, load up a set of windows and panes, and ssh into each computer. One window would be computers in one section of my home, another window would be computers elsewhere. The only challenge was getting a baseline grasp of the tmux scripting syntax.
I initially set it up to run htop on each computer (dashboard goal, plus easy ability to terminate programs), but the basic setup was flexible. I could set other programs to run by default or and send terminal command updates to each computer from any device that could ssh into the primary computer. Automating updates on a computer-by-computer basis is a better solution, but the setup let me quickly oversee and interactively start multiple system updates at once, from a phone, tablet, or laptop.
Maybe the mods can restrict it to, like…Windows Wednesday or something.
One day a week, everyone can post about leaving Windows, why Windows sucks, why Windows is gonna fail in 2024, maybe post a picture of their monitor saying “Now Uninstalling Windows,” all the good shit we’ve seen a hundred times by now.
Then, we can all get the hell on with our lives until next week.
I am sorry if my post made you feel bored. But please don’t unsubscribe. What kind of post do you want to see on this platform? I am sure people can reach a common ground my mutual discussion.
Contrary to what some have said here, it’s not unusual to have to download and manually install the wifi driver for Mint. It’s even mentioned as the one extra step in a cartoon comparing the time it takes to install three different distros. I had to do this for two different laptops.
OmanMkII already provided the link for intel, but here it is again:
Did you use the Debian edition of Mint? Debian doesn’t include a lot of proprietary drivers and/or firmware blobs with its standard edition.
I can’t say that’s the case here, but it’s possible that Mint is either using Debian as a base, or at least following the Debian Free Software Guidelines.
There’s usually a nonfree firmware deb you can use, post installation. If you can complete the install and connect to the internet via the 7480’s Ethernet port, you should be able to get the wifi card working.
Hardware related stuff like this typically comes down to the kernel version, or what kernel modules the distro ships. The linux kernel comes with a ton a drivers for different hardware, each of which implement support for hundreds/thousands of pieces of hardware. The wi-fi driver shipped with Mint isn’t new enough to include an implementation for your specific wi-fi hardware.
Mint seems to be on an LTS 5.X kernel, while Pop is shipping newer 6.X kernels (makes sense, as they like to keep up with gaming-related improvements).
As an example, I had to jump to a newer version on Manjaro, when the LTS kernel used by default was just one digit behind the version that was new enough to have support for the PS DualSense5 controller.
Hopping to a newer kernel version can be tricky depending on the distro, but it looks like Mint has a tool for this. You can find it in the Update Manager: View --> Linux Kernels. There you should be able to switch to running a 6.X kernel version.
Drivers is a vocabulary you should almost forgot in Linux ;) Contrary to other OS, Linux will rarely require you to install a driver.
To answer your question, doing a simple online “mint wireless 8275” returned a forum with your exact issue. The reported solution is to “try powering it off, remove the power cord and hold the power button for 30 seconds. Reconnect cord and power up”. As weird as it sounds this may work. It worked for me 10 years ago with a keyboard. It’s easy and quick to try it. Let us know if that helps or not. Too bad you didn’t like Arch because your laptop was fully supported.
Unless you are suggesting they find a way to remove the battery, “removing the power cord and turning it on without actually turning it on” isn’t something they can try.
And the fact that WiFi works on another distro suggests this isn’t a weird bug-state that the card needs to be snapped out of with power-cycling tricks.
OP has solved his issue already but the trick I mentioned could be due to a capacitor issue which can occur anytime and break things that worked before.
I was just trying to help by suggesting an approach that solved the exact same issue on others’ laptop running the same distro. Even though not convenient you can either wait for your battery to run out or disconnect it to try this trick.
That trick screams “residual power in a capacitor that we need to drain to get a proper restart on some component”
I’ve heard of that working with some motherboards where it seemed they were dead and may explain those boards that don’t work but magically do months later when the capacitors had time to completely discard the small trickle of current they still had.
Thanks, yeah I’ve found a few articles already on running scripts at shutdown…something like this should do it (using Tony Walker’s update script), though I’ve not tested it yet:
That’s the beauty of Linux! If you feel adventurous, you always easily find something to tweak/experiment. Since I moved to Linux my mindset and workflow never ceased to evolve. That’s because I’m curious but that couldn’t be possible in any other OS. Only Linux can offer so much options and an exceptional level of granularity so anyone can build his/herown perfect system. We may achieve the same thing but in different ways and we’ll both run Linux.
If you’re more shy you can simply install a set of software under a given distro and you’re done. This is also a Linux option. Right now, I couldn’t find any challenges to keep me busy for more than a day or two until I decided to test a new system (NixOS) in a virtual machine. This is another way to have the kind of fun you mention :)
I love tweaking and improving my system so much that I dedicated my little blog only to that. Sharing is another crucial principles I love in the Linux philosophy.
I tried Arch in a VM about when Archinstall came out. And after the first install, I did it again with archinstall | lolcat. The configuration part was a little buggy, but let me tell you; it was worth it.
I use uBlue and update manually (using a custom alias/script) whenever I get the time, like say during my lunch break or something. Reason being, I actually like watching the update process and seeing what gets updated, watching out for major version number changes or major package upgrades, and if I’m interested I may look up some of their changelogs to find out about their new features etc.
and being forced to reboot
You should be forced to reboot though? And if you don’t want to reboot, can’t you just do an –apply-live? I mean you’d still need to reboot for a kernel update but for the most part, you should be able to use most of your new packages without a reboot. And this holds true even more so if you’re updating Flatpak/container/Nix/pip/cargo/brew packages. And I hope you’re not doing the rookie mistake of actually installing stuff at the ostree layer instead of using Flatpaks/containers/Nix etc.
I too like to review changes between images, but I’m just as content to run rpm-ostree status and/or rpm-ostree db diff to see what exactly has changed.
You should be forced to reboot though? And if you don’t want to reboot, can’t you just do an --apply-live?
I’m hoping to eliminate the extra reboot each day that is usually necessary to activate the latest image. I know that a lot of this will depend on exactly when the image drops from the repos (versus when I shutdown a host), which is why I was looking for some general feedback from others who might have done the same thing…I didn’t know if it’d be worthwhile in the long run, but I guess there’s only one way to find out. As for the –apply-live, I use it on occasion but I don’t want to rely on it for system updates (if that’s even possible).
As for the –apply-live, I use it on occasion but I don’t want to rely on it for system updates (if that’s even possible).
As I said before, it does work for system updates, the only exception being the kernel. The –apply-live flag was added for that exact reason, to avoid the need for an unnecessary reboot.
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.