Black screen at login for 10 minutes

I do this by removing the nvidia.conf and 90-mhwd.conf and reinstall the driver. It will recreate a default config.

OK so I removed all the old drivers, installed new nvidia drivers 450xx so both nvidia-settings and mhwd says the same:

$ mhwd -li
> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
    video-nvidia-450xx            2019.10.25               false            PCI

and

$ nvidia-smi 
Sat Aug 29 20:13:38 2020       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 450.66       Driver Version: 450.66       CUDA Version: 11.0     |
...

rebooting a couple of times still gives the same result.

It must be something that the ‘default’ boot-up does that just starting X doesn’t since it works just starting X from TTY2.

I discovered now, which is a bit embarrassing, that the default run level is TTY7.
So once I enter the correct password and login, the screen goes black but shifting to another TTY-level and back it works.
Its just a matter of removing the ‘black screen’ now.

Could you post a full journal log of your last boot?

jounrnalctl -b -0 > /home/$USER/journal.txt

That will create log in your home folder called journal.txt.

Also your enabled confgs in lightdm.conf could help:

grep -iv "^#" /etc/lightdm/lightdm.conf

Sure:

$ grep -iv "^#" /etc/lightdm/lightdm.conf
[LightDM]
run-directory=/run/lightdm

[Seat:*]
greeter-session=lightdm-slick-greeter
user-session=xfce
session-wrapper=/etc/lightdm/Xsession
greeter-setup-script=/usr/bin/numlockx on

[XDMCPServer]

[VNCServer]

and the log where I login, shift to TTY6 then back to TTY7:

I am not allowed to use links so:

https: //ufile. io/3ac6sxa7

The log has a duration of about 1min until you typed:

Aug 30 20:21:40 sudo[1225]:   Tim : TTY=pts/0 ; PWD=/home/Tim ; USER=root ; COMMAND=/usr/bin/journalctl -b0 --no-hostname

20:19:17 - 20:21:40
Where are the 9 minutes? :smiley:

If thats the case, than it have to be problem with the monitor, cable or the xorg server that it goes black.

Could you provide thiese logs:

/var/log/Xorg.0.log
/var/log/Xorg.0.log.old

:slight_smile:

If I just login, the screen goes black for more then 10 minutes then it works BUT if I shift TTY from 7 to something else then back it works.
Sorry, the title might be a bit misleading.

The logs:
https ://ufile .io/f/k5zht

Try to override Monitor detection. Since you are using only DFP, add this to the Device Section in /etc/X11/mhwd.d/nvidia.conf and reboot.

Option "ConnectedMonitor" "DFP"

Hmm made the screen black, could not get any screen at all.
Had to remove the option to get the screen working again.
Very strange…

That is strange… whats says:

nvidia-xconfig --query-gpu-info

Are you using DisplayPort?

I’m using HDMI;

$ nvidia-xconfig --query-gpu-info
Number of GPUs: 1

GPU #0:
  Name      : GeForce GTX 1060 6GB
  UUID      : GPU-8aacd71d-fd02-aa54-aecb-a9c75c092a9c
  PCI BusID : PCI:1:0:0

  Number of Display Devices: 1

  Display Device 0 (TV-1):
      EDID Name             : AOC U3277WB
      Minimum HorizSync     : 30.000 kHz
      Maximum HorizSync     : 160.000 kHz
      Minimum VertRefresh   : 23 Hz
      Maximum VertRefresh   : 80 Hz
      Maximum PixelClock    : 600.000 MHz
      Maximum Width         : 3840 pixels
      Maximum Height        : 2160 pixels
      Preferred Width       : 3840 pixels
      Preferred Height      : 2160 pixels
      Preferred VertRefresh : 60 Hz
      Physical Width        : 700 mm
      Physical Height       : 390 mm

Here is a little information about it:

Option “ConnectedMonitor” “string”

Allows you to override what the NVIDIA kernel module detects is connected to your video card. This may be useful, for example, if you use a KVM (keyboard, video, mouse) switch and you are switched away when X is started. In such a situation, the NVIDIA kernel module cannot detect what display devices are connected, and the NVIDIA X driver assumes you have a single CRT.

Valid values for this option are "CRT" (cathode ray tube), "DFP" (digital flat panel), or "TV" (television); if using TwinView, this option may be a comma-separated list of display devices; e.g.: "CRT, CRT" or "CRT, DFP".

It is generally recommended to not use this option, but instead use the "UseDisplayDevice" option.

NOTE: anything attached to a 15 pin VGA connector is regarded by the driver as a CRT. "DFP" should only be used to refer to digital flat panels connected via a DVI port.

Default: string is NULL (the NVIDIA driver will detect the connected display devices).

Option “UseDisplayDevice” “string”

When assigning display devices to X screens, the NVIDIA X driver by default assigns display devices in the order they are found (looking first at CRTs, then at DFPs, and finally at TVs). This option can be used to override this assignment. For example, if both a CRT and a DFP are connected, you could specify:

    Option "UseDisplayDevice" "DFP"

to make the X screen use the DFP, even though it would have used a CRT by default.

Note the subtle difference between this option and the "ConnectedMonitor" option: the "ConnectedMonitor" option overrides what display devices are actually detected, while the "UseDisplayDevice" option controls which of the detected display devices will be used on this X screen.

Source

Maybe use the second Option? I am running out of ideas, what the reason of this behavior could be. :man_shrugging:

I tested this but it did no difference it would seem, still working as before.
I just want to make some more comments of the ‘black screen’ that occurs after login in from the greeter;
I can see the cursor and I can move it around, and at some places it turns to a ‘select text’ line since its hoovering over a sticky note.
So the graphic seems to be running.

1 Like

Last idea i have. You have set this option:

[     4.277] (**) NVIDIA(0): Option "MetaModes" "nvidia-auto-select +0+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"

Remove it or at least use only one of it, not both.

Why?

It has an impact of the draw time:

Sorry to say, it did not seem to make a different either.
I commented out the whole line and still it goes black after login in for at least 3-4 min then I shifted TTY.

Very strange, most things you find on the net involves compiz or so with the XFCE also installed.
Can it be any package that stops the login?

That is really strange sometimes i just get no notification for new posts in that thread…

You could disable the login-manager:

systemctl disable lightdm

and login in shell and type startx to start the xfce4 DE.

Maybe lightdm has a bug somehow?

OK, tried to disable lightdm but the same thing.

Tried to find out the log for the actual startup, think its this below.
Nothing of this can cause that problem I would assume.

sep 09 22:33:59 rtkit-daemon[3576]: Supervising 5 threads of 3 processes of 1 users.
sep 09 22:33:59 rtkit-daemon[3576]: Successfully made thread 25238 of process 24745 owned by '1000' RT at priority 5.
sep 09 22:33:59 rtkit-daemon[3576]: Supervising 6 threads of 3 processes of 1 users.
sep 09 22:33:59 dbus-daemon[25248]: [session uid=1000 pid=25246] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=1000 pid=25241 comm="xfce4-session ")
sep 09 22:33:59 dbus-daemon[25248]: [session uid=1000 pid=25246] Successfully activated service 'org.gtk.vfs.Daemon'
sep 09 22:33:59 org.gtk.vfs.Daemon[25259]: fusermount3: failed to access mountpoint /run/user/1000/gvfs: Permission denied
sep 09 22:33:59 dbus-daemon[25248]: [session uid=1000 pid=25246] Activating service name='org.a11y.Bus' requested by ':1.2' (uid=1000 pid=25241 comm="xfce4-session ")
sep 09 22:33:59 dbus-daemon[25248]: [session uid=1000 pid=25246] Successfully activated service 'org.a11y.Bus'
sep 09 22:33:59 dbus-daemon[25248]: [session uid=1000 pid=25246] Activating service name='org.xfce.Xfconf' requested by ':1.0' (uid=1000 pid=25241 comm="xfce4-session ")
sep 09 22:33:59 dbus-daemon[25248]: [session uid=1000 pid=25246] Successfully activated service 'org.xfce.Xfconf'
sep 09 22:33:59 org.a11y.Bus[25267]: dbus-daemon[25267]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=25241 comm="xfce4-session ")
sep 09 22:33:59 org.a11y.Bus[25267]: dbus-daemon[25267]: Successfully activated service 'org.a11y.atspi.Registry'
sep 09 22:33:59 org.a11y.Bus[25275]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
sep 09 22:33:59 dbus-daemon[25248]: [session uid=1000 pid=25246] Activating service name='org.freedesktop.systemd1' requested by ':1.6' (uid=1000 pid=25281 comm="dbus-update-activation-environment --systemd SSH_A")
sep 09 22:33:59 dbus-daemon[25248]: [session uid=1000 pid=25246] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
sep 09 22:34:00 dbus-daemon[25248]: [session uid=1000 pid=25246] Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by ':1.11' (uid=1000 pid=25303 comm="xfdesktop ")
sep 09 22:34:00 org.freedesktop.thumbnails.Thumbnailer1[25326]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
sep 09 22:34:00 org.freedesktop.thumbnails.Thumbnailer1[25326]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
sep 09 22:34:00 org.freedesktop.thumbnails.Thumbnailer1[25326]: Registered thumbnailer gsf-office-thumbnailer -i %i -o %o -s %s
sep 09 22:34:00 org.freedesktop.thumbnails.Thumbnailer1[25326]: Registered thumbnailer heif-thumbnailer -s %s %i %o
sep 09 22:34:00 org.freedesktop.thumbnails.Thumbnailer1[25326]: Registered thumbnailer ffmpegthumbnailer -i %i -o %o -s %s -f
sep 09 22:34:00 dbus-daemon[25248]: [session uid=1000 pid=25246] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.16' (uid=1000 pid=25326 comm="/usr/lib/tumbler-1/tumblerd ")
sep 09 22:34:00 dbus-daemon[25248]: [session uid=1000 pid=25246] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
sep 09 22:34:00 dbus-daemon[25248]: [session uid=1000 pid=25246] Activating service name='org.gtk.vfs.AfcVolumeMonitor' requested by ':1.16' (uid=1000 pid=25326 comm="/usr/lib/tumbler-1/tumblerd ")
sep 09 22:34:00 polkitd[704]: Registered Authentication Agent for unix-session:4 (system bus name :1.609 [/usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale sv_SE.UTF-8)
sep 09 22:34:00 dbus-daemon[25248]: [session uid=1000 pid=25246] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
sep 09 22:34:00 dbus-daemon[25248]: [session uid=1000 pid=25246] Activating service name='org.gtk.vfs.MTPVolumeMonitor' requested by ':1.16' (uid=1000 pid=25326 comm="/usr/lib/tumbler-1/tumblerd ")
sep 09 22:34:00 dbus-daemon[25248]: [session uid=1000 pid=25246] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
sep 09 22:34:00 dbus-daemon[25248]: [session uid=1000 pid=25246] Activating service name='org.gtk.vfs.GPhoto2VolumeMonitor' requested by ':1.16' (uid=1000 pid=25326 comm="/usr/lib/tumbler-1/tumblerd ")
sep 09 22:34:00 dbus-daemon[25248]: [session uid=1000 pid=25246] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
sep 09 22:34:00 dbus-daemon[25248]: [session uid=1000 pid=25246] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
sep 09 22:34:00 dbus-daemon[25248]: [session uid=1000 pid=25246] Activating service name='org.gtk.vfs.Metadata' requested by ':1.11' (uid=1000 pid=25303 comm="xfdesktop ")
sep 09 22:34:00 dbus-daemon[25248]: [session uid=1000 pid=25246] Successfully activated service 'org.gtk.vfs.Metadata'
sep 09 22:34:16 pulseaudio[24745]: E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.

Phew, i don’t see any relevant line there…

Could be problem between NVIDIA driver and XFCE desktop settings.

remove this file:

/home/$USER/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml

It will be recreated after reboot.

Maybe there is a wrong configuration :man_shrugging:

1 Like

That was the solution… now I get in directly after login in :smile:
One bug away, thanks for you several hints @megavolt

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.