New updates have killed the system [2025 Sept 26th]

I wonder whether there’s a common pattern of failure between our systems.

I don’t suppose you could add a few echo statements around code I found failing?

### BEGIN /etc/grub.d/25_bli ###
echo "------------ LOGS -------------"
if [ "$grub_platform" = "efi" ]; then
  echo "before 'insmod bli' call"
  insmod bli
  echo "after 'insmod bli call"
fi

Though that would require booting into Live USB, mounting the partition wherever your /boot is, then chmod 666 /boot/grub/grub.cfg, and then kate /boot/grub/grub.cfg to open it. Ofc, this would take a bit of time due to needing to boot to usb.

Edit: assuming your problem system is EFI.

The inxi -zv8 report:

System:
  Kernel: 6.12.48-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
    misobasedir=manjaro misolabel=MANJARO_KDE_2509 quiet
    systemd.show_status=1 splash driver=nonfree nouveau.modeset=0
    i915.modeset=1 radeon.modeset=1
  Desktop: KDE Plasma v: 6.3.6 tk: Qt v: N/A info: frameworks v: 6.18.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 20EQS1MY02 v: ThinkPad P50
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: LENOVO model: 20EQS1MY02 v: SDK0J40697 WIN
    serial: <superuser required>
    part-nu: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50
    uuid: <superuser required> UEFI: LENOVO v: N1EETA2W (1.75 )
    date: 03/18/2024
Battery:
  ID-1: BAT0 charge: 20.1 Wh (100%) condition: 20.1/90.1 Wh (22.4%)
    volts: 12.62 min: 11.4 model: LGC 00NY492 type: Li-poly serial: <filter>
    charging: status: full control: start: 0% end: 100% cycles: N/A
Memory:
  System RAM: total: 32 GiB available: 31.17 GiB used: 3.8 GiB (12.2%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 4 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: ChannelA-DIMM0 type: no module installed
  Device-2: ChannelA-DIMM1 type: DDR4 detail: synchronous size: 16 GiB
    speed: 2133 MT/s volts: curr: 1 width (bits): data: 64 total: 64
    manufacturer: f301 part-no: G2BT-4AFP00 serial: <filter>
  Device-3: ChannelB-DIMM0 type: no module installed
  Device-4: ChannelB-DIMM1 type: DDR4 detail: synchronous size: 16 GiB
    speed: 2133 MT/s volts: curr: 1 width (bits): data: 64 total: 64
    manufacturer: f301 part-no: G2BT-4AFP00 serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i7-6820HQ bits: 64 type: MT MCP arch: Skylake-S
    gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
    model-id: 0x5E (94) stepping: 3 microcode: 0xF0
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
    smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
    desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 900 min/max: 800/3600 scaling: driver: intel_pstate
    governor: powersave cores: 1: 900 2: 900 3: 900 4: 900 5: 900 6: 900 7: 900
    8: 900 bogomips: 43214
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida
    intel_pt invpcid lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr
    mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge
    pln pni popcnt pse pse36 pti pts rdrand rdseed rdtscp rep_good sdbg sep
    smap smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2
    tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic
    xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: conditional;
    RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsa status: Not affected
  Type: tsx_async_abort mitigation: TSX disabled
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Intel HD Graphics 530 vendor: Lenovo driver: i915 v: kernel
    arch: Gen-9 process: Intel 14n built: 2015-16 ports: active: eDP-1
    empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:191b
    class-ID: 0300
  Device-2: NVIDIA GM107GLM [Quadro M1000M] vendor: Lenovo driver: nvidia
    v: 580.82.09 alternate: nouveau,nvidia_drm non-free: 550-580.xx+
    status: current (as of 2025-08; EOL~2026-12-xx) arch: Maxwell code: GMxxx
    process: TSMC 28nm built: 2014-2019 pcie: gen: 1 speed: 2.5 GT/s lanes: 16
    link-max: gen: 3 speed: 8 GT/s ports: active: none empty: DP-3,DP-4,DP-5
    bus-ID: 01:00.0 chip-ID: 10de:13b1 class-ID: 0300
  Device-3: Chicony Integrated Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-8:4 chip-ID: 04f2:b52c
    class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_x11 driver: X: loaded: modesetting,nvidia
    alternate: fbdev,nouveau,nv,vesa dri: iris gpu: i915 display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: eDP-1 model: LG Display 0x04a7 built: 2015 res: mode: 1920x1080
    hz: 60 scale: 100% (1) dpi: 142 gamma: 1.2 chroma: red: x: 0.580 y: 0.349
    green: x: 0.341 y: 0.561 blue: x: 0.153 y: 0.125 white: x: 0.314 y: 0.329
    size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9
    modes: 1920x1080
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
    drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia x11: drv: iris inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 25.2.3-arch1.2
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 530 (SKL GT2)
    device-ID: 8086:191b memory: 30.44 GiB unified: yes
  API: Vulkan v: 1.4.321 layers: 2 device: 0 type: discrete-gpu
    name: Quadro M1000M driver: nvidia v: 580.82.09 device-ID: 10de:13b1
    surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
    chip-ID: 8086:a170 class-ID: 0403
  Device-2: NVIDIA GM107 High Definition Audio [GeForce 940MX]
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:0fbc class-ID: 0403
  API: ALSA v: k6.12.48-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.8 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-LM vendor: Lenovo driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b7 class-ID: 0200
  IF: enp0s31f6 state: down mac: <filter>
  Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:24f3 class-ID: 0280
  IF: wlp4s0 state: down mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: No WAN IP found. Connected to web? SSL issues? Try enabling dig
Bluetooth:
  Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:6 chip-ID: 8087:0a2b
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 953.61 GiB used: 1.17 GiB (0.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SNV3S1000G
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: P3BR0A23 temp: 31.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: Cruzer Blade
    size: 14.59 GiB block-size: physical: 512 B logical: 512 B type: USB
    rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
    fw-rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-3: /dev/sdb maj-min: 8:16 vendor: Generic model: Flash Disk
    size: 7.5 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 2.0
    spd: 480 Mb/s lanes: 1 mode: 2.0 tech: SSD serial: <filter> fw-rev: 8.07
    scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  Message: No optical or floppy data found.
Partition:
  ID-1: /run/media/manjaro/usb drive raw-size: 7.5 GiB size: 7.5 GiB (99.97%)
    used: 1.17 GiB (15.6%) fs: exfat dev: /dev/sdb1 maj-min: 8:17
    label: usb drive uuid: 5FDB-73C9
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/nvme0n1p1 maj-min: 259:1 size: 512 MiB fs: vfat label: EFI
    uuid: 97C9-51DD
  ID-2: /dev/nvme0n1p2 maj-min: 259:2 size: 1024 MiB fs: ext4 label: N/A
    uuid: eae378fb-40ca-4fd3-b46c-58b1a88345b8
  ID-3: /dev/nvme0n1p3 maj-min: 259:3 size: 32 GiB fs: swap label: N/A
    uuid: eced3123-24e6-4e9e-9deb-da51e0417c7b
  ID-4: /dev/nvme0n1p4 maj-min: 259:4 size: 898.01 GiB fs: btrfs
    label: Manjaro uuid: 5be28fc1-be69-47de-b656-d5a869416fd4
  ID-5: /dev/sda1 maj-min: 8:1 size: 5.1 GiB fs: iso9660
  ID-6: /dev/sda2 maj-min: 8:2 size: 4 MiB fs: vfat label: MISO_EFI
    uuid: 639E-4CF8
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-1:2 info: Alcor Micro Flash Drive type: mass storage
    driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 200mA chip-ID: 058f:6387 class-ID: 0806
    serial: <filter>
  Device-2: 1-5:3 info: SanDisk Cruzer Blade type: mass storage
    driver: usb-storage interfaces: 1 rev: 2.1 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 224mA chip-ID: 0781:5567 class-ID: 0806
    serial: <filter>
  Device-3: 1-8:4 info: Chicony Integrated Camera type: video
    driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 500mA chip-ID: 04f2:b52c class-ID: 0e02
    serial: <filter>
  Device-4: 1-9:5 info: Validity Sensors VFS7500 Touch Fingerprint Sensor
    type: <vendor specific> driver: N/A interfaces: 1 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 138a:0090 class-ID: ff00 serial: <filter>
  Device-5: 1-14:6 info: Intel Bluetooth wireless interface type: bluetooth
    driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
    mode: 1.1 power: 100mA chip-ID: 8087:0a2b class-ID: e001
  Hub-2: 2-0:1 info: super-speed hub ports: 10 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 39.0 C pch: 37.5 C mobo: N/A
  Fan Speeds (rpm): fan-1: 0 fan-2: 0
Repos:
  Packages: pm: pacman pkgs: 1277 libs: 324 tools: pamac pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://distrohub.kyiv.ua/manjaro/stable/$repo/$arch
    2: https://mirror.futureweb.be/manjaro/stable/$repo/$arch
    3: https://mirror.dc.uz/manjaro/stable/$repo/$arch
    4: https://bd.mirror.vanehost.com/Manjaro/stable/$repo/$arch
    5: https://mirrors.sjtug.sjtu.edu.cn/manjaro/stable/$repo/$arch
    6: https://edgeuno-bog2.mm.fcix.net/manjaro/stable/$repo/$arch
    7: https://mirror.csclub.uwaterloo.ca/manjaro/stable/$repo/$arch
    8: https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch
    9: https://cofractal-ewr.mm.fcix.net/manjaro/stable/$repo/$arch
    10: https://irltoolkit.mm.fcix.net/manjaro/stable/$repo/$arch
    11: https://mirrors.cicku.me/manjaro/stable/$repo/$arch
    12: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
    13: https://mirror.fcix.net/manjaro/stable/$repo/$arch
    14: https://mirror.telepoint.bg/manjaro/stable/$repo/$arch
    15: https://mnvoip.mm.fcix.net/manjaro/stable/$repo/$arch
    16: https://ohioix.mm.fcix.net/manjaro/stable/$repo/$arch
    17: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
    18: https://mirror.dkm.cz/manjaro/stable/$repo/$arch
    19: https://mirror.truenetwork.ru/manjaro/stable/$repo/$arch
    20: https://manjaro.syxpi.fr/manjaro/stable/$repo/$arch
    21: https://manjaro.ipacct.com/manjaro/stable/$repo/$arch
    22: https://mirror.kamtv.ru/manjaro/stable/$repo/$arch
    23: https://quantum-mirror.hu/mirrors/pub/manjaro/stable/$repo/$arch
    24: https://mirrors.aliyun.com/manjaro/stable/$repo/$arch
    25: https://mirror1.sox.rs/manjaro/stable/$repo/$arch
    26: https://repo.iut.ac.ir/repo/manjaro/stable/$repo/$arch
    27: https://mirrors.manjaro.org/repo/stable/$repo/$arch
    28: http://ftp.uni-kl.de/pub/linux/manjaro/stable/$repo/$arch
    29: https://mirror.zetup.net/manjaro/stable/$repo/$arch
    30: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
    31: https://mirror.mobinhost.com/manjaro/stable/$repo/$arch
    32: https://ftp.riken.jp/Linux/manjaro/stable/$repo/$arch
    33: https://ftp.linux.org.tr/manjaro/stable/$repo/$arch
    34: https://mirror.freedif.org/Manjaro/stable/$repo/$arch
    35: https://mirror.2degrees.nz/manjaro/stable/$repo/$arch
    36: https://mirrors2.manjaro.org/stable/$repo/$arch
    37: https://manjaro.grena.ge/stable/$repo/$arch
    38: https://mirrors.sonic.net/manjaro/stable/$repo/$arch
    39: https://ftp.cc.uoc.gr/mirrors/linux/manjaro/stable/$repo/$arch
    40: https://mirrors.eric.ovh/manjaro/stable/$repo/$arch
    41: https://mirror.easyname.at/manjaro/stable/$repo/$arch
    42: https://ftpmirror1.infania.net/mirror/manjaro/stable/$repo/$arch
    43: https://mirror.nyist.edu.cn/manjaro/stable/$repo/$arch
    44: https://mirror.datacenter.by/pub/mirrors/manjaro/stable/$repo/$arch
    45: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
    46: https://mirror.raiolanetworks.com/manjaro/stable/$repo/$arch
    47: https://mirror.archlinux.tw/Manjaro/stable/$repo/$arch
    48: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
    49: https://fosszone.csd.auth.gr/manjaro/stable/$repo/$arch
    50: https://mirror.23m.com/manjaro/stable/$repo/$arch
    51: https://mirror.dimensiondata.com/mirrors/manjaro.org/stable/$repo/$arch
    52: http://ossmirror.mycloud.services/os/linux/manjaro/stable/$repo/$arch
    53: https://mirror.aarnet.edu.au/pub/manjaro/stable/$repo/$arch
    54: https://mirror.xenyth.net/manjaro/stable/$repo/$arch
    55: https://mirror.koddos.net/manjaro/stable/$repo/$arch
    56: https://mirrors.ocf.berkeley.edu/manjaro/stable/$repo/$arch
    57: https://mirror.xeonbd.com/manjaro/stable/$repo/$arch
    58: https://ask4.mm.fcix.net/manjaro/stable/$repo/$arch
    59: https://mirror.hostiko.network/manjaro/stable/$repo/$arch
    60: https://mirror.leitecastro.com/manjaro/stable/$repo/$arch
    61: https://ftp.free.org/mirrors/repo.manjaro.org/repos/stable/$repo/$arch
    62: https://mirror.vinehost.net/manjaro/stable/$repo/$arch
    63: https://linorg.usp.br/manjaro/stable/$repo/$arch
    64: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
    65: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
    66: https://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
    67: https://mirrors.dotsrc.org/manjaro/stable/$repo/$arch
    68: https://mirrors.jlu.edu.cn/manjaro/stable/$repo/$arch
    69: https://southfront.mm.fcix.net/manjaro/stable/$repo/$arch
    70: https://ftp.snt.utwente.nl/pub/linux/manjaro/stable/$repo/$arch
    71: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
    72: https://nnenix.mm.fcix.net/manjaro/stable/$repo/$arch
    73: https://mirror.meowsmp.net/manjaro/stable/$repo/$arch
    74: https://free.nchc.org.tw/manjaro/stable/$repo/$arch
    75: https://mirror.bouwhuis.network/manjaro/stable/$repo/$arch
    76: https://ftp.caliu.cat/pub/distribucions/manjaro/stable/$repo/$arch
    77: https://manjaro.mirrors.uk2.net/stable/$repo/$arch
    78: https://kartolo.sby.datautama.net.id/manjaro/stable/$repo/$arch
    79: https://mirror.komelt.dev/manjaro/stable/$repo/$arch
    80: https://mirrors.ft.uam.es/manjaro/stable/$repo/$arch
    81: https://ipng.mm.fcix.net/manjaro/stable/$repo/$arch
    82: https://manjaro.kurdy.org/stable/$repo/$arch
    83: https://mirrors.ucr.ac.cr/manjaro/stable/$repo/$arch
    84: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/$repo/$arch
    85: https://mirrors.nic.cz/manjaro/stable/$repo/$arch
    86: https://manjaro.mirror.ac.za/stable/$repo/$arch
    87: https://mirrors.atlas.net.co/manjaro/stable/$repo/$arch
    88: https://mirror.ufro.cl/manjaro/stable/$repo/$arch
    89: https://mirrors.ustc.edu.cn/manjaro/stable/$repo/$arch
    90: https://muug.ca/mirror/manjaro/stable/$repo/$arch
    91: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch
    92: https://ba.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    93: https://mirror.init7.net/manjaro/stable/$repo/$arch
    94: https://mirror.alwyzon.net/manjaro/stable/$repo/$arch
    95: https://ftp.psnc.pl/linux/manjaro/stable/$repo/$arch
    96: https://manjaro.mirror.wearetriple.com/stable/$repo/$arch
    97: https://mirror.ibakerserver.pt/manjaro/stable/$repo/$arch
    98: https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/stable/$repo/$arch
    99: https://coresite.mm.fcix.net/manjaro/stable/$repo/$arch
    100: https://ftp.lysator.liu.se/pub/manjaro/stable/$repo/$arch
    101: https://ziply.mm.fcix.net/manjaro/stable/$repo/$arch
    102: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
    103: https://manjaro.repo.cure.edu.uy/stable/$repo/$arch
    104: https://manjaro.mirror.liquidtelecom.com/stable/$repo/$arch
    105: https://manjaro.mirrors.lavatech.top/stable/$repo/$arch
    106: https://mirror.nju.edu.cn/manjaro/stable/$repo/$arch
    107: https://ftp.belnet.be/mirrors/manjaro/repos/stable/$repo/$arch
    108: https://mirrors.up.pt/pub/manjaro/stable/$repo/$arch
    109: https://mirror.netcologne.de/manjaro/stable/$repo/$arch
    110: https://mirror.kku.ac.th/manjaro/stable/$repo/$arch
    111: https://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch
    112: https://mirror.yandex.ru/mirrors/manjaro/stable/$repo/$arch
    113: https://manjaro.ynh.ovh/stable/$repo/$arch
    114: https://manjaro.mirror.garr.it/manjaro/stable/$repo/$arch
    115: https://mirror.ufam.edu.br/manjaro/stable/$repo/$arch
    116: https://mirror.phoepsilonix.love/manjaro/stable/$repo/$arch
    117: https://mirrors.pku.edu.cn/manjaro/stable/$repo/$arch
    118: https://mirror.it4i.cz/manjaro/stable/$repo/$arch
    119: https://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/$repo/$arch
    120: https://mirrors.tuna.tsinghua.edu.cn/manjaro/stable/$repo/$arch
    121: https://mirrors.xtom.jp/manjaro/stable/$repo/$arch
    122: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
    123: https://ct.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    124: https://manjarolinux-mirror.cloud.mu/stable/$repo/$arch
    125: https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 255
  1: cpu: 3.8% command: zsh pid: 18865 mem: 9.08 MiB (0.0%)
  2: cpu: 3.2% command: plasmashell pid: 18196 mem: 289.6 MiB (0.9%)
  3: cpu: 2.1% command: Xorg pid: 18046 mem: 162.2 MiB (0.5%)
  4: cpu: 1.8% command: kwin_x11 pid: 18145 mem: 169.9 MiB (0.5%)
  5: cpu: 1.5% command: dolphin pid: 18775 mem: 131.7 MiB (0.4%)
  Memory top: 5 of 255
  1: mem: 289.6 MiB (0.9%) command: plasmashell pid: 18196 cpu: 3.2%
  2: mem: 169.9 MiB (0.5%) command: kwin_x11 pid: 18145 cpu: 1.8%
  3: mem: 162.2 MiB (0.5%) command: Xorg pid: 18046 cpu: 2.1%
  4: mem: 131.7 MiB (0.4%) command: dolphin pid: 18775 cpu: 1.5%
  5: mem: 124.4 MiB (0.3%) command: kate pid: 18835 cpu: 0.8%
Info:
  Processes: 255 Power: uptime: 4m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.42 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Compilers: N/A Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.39

Too late, reinstall in progress.

Nw, could you let me know how it works out?
I have a feeling I’ll have to reinstall as well.

Trying Kubuntu this time around, I just can’t find the motivation to deal with this on her laptop, which she only uses to start a browser. Switching distro usually results in reinstalling Manjaro a couple of weeks later though. We’ll see how it goes.

2 Likes

Literally my experience. Had some, possibly, grub-related issue some months back. Figured, I’ve been reinstalling Manjaro too much already, and maybe I ought to try another distro.

Tried Linux Mint - everything worked like a charm until… I found that the OS shutsdown, but not laptop’s power. Over 2 days of troubleshooting I found that it’s kernel related. Some issue with ACPI, and out of a few available kernels I could switch between all were affected (minus the older version of mint that would get deprecated in 2 months from the install).

It turned out the issue was inherited from Ubuntu kernel as I saw the same issue reported against Ubuntu kernel… meaning no Ubuntu based distro was probably free from that issue. Ended up switching back to Manjaro. :persevere:

Have you done this already?

Beforehand I would uninstall install-grub.

Yes I did. Sadly, it had no effect.
After performing that, I’m still having the same issue with system halting whilst executing grub.cfg on loading of bli module.

" Beforehand I would uninstall install-grub."

I couldn’t install anything such as grub within that live boot chroot environment due to domain recognition issues with anything mirror related. So uninstalling to re-install wouldn’t work. I tried adding nameservers like 1.1.1.1 or 8.8.8.8 manually, but with no luck.

Could you try to disable the bli module of Grub?

chmod -x /etc/grub.d/25_bli

Edit:

The bli module seems to write some EFI variables. Could it be that there is some problem with that? For example I remember a few years ago a system that had problems because it’s UEFI variable memory was full (it was quite old system to be fair)

2 Likes

Did you downgrade and re-intall grub (via running install-grub.sh plus re-generate the config (via running update-grub.sh)? This should result into what was installed before the update that broke the bootloader. (From the logs i tend to think the new grub version has an issue with the device. This bug report is also for a Lenovo laptop, although seemingly a newer model.)

Regarding stability i blacklisted any grub related packages. From my /etc/pacman.conf

IgnorePkg   = grub-theme-manjaro grub update-grub install-grub

install-grub was never installed on any of my systems, but i’m just afraid of accidents :wink:

1 Like

Maybe I should remove the package install-grub to be part of the default install medias. Seems updating grub in MBR still creates some issues.

1 Like

Seems like all this file contains is that quoted if statement with the module load.
I suppose I could comment out this if statement from the /boot/grub/grub.cfg. I’ll give it a go after 20mins or so once my files back up finishes.

That’s quite curious. Do you know how one would check for such issue? Based on the logs I gathered, it seems the halt happens after triggering some init function after the bli load. I’m guessing there’s something within that function that’s problematic.

I’m unsure of how I would go about doing that. I followed the tutorial linked, but I didn’t see any downgrading action. I assume if I uninstall it & reinstall it, I’ll just get the latest version back, no?

This looks highly promising for going forward. I think I’ll just ignore these package updates as well when I get the system sorted.

In my case the disk’s partition table is GPT.
So GPT could be affected as well.

With MBR I mean the master boot record and the similar in UEFI BIOS. The last time Arch needed to proper install grub was back in 08-2022: Arch Linux - News: Grub bootloader upgrade and configuration incompatibilities However, since we have the package install-grub pre-installed, it seems more breakage can happen. Old issue with configs: FS#75701 : grub 2:2.06.r322.gd9b4638c5-1 issue

Whoah!

Commenting these lines out from /boot/grub/grub.cfg:

Seemed to have allowed the system to reach the grub menu. Further more, as the 5s timeout ended, it just booted into my system.

I’ve got to say I’m surprised. I was expecting the commenting out of this module load to cause issues further down the grub.cfg. But no issues seem to have happened.

I haven’t tried logging into my system or doing anything inside yet. I’ll probably do further testing to see if all is good tomorrow … as it’s sleep time in my time zone.

But I’ve got to wonder… what was the purpose of the BLI module then if it’s … preliminary… seemingly… not needed? Is it some quality of life stuff?

@philm Do you think there’s any connection to what install-grub did that relates to BLI module?

3 Likes

Hmm, needs more investigation. You can move out the /etc/grub.d/25_bli file from /etc/grub.d folder on your system: GNU GRUB Manual 2.12: bli

You may also want to add the following to your /etc/pacman.conf

NoExtract = etc/grub.d/25_bli

Pacman: Skip files from being installed to System

Then update grub.cfg via update-grub and double-check if the BLI section got removed.


Issue I found in the Arch Forum:

3 Likes

The script does not change any grub configuration items or files.

The default/grub is read and other information is extracted from the system.

GRUB maintenance tasks are executed based on the information but no changes to configuration are made outside what grub-install or grub-mkconfig provides. nor is the installation mode changed.

As noted by @philm the issue requires more investigation but the issue on the Arch BBS indicates it to be rooted with GRUB.

EDIT:
This is entiirely speculation…

Since the BLI module is writing data to NVRAM intended to be read by the operating system - I am fhinking - if the NVRAM has run out of space?

I recall issues going back years - where the installer would break with a cryptic message - not enough space on device - and the message was thrown on attempt to write a new boot entry to NVRAM.

1 Like

Got it, thanks for clearing it up.

Also, I did a check on the status of efivarfs as EFI vars were mentioned a couple of times here. It seems that it still has a good deal of free space available. So whatever the BLI module initialization was, it’s likely not lack of efi vars storage. :thinking:

$ df -h /sys/firmware/efi/efivars
Filesystem      Size  Used Avail Use% Mounted on
efivarfs        154K   84K   65K  57% /sys/firmware/efi/efivars

I had the same issue, when upgrading the newest Grub package using pacman with my Lenovo P50. Your suggestion worked for me as well.

Seems since Arch is not updating the grub install but Garuda does it, we have a similar issue on an older PC: GRUB update broke normal laptop boot - Issues & Assistance - Garuda Linux Forum

https://lists.gnu.org/archive/html/bug-grub/2025-09/msg00001.html

Most likely this created the regression with bli: commands/bli: Set LoaderTpm2ActivePcrBanks runtime variable - grub.git - GNU GRUB

1 Like

Proper fix is now added to grub packages: https://lists.gnu.org/archive/html/grub-devel/2025-09/msg00194.html

@DurpiuKalnas can you retest it?

1 Like