So my issue started to arise as from yesterday I was trying to fix the freezes that I’ve been experiencing and I thought of downloading the nvidia divers for my KDE plasma which lead to me downloading the drivers via akmod as I was prompted to do so by a article and nvidia saying that its was better to download community versions instead.
After downloading it, I assumed everything was good, I did see artifacts on certain guis but for the most part it was fine, entill I decisided to restart my computer as I believed that it was the best thing to do as it was the first time the driver was on the computer.
Than the issue happened. When I tryed to login back in, there was a black screen just after the login screen was normal which also had my mouse there working for some reason.
nothing I’ve done has changed anything and I’ve tried tty(2-6) and all I got was nothing since it needed a password which the only 2 passwords that I had made for the computer didn’t work with me constantly getting incorrect password.
I’ve now tried going into a bootable drive but now I can’t access my main storage drive.
I thought I could delete the akmod but nope.
Please help, I now assume that I was meant to give the computer time to download the driver onto itself?
You have to use your account username (the shorter abbreviation that has no spaces), not your account display name (the longer form that often includes spaces) when you try to sign in on one of the virtual terminals.
I would say just boot an older kernel to get back to your previous configuration. Unfortunately, I believe NVIDIA has broken that classic fallback mechanism by forcing a rebuild of all the currently installed kernels whenever a new NVIDIA driver is installed. Blame NVIDIA for this problem. They are the ones who are destroying the fallback options so that people cannot recover from this sort of problem.
Only need to remove the nouveau blacklists from the grub menu command line since the system tries the nouveau drivers first.
This is from the rpmfusion how-to
Switching between nouveau/nvidia
With recent drivers as packaged with RPM Fusion, it is possible to switch easily
between nouveau and nvidia while keeping the nvidia driver installed. When you
are about to select the kernel at the grub menu step. You can edit the kernel
entry, find the linux boot command line and manually remove the following
options "rd.driver.blacklist=nouveau modprobe.blacklist=nouveau". This will allow
you to boot using the nouveau driver instead of the nvidia binary driver. At this
time, there is no way to make the switch at runtime.
That is slightly dated since now the option reads rd.driver.blacklist=nouveau,nova_core modprobe.blacklist=nouveau,nova_core
A new install of the nvidia driver only builds the new driver for the currently booted kernel. A driver update (or install) at the same time as a kernel update builds the driver for the currently booted kernel and the newly installed kernel.
It never rebuilds the driver for the older kernels. In the example below I did an offline upgrade from 43 to 44 and the kernel booted when the driver was built was the 7.0.4 kernel for f44.
$ dnf list --installed kmod-nvidia*
Installed packages (available for reinstall, available for upgrade)
kmod-nvidia-6.19.14-200.fc43.x86_64.x86_64 3:580.159.03-1.fc43 @commandline
kmod-nvidia-7.0.4-100.fc43.x86_64.x86_64 3:580.159.03-1.fc43 @commandline
kmod-nvidia-7.0.4-200.fc44.x86_64.x86_64 3:595.71.05-1.fc44 @commandline
Oh, my mistake (sort of). I was thinking of the DKMS system. If you are using that to build your NVIDIA driver (most people are not), then it will rebuild the driver for all the currently installed kernels.[1] What’s worse, NVIDIA modified the whole DKMS system so that it (by default) does the same thing for all DKMS-built drivers (ZFS, wifi drivers, etc.).
Well i’m unable to do anything as the fact that every action I take in the tty requires me to put in a password and after doing what PG said, I got nothing even after using no uppercase or special characters in all the usernames I’ve set up.
Have you added a lot of custom software or configuration to your system? It might be easier to reinstall the system than it would be to get the current version working again. During a reinstall, it should be possible to keep your home directory and any documents you might have saved there.
I have done basic nothing else to the system beside bringing some files over, installing some programs and added stuff to the desktop, thats all. I was thinking of just doing a reinstall though.
One thing as well, I’m “in” the desktop right now but it seems to work for some small stuff and even some programs show up when searching and loading them up in the change desktop page.
That website seems way to detailed for the average user. It has the user installing the cuda toolkit from nvidia and that often conflicts with the driver itself (and cuda) that is installed from rpmfusion.
I always recommend following the instructions for installing the driver from rpmfusion and it seems to work for almost everyone with no conflicts.
Only one command is necessary if the user has enabled the 3rd party repos during setup on fedora. sudo dnf install akmod-nvidia xorg-x11-drv-nvidia-cuda
That also handles running cuda apps on fedora. The toolkit from nvidia seems to only be necessary for developers of cuda apps.
I guess now a new question for this topic (as I’ve now just reinstalled my Fedora as I need the computer but now dealt with the following problem) would getting the Nvidia drivers help with all the continuous freezing that I now and before had to deal with, as from the start, getting the drivers was what I though would help with all the freezing I was facing?
I’m going to reinstall again to turn on 3rd party repos.
I’m not going to download any of the security updates that ever come for the time being.
This is a question, whats the best way of getting the computer specs of my computer? I want to see if maybe I should update any of my computer aspects like bios or something.
