Kernel

Earlier today while performing the update on my Fedora desktop, I encountered an issue with the new kernel update. As a result, the initramfs was not generated for the new installed kernel. So, I’ll share with you how to rebuild or generate the initramfs while fixing real issue on my Fedora workstation. First, here is an output showing the source of the issue. It might not be clear of what’s going on, but that’s okay as it’s not the main focus of this blog post. ...

I have a Void linux VM which only gets turned on once in every month. Today, when I booted up and updated the packages on this VM, I noticed that there are many old kernels installed. As a seasonal Void user, I had no clue on how to remove older kernels. Fortunately, a quick Google search pointed me to a video: VOID Linux: Removing old kernels with vkpurge. Basically, Void comes with a pre-installed utility program called vkpurge. (man vkpurge for more info.) ...

Just a few a days ago, I wrote a blog post about Pairing Bluetooth Mouse on Command Line on a Fedora laptop. So why do I need to write another post about doing the same thing on Gentoo? Well, as it turned out, I need a bit more than just turning on the bluetooth service and pairing the mouse. My Gentoo’s installation is very minimal, and I think this gives me an excuse to document on how I’d solve or get this working on Gentoo. ...

I’m still running Fedora 31 on my main desktop though Fedora 32 beta has been out for a while. The only reason that stops me from jumping to F32 now is because ZFS 0.8.3 is not compatible with the kernel 5.6.* on F32. Rumor has it, ZFS 0.8.4 will support kernel 5.6. Tonight, while doing the system update with sudo dnf update -y on F31 desktop, I noticed that the kernel for F31 is now kernel-5.6.6-200.fc31.x86_64. Wait, what? I didn’t interrupt the update process, and let it run till finish. ...

My Gentoo based Linux laptop which is still running the older kernel 5.3.15. A short while back, I had a failed attempt to upgrade the kernel to 5.4.2 as the disk which encrypted with dm-crypt couldn’t be decrypted on boot. Since the older kernel 5.3.15 was working fine and free time was I what I lacked of, it seemed logical to just not doing anything about it. Today while updating all the packages on my Gentoo laptop, I notice there was a newer kernel available: 5.6.3. So let’s try to install this newest kernel again and see if the issue with Luks/dm-crypt still persists. ...