I cleaned up my packages and now the kernel creation spams tons of possibly missing firmware warnings.

==> WARNING: Possibly missing firmware for module: 'radeon' ==> WARNING: Possibly missing firmware for module: 'nouveau' ==> WARNING: Possibly missing firmware for module: 'i915' ==> WARNING: Possibly missing firmware for module: 'amdgpu' ==> WARNING: Possibly missing firmware for module: 'xe' ==> WARNING: Possibly missing firmware for module: 'ast' ==> WARNING: Possibly missing firmware for module: 'xhci_pci_renesas' ==> WARNING: Possibly missing firmware for module: 'bfa' ==> WARNING: Possibly missing firmware for module: 'aic94xx' ==> WARNING: Possibly missing firmware for module: 'cxgb3' ==> WARNING: Possibly missing firmware for module: 'cxgb4' ==> WARNING: Possibly missing firmware for module: 'qed' ==> WARNING: Possibly missing firmware for module: 'qla2xxx' ==> WARNING: Possibly missing firmware for module: 'isci' ==> WARNING: Possibly missing firmware for module: 'qla1280' ==> WARNING: Possibly missing firmware for module: 'advansys' ==> WARNING: Possibly missing firmware for module: 'wd719x' ==> WARNING: Possibly missing firmware for module: 'csiostor' ==> WARNING: Possibly missing firmware for module: 'ums_eneub6250' ==> WARNING: Possibly missing firmware for module: 'cs42l43'

None of the firmware is needed, my system operates as expected, and everything works … Oh well 🙄 … Time to create some dummy modules, I guess.

#ArchLinux #pacman #mkinitcpio #JustLinuxThings

Having issues?

#ArchLinux with #LVM on #LUKS and #systemd boot on the new #mkinitcpio 40-2 version?

Basically:
echo "title Arch Linux
linux /vmlinuz-linux-hardened
initrd /initramfs-linux-hardened.img
options rd.luks.name=$(blkid -s UUID -o value /dev/sda2)=root root=/dev/vg0/root rw" >> /boot/loader/entries/arch.conf

/etc/mkinitcpio.conf
HOOKS=(base systemd autodetect microcode modconf kms keyboard keymap sd-vconsole sd-encrypt block filesystems fsck lvm2)

https://wiki.digitalprivacy.diy/en/server/operating_systems/arch_linux#create_an_initial_ramdisk

Deux nouveaux hooks pour #mkinitcpio sur #ArchLinux, suite à la MAJ faite cette nuit : [systemd] et [sd-vconsole]

Conséquence liée ? À l’allumage, ce matin, entre les écrans “Chargement de Linux…” et celui d’ouverture de session, toute la phase de démarrage de systemd se fait… en écran noir complet, à l’aveugle (il n’y a plus la ligne “/dev/sda…”, ni de simple curseur texte “_” gris) ! C’est perturbant, ce changement non sollicité… >__<

mkinitcpio v40, packaging changes and kernel-install - Arch-dev-public - lists.archlinux.org

If you have lots of RAM available, but need to save some space on /boot with Arch Linux   when using mkinitcpio (default initramfs setup): Set MODULES_DECOMPRESS in your mkinitcpio.conf to yes.

The default zstd compression will ensure the initramfs image on /boot to be smaller than if this option were not enabled, but RAM usage may be higher when booting.

#ArchLinux  #initramfs #mkinitcpio

🚀 How to Update GRUB and Regenerate Initramfs from a Manjaro Live USB System 🐧

Sometimes things break—it’s Linux life! 💻 Maybe your Manjaro installation isn’t booting correctly after an update or some system tweaks. Don’t panic! You can easily fix boot-related issues using your Manjaro Live USB stick.

Here’s how you can update your GRUB bootloader and regenerate your initramfs directly from a Manjaro Live USB. Let’s dive in! 🌊

🔧 Step 1: Boot into the Manjaro Live USB & Mount your System

Boot your computer with a Manjaro USB stick. Open a terminal and identify your root partition using:

sudo fdisk -l

Let’s say your root partition is /dev/sda2, then mount it:

sudo mount /dev/sda2 /mnt

If you have separate boot or EFI partitions, mount them too:

  • For a separate /boot partition:
sudo mount /dev/sda1 /mnt/boot
  • For an EFI partition:
sudo mount /dev/sdaX /mnt/boot/efi

(Replace /dev/sdaX with your actual EFI partition.)

🛠️ Step 2: Enter your Installed System with manjaro-chroot

Manjaro makes this super easy:

sudo manjaro-chroot /mnt

Now you’re working inside your actual system environment! 🚪

⚙️ Step 3: Update GRUB Bootloader

Run these commands based on your boot type:

  • For BIOS/Legacy boot:
grub-install /dev/sdaupdate-grub
  • For EFI boot:
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheckupdate-grub

🔄 Step 4: Regenerate your Initramfs

Now regenerate initramfs images:

mkinitcpio -P

🎉 Step 5: Finish & Restart!

Exit the chroot environment:

exit

Unmount your partitions:

sudo umount -R /mnt

And reboot your system:

sudo reboot

That’s it! 🎯 Your Manjaro system should now boot up smoothly.

🔗 Useful Resources:

👉 Check out my original conversation with ChatGPT here for more details.

Happy Linux adventures! 🐧✨

#ArchLinux #BIOS #Bootloader #chroot #EFI #GRUB #initramfs #Linux #LinuxCommands #LinuxTutorial #LiveUSB #Manjaro #mkinitcpio #SystemRecovery #Terminal #Troubleshooting

Can anyone explain the advantages of using #dracut over #mkinitcpio on #arch #linux ? Assuming there are any of course

#DailyStandup (2/2)

Not something I did, but something that happened:
- Friday's #mkinitcpio v39 release means that my #ARM improvements are now in a stable release. #ArchLinuxARM should no longer have to patch mkinitcpio!

What I'm doing today:
- Following up with the gotk4 prep PR
- Working through some of the #Parabola packaging backlog.
- Working through some of the Parabola email mailinglist backlog

Challenges/blockers:
- Waiting for @amerl to email me some files I'd saved on his laptop

v39 · Arch Linux / Mkinitcpio / mkinitcpio · GitLab

CHANGES WITH v39: Announcement of future breaking changes:

GitLab
v39 · Arch Linux / Mkinitcpio / mkinitcpio · GitLab

CHANGES WITH v39: Announcement of future breaking changes:

GitLab