Several of the packages no longer exist.
To ensure no noise - please remove all packages listed by pacman -Qm as they are all unsupported
The easy method is
sudo pacman -Rns $(pacman -Qqm)
When your issue has been solved you can rebuild the ones required for your day-to-day operation.
remove this:
rm /etc/X11/xorg.conf
uninstall these:
pacman -R cuda opencl-nvidia
post also output from:
cat /etc/mkinitcpio.conf
Will the settings be gone as well? Because Coolercontrol and freetube settings are extensive and I hate to have to set them all new again.
[manjaro /]# pacman -R cuda opencl-nvidia
checking dependencies...
:: ocl-icd optionally requires opencl-driver: packaged opencl driver
:: openmpi optionally requires cuda: cuda support
:: openucx optionally requires cuda: for CUDA support
Packages (2) cuda-12.9.1-1 opencl-nvidia-575.64-1
Total Removed Size: 7273.92 MiB
:: Do you want to remove these packages? [Y/n] y
:: Processing package changes...
(1/2) removing cuda [####################################] 100%
(2/2) removing opencl-nvidia [####################################] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Refreshing PackageKit...
Error connecting: Could not connect: No such file or directory
error: command failed to execute correctly
[manjaro /]# cat /etc/mkinitcpio.conf[/quote]
# 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 kms block keyboard keymap consolefont 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=()
# 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"
Sorry I cant seem to get the format right for the last one
No - they are stored locally in your user’s home.
try removing them one at a time… but the most important thing was to remove the xorg.conf…
xorg is gone,
Btw I just posted the result because of the packagekit error, I guess I should uninstall that as well, as suggested before.
i think it uninstalled it … so reboot and see… if it doesnt work post logs:
journalctl -b-1 -p5 --no-pager
sudo dmesg -l err,warn,emerg,alert,crit
Thank you so much!
I am sure removing other stuff as well was important too but this finally got me into Manjaro again.
I luckily did not have to remove all the packages I needed. Although most of them I dont even know what they are for. except for proton-ge-custom-bin. That way someone showed me howto start games without Steam.
I also would like to thank everyone who has tried to help me with this issue!!! Every little bit helped, if even I have learned a thing or two, or have a thread to fall back to if I run into other issues.
Special thanks to @dmt who stuck with this thread from the start and @brahma.
I am still at odds if I should remove those packages (at least the ones I dont know I need) now that I’m into Manjaro again, fearing that it would brake something else.
open pamac gui, select installed, and under foreign, look for packages that dont have official repositories or AUR under their name, those who are empty are safe to remove
Extra firmware for Manjaro manjaro-firmware, manjaro-hotfixes, manjaro-settings-manager-kcm are not important?
no, those are dead packages, all packages that are empty are dead and safe to remove … check also under orphans…
The qt5-based module to integrate the Manjaro Settings Manager into the Plasma System Settings. Given that Plasma is qt6-based now, this integration no longer works, and thus this package was dropped from the repos.
These two have been dropped from the repos because they no longer serve a purpose. Whatever they were offering is now being provided by other packages.
looks good of course. @brahma has done an excellent job of finding the problem.
the only thing left over from nvidia is options nouveau modeset=1, but this has no effect because the driver is not loaded.
I’m a bit confused that your ls /etc/modprobe.d has no result. theoretically there should be a file in the directory that contains the corresponding line.
If you stumble across it somewhere, you can delete the line.
That seems to be from the live USB that was used for the chroot.
To set up a chroot like the one we’re talking about, we do something like this:
/proc, /dev, /sys to the appropriate places in the target filesystemThe kernel and it’s options are from the already running system. That’s why inxi picked it up but it doesn’t seem to be in the target system.
https://wiki.archlinux.org/title/Chroot#Using_chroot
Here’s an example from my system. 
# options from inxi in running system
rw quiet splash udev.log_priority=3
# options from inxi in chrooted system
rw quiet splash udev.log_priority=3
# options from /etc/default/grub in running system
quiet splash udev.log_priority=3
# options from /etc/default/grub in chrooted system
sysrq_always_enabled=1 udev.log_priority=3
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.