Skip to main content

blackscreen mesa xf86-video-vmware

Solving the Blackscreen Issue Caused by Mesa and xf86-video-vmware Drivers on Arch Linux

Arch Linux is loved for its bleeding-edge freshness, supplying you with the latest packages and newest features. But occasionally, this freshness can trigger unexpected issues. Recently, I stumbled into one such scenario—a typical system upgrade caused the dreaded black screen of despair upon booting! After some research, I traced it back to specific driver packages: Mesa and xf86-video-vmware. In this post, I'll guide you through what exactly happened, how the Arch community responded to it, and how I temporarily solved it by preventing these packages from updating.

The Black Screen After "pacman -Syu"

Like any typical Arch user, I ran the routine command to update my system:

sudo pacman -Syu

The command completed successfully, and I rebooted confidently. Unfortunately, confidence quickly turned into panic when I was welcomed by an entirely black screen.

I initially thought this might be a personal miscalculation or a one-off anomaly, but rebooting several times confirmed the issue—completely blank display, no mouse pointer, zero response.

Checking the Arch Community: Reddit to the Rescue

Like any wise Arch Linux user, my next stop after troubleshooting on my own was the friendly Arch Linux subreddit. Lo and behold, it turned out I wasn't alone! Other members of the community had reported exactly the same issue recently.

You can check out the original discussion here:

The Mesa Package (version 1:25.1.1-1) Causes a Black Screen on vmware

Multiple Arch Linux users using VMware virtual machines reported having the black screen issue after updating to Mesa version 1:25.1.1-1 and xf86-video-vmware driver version 13.4.0-4. It became evident that the newer versions of these packages simply didn't play well with VMware graphics virtualization.

The Temporary Solution: Blocking the Packages from Upgrading

The Arch way often involves swift temporary solutions until packages are patched directly by maintainers and developers. In the meantime, to restore system functionality, I decided to ignore upgrades for these two problematic packages temporarily:

IgnorePkg   = xf86-video-vmware mesa

You can implement package blocking by adding the above line to your pacman configuration file located at /etc/pacman.conf. Open it with your favorite editor (I'm using vim here):

sudo vim /etc/pacman.conf

Look for the line that begins with #IgnorePkg, uncomment it (remove the # at the start) if necessary, and add the packages like so:

IgnorePkg   = xf86-video-vmware mesa

Then run a system update again:

sudo pacman -Syu

You should see warnings confirming these packages are being ignored similar to this:

warning: mesa: ignoring package upgrade (1:25.0.5-1 => 1:25.1.1-1)
warning: xf86-video-vmware: ignoring package upgrade (13.4.0-3 => 13.4.0-4)

As you can see, holding back Mesa at version 1:25.0.5-1 and xf86-video-vmware at 13.4.0-3 was exactly the workaround that resolved the black screen catastrophe.

Conclusion

While Arch Linux is a fantastic choice due to its rolling release and fresh software versions, we do encounter occasional blips like this. Thankfully, the community is typically swift to respond and share their knowledge about workarounds and solutions. Until the incompatibility in Mesa and xf86-video-vmware drivers is officially fixed upstream, ignoring package upgrades is our best approach to maintain system usability and avoid dark, frustrating black screens.

Did you encounter the same issue? Or perhaps a different one with Arch upgrades? Let me know! Happy Linux adventures!

Popular posts from this blog

Undefined global vim

Defining vim as global outside of Neovim When developing plugins for Neovim, particularly in Lua, developers often encounter the "Undefined global vim" warning. This warning can be a nuisance and disrupt the development workflow. However, there is a straightforward solution to this problem by configuring the Lua Language Server Protocol (LSP) to recognize 'vim' as a global variable. Getting "Undefined global vim" warning when developing Neovim plugin While developing Neovim plugins using Lua, the Lua language server might not recognize the 'vim' namespace by default. This leads to warnings about 'vim' being an undefined global variable. These warnings are not just annoying but can also clutter the development environment with unnecessary alerts, potentially hiding other important warnings or errors. Defining vim as global in Lua LSP configuration to get rid of the warning To resolve the "Undefined global vi...
Read more

wget maven ntlm proxy

How to make wget, curl and Maven download behind an NTLM Proxy Working on CentOS, behind an NTLM proxy: yum can deal without problem with a NTLM Proxy wget, curl and Maven cannot The solution is to use " cntlm ". " cntlm " is a NTLM client for proxies requiring NTLM authentication. How it works Install "cntlm" Configure "cntlm"  by giving it your credentials by giving it the NTLM Proxy Start "cntlm" deamon (it listens to "127.0.0.1:3128") Configure wget, curl and Maven to use "cntlm" instead of using directly the NTLM Proxy Note: You will have then a kind of 2 stages Proxy : cntlm + the NTLM proxy Configure CNTLM After installing cntlm, the configuration file is in "cntlm.conf". You must have your domain (in the Windows meaning), proxy login and  proxy password. Mine are respectively: rktmb.org, mihamina, 1234abcd (yes, just for the example) You must have you NTLM Proxy Hostnama or IP ...
Read more

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo...
Read more