*** This bug is a duplicate of bug 1832138 ***
https://bugs.launchpad.net/bugs/1832138
Only when using v4.15, if I use the hwe kernel 4.18 on Bionic it passes.
I have strong belief this kernel fix to be a potential good candidate,
but I need to run a bisection to confirm my assumption :
commit 140bcaa23a1c37b694910424075a15e009120dbe
Author: Thomas Hellstrom
Date: Thu Mar 8 10:07:37 2018 +0100
drm/vmwgfx: Fix black screen and device errors when running without
fbdev
When we are running without fbdev, transitioning from the login screen to
X or gnome-shell/wayland will cause a vt switch and the driver will disable
svga mode, losing all modesetting resources. However, the kms atomic state
does not reflect that and may think that a crtc is still turned on, which
will cause device errors when we try to bind an fb to the crtc, and the
screen will remain black.
Fix this by turning off all kms resources before disabling svga
mode.
Cc:
Signed-off-by: Thomas Hellstrom
Reviewed-by: Sinclair Yeh
** This bug has been marked a duplicate of bug 1832138
Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832903
Title:
18.04.2 login screen doesn't work if it uses 'wayland' and if video
kernel driver is 'vgwfx' kernel driver
Status in gdm3 package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Status in wayland package in Ubuntu:
New
Bug description:
After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the
login screen doesn't work if 'Wayland' is in use (default) and if
video kernel driver is 'vgwfx'.
It looks like the login screen got stuck, doesn't exit, and doesn't
fallback to 'x11' by itself in case of failure.
Workaround:
- Access the machine via ssh or any other recovery approaches.
- Force the login screen to use x11:
File: /etc/gdm3/custom.conf
[daemon]
# Uncoment the line below to force the login screen to use Xorg
WaylandEnable=false
I tried to reproduce the behaviour on my personal laptop, KVM guest,
... without success.
So far it is only reproducible when the 'vgwfx' driver is in use in
combination with Wayland.
lspci -nnvvv
00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405]
(prog-if 00 [VGA controller])
Subsystem: VMware SVGA II Adapter [15ad:0405]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR-
Capabilities: [44] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: vmwgfx
Kernel modules: vmwgfx
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832903/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp