For those that don’t know about Void and kernels, Void offers many of them at any single period and updates them within 24hr of a new edition. The kernel pkg name for each edition stays the same, but the versions have an extended naming that is also used in making the bootable images. For example, let’s say you are following “linux4.19” and it is currently linux4.19.39-1. Then there might be 4.19.40-1, 4.19.40-2 and so on. If you use vkpurge to list the editions it will show you all except for the current. Let’s say you also follow linux4.14, linux4.20, and linux5.0. You may end up having to remove many kernel editions within a week. Continue reading
Bits and pieces, some underlined and emphasized, from an article by Lucian Armasu:
The NSA-designed Speck encryption algorithm will be removed from version 4.20 of the Linux kernel, after just recently being added to the Linux kernel version 4.17 in June. The move comes after the International Standards Organization (ISO) rejected two of NSA’s cryptographic designs, Simon and Speck, on the basis of not being trustworthy….. Continue reading
Maybe I Take Back What I Said About Dbus by FigOSdev
Despite what I’ve said about worrying about Bus1 (I’m not worried) I’m increasingly of the opinion that getting rid of Dbus or making it easier to remove is a good idea.
The idea is, you shouldn’t have too much software that is running or even installed when you don’t need it. That’s really simple; defining “too much” is not, but…
I have Dbus installed. I am quite capable of finding every file it installs, and removing that file. I can stop it from installing again– no problem!
There are things I have installed that depend on it– probably also not a problem. However, let’s look at what those are: Continue reading
My test machine is an aging, stock (unmodified), mass produced enterprise grade, machine made by Dell. Ever since my Manjaro days (Manjaro-OpenRC) when the first beta edition of Linux413 was released, it was the only kernel I have ever had problems with.* It always appeared to boot fine and only when X was about to start all input devices would freeze. Nothing in Xorg.0.log seemed to appear as an error. The machine would just lock up and only mechanically could it be rebooted. Continue reading
If you recently installed Artix and you run into any problems that may indicate hardware conflicts or inexistent configurations or have installed some other Kernel than the linux-lts which is the default, try this:
$ inxi -Fx This will give you information about your discovered hardware. $ sudo mkinitcpio -P
While it is building a new image from the kernel for booting up your system you may see a warning such as this one:
==> WARNING: Possibly missing firmware for module: somechipname-xxxx
Grub is and has been problematic for Manjaro. Everytime an other system in the same machine upgrades kernels or grub itself, it generates a /boot/grub/grub.cfg that is incompatible with Manjaro. Then Manjaro will not boot unless you have saved a stub of it menuentry from its own grub.cfg and patch it in the other systems. Then you can start Manjaro do a # sudo grub-install /dev/sd* and then # sudo update-grub to fix things.
You can uninstall grub from all other systems, but then what happens if Manjaro fails?
So, artix is just another system for Manjaro. Artix will create a boot grub entry that throws Manjaro into the known and familiar kernel panic, where you pull the plug and restart.
Someone at that “other forum” said it was about the intel-microcode that is included into the Manjaro kernel (which I didn’t know). No wonder you only find it in AUR! Because it is already within the system and this is why Manjaro’s graphics seem so good for anyone having intel only hardware.