Five seconds to pick Fedora or Windows is four seconds too few. Here’s how to give GRUB more time, and – the trick I set up on my Z840 years ago and never wrote down – how to make it boot whatever you chose last time. Two lines, one twist: Fedora already has half of it.
Bluetooth vanished from my Z8 workstation while WiFi on the same card kept working. Instead of shrugging and reaching for wired headphones, I read the crime scene with PowerShell — and learnt that Windows has a dmesg after all. Nobody just tells you where to look.
The famous Mac startup chime lives in firmware, not macOS — which is why it survives a Fedora install. Here’s how to silence it from Linux by writing a single byte to NVRAM, and why 64 means half volume but 128 means silence.
When my 2011 MacBook Air started crashing its entire desktop every time a new app launched, the obvious suspect was the app. Three wrong theories later, journalctl, coredumpctl and one stack trace led to a confirmed upstream Mesa bug — and a one-line workaround. A practical tour of Linux crash forensics: the tools, the reading skills, and the discipline of letting evidence outrank a good story.
A dead battery held an old Chromebook hostage, a $14 replacement brought it back — and now runs the machine for hours while insisting it doesn’t exist. A tale of brownout loops, battery part numbers, deep-sleep protection, and learning to love a mute fuel gauge.
Google declared this 2017 education Chromebook e-waste. The C128 test disagreed. A full walkthrough of the MrChromebox UEFI conversion and Fedora 44 KDE install — enterprise enrollment checks, the write-protect screw hunt, and the surprises waiting in System Settings.
An always-on home server doesn’t have to be always on. With rtcwake and a systemd timer, my old Samsung Q330 now sleeps fourteen hours a day and wakes itself up on schedule – using hardware that’s been on every motherboard for decades.
A PowerShell script that ran fine 30 minutes ago suddenly “cannot be loaded because running scripts is disabled”? You probably didn’t change anything — you changed terminals. VS Code has two nearly identical PowerShell consoles, and only one of them obeys the execution policy.
