HDMI no video signal

  • Hello everyone,

    I hope so badly, someone could help me. Currently I try to setup my htpc with libreelec 7.9 (exactly: LibreELEC-Generic.x86_64-7.90.004.img ), but I fail at the first step... I couldn't get my TV to display any hdmi signal.

    When I install libreelec with a VGA display connected, Everything seem to work, but with hdmi only nothing works.

    My system:

    Board: ASRock E350M1
    ASRock > E350M1

    With onboard graphics:
    AMD Radeon HD 6310

    dmesg also returns strange errors:

    I hope someone could help me to set the system up.

    Greetings
    Keredo

  • For starters, there are a couple of things to keep in mind:
    - The Asrock E350M1 is not the newest piece of machinery anymore
    - AMD graphics have a history of 'ups & downs' in video driver support
    - Sometimes HDMI cables can get (micro)fractures rendering video and/or audio not working.

    Try connecting your TV directly to your E350-box with HDMI ( and bypass any AVR receiver), and start LibreELEC.
    See if you can log in via SSH. If so, give us the results of the following command(s):

    Code
    xrandr | pastebinit
    dmesg | pastebinit
    pastebinit ~/.kodi/temp/kodi.log
  • Hello Klojum,

    thank you very much for your response.

    The box is directly connected to the tv. I've also tried the stable version of libreelec... same result

    JESM

    dDhN
    AHFG

    Greetings
    Keredo

    Edited once, last by Keredo (August 23, 2016 at 5:56 PM).

  • HDMI-1 disconnected (normal left inverted right x axis y axis)
    VGA-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 338mm x 270mm

    HDMI is to be connected, not VGA.
    Whether you get a display or not.

    I assume you know it's best to turn on your TV first, and then start up your E350 box?

  • Hi,

    my fault... stupid me
    I switched the display before I generate the logs...

    Here is the log with hdmi connected tv and switched on... but no change (no picture) at all :(

    QEJW

    Edited once, last by Keredo (August 23, 2016 at 6:42 PM).

  • Hi,

    I couldn't believe it, but the problem seems to be the cable.... I feel like a bloody newbie not checking this first :)
    But you gave to solution: the xrandr brought me first this line:

    (old cable)

    The new cable gave me:

    First I thought it was just a mistake, but I can reproduce it again and again... Stupid faulty cable :D

    Thank you very much for your help.

    Greetings