If you can ping the VM and SSH in, then your VM's starting. Just not quite as fully as it does with the previous kernels, which is weird.
Do you normally boot into a Gnome or KDE session (graphical.target) for login? Or do you just get to multi-user.target and login through a text-based console?
Might be worth looking into the changelog for the kernel package, see if there's anything obvious between this current release and your last previously fully working version? e.g.:
root@fedora:~# rpm -q --changelog kernel-6.10.6-200.fc40.x86_64 | head -50
* Mon Aug 19 2024 Justin M. Forbes <jforbes@xxxxxxxxxxxxxxxxx> [6.10.6-0]
- Add to BugsFixed (Justin M. Forbes)
- selinux: revert our use of vma_is_initial_heap() (Paul Moore)
- Linux v6.10.6
* Wed Aug 14 2024 Justin M. Forbes <jforbes@xxxxxxxxxxxxxxxxx> [6.10.5-0]
- Revert "ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error" (Niklas Cassel)
- Linux v6.10.5
* Sun Aug 11 2024 Justin M. Forbes <jforbes@xxxxxxxxxxxxxxxxx> [6.10.4-0]
- wifi: brcmfmac: cfg80211: Handle SSID based pmksa deletion (Janne Grunau)
- New config for 6.10.3 (Justin M. Forbes)
- Linux v6.10.4
root@fedora:~# rpm -q --changelog kernel-6.10.6-200.fc40.x86_64 | head -50
* Mon Aug 19 2024 Justin M. Forbes <jforbes@xxxxxxxxxxxxxxxxx> [6.10.6-0]
- Add to BugsFixed (Justin M. Forbes)
- selinux: revert our use of vma_is_initial_heap() (Paul Moore)
- Linux v6.10.6
* Wed Aug 14 2024 Justin M. Forbes <jforbes@xxxxxxxxxxxxxxxxx> [6.10.5-0]
- Revert "ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error" (Niklas Cassel)
- Linux v6.10.5
* Sun Aug 11 2024 Justin M. Forbes <jforbes@xxxxxxxxxxxxxxxxx> [6.10.4-0]
- wifi: brcmfmac: cfg80211: Handle SSID based pmksa deletion (Janne Grunau)
- New config for 6.10.3 (Justin M. Forbes)
- Linux v6.10.4
That might at least narrow down the likely problem space.
On Tue, 27 Aug 2024 at 13:23, Maarten Hoes <hoes.maarten@xxxxxxxxx> wrote:
I'm running VMware Workstation 17.5.2 on Windows 11.
I don't have '3D Acceleration' enabled (like suggested in the reddit post you linked to), it's already off, so that is not the solution for me.
I'm not sure how to go about booting into text-only mode; I've run 'sudo systemctl set-default multi-user.target', would that be the way, or is there something better to achieve that ?
When booting with '6.10.6-200.fc40', I get a blank (black) screen, but: I can ping the vm and ssh into it. (sorry I didn't try this earlier, I just assumed the system was hung without verifying, but you know what happens when we assUme).
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
-- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue