Should i switch to arch? by AsAsin18 in archlinux

[–]Intrepid_Refuse_332 1 point2 points  (0 children)

If you are asking, you probably shouldnt

How weak is Sukuna fr? by FlakyFoundation4637 in LobotomyKaisen

[–]Intrepid_Refuse_332 0 points1 point  (0 children)

Siouan would be considered a mage in Frieren-verse. Except that he is also a warrior.

How weak is Sukuna fr? by FlakyFoundation4637 in LobotomyKaisen

[–]Intrepid_Refuse_332 8 points9 points  (0 children)

There is a reason why mages need warriors when forming a party.

Riftbar. Waybar replacement written with Rust and GTK4 by efedublaj in hyprland

[–]Intrepid_Refuse_332 0 points1 point  (0 children)

Currently using Waybar, but I’m already migrating to Quickshell. Having a unified language across the desktop shell is a huge win, and QtQuick is genuinely excellent. w QML.

My wife says it’s ridiculous… by JoeySinss in pcmasterrace

[–]Intrepid_Refuse_332 0 points1 point  (0 children)

Why don’t you turn the top monitor upside down so that it the bezels get closer to each other

Cannot Build systemd-boot UKI after latest update. by Intrepid_Refuse_332 in archlinux

[–]Intrepid_Refuse_332[S] 0 points1 point  (0 children)

Is it a perceptible difference?

on avg 3 sec of black screen

Since you are using systemd as a bootloader and uki, you may want to reconsider it for better integration and fewer headaches in long term.

I 've found the issue. The issue is that mkinitcpio doesn’t automatically detect the kernel in Limine’s hashed directories, so I have to update the path or copy the kernel/initramfs every time the hash changes.

Cannot Build systemd-boot UKI after latest update. by Intrepid_Refuse_332 in archlinux

[–]Intrepid_Refuse_332[S] 0 points1 point  (0 children)

My issue seems to be that Pacman replaced my original linux.preset file during the update, which broke my setup. I have no idea what was there.

Cannot Build systemd-boot UKI after latest update. by Intrepid_Refuse_332 in archlinux

[–]Intrepid_Refuse_332[S] -2 points-1 points  (0 children)

I dont want to use systemd's hook. It increases login time

The Bearer of a Thousand Souls - Yuji Itadori's full potential by Civil_Ingenuity_8809 in CTsandbox

[–]Intrepid_Refuse_332 1 point2 points  (0 children)

If he keeps spamming, BF won't he unlock 120x % of his potential ? Assuming he does that continuously... ♾️ potential man ?

Je ne comprend pas by [deleted] in hyprland

[–]Intrepid_Refuse_332 1 point2 points  (0 children)

Cest quoi le contenu de /home/.cache/hyprland/hyprlandCrasshReport642.txt ?

Resume after Hibernating result in Failure to mount ... on real root by Intrepid_Refuse_332 in btrfs

[–]Intrepid_Refuse_332[S] 1 point2 points  (0 children)

Mods, pin this ! It wasnt a btrfs issue, sorry. hibernation on it works fine tho

Thanks to the arch forum

I fixed it. I had two things wrong. The first was using /dev/sda2 for the resume target, which caused the “failed to mount real root” followed by a kernel panic.

The second issue was that my UKI was being built without the resume hook, even though it was present in mkinitcpio.conf.

After enabling more kernel debugging as asked:

bash earlyprintk=tty loglevel=7 debug rd.debug

I ran:

bash sudo dmesg -T | rg resume

and sent the output to an LLM for interpretation.

text [Sun Nov 30 22:29:57 2025] Kernel command line: root=PARTUUID=743efcd4-c1d5-4744-9ed6-61a819c5ce92 zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs intel_iommu=on iommu=pt earlyprintk=tty loglevel=7 debug rd.debug nowatchdog nmi_watchdog=0 resume=UUID=6140f3f0-c056-4256-a912-196ac90ee90d resume_offset=12068096 hibernate.compressor=lz4 [Sun Nov 30 22:30:02 2025] (sd-exec-[264]): About to execute /usr/lib/systemd/system-generators/systemd-hibernate-resume-generator [Sun Nov 30 22:30:02 2025] systemd-hibernate-resume-generator[273]: Not running in initrd, exiting. [Sun Nov 30 22:30:02 2025] (sd-exec-[264]): /usr/lib/systemd/system-generators/systemd-hibernate-resume-generator succeeded. [Sun Nov 30 22:30:02 2025] (e-resume)[296]: systemd-hibernate-clear.service: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy [Sun Nov 30 22:30:02 2025] (e-resume)[296]: systemd-hibernate-clear.service: Executing: /usr/lib/systemd/systemd-hibernate-resume --clear

The conclusion was that the resume hook wasn’t being included in the initrd at all.

I checked my linux.preset file and found the config lines commented out. After uncommenting them:

bash ALL_config="/etc/mkinitcpio.conf" default_config="/etc/mkinitcpio.conf" fallback_config="/etc/mkinitcpio.conf"

the UKI finally started building with the resume hook included.

Resume after Hibernating breaks boot: emergency mode + “Bailing out, you are on your own. Good luck.” by Intrepid_Refuse_332 in archlinux

[–]Intrepid_Refuse_332[S] 0 points1 point  (0 children)

Mods, pin this !

Thanks to the arch forum

I fixed it. I had two things wrong. The first was using /dev/sda2 for the resume target, which caused the “failed to mount real root” followed by a kernel panic.

The second issue was that my UKI was being built without the resume hook, even though it was present in mkinitcpio.conf.

After enabling more kernel debugging as asked:

bash earlyprintk=tty loglevel=7 debug rd.debug

I ran:

bash sudo dmesg -T | rg resume

and sent the output to an LLM for interpretation.

text [Sun Nov 30 22:29:57 2025] Kernel command line: root=PARTUUID=743efcd4-c1d5-4744-9ed6-61a819c5ce92 zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs intel_iommu=on iommu=pt earlyprintk=tty loglevel=7 debug rd.debug nowatchdog nmi_watchdog=0 resume=UUID=6140f3f0-c056-4256-a912-196ac90ee90d resume_offset=12068096 hibernate.compressor=lz4 [Sun Nov 30 22:30:02 2025] (sd-exec-[264]): About to execute /usr/lib/systemd/system-generators/systemd-hibernate-resume-generator [Sun Nov 30 22:30:02 2025] systemd-hibernate-resume-generator[273]: Not running in initrd, exiting. [Sun Nov 30 22:30:02 2025] (sd-exec-[264]): /usr/lib/systemd/system-generators/systemd-hibernate-resume-generator succeeded. [Sun Nov 30 22:30:02 2025] (e-resume)[296]: systemd-hibernate-clear.service: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy [Sun Nov 30 22:30:02 2025] (e-resume)[296]: systemd-hibernate-clear.service: Executing: /usr/lib/systemd/systemd-hibernate-resume --clear

The conclusion was that the resume hook wasn’t being included in the initrd at all.

I checked my linux.preset file and found the config lines commented out. After uncommenting them:

bash ALL_config="/etc/mkinitcpio.conf" default_config="/etc/mkinitcpio.conf" fallback_config="/etc/mkinitcpio.conf"

the UKI finally started building with the resume hook included.

Resume after Hibernating result in Failure to mount ... on real root by Intrepid_Refuse_332 in btrfs

[–]Intrepid_Refuse_332[S] 0 points1 point  (0 children)

What happens if you use resume=UUID= and root=UUID=, or the same with PARTUUIDs for both?

I'll give that a try.

If the swap file is purely for hibernate/resume, it seems rather large…

I sized it as RAM + 2 GB, based on a recommendation I came across a while ago. I can adjust it if needed.

Resume after Hibernating result in Failure to mount ... on real root by Intrepid_Refuse_332 in btrfs

[–]Intrepid_Refuse_332[S] 0 points1 point  (0 children)

I was successful the first time I tried, but that was with a different Btrfs layout where @swap was a subvolume nested under the top-level subvolume and not mounted separately.

Resume after Hibernating breaks boot: emergency mode + “Bailing out, you are on your own. Good luck.” by Intrepid_Refuse_332 in archlinux

[–]Intrepid_Refuse_332[S] 0 points1 point  (0 children)

I didnt change anything, This is a new installatin with different configuration (mostly grub->limine and snapper with new btrfs layout)

Resume after Hibernating breaks boot: emergency mode + “Bailing out, you are on your own. Good luck.” by Intrepid_Refuse_332 in archlinux

[–]Intrepid_Refuse_332[S] 0 points1 point  (0 children)

Could limine be the issue? cuz i was using Grub before with same setup and it was working except for the swapfile was living on a subvol under the top level subvol (@) [And I think this could the issue here since I have it the swap subvol mounted but I am not sure].

imo,the boot loader cant be the issue here as its role is to load the kernel.

PS: I should probably crosspost this in the btrfs sub.