Commits on Source (22)
-
Olivier Fourdan authored
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.
dda2fbb1 -
Ray Strode authored
gdm.rules: Prefer Wayland with NVIDIA >= 510 See merge request GNOME/gdm!169
8b1237c7 -
Marc-Antoine Perennou authored
Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
be8d893a -
so that gnome-session finds gnome-login.session
65a79968 -
Ray Strode authored
launch-environment: add DATADIR to XDG_DATA_DIRS Closes #756 See merge request GNOME/gdm!168
7bef7d48 -
Marc-Antoine Perennou authored
Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
7661ffce -
Ray Strode authored
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
b2d6ccee -
Ray Strode authored
data: Don't race with vendor nvidia driver at startup See merge request GNOME/gdm!170
ef5a3d76 -
Ray Strode authored
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
8393c59d -
Ray Strode authored
data: Fix logic error in single card vendor nvidia cases See merge request GNOME/gdm!172
0bdb02c1 -
Asier Sarasua Garmendia authored32035b7e
-
Ray Strode authored
At the moment, GDM waits until systemd says the system supports graphics (via the CanGraphical logind property). Unfortunately, this property isn't really what we need, since it flips to true when *any* graphics are available, not when the main graphics for the system are ready. This is a problem on hybrid graphics systems, if one card is slower to load than another. In particular, the vendor nvidia driver can be slow to load because it has multiple kernel modules it loads in series. Indeed on fast systems, that use the vendor nvidia driver, it's not unusual for boot to get to a point where all of userspace up to and including GDM is executed before the graphics are ready to go. This commit tries to mitigate the situation by adding an additional, check aside from CanGraphical to test if the system is ready. This check waits for the graphics card associated with boot to be fully up and running before proceeding to start a login screen. Closes: https://gitlab.gnome.org/GNOME/gdm/-/issues/763
895f765a -
Ray Strode authored
Ideally we would reread /run/gdm/custom.conf after we've decided graphics setup is complete. This is because the file may not get written out by udev until after GDM is already started and waiting. As a first step to get there, this commit adds an API for rereading the file, and changes the SIGHUP handler to use it (instead of the complete teardown and reinitialization it was doing before).
c4f81c02 -
Ray Strode authored
If GDM starts faster than graphics initialize, then the udev rules that write out /run/gdm/custom.conf might get run too late for GDM to notice. This commit changes GDM to reread its config after graphicals initialization completes. https://gitlab.gnome.org/GNOME/gdm/-/issues/763
45daec66 -
Ray Strode authored
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.
876751b1 -
Ray Strode authored
Try to address nvidia race on hybrid graphics setups Closes #763 See merge request GNOME/gdm!173
6d2e9b95 -
Peniel Vargas authored31063c26
-
sicklylife authored53d996b5
-
Jordi Mas authored7b4db3a6
-
Ray Strode authored678e98c0
-
Ray Strode authored55f57247
-
Jeremy Bicha authoredbdb420a2
This diff is collapsed.
This diff is collapsed.