On 2020-05-22 11:19, linux guy wrote:
On Thu, May 21, 2020 at 9:03 PM Ed Greshko <ed.greshko(a)greshko.com
On 2020-05-22 10:47, linux guy wrote:
> Isn't this interesting...
> # grub2-editenv list
> kernelopts=root=/dev/mapper/fedora_localhost--live-root ro rd.lvm.lv
rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=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
Hit "e" and it gets you to a screen to find the "linux" line and edit
This is a "temporary" edit that doesn't survive boots.
The most important part is "rd.driver.blacklist=nouveau
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
kernel is built. The driver itself will be located in /usr/lib/modules/`uname
$ 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.
$ 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.