Someone please clarify for me: is this my own doing, once again, or is something TOTALLY AMISS WITH the update functionality in Garuda Linux? Last time this happened, it turned out to be my own damned fault, and I know, I know, I read plenty of times to not install stuff -- especially system-level stuff, from the AUR. Yet I thought it would be cool to add some kernel dkms modules from the AUR, which then BUSTED my dkms and royally left me with an unbootable system on reboot.
No surprises to discover a ROYAL F*CK-UP that would leave me without a bootable machine this time around, 'cause I have been here far too many times already than to have any confidence in the dependability of the distro. I now make sure to read the output of the update with a magnifying glass and a fine-toothed comb and always hold my breath when I reboot -- something I try to avoid as much as possible... Don't get me wrong: I love Garuda and I like a painful operating system experience just as much as the next nerd in so much as it provides to me the opportunity to delve deeper in my Linux know-how and kung-fu.
Yet I am also a musician, and use my machine for the production of music. At this point, I want to run back SCREAMING ALL THE WAY to the welcoming, faithful, loyal, dependable and loving arms of a BSD operating system so
fscking hard that I can already hear the violins playing in my head... I ALWAYS DID LOVE YOU, BSD!!! ...yet if only you had more modern driver support for hardware, more software development on the platform (like music production software) we might NEVER HAVE EVER, EVER, EVER PARTED NOR EVER WOULD... Instead, I became a cheater and had to betray you, BSD, for music production's sake and just being able to run something not Microsoft on my 'puter with the Realtek 8188ce wireless network interface and AMD audio chipset still as yet unsupported in BSD territory... Martin Luther King had a world-impacting dream. I also dream, albeit not so majestically or grandiose: I dream a much smaller dream of running Bitwig Studio natively on a BSD and helping to give to the world the first-ever, bonafide, workable, easy, and very capable system of microtonality in modern music production. Maybe some day...
I digress. What broke in the update: kernel updated to 6.0 yet the mkinitcpio portion of pacman's duties failed horrifically with this error:
call to execv failed (No such file or directory)
I then read the manpage on mkinitcpio and deduce that I need to call it thusly, manually:
mkinitcpio -v -k 6.0.2-zen1-1-zen -g /tmp/vmlinux-6.0.2-zen1-1-zen
I did my homework, found a forum post where '-P' is used. Yet this proves useless and makes the command fail due to no presets in /etc/mkinitcpio.d/. So I deduce there must have been a preset and wonder what in the update process might have erased it??? Sure enough, I untar a backup of /etc and find the linux-zen.preset.
But before I F*CK up the already broken system even more than garuda-update did, I opened the /etc/mkinitcpio.conf file, and discovered a garuda-update shortcoming: /etc/mkinitcpio.conf.pacnew. Worse, the .pacnew has no useable values for my system. So I manually fix the .conf file, adding the new directives from the .pacnew, and specify uncompressed and set COMPRESSION=cat as per the manpage. Mkinitcpio reports a successful generation. I would like some confirmation:
From reading the /boot/grub/grub.cfg I deduce that the output of mkinitcpio must be /boot/vmlinuz-linux-zen. Can I 'cp /tmp/vmlinux-6.0.2-zen1-1-zen /boot/vmlinuz-linux-zen' and then do a 'grub-install' and hope to be able to reboot without tears, or do I need to write another love letter to BSD? Anyone but Bob, feel free to answer correctly the question... I know that this might work for the 6.0 kernel.
I offer my help to give garuda-update a serious kick in the pants and update. Yet what might have possibly
fscked up the mkinitcpio, and deleted the linux-zen.preset? The ONLY thing I can think of is my having added that cachyos repo per the instructions in this forum. If cachyos repo turns out to be the culprit, then PLEASE REMOVE THAT F**KING POST IN THE FORUMS AND ALERT OTHER GARUDERS TO THE PROBLEM AND OFFER KUNG-FU FIXES... I WILL HELP!