Re: Nouveau Blacklisting not in /etc/default/grub

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



/proc/cmdline has existed for a long time (>25 years).  It shows what
the active kernel command line is for the current boot.   It is the
source of truth of how the kernel was last booted.

The new kernel install always takes one of the boot lines and uses
that exact line for the newly installed kernel.

On Mon, Oct 31, 2022 at 6:00 PM Stephen Morris <samorris@xxxxxxxxxxxxxxx> wrote:
>
> On 31/10/22 21:12, Roger Heflin wrote:
>
> What does cat /proc/cmdline show for the current kernel parameters?
>
> It shows the blacklisting of the nouveau drivers in there. Is that a change with the 6.0.5 kernel, prior to that kernel they were always in /etc/default/grub?
> Just looking at grub.cfg I have now found that while I thought I was boot off the 6.0.5 kernel, I hadn't actually run grub2-mkconfig to update grub.cfg for the new kernel. I have run that now and because /etc/default/grub no longer has the nouveau blacklisting statements they are not supplied on the kernel line in grub.cfg for any kernels it's set up to boot from. From below /proc/cmdline has also not been updated for the 6.0.5 kernel either, I'll see what it shows when I get a chance to boot off that kernel.
>
> cat /proc/cmdline
> BOOT_IMAGE=/vmlinuz-5.19.16-200.fc36.x86_64 root=UUID=ba36dde9-5bf1-4140-89e7-b82ee1fe7cf9 ro rootflags=subvol=Fedora_root rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1
>
> regards,
> Steve
>
>
> On Mon, Oct 31, 2022 at 2:53 AM Stephen Morris <samorris@xxxxxxxxxxxxxxx> wrote:
>
> On 31/10/22 13:48, Samuel Sieb wrote:
>
> On 10/30/22 19:26, Stephen Morris wrote:
>
> On 31/10/22 09:12, Samuel Sieb wrote:
>
> On 10/30/22 14:54, Stephen Morris wrote:
>
>              I then ran lsmod | grep -i nvidia
>              Does the following display from lsmod indicate that
> the nvidia module has not installed properly? I don't have the drm
> module and the blacklisting of nouveau and the nvidia modeset
> parameter have not been added to the kernel parameters in
> /etc/default/grub, or is it that I did not force a rebuild of the
> kernel module and I did not force an update of the boot image?
>
> lsmod | grep -i nvidia
> nvidia_drm             73728  32
> nvidia_modeset       1187840  65 nvidia_drm
> nvidia_uvm           1318912  0
> nvidia             55242752  2950 nvidia_uvm,nvidia_modeset
>
> Which drm module don't you have?  The listing shows it.  Also, there
> are no nouveau modules listed, so the blacklisting is working.
>
> /etc/default/grub is only used if you fully regenerate the grub.cfg
> file.
>
> I use /etc/default/grub as I always fully regenerate the grub.cfg
> file via grub2-mkconfig.
> Normally the install of akmod-nvidia, kmod-nvidia put the
> blacklisting of nouveau and the nvidia modeset parameters in
> /etc/default/grub, but this time they didn't, which is the first time
> I've seen that issue. I'm also not sure how the nvidia driver has
> been loaded when there are no kernel parameters to do so.
>
> The kernel module will get auto-loaded because it matches the
> hardware. There's probably a blacklist file in /etc/modprobe.d.
>
> There doesn't appear to be a blacklist file in that location for
> nouveau. Maybe the install scripts modified the initrd file, but I
> thought that methodology wasn't used anymore in favour of the kernel
> parameters.
>
> The reason I was querying the display from lsmod is that the web link
> where I got the instructions from for updating the secure boot data
> for fedora showed sample lsmod output as evidence that the signing
> and rebuild had worked correctly, and it was the last two lines in
> the display that I'm querying whether I should have as well (the i915
> is not relevant to me)?
>
> |nvidia_drm 73728 1 nvidia_modeset 1150976 2 nvidia_drm nvidia
> 36954112 129 nvidia_modeset drm_kms_helper 311296 2 nvidia_drm,i915
> drm 630784 28 drm_kms_helper,nvidia,nvidia_drm,i915,ttm |
>
> It looks like they have dual graphics.  Assuming your display is
> working, it's fine.
>
> Yeah, he may do.
> Thankyou for you responses Samuel.
>
> regards,
> Steve
>
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> 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/users@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> 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/users@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> 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/users@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
>
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> 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/users@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux