You can use journalctl -b0 to get system logs since the current boot or journalctl -b-1 for previous boot (can continue decreasing the number to go further back). Assuming it actually boots and just shows a black screen you can switch to another tty, for example CTRL+ALT+F3 and get a prompt where you can run these commands.
You can combine that with something like fpaste in order to upload the logs and provide a link for you to post here. man fpaste to get an idea on how to use it.
I followed the instructions again and it did not crash but it is still using nouveau…
**Graphics:**
**Device-1:** NVIDIA GP106 \[GeForce GTX 1060 6GB\] **vendor:** Gigabyte
**driver:** nouveau **v:** kernel **arch:** Pascal **pcie:** **speed:** 2.5 GT/s **lanes:** 4 **ports:**
So we’re back to needing info. As asked before, we need again the results of dnf list --installed \*nvidia\* to see what is actually installed and if the akmods are actually installed. Review and provide the logs from /var/log/akmods/akmods.log checking for any failure messages.
Also, if you can paste the actual commands to install the drivers that may also be helpful to see if you missed something.
simon@Solaris:\~$ dnf list --installed \\\*nvidia\\\*
Installed packages (available for **reinstall**, available for **upgrade**)
**akmod-nvidia-580xx.x86_64 3:580.173.02-1.fc44 rpmfusion-nonfree-updates**
**kmod-nvidia-580xx-7.1.4-204.fc44.x86_64.x86_64 3:580.173.02-1.fc44 @commandline**
**libva-nvidia-driver.i686 0.0.17-1.fc44 updates**
**libva-nvidia-driver.x86_64 0.0.17-1.fc44 updates**
**nvidia-gpu-firmware.noarch 20260622-1.fc44 updates**
**nvidia-modprobe.x86_64 3:610.43.03-1.fc44 rpmfusion-nonfree-nvidia-driver**
**nvidia-persistenced.x86_64 3:610.43.03-2.fc44 rpmfusion-nonfree-nvidia-driver**
**nvidia-settings-580xx.x86_64 3:580.173.02-1.fc44 rpmfusion-nonfree-updates**
**xorg-x11-drv-nvidia-580xx.x86_64 3:580.173.02-1.fc44 rpmfusion-nonfree-updates**
**xorg-x11-drv-nvidia-580xx-cuda.x86_64 3:580.173.02-1.fc44 rpmfusion-nonfree-updates**
**xorg-x11-drv-nvidia-580xx-cuda-libs.i686 3:580.173.02-1.fc44 rpmfusion-nonfree-updates**
**xorg-x11-drv-nvidia-580xx-cuda-libs.x86_64 3:580.173.02-1.fc44 rpmfusion-nonfree-updates**
**xorg-x11-drv-nvidia-580xx-kmodsrc.x86_64 3:580.173.02-1.fc44 rpmfusion-nonfree-updates**
**xorg-x11-drv-nvidia-580xx-libs.i686 3:580.173.02-1.fc44 rpmfusion-nonfree-updates**
**xorg-x11-drv-nvidia-580xx-libs.x86_64 3:580.173.02-1.fc44 rpmfusion-nonfree-updates**
**xorg-x11-drv-nvidia-580xx-power.x86_64 3:580.173.02-1.fc44 rpmfusion-nonfree-updates**
And somehow for the logs it tells me pemition denied do I need to be logged in as root?
simon@Solaris:\~$ journalctl -b0
juil. 26 19:34:20 Solaris kernel: **Linux version 7.1.4-204.fc44.x86_64 (mockbuild@7bf2e6b0278e48518d21d9f513bd2a35) (gcc (GCC) 16.1.1 20260515 (Red Hat 16.1.1-2), GNU ld version 2.46.1-1.fc4**>
juil. 26 19:34:20 Solaris kernel: Command line: BOOT_IMAGE=(hd1,gpt2)/vmlinuz-7.1.4-204.fc44.x86_64 root=UUID=6584229b-385c-4cb0-8d4e-9af2c8305d44 ro rootflags=subvol=root rhgb quiet rd.dri>
juil. 26 19:34:20 Solaris kernel: BIOS-provided physical RAM map:
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x0000000000000000-0x000000000009ffff\] System RAM
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[gap 0x00000000000a0000-0x00000000000fffff\]
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x0000000000100000-0x00000000ba0bffff\] System RAM
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x00000000ba0c0000-0x00000000ba4f3fff\] device reserved
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x00000000ba4f4000-0x00000000ba503fff\] ACPI data
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x00000000ba504000-0x00000000bb30afff\] ACPI NVS
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x00000000bb30b000-0x00000000bca33fff\] device reserved
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x00000000bca34000-0x00000000bca34fff\] System RAM
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x00000000bca35000-0x00000000bcc3afff\] ACPI NVS
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x00000000bcc3b000-0x00000000bd082fff\] System RAM
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x00000000bd083000-0x00000000bd7f3fff\] device reserved
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x00000000bd7f4000-0x00000000bd7fffff\] System RAM
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[gap 0x00000000bd800000-0x00000000febfffff\]
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x00000000fec00000-0x00000000fec00fff\] device reserved
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[gap 0x00000000fec01000-0x00000000fec0ffff\]
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x00000000fec10000-0x00000000fec10fff\] device reserved
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[gap 0x00000000fec11000-0x00000000fec1ffff\]
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x00000000fec20000-0x00000000fec20fff\] device reserved
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[gap 0x00000000fec21000-0x00000000fecfffff\]
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x00000000fed00000-0x00000000fed00fff\] device reserved
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[gap 0x00000000fed01000-0x00000000fed60fff\]
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x00000000fed61000-0x00000000fed70fff\] device reserved
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[gap 0x00000000fed71000-0x00000000fed7ffff\]
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x00000000fed80000-0x00000000fed8ffff\] device reserved
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[gap 0x00000000fed90000-0x00000000feefffff\]
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x00000000fef00000-0x00000000ffffffff\] device reserved
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[gap 0x0000000100000000-0x0000000100000fff\]
juil. 26 19:34:20 Solaris kernel: BIOS-e820: \[mem 0x0000000100001000-0x000000043effffff\] System RAM
juil. 26 19:34:20 Solaris kernel: NX (Execute Disable) protection: active
juil. 26 19:34:20 Solaris kernel: APIC: Static calls initialized
juil. 26 19:34:20 Solaris kernel: efi: EFI v2.1 by American Megatrends
juil. 26 19:34:20 Solaris kernel: efi: ACPI=0xba4fc000 ACPI 2.0=0xba4fc000 SMBIOS=0xf04c0 MOKvar=0xbbf0c000
juil. 26 19:34:20 Solaris kernel: efi: Not removing mem139: MMIO range=\[0xfec00000-0xfec00fff\] (4KB) from e820 map
juil. 26 19:34:20 Solaris kernel: efi: Not removing mem140: MMIO range=\[0xfec10000-0xfec10fff\] (4KB) from e820 map
juil. 26 19:34:20 Solaris kernel: efi: Not removing mem141: MMIO range=\[0xfec20000-0xfec20fff\] (4KB) from e820 map
juil. 26 19:34:20 Solaris kernel: efi: Not removing mem142: MMIO range=\[0xfed00000-0xfed00fff\] (4KB) from e820 map
juil. 26 19:34:20 Solaris kernel: efi: Not removing mem143: MMIO range=\[0xfed61000-0xfed70fff\] (64KB) from e820 map
juil. 26 19:34:20 Solaris kernel: efi: Not removing mem144: MMIO range=\[0xfed80000-0xfed8ffff\] (64KB) from e820 map
juil. 26 19:34:20 Solaris kernel: efi: Remove mem145: MMIO range=\[0xfef00000-0xffffffff\] (17MB) from e820 map
juil. 26 19:34:20 Solaris kernel: e820: remove \[mem 0xfef00000-0xffffffff\] device reserved
juil. 26 19:34:20 Solaris kernel: secureboot: Secure boot disabled
juil. 26 19:34:20 Solaris kernel: DMI: SMBIOS 2.7 present.
lines 1-45
These are the system logs
At least the start there are tons of lines
Even as root it says permission denied
root@Solaris:\~# /var/log/akmods/akmods.log
-bash: /var/log/akmods/akmods.log: Permission denied
So, just to see I ran the command inxi -Gzxx and somehow in driver this is written:
**Graphics:**
**Device-1:** NVIDIA GP106 \[GeForce GTX 1060 6GB\] **vendor:** Gigabyte
**driver:** nvidia **v:** 580.173.02 **arch:** Pascal **pcie:** **speed:** 5 GT/s **lanes:** 4
This is a log file, assuming it exists (can’t check, don’t have an nvidia card in thus machine). The command you entered tries to execute it.
You probably intend to read it, so open it in an editor of your choice. kate /var/log/akmods/akmods.log for example.
This now indicates that the nvidia driver is in use.
You can be assured that it’s active via the nvidia-smi command.
That will tell you your card, the driver version, what software is currently using it, the current temp of the GPU and so on.
So the command works, but when I run a game like Minecraft I get 2fps, do I need to make a profile with the nvidia profile thing, and if so how?
simon@Solaris:\~$ nvidia-smi
Sun Jul 26 18:52:22 2026
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 580.173.02 Driver Version: 580.173.02 CUDA Version: 13.0 |
+-----------------------------------------+------------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+========================+======================|
| 0 NVIDIA GeForce GTX 1060 6GB Off | 00000000:07:00.0 On | N/A |
| 0% 43C P8 12W / 120W | 404MiB / 6144MiB | 1% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=========================================================================================|
| 0 N/A N/A 2109 C+G /usr/bin/kwin_wayland 63MiB |
| 0 N/A N/A 2170 G /usr/bin/plasma-keyboard 68MiB |
| 0 N/A N/A 2178 G /usr/bin/Xwayland 11MiB |
| 0 N/A N/A 2244 G /usr/bin/plasmashell 165MiB |
| 0 N/A N/A 2519 G /usr/bin/xwaylandvideobridge 1MiB |
+-----------------------------------------------------------------------------------------+
simon@Solaris:\~$
I don’t play minecraft, but you would need to ensure that it’s actually using the card and not falling back to CPU rendering.
You can check by kicking it off and dropping back to this nvidia-smi output to see if it’s listed as a process, just as Xwayland and plasmashell are in your output.
What you actually do to tell minecraft to utilise the card, I’ve no idea but a Google search will undoubtedly assist as you won’t be the first to discover this situation.