I'll make a request to delay the posting, but I don't know how much time I can get you.
Since it might be a while before the partner portal posting is up, I'm attaching the patches to this bug. There are three separate versions of the patch, for different driver versions:
a) nvidia-blacklist-register-mapping-290-295.diff for drivers from releases 290 and 295.
b) nvidia-blacklist-register-mapping-256-285.diff for drivers from releases 256 through 285, inclusive.
c) nvidia-blacklist-register-mapping-195.diff for drivers from releases 195 and earlier. (There were no releases between 195 and 256.)
The patch is intended for use as an argument to the --apply-patch option to the NVIDIA installer script. You can also just use `patch` directly; there are only two files that get patched.
(It looks like I can only attach one file at a time: I'll post separate comments to attach the other two files.)
I'll make a request to delay the posting, but I don't know how much time I can get you.
Since it might be a while before the partner portal posting is up, I'm attaching the patches to this bug. There are three separate versions of the patch, for different driver versions:
a) nvidia- blacklist- register- mapping- 290-295. diff for drivers from releases 290 and 295. blacklist- register- mapping- 256-285. diff for drivers from releases 256 through 285, inclusive. blacklist- register- mapping- 195.diff for drivers from releases 195 and earlier. (There were no releases between 195 and 256.)
b) nvidia-
c) nvidia-
The patch is intended for use as an argument to the --apply-patch option to the NVIDIA installer script. You can also just use `patch` directly; there are only two files that get patched.
(It looks like I can only attach one file at a time: I'll post separate comments to attach the other two files.)