On Mon, Jun 27, 2016 at 10:02 AM, Dave Pawson <dave.pawson(a)gmail.com> wrote:
On 27 June 2016 at 17:28, Gabe Rubin <gaberubin(a)gmail.com>
> On Sun, Jun 26, 2016 at 11:53 PM, Dave Pawson <dave.pawson(a)gmail.com>
>> With my problem (update rather than new system), Xorg log shows
>> similar oddities (my view)
>> LoadModule "nouveau"
>> Loading /usr..... /nouveau_drv.so
>> LoadModule "nv" # is this the Nvidia module????
>> Warning, couldn't open module nv
>> Failed to load module "nv" (module does not exist, 0)
>> On 27 June 2016 at 01:14, Robin Laing <MeSat(a)telusplanet.net> wrote:
>> > Hello,
>> > A new machine and I have installed the rpmfusion nVidia akmods but
>> > is
>> > trying to load module "nv", not "nvidia" according the
>> > Where could the system be trying to load the nv driver instead of the
>> > nvidia
>> > driver?
>> > nvidia-xorg.conf exists
>> > 99-nvidia.conf exists and points to the correct module directories.
>> > This may be the issue.
>> > modprobe: modprobe: ERROR: could not insert 'nvidia': Required key
>> > available
>> > How do I add a key to nvidia to load the module?
>> > I need secure boot configured on this machine for Windows 10 and
>> > as
>> > it is not my computer and will be configured as dual boot.
>> > Robin
> You need to blacklist the nouvea driver. There are instructions on how
> do this online.
"Online"? A rather big place - and why can't the install do this?
Here is a guide (not the one I used, it has been several years since I had
The nouveau driver is built into the kernel, so you need to blacklist it on
startup using your bootloader. If it loads, you can't load another
driver. I believe it was done this way to have some functioning (and open
source) nvidia driver out the box.