I’ve had issues like this (but with Bluetooth) resolved by unplugging the computer from the wall, and holding the power button for a few seconds to clear out the capacitors.
If it’s a laptop that’s a bit harder to do, but might be worth a consider.
I haven’t gone so far as to figure out why this fix works, but it’s happened a few times now and i can’t deny results
Byobu has more user-friendly interface and accessible features - but you can do the same things in tmux. I should probably have worded that better and supplied it as an alternative.
So I assume this is not old info and the thing shows up in lspci?
wifi seems to be a shell script coming from tlp, maybe you can do:
sh -x /usr/bin/wifi
to figure out why it thinks you have no wifi. This gives you a trace of the commands that wifi actually runs.
Also, wifi should be managed by NetworkManager so you could look into that documentation and log files for that. Also look at kernel logs like dmesg maybe.
Also also, this could be hardware problem of course. Maybe it just needs to be fully powered off to reset. Have you tried removing the battery? If you cannot do that, there might be little hole at the bottom of the laptop, to stick a paper clip into, to completely power cycle the machine. Maybe that’ll reset it.
I used awk to migrate users from one system to another. I created template scripts for setting up the user in the new system, I dumped the data from the old system, then used awk to process the dump and create scripts for each user in the new system. That was a fun project.
Everyday. I’ve got a lot of stuff that uses it. Granted most of it was mostly created a decade ago but with minimal maintenance it works great. The most helpful script is parsing megacli outputs so I can get a heads up on drive failures and rebuilds among other things.
A security module or a key fob/smart card processes the key internally using its own dedicated ram and cpu without any debugging support. This way, even something will full ram and cpu access or a compromise of your machine, there is no way to export or access the key. Data is passed to the module and it returns the scrambled or unscrambled result based on the key which no body knows or has ever seen. A key locked with no way to access can’t be hacked without physically stealing the module, which is where your pin comes in to save you. The TPM is a very important part of a secure boot chain. If you want to secure other things I wouldn’t blame you for using a separate module or fob that isn’t always connected util it’s actually needed and it should only be activated with a physical button or something so you have to be present to engage with it. This adds even more security. So you could use the TPM for boot chain security and a separate fob or data privacy for example.
My two cents; install uBlue’s Microsoft Surface Images. Here you can find the (WIP) documentation on how it differs from other uBlue images. I’m sure the following lines should pique your interest:
“Replaces the stock Fedora kernel with the Surface kernel
My personal take on what uBlue is, would be that it’s how Fedora would love to ship their Atomic variants if they could ship everything without worrying about those things they can’t (like hardware acceleration, codecs etc). Furthermore, uBlue even has device-specific images; which is just fantastic if you happen to own such a device.
Last, but definitely not least; it’s the best platform in which the transition to Ostree Native Container has been realized. As such, this allows some very unique ways to maintain a distro. For example; if something broke (for whatever reason) on vanilla Fedora Atomic, then… well, you (the uBlue-user) wouldn’t even have noticed it. Because that breakage simply never hit your device. Instead, uBlue’s maintainers noticed the issue -> somehow applied changes to the image so that the image doesn’t ship the issue (by either not shipping the breakage inducing update of the specific package or by shipping the workaround/fix with the image) -> the very next time you update your system (which happens automatically in the background by default) you just go on with your life as if nothing had happened in the first place 😅. So, in a sense, your system is managed such that breaking changes/updates don’t hit you; while they do hit non-uBlue users.
And I haven’t even touched upon how uBlue enhances tinkering or how it allows one to manage (a fleet of) self-customized images etc.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.