Display turns off after app restart (Intel NUC, 2.2.0, F25)

support

#1

Hello,

we are experiencing a curious issue with app reboots. We are running an app that uses Xorg and Intel NUC.

  • When the device is cold booted or rebooted, the app starts correctly and display works.
  • When the app is restarted (for example from the resin.io dashboard) the app seems to start ok (Xorg.0.log is identical to the cold boot one) but the display goes directly to power saving mode (so there is no display input at all) and doesn’t recover.

I think that the problem started to appear when we upgraded to Resin 2.2.0 + Fedora 25 based container. You can find the Xorg.0.log attached.

Any ideas?

br,
Timo

after-coldboot.xorg.log (17.5 KB)


#4

So the attached log file is after the cold boot where the display receives signal.

Maybe @floion or @agherzan have some ideas here…


#8

You can also control the display power management signaling from your container.
You may want to take a look here: https://wiki.archlinux.org/index.php/Display_Power_Management_Signaling

Best,
ilias


#9

Yes, the Xorg logs are identical (cold boot and app reboot).

I’ll try to disable DPMS if it makes any difference.


#10

DPMS disabled => Issue persists.


#11

Hi, how do you disable DPMS?
Also, do you recall in what combination of resinOS and base image this used to work?


#12

Hi,

“xset s off -dpms” in container after X start.

ResinOS 2.0.6 and F24, as far as I can remember.


#13

Thanks. Can you try to run on 2.2.0 using the F24 base image?


#14

Yeah, I’m in progress of downgrading some packages and get back to you with results asap.


#15

Alas, same thing with F24.

Curiously enough, I was able to circumvent the issue by placing a 5 second sleep followed by “DISPLAY:0 xrandr --output HDMI1 --auto” into app startup script (which is run with startx).

Without the startup hack xrandr reports the following:

Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 connected (normal left inverted right x axis y axis)
2560x1440 59.95 +
1920x1200 59.95
1920x1080 60.00 50.00 59.94
1920x1080i 60.00 50.00 59.94
1680x1050 59.88
1600x900 60.00
1280x1024 60.02
1440x900 59.90
1280x720 60.00 50.00 59.94
1024x768 60.00
800x600 60.32
720x576 50.00
720x480 60.00 59.94
640x480 60.00 59.94
720x400 70.08
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

With the hack:

Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 32767 x 32767
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 600mm x 340mm
2560x1440 59.95*+
1920x1200 59.95
1920x1080 60.00 50.00 59.94
1920x1080i 60.00 50.00 59.94
1680x1050 59.88
1600x900 60.00
1280x1024 60.02
1440x900 59.90
1280x720 60.00 50.00 59.94
1024x768 60.00
800x600 60.32
720x576 50.00
720x480 60.00 59.94
640x480 60.00 59.94
720x400 70.08
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)


#16

Hm. If you get the same result on F24 then it’s really strange. There’s no recent change I can think of in the hostOS that may cause this.
Do you happen to have multiple graphical apps where you can see this behavior exhibiting? Or so far you have only experienced with this one app?