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
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.
May You please tell us more about your filesystem? Do You confirm it use ext4?
If yes, the last mkinitcpio.conf form for your system with parentheses instead of quotes and some improvements will be that one :
# 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)
#
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr and fsck hooks.
HOOKS=(base udev autodetect modconf kms block keyboard keymap consolefont plymouth filesystems fsck)
# 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=(zstd)
# COMPRESSION_OPTIONS
# Additional options for the compressor
COMPRESSION_OPTIONS=(-T0)
# MODULES_DECOMPRESS
# Decompress kernel modules during initramfs creation.
# Enable to speedup boot process, disable to save RAM
# during early userspace. Switch (yes/no).
MODULES_DECOMPRESS=(yes)
Then regenerate initramfs with mkinitcpio -P
If You have an error regarding consolefont, You can remove it from the HOOKS.
Yup, that sure seems like proverbial bs, given that this elusive pacnew file has yet to be confirmed to even exist. I haven’t seen it, and clearly neither has anyone else (at least, from the sampling of those who posted).
df -T /
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda1 ext4 146G 48G 91G 35% /
[quote="Delor3an91, post:104, topic:151904"]
If yes, the last **mkinitcpio.conf** form for your system with **parentheses instead of quotes** and some improvements will be that one :
[/quote]
Thanks, this is way over my head. I suppose I haven’t done too bad since migrating from $MS but I realized a few updates back that I’m barely scratching the surface of Linux and have studying to do (as was pointed out in manjaro threads at that time).
Thanks, I have 3 manjaro systems that are all like this, and as a noob I haven’t altered any files. I have one system that is pretty basic, what I usually do is update that first then go to the other 2 if success.
My logic in posting here was wondering why I have that /etc/mkinitcpio.conf.d folder, thinking there must be other people (noobs) who also have “d” and no /etc/mkinitcpio.conf. I am surprised there has been no mention of the “d”. I searched the web as well.
thanks, over my head, see above EDIT: I have 5 kernels installed, and a preset for each one, but they’re in a folder called mkinitcpio.d There’s that d again. In /etc/, those are the only 2 mkinitcpio folders I see, each ending in “d”.
Why do You have 5 kernels installed? Is it necessary?
I suggest You to keep the 2 last LTS linux66 and linux61 and remove the others.
In the future, I suggest You to use the last avaible kernel avaible and keep the last LTS as a backup solution.
You can remove linuxXX kernels with pacman -Run linuxXX that way, presets wil be deleted too. Or You must delete them later manually.
XX is the kernel version. For examples : linux515 is Linux 5.15 and linux65 Linux6.5
You must have one preset installed by kernels installed. So in your case, You must have five ones.
You can easily install (pacman -S) and remove (pacman -R) kernels/graphic drivers/some configurations with manjaro-settings-manager GUI.
To find and removeorphanspackages that are no more necessary :
pacman -Run $(pacman -Qdtq)
Use it several times until nothing is propose to delete, reboot and your system must be smoother and faster
In linux, something.d is a directory/folder, containing complementing or overriding config files for the something process or something.conf confiig file.
I had a few snapshots of that VM and restored it back to Sep - the mkinitcpio.conf.pacnew I see was created on 08 Sep, so I stand corrected. This should be right after [Stable Update] 2023-08-29.
If some people switched to another branch for a time, and switched back, that might potentially explain why not everyone has it, I suppose. Also, if the .conf file had been manually edited, that would also cause a new .pacnew to exist (because it differed from the expected checksum). Curious, nonetheless.
I confirm that both my Manjaro installs on the PC had a mkinitcpio.conf.pacnew dated Sep 2023. I only just merged them and regenerated the images before installing this present batch of Stable updates.
I have manually edited my mkinitcpio.conf file to correct the issue, so I expect a pacnew file will now be generated at next update (because the .conf file differs). It will be interesting to see whatever the content of that .pacnew file might be.
