Problems with NVIDIA GTX 1060 3GB on Debian 12 and F@H
Problems with NVIDIA GTX 1060 3GB on Debian 12 and F@H
I recommend converting the files to .bak format at the end, even if they have a .conf extension. This will let you isolate the NVIDIA blacklisting file in the directory without interference from others. It helps confirm which kernel module for VGA is active. Use the command: lspci -nnk. To narrow results to your GPU, filter with grep nvidia or vga. This way you can verify the new software is still running instead of the NVIDIA module.
I performed the action, restarted and left the graphical interface off using init 3. Both the driver and kernel module seem new, yet the setup continues to fail.
Alright, rename the .conf file to filename.conf.bak without keeping the original name. Then, set up modprobe.conf in /etc/modprobe.d/. In this new file, add: blacklist nouveau Ctrl X to save. If needed, attempt to remove nouveau software; if it fails, try removing other programs as well. Ensure only five or fewer applications are removed during the process. If you don’t use the .run script in fullscreen “tty” mode or the F1-F6 keys, switch accordingly. Press Ctrl+Alt+F3 to make the screen black with medium-grey text. Enter your username and password when prompted. When a dollar sign appears on the screen, navigate to the .run file using the cd command. Show files with ls. If it’s in Downloads, go to ~/Downloads and use the ~ symbol as a key. Once inside, run sudo sh Nvi to avoid typing the full path. Press Tab (sometimes twice) if you need to finish entering the filename. Even then, errors may persist but you’ll know what’s installed. It’s frustrating when a text file or unknown file conflicts and blocks loading. I swear it’s a conspiracy. With AMD drivers embedded in the kernel, this can cause problems if loading isn’t smooth, and the framebuffer mode may stop working, halting the X graphics interface.
There seems to be an issue where the X server doesn't shut down properly when using ctrl alt f3. I understand how to work around it by running sudo init 3 from the GUI, which then stops the installer. I previously used commands like cd /home/jakob/Downloads and ./[filename].run to start the installer, making it run but hitting a problem. After changing permissions, the issue continued. The last entry was removed but the problem remained.
Consider removing the libdrm-nouveau package unless it conflicts with other applications. I’m unsure why it remains active, so better documentation would help. Have you run nvidia.run with sudo? I thought about using rmmod to disable a kernel module—similar to what I do for the built-in beep speaker. Would that work here?
I tried running it with root permissions, which initially helped. But now everything crashes, making it impossible to remove that issue. It’s frustrating since I’m used to Windows behaving predictably. This problem is especially bothersome because I find the “it works” attitude of the system annoying.
Resolved the new issue, yet the system displayed another question about the "gcc" package.
Transforms programming scripts into executable code. GNU compiler suite supports C, C++ and many more languages. For example, run with sudo apt install build-essential as a standard user.