All right, thanks for pointing that out.
Now I’d like to make the X11 properly work also in the future — I see the old vmware config (90-mhwd.conf) is still pointing to “nowhere” now, because of my renaming the file to old-vmwareconf.20250728:
cd /etc/X11 && tree
.
├── mhwd.d
│ └── old-vmwareconf.20250728
├── xinit
│ ├── xinitrc
│ ├── xinitrc.d
│ │ ├── 40-libcanberra-gtk-module.sh
│ │ ├── 50-systemd-user.sh
│ │ └── 80xapp-gtk3-module.sh
│ └── xserverrc
└── xorg.conf.d
├── 00-keyboard.conf
└── 90-mhwd.conf -> /etc/X11/mhwd.d/vmware.conf
5 directories, 8 files
… and it shows also a warning:
mhwd-gpu --status
:: status
warning: could not find '/etc/X11/xorg.conf.d/90-mhwd.conf'!
So what can I do to fix this properly?
Edit: I continued as follows:
-
I removed the broken symlink
rm --interactive /etc/X11/xorg.conf.d/90-mhwd.conf -
reinstalled the kernel (switched to 6.12 … then
mhwd-kernel -i linux615… then switched back to 6.15.7-1), to see if some X11 mhwd config in the process would be created, no/etc/X11/mhwd.d/vmware.confwas created -
investigating further hardware drivers (https://wiki.manjaro.org/index.php/Manjaro_Hardware_Detection_Overview) with
mhwd --listinstalled --detailit shows the installed drivervideo-vmware2017.03.12, but listing all available drivers (for 6.15.7-1) bymhwd --listallthere are a lot, but novideo-vmware— so I wonder if the installed drivervideo-vmware2017.03.12 is a relict, and what driver should be the right one (and if that is the reason why the/etc/X11/mhwd.d/vmware.confwas created and that X11-log reports that it is still looking for modulevmware):mhwd --listinstalled --detail # NAME: video-vmware # ATTACHED: PCI # VERSION: 2017.03.12 # INFO: X.org vmware video driver. # PRIORITY: 1 # FREEDRIVER: true # DEPENDS: - # CONFLICTS: - # CLASSIDS: 0300 # VENDORIDS: 15admhwd --listall > All PCI configs: -------------------------------------------------------------------------------- NAME VERSION FREEDRIVER TYPE -------------------------------------------------------------------------------- network-rt3562sta 2013.12.07 true PCI network-r8168 2023.09.12 true PCI network-broadcom-wl 2018.10.07 false PCI network-slmodem 2013.12.07 true PCI video-linux 2024.05.06 true PCI video-rendition 2020.01.18 true PCI video-voodoo 2017.03.12 true PCI video-vesa 2017.03.12 true PCI video-modesetting 2020.01.13 true PCI video-hybrid-amd-nvidia-470xx-prime 2023.03.23 false PCI video-hybrid-amd-nvidia-prime 2025.01.13 false PCI video-nvidia-390xx 2023.03.23 false PCI video-nvidia-470xx 2023.03.23 false PCI video-hybrid-intel-nvidia-390xx-bumblebee 2023.03.23 false PCI video-virtualmachine 2024.05.06 true PCI video-hybrid-intel-nvidia-prime 2025.01.13 false PCI video-hybrid-intel-nvidia-470xx-prime 2023.03.23 false PCI video-s3 2020.01.18 true PCI video-sisusb 2020.01.18 true PCI video-nvidia 2025.01.13 false PCI -
so should the
video-vmware2017.03.12 be replaced by another proper available video-something-driver? Or is there an automatic way of reinstalling some package to clean up the “mess”?