VMware Fedora 41 black screen after dnf upgrade

[tragic (Alex K)]

Good afternoon! I have Fedora 41 installed on a VMware Workstation 17 with 3D acceleration enabled. After the sudo dnf upgrade --refresh I got a black screen (more details here), I suspected that the error was related to the kernel version. I managed to upgrade the kernel from version 6.11.4-301.fc41.x86_64 to version 6.12.7-200.fc41.x86_64 without dnf upgrade, and machine rebooted successfully. But after executing sudo dnf upgrade --refresh, I get a black screen again. At the same time, I also can’t boot into the previous kernel. Looks like some new packets make system to crash. Has anyone solved a similar problem?

what i tried to do:
-reinstalling new kernel while booting > doesn’t help

[maierh7 (Harald Maier)]

I did a fresh install of Fedora 41 on VMware Workstation 17.6.2 and VMware Fusion 13.6.2. After upgrading from 6.11.4 to 6.12.7 I got the same problem. Upgrading to 6.11.11 works.

[vsert (X Y)]

Similar issue (VM on the kernel version you list) Fedora Gnome Workstation 6.12.4-200.fc41.x86_64 causing VirtualBox VMs to not be able to launch
My guess is the new kernel expects or interacts with the hypervisor (VMWare and Vbox) in a way that they don’t agree on, and halt.

[artu72 (Andrea)]

I have noticed this problem after upgrading from mesa 24.2 to mesa 24.3, and I have solved by downgrading mesa packages. However, I do not use 3D acceleration since it produces artifacts in MS code and some other apps.

[maierh7 (Harald Maier)]

Yupp! “mesa” downgrade to 24.2.4-1 works.

#! /bin/bash

dnf install
mesa-dri-drivers-24.2.4-1.fc41.x86_64.rpm
mesa-filesystem-24.2.4-1.fc41.x86_64.rpm
mesa-libEGL-24.2.4-1.fc41.x86_64.rpm
mesa-libgbm-24.2.4-1.fc41.x86_64.rpm
mesa-libGL-24.2.4-1.fc41.x86_64.rpm
mesa-libglapi-24.2.4-1.fc41.x86_64.rpm
mesa-va-drivers-24.2.4-1.fc41.x86_64.rpm
mesa-vulkan-drivers-24.2.4-1.fc41.x86_64.rpm \

[tragic (Alex K)]

It really works, brother, thank you

user@fedora:~$ uname -r
6.12.7-200.fc41.x86_64
user@fedora:~$ sudo dnf install -y mesa-dri-drivers-24.2.4-1.fc41.x86_64
sudo dnf install -y mesa-filesystem-24.2.4-1.fc41.x86_64
sudo dnf install -y mesa-libEGL-24.2.4-1.fc41.x86_64
sudo dnf install -y mesa-libgbm-24.2.4-1.fc41.x86_64
sudo dnf install -y mesa-libGL-24.2.4-1.fc41.x86_64
sudo dnf install -y mesa-libglapi-24.2.4-1.fc41.x86_64
sudo dnf install -y mesa-va-drivers-24.2.4-1.fc41.x86_64
sudo dnf install -y mesa-vulkan-drivers-24.2.4-1.fc41.x86_64
[sudo] password for user: 
Updating and loading repositories:
Repositories loaded.
Package "mesa-dri-drivers-24.2.4-1.fc41.x86_64" is already installed.

Nothing to do.
Updating and loading repositories:
Repositories loaded.
Package "mesa-filesystem-24.2.4-1.fc41.x86_64" is already installed.

Nothing to do.
Updating and loading repositories:
Repositories loaded.
Package "mesa-libEGL-24.2.4-1.fc41.x86_64" is already installed.

Nothing to do.
Updating and loading repositories:
Repositories loaded.
Package "mesa-libgbm-24.2.4-1.fc41.x86_64" is already installed.

Nothing to do.
Updating and loading repositories:
Repositories loaded.
Package "mesa-libGL-24.2.4-1.fc41.x86_64" is already installed.

Nothing to do.
Updating and loading repositories:
Repositories loaded.
Package "mesa-libglapi-24.2.4-1.fc41.x86_64" is already installed.

Nothing to do.
Updating and loading repositories:
Repositories loaded.
Package "mesa-va-drivers-24.2.4-1.fc41.x86_64" is already installed.

Nothing to do.
Updating and loading repositories:
Repositories loaded.
Package "mesa-vulkan-drivers-24.2.4-1.fc41.x86_64" is already installed.

Nothing to do.
user@fedora:~$ 

[perockwell (Paul Rockwell)]

I’m seeing the same thing after updating a Fedora 41 aarch64 VM running under VMware Fusion. I’m running kernel 6.12.8 and downgrading Mesa packages fixes the issues for me as well.

I suspect that this is going to be an issue for any user of a Fedora VM that’s using the VMware vmwgfx graphics driver. (All VMware hypervisors and perhaps VBox as well because it looks like those reporting issues on VBox VMs also have the vmwgfx driver in the VM).

I saw this problem on Rawhide and suspect that the updated Mesa packages are causing it there as well. Whatever Mesa 24.3 is doing, it’s no longer playing well with the vmwgfx driver like 24.2 did.

Hope the Mesa developers can get a handle on this and work to fix it this sooner rather than later.

[ouilemur (jim_m)]

I created this topic yesterday that I believe is the same issue only with Virtualbox.

Gnome-shell segfault: mesa 24.3.2-1, vbox guest, VMSVGA, fedora 41 workstation

It looks like if I update mesa to the 24.3.2-1 via dnf update, gnome-shell crashes with a segfault. [ 11.666015] gnome-shell[1289]: segfault at 8 ip 00007f592922904f sp 00007ffda61fb9d0 error 4 in libgallium-24.3.2.so[2904f,7f5929201000+1a4a000] likely on CPU 3 (core 3, socket 0) [ 11.666040] Code: 48 89 e5 41 56 41 55 41 54 41 89 f4 53 4c 8b 6f 58 48 89 fb 0f b6 05 81 b9 a3 02 84 c0 0f 84 98 00 00 00 0f b6 05 71 b9 a3 02 <41> 83 7d 08 03 4c 8d 35 25 01 91 02 88 83 68 01 00 00 7e 0e 49 83 T…

If you start a new pseudo terminal (or SSH into the VM if you have the server running), you can verify the segfault in dmesg.

[acamendez]

Hello there,
I´m having the same issue and I´m new using linux (I´m learning).
Right now, I´m using VMware worstation 17 with fedora 41 but after installing critical updates to the machine, after reeboting, I only see black screen.
After reading the solution to run this command:

sudo dnf install -y mesa-dri-drivers-24.2.4-1.fc41.x86_64
it should be fixed, but the part I don´t kno, if I have black screen, how can I run this command.
My guess, it´s to use SHH, but as I mentioned before, I´m pretty new and I have no idea how to set up this.
Could you please so kind to let me know how to do it?

In advance thanks,

[tragic (Alex K)]

While rebooting, when you see “Welcome to GRUB”, press ESC and you will see list of your kernels. Press E on your kernel 12.7, find “rhgb quiet” and write “3” instead of it. If you just erase it, you will see booting process (as text), if you write “3” you will enter the system “under boot”. Something like that (screenshot). Now press Ctrl+X, and if success, you will see command line. Log-in as usual.

Hope it will help you, and good luck in your learning.

[tragic (Alex K)]

still, there are fewer bugs in native systems… although, there are probably enough bugs due to Nvidia drivers.

[acamendez]

Hello Alex,

Thanks for your reply.
I tried to follow your directions, but I cannot see on the screen the GRUB message “Welcome to GRUB”, and see only the curso blinking (see the picture below) and it just sitting in there, doing nothing.

Do you have any other advice?
Thanks,

[acamendez]

Alex, I finally figure out.
Thanks again for your help.

[xhmikosr]

I wonder, has anyone reported the issue? I just hit it on a fresh VM Install using VirtualBox on a Windows machine.

[perockwell (Paul Rockwell)]

There are at least 2 bug reports submitted to the upstream Mesa developers about this problem. Neither have been acknowledged at this time.