* Re: Suspend Boken under Nvidia Gnome Wayland
2023-11-08 19:30 [ISSUE] Suspend Boken under Nvidia Gnome Wayland CuriousApe2020
@ 2023-11-14 6:05 ` Treeniks
2023-11-14 6:06 ` Treeniks
` (7 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Treeniks @ 2023-11-14 6:05 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 3659 bytes --]
New comment by Treeniks on void-packages repository
https://github.com/void-linux/void-packages/issues/47125#issuecomment-1809598774
Comment:
When I look into gdm's udev rules, I can find these lines:
```
# Check if suspend/resume services necessary for working wayland support is available
TEST{0711}!="/usr/bin/nvidia-sleep.sh", GOTO="gdm_disable_wayland"
TEST{0711}!="/usr/lib/systemd/system-sleep/nvidia", GOTO="gdm_disable_wayland"
...
```
meaning they specifically disable wayland if a `/usr/bin/nvidia-sleep.sh` file is not found.
The Arch Wiki has some info on this:
<https://wiki.archlinux.org/title/GDM#Wayland_and_the_proprietary_NVIDIA_driver>
> If the Wayland option is not displayed in GDM, even after [enabling KMS](https://wiki.archlinux.org/title/NVIDIA#DRM_kernel_mode_setting) and [configuring Wayland](https://wiki.archlinux.org/title/NVIDIA#Wayland), then you most likely have `NVreg_PreserveVideoMemoryAllocations` and [NVIDIA systemd services](https://gitlab.gnome.org/GNOME/gdm/-/commit/51181871e9db716546e9593216220389de0d8b03) disabled.
<https://wiki.archlinux.org/title/NVIDIA/Tips_and_tricks#Preserve_video_memory_after_suspend>
> The still experimental system enables saving all video memory (given enough space on disk or main RAM). The interface is through the `/proc/driver/nvidia/suspend` file as follows:
> * write "suspend" (or "hibernate") to `/proc/driver/nvidia/suspend` immediately before writing to the usual Linux `/sys/power/state` file
> * write "resume" to `/proc/driver/nvidia/suspend` immediately after waking up, or after an unsuccessful attempt to suspend or hibernate.
>
> To save and restore all video memory contents, [load](https://wiki.archlinux.org/title/Kernel_modules#Setting_module_options) the nvidia kernel module with the `NVreg_PreserveVideoMemoryAllocations=1` option and [enable](https://wiki.archlinux.org/title/Enable) `nvidia-suspend.service` and `nvidia-hibernate.service`.
> [...]
> The interaction with `/proc/driver/nvidia/suspend` is handled by the simple Unix shell script at `/usr/bin/nvidia-sleep.sh`, which will itself be called by [systemd](https://wiki.archlinux.org/title/Systemd) or other tools. The [nvidia-utils](https://archlinux.org/packages/?name=nvidia-utils) package ships with the following services (which essentially just call `nvidia-sleep.sh`): `nvidia-suspend.service`, `nvidia-hibernate.service`, `nvidia-resume.service`.
The Debian docs on this also have similar instructions:
<https://wiki.debian.org/NvidiaGraphicsDrivers#Wayland>
From what I can tell by using `xlocate`, I cannot find any package which includes such services or scripts.
I am awfully unqualified for this, but I believe the only way to make this work in Void at the moment is to disable the GDM udev rule entirely (with `ln -s /dev/null /etc/udev/rules.d/61-gdm.rules`) and live with a broken suspend, until a similar `nvidia-utils` package is added.
I did however notice that the `/proc/driver/nvidia/suspend` file already has a `suspend hibernate resume` line written in it. Not sure what this does, but maybe by simply adding the `NVreg_PreserveVideoMemoryAllocations=1` kernel module option, suspend can be fixed (or at least improved)?
I.e. adding a `/etc/modprobe.d/nvidia-power-management.conf` file (be careful not to name it `nvidia.conf` like my idiot self, that will override `/lib/modprobe.p/nvidia.conf` which blacklists nouveau) with the following content:
```
options nvidia NVreg_PreserveVideoMemoryAllocations=1
```
(and I believe one has to [reconfigure the linux kernel](https://docs.voidlinux.org/config/kernel.html#install-hooks)?)
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Suspend Boken under Nvidia Gnome Wayland
2023-11-08 19:30 [ISSUE] Suspend Boken under Nvidia Gnome Wayland CuriousApe2020
2023-11-14 6:05 ` Treeniks
@ 2023-11-14 6:06 ` Treeniks
2023-11-14 6:09 ` Treeniks
` (6 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Treeniks @ 2023-11-14 6:06 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 3663 bytes --]
New comment by Treeniks on void-packages repository
https://github.com/void-linux/void-packages/issues/47125#issuecomment-1809598774
Comment:
When I look into gdm's udev rules, I can find these lines:
```
# Check if suspend/resume services necessary for working wayland support is available
TEST{0711}!="/usr/bin/nvidia-sleep.sh", GOTO="gdm_disable_wayland"
TEST{0711}!="/usr/lib/systemd/system-sleep/nvidia", GOTO="gdm_disable_wayland"
...
```
meaning they specifically disable wayland if a `/usr/bin/nvidia-sleep.sh` file is not found.
The Arch Wiki has some info on this:
<https://wiki.archlinux.org/title/GDM#Wayland_and_the_proprietary_NVIDIA_driver>
> If the Wayland option is not displayed in GDM, even after [enabling KMS](https://wiki.archlinux.org/title/NVIDIA#DRM_kernel_mode_setting) and [configuring Wayland](https://wiki.archlinux.org/title/NVIDIA#Wayland), then you most likely have `NVreg_PreserveVideoMemoryAllocations` and [NVIDIA systemd services](https://gitlab.gnome.org/GNOME/gdm/-/commit/51181871e9db716546e9593216220389de0d8b03) disabled.
<https://wiki.archlinux.org/title/NVIDIA/Tips_and_tricks#Preserve_video_memory_after_suspend>
> The **still experimental** system enables saving all video memory (given enough space on disk or main RAM). The interface is through the `/proc/driver/nvidia/suspend` file as follows:
> * write "suspend" (or "hibernate") to `/proc/driver/nvidia/suspend` immediately before writing to the usual Linux `/sys/power/state` file
> * write "resume" to `/proc/driver/nvidia/suspend` immediately after waking up, or after an unsuccessful attempt to suspend or hibernate.
>
> To save and restore all video memory contents, [load](https://wiki.archlinux.org/title/Kernel_modules#Setting_module_options) the nvidia kernel module with the `NVreg_PreserveVideoMemoryAllocations=1` option and [enable](https://wiki.archlinux.org/title/Enable) `nvidia-suspend.service` and `nvidia-hibernate.service`.
> [...]
> The interaction with `/proc/driver/nvidia/suspend` is handled by the simple Unix shell script at `/usr/bin/nvidia-sleep.sh`, which will itself be called by [systemd](https://wiki.archlinux.org/title/Systemd) or other tools. The [nvidia-utils](https://archlinux.org/packages/?name=nvidia-utils) package ships with the following services (which essentially just call `nvidia-sleep.sh`): `nvidia-suspend.service`, `nvidia-hibernate.service`, `nvidia-resume.service`.
The Debian docs on this also have similar instructions:
<https://wiki.debian.org/NvidiaGraphicsDrivers#Wayland>
From what I can tell by using `xlocate`, I cannot find any package which includes such services or scripts.
I am awfully unqualified for this, but I believe the only way to make this work in Void at the moment is to disable the GDM udev rule entirely (with `ln -s /dev/null /etc/udev/rules.d/61-gdm.rules`) and live with a broken suspend, until a similar `nvidia-utils` package is added.
I did however notice that the `/proc/driver/nvidia/suspend` file already has a `suspend hibernate resume` line written in it. Not sure what this does, but maybe by simply adding the `NVreg_PreserveVideoMemoryAllocations=1` kernel module option, suspend can be fixed (or at least improved)?
I.e. adding a `/etc/modprobe.d/nvidia-power-management.conf` file (be careful not to name it `nvidia.conf` like my idiot self, that will override `/lib/modprobe.p/nvidia.conf` which blacklists nouveau) with the following content:
```
options nvidia NVreg_PreserveVideoMemoryAllocations=1
```
(and I believe one has to [reconfigure the linux kernel](https://docs.voidlinux.org/config/kernel.html#install-hooks)?)
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Suspend Boken under Nvidia Gnome Wayland
2023-11-08 19:30 [ISSUE] Suspend Boken under Nvidia Gnome Wayland CuriousApe2020
2023-11-14 6:05 ` Treeniks
2023-11-14 6:06 ` Treeniks
@ 2023-11-14 6:09 ` Treeniks
2023-11-14 6:09 ` Treeniks
` (5 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Treeniks @ 2023-11-14 6:09 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 3708 bytes --]
New comment by Treeniks on void-packages repository
https://github.com/void-linux/void-packages/issues/47125#issuecomment-1809598774
Comment:
When I look into gdm's udev rules (located at /lib/udev/rules.d/61-gdm.rules`), I can find these lines:
```
# Check if suspend/resume services necessary for working wayland support is available
TEST{0711}!="/usr/bin/nvidia-sleep.sh", GOTO="gdm_disable_wayland"
TEST{0711}!="/usr/lib/systemd/system-sleep/nvidia", GOTO="gdm_disable_wayland"
...
```
meaning they specifically disable wayland if a `/usr/bin/nvidia-sleep.sh` file is not found.
The Arch Wiki has some info on this:
<https://wiki.archlinux.org/title/GDM#Wayland_and_the_proprietary_NVIDIA_driver>
> If the Wayland option is not displayed in GDM, even after [enabling KMS](https://wiki.archlinux.org/title/NVIDIA#DRM_kernel_mode_setting) and [configuring Wayland](https://wiki.archlinux.org/title/NVIDIA#Wayland), then you most likely have `NVreg_PreserveVideoMemoryAllocations` and [NVIDIA systemd services](https://gitlab.gnome.org/GNOME/gdm/-/commit/51181871e9db716546e9593216220389de0d8b03) disabled.
<https://wiki.archlinux.org/title/NVIDIA/Tips_and_tricks#Preserve_video_memory_after_suspend>
> The **still experimental** system enables saving all video memory (given enough space on disk or main RAM). The interface is through the `/proc/driver/nvidia/suspend` file as follows:
> * write "suspend" (or "hibernate") to `/proc/driver/nvidia/suspend` immediately before writing to the usual Linux `/sys/power/state` file
> * write "resume" to `/proc/driver/nvidia/suspend` immediately after waking up, or after an unsuccessful attempt to suspend or hibernate.
>
> To save and restore all video memory contents, [load](https://wiki.archlinux.org/title/Kernel_modules#Setting_module_options) the nvidia kernel module with the `NVreg_PreserveVideoMemoryAllocations=1` option and [enable](https://wiki.archlinux.org/title/Enable) `nvidia-suspend.service` and `nvidia-hibernate.service`.
> [...]
> The interaction with `/proc/driver/nvidia/suspend` is handled by the simple Unix shell script at `/usr/bin/nvidia-sleep.sh`, which will itself be called by [systemd](https://wiki.archlinux.org/title/Systemd) or other tools. The [nvidia-utils](https://archlinux.org/packages/?name=nvidia-utils) package ships with the following services (which essentially just call `nvidia-sleep.sh`): `nvidia-suspend.service`, `nvidia-hibernate.service`, `nvidia-resume.service`.
The Debian docs on this also have similar instructions:
<https://wiki.debian.org/NvidiaGraphicsDrivers#Wayland>
From what I can tell by using `xlocate`, I cannot find any package which includes such services or scripts.
I am awfully unqualified for this, but I believe the only way to make this work in Void at the moment is to disable the GDM udev rule entirely (with `ln -s /dev/null /etc/udev/rules.d/61-gdm.rules`) and live with a broken suspend, until a similar `nvidia-utils` package is added.
I did however notice that the `/proc/driver/nvidia/suspend` file already has a `suspend hibernate resume` line written in it. Not sure what this does, but maybe by simply adding the `NVreg_PreserveVideoMemoryAllocations=1` kernel module option, suspend can be fixed (or at least improved)?
I.e. adding a `/etc/modprobe.d/nvidia-power-management.conf` file (be careful not to name it `nvidia.conf` like my idiot self, that will override `/lib/modprobe.p/nvidia.conf` which blacklists nouveau) with the following content:
```
options nvidia NVreg_PreserveVideoMemoryAllocations=1
```
(and I believe one has to [reconfigure the linux kernel](https://docs.voidlinux.org/config/kernel.html#install-hooks)?)
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Suspend Boken under Nvidia Gnome Wayland
2023-11-08 19:30 [ISSUE] Suspend Boken under Nvidia Gnome Wayland CuriousApe2020
` (2 preceding siblings ...)
2023-11-14 6:09 ` Treeniks
@ 2023-11-14 6:09 ` Treeniks
2023-11-14 6:19 ` Treeniks
` (4 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Treeniks @ 2023-11-14 6:09 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 3709 bytes --]
New comment by Treeniks on void-packages repository
https://github.com/void-linux/void-packages/issues/47125#issuecomment-1809598774
Comment:
When I look into gdm's udev rules (located at `/lib/udev/rules.d/61-gdm.rules`), I can find these lines:
```
# Check if suspend/resume services necessary for working wayland support is available
TEST{0711}!="/usr/bin/nvidia-sleep.sh", GOTO="gdm_disable_wayland"
TEST{0711}!="/usr/lib/systemd/system-sleep/nvidia", GOTO="gdm_disable_wayland"
...
```
meaning they specifically disable wayland if a `/usr/bin/nvidia-sleep.sh` file is not found.
The Arch Wiki has some info on this:
<https://wiki.archlinux.org/title/GDM#Wayland_and_the_proprietary_NVIDIA_driver>
> If the Wayland option is not displayed in GDM, even after [enabling KMS](https://wiki.archlinux.org/title/NVIDIA#DRM_kernel_mode_setting) and [configuring Wayland](https://wiki.archlinux.org/title/NVIDIA#Wayland), then you most likely have `NVreg_PreserveVideoMemoryAllocations` and [NVIDIA systemd services](https://gitlab.gnome.org/GNOME/gdm/-/commit/51181871e9db716546e9593216220389de0d8b03) disabled.
<https://wiki.archlinux.org/title/NVIDIA/Tips_and_tricks#Preserve_video_memory_after_suspend>
> The **still experimental** system enables saving all video memory (given enough space on disk or main RAM). The interface is through the `/proc/driver/nvidia/suspend` file as follows:
> * write "suspend" (or "hibernate") to `/proc/driver/nvidia/suspend` immediately before writing to the usual Linux `/sys/power/state` file
> * write "resume" to `/proc/driver/nvidia/suspend` immediately after waking up, or after an unsuccessful attempt to suspend or hibernate.
>
> To save and restore all video memory contents, [load](https://wiki.archlinux.org/title/Kernel_modules#Setting_module_options) the nvidia kernel module with the `NVreg_PreserveVideoMemoryAllocations=1` option and [enable](https://wiki.archlinux.org/title/Enable) `nvidia-suspend.service` and `nvidia-hibernate.service`.
> [...]
> The interaction with `/proc/driver/nvidia/suspend` is handled by the simple Unix shell script at `/usr/bin/nvidia-sleep.sh`, which will itself be called by [systemd](https://wiki.archlinux.org/title/Systemd) or other tools. The [nvidia-utils](https://archlinux.org/packages/?name=nvidia-utils) package ships with the following services (which essentially just call `nvidia-sleep.sh`): `nvidia-suspend.service`, `nvidia-hibernate.service`, `nvidia-resume.service`.
The Debian docs on this also have similar instructions:
<https://wiki.debian.org/NvidiaGraphicsDrivers#Wayland>
From what I can tell by using `xlocate`, I cannot find any package which includes such services or scripts.
I am awfully unqualified for this, but I believe the only way to make this work in Void at the moment is to disable the GDM udev rule entirely (with `ln -s /dev/null /etc/udev/rules.d/61-gdm.rules`) and live with a broken suspend, until a similar `nvidia-utils` package is added.
I did however notice that the `/proc/driver/nvidia/suspend` file already has a `suspend hibernate resume` line written in it. Not sure what this does, but maybe by simply adding the `NVreg_PreserveVideoMemoryAllocations=1` kernel module option, suspend can be fixed (or at least improved)?
I.e. adding a `/etc/modprobe.d/nvidia-power-management.conf` file (be careful not to name it `nvidia.conf` like my idiot self, that will override `/lib/modprobe.p/nvidia.conf` which blacklists nouveau) with the following content:
```
options nvidia NVreg_PreserveVideoMemoryAllocations=1
```
(and I believe one has to [reconfigure the linux kernel](https://docs.voidlinux.org/config/kernel.html#install-hooks)?)
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Suspend Boken under Nvidia Gnome Wayland
2023-11-08 19:30 [ISSUE] Suspend Boken under Nvidia Gnome Wayland CuriousApe2020
` (3 preceding siblings ...)
2023-11-14 6:09 ` Treeniks
@ 2023-11-14 6:19 ` Treeniks
2023-11-20 15:11 ` m3tav3rse
` (3 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Treeniks @ 2023-11-14 6:19 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 3923 bytes --]
New comment by Treeniks on void-packages repository
https://github.com/void-linux/void-packages/issues/47125#issuecomment-1809598774
Comment:
When I look into gdm's udev rules (located at `/lib/udev/rules.d/61-gdm.rules`), I can find these lines:
```
# Check if suspend/resume services necessary for working wayland support is available
TEST{0711}!="/usr/bin/nvidia-sleep.sh", GOTO="gdm_disable_wayland"
TEST{0711}!="/usr/lib/systemd/system-sleep/nvidia", GOTO="gdm_disable_wayland"
...
```
meaning they specifically disable wayland if a `/usr/bin/nvidia-sleep.sh` file is not found.
The Arch Wiki has some info on this:
<https://wiki.archlinux.org/title/GDM#Wayland_and_the_proprietary_NVIDIA_driver>
> If the Wayland option is not displayed in GDM, even after [enabling KMS](https://wiki.archlinux.org/title/NVIDIA#DRM_kernel_mode_setting) and [configuring Wayland](https://wiki.archlinux.org/title/NVIDIA#Wayland), then you most likely have `NVreg_PreserveVideoMemoryAllocations` and [NVIDIA systemd services](https://gitlab.gnome.org/GNOME/gdm/-/commit/51181871e9db716546e9593216220389de0d8b03) disabled.
<https://wiki.archlinux.org/title/NVIDIA/Tips_and_tricks#Preserve_video_memory_after_suspend>
> The **still experimental** system enables saving all video memory (given enough space on disk or main RAM). The interface is through the `/proc/driver/nvidia/suspend` file as follows:
> * write "suspend" (or "hibernate") to `/proc/driver/nvidia/suspend` immediately before writing to the usual Linux `/sys/power/state` file
> * write "resume" to `/proc/driver/nvidia/suspend` immediately after waking up, or after an unsuccessful attempt to suspend or hibernate.
>
> To save and restore all video memory contents, [load](https://wiki.archlinux.org/title/Kernel_modules#Setting_module_options) the nvidia kernel module with the `NVreg_PreserveVideoMemoryAllocations=1` option and [enable](https://wiki.archlinux.org/title/Enable) `nvidia-suspend.service` and `nvidia-hibernate.service`.
> [...]
> The interaction with `/proc/driver/nvidia/suspend` is handled by the simple Unix shell script at `/usr/bin/nvidia-sleep.sh`, which will itself be called by [systemd](https://wiki.archlinux.org/title/Systemd) or other tools. The [nvidia-utils](https://archlinux.org/packages/?name=nvidia-utils) package ships with the following services (which essentially just call `nvidia-sleep.sh`): `nvidia-suspend.service`, `nvidia-hibernate.service`, `nvidia-resume.service`.
The Debian docs on this also have similar instructions:
<https://wiki.debian.org/NvidiaGraphicsDrivers#Wayland>
From what I can tell by using `xlocate`, I cannot find any package which includes such services or scripts.
I am awfully unqualified for this, but I believe the only way to make this work in Void at the moment is to disable the GDM udev rule entirely (with `ln -s /dev/null /etc/udev/rules.d/61-gdm.rules`) and live with a broken suspend, until a similar `nvidia-utils` package is added.
I did however notice that the `/proc/driver/nvidia/suspend` file already has a `suspend hibernate resume` line written in it. Not sure what this does, ~~but maybe by simply adding the `NVreg_PreserveVideoMemoryAllocations=1` kernel module option, suspend can be fixed (or at least improved)?~~ After short testing, seems to change nothing.
I.e. adding a `/etc/modprobe.d/nvidia-power-management.conf` file (be careful not to name it `nvidia.conf` like my idiot self, that will override `/lib/modprobe.p/nvidia.conf` which blacklists nouveau) with the following content:
```
options nvidia NVreg_PreserveVideoMemoryAllocations=1
```
(and I believe one has to [reconfigure the linux kernel](https://docs.voidlinux.org/config/kernel.html#install-hooks)?)
It might also be possible to simply add `nvidia-sleep.sh` etc. manually by copying it over from the Arch or Debian packages, though that does seem rather hacky.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Suspend Boken under Nvidia Gnome Wayland
2023-11-08 19:30 [ISSUE] Suspend Boken under Nvidia Gnome Wayland CuriousApe2020
` (4 preceding siblings ...)
2023-11-14 6:19 ` Treeniks
@ 2023-11-20 15:11 ` m3tav3rse
2024-05-03 12:47 ` tgorordo
` (2 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: m3tav3rse @ 2023-11-20 15:11 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
New comment by m3tav3rse on void-packages repository
https://github.com/void-linux/void-packages/issues/47125#issuecomment-1819250501
Comment:
It's a bug in elogind's workaround for nvidia driver.
Upstream issues: https://github.com/elogind/elogind/issues/234 https://github.com/elogind/elogind/issues/243
As a workaround you could try putting system to sleep with [zzz](https://man.voidlinux.org/zzz), works on my sway + nvidia system.
> It might also be possible to simply add nvidia-sleep.sh etc. manually by copying it over from the Arch or Debian packages, though that does seem rather hacky.
I doubt it would change anything but you can always copy nvidia-sleep.sh from arch [package](https://archlinux.org/packages/extra/x86_64/nvidia-utils/download/) and test it.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Suspend Boken under Nvidia Gnome Wayland
2023-11-08 19:30 [ISSUE] Suspend Boken under Nvidia Gnome Wayland CuriousApe2020
` (5 preceding siblings ...)
2023-11-20 15:11 ` m3tav3rse
@ 2024-05-03 12:47 ` tgorordo
2024-05-03 12:48 ` tgorordo
2024-05-03 23:27 ` mtvrsh
8 siblings, 0 replies; 10+ messages in thread
From: tgorordo @ 2024-05-03 12:47 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
New comment by tgorordo on void-packages repository
https://github.com/void-linux/void-packages/issues/47125#issuecomment-2092949391
Comment:
The upstream issue may be resolved? It's recently marked closed at least.
Manually tweaking the package template and using `xbps-src` etc. to install `elogind-252.24` instead of the `elogind-252.9` that void currently ships seems to fix some suspend-related nvidia issues I was having, though I can't say with confidence I didn't break something else (to get things to build quick-&-dirty I removed all patches from the template). I'm too much of a newbie to do anything more myself with confidence, but an update of the package might fix things at this point?
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Suspend Boken under Nvidia Gnome Wayland
2023-11-08 19:30 [ISSUE] Suspend Boken under Nvidia Gnome Wayland CuriousApe2020
` (6 preceding siblings ...)
2024-05-03 12:47 ` tgorordo
@ 2024-05-03 12:48 ` tgorordo
2024-05-03 23:27 ` mtvrsh
8 siblings, 0 replies; 10+ messages in thread
From: tgorordo @ 2024-05-03 12:48 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
New comment by tgorordo on void-packages repository
https://github.com/void-linux/void-packages/issues/47125#issuecomment-2092949391
Comment:
The upstream issue may be resolved? It's recently marked closed at least.
Manually tweaking the package template and using `xbps-src` etc. to install `elogind-252.24` instead of the `elogind-252.9` that void currently ships seems to fix some suspend-related nvidia issues I was having, though I can't say for sure I didn't break anything else (to get things to build quick-&-dirty I removed all patches from the template). I'm too much of a newbie to do anything more myself with confidence, but an update of the package might fix things at this point?
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Suspend Boken under Nvidia Gnome Wayland
2023-11-08 19:30 [ISSUE] Suspend Boken under Nvidia Gnome Wayland CuriousApe2020
` (7 preceding siblings ...)
2024-05-03 12:48 ` tgorordo
@ 2024-05-03 23:27 ` mtvrsh
8 siblings, 0 replies; 10+ messages in thread
From: mtvrsh @ 2024-05-03 23:27 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 317 bytes --]
New comment by mtvrsh on void-packages repository
https://github.com/void-linux/void-packages/issues/47125#issuecomment-2093882188
Comment:
You're right upstream fixed this issue.
You only needed to remove 1 patch, like this: https://github.com/mtvrsh/void-packages/commit/ac8d2fec5f2058cbedf382564bf8d8f2f51fe76e
^ permalink raw reply [flat|nested] 10+ messages in thread