| View previous topic :: View next topic |
| Author |
Message |
F1r31c3r
Tux's lil' helper
Joined: 31 Aug 2007
Posts: 107
Location: UK
|
 Posted: Sat Oct 17, 2015 3:16 am Post subject: NEW Nvidia driver 358.09 black screen Secure Boot |
 |
|
Hello all
I thought i would post this if anyone has the issue, particularly with secure boot.
Nvidia has implemented a new modules with their drivers version 358.09.
| Quote: | Added a new kernel module, nvidia-modeset.ko. This new driver component works in conjunction with the nvidia.ko kernel module to program the display engine of the GPU.
nvidia-modeset.ko does not provide any new user-visible functionality or interfaces to third party applications. However, in a later release, nvidia-modeset.ko will be used as a basis for the modesetting interface provided by the kernel's direct rendering manager (DRM). |
So you not only have to sign nvidia.ko and nvidia-uvm.ko but nvidia-modeset.ko now.
Not sure why Nvidia did this but hey they did so just in case anyone else having this issue, remember to do this or you will get a X window session with a black screen and no multi-monitor support.
Here is the source of the beta driver info:
http://www.nvidia.com/download/driverResults.aspx/92712/en-us
_________________
A WikI, A collection of mass misinformation based on opinion and manipulation by a deception of freedom.
If we know the truth, then we should be free from deception (John 8:42-47 ) |
|
| Back to top |
|
 |
Nreal
Apprentice
Joined: 06 Jan 2009
Posts: 265
|
| Posted: Sat Oct 17, 2015 4:11 am Post subject: white screen video |
|
|
its causing white screen here when trying to watch videos fullscreen 
Multiseat is working though without issues |
|
| Back to top |
|
|
Roman_Gruber
Advocate
Joined: 03 Oct 2006
Posts: 3846
Location: Austro Bavaria
|
| Posted: Sat Oct 17, 2015 11:20 am Post subject: |
|
|
Thanks, more a reason to mask any higher version including this.
Until someone tested out how to deal with that and wrote down clear upgrade instructions somewhere (gentoo wiki should be the place)
Hardly a benefit in changing binary blob versions anyway, expierence for ~7 years with nvidia.
edit: masked because no working nvidia-settings in the tree which matches.
Last edited by Roman_Gruber on Sat Oct 17, 2015 12:57 pm; edited 1 time in total |
|
| Back to top |
|
|
Buffoon
Veteran
Joined: 17 Jun 2015
Posts: 1369
Location: EU or US
|
| Posted: Sat Oct 17, 2015 11:53 am Post subject: |
|
|
| The new version works fine in my non-secureboot box. |
|
| Back to top |
|
|
F1r31c3r
Tux's lil' helper
Joined: 31 Aug 2007
Posts: 107
Location: UK
|
| Posted: Sat Oct 17, 2015 9:41 pm Post subject: |
|
|
| Buffoon wrote: | | The new version works fine in my non-secureboot box. |
Yes it will just work fine if you do not use secure boot signed kernel modules, I made this topic to point out Nvidia have split the nvidia.ko module in two and put the mode setting functions into a separate module.
Furthermore if you use secure boot which in Linux is just the signing of each kernel module with a custom key you make and manage yourself then unless the new nvidia-modeset.ko is also manually signed it gives no apparent error message or indication you need sign this additional module.
Maybe it needs to be put into portage enews as to alert those that do update to this version who use the secure boot kernel signing.
| tw04l124 wrote: | | Until someone tested out how to deal with that and wrote down clear upgrade instructions somewhere (gentoo wiki should be the place) |
Good point, I shall head over to the wiki and see what is there and update it, thanks.
The Wiki has been updated to include instructions for module signing and note added for this third module.
https://wiki.gentoo.org/wiki/NVidia/nvidia-drivers#Kernel_module_signing
WhooRaarrr
_________________
A WikI, A collection of mass misinformation based on opinion and manipulation by a deception of freedom.
If we know the truth, then we should be free from deception (John 8:42-47 ) |
|
| Back to top |
|
|
|
Documentation, Tips & Tricks
