In very tiny print in the upper left I get
[ OK ] Reached target network-onlin:target - Network is Online.
Starting cockpit-issue.service - Cockpit issue updater service…
[ OK ] Reached target remote-fs.target - Remote File Systems.
Starting httpd.service - The Apache HTTP Server…
Starting rpc-statd-notify.service - Notify NFS peers of a restart…
Starting systemd-user-session.service - Permit User Sessions.
Starting virtlxcd.service - libvirt LXC daemon…
Starting virtvboxd.service - libvirt VirtualBox daemon…
Starting vsftpd.service - VSftpd ftp daemon…
[ OK ] Started rpc-statd-notify.service - Notify NFS peers of a restart.
[ OK ] Finished systemd-user-sessions.service - Permit User Sessions.
[ OK ] Started vsftpd.service - Vsftpd ftp daemon.
[ OK ] Started atd.service - Deferred execution scheduler.
[ OK ] Started crond.service - Command Scheduler.
Starting gdm.service - GNOME Display Manager …
Starting plymouth-quit-wait.servic.d until boot process finishes up…
Starting vncserver@:1.service - Remote desktop service (VNC)…
Starting vncserver@:1\x0a.service - Remote desktop service (VNC)…
[ OK ] Finished cockpit-issue.service - Cockpit issue updater service.
[ OK ] Started virtlxcd.service - libvirt LXC daemon.
[ OK ] Started gdm.service - GNOME Display Manager.
[FAILED] Failed to start vncserver@:1\x0a.s.ice - Remote desktop service (VNC).
See ‘systemctl status “vncserver@:1\\x0a.service”’ for details.
[ OK ] Started virtvboxd.service - libvirt VirtualBox daemon.
And now I can type but I do not have a shell and F1, F2, F3 alternate screens do not work.
Yes, hold down F1 during boot will go to the BIOS as expected.
What should I do now?