Dell XPS 9570 with TB16 dock issues

Highly recommend the HDMI port.
I also was using 1280 on a notebook and 1440 on external monitor for a long time until just very recently (and I do mean very) when I switched to Desktop PC (at long last) and have two 1440 monitors.
Never had any trouble.

Can you

sudo nano /etc/default/grub

and relay what is on this line?

GRUB_CMDLINE_LINUX_DEFAULT=

It reads

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_psr=0"

As per your direction.

That part did not help so let's remove that.
Can you open another terminal and in it, run

grep "model name" /proc/cpuinfo | sort -u

and relay that output...

Ok, back to the first terminal, can you change the original default line to:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_idle.max_cstate=1"

Can you run

sudo nano ~/.profile

and look through the output and see if there is anything in there that looks like

export Display=

in it?

If no, run in terminal

sudo update-grub

I added the intel_idle.max_cstate=1 and couldn't find any export Display= (or anything similar) so I ran sudo update-grub and this is the output:

Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/zorin/theme.txt
Found linux image: /boot/vmlinuz-5.4.0-65-generic
Found initrd image: /boot/initrd.img-5.4.0-65-generic
Found linux image: /boot/vmlinuz-5.4.0-45-generic
Found initrd image: /boot/initrd.img-5.4.0-45-generic
Adding boot menu entry for EFI firmware configuration
done

Nothing went wrong there- and lacking an export value on your display is a good thing. I am just wracking my brains on possible causes.

Since you updated grub, when you feel up to it, you can try rebooting and testing for flickering, or if there is loss of control over peripherals.

Rebooted, can still replicate the flickering and loss of devices connected via the dock.

For now, so we do not forget, as I had earlier (thanks for reminding me), lets revert your grub back:

GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash”

sudo update-grub

Killer practice, at least.

What happens if no Dock?

Updated that line, updated Grub.

I’ve disconnected the dock, and connected via the HDMI port on the laptop to another display (1080p, I know this introduces new variables, but my 24" 1440p display only has DisplayPort) and cannot replicate the flickering or loss of peripherals.

Ok, so on a different monitor plugged into HDMI directly, no Dock- No flickering?

Do you remember… You said, “I think it’s the dock…” And I said, “I think it is the graphics…”

Can’t say we did not test thoroughly to be sure. In fairness… Losing the Mouse, Keyboard and screen intermittently- the above really would have worked out better if it’s the graphics.

So, think it is the Dock?

Yeah, I have to imagine it’s an issue with the dock. I need to figure out how to get Windows back on this so I can attempt to use Dell’s method to update the BIOS. Until then I guess I have to live with the flickering and 24hz, if I want to use it. Unfortunate, but at least we’ve narrowed the culprit.

I am curious if there’s a way to rectify my ability to swap between my Intel/Nvidia graphics.

When you switch to tty, it is similar to the prompt used in Recovery mode.
Recovery mode is much like safe mode.
ctrl+alt+F2 will get you into tty, and ctrl+alt+F7 should get you back to the desktop.

From tty,

sudo Xorg -configure

startx

Then check nvidia-settings...

Okay, had a difficult time with tty. Managed to get into it, could not get out of it. Regardless, the output wasn’t good, so I attempted to run the command from the recovery mode.

Tried both commands, the Xorg -configure error’d out with a similar if not exact output as the X -configure from before, the startx command failed as well, and pointed to a log file in /var/log/Xorg.0.log I’ve output the contents below.

[    77.337] 
X.Org X Server 1.19.6
Release Date: 2017-12-20
[    77.339] X Protocol Version 11, Revision 0
[    77.340] Build Operating System: Linux 4.15.0-124-generic x86_64 Ubuntu
[    77.340] Current Operating System: Linux XPS-15 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64
[    77.340] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=83b0bd8a-8c7e-404a-8f15-29c2f1947006 ro recovery nomodeset dis_ucode_ldr
[    77.342] Build Date: 30 November 2020  08:01:56PM
[    77.342] xorg-server 2:1.19.6-1ubuntu4.8 (For technical support please see http://www.ubuntu.com/support) 
[    77.343] Current version of pixman: 0.34.0
[    77.344] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    77.344] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    77.348] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Feb 23 22:13:06 2021
[    77.348] (==) Using config file: "/etc/X11/xorg.conf"
[    77.349] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    77.349] (==) ServerLayout "X.org Configured"
[    77.349] (**) |-->Screen "Screen0" (0)
[    77.349] (**) |   |-->Monitor "Monitor0"
[    77.350] (**) |   |-->Device "Card0"
[    77.350] (**) |-->Screen "Screen1" (1)
[    77.350] (**) |   |-->Monitor "Monitor1"
[    77.350] (**) |   |-->Device "Card1"
[    77.350] (**) |-->Input Device "Mouse0"
[    77.350] (**) |-->Input Device "Keyboard0"
[    77.350] (==) Automatically adding devices
[    77.350] (==) Automatically enabling devices
[    77.350] (==) Automatically adding GPU devices
[    77.350] (==) Automatically binding GPU devices
[    77.350] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    77.350] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[    77.350] 	Entry deleted from font path.
[    77.350] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[    77.350] 	Entry deleted from font path.
[    77.350] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[    77.350] 	Entry deleted from font path.
[    77.350] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[    77.350] 	Entry deleted from font path.
[    77.350] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[    77.350] 	Entry deleted from font path.
[    77.350] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[    77.350] 	Entry deleted from font path.
[    77.350] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[    77.350] 	Entry deleted from font path.
[    77.350] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[    77.350] 	Entry deleted from font path.
[    77.350] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[    77.350] 	Entry deleted from font path.
[    77.350] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[    77.350] 	Entry deleted from font path.
[    77.350] (**) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/Type1,
	built-ins,
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/Type1,
	built-ins
[    77.350] (**) ModulePath set to "/usr/lib/xorg/modules"
[    77.350] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[    77.350] (WW) Disabling Mouse0
[    77.350] (WW) Disabling Keyboard0
[    77.350] (II) Loader magic: 0x55ebce579020
[    77.350] (II) Module ABI versions:
[    77.350] 	X.Org ANSI C Emulation: 0.4
[    77.350] 	X.Org Video Driver: 23.0
[    77.350] 	X.Org XInput driver : 24.1
[    77.350] 	X.Org Server Extension : 10.0
[    77.350] (++) using VT number 1

[    77.511] (EE) systemd-logind: failed to get session: PID 1166 does not belong to any known session
[    77.513] (--) PCI:*(0:0:2:0) 8086:3e9b:1028:087c rev 0, Mem @ 0xeb000000/16777216, 0x80000000/268435456, I/O @ 0x00004000/64, BIOS @ 0x????????/131072
[    77.513] (--) PCI: (0:1:0:0) 10de:1c8c:1028:087c rev 161, Mem @ 0xec000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00003000/128, BIOS @ 0x????????/524288
[    77.513] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[    77.513] (II) LoadModule: "glx"
[    77.514] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    77.515] (II) Module glx: vendor="X.Org Foundation"
[    77.515] 	compiled for 1.19.6, module version = 1.0.0
[    77.515] 	ABI class: X.Org Server Extension, version 10.0
[    77.515] (II) LoadModule: "modesetting"
[    77.515] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    77.515] (II) Module modesetting: vendor="X.Org Foundation"
[    77.515] 	compiled for 1.19.6, module version = 1.19.6
[    77.515] 	Module class: X.Org Video Driver
[    77.515] 	ABI class: X.Org Video Driver, version 23.0
[    77.515] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    77.515] (EE) open /dev/dri/card0: No such file or directory
[    77.515] (EE) open /dev/dri/card0: No such file or directory
[    77.515] (WW) Falling back to old probe method for modesetting
[    77.515] (EE) open /dev/dri/card0: No such file or directory
[    77.515] (EE) open /dev/dri/card0: No such file or directory
[    77.515] (EE) Screen 0 deleted because of no matching config section.
[    77.515] (II) UnloadModule: "modesetting"
[    77.515] (EE) Screen 0 deleted because of no matching config section.
[    77.515] (II) UnloadModule: "modesetting"
[    77.515] (EE) Device(s) detected, but none match those in the config file.
[    77.515] (==) Matched modesetting as autoconfigured driver 0
[    77.515] (==) Matched fbdev as autoconfigured driver 1
[    77.515] (==) Matched vesa as autoconfigured driver 2
[    77.515] (==) Assigned the driver to the xf86ConfigLayout
[    77.515] (II) LoadModule: "modesetting"
[    77.515] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    77.515] (II) Module modesetting: vendor="X.Org Foundation"
[    77.515] 	compiled for 1.19.6, module version = 1.19.6
[    77.515] 	Module class: X.Org Video Driver
[    77.515] 	ABI class: X.Org Video Driver, version 23.0
[    77.515] (II) UnloadModule: "modesetting"
[    77.515] (II) Unloading modesetting
[    77.515] (II) Failed to load module "modesetting" (already loaded, 21995)
[    77.515] (II) LoadModule: "fbdev"
[    77.515] (WW) Warning, couldn't open module fbdev
[    77.515] (II) UnloadModule: "fbdev"
[    77.515] (II) Unloading fbdev
[    77.515] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    77.515] (II) LoadModule: "vesa"
[    77.515] (WW) Warning, couldn't open module vesa
[    77.515] (II) UnloadModule: "vesa"
[    77.515] (II) Unloading vesa
[    77.515] (EE) Failed to load module "vesa" (module does not exist, 0)
[    77.515] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    77.515] (EE) open /dev/dri/card0: No such file or directory
[    77.515] (WW) Falling back to old probe method for modesetting
[    77.515] (EE) open /dev/dri/card0: No such file or directory
[    77.515] (EE) Screen 0 deleted because of no matching config section.
[    77.515] (II) UnloadModule: "modesetting"
[    77.515] (EE) Device(s) detected, but none match those in the config file.
[    77.515] (EE) 
Fatal server error:
[    77.515] (EE) no screens found(EE) 
[    77.516] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    77.516] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    77.516] (EE) 
[    77.520] (EE) Server terminated with error (1). Closing log file.

While I was waiting, I was searching Thunderbolt Dock issues such as here:

Not a lot of luck.

To solve several of the errors in that log file, I normally would recommend reinstalling xorg drivers

sudo apt-get install --reinstall xserver-xorg-video-intel xserver-xorg-core xserver-xorg-input-all

Some users have troubles with the default provided HWE (Hardware Enabled ) drivers, as well.

sudo dpkg-reconfigure xserver-xorg

Of course, make sure not logged into Wayland and ensure that

/etc/gdm3/custom.conf

is set

WaylandEnable=false

In your case, because you get normal behavior outside of the dock- I am Less Sure.
But all of the above make me question the graphics - Again, as did the segmentation fault earlier.
If it was me, I would reinstall the xorg drivers anyway.

Also- you get the 2021 award on patience...

I'm not sure what this means.

Wayland is an alternative to the X server we currently use. It has been in development since the Middle Ages and has yet to produce so much as a Stone Wheel.
In principle, Wayland sounds much better than Xserver, as it eliminates several middlemen, allowing the kernel to communicate directly with the rest of the hardware and system.
In practice, many things do not work on Wayland. Well, umm… most things, really… and that extra speed you get out of it? Milliseconds. The average human cannot notice.

When you log out, you can move to log in but instead of entering password, select the user- then the gear icon. That may have changed recently. It used to be a gear icon. It has been a while since I used Gnome… And I never will use it again. But… When you go to log in, you can select which desktop to log into. You can also, at that point select Wayland (Or not).

The rest was a confg file for GDM3, which is the Login and logout screen - that points to Wayland. By editing the file, you can ensure that it cannot point to Wayland if needs be by setting that to False.

Gotcha. Thank you so much for you patience with me. I have uncommented the line from that file to disable Wayland (it was commented out). I'm going to restart now after having run the xserver commands.

We're not done yet it seems. The Nvidia panel is still empty. It's not the end of the world, and perhaps this weekend I'll have some time to reinstall Windows and potentially update the BIOS Firmware. I now understand the issue is with the dock, and will likely tolerate it's quirks until I can get this resolved.

I will admit, as a human being, I am not as adept as I would like to be at eliminating my own bias.
I am maybe 80/20 in agreement that it is the dock. That the monitor worked on HDMI, no dock, certainly indicates that. But it if a true Thunderbolt dock, it’s odd, as well. Plus the x-errors. There’s a chance it is not the dock, but just looks like it is. There is a chance I am stubborn and unable to wipe all bias from my brain, too.
But keep an open mind on it, just in case. Fully agree that aiming toward the dock is the best bet for now.
And I am sorry I took so much time but was unable to resolve the issue and even may have helped lose the Nvidia Settings, too.
I never have used Nvidia, so am less rehearsed in all its ins and outs.
Perhaps another contributor will help out or the Zorin Team will respond to your message with a fix over my bumbling.

1 Like