On Fri, 2018-06-22 at 21:37 +0200, Andreas Beckmann wrote: > On 2018-06-22 12:58, Holger Schröder wrote: > > The changes in /etc/nvidia/current/nvidia-drm-outputclass.conf > > solve the > > Problem and works. > > > > But after Kernelupdate to linux-image-4.16.0-2-amd64 (4.16.16-1) > > boot > > into a black Screen, 4.16.12-1 workd fine. > > Unrelated problem, just nasty to have two big ones at the same time.
It might be possible to patch the module for the usercopy stack issue, but it's quite tricky, the folks at gr security seem to be patching the driver with the needed change: https://www.grsecurity.net/~paxguy1/nvidia-drivers-387.12-pax.patch But given the workaround seems to work fine I wouldn't bother and I'd let Nvidia sort it out. The workaround is to add to the cmdline: slab_common.usercopy_fallback=y > On 2018-06-22 16:27, floris wrote: > > I don't expect this will work with a xserver less then 1.20, > > because the > > ModulePath option in an OutpuClass section is an unknown option. > > Confirmed. > > What about the following /etc/nvidia/current/nvidia-drm- > outputclass.conf > > --------------------------------------------------- > Section "Files" > ModulePath "/usr/lib/xorg/modules/linux" > ModulePath "/usr/lib/xorg/modules" > EndSection > > Section "OutputClass" > Identifier "nvidia" > MatchDriver "nvidia-drm" > Driver "nvidia" > EndSection > --------------------------------------------------- > > That seems to work for stable ... what about sid? > > > Andreas Tried on Sid and at least it doesn't break it - but note that I can't reproduce the original problem, so I can't be sure. -- Kind regards, Luca Boccassi
signature.asc
Description: This is a digitally signed message part
