cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
flatmax
Fanfold Paper
Posts: 7
Registered: ‎11-20-2018
Location: AU
Views: 339
Message 1 of 3

Linux: X1 extreme : HDMI display not working

Hi there,

 

I have updated my bios using the suggestion here :

https://forums.lenovo.com/t5/Linux-Discussion/Linux-X1-extreme-bios-update/m-p/4276567#M12048

 

The HDMI display doesn't work with Linux. When you turn on the laptop - before X11 or Wayland starts - normally the console shows on the HDMI screen.

Right now nothing shows - not the console, nor anything in X11 nor Wayland.

 

What is necessary to get the HDMI display working ?

 

thanks

Matt

flatmax
Fanfold Paper
Posts: 7
Registered: ‎11-20-2018
Location: AU
Views: 272
Message 2 of 3

Re: Linux: X1 extreme : HDMI display not working

Here is some /var/log/syslog output if it helps :

Nov 26 21:33:02 computer gnome-shell[2139]: Failed to blit shared framebuffer: EGL failed to allocate resources for the requested operation.
Nov 26 21:33:02 computer gnome-shell[2139]: Failed to set CRTC mode 1920x1200: No such file or directory
Nov 26 21:33:02 computer gnome-shell[2139]: Failed to blit shared framebuffer: EGL failed to allocate resources for the requested operation.
Nov 26 21:33:02 computer gnome-shell[2139]: Failed to set CRTC mode 1920x1200: No such file or directory
Nov 26 21:33:13 computer org.gnome.Shell.desktop[2139]: Window manager warning: last_user_time (16082366) is greater than comparison timestamp (16082365). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Nov 26 21:33:13 computer org.gnome.Shell.desktop[2139]: Window manager warning: 0x180000a (Desktop) appears to be one of the offending windows with a timestamp of 16082366. Working around...
Nov 26 21:33:15 computer kernel: [16084.666196] rfkill: input handler enabled
Nov 26 21:33:19 computer nautilus-autostart.desktop[2434]: *** BUG ***
Nov 26 21:33:19 computer nautilus-autostart.desktop[2434]: In pixman_region32_init_rect: Invalid rectangle passed
Nov 26 21:33:19 computer nautilus-autostart.desktop[2434]: Set a breakpoint on '_pixman_log_error' to debug
Nov 26 21:33:30 computer kernel: [16099.704021] rfkill: input handler disabled
Nov 26 21:33:31 computer gnome-shell[2139]: Could not get tablet information for 'Wacom Pen and multitouch sensor Pen': (null)
Nov 26 21:33:36 computer gnome-shell[2139]: Object St.Icon (0x562a56e497b0), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: == Stack trace for context 0x562a5336b230 ==
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #0 562a56f178a8 i resource:///org/gnome/shell/ui/osdWindow.js:223 (7ff768cc78b0 @ 231)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #1 7ffdf7944780 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff768fb0b80 @ 71)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #2 7ffdf7944840 b self-hosted:977 (7ff768ff01f0 @ 413)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #3 7ffdf7944930 b resource:///org/gnome/gjs/modules/signals.js:128 (7ff768fc18b0 @ 386)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #4 562a56f17820 i resource:///org/gnome/shell/ui/layout.js:538 (7ff768c04310 @ 127)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #5 7ffdf79458b0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff768fb0b80 @ 71)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #6 7ffdf79464c0 b self-hosted:977 (7ff768ff01f0 @ 413)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: == Stack trace for context 0x562a5336b230 ==
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #0 562a56f178a8 i resource:///org/gnome/shell/ui/osdWindow.js:224 (7ff768cc78b0 @ 273)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #1 7ffdf7944780 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff768fb0b80 @ 71)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #2 7ffdf7944840 b self-hosted:977 (7ff768ff01f0 @ 413)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #3 7ffdf7944930 b resource:///org/gnome/gjs/modules/signals.js:128 (7ff768fc18b0 @ 386)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #4 562a56f17820 i resource:///org/gnome/shell/ui/layout.js:538 (7ff768c04310 @ 127)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #5 7ffdf79458b0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff768fb0b80 @ 71)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #6 7ffdf79464c0 b self-hosted:977 (7ff768ff01f0 @ 413)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: == Stack trace for context 0x562a5336b230 ==
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #0 562a56f178a8 i resource:///org/gnome/shell/ui/osdWindow.js:223 (7ff768cc78b0 @ 231)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #1 7ffdf7944780 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff768fb0b80 @ 71)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #2 7ffdf7944840 b self-hosted:977 (7ff768ff01f0 @ 413)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #3 7ffdf7944930 b resource:///org/gnome/gjs/modules/signals.js:128 (7ff768fc18b0 @ 386)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #4 562a56f17820 i resource:///org/gnome/shell/ui/layout.js:538 (7ff768c04310 @ 127)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #5 7ffdf79458b0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff768fb0b80 @ 71)
Nov 26 21:33:36 computer gnome-shell[2139]: Object St.BoxLayout (0x562a56d1c800), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #6 7ffdf79464c0 b self-hosted:977 (7ff768ff01f0 @ 413)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: == Stack trace for context 0x562a5336b230 ==
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #0 562a56f178a8 i resource:///org/gnome/shell/ui/osdWindow.js:224 (7ff768cc78b0 @ 273)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #1 7ffdf7944780 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff768fb0b80 @ 71)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #2 7ffdf7944840 b self-hosted:977 (7ff768ff01f0 @ 413)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #3 7ffdf7944930 b resource:///org/gnome/gjs/modules/signals.js:128 (7ff768fc18b0 @ 386)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #4 562a56f17820 i resource:///org/gnome/shell/ui/layout.js:538 (7ff768c04310 @ 127)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #5 7ffdf79458b0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff768fb0b80 @ 71)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #6 7ffdf79464c0 b self-hosted:977 (7ff768ff01f0 @ 413)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: == Stack trace for context 0x562a5336b230 ==
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #0 562a56f178a8 i resource:///org/gnome/shell/ui/osdWindow.js:223 (7ff768cc78b0 @ 231)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #1 7ffdf7944780 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff768fb0b80 @ 71)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #2 7ffdf7944840 b self-hosted:977 (7ff768ff01f0 @ 413)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #3 7ffdf7944930 b resource:///org/gnome/gjs/modules/signals.js:128 (7ff768fc18b0 @ 386)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #4 562a56f17820 i resource:///org/gnome/shell/ui/layout.js:538 (7ff768c04310 @ 127)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #5 7ffdf79458b0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff768fb0b80 @ 71)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #6 7ffdf79464c0 b self-hosted:977 (7ff768ff01f0 @ 413)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: == Stack trace for context 0x562a5336b230 ==
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #0 562a56f178a8 i resource:///org/gnome/shell/ui/osdWindow.js:224 (7ff768cc78b0 @ 273)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #1 7ffdf7944780 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff768fb0b80 @ 71)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #2 7ffdf7944840 b self-hosted:977 (7ff768ff01f0 @ 413)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #3 7ffdf7944930 b resource:///org/gnome/gjs/modules/signals.js:128 (7ff768fc18b0 @ 386)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #4 562a56f17820 i resource:///org/gnome/shell/ui/layout.js:538 (7ff768c04310 @ 127)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #5 7ffdf79458b0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7ff768fb0b80 @ 71)
Nov 26 21:33:36 computer org.gnome.Shell.desktop[2139]: #6 7ffdf79464c0 b self-hosted:977 (7ff768ff01f0 @ 413)
... some text cut...

flatmax
Fanfold Paper
Posts: 7
Registered: ‎11-20-2018
Location: AU
Views: 118
Message 3 of 3

Re: Linux: X1 extreme : HDMI display not working

I bought a Lenovo usb-c to displayport adapter and this didn't fix the problem either :

https://forums.lenovo.com/t5/Linux-Discussion/USB-c-to-Displayport-adapter-doesn-t-work/td-p/4293233

Holiday Deals
HAPPENING NOW!

Get the best deals on PCs and tech now during the Holiday Sale
Shop the sale

Top Kudoed Authors