Ensuring nvidia GPU functionality on fedora

Did you read the doc as proposed above?

I began following instruction no.1.
I received the following directions, and got the error I mentioned before during step 1.

Now you need to enroll the public key in MOK, this process is described
below.
- Ask MOK to enroll new keypair with certificate with the command
  `mokutil --import /etc/pki/akmods/certs/public_key.der`.
- mokutil asks to generate a password to enroll the public key.
- Rebooting the system is needed for MOK to enroll the new public key.
- On next boot MOK Management is launched and you have to choose
  "Enroll MOK".
- Choose "Continue" to enroll the key or "View key 0" to show the keys
  already enrolled.
- Confirm enrollment by selecting "Yes".
- You will be invited to enter the password generated above.
  WARNING: keyboard is mapped to QWERTY!
- The new key is enrolled, and system ask you to reboot.

You can confirm the enrollment of the new keypair once the system
rebooted with:
 `mokutil --list-enrolled | grep Issuer`
or with:
 `mokutil --test-key /etc/pki/akmods/certs/public_key.der`

I’m sorry if I got you wrong. if you mean another doc and not @computersavvy 's comment, please specify which one.

I do speak from the doc @computersavvy asked for yes … he also said:

yotamguttman@fedora:~$ mokutil --import /etc/pki/akmods/certs/public_key.der
Failed to get file status, /etc/pki/akmods/certs/public_key.der

I do not see that you have used sudo ?!

Please read carfuly and try to do as proposed above.

Reading the README.secureboot it indicates you should run the steps exactly like this and in the order shown. I added sudo to the 2 important commands you seem to have trouble with so you can copy and paste the commands into your terminal window.

  1. sudo kmodgenca
    • Ask MOK to enroll new keypair with certificate with the command
      sudo mokutil --import /etc/pki/akmods/certs/public_key.der.
  • mokutil asks to generate a password to enroll the public key.
  • Rebooting the system is needed for MOK to enroll the new public key.
  • On next boot MOK Management is launched and you have to choose
    “Enroll MOK”.
  • Choose “Continue” to enroll the key or “View key 0” to show the keys
    already enrolled. (choose “Continue” at this point, not the view key option)
  • Confirm enrollment by selecting “Yes”.
  • You will be invited to enter the password generated above.
    WARNING: keyboard is mapped to QWERTY!
  • The new key is enrolled, and system ask you to reboot.

Once that has been done and the reboot is completed then the last few lines ask you to confirm the import of the key into the bios, again using the mokutil command.

Note that what you called step 1 is actually step 2. They are not numbered in that README.

Only after this has been properly completed should you perform the steps I gave above to remove the kmod-nvidia package and to run the akmods command.

thank you so much for your patience!
I’m starting to get the hang of it.

sharing the confirmation of enrolment:

yotamguttman@fedora:~$ sudo mokutil --list-enrolled
[key 1]
SHA1 Fingerprint: 7e:68:65:1d:52:68:5f:7b:f5:8e:a0:1d:78:4d:2f:90:d3:f4:0f:0a
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number: 2574709492 (0x9976f2f4)
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: CN=Fedora Secure Boot CA
        Validity
            Not Before: Dec  7 16:25:54 2012 GMT
            Not After : Dec  5 16:25:54 2022 GMT
        Subject: CN=Fedora Secure Boot CA
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (2048 bit)
                Modulus:
                    00:ae:f5:f7:52:81:a9:5c:3e:2b:f7:1d:55:f4:5a:
                    68:84:2d:bc:8b:76:96:85:0d:27:b8:18:a5:cd:c1:
                    83:b2:8c:27:5d:23:0a:d1:12:0a:75:98:a2:e6:5d:
                    01:8a:f4:d9:9f:fc:70:bc:c3:c4:17:7b:02:b5:13:
                    c4:51:92:e0:c0:05:74:b9:2e:3d:24:78:a0:79:73:
                    94:c0:c2:2b:b2:82:a7:f4:ab:67:4a:22:f3:64:cd:
                    c3:f9:0c:26:01:bf:1b:d5:3d:39:bf:c9:fa:fb:5e:
                    52:b9:a4:48:fb:13:bf:87:29:0a:64:ef:21:7b:bc:
                    1e:16:7b:88:4f:f1:40:2b:d9:22:15:47:4e:84:f6:
                    24:1c:4d:53:16:5a:b1:29:bb:5e:7d:7f:c0:d4:e2:
                    d5:79:af:59:73:02:dc:b7:48:bf:ae:2b:70:c1:fa:
                    74:7f:79:f5:ee:23:d0:03:05:b1:79:18:4f:fd:4f:
                    2f:e2:63:19:4d:77:ba:c1:2c:8b:b3:d9:05:2e:d9:
                    d8:b6:51:13:bf:ce:36:67:97:e4:ad:58:56:07:ab:
                    d0:8c:66:12:49:dc:91:68:b4:c8:ea:dd:9c:c0:81:
                    c6:91:5b:db:12:78:db:ff:c1:af:08:16:fc:70:13:
                    97:5b:57:ad:6b:44:98:7e:1f:ec:ed:46:66:95:0f:
                    05:55
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            Authority Information Access: 
                CA Issuers - URI:https://fedoraproject.org/wiki/Features/SecureBoot
            X509v3 Authority Key Identifier: 
                FD:E3:25:99:C2:D6:1D:B1:BF:58:07:33:5D:7B:20:E4:CD:96:3B:42
            X509v3 Extended Key Usage: 
                Code Signing
            X509v3 Subject Key Identifier: 
                FD:E3:25:99:C2:D6:1D:B1:BF:58:07:33:5D:7B:20:E4:CD:96:3B:42
    Signature Algorithm: sha256WithRSAEncryption
    Signature Value:
        37:77:f0:3a:41:a2:1c:9f:71:3b:d6:9b:95:b5:15:df:4a:b6:
        f4:d1:51:ba:0d:04:da:9c:b2:23:f0:f3:34:59:8d:b8:d4:9a:
        75:74:65:80:17:61:3a:c1:96:7f:a7:c1:2b:d3:1a:d6:60:3c:
        71:3a:a4:c4:e3:39:03:02:15:12:08:1f:4e:cd:97:50:f8:ff:
        50:cc:b6:3e:03:7d:7a:e7:82:7a:c2:67:be:c9:0e:11:0f:16:
        2e:1e:a9:f2:6e:fe:04:bd:ea:9e:f4:a9:b3:d9:d4:61:57:08:
        87:c4:98:d8:a2:99:64:de:15:54:8d:57:79:14:1f:fa:0d:4d:
        6b:cd:98:35:f5:0c:06:bd:f3:31:d6:fe:05:1f:60:90:b6:1e:
        10:f7:24:e0:3c:f6:33:50:cd:44:c2:71:18:51:bd:18:31:81:
        1e:32:e1:e6:9f:f9:9c:02:53:b4:e5:6a:41:d6:65:b4:2e:f1:
        cf:b3:b8:82:b0:a3:96:e2:24:d8:83:ae:06:5b:b3:24:74:4d:
        d1:a4:0a:1d:0a:32:1b:75:a2:96:d1:0e:3e:e1:30:c3:18:e8:
        cb:53:c4:0b:00:ad:7e:ad:c8:49:41:ef:97:69:bd:13:5f:ef:
        ef:3c:da:60:05:d8:92:fc:da:6a:ea:48:3f:0e:3e:73:77:fd:
        a6:89:e9:3f

[key 2]
SHA1 Fingerprint: 1c:c3:cf:b2:7f:42:b6:63:8a:bb:43:80:f8:7e:aa:e0:4f:4c:e2:48
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            4e:d4:93:0c:bf:f5:3a:05:40:9d:97:c9:03:ab:0d:97:75:60:c2:21
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: O=fedora, OU=fedora/emailAddress=akmods@fedora, L=None, ST=None, C=GB, CN=fedora-228328237
        Validity
            Not Before: Jan 27 18:13:31 2024 GMT
            Not After : Jan 24 18:13:31 2034 GMT
        Subject: O=fedora, OU=fedora/emailAddress=akmods@fedora, L=None, ST=None, C=GB, CN=fedora-228328237
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (4096 bit)
                Modulus:
                    00:e8:45:ca:4b:e3:3a:8e:30:1f:06:84:7a:91:47:
                    41:d9:28:ac:fb:df:67:34:1d:44:27:87:c3:d8:39:
                    d6:4b:7f:f6:e2:4a:63:75:9e:43:c5:e4:dd:05:76:
                    99:eb:d3:46:d0:05:cc:78:65:3f:16:29:a3:5e:f3:
                    60:8c:30:7f:95:bc:30:7a:bf:65:40:35:af:fb:f3:
                    b8:b7:73:a5:46:7f:8f:e1:43:ef:39:8d:5b:92:08:
                    57:a4:42:99:65:04:b1:25:fd:e0:c4:dd:d8:ae:df:
                    37:93:e2:95:e7:1a:58:50:f6:8d:d6:f7:fc:aa:a0:
                    13:bc:7d:a4:18:d7:f0:06:a1:11:4c:fd:77:b0:3c:
                    ec:dd:6a:5f:50:94:ab:0d:47:f9:02:8e:8a:90:82:
                    15:53:64:cb:3e:9a:ce:7a:5b:dd:90:98:b4:84:ed:
                    fb:02:4a:07:9e:7c:e8:d9:d1:cc:cd:98:65:3b:95:
                    23:55:d8:32:a2:90:85:2e:3d:7f:91:28:1b:79:8c:
                    28:8c:c6:c5:b8:8c:9c:55:4d:f4:0d:4b:cd:69:b5:
                    e1:6c:5d:8a:7a:95:5a:c0:58:c5:dc:b6:37:b3:04:
                    ad:de:ca:ef:f4:f1:77:3b:29:89:21:72:e3:c0:d1:
                    db:64:a5:2f:5d:7d:b3:d8:9a:bb:51:72:20:de:6d:
                    30:6b:dd:44:5c:e5:5f:1a:ec:db:9e:8b:f6:9a:8b:
                    b5:31:ab:1f:58:4c:b6:e3:f9:56:c9:2c:35:5c:15:
                    b8:93:dd:cf:06:6a:25:16:1d:df:0d:97:3e:dd:a0:
                    be:37:fb:a0:23:72:63:fd:69:09:dc:32:09:12:30:
                    b1:c2:b6:53:1f:80:4f:28:6f:65:88:61:9a:58:ab:
                    33:38:33:69:28:09:dc:9c:40:d3:93:db:81:b2:40:
                    61:8d:d0:7e:96:d3:c6:13:b2:bc:e2:e0:00:c3:98:
                    a6:17:f9:59:17:c3:46:c2:03:94:f3:c3:8e:9d:b0:
                    31:60:00:ab:eb:a5:3d:54:05:99:f6:bc:d8:45:70:
                    f4:42:f6:6c:27:24:61:34:40:31:53:8c:c5:b2:6b:
                    fa:cc:e7:a4:53:2c:11:90:73:69:31:90:72:6f:05:
                    35:7e:fd:c5:ef:42:86:c1:8c:85:a7:04:4e:1a:85:
                    f0:77:52:43:56:ec:a2:06:b3:eb:5d:cf:57:b2:e6:
                    4f:80:cc:e0:3e:d8:03:43:92:87:28:7c:1d:a6:d8:
                    6b:0d:79:72:4c:e0:7d:49:8a:32:6e:5b:50:74:71:
                    b4:80:b1:3b:2e:ba:e7:d7:79:88:b6:c7:c3:da:20:
                    af:b8:7d:16:db:c1:6a:41:95:c6:b9:3b:b5:ca:f6:
                    21:ed:01
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Basic Constraints: critical
                CA:FALSE
            X509v3 Key Usage: 
                Digital Signature
            X509v3 Subject Key Identifier: 
                3D:11:86:95:60:0D:C1:68:A6:14:FB:08:DF:2D:EA:06:B7:94:2A:97
    Signature Algorithm: sha256WithRSAEncryption
    Signature Value:
        6c:ac:d7:27:c7:9f:69:09:e8:70:09:e0:96:92:26:42:2d:e3:
        17:ca:f9:6c:12:0c:ec:b6:c9:f5:39:b4:24:48:4e:30:52:68:
        d7:0c:df:12:77:63:a8:0e:e5:5d:64:0c:5f:5e:e3:ae:81:c6:
        1b:83:15:8b:7a:43:34:0a:e0:8a:82:27:90:7b:51:31:28:e8:
        16:54:8e:41:bb:01:0b:86:6a:a5:e5:69:66:0c:c1:83:62:95:
        b0:dc:59:2f:8c:ba:b2:eb:88:ab:fc:cf:ee:01:57:bd:68:e4:
        46:91:64:16:29:28:f4:f3:d1:b5:8b:f4:42:54:db:08:11:f8:
        57:a1:6f:8d:7d:69:0f:ae:2a:31:0e:3a:e7:a2:5a:8a:c3:07:
        3a:d8:83:e2:6b:77:1a:7b:80:c4:60:21:c2:2a:6d:30:46:aa:
        80:44:3f:83:21:77:ad:e9:d7:d9:ba:54:53:8a:6f:e8:0a:d2:
        44:b0:6d:ea:cc:45:10:21:de:91:2f:f8:cc:07:4e:ae:bf:04:
        3e:22:8a:54:56:b0:ff:4c:d1:8f:49:3e:48:b1:ab:7e:41:97:
        c3:83:1b:90:76:5a:74:e9:44:9a:b8:d7:8d:b6:af:b9:d6:fc:
        4e:35:10:a8:5b:a5:dc:d0:b1:1a:66:ae:c7:c1:70:ef:79:01:
        b2:d5:ee:66:35:08:aa:6d:a4:c1:90:7e:52:44:7a:d8:3d:93:
        ca:f9:5e:0c:b1:bf:7d:2f:2f:7b:2e:95:4b:47:e7:ef:d0:9a:
        13:d7:97:52:51:9b:fd:4d:ec:6d:f2:de:54:e2:66:41:52:a1:
        b9:03:6e:bb:32:ee:52:f8:a2:5e:f5:0c:01:b9:60:80:95:af:
        b4:1f:59:e0:02:e8:b8:5e:02:61:10:2d:8d:72:b7:3f:ab:db:
        50:ef:80:2c:25:cc:81:6c:75:a7:eb:ca:88:b8:7b:f4:a7:a9:
        90:cc:fc:74:f4:1b:f4:59:78:08:bf:64:e9:39:0b:52:a9:33:
        6e:f7:e6:cb:46:4b:38:d6:e8:21:b3:a4:b1:9d:35:de:e8:23:
        d9:7c:5f:b3:fe:30:69:58:32:cc:c5:cd:ca:90:4c:ad:94:ad:
        ed:8c:e5:13:6d:d2:1f:79:f8:5d:82:cb:6a:a3:56:de:a1:97:
        54:95:70:3a:9f:bd:b3:bb:ac:95:fd:bd:89:d4:4b:7f:61:4e:
        0b:69:05:c2:3a:93:d3:5b:0f:e6:8a:fc:1b:2a:0f:26:77:fe:
        9e:46:b0:c8:76:bf:f0:e6:ee:f0:88:7d:ca:56:fc:ca:d3:44:
        1a:e3:79:eb:18:42:be:44:05:ce:7d:93:8c:49:43:10:fa:1b:
        e8:18:59:ca:9b:b3:5e:81
yotamguttman@fedora:~$ sudo mokutil --test-key /etc/pki/akmods/certs/public_key.der
/etc/pki/akmods/certs/public_key.der is already enrolled

method 1 (–list-enrolled), should probably show a key called ‘grep issuer’? I didn’t find it.
method 2 (–test-key), shows that the key is enrolled. so I suppose that was successful.


I’ve proceeded to your second step. Nvidia drivers have been removed and reinstalled.

mokutil~yotamguttman@fesudo dnf remove kmod-nvidia-*nvidia-*
[sudo] password for yotamguttman: 
Dependencies resolved.
=================================================================================================================
 Package                                   Architecture  Version                      Repository            Size
=================================================================================================================
Removing:
 kmod-nvidia-6.5.6-300.fc39.x86_64         x86_64        3:545.29.06-2.fc39           @@commandline         43 M
 kmod-nvidia-6.6.13-200.fc39.x86_64        x86_64        3:545.29.06-2.fc39           @@commandline         43 M

Transaction Summary
=================================================================================================================
Remove  2 Packages

Freed space: 85 M
Is this ok [y/N]: y
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                         1/1 
  Erasing          : kmod-nvidia-6.6.13-200.fc39.x86_64-3:545.29.06-2.fc39.x86_64                            1/2 
  Running scriptlet: kmod-nvidia-6.6.13-200.fc39.x86_64-3:545.29.06-2.fc39.x86_64                            1/2 
  Erasing          : kmod-nvidia-6.5.6-300.fc39.x86_64-3:545.29.06-2.fc39.x86_64                             2/2 
  Running scriptlet: kmod-nvidia-6.5.6-300.fc39.x86_64-3:545.29.06-2.fc39.x86_64                             2/2 
  Verifying        : kmod-nvidia-6.5.6-300.fc39.x86_64-3:545.29.06-2.fc39.x86_64                             1/2 
  Verifying        : kmod-nvidia-6.6.13-200.fc39.x86_64-3:545.29.06-2.fc39.x86_64                            2/2 

Removed:
  kmod-nvidia-6.5.6-300.fc39.x86_64-3:545.29.06-2.fc39.x86_64                                                    
  kmod-nvidia-6.6.13-200.fc39.x86_64-3:545.29.06-2.fc39.x86_64                                                   

Complete!
yotamguttman@fedora:~$ sudo akmods --force
Checking kmods exist for 6.6.13-200.fc39.x86_64            [  OK  ]
Building and installing nvidia-kmod                        [  OK  ]
yotamguttman@fedora:~$ 


I will go ahead to restart the system now and will keep you posted

so it’s been rebooted.

the first time round I ran the command inxi -Fzxx nvidia, I got this:

now it only replied this:

yotamguttman@fedora:~$ sudo inxi -Fzxx
[sudo] password for yotamguttman: 
System:
  Kernel: 6.6.13-200.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.40-13.fc39 Console: pty pts/1 wm: gnome-shell DM: GDM Distro: Fedora
    release 39 (Thirty Nine)
Machine:
  Type: Desktop System: Dell product: XPS 8930 v: 1.1.31 serial: <filter>
    Chassis: type: 3 serial: <filter>
  Mobo: Dell model: 0DF42J v: A03 serial: <filter> UEFI: Dell v: 1.1.31
    date: 11/21/2023
Battery:
  Device-1: hidpp_battery_0 model: Logitech MX Vertical Advanced Ergonomic
    Mouse serial: <filter> charge: 55% (should be ignored) status: discharging
  Device-2: hidpp_battery_1 model: Logitech Craft Advanced Keyboard
    serial: <filter> charge: 55% (should be ignored) status: discharging
CPU:
  Info: 6-core model: Intel Core i7-8700 bits: 64 type: MT MCP
    arch: Coffee Lake rev: A cache: L1: 384 KiB L2: 1.5 MiB L3: 12 MiB
  Speed (MHz): avg: 1101 high: 1301 min/max: 800/4600 cores: 1: 1301 2: 1300
    3: 800 4: 800 5: 1301 6: 1300 7: 1300 8: 913 9: 800 10: 1300 11: 1301
    12: 800 bogomips: 76799
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: Dell
    driver: i915 v: kernel arch: Gen-9.5 ports: active: none
    empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:3e92
  Device-2: NVIDIA GP104 [GeForce GTX 1070] vendor: Dell driver: nvidia
    v: 545.29.06 arch: Pascal pcie: speed: 8 GT/s lanes: 16 ports: active: none
    off: HDMI-A-3 empty: DP-2, DP-3, DP-4, DVI-D-1 bus-ID: 01:00.0
    chip-ID: 10de:1b81
  Display: server: X.Org v: 23.2.4 with: Xwayland v: 23.2.4
    compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: nouveau,iris gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3440x1440 s-dpi: 96
  Monitor-1: HDMI-A-3 mapped: HDMI-3 note: disabled model: Dell U3419W
    res: 3440x1440 dpi: 109 diag: 867mm (34.1")
  API: OpenGL v: 4.6.0 vendor: nvidia v: 545.29.06 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce GTX 1070/PCIe/SSE2
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: Dell driver: snd_hda_intel
    v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a2f0
  Device-2: NVIDIA GP104 High Definition Audio vendor: Dell
    driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:10f0
  API: ALSA v: k6.6.13-200.fc39.x86_64 status: kernel-api
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.0.1 status: n/a (root, process) with:
    1: pipewire-pulse status: active 2: wireplumber status: active
    3: pipewire-alsa type: plugin
Network:
  Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
    vendor: Rivet Networks Killer Wireless-n/a/ac 1535 driver: ath10k_pci
    v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0
    chip-ID: 168c:003e temp: 44.0 C
  IF: wlp3s0 state: down mac: <filter>
  Device-2: Qualcomm Atheros Killer E2400 Gigabit Ethernet vendor: Dell
    driver: alx v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: d000
    bus-ID: 04:00.0 chip-ID: 1969:e0a1
  IF: enp4s0 state: down mac: <filter>
  Device-3: Realtek RTL8188EUS 802.11n Wireless Network Adapter
    driver: rtl8xxxu type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-5:2
    chip-ID: 0bda:8179
  IF: wlp0s20f0u5 state: up mac: <filter>
Bluetooth:
  Device-1: Qualcomm Atheros QCA61x4 Bluetooth 4.0 driver: btusb v: 0.8
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-8:4 chip-ID: 0cf3:e300
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.0
    lmp-v: 9
RAID:
  Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0
    bus-ID: 00:17.0 chip-ID: 8086:2822
Drives:
  Local Storage: total: 2.05 TiB used: 12.3 GiB (0.6%)
  ID-1: /dev/sda vendor: Toshiba model: DT01ACA200 size: 1.82 TiB
    speed: 6.0 Gb/s serial: <filter> temp: 41 C
  ID-2: /dev/sdb vendor: Verbatim model: Vi550 S3 size: 238.47 GiB type: USB
    rev: 3.0 spd: 5 Gb/s lanes: 1 serial: <filter>
Partition:
  ID-1: / size: 110.65 GiB used: 11.95 GiB (10.8%) fs: btrfs dev: /dev/sdb5
  ID-2: /boot size: 1004.8 MiB used: 249.9 MiB (24.9%) fs: ext4
    dev: /dev/sdb3
  ID-3: /boot/efi size: 574.8 MiB used: 17.4 MiB (3.0%) fs: vfat
    dev: /dev/sdb2
  ID-4: /home size: 110.65 GiB used: 11.95 GiB (10.8%) fs: btrfs
    dev: /dev/sdb5
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 50.0 C mobo: N/A
  Fan Speeds (rpm): cpu: 1650 mobo: 941
Info:
  Processes: 363 Uptime: 10m Memory: total: 16 GiB available: 15.33 GiB
  used: 3.05 GiB (19.9%) Init: systemd v: 254 target: graphical (5)
  default: graphical Compilers: gcc: 13.2.1 Packages: pm: rpm pkgs: N/A
  note: see --rpm pm: flatpak pkgs: 26 Shell: Sudo v: 1.9.15p5
  running-in: gnome-terminal inxi: 3.3.31
yotamguttman@fedora:~$ inxi -Fzxx nvidia
Error 22: Unsupported option: nvidia
Check -h for correct parameters.

yotamguttman@fedora:~$ sudo -h
sudo - execute a command as another user

usage: sudo -h | -K | -k | -V
usage: sudo -v [-ABkNnS] [-g group] [-h host] [-p prompt] [-u user]
usage: sudo -l [-ABkNnS] [-g group] [-h host] [-p prompt] [-U user]
            [-u user] [command [arg ...]]
usage: sudo [-ABbEHkNnPS] [-r role] [-t type] [-C num] [-D directory]
            [-g group] [-h host] [-p prompt] [-R directory] [-T timeout]
            [-u user] [VAR=value] [-i | -s] [command [arg ...]]
usage: sudo -e [-ABkNnS] [-r role] [-t type] [-C num] [-D directory]
            [-g group] [-h host] [-p prompt] [-R directory] [-T timeout]
            [-u user] file ...

Options:
  -A, --askpass                 use a helper program for password prompting
  -b, --background              run command in the background
  -B, --bell                    ring bell when prompting
  -C, --close-from=num          close all file descriptors >= num
  -D, --chdir=directory         change the working directory before running
                                command
  -E, --preserve-env            preserve user environment when running command
      --preserve-env=list       preserve specific environment variables
  -e, --edit                    edit files instead of running a command
  -g, --group=group             run command as the specified group name or ID
  -H, --set-home                set HOME variable to target user's home dir
  -h, --help                    display help message and exit
  -h, --host=host               run command on host (if supported by plugin)
  -i, --login                   run login shell as the target user; a command
                                may also be specified
  -K, --remove-timestamp        remove timestamp file completely
  -k, --reset-timestamp         invalidate timestamp file
  -l, --list                    list user's privileges or check a specific
                                command; use twice for longer format
  -n, --non-interactive         non-interactive mode, no prompts are used
  -P, --preserve-groups         preserve group vector instead of setting to
                                target's
  -p, --prompt=prompt           use the specified password prompt
  -R, --chroot=directory        change the root directory before running command
  -r, --role=role               create SELinux security context with specified
                                role
  -S, --stdin                   read password from standard input
  -s, --shell                   run shell as the target user; a command may
                                also be specified
  -t, --type=type               create SELinux security context with specified
                                type
  -T, --command-timeout=timeout terminate command after the specified time limit
  -U, --other-user=user         in list mode, display privileges for user
  -u, --user=user               run command (or edit file) as specified user
                                name or ID
  -V, --version                 display version information and exit
  -v, --validate                update user's timestamp without running a
                                command
  --                            stop processing command line arguments

inxi -G is just for graphics. If you want to filter for nvidia you have to use grep and sent it thru a pipe | like (this just makes sense if you have a very big output):

inxi -G |grep nvidia

1 Like

sure it makes perfect sense. thank you!

I suppose it’s done the job

$ sudo inxi -G |grep nvidia
[sudo] password for yotamguttman: 
  Device-2: NVIDIA GP104 [GeForce GTX 1070] driver: nvidia v: 545.29.06
    gpu: nvidia,nvidia-nvswitch resolution: 3440x1440~60Hz
  API: OpenGL v: 4.6.0 vendor: nvidia v: 545.29.06 renderer: NVIDIA GeForce

Responses like Check -h for correct parameters. are generated by the program you just ran, in this case inxi, so you are meant to look at inxi -h, not sudo -h.

As already mentioned, searching this forum for inxi -Fzxx nvidia would have shown you existing discussions of similar issues.

Command-line tools are important for managing linux systems. I recommend Linux Command as it has been around for a long time and benefits from having many readers. It also has translations to languages other than English.

1 Like

I understand. thank you for the resource, it’s exactly what I needed to get a head start into it.

is there anything I should look for a particular parameter in Terminal when running the inix -h, to make sure that it all runs correctly now?

what’s changed is that every time I boot the system it requires me to unlock it with a password. otherwise I cannot do anything. attaching a picture as I cannot even take a screenshot.

are you familiar with this authentication request and is there a way to disable it?

thanks for your help!

Yes!
That shows the nvidia driver is fully active. :+1:

The suggestion to read up on the linux command line is quite apt. It will assist you in learning how to manage the system and in learning the language used to do so.

You should NOT be using sudo for most commands in a terminal. It gives the particular command being run root (superuser) privileges when needed for administrative tasks. If used improperly sudo can perform tasks that may destroy the system. Use commands without sudo and only if absolutely necessary then add sudo on the command line.

1 Like

Please start a new thread for this new problem. We will need more details to understand the problem. Are you using LUKS or autologin? When does the “Authentication required” panel appear (at boot, after normal user login, etc.?

Have a look at Gnome Keyring Update Password and Keyring auto login unlock with LUKS passphrase to see if either of those applies.

I understand, thank you very much for your help in the matter.
and your suggestion is very motivating for me. I’m very eager to get my head around it :slight_smile:

no problem. I’m unsure how to title this thread because I don’t know where this problem stems from. it’s the first thing I see when the OS loads.

it started when I disabled the secure boot.

yes , automatic login is enabled for my user. I don’t know what LUKS is.