System can't startup after update kernel using -Syu

Issues & Assistance
1

Please help! system can’t startup!

After updating in July using sudo pacman -Syu my system run into problem can’t boot up after loading initial ramdisk it goes blackscreen (the monitor itself goes off) and pressing any key wont help the screen to turn on, then i boot into lts kernel and it works, so i assume the problem must be inside the linux-cachyos and linux-cachyos-bore update. then i exclude the linux-cachyos-bore update and it works.

warning: linux-cachyos-bore: ignoring package upgrade (7.0.11-1 => 7.1.3-2)

is it safe to keep ignoring the update?
or is there anything i can fix with the startup issue?

below are my system info and config:

❯ jctl
Jul 20 19:17:58 veldabord kernel: No irq handler for 1.55
Jul 20 19:17:58 veldabord kernel: No irq handler for 2.55
Jul 20 19:17:58 veldabord kernel: No irq handler for 3.55
Jul 20 19:18:03 veldabord kernel: Bluetooth: hci0: No support for _PRR ACPI method
Jul 20 19:18:04 veldabord kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (20251212/dsopcode-13>
Jul 20 19:18:04 veldabord kernel: ACPI Error: Aborting method _SB.WMID.WQBC due to previous error (AE_AML_OPERAND_V>
Jul 20 19:18:04 veldabord kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (20251212/dsopcode-13>
Jul 20 19:18:04 veldabord kernel: ACPI Error: Aborting method _SB.WMID.WQBE due to previous error (AE_AML_OPERAND_V>
Jul 20 19:18:04 veldabord bluetoothd[623]: Failed to set mode: Failed (0x03)
Jul 20 19:21:13 veldabord plasmalogin-helper[921]: gkr-pam: unable to locate daemon control file
Jul 20 19:21:21 veldabord bluetoothd[623]: Failed to set mode: Failed (0x03)

~
❯ sudo cat /etc/mkinitcpio.conf
[sudo] password for veldabord:

vim:set ft=sh

MODULES

The following modules are loaded before any boot hooks are

run.  Advanced users may wish to specify all system modules

in this array.  For instance:

MODULES=(usbhid xhci_hcd)

MODULES=(crc32c)

BINARIES

This setting includes any additional binaries a given user may

wish into the CPIO image.  This is run last, so it may be used to

override the actual binaries included by a given hook

BINARIES are dependency parsed, so you may safely ignore libraries

BINARIES=()

FILES

This setting is similar to BINARIES above, however, files are added

as-is and are not parsed in any way.  This is useful for config files.

FILES=()

HOOKS

This is the most important setting in this file.  The HOOKS control the

modules and scripts added to the image, and what happens at boot time.

Order is important, and it is recommended that you do not change the

order in which HOOKS are added.  Run 'mkinitcpio -H ' for

help on a given hook.

'base' is required unless you know precisely what you are doing.

'udev' is required in order to automatically load modules

'filesystems' is required unless you specify your fs modules in MODULES

Examples:

This setup specifies all modules in the MODULES setting above.

No RAID, lvm2, or encrypted root is needed.

HOOKS=(base)



This setup will autodetect all modules for your system and should

work as a sane default

HOOKS=(base udev autodetect modconf block filesystems fsck)



This setup will generate a 'full' image which supports most systems.

No autodetection is done.

HOOKS=(base udev modconf block filesystems fsck)



This setup assembles a mdadm array with an encrypted root file system.

Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices.

HOOKS=(base udev modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck)



This setup loads an lvm2 volume group.

HOOKS=(base udev modconf block lvm2 filesystems fsck)



This will create a systemd based initramfs which loads an encrypted root filesystem.

HOOKS=(base systemd autodetect modconf kms keyboard sd-vconsole sd-encrypt block filesystems fsck)



NOTE: If you have /usr on a separate partition, you MUST include the

usr and fsck hooks.

HOOKS=(base udev autodetect microcode modconf kms plymouth block keyboard keymap filesystems)

COMPRESSION

Use this to compress the initramfs image. By default, zstd compression

is used for Linux ≥ 5.9 and gzip compression is used for Linux < 5.9.

Use 'cat' to create an uncompressed image.

#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

COMPRESSION_OPTIONS

Additional options for the compressor

#COMPRESSION_OPTIONS=()

MODULES_DECOMPRESS

Decompress loadable kernel modules and their firmware during initramfs

creation. Switch (yes/no).

Enable to allow further decreasing image size when using high compression

(e.g. xz -9e or zstd --long --ultra -22) at the expense of increased RAM usage

at early boot.

Note that any compressed files will be placed in the uncompressed early CPIO

to avoid double compression.

#MODULES_DECOMPRESS="no"

~
❯ sudo cat /etc/default/grub

GRUB boot loader configuration

GRUB_DEFAULT=0
GRUB_TIMEOUT='0'
GRUB_DISTRIBUTOR='CachyOS'
GRUB_CMDLINE_LINUX_DEFAULT='quiet splash loglevel=0 nowatchdog zswap.enabled=0 vt.global_cursor_default=0 rd.udev.log_level=0 systemd.show_status=false modprobe.blacklist=sp5100_tco initcall_blacklist=amd_pstate_init amd_pstate=disable'
GRUB_CMDLINE_LINUX=""

Preload both GPT and MBR modules so that they are not missed

GRUB_PRELOAD_MODULES="part_gpt part_msdos"

Uncomment to enable booting from LUKS encrypted devices

#GRUB_ENABLE_CRYPTODISK=y

Set to 'countdown' or 'hidden' to change timeout behavior,

press ESC key to display menu.

GRUB_TIMEOUT_STYLE=hidden

Uncomment to use basic console

GRUB_TERMINAL_INPUT=console

Uncomment to disable graphical terminal

#GRUB_TERMINAL_OUTPUT=console

The resolution used on graphical terminal

note that you can use only modes which your graphic card supports via VBE

you can see them in real GRUB with the command `videoinfo'

GRUB_GFXMODE=auto

Uncomment to allow the kernel use the same resolution used by grub

GRUB_GFXPAYLOAD_LINUX=keep

Uncomment if you want GRUB to pass to the Linux kernel the old parameter

format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"

#GRUB_DISABLE_LINUX_UUID=true

Uncomment to disable generation of recovery mode menu entries

GRUB_DISABLE_RECOVERY='true'

Uncomment and set to the desired menu colors.  Used by normal and wallpaper

modes only.  Entries specified as foreground/background.

#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"

Uncomment one of them for the gfx desired, a image background or a gfxtheme

#GRUB_BACKGROUND="/path/to/wallpaper"
GRUB_THEME='/usr/share/grub/themes/cachyos/theme.txt'

Uncomment to get a beep at GRUB start

#GRUB_INIT_TUNE="480 440 1"

Uncomment to make GRUB remember the last selection. This requires

setting 'GRUB_DEFAULT=saved' above.

#GRUB_SAVEDEFAULT=true

Uncomment to disable submenus in boot menu

GRUB_DISABLE_SUBMENU='false'

Probing for other operating systems is disabled for security reasons. Read

documentation on GRUB_DISABLE_OS_PROBER, if still want to enable this

functionality install os-prober and uncomment to detect and include other

operating systems.

#GRUB_DISABLE_OS_PROBER=false
GRUB_EARLY_INITRD_LINUX_STOCK=''
#GRUB_TOP_LEVEL='/boot/vmlinuz-linux-cachyos'
GRUB_TOP_LEVEL="/boot/vmlinuz-linux-cachyos-bore"

~
❯ sudo cat /etc/systemd/system.conf

This file is part of systemd.



systemd is free software; you can redistribute it and/or modify it under the

terms of the GNU Lesser General Public License as published by the Free

Software Foundation; either version 2.1 of the License, or (at your option)

any later version.



Entries in this file show the compile time defaults. Local configuration

should be created by either modifying this file (or a copy of it placed in

/etc/ if the original file is shipped in /usr/), or by creating "drop-ins" in

/etc/systemd/system.conf.d/ directory. The latter is generally recommended.

Defaults can be restored by simply deleting the main configuration file and

all drop-ins located in /etc/.



Use 'systemd-analyze cat-config systemd/system.conf' to display the full config.



See systemd-system.conf(5) for details.

[Manager]

LogLevecacheefaultLimitDATAcacheefaultLimitDATA=notice
#LogTarget=journal-or-kmsg
#LogColor=yes
#LogLocation=no
#LogTime=no
#DcacheefaultLimitDATAcacheefaultLimitDATAcachecacheDefaufaultLimitDATAcacheefaultLimitDATAmpCorcacheDefau=yes
SlogDefaultLimitRTPRIOowStatus=no
#CrashChangeVT=no
#CrashShell=no
#CralogDefaultLimitRTPRIOhAction=freeze
#CtrlAltDelBurstAction=reboot-force
#CPUAffinity=
#NUMAPolicy=default
#NUMAMask=
#RuntimeWatchdogSec=off
#RuntimeWatchdogPreSec=off
#RuntimeWatchdogPreGovernor=
#RebootWatchdogSec=10min
#KExecWatchdogSec=off
#WatchdogDevice=
#CapabilityBoundingSet=
#NoNewPrivileges=no
#ProtectSystem=auto
#SystemCallArchitectures=
#TimerSlackNSec=
#StatusUnitFormat=description
#DefaultTimerAccuracySec=1min
#DefaultStandardOutput=journal
#DefaultStandardError=inherit
#DefaultTimeouthomee5e-4df3-b151-4915ce9be9a9thomertShohomeec=90s
#DefaultTimehomehometStopSec=90s
#Dehomee5e-4df3-b151-4915ce9be9a9aultTimeoutAhomeortSec=
#DefaultDevhomeceTimeoutSec=90s
#DefaultRestartSec=100ms
#DefaultStartLimitInte@srve5e-4df3-b151-4915ce9be9a9valSec=10s
#DefaultStartLimsrve5e-4df3-b151-4915ce9be9a9tBurst=5srv#DefaultEnvironment=
#DsrvfaultIOAcc@cachedf3-b151-4915ce9be9a9unting=no
#DefaultIPAccountingsrvsrvno
#Defaultsrve5ecachedf3-b151-4915ce9be9a94df3-b151-4915ce9be9a9emoryAccsrvsrvcachenting=yes
#DefaultTsrvsksAccounting=yes
#DefaucacheefaultLimitDATAcacheefaultLimitDATAtcachedf3-b151-4915ce9be9a9asksMax=15%
#DefaultLimitCPU=
#DefaulcacheLimitFSIZE=
#cacheefaultLimitDATAcacheefaultLimitDATA=
#ReloadLimitIntervalSecloge5e-4df3-b151-4915ce9be9a9LimitMSGQUEUE=

#DefaultMemoryPressureWatch=
#DefaulogtSmackProcessLabel=1024:524288
#DefaultLimitRTTIME=
#DefaultMemoryPressureThresholdSec=
#DefaultMemoryPressureWatch=8M
#ReloadLimitBurstloge5e-4df3-b151-4915ce9be9a9
#DefaultSmackProcessLabel=
#DeflogultRestrictSUIDSGID=
#ReloadLimitBurstlogtLimitNICE=
logDefaultLimitRTPRIO=
#DefaultLimitRTTIME=
#DefaultMemoryPressureThresholdSec=200ms
#ReloadLimitBurst=auto
#ReloadLimitBurst=stop
#DefaultSmackProcessLabel=
#DefaultRestrictSUIDSGID=
#ReloadLimitIntervalSec=
#ReloadLimitBurst=

~
❯ cat /etc/fstab

/etc/fstab: static file system information.



Use 'blkid' to print the universally unique identifier for a device; this may

be used with UUID= as a more robust way to name devices that works even if

disks are added and removed. See fstab(5).





UUID=9C1A-41AC                            /boot/efi      vfat    defaults,umask=0077 0 2
UUID=3ae67e23-2e5e-4df3-b151-4915ce9be9a9 /              btrfs   subvol=/,defaults,noatime,compress=zstd,commit=12home 0 0
UUID=3ae67e23-homee5e-4df3-b151-4915ce9be9a9 /home      home   btrfs   subvol=/home,defaults,noatime,compress=zstd,commit=120 0 0
UUID=3ae67e23-2e5e-4df3-b151-4915ce9be9a9 /root          btrfs   subvol=/,defaults,noatime,compress=zstd,commi@srv=120 0 0
UUID=3ae67e23-@srve5e-4df3-b151-4915ce9be9a9 /srv   srv       btrfs   subvol=/srv,defaults,noatime,compress=zstd,commit=120 0 0
UUID=3ae67e23-2e5e-@cachedf3-b151-4915ce9be9a9 /varcachecache     btrfs   subvol=/cache,defaults,noatime,compress=zstd,commit=120 0 0
UUID=3ae67e23-2e5e-4df3-b151-4915ce9be9a9 /var/tmp       btrfs   subvol=/,defaults,noatime,compress=zstd,commit=120 0 0
UUID=3ae67e23-loge5e-4df3-b151-4915ce9be9a9 /var/log       btrfs   subvol=/log,defaults,noatime,compress=zstd,commit=120 0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

UUID=0A70CAD270CAC423 /mnt/data ntfs3 defaults,nofail,force,uid=1000,gid=1000,rw,user,exec,umask=000 0 0

UUID=b503de8f-2c72-4325-bec0-34f9c9925908 /infinity btrfs defaults,nofail,noatime,compress=zstd:3,autodefrag,nossd,space_cache=v2,discard=async 0 0

UUID=b503de8f-2c72-4325-bec0-34f9c9925908 /infinity btrfs defaults,nofail,noatime,compress=zstd,nossd 0 0

~
❯ inxi -b
System:
Host: veldabord Kernel: 7.0.11-1-cachyos-bore arch: x86_64 bits: 64
Desktop: KDE Plasma v: 6.7.3 Distro: CachyOS
Machine:
Type: Laptop System: HP product: HP Notebook v: Type1ProductConfigId
serial:
Mobo: HP model: 80CC v: 99.53 serial:  Firmware: UEFI
vendor: Insyde v: F.29 date: 02/07/2020
CPU:
Info: quad core AMD A8-7410 APU with AMD Radeon R5 Graphics [MCP]
speed (MHz): avg: 1455 min/max: 1000/2200
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Mullins [Radeon R4/R5 Graphics]
driver: amdgpu v: kernel
Device-2: Advanced Micro Devices [AMD/ATI] Sun XT [Radeon HD
8670A/8670M/8690M / R5 M330 M430 Radeon 520 Mobile] driver: amdgpu
v: kernel
Device-3: Realtek HP Truevision HD driver: uvcvideo type: USB
Display: wayland server: Xorg v: 1.21.1.24 with: Xwayland v: 24.1.13
compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
dri: radeonsi gpu: amdgpu resolution: 1366x768~60Hz
API: OpenGL v: 4.6 vendor: amd mesa v: 26.1.5-arch3.1 renderer: AMD
Radeon R5 Graphics (radeonsi kabini ACO DRM 3.64 7.0.11-1-cachyos-bore)
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: amdgpu_top wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Network:
Device-1: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
Device-2: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169
Drives:
Local Storage: total: 1.14 TiB used: 642.74 GiB (55.2%)
Info:
Memory: total: 8 GiB note: est. available: 6.71 GiB used: 3.74 GiB (55.7%)
Processes: 275 Uptime: 2h 26m Shell: fish inxi: 3.3.41

~
❯

Here is the cachyos-rate-mirrors per 21 July 2026 UTC+7 :

❯ sudo cachyos-rate-mirrors
[sudo] password for veldabord:

--> Ranking mirrors for arch repository in /etc/pacman.d/mirrorlist...

STARTED AT: 2026-07-21 01:29:26.035745863 +07:00

VERSION: 0.28.3

ARGS: rate-mirrors --save /tmp/tmp.FYcJBJVE8n arch

FETCHED MIRRORS: 1225

PROTOCOL FILTER: 710 -> 300 mirrors

MIRRORS LEFT AFTER FILTERING: 300

JUMP #1

EXPLORING ID

VISITED ID

+ NEIGHBOR US (by HubsFirst)

+ NEIGHBOR UK (by HubsFirst)

+ NEIGHBOR CA (by HubsFirst)

+ NEIGHBOR SG (by DistanceFirst)

+ NEIGHBOR DE (by DistanceFirst)

+ NEIGHBOR NL (by DistanceFirst)

FINISHED AT: 2026-07-21 01:30:20.345698868 +07:00

Server = https://fastly.mirror.pkgbuild.com/$repo/os/$arch
Server = https://geo.mirror.pkgbuild.com/$repo/os/$arch
Server = https://mirror.osbeck.com/archlinux/$repo/os/$arch
Server = https://singapore.mirror.pkgbuild.com/$repo/os/$arch
Server = https://in.arch.niranjan.co/$repo/os/$arch
Server = https://mirror.limda.net/archlinux/$repo/os/$arch
Server = https://mirrors.aliyun.com/archlinux/$repo/os/$arch
Server = https://mirrors.jlu.edu.cn/archlinux/$repo/os/$arch
Server = https://arch-mirror.wtako.net/$repo/os/$arch
Server = https://mirror.xeonbd.com/archlinux/$repo/os/$arch
Server = https://mirrors.reitarovskyi.com.ua/archlinux/$repo/os/$arch
Server = https://sg.arch.niranjan.co/$repo/os/$arch
Server = https://archlinux.koyanet.lv/archlinux/$repo/os/$arch
Server = https://mirror.trapmaid.org/archlinux/$repo/os/$arch
Server = https://wan.metrosg.ru/archlinux/$repo/os/$arch
Server = https://arch.yhtez.xyz/$repo/os/$arch
Server = https://arch.midov.pl/arch/$repo/os/$arch
Server = https://mirrors.dotsrc.org/archlinux/$repo/os/$arch
Server = https://arch.mirror.constant.com/$repo/os/$arch
Server = https://no.mirror.cx/archlinux/$repo/os/$arch
Server = https://mirror.twds.com.tw/archlinux/$repo/os/$arch
Server = https://at.arch.mirror.kescher.at/$repo/os/$arch
Server = https://ftp.energotel.sk/pub/linux/arch/$repo/os/$arch
Server = https://mirror.archlinux.si/$repo/os/$arch
Server = https://taipei.mirror.pkgbuild.com/$repo/os/$arch
Server = https://mirror.neuf.no/archlinux/$repo/os/$arch
Server = https://gluttony.sin.cvut.cz/arch/$repo/os/$arch
Server = https://mirrors.xtom.ee/archlinux/$repo/os/$arch
Server = https://at.arch.niranjan.co/$repo/os/$arch
Server = https://www.miraa.jp/archlinux/$repo/os/$arch
Server = https://ftp.ek-cer.hu/pub/mirrors/ftp.archlinux.org/$repo/os/$arch
==> Done [arch] /etc/pacman.d/mirrorlist
--> Ranking mirrors for cachyos repository in /etc/pacman.d/cachyos-mirrorlist...

STARTED AT: 2026-07-21 01:30:20.377443591 +07:00

VERSION: 0.28.3

ARGS: rate-mirrors --save /tmp/tmp.FYcJBJVE8n cachyos

MIRRORS LEFT AFTER FILTERING: 28

JUMP #1

EXPLORING ID

VISITED ID

BLANK ITERATION

COUNTRY JUMPING YIELDED TOO FEW MIRRORS (0), ADDING OTHERS TO UNLABELED



TESTING UNLABELED MIRRORS

SpeedTestResult { speed: 846.0 KB/s; elapsed: 870ms; connection_time: 394ms }

SpeedTestResult { speed: 457.0 KB/s; elapsed: 985ms; connection_time: 235ms }

TOO FEW BYTES LOADED https://mirror5.krfoss.org/cachyos/repo/

TOO FEW BYTES LOADED https://mirror2.keiminem.com/cachyos/repo/

TOO FEW BYTES LOADED https://mirror.keiminem.com/cachyos/repo/

TOO FEW BYTES LOADED https://mirrors.nguyenhoang.cloud/cachyos/repo/

SpeedTestResult { speed: 222.0 KB/s; elapsed: 980ms; connection_time: 826ms }

SpeedTestResult { speed: 378.8 KB/s; elapsed: 994ms; connection_time: 1.15s }

TOO FEW BYTES LOADED https://cdn.lansing2600.org/cachyos/repo/

TOO FEW BYTES LOADED https://mirror.lesviallon.fr/cachy/repo/

SpeedTestResult { speed: 209.5 KB/s; elapsed: 938ms; connection_time: 1.32s }

FAILED TO CONNECT TO https://mirror.mergedcloud.de/cachyos/repo/x86_64/cachyos/cachyos.files

SpeedTestResult { speed: 82.2 KB/s; elapsed: 992ms; connection_time: 2.28s }

SpeedTestResult { speed: 119.9 KB/s; elapsed: 951ms; connection_time: 2.36s }

TOO FEW BYTES LOADED https://mirror.nju.edu.cn/cachyos/repo/

SpeedTestResult { speed: 102.8 KB/s; elapsed: 796ms; connection_time: 2.63s }

TOO FEW BYTES LOADED https://cachyos-mirror.m1k.cloud/repo/

SpeedTestResult { speed: 427.4 KB/s; elapsed: 765ms; connection_time: 2.78s }

TOO FEW BYTES LOADED https://mirror.hb9hil.org/cachyos/repo/

TOO FEW BYTES LOADED https://mirrors.lansing2600.org/cachyos/repo/

TOO FEW BYTES LOADED https://mirror.jura12.ru/repo/

TOO FEW BYTES LOADED https://ca.mirror.cx/cachyos/repo/

TOO FEW BYTES LOADED https://mirror.zyner.org/mirror/cachyos/repo/

SpeedTestResult { speed: 117.2 KB/s; elapsed: 976ms; connection_time: 3.13s }

SpeedTestResult { speed: 114.7 KB/s; elapsed: 997ms; connection_time: 3.64s }

TOO FEW BYTES LOADED https://mirror.hjk.gg/cachyos/repo/

TOO FEW BYTES LOADED https://mirror.cachy-arch.ru/cachyos/repo/

SpeedTestResult { speed: 295.1 KB/s; elapsed: 943ms; connection_time: 6.38s }



RE-TESTING TOP MIRRORS

SpeedTestResult { speed: 1.2 MB/s; elapsed: 990ms; connection_time: 101ms }

SpeedTestResult { speed: 1.3 MB/s; elapsed: 992ms; connection_time: 39ms }

SpeedTestResult { speed: 606.6 KB/s; elapsed: 998ms; connection_time: 661ms }

SpeedTestResult { speed: 500.3 KB/s; elapsed: 867ms; connection_time: 1.27s }

SpeedTestResult { speed: 175.9 KB/s; elapsed: 930ms; connection_time: 1.08s }

==== RESULTS (top re-tested) ====

1. SpeedTestResult { speed: 1.3 MB/s; elapsed: 992ms; connection_time: 39ms } -> https://mirror.krfoss.org/cachyos/repo/

2. SpeedTestResult { speed: 1.2 MB/s; elapsed: 990ms; connection_time: 101ms } -> https://cdn77.cachyos.org/repo/

3. SpeedTestResult { speed: 606.6 KB/s; elapsed: 998ms; connection_time: 661ms } -> https://cachyos.next-works.it/repo/

4. SpeedTestResult { speed: 500.3 KB/s; elapsed: 867ms; connection_time: 1.27s } -> https://us.cachyos.org/repo/

5. SpeedTestResult { speed: 175.9 KB/s; elapsed: 930ms; connection_time: 1.08s } -> https://wan.metrosg.ru/cachyos/repo/

6. SpeedTestResult { speed: 222.0 KB/s; elapsed: 980ms; connection_time: 826ms } -> https://at.cachyos.org/repo/

7. SpeedTestResult { speed: 209.5 KB/s; elapsed: 938ms; connection_time: 1.32s } -> https://us-mnz.soulharsh007.dev/cachyos/repo/

8. SpeedTestResult { speed: 119.9 KB/s; elapsed: 951ms; connection_time: 2.36s } -> https://no.mirror.cx/cachyos/repo/

9. SpeedTestResult { speed: 117.2 KB/s; elapsed: 976ms; connection_time: 3.13s } -> https://mirrors.ustc.edu.cn/cachyos/repo/

10. SpeedTestResult { speed: 114.7 KB/s; elapsed: 997ms; connection_time: 3.64s } -> https://nl.mirror.cx/cachyos/repo/

11. SpeedTestResult { speed: 102.8 KB/s; elapsed: 796ms; connection_time: 2.63s } -> https://cachyos.doridian.net/repo/

12. SpeedTestResult { speed: 82.2 KB/s; elapsed: 992ms; connection_time: 2.28s } -> https://archlinux.gay/cachy/repo/

FINISHED AT: 2026-07-21 01:30:36.765143037 +07:00

Server = https://mirror.krfoss.org/cachyos/repo/$arch/$repo
Server = https://cdn77.cachyos.org/repo/$arch/$repo
Server = https://cachyos.next-works.it/repo/$arch/$repo
Server = https://us.cachyos.org/repo/$arch/$repo
Server = https://wan.metrosg.ru/cachyos/repo/$arch/$repo
Server = https://at.cachyos.org/repo/$arch/$repo
Server = https://us-mnz.soulharsh007.dev/cachyos/repo/$arch/$repo
Server = https://no.mirror.cx/cachyos/repo/$arch/$repo
Server = https://mirrors.ustc.edu.cn/cachyos/repo/$arch/$repo
Server = https://nl.mirror.cx/cachyos/repo/$arch/$repo
Server = https://cachyos.doridian.net/repo/$arch/$repo
Server = https://archlinux.gay/cachy/repo/$arch/$repo
==> Done [cachyos] /etc/pacman.d/cachyos-mirrorlist

~ 1m 14s

Here is the -Syu per 21 July 2026 UTC +7

❯ sudo pacman -Syu
:: Synchronizing package databases...
cachyos is up to date
core is up to date
extra                                       8.3 MiB  1177 KiB/s 00:07 [---------------------------------------] 100%
multilib is up to date
:: Starting full system upgrade...
warning: linux-cachyos-bore: ignoring package upgrade (7.0.11-1 => 7.1.3-2)
resolving dependencies...
looking for conflicting packages...

Package (2)   Old Version               New Version               Net Change  Download Size

extra/luajit  2.1.1784360928+14d8a7a-1  2.1.1784535789+5f627e4-1    0.02 MiB       0.33 MiB
extra/srt     1.5.5-1                   1.5.6-1                     0.03 MiB       0.53 MiB

Total Download Size:   0.87 MiB
Total Installed Size:  2.42 MiB
Net Upgrade Size:      0.05 MiB

:: Proceed with installation? [Y/n]

Here is the pacman.conf

❯ cat /etc/pacman.conf



/etc/pacman.conf



See the pacman.conf(5) manpage for option and repository directives



GENERAL OPTIONS



[options]

The following paths are commented out with their default values listed.

If you wish to use different paths, uncomment and update the paths.

#RootDir     = /
#DBPath      = /var/lib/pacman/
#CacheDir    = /var/cache/pacman/pkg/
#LogFile     = /var/log/pacman.log
#GPGDir      = /etc/pacman.d/gnupg/
#HookDir     = /etc/pacman.d/hooks/
HoldPkg     = pacman glibc
#XferCommand = /usr/bin/curl -L -C - -f -o %o %u
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
#UseDelta    = 0.7
Architecture = auto

Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup

IgnorePkg   = linux-cachyos-bore
#IgnoreGroup =

#NoUpgrade   =
#NoExtract   =

Misc options

#UseSyslog
Color
ILoveCandy
#NoProgressBar
#CheckSpace
VerbosePkgLists
DisableDownloadTimeout
ParallelDownloads = 10
DownloadUser = alpm
#DisableSandbox

By default, pacman accepts packages signed by keys that its local keyring

trusts (see pacman-key and its man page), as well as unsigned packages.

SigLevel    = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required

NOTE: You must run pacman-key --init before first using pacman; the local

keyring can then be populated with the keys of all official Arch Linux

packagers with pacman-key --populate archlinux.



REPOSITORIES

- can be defined here or included from another file

- pacman will search repositories in the order defined here

- local/custom mirrors can be added here or in separate files

- repositories listed first will take precedence when packages

have identical names, regardless of version number

- URLs will have $repo replaced by the name of the current repo

- URLs will have $arch replaced by the name of the architecture



Repository entries are of the format:

[repo-name]

Server = ServerName

Include = IncludePath



The header [repo-name] is crucial - it must be present and

uncommented to enable the repo.



cachyos repos

#<disabled_znver4>[cachyos-znver4]
#<disabled_znver4>Include = /etc/pacman.d/cachyos-v4-mirrorlist

#<disabled_znver4>[cachyos-core-znver4]
#<disabled_znver4>Include = /etc/pacman.d/cachyos-v4-mirrorlist

#<disabled_znver4>[cachyos-extra-znver4]
#<disabled_znver4>Include = /etc/pacman.d/cachyos-v4-mirrorlist

#<disabled_v4>[cachyos-v4]
#<disabled_v4>Include = /etc/pacman.d/cachyos-v4-mirrorlist

#<disabled_v4>[cachyos-core-v4]
#<disabled_v4>Include = /etc/pacman.d/cachyos-v4-mirrorlist

#<disabled_v4>[cachyos-extra-v4]
#<disabled_v4>Include = /etc/pacman.d/cachyos-v4-mirrorlist

#<disabled_v3>[cachyos-v3]
#<disabled_v3>Include = /etc/pacman.d/cachyos-v3-mirrorlist

#<disabled_v3>[cachyos-core-v3]
#<disabled_v3>Include = /etc/pacman.d/cachyos-v3-mirrorlist

#<disabled_v3>[cachyos-extra-v3]
#<disabled_v3>Include = /etc/pacman.d/cachyos-v3-mirrorlist

[cachyos]
Include = /etc/pacman.d/cachyos-mirrorlist

The testing repositories are disabled by default. To enable, uncomment the

repo name header and Include lines. You can add preferred servers immediately

after the header, and they will be used before the default mirrors.

#[core-testing]
#Include = /etc/pacman.d/mirrorlist

[core]
Include = /etc/pacman.d/mirrorlist

#[extra-testing]
#Include = /etc/pacman.d/mirrorlist

[extra]
Include = /etc/pacman.d/mirrorlist

If you want to run 32 bit applications on your x86_64 system,

enable the multilib repositories as required here.

#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist

[multilib]
Include = /etc/pacman.d/mirrorlist

An example of a custom package repository.  See the pacman manpage for

tips on creating your own repositories.

#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs

~
❯
2

Does that mean you update every month? Or less? Just asking to understand a bit better what we are dealing with.

warning: linux-cachyos-bore: ignoring package upgrade (7.0.11-1 => 7.1.3-2)

linux-cachyos-bore is currently in version 7.1.4-1, so one might wonder why your system would want to “upgrade” to an older version.

  • Try a sudo pacman -Syu again and maybe give us the output of that
  • and/or do cachyos-rate-mirrors
  • and/or give us the content of /etc/pacman.conf, because something might be off with your repos.

PS: thanks for all the info, but please try to format such output with the </> button or CTRL+E next time for readability reasons. I for one could not make heads or tails of ALL THOSE HUGE HEADLINES ALL OVER THE PLACE :laughing:

3

I’ve edited and updated the post now include the cachyos-rate-mirrors and sudo pacman -Syu result
and a better readability with </> format

So is there any change with the recent kernel update that cause my laptop to blackscreen (turned off screen) after loading initial ramdisk?

because before the update it just work fine so then I had to ignore the kernel update just to run -Syu and update anything else beside the kernel linux-cachyos-bore

Or I just need to wait for the newer update kernel linux-cachyos-bore that already fixed the problem then run the update after that fixed?

4

Thanks for taking the time to format the output.

I’m afraid I can’t answer your questions, because I never had such a problem that a pacman -Syu lead to an unbootable system (knock on wood), but I’m sure someone else might have an idea :crossed_fingers:

Please also provide the output of cat /etc/pacman.conf, in case something is messed up here. Many problems like these stem from a misconfigured pacman.

5

I’ve added the pacman.conf in the post also, thanks for the feedback.
as I remember I only include x64 multilib for a 32bit games in pacman config.
And for now I’ll just wait here and still ignoring the kernel linux-cachyos-bore update until it fixed in the newer version I hope.

6

Errm… to my untrained eye it looks as if all important repos are commented out?

#<disabled_znver4>[cachyos-znver4]
#<disabled_znver4>Include = /etc/pacman.d/cachyos-v4-mirrorlist

#<disabled_znver4>[cachyos-core-znver4]
#<disabled_znver4>Include = /etc/pacman.d/cachyos-v4-mirrorlist

#<disabled_znver4>[cachyos-extra-znver4]
#<disabled_znver4>Include = /etc/pacman.d/cachyos-v4-mirrorlist

#<disabled_v4>[cachyos-v4]
#<disabled_v4>Include = /etc/pacman.d/cachyos-v4-mirrorlist

#<disabled_v4>[cachyos-core-v4]
#<disabled_v4>Include = /etc/pacman.d/cachyos-v4-mirrorlist

This should not be? Please make a backup of it before you change anything in that file!!

This is the relevant section of my pacman.conf:

#
# REPOSITORIES
#   - can be defined here or included from another file
#   - pacman will search repositories in the order defined here
#   - local/custom mirrors can be added here or in separate files
#   - repositories listed first will take precedence when packages
#     have identical names, regardless of version number
#   - URLs will have $repo replaced by the name of the current repo
#   - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
#       [repo-name]
#       Server = ServerName
#       Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#

# cachyos repos

[cachyos-znver4]
Include = /etc/pacman.d/cachyos-v4-mirrorlist

[cachyos-core-znver4]
Include = /etc/pacman.d/cachyos-v4-mirrorlist

[cachyos-extra-znver4]
Include = /etc/pacman.d/cachyos-v4-mirrorlist

[cachyos]
Include = /etc/pacman.d/cachyos-mirrorlist

# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.

#[core-testing]
#Include = /etc/pacman.d/mirrorlist

[core]
Include = /etc/pacman.d/mirrorlist

#[extra-testing]
#Include = /etc/pacman.d/mirrorlist

[extra]
Include = /etc/pacman.d/mirrorlist

# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.

#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist

[multilib]
Include = /etc/pacman.d/mirrorlist

See? Here, all the v4 repos are active. Of course it depends on your CPU, maybe it’s correct that those are commented out. I am on a Ryzen 7 8700G here, so v4 is my turf.

I can’t guide you how to fix your conf because I am too much of a noob, but why was your conf changed like that? Did you do that manually?

7

I think it is the default pacman.conf for my laptop and I believe it has a different conf for different region and devices from where is shipped.
The only thing I edit is just uncomment the mutilib for a 32bit games and the most recent edit is that I uncomment the IgnorePkg and added linux-cachyos-bore to exclude the kernel update.

I pretty sure it has nothing to do with the repo and the pacman conf,
like i said before,

Everything works perfectly fine before the kernel update

so it must be the kernel update that has some error bug issue, not my fault.

8

If they do not have v3 or newer then all of those should be disabled.

Its a little funny looking but assuming the hardware is old enough it is not wrong.

What may be an issue is all the comments that are not comments;

But it is unclear if that is a result of broken format while sharing or what.

I would probably suggest use something like the following to be sure;

paste-cachyos /etc/pacman.conf

(and share the link here)

9

i was there in the bottom of the first post

10

No it is not.

There is no link to any paste anywhere in this thread.

Some manually pasted text is posted above that, in its presentation here, is broken.

So, because we are not sure if we can rely on that presentation, I am suggesting to use the paste tool so we get the whole file intact.

11

I’ve provided the conf in the first page at the very bottom.

And also its not about the conf that cause the trouble, its the kernel updates!

Everyone else with older and legacy hardware/device or laptop are experiencing the same issue, error and bug everywhere with that 7.1 recent kernel update.
One that doesn’t affected are with newer hardware.

I’m not going to cause any more error with messing around config or anything else.
the root cause is just that recent kernel update has so many error issue and bugs!

Everything works perfectly fine before the kernel update!

the repo is fine, the boot is fine, the pacman is fine,

I’ll just waiting here and keep ignoring the kernel update for a month and see if they fix it or not.
if not, I’ll just trying another distro eventho I didn’t want to.

12

And I repeat that we cannot rely on that - so I am asking for a different method of sharing it.

If it is exactly as you show here then it is broken and needs fixing.

So you say.

But if the conf file is as it appears here you absolutely need to edit it.

And its not clear it is not causing an issue.

For example a malformed pacman.conf can cause partial-upgrades .. leading to a system state like you describe.

Is that true?
I am not so sure.
In any case I would suggest most users keep an LTS installed and for users of very old hardware it also probably makes even more sense.

OK so you do not want to investigate or fix anything?
Then what is the point of the thread?

It is a bit odd and extreme you ‘do not want’ to even share the contents of the conf file .. but are willing to commit a partial-upgrade, artificially hold a package back, or just hold off on all upgrades including security patches for a month or more.

If your pacman.conf were broken then an upgrade could cause instability through not being able to perform the upgrade correctly.

And maybe then we will find out if you actually have a broken pacman.conf or not.

Which I will repeat again that if it appears as you show here, even if it is not the cause of this problem, would still be a problem.

PS.

This looks like a BIOS problem to me.
Do you have BIOS updates?
Again we would need you to cooperate - the output of sudo cachyos-bugreport.sh would be helpful here. Alas.

13

long time ago back when i was on windows, I updated my BIOS driver where supposedly not, because laptop hardware should be using default driver as they shipped, that include my display driver and it really buggy so I’ve to downgrade that driver. but magically when I installed cachyos that display driver problem is gone im so happy up until the recent kernel 7.1 updates

I’ve been using cachyos for almost a year now and never facing a screen black out after an update!
the pacman config still work fine until now
the point of this thread is to let know that are error and bugs on the recent kernel update and needed to be fix!

The downside to being on the absolute frontier of Linux development is that we are the first line of defense when upstream code contains massive architectural bugs.

Because these bugs live directly inside the core code of linux-cachyos 7.1.x, no amount of configuration tweaking or manual file scrubbing will permanently stabilize it.

Staying parked safely on the 6.18 LTS kernel branch is the objective, correct choice while Linus Torvalds and the AMD driver maintainers patch these regressions over the next few sub-minor iterations.

here are some error issues and bugs caused by the recent kernel updates 7.1

https://paste.cachyos.org/a556d3f.conf

im not refusing it was just there the whole time you just ignore it

14

We cannot be sure until you actually share it.

I repeat - if it is as you show it above then it is broken.

I was giving some lee-way and guessing maybe some of it could be attributed to formatting and so suggest you use the pasting tool.

You refuse to do that so I can only guess as to the real content of the file.

Similarly a bugreport was asked for and also refused.

:person_shrugging:

15

Let me try to calm the waves a little.

The problem here is that somehow in the process of copy/pasting and then reformatting the output of cat /etc/mkinitcpio.conf and cat /etc/pacman.conf, apparently some characters might have gone missing.

For example this part

MODULES

The following modules are loaded before any boot hooks are

run.  Advanced users may wish to specify all system modules

in this array.  For instance:

MODULES=(usbhid xhci_hcd)

simply cannot really look like that, because these are all comments and should look like this:

# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
# MODULES=(usbhid xhci_hcd)

Same is true for the pacman.conf.

Therefore, @cscs proposed to directly upload those files to paste.cachyos.org like so

paste-cachyos /etc/pacman.conf

I see you did that in this post, but it is easily to be overlooked.

So here is the link again: https://paste.cachyos.org/a556d3f.conf

And maybe we cant get the same for /etc/mkinitcpio.conf?

paste-cachyos /etc/mkinitcpio.conf

And also the output of cachyos-bugreport.sh?

PS: We are here to help, but we are all unpaid humans, doing this in our spare time and hitting us with your frustration does not really help anyone. I understand you are frustrated, but there is really no need to argue.

16

It was not present in the original form of the post. It was added in a subsequent edit.

The pacman.conf does look fine - the comments were comments and formatting here was the issue.

We can still check on the mirrorlist files in the same way so that we are sure they contain working mirrors but with that we would be done with that line of inquiry.

We may still be interested in

sudo cachyos-bugreport.sh

So that we can see more general system information.

Of course there is always the question of pacnews too;

pacdiff -o
17

I didn’t know that new user have a limited amount of reply sorry i had to do that in an edited reply and still I didn’t find answer to my first question.
is it safe to keep ignoring the kernel update?

if yes how long will it be safe?

if not will it break my system?

18

It will break your system eventually if you keep refusing updates for Just the kernel, but if you were to hold off on all updates you could be fine for awhile. Just remember that if you wait too long you’re going to end up with a mega update that could include hundreds of files.

As long as you have plenty of free space in your root filesystem that shouldn’t be a problem.

A much better, safer option would be to just use the LTS until the current tomfoolery with 7.X stabilizes. It does exist for the exact reason that sometimes the “stable” kernel will have issues that don’t affect upstream testing but once they hit the wider market a whole host of bs just appears out of the woodwork.

19

Difficult to define ‘safe’.

But if we want the black-and-white standard .. any package ignored is inherently a partial-upgrade which means the system is in a broken state. How much of a real problem this is will depend on the current status and what is being skipped and so on. But it will get worse the longer this goes on.

This is the more correct answer.


For further assistance