Posts by chewitt

  • LE11 nightly 2022-12-28 - HDMI 2.0b: no 4K Video, no HD Audio

    ^ According to this, there are two streams: #0 which is 4K, and #1 which is 1080p. The next lines are confusing as they appear to show stream 0 being discarded (as it contains Dolby Vision) and then the last line shows it opening stream 0. Regardless, the root issue here is no support for Dolby Vision. This is a known restriction; there is no open-source implementation for Dolby Vision. Kodi can play DV media on Android devices that have DV licensed support built-in to their software, and on a small number of Linux devices that use (Android oriented) ARM vendor kernel/ffmpeg sources have have DV support. Nothing exists for Intel so there is no playable video stream; hence what you see.

  • LE11 nightly 2022-12-28 - HDMI 2.0b: no 4K Video, no HD Audio

    Code
    2022-12-29 11:28:54.444 T:758      info <general>:     Device 3
2022-12-29 11:28:54.445 T:758      info <general>:         m_deviceName      : hdmi:CARD=PCH,DEV=0
2022-12-29 11:28:54.445 T:758      info <general>:         m_displayName     : HDA Intel PCH
2022-12-29 11:28:54.445 T:758      info <general>:         m_displayNameExtra: SAM SAMSUNG on DisplayPort #0
2022-12-29 11:28:54.445 T:758      info <general>:         m_deviceType      : AE_DEVTYPE_HDMI
2022-12-29 11:28:54.445 T:758      info <general>:         m_channels        : FL, FR, LFE, FC, BL, BR, BC, BLOC, BROC
2022-12-29 11:28:54.445 T:758      info <general>:         m_sampleRates     : 32000,44100,48000,88200,96000,176400,192000
2022-12-29 11:28:54.445 T:758      info <general>:         m_dataFormats     : AE_FMT_RAW,AE_FMT_S32NE,AE_FMT_S16NE,AE_FMT_S16LE,AE_FMT_RAW
2022-12-29 11:28:54.445 T:758      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

    ^ This shows the TV (or presumably the AVR passing through the TVs EDID) connected to "hdmi:CARD=PCH,DEV=0" .. while:

    ^ This shows the Kodi output device is "hdmi:CARD=PCH,DEV=1" which is not connected to anything that provides EDID info to define what the output is capable of, so Kodi falls back to 2-channel audio. TL/DR; select the DP output in the GUI (should have 'SAMSUNG' in the name) and you should get multi-channel audio.

    LE images using GBM don't support screenshots due to changes in the video pipeline; this is known and not a bug.

  • LibreElec on Wyse 5010 does not properly shut down

    Quote from Skeeve

    My assumption is: The wyse needs some special shutdown no one knows about :D So there is no machine-specific shutdown procedure in LibreElec's kernel. I also assume that it's safe, but yet annoying, to power it down manually when the "Power Down" message appears.

    I found a couple of other references, but no solution:

    201965 – Power off / Shutdown hangs after echoing "Reboot: Power down" on DELL / WYSE Thin Client - AMD G-T56N

    GitHub - sanrab/Dell-Wyse-Thin-Client-Dx0D-5010: Linux install on Dell Wyse Thin Client Dx0D/5010
    Linux install on Dell Wyse Thin Client Dx0D/5010. Contribute to sanrab/Dell-Wyse-Thin-Client-Dx0D-5010 development by creating an account on GitHub.
    github.com

    I'd start with ensuring the device has the latest/last available BIOS/firmware update installed, and seeing what if-anything can be configured in the BIOS for the device with respect to power states.

    These devices do claim to support SUSE Linux (SLES 12) so any attempt to triage the process might require comparisons with that OS to see what state certain registers or things are being set to (or not) and upstream linux. How to diagnose power-state issues are way beyond my sphere of knowledge though. I did attempt to Google ACPI and references to Wyse but drew blanks. NB: Userspace shutdown scripts are not the problem or solution here. The issue (and any resolution) will be in lower-level code.

  • LE 11 wont boot on PC

    If you see that message on-screen (which is generated by our kernel init script) the system booted. It may have some issue with video drivers or similar that prevents further output on-screen, but the rest of the OS is probably running in the background and if you force SSH on in boot params (add "ssh" to them) you should be able to login and poke around to share logs etc. so we have some into to work with. In the absence of any further info the only real answer is /shrug

  • Libreelec not seen every where on netwoek

    Windows share browsing has been broken since Windows 95 but in 99% of cases the ability to browse the network and mount a share has nothing to do with your ability to manually mount a share. TL/DR; the sooner you master the basic skill of manual mounting, the sooner you stop searching for a solution to something Microsoft has failed to make work for 25+ years.

  • LE 9.80 Nightly on RPi 4B - Kodi Screenshot does not work properly

    Quote from Petes

    According to this https://github.com/xbmc/xbmc/pull/18741 it won't be fixed until Omega 21.0 Alpha 1, if I understand correctly.

    There isn't a nice way to (re)add the feature, so that PR is more of a hack to generate discussion than a serious proposal for code merge. As such it's not been merged and it's been moved K20 to K21, and at some future point it'll probably be punted down the road to Kodi 'M' too.