LM stuck on underscore after installing Nvidia drivers

[Vraixen]

I have freshly re-installed Linux Mint x64 on a drive and i can't boot normally into Linux because of my GPU, so the first thing i've done is to boot into recovery mode and install the nvidia drivers, after selecting the reccomended version i reboot and what i get is an initially blinkling underscore and then it freeze. So im forced to reboot my PC. (pressing Ctrl+Alt+F1 does nothing)

The only way to be able to re login into mint is to use the recovery mode to uninstall the nvidia drivers through terminal.
I already tried to reinstall Linux mint but no luck.
Secure boot is off
i already tried to add this lines in the modules file located in /etc/modules

Code: Select all

nvidia 
nvidia-drm
nvidia-modeset

My GPU is an RTX 2080s

(the first time i installed Mint a month ago the drivers was working)

ps if you don't see the drivers installed in the outputs below is because i have uninstalled them to be able to login in the system.

inxi -Fx

Code: Select all

System:
  Host: vraixen-mint Kernel: 5.4.0-74-generic x86_64 bits: 64 compiler: gcc 
  v: 9.3.0 Desktop: Cinnamon 4.8.6 Distro: Linux Mint 20.1 Ulyssa 
  base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop System: Gigabyte product: Z490 VISION D v: -CF 
  serial: <superuser/root required> 
  Mobo: Gigabyte model: Z490 VISION D serial: <superuser/root required> 
  UEFI: American Megatrends v: F5a date: 06/22/2020 
CPU:
  Topology: 8-Core model: Intel Core i7-10700K bits: 64 type: MT MCP 
  arch: N/A L2 cache: 16.0 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 121596 
  Speed: 800 MHz min/max: 800/5100 MHz Core speeds (MHz): 1: 800 2: 800 
  3: 800 4: 800 5: 801 6: 800 7: 800 8: 800 9: 801 10: 800 11: 800 12: 800 
  13: 800 14: 802 15: 800 16: 800 
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2080 SUPER] driver: N/A 
  bus ID: 01:00.0 
  Display: x11 server: X.Org 1.20.9 driver: fbdev unloaded: modesetting,vesa 
  resolution: 1024x768~76Hz 
  OpenGL: renderer: llvmpipe (LLVM 11.0.0 256 bits) v: 4.5 Mesa 20.2.6 
  direct render: Yes 
Audio:
  Device-1: Intel Comet Lake PCH cAVS vendor: Gigabyte driver: snd_hda_intel 
  v: kernel bus ID: 00:1f.3 
  Device-2: NVIDIA TU104 HD Audio driver: snd_hda_intel v: kernel 
  bus ID: 01:00.1 
  Device-3: Samson Meteor condenser microphone type: USB 
  driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-3:2 
  Sound Server: ALSA v: k5.4.0-74-generic 
Network:
  Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi v: kernel bus ID: 00:14.3 
  IF: wlo1 state: down mac: 58:96:1d:57:f2:ab 
  Device-2: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: 3.2.6-k 
  port: efa0 bus ID: 00:1f.6 
  IF: eno2 state: down mac: b4:2e:99:fc:96:b4 
  Device-3: Intel vendor: Gigabyte driver: igc v: 0.0.1-k port: 3000 
  bus ID: 05:00.0 
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: b4:2e:99:fc:96:b2 
Drives:
  Local Storage: total: 2.06 TiB used: 7.99 GiB (0.4%) 
  ID-1: /dev/nvme0n1 vendor: Intel model: MEMPEK1W016GA size: 13.41 GiB 
  ID-2: /dev/nvme1n1 model: NVME SSD 1TB size: 953.87 GiB 
  ID-3: /dev/sda vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB 
  ID-4: /dev/sdb vendor: Samsung model: SSD 860 EVO M.2 250GB 
  size: 232.89 GiB 
RAID:
  Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 
  bus ID: 00:17.0 
Partition:
  ID-1: / size: 223.79 GiB used: 7.95 GiB (3.6%) fs: ext4 dev: /dev/sdb3 
  ID-2: swap-1 size: 3.81 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb1 
Sensors:
  System Temperatures: cpu: 45.0 C mobo: 27.8 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 356 Uptime: 1m Memory: 15.55 GiB used: 1.40 GiB (9.0%) 
  Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 
  inxi: 3.0.38 

inxi -Fxxxrz

Code: Select all

CPU:
  Topology: 8-Core model: Intel Core i7-10700K bits: 64 type: MT MCP 
  arch: N/A L2 cache: 16.0 MiB bogomips: 121596 
  Speed: 800 MHz min/max: 800/5100 MHz Core speeds (MHz): 1: 800 2: 800 
  3: 800 4: 800 5: 800 6: 800 7: 800 8: 801 9: 800 10: 800 11: 800 12: 800 
  13: 800 14: 800 15: 800 16: 800 
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat 
  arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush 
  clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 
  dtherm dts ept ept_ad erms est f16c flexpriority flush_l1d fma fpu 
  fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs 
  ibrs_enhanced ida intel_pt invpcid invpcid_single lahf_lm lm mca mce 
  md_clear mmx monitor movbe mpx msr mtrr nonstop_tsc nopl nx ospke pae pat 
  pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pku pln pni popcnt pse pse36 pts 
  rdrand rdseed rdtscp rep_good sdbg sep smap smep smx ss ssbd sse sse2 
  sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc tsc_adjust 
  tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1 xsave xsavec xsaveopt 
  xsaves xtopology xtpr 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com ulyssa main upstream import backport #id:linuxmint_main
  2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner

nvidia-smi

Code: Select all

NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

[JeremyB]

I wonder if Secure Boot got enabled, check mokutil --sb-state

[Vraixen]

Secure boot disabled

[Vraixen]

it can be something related with my Motherboard?

[SMG]

it can be something related with my Motherboard?

Does your motherboard give an option to use onboard graphics OR the discrete (Nvidia) card? Or does it let you use both simultaneously?

There is a bug with the i915 Intel driver that can result in a black screen. Based on the investigation in the thread Black Screen Z590 Chipset i7-10700k Intel UHD 630 Graphics, we found the 5.10-oem kernel resolved the issue. You can install the 5.10-oem kernel with sudo apt install linux-oem-20.04b.

I do not know how that might relate to the issues you are seeing with regards to Nvidia, but maybe installing that kernel will at least give you graphics to help investigate the situation.

[Vraixen]

it can be something related with my Motherboard?

Does your motherboard give an option to use onboard graphics OR the discrete (Nvidia) card? Or does it let you use both simultaneously?

There is a bug with the i915 Intel driver that can result in a black screen. Based on the investigation in the thread Black Screen Z590 Chipset i7-10700k Intel UHD 630 Graphics, we found the 5.10-oem kernel resolved the issue. You can install the 5.10-oem kernel with sudo apt install linux-oem-20.04b.

I do not know how that might relate to the issues you are seeing with regards to Nvidia, but maybe installing that kernel will at least give you graphics to help investigate the situation.

I tried to install the kernel and then the drivers nothing changed.. in my motherboard i have set the graphic card Pcie 1 and the integrated to "disabled"
Also i want to mention that i have the underscore so it is not a complete black screen.

[SMG]

I tried to install the kernel and then the drivers nothing changed.. in my motherboard i have set the graphic card Pcie 1 and the integrated to "disabled"
Also i want to mention that i have the underscore so it is not a complete black screen.

If you have the 5.10-oem kernel installed, I would think that if you enabled the integrated graphics that you should be able to boot normally and use Intel graphics. I would think that would rule out any general problems with the motherboard.

I would suggest checking the journalctl for one of the "underscore" boots to see what errors are showing. If you had an underscore boot and then you booted the next time in Recovery Mode, the following would give us underscore-boot information:
journalctl -rb -1 | nc termbin.com 9999
That command prints the journal log information of the prior boot cycle (the one with the underscore that you stopped by pressing the power button) in reverse order (so the reason for the blank screen should be near the top) and sends it to termbin. It will return with a url address that you should post in your next reply.

If you have booted two times since you last saw the blank screen, then use:
journalctl -rb -2 | nc termbin.com 9999
and let us know the url.

[Vraixen]

I tried to install the kernel and then the drivers nothing changed.. in my motherboard i have set the graphic card Pcie 1 and the integrated to "disabled"
Also i want to mention that i have the underscore so it is not a complete black screen.

If you have the 5.10-oem kernel installed, I would think that if you enabled the integrated graphics that you should be able to boot normally and use Intel graphics. I would think that would rule out any general problems with the motherboard.

I would suggest checking the journalctl for one of the "underscore" boots to see what errors are showing. If you had an underscore boot and then you booted the next time in Recovery Mode, the following would give us underscore-boot information:
journalctl -rb -1 | nc termbin.com 9999
That command prints the journal log information of the prior boot cycle (the one with the underscore that you stopped by pressing the power button) in reverse order (so the reason for the blank screen should be near the top) and sends it to termbin. It will return with a url address that you should post in your next reply.

If you have booted two times since you last saw the blank screen, then use:
journalctl -rb -2 | nc termbin.com 9999
and let us know the url.

There we go: http://termbin.com/drnv
I booted into recovery at:

Code: Select all

giu 20 17:11:14

so before that you should see the normal boot with the issue.
if you see something with network mananger is because it wasn't started and i wasn't able to use that command.

[SMG]

There we go: http://termbin.com/drnv
I booted into recovery at:

Code: Select all

giu 20 17:11:14

so before that you should see the normal boot with the issue.

The information you posted is not what I was expecting, so perhaps I did not explain very well what was needed.

I presumed when you get the blinking underscore on your screen that you power off the computer in order to start over. Let's call that blinking underscore result Boot 1.

I presumed you then re-power the computer, boot into grub and select Recovery Mode which we will call Boot 2. You get images on the screen while in Boot 2 because the system is using software rendering mode to display graphics.

The first command I gave you are the instructions for how to get Boot 1 information when you are in the Boot 2 instance. If you booted a second time into Recovery Mode after getting the blinking underscore then that would be Boot 3 and you would use the second command I listed.

The data you posted is a Recovery Mode boot cycle, so it is not Boot 1 which ended with the blinking underscore on the screen. It might be a Boot 2? The next to last line in what you posted indicates:

giu 20 17:07:04 vraixen-mint kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=127d30c2-085c-4fae-ba8b-e8cbcd768228 ro recovery nomodeset dis_ucode_ldr

Recovery Mode adds the kernel parameter nomodeset automatically which prevents the Nvidia driver from loading.

Code: Select all

giu 20 17:07:04 vraixen-mint kernel: You have booted with nomodeset. This means your GPU drivers are DISABLED

What I was hoping to see was a boot cycle that had errors/reasons for the blinking underscore, but that is not what was posted. Please let me know if you have questions about my explanation so we can the error info which might help.

[Vraixen]

There we go: http://termbin.com/drnv
I booted into recovery at:

Code: Select all

giu 20 17:11:14

so before that you should see the normal boot with the issue.

The information you posted is not what I was expecting, so perhaps I did not explain very well what was needed.

I presumed when you get the blinking underscore on your screen that you power off the computer in order to start over. Let's call that blinking underscore result Boot 1.

I presumed you then re-power the computer, boot into grub and select Recovery Mode which we will call Boot 2. You get images on the screen while in Boot 2 because the system is using software rendering mode to display graphics.

The first command I gave you are the instructions for how to get Boot 1 information when you are in the Boot 2 instance. If you booted a second time into Recovery Mode after getting the blinking underscore then that would be Boot 3 and you would use the second command I listed.

The data you posted is a Recovery Mode boot cycle, so it is not Boot 1 which ended with the blinking underscore on the screen. It might be a Boot 2? The next to last line in what you posted indicates:

giu 20 17:07:04 vraixen-mint kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=127d30c2-085c-4fae-ba8b-e8cbcd768228 ro recovery nomodeset dis_ucode_ldr

Recovery Mode adds the kernel parameter nomodeset automatically which prevents the Nvidia driver from loading.

Code: Select all

giu 20 17:07:04 vraixen-mint kernel: You have booted with nomodeset. This means your GPU drivers are DISABLED

What I was hoping to see was a boot cycle that had errors/reasons for the blinking underscore, but that is not what was posted. Please let me know if you have questions about my explanation so we can the error info which might help.

Sorry i tried again but with boot 2
http://termbin.com/2bez

[SMG]

I have freshly re-installed Linux Mint x64 on a drive

What was the reason you freshly re-installed Mint? You indicated it was working originally. Did you make a hardware change?

Sorry i tried again but with boot 2
http://termbin.com/2bez

There is a kernel Oops related to Nvidia. I did not include all the messages related to the oops, but here are ones I consider key.

Code: Select all

giu 20 19:49:10 vraixen-mint kernel: BUG: unable to handle page fault for address: ffff9cfc44832000
giu 20 19:49:10 vraixen-mint kernel: #PF: supervisor write access in kernel mode
giu 20 19:49:10 vraixen-mint kernel: #PF: error_code(0x0003) - permissions violation
giu 20 19:49:10 vraixen-mint kernel: PGD 491001067 P4D 491001067 PUD 1010d8063 PMD 10c54a063 PTE 8000000104832161
giu 20 19:49:10 vraixen-mint kernel: Oops: 0003 [#1] SMP NOPTI
giu 20 19:49:10 vraixen-mint kernel: CPU: 4 PID: 1098 Comm: Xorg Tainted: P           OE     5.10.0-1029-oem #30-Ubuntu
giu 20 19:49:10 vraixen-mint kernel: Hardware name: Gigabyte Technology Co., Ltd. Z490 VISION D/Z490 VISION D, BIOS F5a 06/22/2020
giu 20 19:49:10 vraixen-mint kernel: RIP: 0010:memcpy_erms+0x6/0x10
...
giu 20 19:49:10 vraixen-mint kernel: Call Trace:
giu 20 19:49:10 vraixen-mint kernel:  ? os_mem_copy+0x10/0x20 [nvidia]
giu 20 19:49:10 vraixen-mint kernel:  _nv017679rm+0x56c/0x710 [nvidia]
giu 20 19:49:10 vraixen-mint kernel: WARNING: kernel stack frame pointer at 0000000039517294 in Xorg:1098 has bad value 00000000c953d549
...
giu 20 19:49:10 vraixen-mint kernel: ---[ end trace bb961c5e2a4175d9 ]---

Then a second Oops happens.

Code: Select all

giu 20 19:49:10 vraixen-mint kernel: Oops: 0000 [#2] SMP NOPTI

Then there is another problem, but this one does not mention Nvidia.

Code: Select all

giu 20 19:49:14 vraixen-mint kernel: general protection fault, probably for non-canonical address 0x28cd41a51ecfbebb: 0000 [#3] SMP NOPTI

Because you were having problems with the 5.4 kernel as well as with this 5.10-oem kernel, I would not think the kernel is the issue.

I am not sure if this is an issue with the Nvidia driver, something related to the GPU's hardware, or something else. One possible way to test if the GPU is okay is to install the nouveau (open-source) driver and test it. Have you tried that yet?

I did check the Nvidia forum to see if anyone was having a similar issue. There seemed to be quite a few issues and some people discovered if they used HDMI connections instead of Displayport then they were able to get graphics. I do not know if that might be a factor in your situation.

Let us know why you re-installed Mint as that might be a clue as to what is happening now.

[Vraixen]

I have freshly re-installed Linux Mint x64 on a drive

What was the reason you freshly re-installed Mint? You indicated it was working originally. Did you make a hardware change?

Sorry i tried again but with boot 2
http://termbin.com/2bez

There is a kernel Oops related to Nvidia. I did not include all the messages related to the oops, but here are ones I consider key.

Code: Select all

giu 20 19:49:10 vraixen-mint kernel: BUG: unable to handle page fault for address: ffff9cfc44832000
giu 20 19:49:10 vraixen-mint kernel: #PF: supervisor write access in kernel mode
giu 20 19:49:10 vraixen-mint kernel: #PF: error_code(0x0003) - permissions violation
giu 20 19:49:10 vraixen-mint kernel: PGD 491001067 P4D 491001067 PUD 1010d8063 PMD 10c54a063 PTE 8000000104832161
giu 20 19:49:10 vraixen-mint kernel: Oops: 0003 [#1] SMP NOPTI
giu 20 19:49:10 vraixen-mint kernel: CPU: 4 PID: 1098 Comm: Xorg Tainted: P           OE     5.10.0-1029-oem #30-Ubuntu
giu 20 19:49:10 vraixen-mint kernel: Hardware name: Gigabyte Technology Co., Ltd. Z490 VISION D/Z490 VISION D, BIOS F5a 06/22/2020
giu 20 19:49:10 vraixen-mint kernel: RIP: 0010:memcpy_erms+0x6/0x10
...
giu 20 19:49:10 vraixen-mint kernel: Call Trace:
giu 20 19:49:10 vraixen-mint kernel:  ? os_mem_copy+0x10/0x20 [nvidia]
giu 20 19:49:10 vraixen-mint kernel:  _nv017679rm+0x56c/0x710 [nvidia]
giu 20 19:49:10 vraixen-mint kernel: WARNING: kernel stack frame pointer at 0000000039517294 in Xorg:1098 has bad value 00000000c953d549
...
giu 20 19:49:10 vraixen-mint kernel: ---[ end trace bb961c5e2a4175d9 ]---

Then a second Oops happens.

Code: Select all

giu 20 19:49:10 vraixen-mint kernel: Oops: 0000 [#2] SMP NOPTI

Then there is another problem, but this one does not mention Nvidia.

Code: Select all

giu 20 19:49:14 vraixen-mint kernel: general protection fault, probably for non-canonical address 0x28cd41a51ecfbebb: 0000 [#3] SMP NOPTI

Because you were having problems with the 5.4 kernel as well as with this 5.10-oem kernel, I would not think the kernel is the issue.

I am not sure if this is an issue with the Nvidia driver, something related to the GPU's hardware, or something else. One possible way to test if the GPU is okay is to install the nouveau (open-source) driver and test it. Have you tried that yet?

I did check the Nvidia forum to see if anyone was having a similar issue. There seemed to be quite a few issues and some people discovered if they used HDMI connections instead of Displayport then they were able to get graphics. I do not know if that might be a factor in your situation.

Let us know why you re-installed Mint as that might be a clue as to what is happening now.

I have reinstalled Mint because i messed with grub using grub customizer, so nothing particular.
The only change is that i got a new monitor.

So what you reccomend me to do practically?

[SMG]

So what you reccomend me to do practically?

I have heard grub customizer can cause issues, so that would be a good reason to re-install.

-- If you still have the old monitor, try booting with it attached instead of the new one (since Mint worked with that one).
-- Try installing the nouveau (xorg) driver to see if it works.

I believe the version of the Nvidia driver you installed now is different than the one you would have used a month ago (but I do not know that for sure). I did read on the Nvidia forum that some people were able to go back to an earlier Nvidia-460 version and have the displayports work properly. How are you connecting your monitor to the GPU?

[Vraixen]

So what you reccomend me to do practically?

I have heard grub customizer can cause issues, so that would be a good reason to re-install.

-- If you still have the old monitor, try booting with it attached instead of the new one (since Mint worked with that one).
-- Try installing the nouveau (xorg) driver to see if it works.

I believe the version of the Nvidia driver you installed now is different than the one you would have used a month ago (but I do not know that for sure). I did read on the Nvidia forum that some people were able to go back to an earlier Nvidia-460 version and have the displayports work properly. How are you connecting your monitor to the GPU?

Okay i can confirm you that with HDMI the driver work with DisplayPort not, it can be part of the problem that i have 2 monitor? (when i had installed mint it was working with both monitors using DP). Another weird thing is that my second monitor is connected with DP and it work but if i try to use my primary monitor with DP it does not... If can be useful mi monitor is a DELL Alienware (AW2518HF) it has a refresh rate of 240Hz, i don't know how can impact the drivers but in HDMI works fine
Now im wondering how can i make it work the drivers with DisplayPort.

[SMG]

Okay i can confirm you that with HDMI the driver work with DisplayPort not, it can be part of the problem that i have 2 monitor? (when i had installed mint it was working with both monitors using DP).

Progress is good! It's not good that DP does not work, but at least HDMI does which hopefully means Nvidia is working on a fix since many others seem to have the same problem.

Now im wondering how can i make it work the drivers with DisplayPort.

Someone on the Nvidia forum mentioned that if they went back to an earlier version of the Nvidia-460 driver then their monitors connected with DisplayPort worked. I will go check those threads and see if I can get the specific version number to try (and see if the newest Nvidia-460 has the problem fixed yet).

[Vraixen]

Okay i can confirm you that with HDMI the driver work with DisplayPort not, it can be part of the problem that i have 2 monitor? (when i had installed mint it was working with both monitors using DP).

Progress is good! It's not good that DP does not work, but at least HDMI does which hopefully means Nvidia is working on a fix since many others seem to have the same problem.

Now im wondering how can i make it work the drivers with DisplayPort.

Someone on the Nvidia forum mentioned that if they went back to an earlier version of the Nvidia-460 driver then their monitors connected with DisplayPort worked. I will go check those threads and see if I can get the specific version number to try (and see if the newest Nvidia-460 has the problem fixed yet).

Thank you so much for helping me. Thats really weird that don't like this monitor precisely... but with my ultrawide monitor connected with DP it work.
I'll wait to know what to do to be able to use DP.

[SMG]

Here are the Nvidia 460.80 Release Notes. I see two release highlights mention fixes for DisplayPort connections, but maybe those fixes broke something else based on the complaints on the Nvidia forum. (That is my guess as I do not know for sure.)

There is usually a little delay between when Nvidia releases a new version and when that new version becomes available in Driver Manager. It is possible you were using a different Nvidia driver version when you originally had Mint installed.

Nvidia has released the 460.84 version of the driver, but the only release highlights indicate support for two new cards. No fixes are listed.

In this thread Nvidia driver black screen problem (Ubuntu) poster mashiach404 at the bottom indicates, "latest know driver to work with DisplayPort is 460.73.01". Based on the date Nvidia released that driver and knowing there is a little delay between when the driver becomes available on Driver Manager, that is probably the driver you were using on your first install of Mint.

Here is the Linux x64 (AMD64/EM64T) Display Driver 460.73 from the Nvidia website.

Many people seem to be having issues related to the Nvidia-460 and Nvidia-465 drivers, so roblm put instructions in this post on how to install Nvidia drivers from Nvidia's website instead of using Driver Manager. He gives the link for the Nvidia-450, but you can decide if you want to try the 460.73 or the 450. Or if you want to continue using the 460.80 and use HDMI and rearrange your monitors to wait for a fix to be released by Nvidia. (I have no idea how long that might take.)

With any graphic driver changes, I recommend taking a Timeshift snapshot before you start.

[Vraixen]

Here are the Nvidia 460.80 Release Notes. I see two release highlights mention fixes for DisplayPort connections, but maybe those fixes broke something else based on the complaints on the Nvidia forum. (That is my guess as I do not know for sure.)

There is usually a little delay between when Nvidia releases a new version and when that new version becomes available in Driver Manager. It is possible you were using a different Nvidia driver version when you originally had Mint installed.

Nvidia has released the 460.84 version of the driver, but the only release highlights indicate support for two new cards. No fixes are listed.

In this thread Nvidia driver black screen problem (Ubuntu) poster mashiach404 at the bottom indicates, "latest know driver to work with DisplayPort is 460.73.01". Based on the date Nvidia released that driver and knowing there is a little delay between when the driver becomes available on Driver Manager, that is probably the driver you were using on your first install of Mint.

Here is the Linux x64 (AMD64/EM64T) Display Driver 460.73 from the Nvidia website.

Many people seem to be having issues related to the Nvidia-460 and Nvidia-465 drivers, so roblm put instructions in this post on how to install Nvidia drivers from Nvidia's website instead of using Driver Manager. He gives the link for the Nvidia-450, but you can decide if you want to try the 460.73 or the 450. Or if you want to continue using the 460.80 and use HDMI and rearrange your monitors to wait for a fix to be released by Nvidia. (I have no idea how long that might take.)

With any graphic driver changes, I recommend taking a Timeshift snapshot before you start.

i can finally and happily say that the drivers now are working... do you know why the drivers was working before i reinstalled mint? the simple explanation is that i was using the 460.73.01 version which has not this bug. I guess i'll use this version meanwhile they fix these damn drivers. Thank you again for your help

[SMG]

i can finally and happily say that the drivers now are working... do you know why the drivers was working before i reinstalled mint? the simple explanation is that i was using the 460.73.01 version which has not this bug. I guess i'll use this version meanwhile they fix these damn drivers. Thank you again for your help

Glad to hear it is working.

Please go to your first post in this thread, click the pencil icon, and add [SOVLED] to the title so others know you no longer need help on this issue.

[Vraixen]

i can finally and happily say that the drivers now are working... do you know why the drivers was working before i reinstalled mint? the simple explanation is that i was using the 460.73.01 version which has not this bug. I guess i'll use this version meanwhile they fix these damn drivers. Thank you again for your help

Glad to hear it is working.

Please go to your first post in this thread, click the pencil icon, and add [SOVLED] to the title so others know you no longer need help on this issue.

Before this post get closed can i ask if there's some differencies installing the driver through Driver Manager and through the run file downloaded from nvidia?
because i have a problem with steam and it won't launch.