nVidia: Loading out of tree module taints kernel problem.

[linux guy]

Hello fellow Fedorians.

I have everything set up to run nvidia drivers for my GTX 1060.   But my
machine loads nouveau instead, due to a tainted kernel message.

I turned off "Secure Boot" in the BIOS and enabled Compatibility Support
Mode - UEFI.

How do I force the use of the nvidia driver over nouveau ?

Thanks

dnf list \*nvidia\*

Installed Packages
akmod-nvidia.x86_64                                3:440.82-1.fc32
 @rpmfusion-nonfree
kmod-nvidia-5.6.13-300.fc32.x86_64.x86_64          3:440.82-1.fc32
 @@commandline
nvidia-settings.x86_64                             3:440.82-1.fc32
 @rpmfusion-nonfree
xorg-x11-drv-nvidia.x86_64                         3:440.82-1.fc32
 @rpmfusion-nonfree
xorg-x11-drv-nvidia-cuda-libs.x86_64               3:440.82-1.fc32
 @rpmfusion-nonfree
xorg-x11-drv-nvidia-kmodsrc.x86_64                 3:440.82-1.fc32
 @rpmfusion-nonfree
xorg-x11-drv-nvidia-libs.i686                      3:440.82-1.fc32
 @rpmfusion-nonfree
xorg-x11-drv-nvidia-libs.x86_64                    3:440.82-1.fc32
 @rpmfusion-nonfree

# akmods
Checking kmods exist for 5.6.13-300.fc32.x86_64            [  OK  ]

uname -a
Linux bigboy 5.6.13-300.fc32.x86_64 #1 SMP Thu May 14 22:51:37 UTC 2020
x86_64 x86_64 x86_64 GNU/

dmesg | grep nvidia
[    4.945685] nvidia: loading out-of-tree module taints kernel.
[    4.945827] nvidia: module license 'NVIDIA' taints kernel.
[    4.971124] nvidia: module verification failed: signature and/or
required key missing - tainting kernel
[    5.034533] nvidia-nvlink: Nvlink Core is being initialized, major
device number 237
               NVRM: nouveau, rivafb, nvidiafb or rivatv
[    5.036086] nvidia-nvlink: Unregistered the Nvlink Core, major device
number 237
[    5.168304] nvidia-nvlink: Nvlink Core is being initialized, major
device number 237
               NVRM: nouveau, rivafb, nvidiafb or rivatv
[    5.168962] nvidia-nvlink: Unregistered the Nvlink Core, major device
number 237
[   25.343678] nvidia-nvlink: Nvlink Core is being initialized, major
device number 237
               NVRM: nouveau, rivafb, nvidiafb or rivatv
[   25.358661] nvidia-nvlink: Unregistered the Nvlink Core, major device
number 237
[   25.444355] nvidia-nvlink: Nvlink Core is being initialized, major
device number 237
               NVRM: nouveau, rivafb, nvidiafb or rivatv
[   25.444678] nvidia-nvlink: Unregistered the Nvlink Core, major device
number 237
[   46.628271] nvidia-nvlink: Nvlink Core is being initialized, major
device number 237
               NVRM: nouveau, rivafb, nvidiafb or rivatv
[   46.628573] nvidia-nvlink: Unregistered the Nvlink Core, major device
number 237

[John M. Harris Jr]

On Thursday, May 21, 2020 4:56:02 PM MST linux guy wrote:
>  Hello fellow Fedorians.
>  
>  I have everything set up to run nvidia drivers for my GTX 1060.   But my
>  machine loads nouveau instead, due to a tainted kernel message.
>  
>  I turned off "Secure Boot" in the BIOS and enabled Compatibility Support
>  Mode - UEFI.
>  
>  How do I force the use of the nvidia driver over nouveau ?
>  
>  Thanks
>  
>  dnf list \*nvidia\*
>  
>  Installed Packages
>  akmod-nvidia.x86_64                                3:440.82-1.fc32
>   @rpmfusion-nonfree
>  kmod-nvidia-5.6.13-300.fc32.x86_64.x86_64          3:440.82-1.fc32
>   @@commandline
>  nvidia-settings.x86_64                             3:440.82-1.fc32
>   @rpmfusion-nonfree
>  xorg-x11-drv-nvidia.x86_64                         3:440.82-1.fc32
>   @rpmfusion-nonfree
>  xorg-x11-drv-nvidia-cuda-libs.x86_64               3:440.82-1.fc32
>   @rpmfusion-nonfree
>  xorg-x11-drv-nvidia-kmodsrc.x86_64                 3:440.82-1.fc32
>   @rpmfusion-nonfree
>  xorg-x11-drv-nvidia-libs.i686                      3:440.82-1.fc32
>   @rpmfusion-nonfree
>  xorg-x11-drv-nvidia-libs.x86_64                    3:440.82-1.fc32
>   @rpmfusion-nonfree
>  
>  # akmods
>  Checking kmods exist for 5.6.13-300.fc32.x86_64            [  OK  ]
>  
>  uname -a
>  Linux bigboy 5.6.13-300.fc32.x86_64 #1 SMP Thu May 14 22:51:37 UTC 2020
>  x86_64 x86_64 x86_64 GNU/
>  
>  dmesg | grep nvidia
>  [    4.945685] nvidia: loading out-of-tree module taints kernel.
>  [    4.945827] nvidia: module license 'NVIDIA' taints kernel.
>  [    4.971124] nvidia: module verification failed: signature and/or
>  required key missing - tainting kernel
>  [    5.034533] nvidia-nvlink: Nvlink Core is being initialized, major
>  device number 237
>                 NVRM: nouveau, rivafb, nvidiafb or rivatv
>  [    5.036086] nvidia-nvlink: Unregistered the Nvlink Core, major device
>  number 237
>  [    5.168304] nvidia-nvlink: Nvlink Core is being initialized, major
>  device number 237
>                 NVRM: nouveau, rivafb, nvidiafb or rivatv
>  [    5.168962] nvidia-nvlink: Unregistered the Nvlink Core, major device
>  number 237
>  [   25.343678] nvidia-nvlink: Nvlink Core is being initialized, major
>  device number 237
>                 NVRM: nouveau, rivafb, nvidiafb or rivatv
>  [   25.358661] nvidia-nvlink: Unregistered the Nvlink Core, major device
>  number 237
>  [   25.444355] nvidia-nvlink: Nvlink Core is being initialized, major
>  device number 237
>                 NVRM: nouveau, rivafb, nvidiafb or rivatv
>  [   25.444678] nvidia-nvlink: Unregistered the Nvlink Core, major device
>  number 237
>  [   46.628271] nvidia-nvlink: Nvlink Core is being initialized, major
>  device number 237
>                 NVRM: nouveau, rivafb, nvidiafb or rivatv
>  [   46.628573] nvidia-nvlink: Unregistered the Nvlink Core, major device
>  number 237 
Loading nvidia is what *causes* the kernel to become tainted. It doesn't 
prevent you from loading nvidia.

-- 
John M. Harris, Jr.
Splentity

[linux guy]

It seems to stop it from loading.  SELinux ?

On Thu, May 21, 2020 at 6:20 PM John M. Harris Jr <johnmh(a)splentity.com&gt;
wrote:

>  On Thursday, May 21, 2020 4:56:02 PM MST linux guy wrote:
>  > Hello fellow Fedorians.
>  >
>  > I have everything set up to run nvidia drivers for my GTX 1060.   But my
>  > machine loads nouveau instead, due to a tainted kernel message.
>  >
>  > I turned off "Secure Boot" in the BIOS and enabled Compatibility Support
>  > Mode - UEFI.
>  >
>  > How do I force the use of the nvidia driver over nouveau ?
>  >
>  > Thanks
>  >
>  > dnf list \*nvidia\*
>  >
>  > Installed Packages
>  > akmod-nvidia.x86_64                                3:440.82-1.fc32
>  >  @rpmfusion-nonfree
>  > kmod-nvidia-5.6.13-300.fc32.x86_64.x86_64          3:440.82-1.fc32
>  >  @@commandline
>  > nvidia-settings.x86_64                             3:440.82-1.fc32
>  >  @rpmfusion-nonfree
>  > xorg-x11-drv-nvidia.x86_64                         3:440.82-1.fc32
>  >  @rpmfusion-nonfree
>  > xorg-x11-drv-nvidia-cuda-libs.x86_64               3:440.82-1.fc32
>  >  @rpmfusion-nonfree
>  > xorg-x11-drv-nvidia-kmodsrc.x86_64                 3:440.82-1.fc32
>  >  @rpmfusion-nonfree
>  > xorg-x11-drv-nvidia-libs.i686                      3:440.82-1.fc32
>  >  @rpmfusion-nonfree
>  > xorg-x11-drv-nvidia-libs.x86_64                    3:440.82-1.fc32
>  >  @rpmfusion-nonfree
>  >
>  > # akmods
>  > Checking kmods exist for 5.6.13-300.fc32.x86_64            [  OK  ]
>  >
>  > uname -a
>  > Linux bigboy 5.6.13-300.fc32.x86_64 #1 SMP Thu May 14 22:51:37 UTC 2020
>  > x86_64 x86_64 x86_64 GNU/
>  >
>  > dmesg | grep nvidia
>  > [    4.945685] nvidia: loading out-of-tree module taints kernel.
>  > [    4.945827] nvidia: module license 'NVIDIA' taints kernel.
>  > [    4.971124] nvidia: module verification failed: signature and/or
>  > required key missing - tainting kernel
>  > [    5.034533] nvidia-nvlink: Nvlink Core is being initialized, major
>  > device number 237
>  >                NVRM: nouveau, rivafb, nvidiafb or rivatv
>  > [    5.036086] nvidia-nvlink: Unregistered the Nvlink Core, major device
>  > number 237
>  > [    5.168304] nvidia-nvlink: Nvlink Core is being initialized, major
>  > device number 237
>  >                NVRM: nouveau, rivafb, nvidiafb or rivatv
>  > [    5.168962] nvidia-nvlink: Unregistered the Nvlink Core, major device
>  > number 237
>  > [   25.343678] nvidia-nvlink: Nvlink Core is being initialized, major
>  > device number 237
>  >                NVRM: nouveau, rivafb, nvidiafb or rivatv
>  > [   25.358661] nvidia-nvlink: Unregistered the Nvlink Core, major device
>  > number 237
>  > [   25.444355] nvidia-nvlink: Nvlink Core is being initialized, major
>  > device number 237
>  >                NVRM: nouveau, rivafb, nvidiafb or rivatv
>  > [   25.444678] nvidia-nvlink: Unregistered the Nvlink Core, major device
>  > number 237
>  > [   46.628271] nvidia-nvlink: Nvlink Core is being initialized, major
>  > device number 237
>  >                NVRM: nouveau, rivafb, nvidiafb or rivatv
>  > [   46.628573] nvidia-nvlink: Unregistered the Nvlink Core, major device
>  > number 237
>
>  Loading nvidia is what *causes* the kernel to become tainted. It doesn't
>  prevent you from loading nvidia.
>
>  --
>  John M. Harris, Jr.
>  Splentity
>
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>

[Ed Greshko]

On 2020-05-22 07:56, linux guy wrote:
>  How do I force the use of the nvidia driver over nouveau ? 
So, you're saying

lsmod | grep nvidia

returns nothing?

And, just to check, what is the output of....

cat /proc/cmdline

-- 
The key to getting good answers is to ask good questions.

[linux guy]

Thanks for the replies.

$ lsmod | grep nvidia

$ lsmod | grep nouveau
nouveau              2338816  32
video                  53248  2 asus_wmi,nouveau
mxm_wmi                16384  1 nouveau
i2c_algo_bit           16384  1 nouveau
drm_kms_helper        241664  1 nouveau
ttm                   122880  1 nouveau
drm                   598016  26 drm_kms_helper,ttm,nouveau
wmi                    36864  4 asus_wmi,wmi_bmof,mxm_wmi,nouveau

$ cat /proc/cmdline
BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.6.13-300.fc32.x86_64
root=/dev/mapper/fedora_localhost--live-root ro
resume=/dev/mapper/fedora_localhost--live-swap
rd.lvm.lv=fedora_localhost-live/root
rd.lvm.lv=fedora_localhost-live/swap rhgb quiet



On Thu, May 21, 2020 at 6:49 PM Ed Greshko <ed.greshko(a)greshko.com&gt; wrote:

>  On 2020-05-22 07:56, linux guy wrote:
>  > How do I force the use of the nvidia driver over nouveau ?
>
>  So, you're saying
>
>  lsmod | grep nvidia
>
>  returns nothing?
>
>  And, just to check, what is the output of....
>
>  cat /proc/cmdline
>
>  --
>  The key to getting good answers is to ask good questions.
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>

[Ed Greshko]

On 2020-05-22 10:23, linux guy wrote:
>  $ cat /proc/cmdline
>  BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.6.13-300.fc32.x86_64
> root=/dev/mapper/fedora_localhost--live-root ro
> resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv
> <http://rd.lvm.lv>=fedora_localhost-live/root rd.lvm.lv
> <http://rd.lvm.lv>=fedora_localhost-live/swap rhgb quiet 
Well, there's the problem.  It seems the install of the nvidia packages didn't
alter the boot parameters.
That line should look like....

BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.6.13-300.fc32.x86_64
root=UUID=4455f2e9-fed2-4e1e-856d-642b531547f9 ro rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau nvidia-drm.modeset=1 nomodeset

So, nouveau isn't getting blacklisted.

What is the output of....

grub2-editenv list

-- 
The key to getting good answers is to ask good questions.

[linux guy]

Isn't this interesting...

# grub2-editenv list
saved_entry=c1d3ebaecd08428ba86f4aba3749efca-5.6.13-300.fc32.x86_64
boot_success=1
kernelopts=root=/dev/mapper/fedora_localhost--live-root ro
rd.lvm.lv=fedora/root
rd.lvm.lv=fedora/swap rhgb quiet rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau nvidia-drm.modeset=1
boot_indeterminate=1

[linux guy]

Do I need to modprobe nvidia or something ?

[Ed Greshko]

On 2020-05-22 10:47, linux guy wrote:
>  Isn't this interesting...
>
>  # grub2-editenv list
>  saved_entry=c1d3ebaecd08428ba86f4aba3749efca-5.6.13-300.fc32.x86_64
>  boot_success=1
>  kernelopts=root=/dev/mapper/fedora_localhost--live-root ro rd.lvm.lv
> <http://rd.lvm.lv>=fedora/root rd.lvm.lv <http://rd.lvm.lv>=fedora/swap rhgb
> quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1
>  boot_indeterminate=1
>
>  
Your kernelopts in the env don't match the /proc/cmdline.

Can you boot and then check/edit the "linux" line?

The most important part is "rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
nvidia-drm.modeset=1"

And boot including those parameters? 

Also, you would want to check /var/cache/akmods/akmods.log to ensure the driver for the
running
kernel is built.  The driver itself will be located in /usr/lib/modules/`uname
-r`/extra/nvidia

[root@meimei ~]# ls /usr/lib/modules/`uname -r`/extra/nvidia
nvidia-drm.ko  nvidia.ko  nvidia-modeset.ko  nvidia-uvm.ko



-- 
The key to getting good answers is to ask good questions.

[linux guy]

Comments below.

On Thu, May 21, 2020 at 9:03 PM Ed Greshko <ed.greshko(a)greshko.com&gt; wrote:

>  On 2020-05-22 10:47, linux guy wrote:
>  > Isn't this interesting...
> >  
>  > # grub2-editenv list
>  > saved_entry=c1d3ebaecd08428ba86f4aba3749efca-5.6.13-300.fc32.x86_64
>  > boot_success=1
>  > kernelopts=root=/dev/mapper/fedora_localhost--live-root ro rd.lvm.lv <
>  http://rd.lvm.lv>=fedora/root rd.lvm.lv <http://rd.lvm.lv>=fedora/swap
>  rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
>  nvidia-drm.modeset=1
>  > boot_indeterminate=1
> >  
> >  
>  Your kernelopts in the env don't match the /proc/cmdline.
>  
Yes.   How can that be ?

Can you boot and then check/edit the "linux" line?
>  
You mean cat  /proc/cmdline ?

How do I edit it ?



> The most important part is "rd.driver.blacklist=nouveau
> modprobe.blacklist=nouveau nvidia-drm.modeset=1"
>  
Agreed.

And boot including those parameters?
>  
How ?   I was comfortable with grub, but I'm lost with these new boot
systems.

Also, you would want to check /var/cache/akmods/akmods.log to ensure the
> driver for the running
> kernel is built.  The driver itself will be located in
> /usr/lib/modules/`uname -r`/extra/nvidia
>  
$ dnf list \*kmod\*

Installed Packages
akmod-nvidia.x86_64                             3:440.82-1.fc32
@rpmfusion-nonfree
akmods.noarch                                   0.5.6-25.fc32
@fedora
kmod.x86_64                                     27-1.fc32
@fedora
kmod-libs.x86_64                                27-1.fc32
@fedora
kmod-nvidia-5.6.13-300.fc32.x86_64.x86_64       3:440.82-1.fc32
@@commandline            << HERE IT IS.


kmodtool.noarch                                 1-38.fc32
@fedora
libmikmod.x86_64                                3.3.11.1-8.fc32
@fedora
xorg-x11-drv-nvidia-kmodsrc.x86_64              3:440.82-1.fc32
@rpmfusion-nonfree

Also:

$ ls /usr/lib/modules/`uname -r`/extra/nvidia
nvidia-drm.ko  nvidia.ko  nvidia-modeset.ko  nvidia-uvm.ko

[linux guy]

I rebooted, same result.

$ cat /proc/cmdline
BOOT_IMAGE=(hd1,gpt2)/vmlinuz-5.6.13-300.fc32.x86_64
root=/dev/mapper/fedora_localhost--live-root ro
resume=/dev/mapper/fedora_localhost--live-swap
rd.lvm.lv=fedora_localhost-live/root
rd.lvm.lv=fedora_localhost-live/swap rhgb quiet

# grub2-editenv list
saved_entry=c1d3ebaecd08428ba86f4aba3749efca-5.6.13-300.fc32.x86_64
boot_success=1
kernelopts=root=/dev/mapper/fedora_localhost--live-root ro
rd.lvm.lv=fedora/root
rd.lvm.lv=fedora/swap rhgb quiet rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau nvidia-drm.modeset=1
boot_indeterminate=1

How do I fix this ?







On Thu, May 21, 2020 at 9:19 PM linux guy <linuxguy123(a)gmail.com&gt; wrote:

>  Comments below.
>
>  On Thu, May 21, 2020 at 9:03 PM Ed Greshko <ed.greshko(a)greshko.com&gt; wrote:
>
> > On 2020-05-22 10:47, linux guy wrote:
> > > Isn't this interesting...
> > >
> > > # grub2-editenv list
> > > saved_entry=c1d3ebaecd08428ba86f4aba3749efca-5.6.13-300.fc32.x86_64
> > > boot_success=1
> > > kernelopts=root=/dev/mapper/fedora_localhost--live-root ro rd.lvm.lv <
> > http://rd.lvm.lv>=fedora/root rd.lvm.lv <http://rd.lvm.lv>=fedora/swap
> > rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
> > nvidia-drm.modeset=1
> > > boot_indeterminate=1
> > >
> > >
> >
> > Your kernelopts in the env don't match the /proc/cmdline.
> >
>
>  Yes.   How can that be ?
>
>  Can you boot and then check/edit the "linux" line?
> >
>
>  You mean cat  /proc/cmdline ?
>
>  How do I edit it ?
>
>
>
> > The most important part is "rd.driver.blacklist=nouveau
> > modprobe.blacklist=nouveau nvidia-drm.modeset=1"
> >
>
>  Agreed.
>
>  And boot including those parameters?
> >
>
>  How ?   I was comfortable with grub, but I'm lost with these new boot
>  systems.
>
>  Also, you would want to check /var/cache/akmods/akmods.log to ensure the
> > driver for the running
> > kernel is built.  The driver itself will be located in
> > /usr/lib/modules/`uname -r`/extra/nvidia
> >
>
>  $ dnf list \*kmod\*
>
>  Installed Packages
>  akmod-nvidia.x86_64                             3:440.82-1.fc32
>    @rpmfusion-nonfree
>  akmods.noarch                                   0.5.6-25.fc32
>    @fedora
>  kmod.x86_64                                     27-1.fc32
>    @fedora
>  kmod-libs.x86_64                                27-1.fc32
>    @fedora
>  kmod-nvidia-5.6.13-300.fc32.x86_64.x86_64       3:440.82-1.fc32
>    @@commandline            << HERE IT IS.
>
>
>  kmodtool.noarch                                 1-38.fc32
>    @fedora
>  libmikmod.x86_64                                3.3.11.1-8.fc32
>    @fedora
>  xorg-x11-drv-nvidia-kmodsrc.x86_64              3:440.82-1.fc32
>    @rpmfusion-nonfree
>
>  Also:
>
>  $ ls /usr/lib/modules/`uname -r`/extra/nvidia
>  nvidia-drm.ko  nvidia.ko  nvidia-modeset.ko  nvidia-uvm.ko
>
>
>

[Ed Greshko]

On 2020-05-22 11:34, linux guy wrote:
>  I rebooted, same result.
>
>  $ cat /proc/cmdline
>  BOOT_IMAGE=(hd1,gpt2)/vmlinuz-5.6.13-300.fc32.x86_64
> root=/dev/mapper/fedora_localhost--live-root ro
> resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv
> <http://rd.lvm.lv>=fedora_localhost-live/root rd.lvm.lv
> <http://rd.lvm.lv>=fedora_localhost-live/swap rhgb quiet
>
>  # grub2-editenv list
>  saved_entry=c1d3ebaecd08428ba86f4aba3749efca-5.6.13-300.fc32.x86_64
>  boot_success=1
>  kernelopts=root=/dev/mapper/fedora_localhost--live-root ro rd.lvm.lv
> <http://rd.lvm.lv>=fedora/root rd.lvm.lv <http://rd.lvm.lv>=fedora/swap rhgb
> quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1
>  boot_indeterminate=1
>
>  How do I fix this ?
>  
I don't know at the moment.

But, to be clear, after you edited the "linux" line you did a "Ctrl-x"
to stat the boot.

And one thing doesn't make sense.

Earlier you wrote....

$ cat /proc/cmdline
BOOT_IMAGE=(hd0,gpt2)/vmlinuz-5.6.13-300.fc32.x86_64
root=/dev/mapper/fedora_localhost--live-root ro
resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv
<http://rd.lvm.lv>=fedora_localhost-live/root rd.lvm.lv
<http://rd.lvm.lv>=fedora_localhost-live/swap rhgb quiet

As you can see, they are different.  hd0,gpt2 v.s. hd1,gpt2



-- 
The key to getting good answers is to ask good questions.

[linux guy]

"As you can see, they are different.  hd0,gpt2 v.s. hd1,gpt2"

Good catch.  I have no idea what is going on here.

I miss the old days of /dev/sda1  and grub.conf

[linux guy]

But they are both 5.6.13-300 !   I have a very poor understanding of lvm
stuff.

On Thu, May 21, 2020 at 11:21 PM linux guy <linuxguy123(a)gmail.com&gt; wrote:

>  "As you can see, they are different.  hd0,gpt2 v.s.
> hd1,gpt2"
>
>  Good catch.  I have no idea what is going on here.
>
>  I miss the old days of /dev/sda1  and grub.conf
>
>
>

[linux guy]

Good news !  (Sort of...)

I rebooted and edited the boot command of my kernel in grub, using e... and
then booted it.
I added the following to the command line:  rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau nvidia-drm.modeset=1

This caused the kernel to boot with nvidia instead of nouveau.   Even
better, the nvidia driver decreased my CPU load tremendously in the
application that I was working with.  From 90% (barely useable) to 30%
(loafing along).

Now I just need to figure out what is going on with my boot setup.

Thanks for all the help!

[linux guy]

Relevant discussion of Nvidia graphics card performance with nouveau versus
an nvidia driver:
https://www.phoronix.com/scan.php?page=article&item=nouveau-summer-20...

[Ed Greshko]

On 2020-05-22 14:52, linux guy wrote:
>  Good news !  (Sort of...)
>
>  I rebooted and edited the boot command of my kernel in grub, using e... and then booted
> it.
>  I added the following to the command line:  rd.driver.blacklist=nouveau
> modprobe.blacklist=nouveau nvidia-drm.modeset=1
>
>  This caused the kernel to boot with nvidia instead of nouveau.   Even better, the nvidia
> driver decreased my CPU load tremendously in the application that I was working with. 
> From 90% (barely useable) to 30% (loafing along).
>
>  Now I just need to figure out what is going on with my boot setup.
>  
It sounds to me as if the old grub methods are being used.  Or at least confused.

What do you get for

grep BLSCFG /etc/default/grub


-- 
The key to getting good answers is to ask good questions.

[John Pilkington]

On 22/05/2020 07:52, linux guy wrote:
>  Good news !  (Sort of...)
>  
>  I rebooted and edited the boot command of my kernel in grub, using e... 
>  and then booted it.
>  I added the following to the command line:  rd.driver.blacklist=nouveau 
>  modprobe.blacklist=nouveau nvidia-drm.modeset=1
>  
>  This caused the kernel to boot with nvidia instead of nouveau.   Even 
>  better, the nvidia driver decreased my CPU load tremendously in the 
>  application that I was working with.  From 90% (barely useable) to 30% 
>  (loafing along).
>  
>  Now I just need to figure out what is going on with my boot setup.
>  
>  Thanks for all the help! 
In the past it has seemed to me that switching between the nouveau and 
rpmfusion nvidia drivers was easy, provided that the wanted driver was 
the one installed most recently.  Otherwise you may get blacklist 
troubles.  Just a thought.

John P

[Ed Greshko]

On 2020-05-22 11:19, linux guy wrote:
>  Comments below.
>
>  On Thu, May 21, 2020 at 9:03 PM Ed Greshko <ed.greshko(a)greshko.com
> <mailto:[e-mail]>> wrote:
>
>      On 2020-05-22 10:47, linux guy wrote:
>      > Isn't this interesting...
>      >
>      > # grub2-editenv list
>      > saved_entry=c1d3ebaecd08428ba86f4aba3749efca-5.6.13-300.fc32.x86_64
>      > boot_success=1
>      > kernelopts=root=/dev/mapper/fedora_localhost--live-root ro rd.lvm.lv
> <http://rd.lvm.lv> <http://rd.lvm.lv>=fedora/root rd.lvm.lv
> <http://rd.lvm.lv> <http://rd.lvm.lv>=fedora/swap rhgb quiet
> rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1
>      > boot_indeterminate=1
>      >
>      >
>
>      Your kernelopts in the env don't match the /proc/cmdline.
>
>
>  Yes.   How can that be ? 
I don't know.  I too am not a "grub" person.

>      Can you boot and then check/edit the "linux" line?
>
>
>  You mean cat  /proc/cmdline ? 
No. When you boot, I seem to recall you're an Xfce user?, you have a choice of kernels
to boot.
Hit "e" and it gets you to a screen to find the "linux" line and edit
it.

This is a "temporary" edit that doesn't survive boots.

>      The most important part is "rd.driver.blacklist=nouveau
> modprobe.blacklist=nouveau nvidia-drm.modeset=1"
>
>
>  Agreed.
>
>      And boot including those parameters? 
>
>
>  How ?   I was comfortable with grub, but I'm lost with these new boot systems.
>
>      Also, you would want to check /var/cache/akmods/akmods.log to ensure the driver for
> the running
>      kernel is built.  The driver itself will be located in /usr/lib/modules/`uname
> -r`/extra/nvidia
>
>
>  $ dnf list \*kmod\* 
The suggestion to check the log was to look for....

2020/05/20 15:26:42 akmods: Building and installing nvidia-kmod
2020/05/20 15:26:42 akmods: Building RPM using the command '/sbin/akmodsbuild
--kernels 5.6.13-300.fc32.x86_64 /usr/src/akmods/nvidia-kmod.latest'
2020/05/20 15:27:58 akmods: Installing newly built rpms
2020/05/20 15:27:58 akmods: DNF detected
2020/05/20 15:28:07 akmods: Successful.

>  Also:
>
>  $ ls /usr/lib/modules/`uname -r`/extra/nvidia
>  nvidia-drm.ko  nvidia.ko  nvidia-modeset.ko  nvidia-uvm.ko 
But they are there, so they were built

You may have to wait for others better prepared to diagnose/fix grub issues.


-- 
The key to getting good answers is to ask good questions.

[stan]

On Thu, 21 May 2020 20:47:18 -0600
linux guy <linuxguy123(a)gmail.com&gt; wrote:

>  Isn't this interesting...
>  
>  # grub2-editenv list
>  saved_entry=c1d3ebaecd08428ba86f4aba3749efca-5.6.13-300.fc32.x86_64
>  boot_success=1
>  kernelopts=root=/dev/mapper/fedora_localhost--live-root ro
>  rd.lvm.lv=fedora/root
>  rd.lvm.lv=fedora/swap rhgb quiet rd.driver.blacklist=nouveau
>  modprobe.blacklist=nouveau nvidia-drm.modeset=1
>  boot_indeterminate=1 
What does /etc/default/grub show?  e.g. cat /etc/default/grub
You should have the line
GRUB_ENABLE_BLSCFG=true 
so that you are using boot loader snippets.

What is in /boot/loader/entries?

What is in /boot/efi/EFI/fedora/grub.cfg?
After you are sure that /etc/default/grub is correct
(GRUB_CMDLINE_LINUX= what you expect), move that to a backup file, and
run 
grub2-mkconfig -o grub.cfg
in /boot/efi/EFI/fedora/.  Then do a diff of the backup and the new
file.  Are there any differences?  Do a boot with the new config file,
does it work correctly?

You should turn off rhgb and quiet during boot by pressing space bar
repeatedly during boot, and editing the boot line using e.  Then, if
something goes wrong, you can see what is happening.

[linux guy]

Thanks for the tips, guys.  I'll test them when I have time next week.

On Fri, May 22, 2020 at 11:55 AM stan via users <
users(a)lists.fedoraproject.org&gt; wrote:

>  On Thu, 21 May 2020 20:47:18 -0600
>  linux guy <linuxguy123(a)gmail.com&gt; wrote:
>
>  > Isn't this interesting...
>  >
>  > # grub2-editenv list
>  > saved_entry=c1d3ebaecd08428ba86f4aba3749efca-5.6.13-300.fc32.x86_64
>  > boot_success=1
>  > kernelopts=root=/dev/mapper/fedora_localhost--live-root ro
>  > rd.lvm.lv=fedora/root
>  > rd.lvm.lv=fedora/swap rhgb quiet rd.driver.blacklist=nouveau
>  > modprobe.blacklist=nouveau nvidia-drm.modeset=1
>  > boot_indeterminate=1
>
>  What does /etc/default/grub show?  e.g. cat /etc/default/grub
>  You should have the line
>  GRUB_ENABLE_BLSCFG=true
>  so that you are using boot loader snippets.
>
>  What is in /boot/loader/entries?
>
>  What is in /boot/efi/EFI/fedora/grub.cfg?
>  After you are sure that /etc/default/grub is correct
>  (GRUB_CMDLINE_LINUX= what you expect), move that to a backup file, and
>  run
>  grub2-mkconfig -o grub.cfg
>  in /boot/efi/EFI/fedora/.  Then do a diff of the backup and the new
>  file.  Are there any differences?  Do a boot with the new config file,
>  does it work correctly?
>
>  You should turn off rhgb and quiet during boot by pressing space bar
>  repeatedly during boot, and editing the boot line using e.  Then, if
>  something goes wrong, you can see what is happening.
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>

[Ed Greshko]

On 2020-05-23 04:47, linux guy wrote:
>  Thanks for the tips, guys.  I'll test them when I have time next
> week. 
Don't wait too long.  Some people may forget what was said/done and be forced to
review things.  :-) :-)

-- 
The key to getting good answers is to ask good questions.