Posts by HiassofT

    There is a post 19.0 PR fixing the default whitelist that may help (there is more fixed than the title suggest): Resolution: Try double refreshrate and pulldown also when no whitelist is set by fritsch · Pull Request #19382 · xbmc/xbmc · GitHub

    Yes, I'm aware of that, and that will help with playback of eg interlaced videos on RPi4 - but it still won't help with stock default kodi installations where GUI is set to 4096x2160p30 or 3840x2160p30 - there are no higher res modes and no higher refresh rates. You need to switch resolution down to 1920x1080 so you can play back 50/60 i/p HD stuff.

    Things will get better when 4kp60 output is supported in the driver (first version of patches already looks promising, but we're not fully there yet).

    so long,

    Hias

    Just an FYI, you don't need a whitelist to use refresh rate switching, you just need the "Adjust display refresh rate" option enabled.

    FYI: that doesn't work too well if display is set to 4k (which is default after plain install without changing settings) and max refresh rate is 30Hz. Kodi doesn't seem to switch resolutions (eg to 1920x1080 which will support 24-60Hz).

    So on RPi with 4k TVs I very much recommend to configure whitelist correctly (and changing display mode from 4096x2160 to 1920x1080 is also a very good idea).

    so long,

    Hias

    You can enable analog audio output by adding `dtparam=audio=on` to config.txt.

    According to your kodi log you don't seem to have a whitelist set up and didn't enable adjust refresh rate. Make sure you do that, don't enable 25-30Hz rates of 1280x720, 1920x1080 and allow using double-rate refresh rates in whitelist instead. You are probably running in a 30Hz 4k mode and kodi doesn't cope with that too well if you try to play a 60Hz video - this is probably causing your audio sync issues.

    so long,

    Hias

    To enable busybox's getty simply change busybox's target configuration to have CONFIG_GETTY=y - see here LibreELEC.tv/busybox-target.conf at master · LibreELEC/LibreELEC.tv · GitHub

    You'll also need a systemd unit (and enable it) so getty is automatically started. In LE we remove getty.target and the serial-getty@ template, have a look at the latter systemd/[email protected] at main · systemd/systemd · GitHub as a starting point. Yu need to adapt the agetty options to busybox's getty options and can simply use a fixed device instead of a unit template and let it install to multi-user.target - the TTY settings in the Service block should be fine though.

    so long,

    Hias

    This could be done via an addon, I don't think we have a getty in some addon though as that is an extremely niche usecase (building your own image and enabling the busybox getty applet and providing systemd unit files to enable it would be another possibility).

    Keep in mind that a password on a serial console provides rather low additional protections. Once you have physical access to the device to hook up a serial console you could as well just take out the SD card and do everything you want (reading/modifying the data, enabling debug shell etc).

    And if you go to the effort of securing physical access to the SD card you could as well secure access to the serial console pins - eg by putting everything in a metal box with a lock.

    so long,

    Hias

    Thanks a lot for reporting back and I'm glad it's working now!

    I expected that the video= option is needed, without it linux doesn't detect that AVR.

    I'm currently working on a script to simplify this whole edid stuff - hopefully that should make it into beta2.

    I'm not 100% sure why hdmi_ignore_cec_init doesn't seem to work - make sure everything's set up correctly in kodi's CEC settings (though CEC should only be ever used on hdmi0 in kodi/linux - so it's puzzling why your AVR turns on).

    so long,

    Hias

    Please give the LibreELEC 10 beta 1 build a try - with LE 9.2 you need to add a bunch of settings to config.txt to override the video mode, the simple cmdline.txt solution only works with LE 10.

    If you connected a 4k monitor then it could also be that the HDMI cable is not specced for 4k - it's easy to find out though, LE 10 with the video mode option in cmdline.txt will start in HD, then you can try switching to 3840x2160 in Kodi (Settings->System->Display). If you get "no signal" on TV wait a couple of seconds, then kodi will automatically switch back to the previous (HD) mode.

    so long,

    Hias

    Thanks a lot for your edid!

    I gave it a try and got a picture with it, but it's skewed horizontally. Not really sure what's going on there, could be that my monitors can't cope with that mode, could be some odd issue in the video driver. I've contacted RPi devs.

    BTW: you could also try using video=HDMI-A-1:1360x768M@60 - that will give you a mode that's closer to the probably native panel resolution and thus avoids down/up scaling from 1920x1080 or 1280x720 and may give a clearer GUI. Not all monitors/TVs accept that mode though.

    so long,

    Hias

    Thanks, this is looking good now.

    Keep the video= setting in cmdline.txt, this is the standard linux method to configure video modes (and work around video/edid issues) - see modedb default video mode support — The Linux Kernel documentation

    Out of curiosity: can you upload your edid? run

    Code
    cat /sys/class/drm/card0-HDMI-A-1/edid > edid.bin

    and then attach the edid.bin file - we'll have a look if it's possible to improve video mode handling in the driver.

    so long,

    Hias

    The logs shows you still have all the old cruft you added in config.txt - again, drop that, this is not going to work and very likely causing your crashes.

    Replace your config.txt with the stock version from /usr/share/bootloader/config.txt and don't touch gpu_mem, distroconfig.txt or kms overlays.

    so long,

    Hias

    It's a bit puzzling that HDMI-A-2 shows connected status but edid is not being read - please run "pastekodi" and post the URL.

    It might be worth forcing connector status to enabled (eg with video=HDMI-A-2:D) and double-checking your cmdline is correct.

    eg this should work (using lg-55c8.dat edid on first HDMI, forcing mode to HD and your pioneer edid on second HDMI forcing to always on without specific mode - you could also use 1920x1080@60D there):

    Code
    drm.edid_firmware=HDMI-A-1:edid/lg-55c8.dat,HDMI-A-2:edid/pioneer-vsx520.bin video=HDMI-A-1:1920x1080@60D video=HDMI-A-2:D

    Testing that here (with nothing connected to second HDMI) worked fine.

    EDID loaded lines in dmesg:

    Code
    [ 3.434129] [drm] Got external EDID base block and 1 extension from "edid/lg-55c8.dat" for connector "HDMI-A-1"
    [ 3.444927] [drm] Got external EDID base block and 1 extension from "edid/pioneer-vsx520.bin" for connector "HDMI-A-2"

    and kodi also detected the audio device with the pioneer AVR

    Code
    2021-03-21 13:22:04.378 T:948 INFO <general>: Device 6
    2021-03-21 13:22:04.379 T:948 INFO <general>: m_deviceName : hdmi:CARD=vc4hdmi1,DEV=0
    2021-03-21 13:22:04.379 T:948 INFO <general>: m_displayName : vc4-hdmi-1
    2021-03-21 13:22:04.379 T:948 INFO <general>: m_displayNameExtra: PIO VSX-520 on HDMI
    2021-03-21 13:22:04.379 T:948 INFO <general>: m_deviceType : AE_DEVTYPE_HDMI
    2021-03-21 13:22:04.379 T:948 INFO <general>: m_channels : FL, FR, LFE, FC, BL, BR, BLOC, BROC
    2021-03-21 13:22:04.379 T:948 INFO <general>: m_sampleRates : 32000,44100,48000,88200,96000,176400,192000
    2021-03-21 13:22:04.379 T:948 INFO <general>: m_dataFormats : AE_FMT_RAW,AE_FMT_S24NE3,AE_FMT_S24NE4,AE_FMT_S32NE,AE_FMT_S16NE,AE_FMT_S16LE,AE_FMT_S16BE,AE_FMT_U8,AE_FMT_RAW
    2021-03-21 13:22:04.379 T:948 INFO <general>: m_streamTypes : STREAM_TYPE_AC3,STREAM_TYPE_DTSHD,STREAM_TYPE_DTSHD_MA,STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_512,STREAM_TYPE_EAC3,STREAM_TYPE_TRUEHD

    so long,

    Hias