Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitor (LVDS) blacks out when adding external monitor #44

Open
WLCIssuesBot opened this issue May 3, 2017 · 17 comments
Open

Monitor (LVDS) blacks out when adding external monitor #44

WLCIssuesBot opened this issue May 3, 2017 · 17 comments
Labels

Comments

@WLCIssuesBot
Copy link
Collaborator

Issue by Manouchehri
Sunday Nov 22, 2015 at 15:38 GMT
Originally opened as Cloudef/wlc#87


Upon plugging in an HDMI monitor to my laptop, the LVDS/internal screen powers off and I cannot see anything on it. Unplugging the HDMI cable does not turn the LVDS screen back on either.

~ > find /sys/class/backlight/intel_backlight/ -type f -print -exec cat {} \;
/sys/class/backlight/intel_backlight/type
raw
/sys/class/backlight/intel_backlight/brightness
976
/sys/class/backlight/intel_backlight/power/control
auto
/sys/class/backlight/intel_backlight/power/async
disabled
/sys/class/backlight/intel_backlight/power/runtime_enabled
disabled
/sys/class/backlight/intel_backlight/power/runtime_active_kids
0
/sys/class/backlight/intel_backlight/power/runtime_active_time
0
/sys/class/backlight/intel_backlight/power/autosuspend_delay_ms
cat: /sys/class/backlight/intel_backlight/power/autosuspend_delay_ms: Input/output error
/sys/class/backlight/intel_backlight/power/runtime_status
unsupported
/sys/class/backlight/intel_backlight/power/runtime_usage
0
/sys/class/backlight/intel_backlight/power/runtime_suspended_time
0
/sys/class/backlight/intel_backlight/bl_power
4
/sys/class/backlight/intel_backlight/max_brightness
976
/sys/class/backlight/intel_backlight/uevent
/sys/class/backlight/intel_backlight/actual_brightness
0
@WLCIssuesBot
Copy link
Collaborator Author

Comment by Earnestly
Sunday Nov 22, 2015 at 16:26 GMT


Does the log contain any useful information perhaps?

@WLCIssuesBot
Copy link
Collaborator Author

Comment by Manouchehri
Sunday Nov 22, 2015 at 16:29 GMT


Sure. Didn't think it was necessary (thought the issue would be easy to spot), but I'll grab a log.

@WLCIssuesBot
Copy link
Collaborator Author

Comment by Manouchehri
Sunday Nov 22, 2015 at 16:36 GMT


Towards the end is when I inserted the HDMI cable. Doesn't seem to mention anything about powering off LVDS (but it definitely is).

Starting sway version g56e80c0 (2015-11-21, branch "makepkg")

Loading config
Checking for config at /home/dave/.sway/config
Checking for config at /home/dave/.config/sway/config
handling config command 'set $mod Mod4'
handling config command 'set $term gnome-terminal'
handling config command 'new_window pixel 1'
Error on line 'new_window pixel 1': Unknown/invalid command
handling config command 'floating_modifier $mod'
handling config command 'bindsym $mod+Return exec $term'
bindsym - Bound Mod4+Return to command exec gnome-terminal
handling config command 'bindsym $mod+Shift+return exec urxvtc'
bindsym - Bound Mod4+Shift+return to command exec urxvtc
handling config command 'bindsym $mod+Shift+w exec chromium'
bindsym - Bound Mod4+Shift+w to command exec chromium
handling config command 'bindsym $mod+Shift+F12 exit'
bindsym - Bound Mod4+Shift+F12 to command exit
handling config command 'bindsym $mod+Shift+p exec subl3 -n'
bindsym - Bound Mod4+Shift+p to command exec subl3 -n
handling config command 'bindsym $mod+Shift+q kill'
bindsym - Bound Mod4+Shift+q to command kill
handling config command 'bindsym $mod+Left focus left'
bindsym - Bound Mod4+Left to command focus left
handling config command 'bindsym $mod+Down focus down'
bindsym - Bound Mod4+Down to command focus down
handling config command 'bindsym $mod+Up focus up'
bindsym - Bound Mod4+Up to command focus up
handling config command 'bindsym $mod+Right focus right'
bindsym - Bound Mod4+Right to command focus right
handling config command 'bindsym $mod+Shift+Left move left'
bindsym - Bound Mod4+Shift+Left to command move left
handling config command 'bindsym $mod+Shift+Down move down'
bindsym - Bound Mod4+Shift+Down to command move down
handling config command 'bindsym $mod+Shift+Up move up'
bindsym - Bound Mod4+Shift+Up to command move up
handling config command 'bindsym $mod+Shift+Right move right'
bindsym - Bound Mod4+Shift+Right to command move right
handling config command 'bindsym $mod+h split h'
bindsym - Bound Mod4+h to command split h
handling config command 'bindsym $mod+v split v'
bindsym - Bound Mod4+v to command split v
handling config command 'bindsym $mod+f fullscreen'
bindsym - Bound Mod4+f to command fullscreen
handling config command 'bindsym $mod+Shift+space floating toggle'
bindsym - Bound Mod4+Shift+space to command floating toggle
handling config command 'bindsym $mod+1 workspace 1'
bindsym - Bound Mod4+1 to command workspace 1
handling config command 'bindsym $mod+2 workspace 2'
bindsym - Bound Mod4+2 to command workspace 2
handling config command 'bindsym $mod+3 workspace 3'
bindsym - Bound Mod4+3 to command workspace 3
handling config command 'bindsym $mod+4 workspace 4'
bindsym - Bound Mod4+4 to command workspace 4
handling config command 'bindsym $mod+5 workspace 5'
bindsym - Bound Mod4+5 to command workspace 5
handling config command 'bindsym $mod+6 workspace 6'
bindsym - Bound Mod4+6 to command workspace 6
handling config command 'bindsym $mod+7 workspace 7'
bindsym - Bound Mod4+7 to command workspace 7
handling config command 'bindsym $mod+8 workspace 8'
bindsym - Bound Mod4+8 to command workspace 8
handling config command 'bindsym $mod+9 workspace 9'
bindsym - Bound Mod4+9 to command workspace 9
handling config command 'bindsym $mod+0 workspace 10'
bindsym - Bound Mod4+0 to command workspace 10
handling config command 'bindsym $mod+Shift+1 move container to workspace 1'
bindsym - Bound Mod4+Shift+1 to command move container to workspace 1
handling config command 'bindsym $mod+Shift+2 move container to workspace 2'
bindsym - Bound Mod4+Shift+2 to command move container to workspace 2
handling config command 'bindsym $mod+Shift+3 move container to workspace 3'
bindsym - Bound Mod4+Shift+3 to command move container to workspace 3
handling config command 'bindsym $mod+Shift+4 move container to workspace 4'
bindsym - Bound Mod4+Shift+4 to command move container to workspace 4
handling config command 'bindsym $mod+Shift+5 move container to workspace 5'
bindsym - Bound Mod4+Shift+5 to command move container to workspace 5
handling config command 'bindsym $mod+Shift+6 move container to workspace 6'
bindsym - Bound Mod4+Shift+6 to command move container to workspace 6
handling config command 'bindsym $mod+Shift+7 move container to workspace 7'
bindsym - Bound Mod4+Shift+7 to command move container to workspace 7
handling config command 'bindsym $mod+Shift+8 move container to workspace 8'
bindsym - Bound Mod4+Shift+8 to command move container to workspace 8
handling config command 'bindsym $mod+Shift+9 move container to workspace 9'
bindsym - Bound Mod4+Shift+9 to command move container to workspace 9
handling config command 'bindsym $mod+Shift+0 move container to workspace 10'
bindsym - Bound Mod4+Shift+0 to command move container to workspace 10
handling config command 'bindsym $mod+Shift+c reload'
bindsym - Bound Mod4+Shift+c to command reload
handling config command 'bindsym $mod+Shift+r restart'
bindsym - Bound Mod4+Shift+r to command restart
handling config command 'exec xrdb -merge ~/.Xresources'
Defferring command `exec xrdb -merge ~/.Xresources'
handling config command 'exec chromium'
Defferring command `exec chromium'
handling config command 'client.focused '
Error on line 'client.focused ': Unknown/invalid command
handling config command 'client.focused_inactive '
Error on line 'client.focused_inactive ': Unknown/invalid command
handling config command 'client.unfocused '
Error on line 'client.unfocused ': Unknown/invalid command
handling config command 'client.urgent '
Error on line 'client.urgent ': Unknown/invalid command
Error(s) loading config!
[wlc] libinput: resume
[wlc] Activating tty
[wlc] MODE: (0) 1366x768 *
[wlc] Connector 1 is not connected or has no modes
[wlc] Connector 2 is not connected or has no modes
[wlc] Connector 3 is not connected or has no modes
[wlc] LVDS-1 Chose mode (0) 1366x768
Output 1 resolution changed to 1366 x 768
[wlc] EGL context is double buffered
[wlc] EGL version: 1.4 (DRI2)
[wlc] EGL vendor: Mesa Project
[wlc] EGL client APIs: OpenGL OpenGL_ES OpenGL_ES2 OpenGL_ES3 
[wlc] EGL context (RGB888)
[wlc] GL version: OpenGL ES 3.0 Mesa 11.0.6
[wlc] GL vendor: Intel Open Source Technology Center
[wlc] GLES2 renderer initialized
[wlc] Set new bsurface to output (1)
New output 1:LVDS-1
Adding 0x379c7b0 (1, 1366.000000x768.000000) to 0x61dce0 (0, 0.000000x0.000000)
Workspace: Generating new name
Got valid workspace command for target: '1'
Workspace: Found free name 1
Added workspace 1 for output 1
Adding 0x37ac390 (2, 1366.000000x768.000000) to 0x379c7b0 (1, 1366.000000x768.000000)
Setting focus to 0x379c7b0:1 (OUTPUT 'LVDS-1')
[wlc] Added output (1)
[wlc] become active
[wlc] Xwayland started (DISPLAY :0)
[wlc] xfixes (5.0)
Compositor is ready, executing cmds in queue
Handling command 'exec xrdb -merge ~/.Xresources'
Executing xrdb -merge ~/.Xresources
Child process created with pid 8428
Handling command 'exec chromium'
Executing chromium
Child process created with pid 8430
Xlib:  extension "XFree86-VidModeExtension" missing on display ":0".
handle:2 type:0 state:0 parent:0 mask:1 (x:0 y:0 w:1359 h:767) title:Twitter / Notifications - Chromium class:chromium appid:(null)
Adding new view 2:Twitter / Notifications - Chromium to container 0x37ac390 2
Adding 0x319a1a0 (4, 0.000000x0.000000) to 0x37ac390 (2, 1366.000000x768.000000)
Setting focus to 0x319a1a0:2 (VIEW 'Twitter / Notifications -)
Arranging layout for 0x379c7b0 (OUTPUT 'LVDS-1')
Arranging layout for 0x379c7b0 LVDS-1 1366.000000x768.000000+0.000000,0.000000
Arranging workspace #0 at 0.000000, 0.000000
Arranging layout for 0x37ac390 (WORKSPACE '1')
Arranging layout for 0x37ac390 1 1366.000000x768.000000+0.000000,0.000000
Arranging 0x37ac390 horizontally
Calculating arrangement for 0x319a1a0:4 (will scale 1366.000000 by 1.000000)
Arranging layout for 0x319a1a0 Twitter / Notifications - Chromium 1366.000000x0.000000+0.000000,0.000000
Set view to 1366 x 768 @ 0, 0
focus:R|(0x61dce0)(p:(nil))(f:0x379c7b0)(h:-1)Type:Root|layout:NONE|w:0|h:0|x:0|y:0|g:0|vis:t|name:(null)|children:1
|focus:X|(0x379c7b0)(p:0x61dce0)(f:0x37ac390)(h:1)Type:Output|layout:NONE|w:1366|h:768|x:0|y:0|g:-1|vis:t|name:LVDS-1|children:1
|-focus:W|(0x37ac390)(p:0x379c7b0)(f:0x319a1a0)(h:-1)Type:Workspace|layout:Horiz|w:1366|h:768|x:0|y:0|g:-1|vis:t|name:1|children:1
|--focus:K|(0x319a1a0)(p:0x37ac390)(f:(nil))(h:2)Type:View|layout:NONE|w:1366|h:768|x:0|y:0|g:-1|vis:t|name:Twitter / Notifi|children:0
geometry request for 2 0x0 : 1366x768
Handling command 'exec gnome-terminal'
Executing gnome-terminal
Child process created with pid 8825
handle:3 type:0 state:0 parent:0 mask:1 (x:0 y:0 w:1004 h:699) title:Terminal class:(null) appid:gnome-terminal-server
Adding new view 3:Terminal to container 0x319a1a0 4
Setting focus to 0x37b20d0:3 (VIEW 'Terminal')
Arranging layout for 0x379c7b0 (OUTPUT 'LVDS-1')
Arranging layout for 0x379c7b0 LVDS-1 1366.000000x768.000000+0.000000,0.000000
Arranging workspace #0 at 0.000000, 0.000000
Arranging layout for 0x37ac390 (WORKSPACE '1')
Arranging layout for 0x37ac390 1 1366.000000x768.000000+0.000000,0.000000
Arranging 0x37ac390 horizontally
Calculating arrangement for 0x319a1a0:4 (will scale 1366.000000 by 0.500000)
Arranging layout for 0x319a1a0 Twitter / Notifications - Chromium 1366.000000x768.000000+0.000000,0.000000
Set view to 683 x 768 @ 0, 0
Calculating arrangement for 0x37b20d0:4 (will scale 1366.000000 by 0.500000)
Arranging layout for 0x37b20d0 Terminal 1366.000000x0.000000+683.000000,0.000000
Set view to 683 x 768 @ 683, 0
focus:R|(0x61dce0)(p:(nil))(f:0x379c7b0)(h:-1)Type:Root|layout:NONE|w:0|h:0|x:0|y:0|g:0|vis:t|name:(null)|children:1
|focus:X|(0x379c7b0)(p:0x61dce0)(f:0x37ac390)(h:1)Type:Output|layout:NONE|w:1366|h:768|x:0|y:0|g:-1|vis:t|name:LVDS-1|children:1
|-focus:W|(0x37ac390)(p:0x379c7b0)(f:0x37b20d0)(h:-1)Type:Workspace|layout:Horiz|w:1366|h:768|x:0|y:0|g:-1|vis:t|name:1|children:2
|--focus:X|(0x319a1a0)(p:0x37ac390)(f:(nil))(h:2)Type:View|layout:NONE|w:683|h:768|x:0|y:0|g:-1|vis:t|name:Twitter / Notifi|children:0
|--focus:K|(0x37b20d0)(p:0x37ac390)(f:(nil))(h:3)Type:View|layout:NONE|w:683|h:768|x:683|y:0|g:-1|vis:t|name:Terminal|children:0
geometry request for 2 0x0 : 683x768
geometry request for 3 683x0 : 683x768
Handling command 'fullscreen'
Arranging layout for 0x37b20d0 (VIEW 'Terminal')
Arranging layout for 0x37b20d0 Terminal 683.000000x768.000000+683.000000,0.000000
Set view to 683 x 768 @ 683, 0
focus:R|(0x61dce0)(p:(nil))(f:0x379c7b0)(h:-1)Type:Root|layout:NONE|w:0|h:0|x:0|y:0|g:0|vis:t|name:(null)|children:1
|focus:X|(0x379c7b0)(p:0x61dce0)(f:0x37ac390)(h:1)Type:Output|layout:NONE|w:1366|h:768|x:0|y:0|g:-1|vis:t|name:LVDS-1|children:1
|-focus:W|(0x37ac390)(p:0x379c7b0)(f:0x37b20d0)(h:-1)Type:Workspace|layout:Horiz|w:1366|h:768|x:0|y:0|g:-1|vis:t|name:1|children:2
|--focus:X|(0x319a1a0)(p:0x37ac390)(f:(nil))(h:2)Type:View|layout:NONE|w:683|h:768|x:0|y:0|g:-1|vis:t|name:Twitter / Notifi|children:0
|--focus:K|(0x37b20d0)(p:0x37ac390)(f:(nil))(h:3)Type:View|layout:NONE|w:683|h:768|x:683|y:0|g:-1|vis:t|name:Terminal|children:0
geometry request for 3 0x0 : 1366x768
Handling command 'fullscreen'
Arranging layout for 0x37ac390 (WORKSPACE '1')
Arranging layout for 0x37ac390 1 1366.000000x768.000000+0.000000,0.000000
Arranging 0x37ac390 horizontally
Calculating arrangement for 0x319a1a0:4 (will scale 1366.000000 by 1.000000)
Arranging layout for 0x319a1a0 Twitter / Notifications - Chromium 683.000000x768.000000+0.000000,0.000000
Set view to 683 x 768 @ 0, 0
Calculating arrangement for 0x37b20d0:4 (will scale 1366.000000 by 1.000000)
Arranging layout for 0x37b20d0 Terminal 683.000000x768.000000+683.000000,0.000000
Set view to 683 x 768 @ 683, 0
focus:R|(0x61dce0)(p:(nil))(f:0x379c7b0)(h:-1)Type:Root|layout:NONE|w:0|h:0|x:0|y:0|g:0|vis:t|name:(null)|children:1
|focus:X|(0x379c7b0)(p:0x61dce0)(f:0x37ac390)(h:1)Type:Output|layout:NONE|w:1366|h:768|x:0|y:0|g:-1|vis:t|name:LVDS-1|children:1
|-focus:W|(0x37ac390)(p:0x379c7b0)(f:0x37b20d0)(h:-1)Type:Workspace|layout:Horiz|w:1366|h:768|x:0|y:0|g:-1|vis:t|name:1|children:2
|--focus:X|(0x319a1a0)(p:0x37ac390)(f:(nil))(h:2)Type:View|layout:NONE|w:683|h:768|x:0|y:0|g:-1|vis:t|name:Twitter / Notifi|children:0
|--focus:K|(0x37b20d0)(p:0x37ac390)(f:(nil))(h:3)Type:View|layout:NONE|w:683|h:768|x:683|y:0|g:-1|vis:t|name:Terminal|children:0
geometry request for 3 683x0 : 683x768
libpng warning: iCCP: known incorrect sRGB profile
[wlc] udev: got device card0
[wlc] udev: hotplug
[wlc] MODE: (0) 1366x768 *
[wlc] Connector 1 is not connected or has no modes
[wlc] MODE: (2) 1920x1080 !
[wlc] MODE: (2) 1920x1080 
[wlc] MODE: (2) 1920x1080 
[wlc] MODE: (2) 1920x1080 
[wlc] MODE: (2) 1920x1080 
[wlc] MODE: (2) 1920x1080 
[wlc] MODE: (2) 1280x1024 
[wlc] MODE: (2) 1280x1024 
[wlc] MODE: (2) 1152x864 
[wlc] MODE: (2) 1280x720 
[wlc] MODE: (2) 1280x720 
[wlc] MODE: (2) 1280x720 
[wlc] MODE: (2) 1024x768 
[wlc] MODE: (2) 1024x768 
[wlc] MODE: (2) 800x600 
[wlc] MODE: (2) 800x600 
[wlc] MODE: (2) 720x576 
[wlc] MODE: (2) 720x576 
[wlc] MODE: (2) 720x480 
[wlc] MODE: (2) 720x480 
[wlc] MODE: (2) 720x480 
[wlc] MODE: (2) 720x480 
[wlc] MODE: (2) 640x480 
[wlc] MODE: (2) 640x480 
[wlc] MODE: (2) 640x480 
[wlc] MODE: (2) 720x400 
[wlc] Connector 3 is not connected or has no modes
[wlc] HDMI-A-1 Chose mode (0) 1920x1080
Output 4 resolution changed to 1920 x 1080
[wlc] EGL context is double buffered
[wlc] EGL version: 1.4 (DRI2)
[wlc] EGL vendor: Mesa Project
[wlc] EGL client APIs: OpenGL OpenGL_ES OpenGL_ES2 OpenGL_ES3 
[wlc] EGL context (RGB888)
[wlc] GL version: OpenGL ES 3.0 Mesa 11.0.6
[wlc] GL vendor: Intel Open Source Technology Center
[wlc] GLES2 renderer initialized
[wlc] Set new bsurface to output (4)
New output 4:HDMI-A-1
Adding 0x38c2ea0 (1, 1920.000000x1080.000000) to 0x61dce0 (0, 0.000000x0.000000)
Workspace: Generating new name
Got valid workspace command for target: '1'
Got valid workspace command for target: '2'
Workspace: Found free name 2
Added workspace 2 for output 4
Adding 0x38db210 (2, 1920.000000x1080.000000) to 0x38c2ea0 (1, 1920.000000x1080.000000)
Setting focus to 0x38c2ea0:4 (OUTPUT 'HDMI-A-1')
Setting focus to 0x379c7b0:1 (OUTPUT 'LVDS-1')
[wlc] Added output (4)
[wlc] Failed to page flip: No space left on device
Setting focus to 0x319a1a0:2 (VIEW 'Twitter / Notifications -)
Setting focus to 0x37b20d0:3 (VIEW 'Terminal')
HDMI-A-1 (1920x1080+1366+0) is right of current output LVDS-1 (y-position 0)
Switching to workspace 0x38db210:2
Setting focus to 0x38db210:-1 (WORKSPACE '2')
Setting focus to 0x38c2ea0:4 (OUTPUT 'HDMI-A-1')
Arranging layout for 0x38db210 (WORKSPACE '2')
Arranging layout for 0x38db210 2 1920.000000x1080.000000+1366.000000,0.000000
focus:R|(0x61dce0)(p:(nil))(f:0x38c2ea0)(h:-1)Type:Root|layout:NONE|w:0|h:0|x:0|y:0|g:0|vis:t|name:(null)|children:2
|focus:X|(0x379c7b0)(p:0x61dce0)(f:0x37ac390)(h:1)Type:Output|layout:NONE|w:1366|h:768|x:0|y:0|g:-1|vis:t|name:LVDS-1|children:1
|-focus:X|(0x37ac390)(p:0x379c7b0)(f:0x37b20d0)(h:-1)Type:Workspace|layout:Horiz|w:1366|h:768|x:0|y:0|g:-1|vis:t|name:1|children:2
|--focus:X|(0x319a1a0)(p:0x37ac390)(f:(nil))(h:2)Type:View|layout:NONE|w:683|h:768|x:0|y:0|g:-1|vis:t|name:Twitter / Notifi|children:0
|--focus:X|(0x37b20d0)(p:0x37ac390)(f:(nil))(h:3)Type:View|layout:NONE|w:683|h:768|x:683|y:0|g:-1|vis:t|name:Terminal|children:0
|focus:X|(0x38c2ea0)(p:0x61dce0)(f:0x38db210)(h:4)Type:Output|layout:NONE|w:1920|h:1080|x:1366|y:0|g:-1|vis:f|name:HDMI-A-1|children:1
|-focus:K|(0x38db210)(p:0x38c2ea0)(f:(nil))(h:-1)Type:Workspace|layout:Horiz|w:1920|h:1080|x:1366|y:0|g:-1|vis:t|name:2|children:0
Handling command 'exec gnome-terminal'
Executing gnome-terminal
Child process created with pid 9047
handle:5 type:0 state:0 parent:0 mask:1 (x:0 y:0 w:1004 h:699) title:Terminal class:(null) appid:gnome-terminal-server
Adding new view 5:Terminal to container 0x38db210 2
Adding 0x38cca10 (4, 0.000000x0.000000) to 0x38db210 (2, 1920.000000x1080.000000)
Setting focus to 0x38cca10:5 (VIEW 'Terminal')
Arranging layout for 0x38c2ea0 (OUTPUT 'HDMI-A-1')
Arranging layout for 0x38c2ea0 HDMI-A-1 1920.000000x1080.000000+1366.000000,0.000000
Arranging workspace #0 at 0.000000, 0.000000
Arranging layout for 0x38db210 (WORKSPACE '2')
Arranging layout for 0x38db210 2 1920.000000x1080.000000+0.000000,0.000000
Arranging 0x38db210 horizontally
Calculating arrangement for 0x38cca10:4 (will scale 1920.000000 by 1.000000)
Arranging layout for 0x38cca10 Terminal 1920.000000x0.000000+0.000000,0.000000
Set view to 1920 x 1080 @ 0, 0
focus:R|(0x61dce0)(p:(nil))(f:0x38c2ea0)(h:-1)Type:Root|layout:NONE|w:0|h:0|x:0|y:0|g:0|vis:t|name:(null)|children:2
|focus:X|(0x379c7b0)(p:0x61dce0)(f:0x37ac390)(h:1)Type:Output|layout:NONE|w:1366|h:768|x:0|y:0|g:-1|vis:t|name:LVDS-1|children:1
|-focus:X|(0x37ac390)(p:0x379c7b0)(f:0x37b20d0)(h:-1)Type:Workspace|layout:Horiz|w:1366|h:768|x:0|y:0|g:-1|vis:t|name:1|children:2
|--focus:X|(0x319a1a0)(p:0x37ac390)(f:(nil))(h:2)Type:View|layout:NONE|w:683|h:768|x:0|y:0|g:-1|vis:t|name:Twitter / Notifi|children:0
|--focus:X|(0x37b20d0)(p:0x37ac390)(f:(nil))(h:3)Type:View|layout:NONE|w:683|h:768|x:683|y:0|g:-1|vis:t|name:Terminal|children:0
|focus:X|(0x38c2ea0)(p:0x61dce0)(f:0x38db210)(h:4)Type:Output|layout:NONE|w:1920|h:1080|x:1366|y:0|g:-1|vis:t|name:HDMI-A-1|children:1
|-focus:W|(0x38db210)(p:0x38c2ea0)(f:0x38cca10)(h:-1)Type:Workspace|layout:Horiz|w:1920|h:1080|x:0|y:0|g:-1|vis:t|name:2|children:1
|--focus:K|(0x38cca10)(p:0x38db210)(f:(nil))(h:5)Type:View|layout:NONE|w:1920|h:1080|x:0|y:0|g:-1|vis:t|name:Terminal|children:0
geometry request for 5 0x0 : 1920x1080

@WLCIssuesBot
Copy link
Collaborator Author

Comment by Manouchehri
Sunday Nov 22, 2015 at 16:43 GMT


It's only the hot-plugging that has an issue. If I boot with HDMI plugged in during startup, there's no issues with LVDS.

~ > find /sys/class/backlight/intel_backlight/ -type f -print -exec cat {} \;
/sys/class/backlight/intel_backlight/type
raw
/sys/class/backlight/intel_backlight/brightness
976
/sys/class/backlight/intel_backlight/power/control
auto
/sys/class/backlight/intel_backlight/power/async
disabled
/sys/class/backlight/intel_backlight/power/runtime_enabled
disabled
/sys/class/backlight/intel_backlight/power/runtime_active_kids
0
/sys/class/backlight/intel_backlight/power/runtime_active_time
0
/sys/class/backlight/intel_backlight/power/autosuspend_delay_ms
cat: /sys/class/backlight/intel_backlight/power/autosuspend_delay_ms: Input/output error
/sys/class/backlight/intel_backlight/power/runtime_status
unsupported
/sys/class/backlight/intel_backlight/power/runtime_usage
0
/sys/class/backlight/intel_backlight/power/runtime_suspended_time
0
/sys/class/backlight/intel_backlight/bl_power
0
/sys/class/backlight/intel_backlight/max_brightness
976
/sys/class/backlight/intel_backlight/uevent
/sys/class/backlight/intel_backlight/actual_brightness
976

@WLCIssuesBot
Copy link
Collaborator Author

Comment by Earnestly
Sunday Nov 22, 2015 at 17:01 GMT


That could very likely be a drm driver (kernel) issue, although I have no idea really.

@WLCIssuesBot
Copy link
Collaborator Author

Comment by Manouchehri
Sunday Nov 22, 2015 at 17:03 GMT


The issue isn't present with X. If it was a kernel issue, wouldn't I see it
in both X and Wayland?

@WLCIssuesBot
Copy link
Collaborator Author

Comment by Earnestly
Sunday Nov 22, 2015 at 17:12 GMT


Nah, wayland stuff stresses different parts of the code in the driver. In the early days of wayland and orbment things would break quite often, in some cases orbments fault (page flipping) and in the others the driver. When the next kernel rolled out some of these problems just went away.

@WLCIssuesBot
Copy link
Collaborator Author

Comment by Cloudef
Sunday Nov 22, 2015 at 20:45 GMT


[wlc] Failed to page flip: No space left on device

Something seems to break during the hot plugging.

@WLCIssuesBot
Copy link
Collaborator Author

Comment by Manouchehri
Sunday Nov 22, 2015 at 20:59 GMT


Which device is it saying is full?

~ > df -h | awk '{print $5}' 
Use%
0%
1%
2%
2%
0%
13%
0%
16%
16%

@WLCIssuesBot
Copy link
Collaborator Author

Comment by Cloudef
Monday Nov 23, 2015 at 08:53 GMT


The error message may be garbage. I don't think the drm function that fails sets errno, so it just says "No space left on device". (Should be fixed). But nevertheless the card page flipping starts failing after you plug the monitor. This might be issue with either drm or wlc causing race condition during hotplug.

@WLCIssuesBot
Copy link
Collaborator Author

Comment by Manouchehri
Monday Nov 23, 2015 at 20:21 GMT


My GPU does crash a fair amount, that could be it. I don't see anything in dmesg when I plug another monitor in; where else should I be looking?

@WLCIssuesBot
Copy link
Collaborator Author

Comment by Fale
Wednesday Nov 23, 2016 at 12:19 GMT


This same problem is also discussed at swaywm/sway#960

@WLCIssuesBot
Copy link
Collaborator Author

Comment by Fale
Friday Nov 25, 2016 at 09:52 GMT


I've a log with also WLC debug enabled, if it can help: http://paste.fedoraproject.org/489432/14800674/

The WLC debug option:

WLC_DEBUG=handle,render,render-loop,focus,xwm,keyboard,commit,request

@WLCIssuesBot
Copy link
Collaborator Author

Comment by maximiliankaul
Tuesday Feb 07, 2017 at 10:16 GMT


I’m not sure if this is relevant but I made the following observation:

  • Plugging in the HDMI monitor AFTER sway is started leads to the described issue. Laptop screen stays blank after connecting HDMI until reboot (will show shutdown message)
  • Plugging in the HDMI monitor BEFORE sway is started => everything works as expected (I can even unplug the HDMI monitor and plug it in again without breaking the laptop monitor)

I’m tested on the following versions:

pacman -Qs wayland 
local/lib32-wayland 1.12.0-1
    A computer display server protocol
local/sway-git r2141.aed3469-1
    i3 compatible window manager for Wayland
local/wayland 1.12.0-1
    A computer display server protocol
local/wayland-protocols 1.7-1
    Specifications of extended Wayland protocols
local/wlc-git 0.0.7.r27.g6f3758b-1
    wayland compositor library
local/xorg-server-xwayland 1.19.1-1 (xorg)
    run X clients under wayland

@2Belette
Copy link

same issue here...

@paulangton
Copy link

I observe the exact behavior described by @maximiliankaul. Any updates on this issue?

@hjfreyer
Copy link

Anyone at least have a workaround for this besides rebooting the system?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants