My greatest LM disappointment-Multiple monitors failure w/Nvidia

aaron · Post by **aaron** » Wed Mar 29, 2023 4:31 am

Sorry for the clickbait title, but...it's true.

I've been using linux for > 10 yrs.

I've gone through the graphics tips troubleshooting page.

My objective: To be able to use at least 2 or more monitors (since I want to trade markets online.)
I want to use DVI connections b/c my monitors have only VGA & DVI connectors.
All monitors are 22/23 inch.

If I use noveau driver, I can use 2 (Envision and MAG) monitors, but only if use the MAG as the second screen (via the nVidia DVI cable).
In the system settings control panel, the computer doesn't recognize LG or Samsung screens. If I use the VGA cable as a 3rd screen, the resolution is terrible.

If I use the nvidia 340 driver (recommended ), I got a black screen/blinking cursor screen w/any screen hooked up (took >3 hours to fix)

If I use the nvidia 390 driver only one screen will work at a time, and only through the motherboard Intel graphics chip. (Nvidia connection doesn't work at all!! and yes, I've used DVI multiple cables to test)

Synaptic says that I have nvidia prime installed, and there's no broken packages. Today, it's not showing up on my menu, and yesterday, when it was there, the applet just said "ERR". In the past, when the Nvidia X-server app was there, it always displayed an empty box.

I can't find the link, so I'm doing this by heart, but I did the fix that said to go into etc/modules and added 4 lines: CODE: SELECT ALL, nvidia, nvidia-drm, nvidia nomodeset.
BTW, my computer doesn't have "etc/modules", it has "etc/modules-load.d, and the file I modified was "modules.conf"
THANKS A MILLION!

Code: Select all

$ inxi -Fxxxrz
System:
  Kernel: 5.4.0-146-generic x86_64 bits: 64 compiler: gcc v: 9.4.0 
  Desktop: Cinnamon 4.8.6 wm: muffin 4.8.1 dm: GDM3 3.36.3 
  Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop Mobo: Gigabyte model: H97-HD3 v: x.x serial: <filter> 
  BIOS: American Megatrends v: F7 date: 04/22/2015 
CPU:
  Topology: Quad Core model: Intel Core i5-4460 bits: 64 type: MCP 
  arch: Haswell rev: 3 L2 cache: 6144 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 25542 
  Speed: 897 MHz min/max: 800/3400 MHz Core speeds (MHz): 1: 864 2: 873 
  3: 881 4: 892 
Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
  vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0412 
  Device-2: NVIDIA GF119 [GeForce GT 520] vendor: Point of View BV 
  driver: nouveau v: kernel bus ID: 05:00.0 chip ID: 10de:1040 
  Display: x11 server: X.Org 1.20.13 driver: vesa 
  unloaded: fbdev,modesetting resolution: 1680x1050~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) 
  v: 4.5 Mesa 21.2.6 compat-v: 3.0 direct render: Yes 
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
  driver: snd_hda_intel v: kernel bus ID: 00:03.0 chip ID: 8086:0c0c 
  Device-2: Intel 9 Series Family HD Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8ca0 
  Device-3: NVIDIA GF119 HDMI Audio vendor: Point of View BV 
  driver: snd_hda_intel v: kernel bus ID: 05:00.1 chip ID: 10de:0e08 
  Device-4: HP HP USB Webcam type: USB driver: snd-usb-audio,uvcvideo 
  bus ID: 3-3:2 chip ID: 03f0:8007 
  Device-5: Microsoft LifeChat LX-3000 Headset type: USB 
  driver: hid-generic,snd-usb-audio,usbhid bus ID: 3-10:5 chip ID: 045e:070f 
  Sound Server: ALSA v: k5.4.0-146-generic 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Gigabyte driver: r8169 v: kernel port: e000 bus ID: 02:00.0 
  chip ID: 10ec:8168 
  IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
  Device-2: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter 
  driver: 8139too v: 0.9.28 port: d000 bus ID: 04:00.0 chip ID: 10ec:8139 
  IF: enp4s0 state: down mac: <filter> 
Drives:
  Local Storage: total: 2.33 TiB used: 407.11 GiB (17.1%) 
  ID-1: /dev/sda model: SATA SSD size: 55.90 GiB speed: 6.0 Gb/s 
  serial: <filter> rev: 02.1 scheme: MBR 
  ID-2: /dev/sdb vendor: Seagate model: ST1500DL001-9VT15L size: 1.36 TiB 
  speed: 3.0 Gb/s rotation: 5900 rpm serial: <filter> rev: CC98 scheme: MBR 
  ID-3: /dev/sdc vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
  speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: A750 scheme: GPT 
Partition:
  ID-1: / size: 53.78 GiB used: 49.28 GiB (91.6%) fs: ext4 dev: /dev/sda5 
  ID-2: /boot size: 942.3 MiB used: 112.3 MiB (11.9%) fs: ext4 
  dev: /dev/sda1 
  ID-3: /home size: 910.31 GiB used: 357.70 GiB (39.3%) fs: ext4 
  dev: /dev/sdc2 
  ID-4: swap-1 size: 5.59 GiB used: 23.3 MiB (0.4%) fs: swap dev: /dev/sdc1 
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nouveau temp: 59 C 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list 
  1: deb http://repos.azulsystems.com/ubuntu stable main
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
  1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/dupeguru-ppa-focal.list 
  1: deb http://ppa.launchpad.net/dupeguru/ppa/ubuntu focal main
  2: deb-src http://ppa.launchpad.net/dupeguru/ppa/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
  1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/graphics-drivers-ppa-focal.list 
  1: deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal main
  2: deb-src http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com ulyssa main upstream import backport
  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
  Active apt repos in: /etc/apt/sources.list.d/official-source-repositories.list 
  1: deb-src http://packages.linuxmint.com ulyssa main upstream import backport
  2: deb-src http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb-src http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb-src http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb-src http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb-src http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
  1: deb [arch=amd64] https://repo.skype.com/deb stable main
  Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
  1: deb [signed-by=/usr/share/keyrings/teamviewer-keyring.gpg] https://linux.teamviewer.com/deb stable main
  Active apt repos in: /etc/apt/sources.list.d/winehq.list 
  1: deb [signed-by=/usr/share/keyrings/winehq.gpg] http://dl.winehq.org/wine-builds/ubuntu/ focal main
  Active apt repos in: /etc/apt/sources.list.d/zulu-openjdk.list 
  1: deb [ arch=amd64 ] https://repos.azul.com/zulu/deb/ stable main
Info:
  Processes: 293 Uptime: 1h 43m Memory: 7.56 GiB used: 4.02 GiB (53.2%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.4.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38

Post by **SMG** » Fri Mar 31, 2023 8:25 pm

aaron wrote: ⤴Wed Mar 29, 2023 4:31 amSystem:
Kernel: 5.4.0-146-generic x86_64 bits: 64 compiler: gcc v: 9.4.0
Desktop: Cinnamon 4.8.6 wm: muffin 4.8.1 dm: GDM3 3.36.3
Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal

What happened to LightDM? Cinnamon does not use GDM3.

How did you end up with the vesa driver loading?

Did you create a custom xorg.conf file which might have blocked something it should not have blocked?

Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0412
Device-2: NVIDIA GF119 [GeForce GT 520] vendor: Point of View BV
driver: nouveau v: kernel bus ID: 05:00.0 chip ID: 10de:1040
Display: x11 server: X.Org 1.20.13 driver: vesa
unloaded: fbdev,modesetting resolution: 1680x1050~60Hz, 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2)
v: 4.5 Mesa 21.2.6 compat-v: 3.0 direct render: Yes

The driver should be modesetting, but that is showing as unloaded.

Could you please give us a little history of how you ended up with your current LM20.1 install? If you still have your install media (usb/dvd), please boot to it and provide the output of inxi from it.

I suggest you clean this root partition ASAP because you are soon going to have problems logging in. In fact, I suspect you may already be getting warning messages.

Partition:
ID-1: / size: 53.78 GiB used: 49.28 GiB (91.6%) fs: ext4 dev: /dev/sda5
ID-2: /boot size: 942.3 MiB used: 112.3 MiB (11.9%) fs: ext4
dev: /dev/sda1
ID-3: /home size: 910.31 GiB used: 357.70 GiB (39.3%) fs: ext4
dev: /dev/sdc2
ID-4: swap-1 size: 5.59 GiB used: 23.3 MiB (0.4%) fs: swap dev: /dev/sdc1

What did you install from this repo?

Code: Select all

  Active apt repos in: /etc/apt/sources.list.d/graphics-drivers-ppa-focal.list 
  1: deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal main
  2: deb-src http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal main

aaron · Post by **aaron** » Mon Apr 10, 2023 7:45 am

Thanks SMG for your response!
I thought that I had checked "notify by email if there's a response box".
I never got an email, so I thought nobody answered my questions

SMG wrote: ⤴Fri Mar 31, 2023 8:25 pm
aaron wrote: ⤴Wed Mar 29, 2023 4:31 amSystem:
Kernel: 5.4.0-146-generic x86_64 bits: 64 compiler: gcc v: 9.4.0
Desktop: Cinnamon 4.8.6 wm: muffin 4.8.1 dm: GDM3 3.36.3
Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal
What happened to LightDM? Cinnamon does not use GDM3. I have no idea what happened to it, or why GDM is on my computer

How did you end up with the vesa driver loading? No idea!!

Did you create a custom xorg.conf file which might have blocked something it should not have blocked?
I searched etd/X11 and didn't find any such file

Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0412
Device-2: NVIDIA GF119 [GeForce GT 520] vendor: Point of View BV
driver: nouveau v: kernel bus ID: 05:00.0 chip ID: 10de:1040
Display: x11 server: X.Org 1.20.13 driver: vesa
unloaded: fbdev,modesetting resolution: 1680x1050~60Hz, 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2)
v: 4.5 Mesa 21.2.6 compat-v: 3.0 direct render: Yes

The driver should be modesetting, but that is showing as unloaded.
I don't understand this, but if my ignorance is acceptable to you, it's ok w/me

Could you please give us a little history of how you ended up with your current LM20.1 install? If you still have your install media (usb/dvd), please boot to it and provide the output of inxi from it.
I've had this LM20.1 for a long time....and I've updated it religiously since installation
I looked for and couldn't find the original usb drive....but I'm certain the source was linuxmint.com

I suggest you clean this root partition ASAP because you are soon going to have problems logging in. In fact, I suspect you may already be getting warning messages. OK, will do. thanks!

Partition:
ID-1: / size: 53.78 GiB used: 49.28 GiB (91.6%) fs: ext4 dev: /dev/sda5
ID-2: /boot size: 942.3 MiB used: 112.3 MiB (11.9%) fs: ext4
dev: /dev/sda1
ID-3: /home size: 910.31 GiB used: 357.70 GiB (39.3%) fs: ext4
dev: /dev/sdc2
ID-4: swap-1 size: 5.59 GiB used: 23.3 MiB (0.4%) fs: swap dev: /dev/sdc1

What did you install from this repo?
Code: Select all
  Active apt repos in: /etc/apt/sources.list.d/graphics-drivers-ppa-focal.list 
  1: deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal main
  2: deb-src http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal main
I don't know how to answer this question....

Post by **SMG** » Mon Apr 10, 2023 11:14 am

aaron wrote: ⤴Mon Apr 10, 2023 7:45 amI looked for and couldn't find the original usb drive....but I'm certain the source was linuxmint.com

The source is not relevant. I wanted you to boot with the install usb to show what the information should be.

aaron wrote: ⤴Mon Apr 10, 2023 7:45 amI have no idea what happened to it, or why GDM is on my compute

Apparently you installed something which made changes on your system. That change resulted in other changes in your system such that you no longer have a true Linux Mint install. Updates from Linux Mint do not make that happen.

If you don't know what you did, and you don't have an old Timeshift snapshot which dates back to before you made these changes to your system, then it may be best to back up your personal data and do a fresh install.

aaron · Post by **aaron** » Mon Apr 10, 2023 11:24 am

I don't have the original usb.
Now I have a 20.2 linux mint usb drive
will that work for what you want to find out?

Before I do the entire backup/wipe, would it be advised for me to ditch GDM and install light DM?

thanks!

Post by **SMG** » Mon Apr 10, 2023 11:30 am

aaron wrote: ⤴Mon Apr 10, 2023 11:24 am I don't have the original usb.
Now I have a 20.2 linux mint usb drive
will that work for what you want to find out?

Yes, that will work. Boot to a live session and provide the same inxi output like you did in the first post.

aaron wrote: ⤴Mon Apr 10, 2023 11:24 amBefore I do the entire backup/wipe, would it be advised for me to ditch GDM and install light DM?

I don't know if that would fix it or not. I've seen people who installed software and ended up with both LightDM and GDM3 on their system. Yours is the first I've seen with just GDM3. I don't know what else might have been changed because your graphics driver is also not correct. It would be a bunch of guesses to figure out how to undo what you did, but as long as you have your data backed up (so you can start over if need be), you can try getting it fixed.

aaron · Post by **aaron** » Mon Apr 10, 2023 4:12 pm

Here's the file from the usb mint 20.2 usb drive:

Code: Select all

mint@mint:~$ inxi -Fxxxrz
System:
  Kernel: 5.4.0-74-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 5.0.4 wm: muffin 5.0.1 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop Mobo: Gigabyte model: H97-HD3 v: x.x serial: <filter> 
  BIOS: American Megatrends v: F7 date: 04/22/2015 
CPU:
  Topology: Quad Core model: Intel Core i5-4460 bits: 64 type: MCP 
  arch: Haswell rev: 3 L2 cache: 6144 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 25541 
  Speed: 898 MHz min/max: 800/3400 MHz Core speeds (MHz): 1: 898 2: 898 
  3: 898 4: 898 
Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
  vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0412 
  Device-2: NVIDIA GF119 [GeForce GT 520] vendor: Point of View BV 
  driver: nouveau v: kernel bus ID: 05:00.0 chip ID: 10de:1040 
  Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1680x1050~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) 
  v: 4.5 Mesa 20.2.6 compat-v: 3.0 direct render: Yes 
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
  driver: snd_hda_intel v: kernel bus ID: 00:03.0 chip ID: 8086:0c0c 
  Device-2: Intel 9 Series Family HD Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8ca0 
  Device-3: NVIDIA GF119 HDMI Audio vendor: Point of View BV 
  driver: snd_hda_intel v: kernel bus ID: 05:00.1 chip ID: 10de:0e08 
  Device-4: HP HP USB Webcam type: USB driver: snd-usb-audio,uvcvideo 
  bus ID: 3-3:2 chip ID: 03f0:8007 
  Device-5: Microsoft LifeChat LX-3000 Headset type: USB 
  driver: hid-generic,snd-usb-audio,usbhid bus ID: 3-10:5 chip ID: 045e:070f 
  Sound Server: ALSA v: k5.4.0-74-generic 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Gigabyte driver: r8169 v: kernel port: e000 bus ID: 02:00.0 
  chip ID: 10ec:8168 
  IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
  Device-2: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter 
  driver: 8139too v: 0.9.28 port: d000 bus ID: 04:00.0 chip ID: 10ec:8139 
  IF: enp4s0 state: down mac: <filter> 
Drives:
  Local Storage: total: 2.39 TiB used: 39.67 GiB (1.6%) 
  ID-1: /dev/sda model: SATA SSD size: 55.90 GiB speed: 6.0 Gb/s 
  serial: <filter> rev: 02.1 temp: 30 C scheme: MBR 
  ID-2: /dev/sdb vendor: Seagate model: ST1500DL001-9VT15L size: 1.36 TiB 
  speed: 3.0 Gb/s rotation: 5900 rpm serial: <filter> rev: CC98 temp: 47 C 
  scheme: MBR 
  ID-3: /dev/sdc vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
  speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: A750 temp: 47 C 
  scheme: GPT 
  ID-4: /dev/sdd type: USB vendor: SanDisk model: Cruzer Blade 
  size: 7.45 GiB serial: <filter> rev: 1.26 scheme: MBR 
  ID-5: /dev/sde type: USB vendor: SanDisk model: Cruzer Blade 
  size: 58.42 GiB serial: <filter> rev: 1.00 scheme: MBR 
Partition:
  ID-1: / size: 3.78 GiB used: 19.3 MiB (0.5%) fs: overlay source: ERR-102 
  ID-2: /var/log size: 5.29 GiB used: 42.9 MiB (0.8%) fs: ext4 
  dev: /dev/sdd3 
  ID-3: swap-1 size: 5.59 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdc1 
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nouveau temp: 61 C 
  Fan Speeds (RPM): N/A 
Repos:
  Active apt repos in: /etc/apt/sources.list 
  1: deb cdrom:[Linux Mint 20.2 _Uma_ - Release amd64 20210703]/ focal contrib main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com uma 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
Info:
  Processes: 224 Uptime: N/A Memory: 7.56 GiB used: 699.5 MiB (9.0%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38

Post by **SMG** » Mon Apr 10, 2023 6:45 pm

System:
Kernel: 5.4.0-74-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Cinnamon 5.0.4 wm: muffin 5.0.1 dm: LightDM 1.30.0
Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal

Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0412
Device-2: NVIDIA GF119 [GeForce GT 520] vendor: Point of View BV
driver: nouveau v: kernel bus ID: 05:00.0 chip ID: 10de:1040
Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa
resolution: 1680x1050~60Hz, 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2)
v: 4.5 Mesa 20.2.6 compat-v: 3.0 direct render: Yes

I really do not have any ideas of how/why your system was switched from LightDM to GDM3. Maybe you could try the information in this Some Common Ubuntu Display Managers and How to Switch Between Them to get back to LightDM? I've never done it so I don't know if anything else might be needed because Linux Mint does not use GDM3.

aaron · Post by **aaron** » Tue Apr 11, 2023 3:30 am

Thanks, I switched over to lightDM, as the default, but no difference.

any other ideas?

Post by **SMG** » Tue Apr 11, 2023 10:56 am

aaron wrote: ⤴Tue Apr 11, 2023 3:30 am Thanks, I switched over to lightDM, as the default, but no difference.

What is the current output of

Code: Select all

inxi -SGxxx

aaron · Post by **aaron** » Tue Apr 11, 2023 11:25 am

This is using the current mint, not the usb drive:

Code: Select all

System:
  Host: tatti-H97-HD3 Kernel: 5.4.0-146-generic x86_64 bits: 64 
  compiler: gcc v: 9.4.0 Desktop: Cinnamon 4.8.6 wm: muffin 4.8.1 
  dm: LightDM 1.30.0 Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
  vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0412 
  Device-2: NVIDIA GF119 [GeForce GT 520] vendor: Point of View BV 
  driver: nouveau v: kernel bus ID: 05:00.0 chip ID: 10de:1040 
  Display: x11 server: X.Org 1.20.13 driver: modesetting 
  unloaded: fbdev,vesa resolution: 1680x1050~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) 
  v: 4.5 Mesa 21.2.6 compat-v: 3.0 direct render: Yes

Post by **SMG** » Tue Apr 11, 2023 11:32 am

aaron wrote: ⤴Tue Apr 11, 2023 3:30 am Thanks, I switched over to lightDM, as the default, but no difference.

What does "no difference" mean?

LightDM is now being used and the correct graphics driver is loaded.

System:
Host: tatti-H97-HD3 Kernel: 5.4.0-146-generic x86_64 bits: 64
compiler: gcc v: 9.4.0 Desktop: Cinnamon 4.8.6 wm: muffin 4.8.1
dm: LightDM 1.30.0 Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal
Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0412
Device-2: NVIDIA GF119 [GeForce GT 520] vendor: Point of View BV
driver: nouveau v: kernel bus ID: 05:00.0 chip ID: 10de:1040
Display: x11 server: X.Org 1.20.13 driver: modesetting
unloaded: fbdev,vesa resolution: 1680x1050~60Hz, 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2)
v: 4.5 Mesa 21.2.6 compat-v: 3.0 direct render: Yes

Turtletronic · Post by **Turtletronic** » Tue Apr 11, 2023 1:34 pm

aaron wrote: ⤴Wed Mar 29, 2023 4:31 am My greatest LM disappointment-Multiple monitors failure w/Nvidia

The OP does not seem to have verified if his decade old device can even provide for multiple monitors. Just because there are multiple output *options* does not mean that the card can provide for two different ones at the same time (or with the same resolution). Different vendors utilizing this chipset may (or may not) also provide "alternative" port configs with VGA/DVI/HDMI outlets; the problem however persists and DVI (especially over splitter cable) is often problematic with flat-chested cards. Online references show that the GF119/GT520 in various configurations is known to show the same behaviour under Windows ... go figure.

aaron · Post by **aaron** » Wed Apr 12, 2023 2:51 pm

How do you suggest I verify if it can even provide for multiple monitors?

(It does, but only w/the nouveau driver, as mentioned)

No splitter cable here.

Flat chested cards?????????????

Turtletronic · Post by **Turtletronic** » Fri Apr 14, 2023 7:08 pm

aaron wrote: ⤴Wed Apr 12, 2023 2:51 pm How do you suggest I verify if it can even provide for multiple monitors?

Best source of info is of course nvidia which does not sell or market your setup as multi-monitor capable in the first place. If you read up on what different VGA vendors made from it (including the various port configurations) you will also find hints enough which speak against various forms of multi-monitor use, including users that complain about similar problems like yours. You could of course also check the corresponding tech sites/forums which deal with (or talk about) multi-monitor problems in general; there you will find numerous enquiries regarding your (or similar) setups which all boil down to the same: your setup is simply not capable of serving your monitors as you wish.

aaron wrote: ⤴Wed Apr 12, 2023 2:51 pm Flat chested cards?????????????

The GF119/GT520 was intended for low level (single monitor) desktop use well over a decade ago. "Flat chested" is a term often used to describe something that is greatly underpowered.

aaron · Post by **aaron** » Sat Apr 15, 2023 3:07 pm

Wow.
Truly disappointing......
I made the assumption that since there were 2 'sockets', the video card or motherboard could handle 2 monitors at once.

Still the problem remains that even running one monitor per video card (built in or added on),

the nvidia drivers don't recognize 2 different DVI monitors at the same time (one MAG monitor is the exception), the Nvidia 340 driver (recommended) only gives a black screen, the Nvidea 390 driver doesn't work w/the nvidia card, and the only one that works is the non-nvidia driver, the noveau driver......

Post by **SMG** » Sat Apr 15, 2023 3:22 pm

aaron wrote: ⤴Sat Apr 15, 2023 3:07 pmStill the problem remains that even running one monitor per video card (built in or added on),

the nvidia drivers don't recognize 2 different DVI monitors at the same time

Why would you expect the Nvidia driver to recognize 2 different monitors if only one monitor is attached to it?

aaron · Post by **aaron** » Sat Apr 15, 2023 3:27 pm

One monitor per video chip.
One connected to the MB, one connected to the video card

Post by **SMG** » Sat Apr 15, 2023 3:35 pm

aaron wrote: ⤴Sat Apr 15, 2023 3:27 pm One monitor per video chip.
One connected to the MB, one connected to the video card

Please read what you wrote because it appears you are typing something other than what you may mean.

You said the Nvidia driver will not recognize two monitors yet you re-affirmed there is only one monitor attached to it. Therefore it does not make sense for the Nvidia driver to recognize two monitors when there is only one attached to it.

If you mean the Nvidia driver is not recognizing the one monitor attached to the Nvidia GPU, then that is different from what you just posted.

Linux Mint Forums

My greatest LM disappointment-Multiple monitors failure w/Nvidia

My greatest LM disappointment-Multiple monitors failure w/Nvidia

Re: My greatest LM disappointment-Multiple monitors failure w/Nvidia

Re: My greatest LM disappointment-Multiple monitors failure w/Nvidia

Re: My greatest LM disappointment-Multiple monitors failure w/Nvidia

Re: My greatest LM disappointment-Multiple monitors failure w/Nvidia

Re: My greatest LM disappointment-Multiple monitors failure w/Nvidia

Re: My greatest LM disappointment-Multiple monitors failure w/Nvidia

Re: My greatest LM disappointment-Multiple monitors failure w/Nvidia

Re: My greatest LM disappointment-Multiple monitors failure w/Nvidia

Re: My greatest LM disappointment-Multiple monitors failure w/Nvidia

Re: My greatest LM disappointment-Multiple monitors failure w/Nvidia

Re: My greatest LM disappointment-Multiple monitors failure w/Nvidia

Re: My greatest LM disappointment-Multiple monitors failure w/Nvidia

Re: My greatest LM disappointment-Multiple monitors failure w/Nvidia

Re: My greatest LM disappointment-Multiple monitors failure w/Nvidia

Re: My greatest LM disappointment-Multiple monitors failure w/Nvidia

Re: My greatest LM disappointment-Multiple monitors failure w/Nvidia

Re: My greatest LM disappointment-Multiple monitors failure w/Nvidia

Re: My greatest LM disappointment-Multiple monitors failure w/Nvidia