Hey! Since i ran a dnf update earlier today my VMs with Rawhide and 36 Beta Frozen, does not boot with Kernel 5.18-rc0 (not sure what the problem is but they boot with Kernel 5.17 just fyi)
5.18-rc0 is kernel of rawhide , not F36 Beta , on F36 you should get kernel 5.17.1
Have the same problem with 5.18-rc1 in rawhide
Still broken with todays compose
Still broken with todays 10th April composehttps://cdimage.ubuntu.com/daily-live/20220409/jammy-desktop-arm64.manifest
Linux vmdevf36.local 5.18.0-0.rc1.20220408git1831fed559732b1.20.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Apr 8 16:16:01 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux boots for me on F36 [2] but without logging and with a gap of 36 seconds or more [1] seems it is "detected fb_set_par" ? [1] [ 16.709503] daemon-init (1056) used greatest stack depth: 11760 bytes left [ 52.761659] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel. (...) [ 65.118481] detected fb_set_par error, error code: -22 [2] dnf --disablerepo='*' --enablerepo=rawhide update "kernel*"
(In reply to Sergio Basto from comment #5) > Linux vmdevf36.local 5.18.0-0.rc1.20220408git1831fed559732b1.20.fc37.x86_64 > #1 SMP PREEMPT_DYNAMIC Fri Apr 8 16:16:01 UTC 2022 x86_64 x86_64 x86_64 > GNU/Linux > boots for me on F36 [2] but without logging and with a gap of 36 seconds or > more [1] seems it is "detected fb_set_par" ? > > [1] > [ 16.709503] daemon-init (1056) used greatest stack depth: 11760 bytes left > [ 52.761659] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel. > (...) > [ 65.118481] detected fb_set_par error, error code: -22 > > [2] > dnf --disablerepo='*' --enablerepo=rawhide update "kernel*" Thanks that is helpful. This seems to be a regression in the vmwgfx driver. I assume that if you add "nomodeset" to the kernel commandline, or if you change the virtual GPU to VboxSVGA that the VM will boot with 5.18-rc# properly then?
@Hans de Goede: yeah switching it to VboxSVGA makes it work
seems gdm, does not like it for GNOME however (but worked on the VMs without X/Wayland)
I've taken some time today to work on fixing this and I've posted a patch fixing the vmwgfx issue upstream: https://lore.kernel.org/dri-devel/20220509110425.165537-1-hdegoede@redhat.com/ hopefully upstream will pick this up before 5.18.0 is released, if not then we can add it as a downstream patch in Fedora before we push 5.18.y kernel updates to F35 and F36.
with kernel-5.18.0-0.rc7 is fixed , closing , thank you