[SOLVED] F30 & Dell XPS, external display stopped working around kernel 5.1

LinuxQuestions.org

Download your favorite Linux distribution at LQ ISO.

Mark Forums Read

		LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
[SOLVED] F30 & Dell XPS, external display stopped working around kernel 5.1

Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Welcome to LinuxQuestions.org, a friendly and active Linux Community.

You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

Are you new to LinuxQuestions.org? Visit the following links:
Site Howto | Site FAQ | Sitemap | Register Now

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.

Exclusive for LQ members, get up to 45% off per month. Click here for more info.

Reply

Search this Thread

08-24-2019, 02:13 AM	#1
Hajo_s LQ Newbie Registered: Aug 2019 Posts: 7 Rep:	F30 & Dell XPS, external display stopped working around kernel 5.1 Hi forum, Fedora 30 (gnome-shell, Wayland) running on Dell XPS15 (Intel HD530 & GeForce 960M controllers). External monitor connected through dock , HDMI. Since around kernel 5.1 my external monitor is no longer working: - On boot with ext monitor connected, system freezes after the rhgb splash disappears - the mouse pointer just comes up, then system freezes - With only internal display, system boots. When connecting the external monitor while system is up, system freezes. When disconnecting it, it unfreezes! - Booting only with external monitor (laptop lid closed) provides no display. Opening lid shows image on internal display I noticed that the kernel without rhgb usually mirrors the boot progress on the external monitor. With kernel >5.0 this is no longer the case. So I suspect the issue is in the kernel/display driver/dock driver somewhere, not gnome/wayland/... I booted to runlevel 3 both with kernel 5.0 (can see mirrored display) and kernel 5.2 (can only see image on internal screen) and took some snapshots: - dmesg 5.2 - dmesg 5.0 - lspci 5.2 - lspci 5.0 - lsmod 5.2 - lsmod 5.0 Would highly appreciate if some guru could skim over them and comment if any idea. TIA, Hajo Last edited by Hajo_s; 08-24-2019 at 10:35 AM.

08-26-2019, 02:07 AM	#2
mrmazda LQ Guru Registered: Aug 2016 Location: SE USA Distribution: openSUSE & OS/2 24/7; Debian, Knoppix, Mageia, Fedora, others Posts: 6,562 Blog Entries: 1 Rep:	Normally when screen output is wrong, black, corrupt, etc, what needs to be uploaded for diagnostic purposes is Xorg.0.log either from /var/log/ or ~/.local/share/xorg/, whichever is newer if both exist. Something to try: disable plymouth by appending plymouth.enable=0 to the (probably wrapped) linux line using the E key at the Grub menu. Because yours is an Optimus system, there likely is some Bumblebee, Prime or related problem causing your problem. I don't have Optimus, so can't expect to spot a problem from your existing uploads.

08-26-2019, 02:27 AM	#3
Hajo_s LQ Newbie Registered: Aug 2019 Posts: 7 Original Poster Rep:	Thx MrMazda! Pls note that I’m booting to run level 3, only to console. No XServer is started. Also disabled rhgb. In any case, I’m using Wayland, not X. Can provide a complete syslog for a graphical boot if that would help. Will try disabling plymouth later today. Thx, Hajo UPDATE: Booting with plymouth disabled is same result, external monitor not detected in text mode boot. FWIW I then tried to start an XServer from runlevel 3, that failed with a weird error, see Xorg.0.log for Kernel 5.2 Last edited by Hajo_s; 08-26-2019 at 06:10 AM. Reason: Updated results

08-26-2019, 09:11 AM	#4
mrmazda LQ Guru Registered: Aug 2016 Location: SE USA Distribution: openSUSE & OS/2 24/7; Debian, Knoppix, Mageia, Fedora, others Posts: 6,562 Blog Entries: 1 Rep:	Please use any of the following next time instead of dropbox: Code: http://paste.fedoraproject.org http://susepaste.org/ http://paste.opensuse.org/ http://pastebin.centos.org/ http://paste.debian.net/ http://pastebin.com/ http://paste.ubuntu.com/ https://gist.github.com/ <your own webspace, such as from running apache> Out of space errors aren't so wierd. Maybe the root filesystem is out of space. How many kernels are installed? Are you using snapshotting and/or BTRFS? What do the following report: Code: df -h / journalctl --disk-usage du -sh /var/cache/dnf du -sh / Journal and dnf are candidates for quickly freeing up wasted space.

Old

08-26-2019, 09:48 AM

#5

Hajo_s

LQ Newbie

Registered: Aug 2019

Posts: 7

Original Poster

Rep:

Reputation: Disabled

Apologies for the Dropbox links. Duh, I assumed the out of space error related to embedded device volatile memory, not file system.

To your questions,
- 4 kernels:

Code:

$ ls /boot/vmlin*
vmlinuz-0-rescue-9ac5fbfc9d6943ffb4385734976a3ebf
vmlinuz-5.0.9-301.fc30.x86_64
vmlinuz-5.1.21-200.fc29.x86_64
vmlinuz-5.2.9-200.fc30.x86_64

(fc29 5.1 kernel is a left-over from upgrade. Not using it but even on F29 it already caused the problem AFAIR)

- no snapshotting, no BTRFS (using ext4)

Code:

$ df -h /
Filesystem                               Size  Used Avail Use% Mounted on
/dev/mapper/fedora_localhost--live-root   49G   20G   28G  42% /

Code:

$ journalctl --disk-usage
Archived and active journals take up 1.4G in the file system.

Code:

$ du -sh /var/cache/dnf
330M	/var/cache/dnf/

Code:

$ du -sh /
85G	/

Uh? On a 49G partition? It includes mounted /home:

Code:

$ df -h
Filesystem                               Size  Used Avail Use% Mounted on
devtmpfs                                 7.8G     0  7.8G   0% /dev
tmpfs                                    7.8G     0  7.8G   0% /dev/shm
tmpfs                                    7.8G  1.8M  7.8G   1% /run
tmpfs                                    7.8G     0  7.8G   0% /sys/fs/cgroup
/dev/mapper/fedora_localhost--live-root   49G   20G   28G  42% /
tmpfs                                    7.8G  4.0K  7.8G   1% /tmp
/dev/nvme0n1p7                           976M  202M  708M  23% /boot
/dev/nvme0n1p1                           496M   83M  414M  17% /boot/efi
/dev/mapper/fedora_localhost--live-home  220G   65G  145G  31% /home
tmpfs                                    1.6G  4.0K  1.6G   1% /run/user/1000

08-26-2019, 11:01 AM	#6
mrmazda LQ Guru Registered: Aug 2016 Location: SE USA Distribution: openSUSE & OS/2 24/7; Debian, Knoppix, Mageia, Fedora, others Posts: 6,562 Blog Entries: 1 Rep:	If this issue is LVM-related, I won't be of any use. Why there might be messages about out of space I can't fathom. Please show output from: Code: inxi -GxxSMaz xrandr --listproviders xrandr \| egrep -B1 -A4 'onnect\|creen\|\*' \| grep -v disconn There should be an Xorg.0.log from a Wayland session in /var/log/ or ~/.local/share/xorg/ to upload for us to see. To try to isolate whether this issue is Wayland/Gnome or drivers/kernel, try opening an IceWM session in Xorg and upload Xorg.0.log from it. IceWM is quite lean, quick to install if not already installed, and test with Xterm, using redirection if necessary to capture command output.

Old

08-27-2019, 07:33 AM

#7

Hajo_s

LQ Newbie

Registered: Aug 2019

Posts: 7

Original Poster

Rep:

Reputation: Disabled

Thx again for your time on this!

I'm quite sure it's not fs related. It broke with a kernel update and it works when the external display is not connected...

Code:

$ inxi -GxxSMaz
System:    Host: earth Kernel: 5.2.9-200.fc30.x86_64 x86_64 bits: 64 compiler: gcc v: 9.1.1 
           parameters: BOOT_IMAGE=(hd0,gpt7)/vmlinuz-5.2.9-200.fc30.x86_64 root=/dev/mapper/fedora_localhost--live-root ro 
           resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root 
           rd.lvm.lv=fedora_localhost-live/swap 3 
           Console: tty 1 dm: N/A Distro: Fedora release 30 (Thirty) 
Machine:   Type: Laptop System: Dell product: XPS 15 9550 v: N/A serial: <filter> Chassis: type: 9 serial: <filter> 
           Mobo: Dell model: 0N7TVV v: A01 serial: <filter> UEFI: Dell v: 1.11.2 date: 07/30/2019 
Graphics:  Device-1: Intel HD Graphics 530 vendor: Dell XPS 15 9550 driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:191b 
           Device-2: NVIDIA GM107M [GeForce GTX 960M] vendor: Dell XPS 15 9550 driver: nouveau v: kernel bus ID: 01:00.0 
           chip ID: 10de:139b 
           Display: tty server: X.org 1.20.5 driver: nouveau tty: 480x135 
           Message: Advanced graphics data unavailable in console. Try -G --display

xrandr/ IceWM can't be used. As said, any Xorg/Wayland session crashes on startup, freezing the system.

Wayland doesn't create a Xorg.0.log on my system, instead it logs here:

Code:

$ journalctl | grep "gnome-session\|Shell.desktop" 
Aug 27 19:31:24 earth org.gnome.Shell.desktop[1332]: glamor: No eglstream capable devices found
Aug 27 19:31:25 earth org.gnome.Shell.desktop[1332]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Aug 27 19:31:25 earth org.gnome.Shell.desktop[1332]: > Internal error:   Could not resolve keysym XF86MonBrightnessCycle
Aug 27 19:31:25 earth org.gnome.Shell.desktop[1332]: > Internal error:   Could not resolve keysym XF86RotationLockToggle
Aug 27 19:31:25 earth org.gnome.Shell.desktop[1332]: Errors from xkbcomp are not fatal to the X server
Aug 27 19:31:26 earth org.gnome.Shell.desktop[1332]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Aug 27 19:31:26 earth org.gnome.Shell.desktop[1332]: > Warning:          Unsupported maximum keycode 569, clipping.
Aug 27 19:31:26 earth org.gnome.Shell.desktop[1332]: >                   X11 cannot support keycodes above 255.
Aug 27 19:31:26 earth org.gnome.Shell.desktop[1332]: > Internal error:   Could not resolve keysym XF86MonBrightnessCycle
Aug 27 19:31:26 earth org.gnome.Shell.desktop[1332]: > Internal error:   Could not resolve keysym XF86RotationLockToggle
Aug 27 19:31:26 earth org.gnome.Shell.desktop[1332]: Errors from xkbcomp are not fatal to the X server
Aug 27 19:31:26 earth gnome-session-binary[1302]: Entering running state

But since the system freezes I'm not sure if all the events get logged in time; probably not. GDM doesn't tell me more either :-(

Code:

$ journalctl | grep gdm
Aug 27 19:31:22 earth audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=gdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 27 19:31:23 earth gdm-launch-environment][1221]: accountsservice: Could not get current seat: No data available
Aug 27 19:31:23 earth audit[1221]: USER_AUTH pid=1221 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_permit acct="gdm" exe="/usr/libexec/gdm-session-worker" hostname=earth addr=? terminal=/dev/tty1 res=success'
Aug 27 19:31:23 earth audit[1221]: USER_ACCT pid=1221 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_permit acct="gdm" exe="/usr/libexec/gdm-session-worker" hostname=earth addr=? terminal=/dev/tty1 res=success'
Aug 27 19:31:23 earth audit[1221]: CRED_ACQ pid=1221 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_permit acct="gdm" exe="/usr/libexec/gdm-session-worker" hostname=earth addr=? terminal=/dev/tty1 res=success'
Aug 27 19:31:23 earth systemd-logind[991]: New session c1 of user gdm.
Aug 27 19:31:23 earth audit[1239]: USER_ACCT pid=1239 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='op=PAM:accounting grantors=pam_unix acct="gdm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 27 19:31:23 earth systemd[1239]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0)
Aug 27 19:31:23 earth audit[1239]: USER_START pid=1239 uid=0 auid=42 ses=1 subj=system_u:system_r:init_t:s0 msg='op=PAM:session_open grantors=pam_selinux,pam_selinux,pam_loginuid,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="gdm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 27 19:31:23 earth systemd[1]: Started Session c1 of user gdm.
Aug 27 19:31:23 earth gdm-launch-environment][1221]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
Aug 27 19:31:23 earth audit[1221]: USER_START pid=1221 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_keyinit,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_umask acct="gdm" exe="/usr/libexec/gdm-session-worker" hostname=earth addr=? terminal=/dev/tty1 res=success'

Since I can't see mirrored display in text boot since kernel upgrade, I really suspect something in the kernel (drivers) is broken, I'm at a loss however how to debug the kernel drivers. I'm thinking to fix the mirrored display first and once that works see if the graphical environment can be resurrected as well. But what do I know, I haven't compiled a kernel for at least 15 years...

Really appreciate you taking your time so far on this!
Hajo

Old

08-27-2019, 08:30 AM

#8

mrmazda

LQ Guru

Registered: Aug 2016

Location: SE USA

Distribution: openSUSE & OS/2 24/7; Debian, Knoppix, Mageia, Fedora, others

Posts: 6,562

Blog Entries: 1

Rep:

Reputation: 2267

Reputation: 2267

Reputation: 2267

Reputation: 2267

Reputation: 2267

Reputation: 2267

Reputation: 2267

Reputation: 2267

Reputation: 2267

Reputation: 2267

Reputation: 2267

Quote:

Originally Posted by Hajo_s

View Post

Code:

$ inxi -GxxSMaz
...
           Message: Advanced graphics data unavailable in console. Try -G --display

I neglected to include an instruction that this be run from a GUI terminal, as the message implies.

Quote:

xrandr/ IceWM can't be used. As said, any Xorg/Wayland session crashes on startup, freezing the system.

I must have missed the part of your report saying

Code:

# startx /usr/bin/icewm -- :1

from a tty produces the same trouble as with Wayland/Gnome via GDM.

Quote:

Wayland doesn't create a Xorg.0.log on my system, instead it logs here:

Code:

$ journalctl | grep "gnome-session\|Shell.desktop" 
Aug 27 19:31:24 earth org.gnome.Shell.desktop[1332]: glamor: No eglstream capable devices found...

I'm pretty sure some better output can be had from the journal. I just haven't been able to remember where I've seen it, or find it in the journal's man page.

Quote:

But since the system freezes I'm not sure if all the events get logged in time; probably not.

Maybe, or maybe they're just not being requested with proper switche(s).

Quote:

Code:

$ journalctl | grep gdm...

...

So, GDM itself seems not to be the problem. Maybe it is though. How about switching to LightDM or SDDM from GDM, and trying to run any non-Gnome session, e.g. IceWM.

Quote:

Since I can't see mirrored display in text boot since kernel upgrade, I really suspect something in the kernel (drivers) is broken, I'm at a loss however how to debug the kernel drivers. I'm thinking to fix the mirrored display first and once that works see if the graphical environment can be resurrected as well.

Maybe a better next step would derive from going through https://01.org/linuxgraphics/documen...ow-report-bugs, including attracting attention to your problem from the Intel developers on their mailing list: https://lists.freedesktop.org/mailma...info/intel-gfx. Someone there should be able to tell whether the fault is in the kernel or not, as well as how to get a functional equivalent to Xorg.0.log from Wayland from the journal.

Can you try bypassing the dock?

Old

08-27-2019, 09:47 AM

#9

Hajo_s

LQ Newbie

Registered: Aug 2019

Posts: 7

Original Poster

Rep:

Reputation: Disabled

Quote:

Originally Posted by mrmazda

View Post

I must have missed the part of your report saying

Code:

# startx /usr/bin/icewm -- :1

from a tty produces the same trouble as with Wayland/Gnome via GDM.

Happens to the best of us

XOrg.1.log -- Xorg & Icewm starts, but only on built-in display. External screen remains off, however the mouse moves "over" to the dead screen.

And since that somehow works, here's more info from a xterm inside icewm:

Code:

$ inxi -GxxSMaz
System:
  Host: earth Kernel: 5.2.9-200.fc30.x86_64 x86_64 bits: 64 compiler: gcc 
  v: 9.1.1 
  parameters: BOOT_IMAGE=(hd0,gpt7)/vmlinuz-5.2.9-200.fc30.x86_64 
  root=/dev/mapper/fedora_localhost--live-root ro 
  resume=/dev/mapper/fedora_localhost--live-swap 
  rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap 
  3 
  Desktop: IceWM 1.3.8 dm: startx Distro: Fedora release 30 (Thirty) 
Machine:
  Type: Laptop System: Dell product: XPS 15 9550 v: N/A serial: <filter> 
  Chassis: type: 9 serial: <filter> 
  Mobo: Dell model: 0N7TVV v: A01 serial: <filter> UEFI: Dell v: 1.11.2 
  date: 07/30/2019 
Graphics:
  Device-1: Intel HD Graphics 530 vendor: Dell XPS 15 9550 driver: i915 
  v: kernel bus ID: 00:02.0 chip ID: 8086:191b 
  Device-2: NVIDIA GM107M [GeForce GTX 960M] vendor: Dell XPS 15 9550 
  driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:139b 
  Display: server: Fedora Project X.org 1.20.5 driver: nouveau 
  resolution: 3840x2160~60Hz, 2560x1440~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2) 
  v: 4.5 Mesa 19.1.5 compat-v: 3.0 direct render: Yes

Quote:

So, GDM itself seems not to be the problem. Maybe it is though. How about switching to LightDM or SDDM from GDM, and trying to run any non-Gnome session, e.g. IceWM.

Need to digest this first, bear with me for a while...

Quote:

Maybe a better next step would derive from going through https://01.org/linuxgraphics/documen...ow-report-bugs, including attracting attention to your problem from the Intel developers on their mailing list:

The linked HowTo is a good one, there's instructions on debug-output of dmesg. I'll also dig into this. Meanwhile, overlap, I have reported a bug @ freedesktop and got some initial attention.

Quote:

Can you try bypassing the dock?

Unfortunately not. Only a TB port in the laptop, no adapter to HDMI here. But I may be able to borrow one from a colleague one of these days.

08-28-2019, 01:41 AM	#10
mrmazda LQ Guru Registered: Aug 2016 Location: SE USA Distribution: openSUSE & OS/2 24/7; Debian, Knoppix, Mageia, Fedora, others Posts: 6,562 Blog Entries: 1 Rep:	If you place the external above or below the internal using xrandr, do the out of space and/or other errors disappear?

09-03-2019, 09:24 AM	#11
Hajo_s LQ Newbie Registered: Aug 2019 Posts: 7 Original Poster Rep:	Quick update -- sorry for the pause for s few days: I have meanwhile attracted Intel's attention on the topic and further figured out that not only the external display but even devices such as HIDs connected through the dock are unusable when booting the newer kernels. It goes so far as when a newer kernel was booted and allowed to access the dock, the dock will be unusable even for old kernels unless it is powered down for some 30 minutes. All that somehow makes me think that the issue is somewhere in the dock drivers (i915?) in the kernel rather than Wayland/X. I'll follow that path for a while and will definitely report back as things develop. Hopefully in the next few days... BTW: The "out of space" are from dmesg before even an X/Wayland server is started; it comes from nouveau kernel driver.

09-11-2019, 07:00 AM	#12
Hajo_s LQ Newbie Registered: Aug 2019 Posts: 7 Original Poster Rep:	Update: Thx again mrmazda for your efforts on this. It was indeed an issue in the kernel as seen here. I'm not comprehending the root-cause but happy that it's gone :-)

Reply

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Posting Rules
You may not post new threads You may not post replies You may not post attachments You may not edit your posts BB code is On Smilies are On [IMG] code is Off HTML code is Off Forum Rules

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Earbuds suddently stopped working on Dell xps 13 Linux Mint Sonya	BlobfishSushi	Linux - Newbie	4	11-01-2017 10:04 PM
Dell XPS 13 9350 -> Dell Docking Station D3100 fails to support external monitors	lPrentice	Linux - Hardware	2	06-05-2017 06:40 AM
[SOLVED] external mic not working on Dell XPS M1530, Ubuntu 8.04	drkayak	Linux - Hardware	1	11-10-2009 06:00 PM
Trouble installing Canon Multipass f30 printer	warrenw	Linux - Hardware	1	02-23-2007 04:58 PM
Can't copy files from Fuji Feinpix F30	Ossah	Linux - Hardware	2	02-04-2007 07:34 AM

All times are GMT -5. The time now is 05:50 AM.

Main Menu

Advertisement

My LQ

Write for LQ

LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.

Main Menu

Syndicate

Latest Threads

LQ News

Twitter: @linuxquestions

Open Source Consulting | Domain Registration