Kernel Update error on omarchy leading to emergency mode after reboot

[sage atlas]

I am having trouble setting up omarchy again i am getting into emergency mode after updating by sudo pacman -Syu and even by omarchy update and i found this a kernel problem if you can help please or else i cant use my omarchy

[eternal hollow]

what machine is this?

the issue has been talked about if you search for "cpu features" or similar keywords, here in this discord

sudo pacman -Rns limine-mkinitcpio-hook && yay -S aur/limine-mkinitcpio-hook

[vital dune]

Ur cpu too old but can be fixed just like foghorn mentioned

[sage atlas]

is my hardware not supported anymore?

[eternal hollow]

it may work but, there is an easy yay solution

[sage atlas]

what it is?

[eternal hollow]

try

sudo pacman -Rns limine-snapper-sync && yay -S aur/limine-snapper-sync

OR

sudo pacman -Rns limine-mkinitcpio-hook && yay -S aur/limine-mkinitcpio-hook

do only one to help identify the bug

then try omarchy-update

also, copy text of the FLAGS of lscpu
lscpu | grep Flags | wl-copy
paste here

[hearty totem]

Hi, I'm having a really annoying error when trying to install Omarchy with the installation script. Many dependencies are more up-to-date on Arch than in the Omarchy repository. I've already tried rollback, However, when running the script again, the error returns.

Could someone help me?

[eternal hollow]

unrelated to thread , use search

[sage atlas]

nothing print by this command

[eternal hollow]

its in your clipboard

[sage atlas]

is this what you want

Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave avx f16c lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp fsgsbase smep erms xsaveopt dtherm arat pln pts md_clear flush_l1d

[eternal hollow]

wooooooo

that may help a dev to fix the issue

sudo pacman -Rns limine-mkinitcpio-hook && yay -S aur/limine-mkinitcpio-hook

[sage atlas]

~ ❯ sudo pacman -Rns limine-mkinitcpio-hook && yay -S aur/limine-mkinitcpio-hook
[sudo] password for atif:
error: target not found: limine-mkinitcpio-hook

[eternal hollow]

hmm
try one then the other instead of &&

[sage atlas]

is this installed correctly

[eternal hollow]

now try sudo limine-update

[sage atlas]

~ ❯ sudo limine-update
[sudo] password for atif:
Limine EFI update completed successfully.
Building UKI for linux (6.18.7-arch1-1)
==> Starting build: '6.18.7-arch1-1'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [microcode]
-> Running build hook: [modconf]
-> Running build hook: [kms]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
-> Running build hook: [block]
-> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: 'qat_6xxx'
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Creating unified kernel image: '/tmp/staging_uki.efi'
==> Unified kernel image generation successful
UKI stored in /boot/EFI/Linux/omarchy_linux.efi
Updated: /boot/limine.conf

[eternal hollow]

your in biz

omarchy-update

[sage atlas]

it says reboot should I or something else left @eternal hollow

[eternal hollow]

sounds good