[Stable Update] 2023-11-21 - Systemd, Gamescope-Plus, KDE Frameworks, Wine, Pipewire, Thunderbird

Erik politely asked users that were not actively participating to leave the channel. The choice was up to you. :wink:

He sent me the same PM, by the way.

1 Like

Maybe it is time for the manjaro developers to take action and code/fork/find another installer, because right now, they lose control of their own distro. It does not matter what you put in the ISO if something else lands on the hard drive on install. And stuff like /etc/fstab and /etc/mkinitcpio.conf seems pretty critical to be ignored. I wonder what other surprises are there and what will be the next discovery…

You’re making absolutely no sense. What do you think Calamares is doing? It’s just a graphical installer. All settings are determined by default packages and settings in the ISO profiles.

I didn’t say that he wasn’t polite, but the reason he gave me was not that I wasn’t active in there. He explicitly stated that the channel was only for calamares developers.

Well, that was the point of the PMs. Someone invited us and later Erik decided to focus the channel in that regard. There was no offense toward anyone he asked to leave.

I just checked and wanted to add this for completeness. I’ve installed Manjaro from the .iso file:
manjaro-gnome-22.0.3-230213-linux61.iso.

My mkinitcpio.conf file is a strange mix of double quotes and parantheses:

MODULES=""
…
BINARIES=()
…
FILES=""
…
HOOKS="base udev …"

The rest is all commented out including the “Compression” section below the HOOKS. I also checked again with sudo find / -name "mkinitcpio.conf.pacnew" but nothing is found.

After following this discussion I’m still not 100% sure if I’ll run into any problems with this update or if I have to do something about the outdated .conf file but as far as I understand the update should be running fine because of the existing ‘base’ hook.

You will be fine for the update. Yep, that is how it really is - a mix of both.

But thank you about the example, i guess that saves me the trouble of installing fresh in VM just to prove a point.
Lets not blame Calamares then, let us just say the fact is, between the ISO and the installed OS some config files magically change filling with deprecated stuff. I am sure @Yochanan can explain it better.

p.s. i also wondered why EVERY compression method is commented out…and somehow still gzip image is generated.

1 Like

I confirm that the error is only generated for kernel 5.15 and not for 6.1. Also not related to the consolefont warning message.
In my case, despite the 5.1 kernel error, my system boots fine with this kernel and of course with 6.1.

(10/17) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-5.15-x86_64 -g /boot/initramfs-5.15-x86_64.img --microcode /boot/amd-ucode.img --microcode /boot/intel-ucode.img
==> Starting build: '5.15.138-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.15-x86_64.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-5.15-x86_64 -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect --microcode /boot/amd-ucode.img --microcode /boot/intel-ucode.img
==> Starting build: '5.15.138-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-5.15-x86_64-fallback.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux61.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.1-x86_64 -g /boot/initramfs-6.1-x86_64.img --microcode /boot/amd-ucode.img --microcode /boot/intel-ucode.img
==> Starting build: '6.1.62-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.1-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux61.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.1-x86_64 -g /boot/initramfs-6.1-x86_64-fallback.img -S autodetect --microcode /boot/amd-ucode.img --microcode /boot/intel-ucode.img
==> Starting build: '6.1.62-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.1-x86_64-fallback.img'
==> Image generation successful
error: la orden no se ejecutó correctamente

Hi @r0nin

I suggest You to install linux66 as it it is the last LTS kernel and remove linux515 with pacman -Run linux515

Wish You well

1 Like

Looks like Calamares issue to me. This code is replacing existing HOOKS line with one surrounded by quotes… and any other line it touches gets quoted too.

7 Likes

Did you try this: Unable to boot after last update - #26 by bassamanator

7 Likes

Thanks, that solves the problem !

I had the same problem with plasma-x11 and and also plasma-wayland on my notebook.

For me helped the reset of the local mime directory from @tommetomme described here:

2 posts were split to a new topic: Spotify doesn’t work for me anymore

Thank you for this update. No new issues evolved after this update.
The known KDE Powerdevil bug from last time (476375 – Powerdevil fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds)
and again on my laptop, KDE System Monitor crashes when I change the page, which was also there once before and solved itself after a few or more than a few boots last time.

Concerned about the base hook requirement known issue mentioned above as I don’t have an /etc/mkinitcpio.conf file folder, only /etc/mkinitcpio.conf.d and there’s nothing in it. I believe my system was installed April 2020 and I have never modified any of these files. Running kernel 6.1.62-1

It is not stable update related so you should have startet another topic…
I do not know how your system is working without these files, it should break at the next kernel update…
here is a linux61.preset to put in that empty folder

# mkinitcpio preset file for the '6.1-x86_64' package

#ALL_config="/etc/mkinitcpio.conf"
ALL_kver="/boot/vmlinuz-6.1-x86_64"
ALL_microcode=(/boot/*-ucode.img)

PRESETS=('default' 'fallback')

#default_config="/etc/mkinitcpio.conf"
default_image="/boot/initramfs-6.1-x86_64.img"
#default_uki="/efi/EFI/Linux/manjaro-6.1-x86_64.efi"
#default_options="--splash /usr/share/systemd/bootctl/splash-manjaro.bmp"

#fallback_config="/etc/mkinitcpio.conf"
fallback_image="/boot/initramfs-6.1-x86_64-fallback.img"
#fallback_uki="/efi/EFI/Linux/manjaro-6.1-x86_64-fallback.efi"
fallback_options="-S autodetect"

And /etc/mkinitcpio.conf is a file. You can just cat /etc/mkinitcpio.conf to see if it comes up.

Thanks, I thought it was stable update related because I’m not updating due to confusion about that file. I saw your earlier post and ran that command but unsure what it’s telling me.

I’ve been regularly updating this system since installation in 2020. Sorry, that’s all I know, was hoping posting about this would get me through this update. Concerned about that base hook thing.

$ cat /etc/mkinitcpio.conf
# 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=(piix ide_disk reiserfs)
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 block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   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 filesystems"

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

You have it, you will be fine. You probably have the preset files too, they cannot magically disappear. Just check and drop a preset if you really have none.