2nd monitor no signal after reboot

Support and Help
,
1

Ubuntu Version:
Ubuntu 24.04.4 LTS Linux 6.8.0-110-lowlatency 64 bit

Desktop Environment/System info:
HP HP ENVY Desktop TE02
GEForce RTX 3070 Lite Hash Rate
Driver = Nvidia (open kernel) Metapackage 580-open (proprietary-tested)

Problem Description:Installed Ubuntu 24.04.4 LTS and Ubuntu Studio. Everything was working fine for two days including both ViewSonic monitors. I believe problem arose when I attempted (and failed) to install the latest version of Resolve (followed the instructions to a tee). Later in the day I restarted Linux. Second monitor failed to work (no signal). When I viewed the system files, it still showed the initial driver (580). Everything else is working fine.

What I’ve Tried
I looked up current resolutions for my problem, but couldn’t find anything pertinent. Most said, check your connections, etc. Newbie stuff! That’s why I’m here, so I can get the best advice.

2

Welcome to the Ubuntu Discourse, Marion!

So let’s skip the newbie stuff. :wink:

Let’s start by examining those instructions to install “Resolve”; I have no knowledge of it. But before you start explaining let’s check the usual suspects. We’ll need a terminal and some command line tools for that.

A good place to start is always this command:

journalctl --no-hostname --boot --priority=err

That’ll give you all error messages since you started the system.

Let’s check the integrity of system packages next, because all too many guides instruct to overwrite files that shouldn’t be altered in the places they are. We’ll need the package debsums for that:

sudo apt install debsums

Then run:

sudo debsums --all --changed

That includes system files which should never be altered manually and configuration files, which may have different settings from the default.

And then you might want to tell us what you did – to the tee :wink: – to try and install “Resolve”. Maybe start with what it is, because I haven’t heard of it. Or just provide a link to the instructions you followed.

Please put all log and other console/terminal output in code blocks (</>), ideally wrapped in a “Hide Details” element. See items 4 and 5 in the Posting Guide.

Optional helper script

If you are so inclined, I took it upon myself to provide a little helper script for that. :sweat_droplets:

3

Thank you for your prompt reply. I shall give that a try tomorrow morning. Yes, I’m certain that something was altered that should not have been touched. As you can imagine, I will hold off on any attempt to reinstall Davinci Resolve, until they come up with a viable solution. I’ll keep you posted regarding the results. Again, thank you for reaching out.

4

Good morning. Had a chance to run terminal this morning.

~$ sudo debsums --all --changed
[sudo] password for marion:
/etc/gdm3/custom.conf

Apr 20 14:33:34 bluetoothd[1282]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Apr 20 14:33:34 bluetoothd[1282]: sap-server: Operation not permitted (1)
Apr 20 14:33:36 canonical-livepatch.canonical-livepatchd[1748]: refresh patch failed: livepatch check failed: POST request to "https://livepatch.canonical.com/v1/client/b50c1216eca948e6a64e61bf8a627c04/updates" failed: Post "https://livepatch.canonical.com/v1/client/b50c1216eca948e6a64e61bf8a627c04/updates": dial tcp: lookup livepatch.canonical.com on 127.0.0.53:53: server misbehaving
Apr 20 14:33:36 canonical-livepatch.canonical-livepatchd[1748]: Task "refresh" returned an error: livepatch check failed: POST request to "https://livepatch.canonical.com/v1/client/b50c1216eca948e6a64e61bf8a627c04/updates" failed: Post "https://livepatch.canonical.com/v1/client/b50c1216eca948e6a64e61bf8a627c04/updates": dial tcp: lookup livepatch.canonical.com on 127.0.0.53:53: server misbehaving, retrying in 30s.
Apr 20 14:33:39 hpfax[1959]: [1959]: error: Failed to create /var/spool/cups/tmp/.hplip
Apr 20 14:33:55 gdm3[1994]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Apr 20 14:33:56 (uidsynth)[2028]: fluidsynth.service: Failed to drop capabilities: Operation not permitted
Apr 20 14:33:56 systemd[2011]: Failed to start fluidsynth.service - FluidSynth Daemon.
Apr 20 14:33:56 gdm-autologin][2003]: gkr-pam: couldn't unlock the login keyring.
Apr 20 14:33:56 gdm3[1994]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Apr 20 14:33:56 gdm3[1994]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Apr 20 14:33:56 jackdbus[2072]: default: failed to stat "/home/marion/.config/jack/conf.xml", error is 2 (No such file or directory)
Apr 20 14:33:56 jackdbus[2072]: default: open() failed to open conf filename.
Apr 20 14:34:06 systemd[2011]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-2543.scope - Application launched by gnome-session-binary.
Apr 20 14:34:06 systemd[2011]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-2544.scope - Application launched by gnome-session-binary.
Apr 20 14:34:08 systemd[2011]: Failed to start app-gnome-im\x2dlaunch-2897.scope - Application launched by gnome-session-binary.
Apr 20 15:40:36 gdm3[1994]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Apr 20 15:40:57 gdm3[1994]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Apr 20 15:40:57 (uidsynth)[51602]: fluidsynth.service: Failed to drop capabilities: Operation not permitted
Apr 20 15:40:57 systemd[51588]: Failed to start fluidsynth.service - FluidSynth Daemon.
Apr 20 15:40:57 jackdbus[51635]: default: failed to stat "/var/lib/gdm3/.config/jack/conf.xml", error is 2 (No such file or directory)
Apr 20 15:40:57 jackdbus[51635]: default: open() failed to open conf filename.
Apr 20 15:41:06 gdm-password][52253]: gkr-pam: unable to locate daemon control file
Apr 20 15:41:06 (uidsynth)[52292]: fluidsynth.service: Failed to drop capabilities: Operation not permitted
Apr 20 15:41:06 systemd[52264]: Failed to start fluidsynth.service - FluidSynth Daemon.
Apr 20 15:41:06 jackdbus[52329]: default: failed to stat "/home/marion/.config/jack/conf.xml", error is 2 (No such file or directory)
Apr 20 15:41:06 jackdbus[52329]: default: open() failed to open conf filename.
Apr 20 15:41:06 gdm3[1994]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Apr 20 15:41:07 systemd[52264]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-52600.scope - Application launched by gnome-session-binary.
Apr 20 15:41:07 systemd[52264]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-52603.scope - Application launched by gnome-session-binary.
Apr 20 15:41:39 gdm3[1994]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed

Here is the link to the page regarding how to install Davinci Resolve

5

OK, thankfully that list is very short. :wink: But GDM3 is the GNOME Display Manager, so maybe it’s some setting you’ve changed and have forgotten about. What’s the output of:

cat /etc/gdm3/custom.conf

I keep circling back to the reboot. I seem to vaguely remember that some combos of monitor and graphics cards can exhibit issues especially in such scenarios; like the short on/off cycle tripping them up. And it doesn’t have to be the same for both, even if they are indentical monitors, because they cannot share the same connection port.
Have you tried disconnecting the signal cable and plugging it back in? That can help with snapping the monitor out of its limbo state, if that’s the case.

I haven’t had a look a the Resolve install instructions yet, just so you know.

1 Like
6 
# GDM configuration storage
#
# See /usr/share/gdm/gdm.schemas for a list of available options.

[daemon]
AutomaticLoginEnable=true
AutomaticLogin=marion

# Uncomment the line below to force the login screen to use Xorg
#WaylandEnable=false

# Enabling automatic login

# Enabling timed login
#  TimedLoginEnable = true
#  TimedLogin = user1
#  TimedLoginDelay = 10

[security]

[xdmcp]

[chooser]

[debug]
# Uncomment the line below to turn on debugging
# More verbose logs
# Additionally lets the X server dump core if it crashes
#Enable=true

The results of the cat”scan” :grinning_face: No, haven’t made any changes at all to the config files for the displays. I’m going to try a reboot again to see what happens. I’ll stay tuned for more…

7

And yes, have tried the tried and true and didn’t make a difference. I even swapped positions for monitors 1 and 2 into the graphics card. :melting_face:

8

Just did a reboot. Sad to say I still only have a solitary monitor. I know this will be something simple, but since I’m new to Linux, well, it may take a bit.

Now if it were Windows, I could most likely figure out on my own. Used to install networks for small business, taught a few classes and did private tutoring. Now entering a new zone, but I love learning so…

9

Question… doing some homework re: running Wayland or X11. I’m currently running Wayland. However, I see on some sites that running Wayland with a proprietary Nvidia, can sometimes cause problems. Would you suggest I switch to see if that’s a fix?

10

That’s not a bad idea, at all. BTW, what happened when switching places for the monitors? Is one permanently not working, not even on the other port? Or is one port out of order and both monitors don’t work on that?

FWIW, the Resolve installation instructions are harmless enough. I think they should have explored changing the order of shared library lookup, though.

1 Like
11

Quick study for Linux

https://www.xda-developers.com/this-nvidia-linux-driver-update-finally-fixes-a-frustrating-wayland-display-problem/

Upon more research regarding Wayland and Nvidia.

Says that the new driver will work with my RTX 3070

12

Made no difference the order of HDMI. Regardless, one monitor works at a time.

13

But which one? Is it the same monitor on two different ports? Or is it the same port but a different monitor each time?

14

Each monitor works when switched. Each monitor works (one at a time) when switched to port two.

15

My system is performing a backup right now, so I shall wait until later in the evening. Of course, will keep you informed on my progress.

Appreciatively, M

16

So it looks like it’s an issue with port one. That’s at least narrowing it down a little. The above error log doesn’t show any related messages, so we may need the warnings as well.

journalctl --no-hostname -b -p warning

But before you run that command, please do one cycle of un-/plugging on ports one and two. Hopefully there will be an event in the log just at the end then, at least for port two.

1 Like
17

One more thing to try just popped into my head. Can you run the Ubuntu Live installer in “Try Ubuntu” mode? If the two ports worked when you installed Ubuntu, then they should do so again with the Live session.

18 
Apr 21 17:02:33 kernel:   #1  #3  #5  #7  #9 #11 #13 #15
Apr 21 17:02:33 kernel: pnp 00:01: disabling [mem 0xc0000000-0xcfffffff] because it overlaps 0000:00:02.0 BAR 9 [mem 0x00000000-0xdfffffff 64bit pref]
Apr 21 17:02:33 kernel: hpet_acpi_add: no address or irqs in _CRS
Apr 21 17:02:33 kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Apr 21 17:02:33 kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
Apr 21 17:02:33 kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Apr 21 17:02:33 kernel: blacklist: Duplicate blacklisted hash bin:47ff1b63b140b6fc04ed79131331e651da5b2e2f170f5daef4153dc2fbc532b1
Apr 21 17:02:33 kernel: blacklist: Duplicate blacklisted hash bin:5391c3a2fb112102a6aa1edc25ae77e19f5d6f09cd09eeb2509922bfcd5992ea
Apr 21 17:02:33 kernel: blacklist: Duplicate blacklisted hash bin:80b4d96931bf0d02fd91a61e19d14f1da452e66db2408ca8604d411f92659f0a
Apr 21 17:02:33 kernel: blacklist: Duplicate blacklisted hash bin:992d359aa7a5f789d268b94c11b9485a6b1ce64362b0edb4441ccc187c39647b
Apr 21 17:02:33 kernel: blacklist: Duplicate blacklisted hash bin:c452ab846073df5ace25cca64d6b7a09d906308a1a65eb5240e3c4ebcaa9cc0c
Apr 21 17:02:33 kernel: blacklist: Duplicate blacklisted hash bin:e051b788ecbaeda53046c70e6af6058f95222c046157b8c4c1b9c2cfc65f46e5
Apr 21 17:02:33 kernel: pci 10000:e0:06.0: Primary bus is hard wired to 0
Apr 21 17:02:33 kernel: pci 10000:e0:06.0: Primary bus is hard wired to 0
Apr 21 17:02:33 kernel: usb: port power management may be unreliable
Apr 21 17:02:33 kernel: r8169 0000:3b:00.0: can't disable ASPM; OS doesn't have ASPM control
Apr 21 17:02:33 kernel: pcieport 10000:e0:06.0: can't derive routing for PCI INT D
Apr 21 17:02:33 kernel: pcieport 10000:e0:06.0: PCI INT D: no GSI
Apr 21 17:02:33 kernel: ahci 10000:e0:17.0: can't derive routing for PCI INT A
Apr 21 17:02:33 kernel: ahci 10000:e0:17.0: PCI INT A: no GSI
Apr 21 17:02:33 kernel: pcieport 10000:e0:06.0: can't derive routing for PCI INT A
Apr 21 17:02:33 kernel: nvme 10000:e1:00.0: PCI INT A: no GSI
Apr 21 17:02:33 lvm[759]: PV /dev/nvme0n1p3 online, VG ubuntu-vg is complete.
19

I will “Try Live” this morning to see if it brings functionality back.

20

That’s way too short a list, given that your errors list was longer. I think you need to run it again; I forgot that journalctl automatically opens a pager with long output:

journalctl --no-hostname --no-pager -b -p warning

Make sure to get the whole output. And don’t forget to un-/re-plug both ports before that.