| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
Over the many changes to the udev rules, the comments at the top
have become a little disheveled.
This commit fixes that up.
Spotted by Adam Williamson
|
| |
|
|
|
|
|
|
| |
commit 72bde3b3f474135e792c6c4e40932d7c82f87985 accidentally added
two checks for virtio pci devices. The latter check is too broad
and could potentially match non-graphics cards.
This commit drops it.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
With EFI and simpledrm we may end up booting without a card0 but
with a card1 drm device. This defeats GDM's simplistic hybrid
graphics check.
Also, our detection for virtio graphics wasn't working so well, because
it wrote the results into an environment variable of a non-parent
device.
This commit gets the detection logic working better for virt/efi setups.
Closes: https://gitlab.gnome.org/GNOME/gdm/-/issues/832
|
| |
|
|
|
| |
Mutter doesn't seem to work with multiple guest gpus right now,
so disable that.
|
| |
|
|
|
| |
If a VM has both virtualized graphics and is passing through host
hardware graphics, then we should disable wayland
|
| |
|
|
|
|
|
| |
mutter isn't great running in native mode on chips that don't have
fast blending.
This commit disables wayland on aspeed and matrox server cards.
|
| |
|
|
|
|
|
|
| |
The vendor nvidia driver scrambles texture memory during suspend, and
only restores it under certain situations.
This commit tries to detect those situations and only use wayland
in those cases.
|
| |
|
|
|
|
|
| |
We really don't want wayland on hybrid graphics laptops, because
certain connectors won't work right now.
This commit tries to detect the case and disable it.
|
| |
|
|
|
|
|
|
|
|
| |
udev sends a variety of events about devices during boot. Right
now we may be disabling wayland multiple times on Hi1710 ARM
machines, because we just match the device by id, and fail
to look at the event itself.
This commit just adds subsystem and action guards to specify
when the wayland disabling code should run a little more specifically.
|
| |
|
|
|
|
|
|
| |
GDM now blocks itself at runtime until udev is ready, so there's
no point in delaying GDM startup, too.
This commit reverts udev and systemd logic put in place to stall
GDM start up until udev finished.
|
| |
|
|
|
|
|
|
|
|
| |
At the moment we neglect to clean up the sync file GDM uses
to know when it's okay to start in the case there's only
a single card.
This commit fixes that.
https://gitlab.gnome.org/GNOME/gdm/-/issues/763
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The vendor nvidia driver has two modules loaded
at startup.
It's not uncommon for the second module to still
be loading when GDM starts.
Our udev rule relies on the second module to set
up GDM's boot configuration.
This commit adds some synchronization to stall
GDM a bit if the vendor driver is still coming
up.
https://gitlab.gnome.org/GNOME/gdm/-/issues/763
|
| |
|
|
|
|
|
| |
NVIDIA driver version 510 and above have support for GBM, use Wayland by
default with NVIDIA proprietary driver version 510 and above.
For versions between 470 and 510, prefer Xorg as before.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Not all DRM drivers are disabled when the nomodeset kernel cmdline option
is used. For example the simpledrm driver that use the system framebuffer
set-up by the bootloader, provides a modesetting interface.
Exclude the DRM drivers that match against the "simple-framebuffer" device
and only disable wayland for platform DRM drivers.
This allows to start a wayland session when nomodeset is used to disable a
platform DRM driver by using the simpledrm driver instead of legacy fbdev
drivers such as efifb, that does not support modsetting and could only be
used with an Xorg session.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Nvidia drivers since version 470 supports both native wayland and
accelerated Xwayland. The latter also works in hybrid configurations
using nvidia Optimus (the session will run using the main integrated
GPU, but it will be possible to use switcherooctl to run applications
using the discrete nvidia card).
However, the gdm rules were including a line that was supposed to
disable such scenario, but it didn't actually work as expected, so we
can safely remove it, without changing the behavior.
At the same time we can tune the rules so that, when the nvidia-drm
module is loaded, if the driver version is minor than 470, wayland is
disabled.
|
| |
|
|
|
|
|
|
| |
NVidia's wayland story is in a lot better shape these days, so
disabling wayland entirely by default is a big too much.
This commit changes the udev rule to just default to Xorg on single
GPU nvidia vendor driver systems instead of disabling wayland
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We can disable Wayland in runtime by invoking gdm-disable-wayland.
However, we may also want to enable Wayland in runtime for some
reasons. This idea is extended to modify more options/configurations in
runtime.
This commit renames gdm-disable-wayland to gdm-runtime-config and
unlocks the feature to modify more gdm configurations in runtime.
The new command format will be:
gdm-runtime-config set <group> <key> <value>
The configurable items refer to gdm.schemas. "<group>/<key>" combination
is the key in gdm.schemas.
For example, the original "gdm-disable-wayland" is replaced by
"gdm-runtime-config set daemon WaylandEnable false".
Link: https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/115#note_944907
|
| |
|
|
|
|
|
|
| |
wayland requires working modesetting, so don't even
bother trying it if modesetting is disabled.
This is more efficient and side-steps a bug in the fallback
logic if start up is unreasonably slow.
|
| |
|
|
|
|
|
|
| |
We disable Wayland on Cirrus since f15e6451, but the cirrus driver was
reimplemented in kernel v5.2 or later. This commit will enable Wayland
on Cirrus chipset.
Closes #586
|
| |
|
|
|
|
|
|
|
| |
At the moment GLX applications don't work well when the
proprietary nvidia driver is used with a wayland session.
For now, disable wayland on that hardware, and users who
want to opt in can just edit the udev rule.
(or add their own that overrides it)
|
| |
|
|
|
|
|
|
|
| |
Disable wayland for Huawei Hi1710 chipsets.
The login screen is skewed/distorted on arm server, and I couldn't
find root cause, and no other developer ever has access to the hardware.
https://gitlab.gnome.org/GNOME/mutter/issues/219
|
|
|
Now that we have a gdm-disable-wayland binary for disabling
wayland at boot, we should use it.
This commit changes the cirrus udev rule to use gdm-disable-wayland,
rather than running sh and printf.
https://bugzilla.gnome.org/show_bug.cgi?id=796315
|
