Skip to main content
Topic: Strange Messages when updating kernels with pacamn SUY (Read 883 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Strange Messages when updating kernels with pacamn SUY

When doing a system update, I got this trace
Code: [Select]
Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
==> Using drop-in configuration file: 'asus.conf'
==> Starting build: '6.7.5-artix1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
/usr/lib/initcpio/functions: line 561: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 561: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 596: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 596: _addedmodules[]: bad array subscript
==> ERROR: module not found: ''
/usr/lib/initcpio/functions: line 944: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 944: _addedmodules[]: bad array subscript
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
==> Using drop-in configuration file: 'asus.conf'
==> Starting build: '6.7.5-artix1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
/usr/lib/initcpio/functions: line 561: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 561: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 596: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 596: _addedmodules[]: bad array subscript
==> ERROR: module not found: ''
/usr/lib/initcpio/functions: line 944: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 944: _addedmodules[]: bad array subscript
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-zen -g /boot/initramfs-linux-zen.img
==> Using drop-in configuration file: 'asus.conf'
==> Starting build: '6.7.5-zen1-1-zen'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
/usr/lib/initcpio/functions: line 561: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 561: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 596: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 596: _addedmodules[]: bad array subscript
==> ERROR: module not found: ''
/usr/lib/initcpio/functions: line 944: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 944: _addedmodules[]: bad array subscript
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-zen.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-zen -g /boot/initramfs-linux-zen-fallback.img -S autodetect
==> Using drop-in configuration file: 'asus.conf'
==> Starting build: '6.7.5-zen1-1-zen'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
/usr/lib/initcpio/functions: line 561: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 561: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 596: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 596: _addedmodules[]: bad array subscript
==> ERROR: module not found: ''
/usr/lib/initcpio/functions: line 944: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 944: _addedmodules[]: bad array subscript
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-zen-fallback.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly
(14/24) Reloading system bus configuration...
 * Reloading D-BUS messagebus config ... [ ok ]
(15/24) Warn about old perl modules
(16/24) Updating fontconfig cache...
(17/24) Updating 32-bit fontconfig cache...
(18/24) Probing GDK-Pixbuf loader modules...
(19/24) Compiling GSettings XML schema files...
(20/24) Probing GTK3 input method modules...
(21/24) Updating icon theme caches...
(22/24) Updating GTK4 module cache...
(23/24) Updating the info directory file...
(24/24) Updating the desktop file MIME type cache...

and when running sudo grub-mkconfig -o /boot/efi/grub I got
Code: [Select]
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/artix/theme.txt
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot:  intel-ucode.img amd-ucode.img initramfs-linux-zen-fallback.img
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot:  intel-ucode.img amd-ucode.img initramfs-linux-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
/usr/bin/grub-mkconfig: line 316: /boot/efi/grub: Is a directory

I am not sure what all of this means. I am particularly worried about the bad array subscript things that it was complaining about in the update.  And also, I am worried about restarting or shutting down and then turning on the computer and having an unusable computer.  What steps can I take to handle this.  I am looking up solutions of course ,but if anybody has a clear idea of what is this I will be very thankful for any help you can provide.

Re: Strange Messages when updating kernels with pacamn SUY

Reply #1
Code: [Select]
sudo mkinitcpio -vp linux
Will provide verbose output.
Which may or may not help narrow it down ?

Re: Strange Messages when updating kernels with pacamn SUY

Reply #2
+1 to @gripped 's suggestion, although just from the output you posted there are a couple possible issues

...
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
...

Possibly not related - the consolefont module won't work if you don't set a font, generally it's safe to remove this module entirely unless you want a special font at boot

...
==> ERROR: module not found: ''
...

Possibly related - a missing module could definitely mess up the HOOKS array. Check your mkinitcpio.conf for typos, or additionally paste it here if you want a second opinion.

Re: Strange Messages when updating kernels with pacamn SUY

Reply #3
Hey guys! I am very sorry I abandonded this thread. Things happened IRL and I just didn't log back... I ended up updating and there were no further issues. But the messages remain. I don't like having such message on my system, so I will share what I could find:

Code: [Select]
sudo mkinitcpio -vp linux
gave me some errors like
Code: [Select]
    adding module: asus-nb-wmi (/lib/modules/6.9.2-artix1-1/kernel/drivers/platform/x86/asus-nb-wmi.ko.zst)
/usr/lib/initcpio/functions: line 1125: _addedmodules[]: bad array subscript
/usr/lib/initcpio/functions: line 1125: _addedmodules[]: bad array subscript

And regarding the mkinitcpio.conf file, this is what I have
Code: [Select]
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block keyboard keymap consolefont resume filesystems fsck"

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used. 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=()

So, where should I go from here?

Re: Strange Messages when updating kernels with pacamn SUY

Reply #4
Code: [Select]
==> Using drop-in configuration file: 'asus.conf'
Did you try to delete this file?

Re: Strange Messages when updating kernels with pacamn SUY

Reply #5
Here's a related thread, the last post is especially interesting.
From the Arch wiki:
Quote
Preset files created by mkinitcpio before Version 36 set the variable ALL_config, which prevents drop-in configuration files from being loaded. To enable drop-in files, comment out the line ALL_config="/etc/mkinitcpio.conf" in older preset files.
So, try editing the asus.conf file (or, as mentioned, deleting it, though make a backup first). It should be in /etc/mkinitcpio.conf.d/ or in /etc/mkinitcpio.d/

Re: Strange Messages when updating kernels with pacamn SUY

Reply #6
Code: [Select]
==> Using drop-in configuration file: 'asus.conf'
Did you try to delete this file?
I have not deleted the file, no. Not exactly sure why I would do that.
But regarding
Here's a related thread, the last post is especially interesting.
From the Arch wiki:
Quote
Preset files created by mkinitcpio before Version 36 set the variable ALL_config, which prevents drop-in configuration files from being loaded. To enable drop-in files, comment out the line ALL_config="/etc/mkinitcpio.conf" in older preset files.
So, try editing the asus.conf file (or, as mentioned, deleting it, though make a backup first). It should be in /etc/mkinitcpio.conf.d/ or in /etc/mkinitcpio.d/
The ALL_CONFIG line is already commented out, for example I have this in the linux.preset file:
Code: [Select]
# mkinitcpio preset file for the 'linux' package

#ALL_config="/etc/mkinitcpio.conf"
ALL_kver="/boot/vmlinuz-linux"

PRESETS=('default' 'fallback')

#default_config="/etc/mkinitcpio.conf"
default_image="/boot/initramfs-linux.img"
#default_options=""

#fallback_config="/etc/mkinitcpio.conf"
fallback_image="/boot/initramfs-linux-fallback.img"
fallback_options="-S autodetect"
and same for zen linux
Code: [Select]
# mkinitcpio preset file for the 'linux-zen' package

#ALL_config="/etc/mkinitcpio.conf"
ALL_kver="/boot/vmlinuz-linux-zen"

PRESETS=('default' 'fallback')

#default_config="/etc/mkinitcpio.conf"
default_image="/boot/initramfs-linux-zen.img"
#default_options=""

#fallback_config="/etc/mkinitcpio.conf"
fallback_image="/boot/initramfs-linux-zen-fallback.img"
fallback_options="-S autodetect"

 

Re: Strange Messages when updating kernels with pacamn SUY

Reply #7
Ah I forgot to add the mkinitcpio.conf.pacnew file, in case it's relevant
Code: [Select]
# 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=()

# 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 <hook name>' 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  you MUST include the
#    usr and fsck hooks.
HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block filesystems fsck)

# 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"