4:54 p.m.
Hi,
Having secureboot in the bios set to "Windows Mode" I have manually
signed the nvidia drivers after uninstalling akmod-nvidia and
kmod-nvidia and all the associated packages.
I then:
generated a signing key using kmodgenca
ran mokutil to import the generated key
rebooted
And at the MOK Manager interface I enrolled the key and
rebooted again
Then once in KDE I reinstalled akmod-nvidia and kmod-nvidia
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
regards,
Steve
5:03 p.m.
On 10/30/2022 03:54 PM, Stephen Morris wrote:
Then once in KDE I reinstalled akmod-nvidia and kmod-nvidia
Installing both akmod-nvidia and kmod-nvidia is redundant. At boot,
akmod-nvidia checks to see if you have the appropriate kmod for the
running kernel. If so, it exits; if not, it builds it. The only time
it's going to make a difference is in the fairly rare case that the new
kmod-nvidia is delayed.
5:12 p.m.
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.
9:26 p.m.
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 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 |
|regards,|
|Steve|
||
_______________________________________________
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/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
9:48 p.m.
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.
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.
2:52 a.m.
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(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/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
5:12 a.m.
What does cat /proc/cmdline show for the current kernel parameters?
On Mon, Oct 31, 2022 at 2:53 AM Stephen Morris <samorris(a)netspace.net.au> 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(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/users@lists.fedoraproject.org
> > Do not reply to spam, report it:
> > https://pagure.io/fedora-infrastructure/new_issue
> _______________________________________________
> 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/users@lists.fedoraproject.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
5:59 p.m.
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(a)netspace.net.au> 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(a)lists.fedoraproject.org
>> To unsubscribe send an email tousers-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/users@lists.fedoraproject.org
>> Do not reply to spam, report it:
>> https://pagure.io/fedora-infrastructure/new_issue
> _______________________________________________
> users mailing list --users(a)lists.fedoraproject.org
> To unsubscribe send an email tousers-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/users@lists.fedora...
> Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
users mailing list --users(a)lists.fedoraproject.org
To unsubscribe send an email tousers-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/users@lists.fedora...
Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue
6:32 p.m.
/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(a)netspace.net.au> 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(a)netspace.net.au>
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(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/users@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
> _______________________________________________
> 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/users@lists.fedoraproject.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> _______________________________________________
> 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/users@lists.fedoraproject.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
>
> _______________________________________________
> 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/users@lists.fedoraproject.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
10:14 p.m.
On 1/11/22 10:32, Roger Heflin wrote:
/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.
I've just managed to get the
6.0.5 kernel to load the nvidia driver.
There is potentially a defect in the akmod-nvidia (or relevant package)
scripts in that it seems that they no longer add the blacklisting
statements for nouveau into the kernel parameters in /etc/default/grub,
I had to put those statements in there manually before the nvidia driver
was loaded instead of the nouveau driver.
regards,
Steve
On Mon, Oct 31, 2022 at 6:00 PM Stephen Morris <samorris(a)netspace.net.au> 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(a)netspace.net.au>
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(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/users@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
> _______________________________________________
> 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/users@lists.fedoraproject.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> _______________________________________________
> 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/users@lists.fedoraproject.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
>
> _______________________________________________
> 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/users@lists.fedoraproject.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
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/users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
6:53 a.m.
On Tue, Nov 1, 2022 at 4:15 AM Stephen Morris <samorris(a)netspace.net.au> wrote:
I've just managed to get the 6.0.5 kernel to load the nvidia
driver.
There is potentially a defect in the akmod-nvidia (or relevant package)
scripts in that it seems that they no longer add the blacklisting
statements for nouveau into the kernel parameters in /etc/default/grub,
I had to put those statements in there manually before the nvidia driver
was loaded instead of the nouveau driver.
/etc/default/grub - contains default kernel options
/boot/grub2/grubenv - has the line
saved_entry=<id>
which refers to
/boot/loader/entries/<id>.conf
which contains kernel options for the entry (which are actually used)
which get modified when editing kernel options via grub menu (thus becom
ing persistent)
/etc/default/grub - contains the line
GRUB_ENABLE_BLSCFG=true
which is documented at
https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault
greg
3:46 p.m.
On 1 Nov 2022, at 11:53, greg <poisson02+fedora(a)gmail.com>
wrote:
On Tue, Nov 1, 2022 at 4:15 AM Stephen Morris <samorris(a)netspace.net.au> wrote:
> I've just managed to get the 6.0.5 kernel to load the nvidia driver.
> There is potentially a defect in the akmod-nvidia (or relevant package)
> scripts in that it seems that they no longer add the blacklisting
> statements for nouveau into the kernel parameters in /etc/default/grub,
> I had to put those statements in there manually before the nvidia driver
> was loaded instead of the nouveau driver.
I think it is because it is no longer needed. My memory on this prompted by reply in
another thread.
If nvidia fails to be available, not install or did not build, then nouveau is used.
Barry
/etc/default/grub - contains default kernel options
/boot/grub2/grubenv - has the line
saved_entry=<id>
which refers to
/boot/loader/entries/<id>.conf
which contains kernel options for the entry (which are actually used)
which get modified when editing kernel options via grub menu (thus becom
ing persistent)
/etc/default/grub - contains the line
GRUB_ENABLE_BLSCFG=true
which is documented at
https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault
greg
_______________________________________________
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/users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
4:50 p.m.
On 11/1/22 16:46, Barry Scott wrote:
> On 1 Nov 2022, at 11:53, greg <poisson02+fedora(a)gmail.com> wrote:
>
> On Tue, Nov 1, 2022 at 4:15 AM Stephen Morris <samorris(a)netspace.net.au>
wrote:
>> I've just managed to get the 6.0.5 kernel to load the nvidia driver.
>> There is potentially a defect in the akmod-nvidia (or relevant package)
>> scripts in that it seems that they no longer add the blacklisting
>> statements for nouveau into the kernel parameters in /etc/default/grub,
>> I had to put those statements in there manually before the nvidia driver
>> was loaded instead of the nouveau driver.
I think it is because it is no longer needed. My memory on this prompted by reply in
another thread.
If nvidia fails to be available, not install or did not build, then nouveau is used.
Barry
> /etc/default/grub - contains default kernel options
> /boot/grub2/grubenv - has the line
> saved_entry=<id>
> which refers to
> /boot/loader/entries/<id>.conf
> which contains kernel options for the entry (which are actually used)
> which get modified when editing kernel options via grub menu (thus becom
> ing persistent)
>
> /etc/default/grub - contains the line
> GRUB_ENABLE_BLSCFG=true
> which is documented at
> https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault
Things seem to be in quite a mess. The grub.cfg file is almost
irrelevant with only the Windows chainloader stanza having any meaning.
It doesn't get updated with new kernals. Only
/boot/loader/entries/*.conf. With the appropriate entries in /boot and
/boot/loader/entries/*.conf multiple fedora invocations and centOS8 show
in the menu and are boot-able. Not sure where blscfg comes in to the
process. Dynamic change is far out stripping documentation.
4:57 p.m.
On 11/1/22 14:50, Robert McBroom via users wrote:
On 11/1/22 16:46, Barry Scott wrote:
>
>> On 1 Nov 2022, at 11:53, greg <poisson02+fedora(a)gmail.com> wrote:
>> /etc/default/grub - contains the line
>> GRUB_ENABLE_BLSCFG=true
>> which is documented at
>> https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault
>
Things seem to be in quite a mess. The grub.cfg file is almost
irrelevant with only the Windows chainloader stanza having any meaning.
It doesn't get updated with new kernals. Only
/boot/loader/entries/*.conf. With the appropriate entries in /boot and
/boot/loader/entries/*.conf multiple fedora invocations and centOS8 show
in the menu and are boot-able. Not sure where blscfg comes in to the
process. Dynamic change is far out stripping documentation.
blscfg is documented at the link given there. It refers to the files in
/boot/loader/entries.
5:34 p.m.
On 2/11/22 08:57, Samuel Sieb wrote:
On 11/1/22 14:50, Robert McBroom via users wrote:
> On 11/1/22 16:46, Barry Scott wrote:
>>
>>> On 1 Nov 2022, at 11:53, greg <poisson02+fedora(a)gmail.com> wrote:
>>> /etc/default/grub - contains the line
>>> GRUB_ENABLE_BLSCFG=true
>>> which is documented at
>>> https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault
>>
> Things seem to be in quite a mess. The grub.cfg file is almost
> irrelevant with only the Windows chainloader stanza having any
> meaning. It doesn't get updated with new kernals. Only
> /boot/loader/entries/*.conf. With the appropriate entries in /boot
> and /boot/loader/entries/*.conf multiple fedora invocations and
> centOS8 show in the menu and are boot-able. Not sure where blscfg
> comes in to the process. Dynamic change is far out stripping
> documentation.
blscfg is documented at the link given there. It refers to the files
in /boot/loader/entries.
I have blscfg disabled in /etc/default/grub because I hate
it functionality.
/etc/default/grub is still significant if using grub2-mkconfig, it may
be supplemented from the other locations, but what is in there is still
honoured.
What seems to be the problem now, which may be the rpmfusion environment
or may be Fedora, is that they don't play properly with full secureboot.
What I'm experiencing is that in full secureboot mode is the install of
the nvidia packages from either rpmfusion-nonfree or from
rpmfusion-nonfree-nvidia, which ever one dnf is using, does not add the
nouveau blacklisting parameters and the nvidia modeset parameter into
the kernel parameters in /etc/default/grub that are added in non-full
secureboot mode.
The grub menu is extremely relevant, at least for me, when booting
between Fedora, Windows and Ubuntu, albeit ignoring the os-prober
functionality that is wrong (it boots Ubuntu from the wrong partition
for UEFI, but even though it is wrong Ubuntu still boots anyway, and
ignoring the fact that Ubuntu ignores certain configuration
specifications at install time, at least if in UEFI mode.
regards,
Steve
_______________________________________________
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/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
5:20 p.m.
On 2/11/22 07:46, Barry Scott wrote:
> On 1 Nov 2022, at 11:53, greg <poisson02+fedora(a)gmail.com> wrote:
>
> On Tue, Nov 1, 2022 at 4:15 AM Stephen Morris <samorris(a)netspace.net.au>
wrote:
>> I've just managed to get the 6.0.5 kernel to load the nvidia driver.
>> There is potentially a defect in the akmod-nvidia (or relevant package)
>> scripts in that it seems that they no longer add the blacklisting
>> statements for nouveau into the kernel parameters in /etc/default/grub,
>> I had to put those statements in there manually before the nvidia driver
>> was loaded instead of the nouveau driver.
I think it is because it is no longer needed. My memory on this prompted by reply in
another thread.
If nvidia fails to be available, not install or did not build, then nouveau is used.
The nouveau blacklisting parameters were added to /etc/default/grub
before I embarked on adding the signing keys for the nvidia driver into
secureboot. Those parameters are still required as even though
akmod/kmod is providing the driver for the booted kernel without those
parameters in /etc/default/grub and propagated into grub.cfg via
grub2-mkconfig the nouveau driver is used instead. What seems to be the
functionality now is, if the nvidia driver can't be loaded for whatever
reason the system does a fail over to nouveau, and produces a message to
that effect, even if the blacklisting parameters are specified. I was in
that situation when I changed the secureboot mode and lack of signing
was preventing the nvidia driver from being loaded by the kernel (in
full secure boot mode the kernel won't allow non-signed drivers to be
loaded). What I found was that after activating full secureboot the
install of akmod-nvidia, kmod-nvidia and all the associated packages no
longer added the parameters into /etc/default/grub.
regards,
Steve
Barry
> /etc/default/grub - contains default kernel options
> /boot/grub2/grubenv - has the line
> saved_entry=<id>
> which refers to
> /boot/loader/entries/<id>.conf
> which contains kernel options for the entry (which are actually used)
> which get modified when editing kernel options via grub menu (thus becom
> ing persistent)
>
> /etc/default/grub - contains the line
> GRUB_ENABLE_BLSCFG=true
> which is documented at
> https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault
>
> greg
> _______________________________________________
> 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/users@lists.fedoraproject.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
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/users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
4:53 p.m.
On 1/11/22 22:53, greg wrote:
On Tue, Nov 1, 2022 at 4:15 AM Stephen
Morris<samorris(a)netspace.net.au> wrote:
> I've just managed to get the 6.0.5 kernel to load the nvidia driver.
> There is potentially a defect in the akmod-nvidia (or relevant package)
> scripts in that it seems that they no longer add the blacklisting
> statements for nouveau into the kernel parameters in /etc/default/grub,
> I had to put those statements in there manually before the nvidia driver
> was loaded instead of the nouveau driver.
/etc/default/grub - contains default kernel options
/boot/grub2/grubenv - has the line
saved_entry=<id>
which refers to
/boot/loader/entries/<id>.conf
which contains kernel options for the entry (which are actually used)
which get modified when editing kernel options via grub menu (thus becom
ing persistent)
/etc/default/grub - contains the line
GRUB_ENABLE_BLSCFG=true
which is documented at
https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault
I have
GRUB_ENABLE_BLSCFG=false in /etc/default/grub because I hate that
functionality.
My concern was with the GRUB_CMDLINE_LINUX statement which was not
supplying the parameters to blacklist the nouveau driver and load the
nvidia driver that is supplied in other situations (maybe secureboot is
impacting that functionality, the parameters were supplied before I got
the signing keys into secureboot).
regards,
Steve
greg
_______________________________________________
users mailing list --users(a)lists.fedoraproject.org
To unsubscribe send an email tousers-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/users@lists.fedora...
Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue
535
days inactive
537
days old
16 comments
7 participants
participants (7)
-
Barry Scott -
greg -
Joe Zeff -
Robert McBroom -
Roger Heflin -
Samuel Sieb -
Stephen Morris