Black background after kernel update

I updated/upgraded the kernel to from version 5.5.16-100.fc30.x86_64 to version 5.6.7.100.fc30.x86_64 and after restart en login my desktop is black and I can only see the mouse pointer, which I can still move.

From another similar discussion (upgrade of Fedora) I performed the command:
journalctl -b -1 -p4 --no-pager

Output:

-- Logs begin at Wed 2018-09-05 12:33:29 CEST, end at Fri 2020-05-15 15:01:01 CEST. --
May 15 14:47:20 some_name kernel: DMAR-IR: This system BIOS has enabled interrupt remapping
                               on a chipset that contains an erratum making that
                               feature unstable.  To maintain system stability
                               interrupt remapping is being disabled.  Please
                               contact your BIOS vendor for an update
May 15 14:47:20 some_name kernel: core: CPUID marked event: 'bus cycles' unavailable
May 15 14:47:20 some_name kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
May 15 14:47:20 some_name kernel:   #5  #6  #7
May 15 14:47:20 some_name kernel: pmd_set_huge: Cannot satisfy [mem 0xf4000000-0xf4200000] with a huge-page mapping due to MTRR override.
May 15 14:47:20 some_name kernel: pci 0000:00:1c.4: ASPM: current common clock configuration is broken, reconfiguring
May 15 14:47:20 some_name kernel: r8169 0000:07:00.0: can't disable ASPM; OS doesn't have ASPM control
May 15 14:47:20 some_name kernel: MXM: GUID detected in BIOS
May 15 14:47:21 some_name kernel: nouveau 0000:03:00.0: DRM: TMDS table script pointers not stubbed
May 15 14:47:24 some_name systemd-vconsole-setup[641]: KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument
May 15 14:47:24 some_name systemd-vconsole-setup[641]: Fonts will not be copied to remaining consoles
May 15 14:47:26 some_name kernel: printk: systemd: 23 output lines suppressed due to ratelimiting
May 15 14:47:26 some_name systemd-vconsole-setup[681]: KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument
May 15 14:47:26 some_name systemd-vconsole-setup[681]: Fonts will not be copied to remaining consoles
May 15 14:47:26 some_name kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x000000000000042C-0x000000000000042D (\GP2C) (20191018/utaddress-204)
May 15 14:47:26 some_name kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
May 15 14:47:26 some_name kernel: kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using workaround
May 15 14:47:26 some_name systemd-vconsole-setup[902]: KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument
May 15 14:47:26 some_name systemd-vconsole-setup[902]: Fonts will not be copied to remaining consoles
May 15 14:47:26 some_name systemd-vconsole-setup[903]: KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument
May 15 14:47:26 some_name systemd-vconsole-setup[903]: Fonts will not be copied to remaining consoles
May 15 14:47:28 some_name colord[1075]: failed to get edid data: EDID length is too small
May 15 14:47:28 some_name colord[1075]: failed to get session [pid 1060]: No data available
May 15 14:47:28 some_name colord[1075]: failed to get session [pid 1060]: No data available
May 15 14:47:28 some_name colord[1075]: failed to get session [pid 1060]: No data available
May 15 14:47:31 some_name kernel: kauditd_printk_skb: 68 callbacks suppressed
May 15 14:49:03 some_name avahi-daemon[1156]: Disconnected from D-Bus, exiting.
May 15 14:49:05 some_name kernel: printk: systemd-shutdow: 58 output lines suppressed due to ratelimiting

I cannot make heads or tails from this output.

But if I restart with nomodeset in the boot menu the resolution is lower than normal (1600x1200).
Somehow the problem solved itself by rebooting again without nomodeset.
However, if I perform the same command
journalctl -b -1 -p4 --no-pager
I get a way longer output with some lines in red, which I have trouble reading it on a black background. An example of a line with red font: Glib-CRITICAL: g_child_watch_add_full: assertion 'pid > 0' failed

Should I do something?
EDIT: I should do something, but what?

After another reboot, and after login I got again a black desktop with only a mouse pointer visible.
And after another reboot, the program windows look they have a sepia filter over it.
If I open Terminal in Gnome Desktop it is complete black with only a blinking cursor. I can close Terminal with exit command. It works but is not readable.

From journalctl’s man page:

   -p, --priority=
       Filter output by message priorities or priority ranges. Takes
       either a single numeric or textual log level (i.e. between
       0/"emerg" and 7/"debug"), or a range of numeric/text log levels in
       the form FROM..TO. The log levels are the usual syslog log levels
       as documented in syslog(3), i.e.  "emerg" (0), "alert" (1),
       "crit" (2), "err" (3), "warning" (4), "notice" (5), "info" (6),
       "debug" (7). If a single log level is specified, all messages with
       this log level or a lower (hence more important) log level are
       shown. If a range is specified, all messages within the range are
       shown, including both the start and the end value of the range.
       This will add "PRIORITY=" matches for the specified priorities.

Try the more important numbers, 0, 1, 2 and maybe 3 and see if something corresponds to some serious problem.

Would you happen to have night light enabled in the display settings?

At first glance, it seems to suggest the kernel is unable to request information from your monitor to know what modes it supports.

hum… is it a laptop?

Does it have a monitor attached?

You could try to install monitor-edid and see what is it output…
else, as you already know to boot with nomodeset, you could:

journalctl -g VESA --no-pager
maybe pipe it through | fpaste
to get it on the web, and get a link to it you could post here.

It was on, but not active. Turning it off made it worse :slight_smile:

It is an old desktop with Gigabyte X58A-UD3R motherboard, Intel Core i7 CPU 930, 12 GB RAM with a 21" Wacom DTZ-2100D as monitor connected to an old NVIDIA graphics card.
If I go to Display Settings in Gnome it shows that there is an unknown monitor next to the Wacom, but there is only the Wacom connected.

Problem Reporting shows also errors from today.

The following is done by starting with the previous kernel version Linux some_name 5.5.16-100.fc30.x86_64

I removed the old lines until yesterday. They were all same:

Output from
journalctl -g VESA --no-pager
https://paste.centos.org/view/62e217c1

mei 15 15:38:59 some_name /usr/libexec/gdm-x-session[2738]: (II) VESA(0): VESA VBE DDC supported
mei 15 15:38:59 some_name /usr/libexec/gdm-x-session[2738]: (II) VESA(0): VESA VBE DDC Level none
mei 15 15:38:59 some_name /usr/libexec/gdm-x-session[2738]: (II) VESA(0): VESA VBE DDC transfer in appr. 0 sec.
mei 15 15:38:59 some_name /usr/libexec/gdm-x-session[2738]: (II) VESA(0): VESA VBE DDC read failed
mei 15 15:38:59 some_name /usr/libexec/gdm-x-session[2738]: (II) VESA(0): VESA VBE PanelID read successfully
mei 15 15:38:59 some_name /usr/libexec/gdm-x-session[2738]: (II) VESA(0): PanelID returned panel resolution -13184x-8470
mei 15 15:38:59 some_name /usr/libexec/gdm-x-session[2738]: (II) VESA(0): …which I refuse to believe
mei 15 15:38:59 some_name /usr/libexec/gdm-x-session[2738]: (II) VESA(0): Searching for matching VESA mode(s):
mei 15 15:38:59 some_name /usr/libexec/gdm-x-session[2738]: (II) VESA(0): Total Memory: 4096 64KB banks (262144kB)

I agree with VESA driver, a resolution of -13184x-8470 seems weird…
in part because negative values for resolution is weird.

mei 15 15:38:59 some_name /usr/libexec/gdm-x-session[2738]: (II) VESA(0): VESA VBE OEM Software Rev: 5.115
mei 15 15:38:59 some_name /usr/libexec/gdm-x-session[2738]: (II) VESA(0): VESA VBE OEM Vendor: NVIDIA Corporation
mei 15 15:38:59 some_name /usr/libexec/gdm-x-session[2738]: (II) VESA(0): VESA VBE OEM Product: G73 Board - p501h7b
mei 15 15:38:59 some_name /usr/libexec/gdm-x-session[2738]: (II) VESA(0): VESA VBE OEM Product Rev: Chip Rev
mei 15 15:38:59 some_name /usr/libexec/gdm-x-session[2738]: (II) VESA(0): Creating default Display subsection in Screen section

ok

mei 15 15:38:59 some_name /usr/libexec/gdm-x-session[2738]: (II) VESA(0): Setting up VESA Mode 0x118 (1024x768)

1024x768 seems a reasonable mode when you don’t know

I don’t see EDID information… except for panel returned resolution

Searching your monitor model…
https://www.manualslib.com/manual/378127/Wacom-Dtz-2100d.html?page=31
Supports 1600x1200
Plug&Play: DDC2B … don’t know that.
2007 active-matrix LCD display.

It seems the driver that should handle DDC2B would be:


according to:

I think current Linux does not handle well, DDC2B anymore.

You should create an Xorg.conf file to describe your monitor.
Did not done that for a while… trying:

Section "Monitor"
Identifier "Wacom DTZ-2100D"
HorizSync 31-92
VertRefresh 56-85
DisplaySize 432 324
# 1600x1200 @ 60.00 Hz (GTF) hsync: 74.52 kHz; pclk: 160.96 MHz
Modeline "1600x1200_60.00" 160.96 1600 1704 1880 2160 1200 1201 1204 1242 HSync +Vsync
EndSection

except the doc says VertRefresh should be 60 if UXGA (1600x1200)… hum.

Using https://arachnoid.com/modelines/ I get:

# 1600x1200 @ 60.00 Hz (GTF) hsync: 74.52 kHz; pclk: 160.96 MHz
Modeline "1600x1200_60.00" 160.96 1600 1704 1880 2160 1200 1201 1204 1242 -HSync +Vsync

but I am hesitant…

I would suggest to use:
sudo nano /etc/X11/xorg.conf.d/23-mymonitor.conf
to create the file.

Also, your 7300 GT nvidia card, would be NV40 family on:
https://nouveau.freedesktop.org/wiki/FeatureMatrix/ which seems fine at first.

This got me thinking. I did had a two monitor setup with an Iiyama 22" CRT monitor and an 17" HP LCD monitor.
Since I returned to using only one monitor (Wacom) I still have this odd issue. The Display Settings shows always an Unknown Display. Even if I disconnect the Wacom and I connect the HP LCD monitor there is still this unknown display.


And my HP monitor is number 2 and the unknown monitor is number 1. I find that odd.

I have no display issues with the HP monitor. I don’t need to startup/boot with nomodeset in grub.
I did notice another odd thing. If I start my system with nomodeset with my HP monitor I found this in these lines:

mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): PanelID returned panel resolution 3074x20408

Which I would refuse to believe :thinking:

mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA: driver for VESA chipsets: vesa
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): initializing int10
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): Primary V_BIOS segment is: 0xc000
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA BIOS detected
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE Version 3.0
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE Total Mem: 262144 kB
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE OEM: NVIDIA
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE OEM Software Rev: 5.115
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE OEM Vendor: NVIDIA Corporation
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE OEM Product: G73 Board - p501h7b
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE OEM Product Rev: Chip Rev
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): Creating default Display subsection in Screen section
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (==) VESA(0): Depth 24, (--) framebuffer bpp 32
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (==) VESA(0): RGB weight 888
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (==) VESA(0): Default visual is TrueColor
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE DDC supported
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE DDC Level none
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE DDC transfer in appr. 0 sec.
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE DDC read failed
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE PanelID read successfully
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): PanelID returned panel resolution 3074x20408
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): Searching for matching VESA mode(s):
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): Total Memory: 4096 64KB banks (262144kB)
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): <default monitor>: Using hsync range of 29.37-1259.20 kHz
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): <default monitor>: Using vrefresh range of 56.00-60.00 Hz
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (WW) VESA(0): Unable to estimate virtual size
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): Not using built-in mode "1024x768" (no mode of this name)
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): Not using built-in mode "800x600" (no mode of this name)
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): Not using built-in mode "640x480" (no mode of this name)
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): Not using built-in mode "640x400" (no mode of this name)
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): Not using built-in mode "320x400" (no mode of this name)
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): Not using built-in mode "320x240" (no mode of this name)
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): Not using built-in mode "320x200" (no mode of this name)
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (WW) VESA(0): No valid modes left. Trying less strict filter...
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): <default monitor>: Using hsync range of 29.37-1259.20 kHz
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): <default monitor>: Using vrefresh range of 56.00-60.00 Hz
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (WW) VESA(0): Unable to estimate virtual size
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): Not using built-in mode "640x400" (hsync out of range)
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): Not using built-in mode "320x400" (hsync out of range)
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): Not using built-in mode "320x240" (illegal horizontal timings)
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): Not using built-in mode "320x200" (illegal horizontal timings)
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): Virtual size is 1024x768 (pitch 1024)
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (**) VESA(0): *Built-in mode "1024x768"
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (**) VESA(0): *Built-in mode "800x600"
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (**) VESA(0): *Built-in mode "640x480"
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (==) VESA(0): DPI set to (96, 96)
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (**) VESA(0): Using "Shadow Framebuffer"
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): initializing int10
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): Primary V_BIOS segment is: 0xc000
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA BIOS detected
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE Version 3.0
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE Total Mem: 262144 kB
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE OEM: NVIDIA
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE OEM Software Rev: 5.115
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE OEM Vendor: NVIDIA Corporation
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE OEM Product: G73 Board - p501h7b
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): VESA VBE OEM Product Rev: Chip Rev
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): virtual address = 0x7f3cc8d50000, VGAbase = 0x7f3cd8e9a000
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (II) VESA(0): Setting up VESA Mode 0x118 (1024x768)
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (==) VESA(0): Default visual is TrueColor
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (==) VESA(0): Backing store enabled
mei 16 13:46:52 some_name /usr/libexec/gdm-x-session[3288]: (==) VESA(0): DPMS enabled

I did not create .conf file yet, because you said you were hesitant. Why? Is there a risk involved?
Can I create in this .conf file multiple lines starting with Modeline?
Thanks already for putting this much effort in it! :+1:

I am not too worry about an incorrect .conf file.

I means, in the very beginning, sending a wrong signal to the monitor could break it… on some uncommon models… but I believe your monitors are still new enough to just show an invalid resolution message on the screen it that happens.

I would like to remember you that you are supposed to power-off computer and monitor before changing connections… although I admit I often don’t.

Clearly the goal of the conf file is to get the higher resolution I think… maybe it would be best to just comment out the line with vertical refresh… as the default seems 56-60 Hertz, and seems fine…

Now, my other problem is that I don’t think my monitor section is enough… I think you need a server section that reference it … searching a bit…

Also… you have:
VESA VBE DDC Level none
VESAA VBE DDC read failed

So my guess the panel resolution you get is some kind of ghost values because it was not able to talk to the monitor, as DDC level none, seems equivalent to not supporting DDC.

Maybe change the conf file to:

Section "Monitor"
  Identifier "Wacom DTZ-2100D"
  HorizSync 31-92
  # real value but i 1600x1200 should be 60 Hz: VertRefresh 56-85
  VertRefresh 60-60
  DisplaySize 432 324
  # 1600x1200 @ 60.00 Hz (GTF) hsync: 74.52 kHz; pclk: 160.96 MHz
  Modeline "1600x1200_60.00" 160.96 1600 1704 1880 2160 1200 1201 1204 1242 -HSync +Vsync
  Option         "PreferredMode"  "1600x1200_60.00"
EndSection

Hey… I think I will try it on my computer… and see how much bad it do.

Well… that’s not seems enough for Xorg to apply it.

Haha, You mean the .conf file needs more than just a Monitor section?
Well, I trust that a Wacom monitor with a DVI connector is new enough :smile: So I started right away to experiment and I believe so.that something is missing indeed. Somewhere the boot stops. I boot the system with quiet removed in grub
I still can switch with CTRL-ALT F2 to another console and login to edit the file and reboot the system. I use vi btw.
Hmmm, probably a typo somehere in the file HSync is not a valid keyword in this section. Parse error. No screen found. Unable to run X server. Termination reason code 7. Hmm, let’s dive in it.

At the end, I now have:

Section "Monitor"
  Identifier "DTZ2100"
  HorizSync 31-92
  # real value but i 1600x1200 should be 60 Hz: VertRefresh 56-85
  VertRefresh 60-60
  DisplaySize 432 324
  # 1600x1200 @ 60.00 Hz (GTF) hsync: 74.52 kHz; pclk: 160.96 MHz
  Modeline "1600x1200_60.00" 160.96 1600 1704 1880 2160 1200 1201 1204 1242 -HSync +Vsync
  Option         "PreferredMode"  "1600x1200_60.00"
EndSection

Section "Device"
    Identifier "nvidia card"
    Driver "nouveau"
    #Driver "vesa"
EndSection

Section "Screen"
  Identifier "Wacom"
  Monitor "DTZ2100"
  DefaultDepth 24
    SubSection "Display"
      Depth      24
    EndSubSection
  Device "nvidia card"
EndSection

But because for me, detection of the screen info works… it use it … in part.
For me it had chosen 1280x1024 resolution… will stop to look at this a few hours now.

Seems you have the version where I had Hsync rather than -HSync

I just hope you don’t have the option that was disabling automatic add of the keyboard and mouse too!

That’s what I found out indeed :smiley:
Well, the extra sections did the trick. After first login to the desktop the background was black with only a mouse pointer. After second reboot everything went well. Don’t know why the first time it remained black.
This is my .conf file with minor changes and additions.

Section "Monitor"
  Identifier 	"Cintiq Tablet"
  VendorName 	"Wacom"
  ModelName 	"DTZ-2100D"
  HorizSync 	31-92
  VertRefresh 	56-85
  DisplaySize 	432 324
# 1600x1200 @ 60.00 Hz (GTF) hsync: 74.52 kHz; pclk: 160.96 MHz
  Modeline	"1600x1200_60.00" 160.96 1600 1704 1880 2160 1200 1201 1204 1242 -HSync +Vsync
  Option        "PreferredMode"  "1600x1200_60.00"
EndSection

Section "Device"
  Identifier	"NVIDIA adapter" 
  Driver	"nouveau"
EndSection

Section "Screen"
  Identifier	"Wacom"
  Monitor	"Cintiq Tablet"
  DefaultDepth	24
    SubSection	"Display"
      Depth	24
    EndSubSection
  Device	"NVIDIA adapter"
EndSection

Do you think I need in the Monitor section the following line?

  Option "DPMS" "true"

You mean this in 00-keyboard.conf?

Section "InputClass"
        Identifier "system-keyboard"
        MatchIsKeyboard "on"
        Option "XkbLayout" "us"
        Option "XkbVariant" "euro"
EndSection

I had no issues with my mouse and keyboard, although it is a crappy cordless Logitech set. Sometimes the keyboard hangs.
You were a great help, Paul. Thank you very much. Probably I will dive more into this and play around with more settings :smiley:

In a previous version I had:

 Option "AutoAddDevices" "false"

and I was not able to use any input devices with that… (because I had none defined)… and so I had to use a live usb key to fix my .conf file.

I think it would enable to have the screen to go in energy saving mode when not use a while… I think it is a good idea… but I don’t know this much…

So it really used the 1600x1200 resolution? It kind of impress me if it does!

Yes, it did. And here is your proof :smiley:

And I also think I know what this unknown display is. It might be the TV/Video-output on the card, which has nothing connected to it. It looks like an S-video connector but with more holes. But anyhow it works!

1 Like

After all this… it have come to my mind that maybe this is your DVI cable that does not have the pins to handle DDC2B…

I say in part because you have 2 monitors that were not able to read info from the monitor.

Maybe a VGA cable would have done better.

These are pins from the Wacom. Fourth and fifth black square from the top row are pin 6 and pin7. According to the wiki article pin 6 is DDC clock and pin 7 is DDC data. It is available I think. :man_shrugging:

Reading your Wacom manual, I see there is a switch behind your monitor: DVI/VGA… have you checked it is in DVI mode? I make the hypothesis it could be in VGA mode, and sending the signal to DVI on the 4 pins of VGA compatibility… that would not have DDC support. That would be on the top left when looking behind… would be the one the more to the left.

Yes, the switch is in DVI mode.

While I was playing with my .conf file at some moments my Gnome Desktop froze, had GPU lockups and so on. So I reverted back to the last working .conf settings as in our previous posts above. But my desktop remained black with only a mouse pointer. Unfortunately, I am back where I started.

In the meanwhile I updated my kernel to 5.6.11-100.fc30.x86_64 hoping it will solve the black blackground.
It did kinda solve. My desktop was one time only not black, but text was a little garbled. For example, in the bottom right corner it shows a yellow bar instead of the text fedora. Some windows are completely white. Sometimes you can see the shades of the bars, buttons etc. You can close the open windows by clicking somewhere in the top right corner.
After next boot. It was black again. Gnome desktop thinks two monitors are connected. Display 2 is the Wacom on the left. Display 1 is TV-1 on the right. The displays are aligned to the top. I know this because my pointer hits in the bottom half the right edge of display 2. At the top half of my right edge I can move my pointer away ‘off’ the display.

For now I cannot use my Wacom as a monitor. With my HP as a monitor I do not have any issues.
In both cases I did the following to see the differences. I noticed some odd things.

journalctl -b -g NOUVEAU --no-pager

HP connected to D-SUB/VGA

mei 17 12:36:30 no_name /usr/libexec/gdm-x-session[1449]: (II) NOUVEAU(0): EDID for output DVI-I-1
mei 17 12:36:30 no_name /usr/libexec/gdm-x-session[1449]: (II) NOUVEAU(0): Manufacturer: HWP  Model: 2609  Serial#: 858931783
mei 17 12:36:30 no_name /usr/libexec/gdm-x-session[1449]: (II) NOUVEAU(0): Year: 2004  Week: 19
mei 17 12:36:30 no_name /usr/libexec/gdm-x-session[1449]: (II) NOUVEAU(0): EDID Version: 1.3
mei 17 12:36:30 no_name /usr/libexec/gdm-x-session[1449]: (II) NOUVEAU(0): Analog Display Input,  Input Voltage Level: 0.700/0.700 V

Output DVI-I and VGA is other way around, which I find odd. Output TV is unused and not connected. I wish I could set it to disconnected.

mei 17 12:36:30 no_name /usr/libexec/gdm-x-session[1449]: (II) NOUVEAU(0): Output DVI-I-1 connected
mei 17 12:36:30 no_name /usr/libexec/gdm-x-session[1449]: (II) NOUVEAU(0): Output VGA-1 disconnected
mei 17 12:36:30 no_name /usr/libexec/gdm-x-session[1449]: (II) NOUVEAU(0): Output TV-1 connected

No, there is nothing to span.

mei 17 12:36:30 no_name /usr/libexec/gdm-x-session[1449]: (II) NOUVEAU(0): Using spanning desktop for initial modes
mei 17 12:36:30 no_name /usr/libexec/gdm-x-session[1449]: (II) NOUVEAU(0): Output DVI-I-1 using initial mode 1280x1024 +0+0
mei 17 12:36:30 no_name /usr/libexec/gdm-x-session[1449]: (II) NOUVEAU(0): Output TV-1 using initial mode 720x576 +1280+0
mei 17 12:36:30 no_name /usr/libexec/gdm-x-session[1449]: (II) NOUVEAU(0): Output DVI-I-1 using initial mode 1280x1024 +0+0
mei 17 12:36:30 no_name /usr/libexec/gdm-x-session[1449]: (II) NOUVEAU(0): Output TV-1 using initial mode 720x576 +1280+0
mei 17 12:36:30 no_name /usr/libexec/gdm-x-session[1449]: (==) NOUVEAU(0): Using gamma correction (1.0, 1.0, 1.0)
mei 17 12:36:30 no_name /usr/libexec/gdm-x-session[1449]: (II) NOUVEAU(0): Virtual size is 2000x1024 (pitch 0)

Wacom connected to DVI

May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): EDID for output DVI-I-1
May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): EDID for output VGA-1
May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): Manufacturer: WAC  Model: 1014  Serial#: 96
May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): Year: 2009  Week: 45
May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): EDID Version: 1.3
May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): Digital Display Input

Looks promising, especially #5

May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): Supported standard timings:
May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): #0: hsize: 640  vsize 480  refresh: 85  vid: 22833
May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): #1: hsize: 800  vsize 600  refresh: 85  vid: 22853
May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): #2: hsize: 1024  vsize 768  refresh: 85  vid: 22881
May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): #3: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): #4: hsize: 1280  vsize 1024  refresh: 85  vid: 39297
May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): #5: hsize: 1600  vsize 1200  refresh: 60  vid: 16553

Same story here, Output DVI-I and VGA is other way around and TV is not connected.

May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): Output DVI-I-1 disconnected
May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): Output VGA-1 connected
May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): Output TV-1 connected

Again, nothing to span. There is only one monitor connected.

May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): Using spanning desktop for initial modes
May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): Output VGA-1 using initial mode 1600x1200 +0+0
May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): Output TV-1 using initial mode 720x576 +1600+0
May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (==) NOUVEAU(0): Using gamma correction (1.0, 1.0, 1.0)
May 17 13:03:35 no_name /usr/libexec/gdm-x-session[1467]: (II) NOUVEAU(0): Virtual size is 2320x1200 (pitch 0)

A link to full outputs will follow soon.
Full output HP monitor https://paste.centos.org/view/f2e2dbea
Full output Wacom monitor https://paste.centos.org/view/462cdc48

It seems that you can.
You could boot with kernel parameter: nouveau.tv_disable=1.
I just found that by doing modinfo nouveau.
You can make it permanent, for one kernel version, by editing:

sudo su
cd cd /boot/loader/entries/

and then edit one of the entries… and make the line looks like:

options $kernelopts nouveau.tv_disable=1

I am glad you get EDID information from your monitors now… and that the nouveau driver shos that information!

You know that when it is not black… and you can use it… then you can use the -b -1 or -b -2 of journalctl, to get to previous boot sessions when it was black… so that you can investigate what journalctl was saying for black sessions. Also I suggest to people to use --no-pager when I suggest to | fpaste but in normal conditoins, you should probably omit it so that it does like | less making it easy to read and go back.

Also, you might want to explore the use of xrandr, most likely by reading man xrandr

At first, I thought of a bug with nouveau driver… but since it works with HP monitor… I am unsure what to think.

True! I did so many reboots I lost count. In yum/dnf history I could find the time of update. I will look into that.
I did multiple outputs of journalctl to see the differences.

  • kernel 5.5.x / Wacom switch on VGA
  • kernel 5.5.x / Wacom switch on DVI
  • kernel 5.6.x / Wacom switch on VGA
  • kernel 5.6.x / Wacom switch on DVI

For now kernel version 5.6.x does not work well with 1600x1200@60Hz on my Wacom without tweaking somewhere. There must be way to get it working.

I have to find a way on how to keep my last good working kernel version in the boot menu, just like the rescue boot menu entry. I do not want to loose that entry after another kernel update.

I had to boot into kernel version 5.5.x to set the resolution in 1280x1024@60Hz and then boot into kernel version 5.6.x.

I have read swiftly about it, but I did not dive into it yet. What I have read seemed promising.
I will get back later. It’s dinner time! Cannot think on an empty stomach :smiley:

The outputs of journalctl -g NOUVEAU are the same for both kernel versions now.
Perhaps I should dive into the complete bootlog, to see if something ‘unrelated’ might be the root cause of the display problems at 1600x1200@60Hz with the new kernel version.
https://paste.centos.org/view/6b52b4ea
https://paste.centos.org/view/da3716e3

Some parts which caught my attention are the refresh rates. They are all 0.0:

(II) NOUVEAU(0): NVEnterVT is called.
(II) NOUVEAU(0): Setting screen physical size to 423 x 317
(II) NOUVEAU(0): EDID vendor "WAC", prod id 4116
(II) NOUVEAU(0): Using EDID range info for horizontal sync
(II) NOUVEAU(0): Using EDID range info for vertical refresh
(II) NOUVEAU(0): Printing DDC gathered Modelines:
(II) NOUVEAU(0): Modeline "1600x1200"x0.0  162.00  1600 1664 1856 2160  1200         1201 1204 1250 +hsync +vsync (75.0 kHz eP)
(II) NOUVEAU(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
(II) NOUVEAU(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
(II) NOUVEAU(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
(II) NOUVEAU(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
(II) NOUVEAU(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
(II) NOUVEAU(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
(II) NOUVEAU(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
(II) NOUVEAU(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
(II) NOUVEAU(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769     772 800 +hsync +vsync (60.0 kHz e)
(II) NOUVEAU(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
(II) NOUVEAU(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
(II) NOUVEAU(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
(II) NOUVEAU(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
(II) NOUVEAU(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
(II) NOUVEAU(0): Modeline "640x480"x0.0   36.00  640 696 752 832  480 481 484 509 -hsync -vsync (43.3 kHz e)
(II) NOUVEAU(0): Modeline "800x600"x0.0   56.25  800 832 896 1048  600 601 604 631 +hsync +vsync (53.7 kHz e)
(II) NOUVEAU(0): Modeline "1024x768"x0.0   94.50  1024 1072 1168 1376  768 769 772 808 +hsync +vsync (68.7 kHz e)
(II) NOUVEAU(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
(II) NOUVEAU(0): Modeline "1280x1024"x0.0  157.50  1280 1344 1504 1728  1024     1025 1028 1072 +hsync +vsync (91.1 kHz e)

xrandr works only in Terminal. In console you get “Can’t open display” which is actually obvious

xrandr shows the following:

Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 4096 x 4096
DVI-I-1 disconnected (normal left inverted right x axis y axis)
VGA-1 connected primary 1280x1024+0+0 (normal left inverted right x axis y axis) 432mm x 324mm
   1600x1200     60.00 +
   1280x1024     85.02    75.02    60.02* 
   1024x768      85.00    75.03    70.07    60.00  
   832x624       74.55  
   800x600       85.06    72.19    75.00    60.32    56.25  
   640x480       85.01    75.00    72.81    66.67    59.94  
   720x400       70.08  
TV-1 disconnected (normal left inverted right x axis y axis)

It’s getting late. Have to work tomorrow (at home).