v7.95.3 BETA | Display mode change = black screen

alex-pex · February 21, 2017 at 9:58 PM

Hello,

I've tried the latest beta (v7.95.3) and I have a black screen when I try to change the display mode (System settings > Video output > Display mode).

My computer is a Shuttle XS35-704 and only has VGA output. When display mode is "default", I only get basic 4:3 resolutions, I need to change the display mode to "vga" to allow full range screen resolutions.

I tried different OpenELEC / LibreELEC versions
- OpenELEC (various versions): all fine
- LibreELEC v7.0.3: working fine
- LibreELEC v7.95.3: black screen when I switch from "default" to "vga"

On my first LibreELEC install, I tried LibreELEC v7.0.3, changed settings, then manual upgrade to v7.95.3. I had video output, but out of screen. I couldn't change the screen resolution because the settings button was out of screen :s
On the second, I directly installed the v7.95.3, changed display mode, and I get the problem i'm facing now.

My hardware specs:
- CPU: Intel Atom D510 1,66 GHz
- Chipset: Intel NM10 Express
- GPU: Intel GMA 3150
Shuttle Europe: Specification

I can provide additional details if you want, as I should have ssh access to the computer.

vitorp07 · February 22, 2017 at 2:04 AM

With the TV powered on and connected with the VGA cable, can you access your machine via SSH and copy/paste the output of the following command

Code

xrandr

And what is the supported resolution of the TV you have your machine connected to?

alex-pex · February 24, 2017 at 10:52 PM

Code

Octopus:~ # xrandr
Screen 0: minimum 8 x 8, current 1680 x 1050, maximum 32767 x 32767
LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x768      60.00*+
   800x600       60.32    56.25
   640x480       59.94
   512x384       60.00
VGA1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 430mm x 270mm
   1680x1050     59.88*+
   1600x1200     60.00
   1600x1000     60.01
   1280x1024     75.02    60.02
   1440x900      59.89
   1280x960      60.00
   1152x864      75.00
   1152x720      59.97
   1024x768      75.03    60.00
   832x624       74.55
   800x600       75.00    60.32
   640x480       75.00    66.67    59.94
   720x400       70.08
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Display More

I'm currently connecting the device to my computer screen, so the optimal screen resolution is 1680x1050 VGA1 (I'm currently at 1024x768 LVDS1)

vitorp07 · February 25, 2017 at 1:05 AM

Are you going to keep it connected to that screen(1680x1050 VGA1) if so SSH try this below;

Code

echo "#!/bin/sh" > /storage/.config/autostart.sh

Code

echo "xrandr --output VGA1 --mode 1680x1050 --rate 60.00" >> /storage/.config/autostart.sh

Or if you also want to disable the other screen do this below;

Code

echo "#!/bin/sh" > /storage/.config/autostart.sh

Code

echo "xrandr --output LVDS1 --off && xrandr --output VGA1 --mode 1680x1050 --rate 60.00" >> /storage/.config/autostart.sh

You might need to change where it says "rate 60.00" to "rate 59.88" or "rate 59.00"

But every time you need to make changes/test, first delete the "autostart.sh" file created by doing this command below before making the change;

Code

rm /storage/.config/autostart.sh

alex-pex · February 25, 2017 at 6:06 PM

I connected the device to my TV before modifying the default resolution. I ended up putting this autostart script :

Bash

#!/bin/sh


xrandr --output LVDS1 --off
xrandr --output VGA1 --mode 1280x720 --rate 60.00

It's not the optimal TV resolution, but it's the best I found without offscreen image position.

Here the xrandr of my TV

Code

Octopus:~ # xrandr
Screen 0: minimum 8 x 8, current 1360 x 768, maximum 32767 x 32767
LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x768      60.00*+
   800x600       60.32    56.25
   640x480       59.94
   512x384       60.00
VGA1 connected 1360x768+0+0 (normal left inverted right x axis y axis) 820mm x 460mm
   1360x768      60.02*+  59.80
   1600x1200     60.00
   1400x1050     74.87    59.98
   1600x900      60.00
   1280x1024     85.02    75.02    60.02
   1440x900      84.84    74.98    59.89
   1280x960      85.00    60.00
   1280x800      84.88    74.93    59.81
   1152x864      75.00
   1280x768      84.84    74.89    59.87
   1280x720      60.00
   1024x768      85.00    75.03    70.07    60.00
   1024x768i     86.96
   1024x576      59.97
   832x624       74.55
   800x600       85.06    72.19    75.00    60.32    56.25
   848x480       60.00
   640x480       85.01    75.00    72.81    66.67    59.94
   720x400       85.04    70.08
   640x400       85.08
   640x350       85.08
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Display More

The problem is fixed, but I don't know why I needed a script to fix the problem.

vitorp07 · February 25, 2017 at 8:12 PM

Quote from alex-pex

The problem is fixed, but I don't know why I needed a script to fix the problem.

I see this problem a lot when "LVDS" is present, that includes laptops also.

alex-pex · February 25, 2017 at 8:23 PM

I think it's completly unrelated, but the video decoding is slooooww. I tried a different OS, using Kodi 16, and it's fine.
(maybe i should post another bug report for this)

vitorp07 · February 25, 2017 at 8:27 PM

Did you try the same file when when you tried in a different OS?

Looking at the specs of the hardware i wouldn't expect so much,
you are probably limited to H.264 720p.

alex-pex · February 25, 2017 at 8:29 PM

Quote from vitorp07

Did you try the same file when when you tried in a different OS?

Looking at the specs of the hardware i wouldn't expect so much.

I tried the same file, and the playing performance was perfect
Using LibreElec it's almost 1 FPS

Here a debuglog : UKYX
(The playing starts at 21:21:58.960)

vitorp07 · February 25, 2017 at 8:35 PM

Try setting "Number of buffers used by graphics driver" at 2,
also "Enable HQ scalers for scaling above" try 30 or 40%,
try enabling or disabling Hardware acceleration to see if it makes a difference.

Might also be a connection/network problem