systemd/hwdb.d/60-seat.hwdb

# This file is part of systemd.
#
# This file lists graphic devices that don't have a DRM driver and fall back to
# a frame-buffer one instead. Since commit 6260d28b8a, frame-buffer devices are
# no more considered as graphical capable.
#
# The matches have the 'fb' prefix to make sure that only the framebuffer
# device, and not the (parent) PCI device, is tagged with 'master-of-seat'.
#
# Allowed properties are:
#    ID_TAG_MASTER_OF_SEAT=1

#########################################
# eXtreme Graphic Innovation (XGI)
#########################################

# Z7/Z9 (XG20 core), a rather ancient graphic chip, doesn't have a DRM driver
# and falls back to vesafb.
fb:pci:v000018CAd00000020*
 ID_TAG_MASTER_OF_SEAT=1

#########################################
# HyperV
#########################################

# HyperV currently doesn't do DRM, hence we need to synthesize for HyperV's fb
# device instead.
fb:pci:v00001414d00005353*
 ID_TAG_MASTER_OF_SEAT=1

#########################################
# Parallels
#########################################

fb:pci:v00001ab8d00004005*
 ID_TAG_MASTER_OF_SEAT=1
login: XGI Z7/Z9 (XG20 core) graphic chip requires master-of-seat to be set This graphic chip doesn't have a DRM driver and fall back to vesa-framebuffer driver. Without this patch, users of such chip suddenly see their GUI broken without any indication or reason of what happened (no error message). Hence this regression is near to impossible to troubleshoot for end users. Such case was reported https://bugzilla.opensuse.org/show_bug.cgi?id=1187154. Rather than adding another exception in the udev rules to deal with such HWs, they instead get their own hwdb file '60-seat.hwdb'. 2021-07-01 13:30:29 +03:00			`# This file is part of systemd.`
			`#`
			`# This file lists graphic devices that don't have a DRM driver and fall back to`
			`# a frame-buffer one instead. Since commit 6260d28b8a, frame-buffer devices are`
			`# no more considered as graphical capable.`
			`#`
			`# The matches have the 'fb' prefix to make sure that only the framebuffer`
			`# device, and not the (parent) PCI device, is tagged with 'master-of-seat'.`
			`#`
			`# Allowed properties are:`
			`# ID_TAG_MASTER_OF_SEAT=1`

			`#########################################`
			`# eXtreme Graphic Innovation (XGI)`
			`#########################################`

			`# Z7/Z9 (XG20 core), a rather ancient graphic chip, doesn't have a DRM driver`
			`# and falls back to vesafb.`
			`fb:pci:v000018CAd00000020*`
			`ID_TAG_MASTER_OF_SEAT=1`
login: use a hwdb entry for tagging HyperV's fb devices with 'master-of-seat' tag Graphic devices that don't do DRM and relies on fb devices are now listed in hwdb. Dedicated udev rules are no more needed. 2021-07-01 22:34:34 +03:00
			`#########################################`
			`# HyperV`
			`#########################################`

			`# HyperV currently doesn't do DRM, hence we need to synthesize for HyperV's fb`
			`# device instead.`
			`fb:pci:v00001414d00005353*`
			`ID_TAG_MASTER_OF_SEAT=1`
login: use a hwdb entry for tagging Parallels' fb devices with 'master-of-seat' tag This assumes that (vesa)fb driver is used as fallback. 2021-07-02 15:43:50 +03:00
			`#########################################`
			`# Parallels`
			`#########################################`

			`fb:pci:v00001ab8d00004005*`
			`ID_TAG_MASTER_OF_SEAT=1`