Hi,
after updating to a new kernel, the nvidia driver can no longer be loaded.
I have an older computer with a Geforce GT 1030 and without secureboot enabled.
root@fc40:/tmp# lspci | grep -Ei ‘VGA|3D’
02:00.0 VGA compatible controller: NVIDIA Corporation GP108 [GeForce GT 1030] (rev a1)
root@fc40:/tmp# mokutil --sb-state
EFI variables are not supported on this system
link to nvidia-bug-report.log.gz
Regards
Martin
This tells us that you have installed fedora in the legacy (MBR) boot mode and that it is not booting uefi. Secure boot is never available when using legacy boot.
What is the actual question / problem?
Details are required so we may be able to suggest a solution.
Most of us will refuse to download files to assist. Although I do not expect your .gz file contains malicious content it is still not a good practice to need to download the file then extract it before being able to read it. Having the text posted here is much preferred.
Please post the output of inxi -Fzxx and dnf list installed \*nvidia\* so we can see the hardware and drivers. Use text that you copy and paste from your screen using the </> button for preformatted text so it retains the on-screen formatting and is more readable.
If you installed the drivers from the rpmfusion repo (it is not apparent from your information) then one quick fix may be to run sudo akmods --force to build the driver for the running kernel. (or sudo akmods --force --rebuild)
Hi,
the problem is, that no nvidia modules are loaded, only nouveau modules. The maximum screen resolution is 1024 x 768.
I was able to solve the problem myself in the meantime.
When creating the kernel module with
akmods --force --rebuild
an error was reported in the file /var/cache/akmods/nvidia/560.28.03-1-for-6.9.10-200.fc40.x86_64.failed.log “No space left on device”, therefore the module could not be created. My directory /tmp was simply too small for the creation.
I then set the tmpdir from /tmp to another larger directory in the /usr/sbin/akmodsbuild file and it worked.
This may happen with builds when a system has very limited amount of RAM since /tmp is a virtual file system in RAM when running.
The system may continue to be used for quite some time if you were to increase the amount of RAM installed. The 'inxi -Fzxx` command output would have allowed us to see that problem as you see here.
Info:
Memory: total: 32 GiB available: 31.26 GiB used: 5.17 GiB (16.5%)
Processes: 451 Power: uptime: 1h 58m wakeups: 0 Init: systemd v: 255
target: graphical (5) default: graphical
Packages: pm: flatpak pkgs: 18 Compilers: gcc: 14.1.1 Shell: Bash
v: 5.2.26 running-in: gnome-terminal inxi: 3.3.34
Continuing to operate with very limited RAM installed will likely only continue to create problems in the future. RAM is used for the OS, including several virtual file systems, as well as swap and running programs.
Thanks for your support. will upgrade the RAM on my older computer to 16 GB