| 1 |
On Tue, Dec 21, 2021 at 08:31:55AM +0200, Nikos Chantziaras wrote: |
| 2 |
> Seems to be a different issue then. I'm on an nvidia card using the |
| 3 |
> binary driver, and there's no problems like the ones you're having. It's |
| 4 |
> a straight disappearance of the desktop here when it happens due to the |
| 5 |
> X11 process segfault. |
| 6 |
|
| 7 |
If using xorg-21, I assume using nvidia-drivers-495.xx as well? |
| 8 |
|
| 9 |
I was never able to reproduce these, but did run into users running |
| 10 |
into segfault-at-start issues with 495. |
| 11 |
|
| 12 |
With 495.44-r2 and 495.46-r10, Xorg log may have a backtrace |
| 13 |
mentioning libnvidia-glcore.so, if so try 495.46-r0. |
| 14 |
|
| 15 |
Alternatively, 495.46* may mention failed in libpthread (or libc if |
| 16 |
glibc-2.34), in that case try 495.44-r2 instead. |
| 17 |
|
| 18 |
The more failsafe approach however is to just use stable drivers though. |
| 19 |
|
| 20 |
echo "x11-drivers/nvidia-drivers -~amd64" >> /etc/portage/package.accept_keywords |
| 21 |
|
| 22 |
Or 470.94 is fine too (due to be next stable soon). |
| 23 |
|
| 24 |
If still happening, then I don't know what might be wrong just from |
| 25 |
this. |
| 26 |
|
| 27 |
-- |
| 28 |
ionen |
Archives