Black screen after system update (no graphical interface, XOrg failed to load module ‘vmware’)

Hey there!

After a system update, all I get is a black screen. I set up Manjaro on VMWare Workstation Player 17 as a guest system, and everything was working fine until now. sudo mhwd-kernel -li reports: currently running: 6.6.94-1-MANJARO (linux66)

To see what happens during bootup, I can initially change the GRUB entry with ESC or F2 to display the processes on the screen where it gets stuck, and with the GRUB entry from ... rw quiet ... (= default, i.e. without any text messages on the screen) to boot stage 3 ... rw 3 ... (with text messages only in the command line system) or 5 ... rw 5 ... (with text messages in the graphical interface system) and reading some system logs, the following came to light, whereby the main cause seems to be that the graphical interface system is not being set up at all and aborts with an error:

  1. journalctl --priority=warning..crit --no-pager --boot=-1 > /path/to/readable/directory/journalctl_02.log – System warnings, etc. showed “EXT4-fs (sda1): warning: mounting fs with errors, running e2fsck is recommended” – I had initially repaired this with Live Manjaro USB (… manjaro-chroot -a, mhwd-kernel --listinstalled, umount /dev/sda1, test first: e2fsck -n /dev/sda1, then repairing: e2fsck /dev/sda1 …) was successful, the graphical user interface (sddm) showed some errors and no longer starts up:
Jul 07 11:13:16 andreas-arch sddm[960]: Failed to read display number from pipe
Jul 07 11:13:16 andreas-arch sddm[960]: Attempt 1 starting the Display server on vt 2 failed
Jul 07 11:13:18 andreas-arch sddm[960]: Failed to read display number from pipe
Jul 07 11:13:18 andreas-arch sddm[960]: Attempt 2 starting the Display server on vt 2 failed
Jul 07 11:13:20 andreas-arch sddm[960]: Failed to read display number from pipe
Jul 07 11:13:20 andreas-arch sddm[960]: Attempt 3 starting the Display server on vt 2 failed
Jul 07 11:13:20 andreas-arch sddm[960]: Could not start Display server on vt 2

The last message on the screen at boot stage 5 is TLP system startup/shutdown and it doesn’t go any further

  1. From the graphics interface system: cat /var/log/Xorg.0.log showed ‘Warning, couldn't open module vmware’ and ‘Failed to load module “vmware” (module does not exist, 0)’:
...
[ 910.093] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[ 910.094] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 910.094] (II) Platform probe for /sys/devices/pci0000:00/0000:00:0f.0/drm/card0
[ 910.095] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 13 paused 0
[ 910.099] (--) PCI:*(0@0:15:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xe8000000/134217728, 0xfe000000/8388608, I/O @ 0x00001070/16, BIOS @ 0x????????/131072
[ 910.099] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 910.099] (II) LoadModule: ‘glx’
[ 910.101] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 910.115] (II) Module glx: vendor="X.Org Foundation"
[ 910.115]     compiled for 1.21.1.18, module version = 1.0.0
[ 910.115]     ABI class: X.Org Server Extension, version 10.0
[ 910.115] (II) LoadModule: ‘vmware’
[ 910.117] (WW) Warning, couldn't open module vmware
[ 910.117] (EE) Failed to load module ‘vmware’ (module does not exist, 0)
[ 910.117] (EE) No drivers available.
[ 910.117] (EE)
Fatal server error:
[ 910.117] (EE) no screens found(EE)
[ 910.117] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
 
[ 910.117] (EE) Please also check the log file at ‘/var/log/Xorg.0.log’ for additional information.
[ 910.117] (EE)
[ 910.120] (EE) Server terminated with error (1). Closing log file.

… and this is where I’m basically stuck :neutral_face: and can’t get any further because I don’t know how to solve the vmware module problem.

I also found that there were some fundamental package changes a few weeks ago Missing xf86-video-vmware in repository (github.com/archlinux/archinstall/issues/3584), but I don’t know which replacement package would provide the right solution.

Can anyone help me or point me in the right direction for further research, or are there any system messages missing that would help me describe the problem in more detail? Thanks for any help.

PS: I rewrote the post in English because we may be able to find a solution faster than on the German page, but I will add the solution to the German page as soon as one is found.

The package xf86-video-vmware was removed from upstream repo and placed in AUR.

 $ pamac info xf86-video-vmware --aur
Name                  : xf86-video-vmware
Version               : 13.4.0-4
Description           : X.org vmware video driver
URL                   : https://xorg.freedesktop.org/
Licenses              : MIT AND X11
Repository            : AUR
Groups                : xorg-drivers
Depends On            : mesa systemd-libs libxext libx11 libdrm glibc
Optional Dependencies : --
Make Dependencies     : xorg-server-devel X-ABI-VIDEODRV_VERSION=25.2
Check Dependencies    : --
Provides              : --
Replaces              : --
Conflicts With        : xorg-server<21.1.1 X-ABI-VIDEODRV_VERSION<25 X-ABI-VIDEODRV_VERSION>=26
Maintainer            : Edu4rdSHL
First Submitted       : ons 11 jun 2025 08:01:08 CEST
Last Modified         : ons 11 jun 2025 08:01:08 CEST
Votes                 : 9
Out of Date           : --

I don’t know the reasoning behind the change…

Yes, that’s right, I don’t know either :wink: … Should I install xf86-video-vmware from AUR, or is there an official replacement solution without xf86-video-vmware?

You could try…

have you tried removing the package xf86-video-vmware?

I found this Broken by upstream mesa deprecation (gallium-xa) (#3) · Issues · Arch Linux / Packaging / Packages / xf86-video-vmware · GitLab which seems to point to mesa.

The discussion is about both vmware workstation/player and virtualbox.

For virtualbox it seems possible to use vboxsvga but since you are using vmware - it could be harder to solve.

//EDIT:

I am thinking that syncing a newer kernel may do the trick - but I have no idea.

You mention nothing of the host nor the version of vmware; need to mention that VMware is largely unsupported.

I have tested VMware on a Manjaro host; creating a new virtual Manjaro Xfce (latest ISO 25.0.4 released on 250623); there is no issues booting; no gpu issue; it work as expected.

  • My host is AMD hardware running Linux 6.15.5 kernel.
  • The guest is using Linux 6.12.34 kernel.

Thanks for your suggestions. What I did so far was

sudo mhwd-kernel -i linux615 # new kernel 6.15.3-1
# and later
yay -S xf86-video-vmware # without success
yay -Rns xf86-video-vmware # remove it

yay -S xf86-video-vmware-git # without success

… it’s still a black screen, I have to look further into the system messages, but I can also see that more people have a similar problem.

I suggest you remove the package xf86-video-vmware as it is obsolete.

If this still doesn’t do it - I suggest removing plymouth from the equation.

Because the topic involves a Virtual Machine, creating a new VM might be worthwhile.

You could, for example, ascertain whether the same scenario might reveal itself in a new installation; and if it doesn’t, the new VM could then be used instead.

The virtual disk of the old installation could be temporarily connected as a secondary disk in the new installation, thereby allowing you to also copy your /home directories to the new VM.

I suggest this only because it can potentially save much time and effort spent on otherwise “repairing” the VM Manjaro installation.

That said, if repairing the VM Manjaro is generally a learning exercise for you, then have at it. :wink:

Regards.

1 Like

@infinite-dao
Just curious:
I’m not a “linux engineer” at all, but I had the exact same “Failed to load module vmware” message in Xorg.0.log after updating last week.
It pointed out I had a config file /etc/X11/mhwd.d/vmware.conf starting with:

Section "Device"
    Identifier  "Device0"
    Driver      "vmware"
	Option      "DRI"    "true"
EndSection

After renaming that file to somthing useless Xserver started after reboot.
There could also be a symlink in /etc/X11/xorg.conf.d/ pointing to a file with the above config section.
Hope this helps.

1 Like

The workaround of renaming /etc/X11/mhwd.d/vmware.conf, which made it unusable, was successful for the time being and got the graphical user interface working again. I don’t know if this is the appropriate solution (in a technical, systemic sense).

What I tried and did, after deciding to remove xf86-video-vmware was:

(1) As user, remove the previously installed package from AUR xf86-video-vmware/xf86-video-vmware-git

yay -Rns xf86-video-vmware-git # remove it again

sudo pacman -Syyu # lots of packages, 10568.59 MB total updates – should be sudo pacman -Syu (a single y), see below

reboot # no success, no graphical user interface

(2) Attempt to rename the X11 configuration file to make it unusable:

cd /etc/X11/mhwd.d/ && mv vmware.conf old-vmwareconf.20250728

reboot # successful, with graphical user interface

In the Manjaro Settings Manager, I subsequently removed kernel linux66 and added an LTS kernel linux612. The VM is currently running linux615 (which is currently 6.15.7-1).

I don’t know how long the file renaming solution (?workaround) will help, since the X11 configuration file may be recreated by mhwd at some point in the future, and the question is with which entries the *.conf is created. The X11 system messages indicate that X11 is still looking for the vmware module but cannot find it and is probably using some other default setting. I wonder how I can determine whether any vmware packages are still installed that will no longer be supported in the future, so that there is no confusion and the black screen does not reappear at some point.

In /var/log/Xorg.0.log, it is still searching for a module vmware

...
[ 6.409] (II) LoadModule: “vmware”
[ 6.410] (WW) Warning, couldn't open module vmware
[ 6.410] (EE) Failed to load module “vmware” (module does not exist, 0)
[ 6.410] (II) LoadModule: “modesetting”
[ 6.410] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 6.413] (II) Module modesetting: vendor="X.Org Foundation"
[ 6.413]     compiled for 1.21.1.18, module version = 1.21.1
[ 6.413]     Module class: X.Org Video Driver
[ 6.413]     ABI class: X.Org Video Driver, version 25.2
...

It appears that only open-vm-tools is installed now:

pacman -Ss vmware
extra/open-vm-tools 6:13.0.0-1 [Installed]
    The Open Virtual Machine Tools (open-vm-tools) are the open source implementation of VMware Tools
extra/xf86-input-vmmouse 13.2.0-2 (xorg-drivers)
    X.org VMWare Mouse input driver

Note that the expected command here is:
sudo pacman -Syu (a single y)

Cheers.

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.conf was created

  • investigating further hardware drivers (Manjaro Hardware Detection Overview - Manjaro) with mhwd --listinstalled --detail it shows the installed driver video-vmware 2017.03.12, but listing all available drivers (for 6.15.7-1) by mhwd --listall there are a lot, but no video-vmware — so I wonder if the installed driver video-vmware 2017.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.conf was created and that X11-log reports that it is still looking for module vmware):

    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:   15ad 
    
    mhwd  --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-vmware 2017.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”?

It should be removed.

There is no packages replacing it.

I have never been involved with mhwd - I just spotted the issue.

As I see from your listing - and verified - the VERSION and INFO properties should have been updated when the xf86-video-vmware dependency was removed - but I didn’t see that and the maintainer merge my change without comments.

I have created a MR to rectify this

All right I try to replace video-vmware 2017.03.12 — reading mhwd (Configure Graphics Cards - Manjaro) I used the automatic detection of driver selection:

# as root/sudo — and 0300 from above is my CLASSID from the info of `mhwd -li -d`
mhwd --auto pci free 0300
# > Using config ‘video-virtualmachine’ for device: 0000:00:0f.0 (0300:15ad:0405) Display controller VMware, Inc. VMWARE0405
# > Installing video-virtualmachine...
#  
# Sourcing /etc/mhwd-x86_64.conf
# Has lib32 support: true
# Sourcing /var/lib/mhwd/db/pci/graphic_drivers/video-virtualmachine/MHWDCONFIG
# Processing classid: 0300
#  
# Sourcing /var/lib/mhwd/scripts/include/0300
# :: Package databases are being synchronized ...
# core is being downloaded ...
# extra is being downloaded ...
# community is being downloaded ...
# multilib is being downloaded ...
#  
# Error: Target not found: xf86-video-vmware
# Warning: open-vm-tools-6:13.0.0-1 is current -- Skipping
# Warning: gtkmm3-3.24.10-1 is current -- Skipping
# Error: pacman failed!
# Error: script failed!
  • …free… or …nonfree… results both in “Error: script failed!” — so somewhere in the mystics of the system it is searching still for xf86-video-vmware, although I removed it, I thought so :thinking:

I guess this is the X11 report what driver it uses now:

inxi -G

Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0
  Display: unspecified server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8 driver: X:
    loaded: modesetting dri: vmwgfx gpu: vmwgfx tty: 212x32
  API: EGL v: 1.5 drivers: swrast,vmwgfx platforms: gbm,surfaceless,device
  API: OpenGL v: 4.5 compat-v: 3.3 vendor: mesa v: 25.1.6-arch1.1 note: console (EGL sourced)
    renderer: SVGA3D; build: RELEASE; LLVM;, llvmpipe (LLVM 20.1.8 256 bits)
  API: Vulkan Message: No Vulkan data available.
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
    wl: wayland-info x11: xdpyinfo, xprop, xrandr

I decided to remove video-vmware 2017.03.12 and replace it.

mhwd  --listall # auflisten verfügbarer Treiber

mhwd  --listinstalled --detail # bereiterstellten Treiber ausführlich beschreiben

# mhwd --auto pci free 0300 # selbtätige Treiberauswahl ergibt Fehler mit Abbruch

mhwd  --remove pci video-vmware

I installed mhwd --install pci video-nvidia … but later removed that (mhwd --remove pci video-nvidia) because of other problems and decided to install video-linux:

mhwd  --install pci video-linux
> Installing video-linux...
Sourcing /etc/mhwd-x86_64.conf
Has lib32 support: true
Sourcing /var/lib/mhwd/db/pci/graphic_drivers/video-linux/MHWDCONFIG
Processing classid: 0300
Sourcing /var/lib/mhwd/scripts/include/0300
Processing classid: 0380
Processing classid: 0302
:: Paketdatenbanken werden synchronisiert …
 core wird heruntergeladen …
 extra wird heruntergeladen …
 community wird heruntergeladen …
 multilib wird heruntergeladen …
Abhängigkeiten werden aufgelöst …
Nach in Konflikt stehenden Paketen wird gesucht …

Pakete (11) lib32-xcb-util-keysyms-0.4.1-2  lib32-vulkan-intel-1:25.1.6-1  lib32-vulkan-nouveau-1:25.1.6-1  lib32-vulkan-radeon-1:25.1.6-1  vulkan-intel-1:25.1.6-1  vulkan-nouveau-1:25.1.6-1  vulkan-radeon-1:25.1.6-1  xf86-video-amdgpu-23.0.0-2  xf86-video-ati-1:22.0.0-2  xf86-video-intel-1:2.99.917+939+g4a64400e-1  xf86-video-nouveau-1.0.18-1

Gesamtgröße des Downloads:              20,74 MiB
Gesamtgröße der installierten Pakete:  128,57 MiB

:: Installation fortsetzen? [J/n] 
:: Pakete werden empfangen …
 lib32-vulkan-intel-1:25.1.6-1-x86_64 wird heruntergeladen …
 vulkan-intel-1:25.1.6-1-x86_64 wird heruntergeladen …
 lib32-vulkan-radeon-1:25.1.6-1-x86_64 wird heruntergeladen …
 vulkan-radeon-1:25.1.6-1-x86_64 wird heruntergeladen …
 lib32-vulkan-nouveau-1:25.1.6-1-x86_64 wird heruntergeladen …
 vulkan-nouveau-1:25.1.6-1-x86_64 wird heruntergeladen …
 xf86-video-intel-1:2.99.917+939+g4a64400e-1-x86_64 wird heruntergeladen …
 xf86-video-ati-1:22.0.0-2-x86_64 wird heruntergeladen …
 xf86-video-nouveau-1.0.18-1-x86_64 wird heruntergeladen …
 xf86-video-amdgpu-23.0.0-2-x86_64 wird heruntergeladen …
 lib32-xcb-util-keysyms-0.4.1-2-x86_64 wird heruntergeladen …
Schlüsselbund wird geprüft …
Paketintegrität wird geprüft …
Paket-Dateien werden geladen …
Auf Dateikonflikte wird geprüft …
Verfügbarer Festplattenspeicher wird ermittelt …
:: Paketänderungen werden verarbeitet …
xf86-video-ati wird installiert …
xf86-video-amdgpu wird installiert …
xf86-video-intel wird installiert …
>>> This driver now uses DRI3 as the default Direct Rendering
    Infrastructure. You can try falling back to DRI2 if you run
    into trouble. To do so, save a file with the following 
    content as /etc/X11/xorg.conf.d/20-intel.conf :
      Section "Device"
        Identifier  "Intel Graphics"
        Driver      "intel"
        Option      "DRI" "2"             # DRI3 is now default 
        #Option      "AccelMethod"  "sna" # default
        #Option      "AccelMethod"  "uxa" # fallback
      EndSection
Optionale Abhängigkeiten für xf86-video-intel
    libxrandr: for intel-virtual-output [Installiert]
    libxinerama: for intel-virtual-output [Installiert]
    libxcursor: for intel-virtual-output [Installiert]
    libxtst: for intel-virtual-output [Installiert]
    libxss: for intel-virtual-output [Installiert]
xf86-video-nouveau wird installiert …
vulkan-intel wird installiert …
Optionale Abhängigkeiten für vulkan-intel
    vulkan-mesa-layers: additional vulkan layers
vulkan-nouveau wird installiert …
Optionale Abhängigkeiten für vulkan-nouveau
    vulkan-mesa-layers: additional vulkan layers
vulkan-radeon wird installiert …
Optionale Abhängigkeiten für vulkan-radeon
    vulkan-mesa-layers: additional vulkan layers
lib32-xcb-util-keysyms wird installiert …
lib32-vulkan-intel wird installiert …
Optionale Abhängigkeiten für lib32-vulkan-intel
    lib32-vulkan-mesa-layers: additional vulkan layers
lib32-vulkan-nouveau wird installiert …
Optionale Abhängigkeiten für lib32-vulkan-nouveau
    lib32-vulkan-mesa-layers: additional vulkan layers
lib32-vulkan-radeon wird installiert …
Optionale Abhängigkeiten für lib32-vulkan-radeon
    lib32-vulkan-mesa-layers: additional vulkan layers
:: Post-transaction-Hooks werden gestartet …
(1/2) Arming ConditionNeedsUpdate...
(2/2) Refreshing PackageKit...
xf86-video-ati: Installations-Grund wurde auf "Ausdrücklich installiert" gesetzt
xf86-video-amdgpu: Installations-Grund wurde auf "Ausdrücklich installiert" gesetzt
xf86-video-intel: Installations-Grund wurde auf "Ausdrücklich installiert" gesetzt
xf86-video-nouveau: Installations-Grund wurde auf "Ausdrücklich installiert" gesetzt
vulkan-intel: Installations-Grund wurde auf "Ausdrücklich installiert" gesetzt
vulkan-nouveau: Installations-Grund wurde auf "Ausdrücklich installiert" gesetzt
vulkan-radeon: Installations-Grund wurde auf "Ausdrücklich installiert" gesetzt
lib32-vulkan-intel: Installations-Grund wurde auf "Ausdrücklich installiert" gesetzt
lib32-vulkan-nouveau: Installations-Grund wurde auf "Ausdrücklich installiert" gesetzt
lib32-vulkan-radeon: Installations-Grund wurde auf "Ausdrücklich installiert" gesetzt
> Successfully installed video-linux

Now the X11 configuration looks as such:

tree /etc/X11/

/etc/X11/
├── mhwd.d
│   ├── nvidia.conf.nvidia-xconfig-original
│   └── 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

5 directories, 8 files

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.