➜ ~ ls -l /usr/lib/libwacom*
lrwxrwxrwx 1 root root 13 Aug 7 05:12 /usr/lib/libwacom.so -> libwacom.so.9
-rw-r--r-- 1 root root 55136 Aug 18 19:18 /usr/lib/libwacom.so.2
-rw-r--r-- 1 root root 55136 Aug 18 19:18 /usr/lib/libwacom.so.2.6.1
lrwxrwxrwx 1 root root 17 Aug 7 05:12 /usr/lib/libwacom.so.9 -> libwacom.so.9.0.0
-rwxr-xr-x 1 root root 55240 Aug 7 05:12 /usr/lib/libwacom.so.9.0.0
➜ ~ pacman -Qo /usr/lib/libwacom*
/usr/lib/libwacom.so is owned by libwacom 2.4.0-1
/usr/lib/libwacom.so.2 is owned by libwacom1 1.12.1-2
/usr/lib/libwacom.so.2.6.1 is owned by libwacom1 1.12.1-2
/usr/lib/libwacom.so.9 is owned by libwacom 2.4.0-1
/usr/lib/libwacom.so.9.0.0 is owned by libwacom 2.4.0-1
➜ ~ sudo pacman -S linux519
warning: linux519-5.19.7-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) linux519-5.19.7-1
Total Installed Size: 184.02 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [#############################################################################] 100%
(1/1) checking package integrity [#############################################################################] 100%
(1/1) loading package files [#############################################################################] 100%
(1/1) checking for file conflicts [#############################################################################] 100%
(1/1) checking available disk space [#############################################################################] 100%
:: Running pre-transaction hooks...
(1/2) Creating Timeshift snapshot before upgrade...
==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
(2/2) Remove upgraded DKMS modules
:: Processing package changes...
(1/1) reinstalling linux519 [#############################################################################] 100%
ldconfig: /usr/lib/libwacom.so.2 is not a symbolic link
:: Running post-transaction hooks...
(1/7) Arming ConditionNeedsUpdate...
(2/7) Updating module dependencies...
(3/7) Install DKMS modules
(4/7) Updating linux initcpios...
call to execv failed (Permission denied)
error: command failed to execute correctly
(5/7) Updating Kernel initcpios for Nvidia-DRM...
(6/7) Refreshing PackageKit...
(7/7) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/tela/theme.txt
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-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.
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
Where does this package come from, AUR? Do you need it? Remove it otherwise. (Or else delete .so.2 and make symbolic link .so.2 → .so.2.6.1)
Perhaps post what other foreign packages you have installed:
pacman -Qm
As for this…
…it looks like some script or something in mkinitcpio.hook is missing +x permission. Did you try reinstalling mkinitcpio?
> Installed PCI configs:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-modesetting 2020.01.13 true PCI
video-hybrid-intel-nvidia-prime 2021.12.18 false PCI
Warning: No installed USB configs!
➜ ~ sudo ls /etc/mkinitcpio.d/*.preset
/etc/mkinitcpio.d/linux515.preset
# mkinitcpio preset file for the 'linux515' package
ALL_config="/etc/mkinitcpio.conf"
ALL_kver="/boot/vmlinuz-5.15-x86_64"
PRESETS=('default' 'fallback')
#default_config="/etc/mkinitcpio.conf"
default_image="/boot/initramfs-5.15-x86_64.img"
#default_options=""
#fallback_config="/etc/mkinitcpio.conf"
fallback_image="/boot/initramfs-5.15-x86_64-fallback.img"
fallback_options="-S autodetect"
# 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 filesystems keyboard 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=()
# 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"
That what has been discussed at least in the last 50 posts. Installing kernels doesn’t create the preset, doesn’t generate the kernel images. At some point with Brama’s help it miraculously worked in chroot and external tools for 5.15, but it wasn’t possible to do it again for other kernels.
His system seems broken completely, and without knowing what he has done to it (like we discover at post 140+ that he was using rEFInd) it seems a waste of time (but maybe it isn’t).
PS: not to be a but come on, in the last posts there are many things asked (not specifically by you) that have already been answered, it is like you (not specifically you) discover the thread and reply without reading it (I know it is 150 messages now but asking the same thing over and over, what Brama already did when trying to solve it, only adds up to the count, and if everyone does that it is a Groundhog Day rehearsal).
Maybe it’s me to blame cuz I created a new topic. He replied to the new topic but the new topic is merged here. Since I can enter the system, is it the best solution to backup important files and reinstall the system? I’ll get lots of time quite soon so I can work on that.
Maybe that’s it then for those replies I was targeting. My bad if so, their bad if not
My personal opinion would be of course backup you data now since it seems your system integrity is not so good, just in case.
I myself would do a clean install at this point because lot of things don’t make sense to me and I wouldn’t know what to do now, but I can’t speak for yourself, make your mind, is it worth, is it interesting for you to try to find the issue and repair it, or not? Both answers are valid.
Honestly a reinstall from fresh ISO is quick, what takes time is configuring the desktop environment settings, installing/removing programs, customizing some advanced stuff, and often the longest, is to import the backed up files back into the freshly installed system. Depending on your “usage” of Manjaro it can be quick (like for me installing configuring and customizing KDE would take 30 minutes max for everything including copying latest ISO to use for install) or take a few hours to reinstall and make it proper for your “usage”.
Yeah configuring the new system is very annoying. I’ll get 7 day off so I have some time for that. I use Manjaro for school work some the cofiguation won’t be too complicated. I think I need to backup some dotfiles since I’m using i3.
Thank you guys so much for trying to help me. And thank @brahma for saving me cuz I have some deadline next week and all the stuff are in Manjaro. I’ll reinstall the system.
but come on, in the last posts there are many things asked (not specifically by you) that have already been answered, it is like you (not specifically you) discover the thread and reply without reading it (I know it is 150 messages now but asking the same thing over and over, what Brama already did when trying to solve it, only adds up to the count, and if everyone does that it is a 
