Posts by chewitt

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:

2022-12-29 11:29:35.322 T:759      info <general>: CActiveAESink::OpenSink - initialize sink
2022-12-29 11:29:35.322 T:759     debug <general>: CActiveAESink::OpenSink - trying to open device ALSA:hdmi:CARD=PCH,DEV=1
2022-12-29 11:29:35.322 T:759      info <general>: CAESinkALSA::Initialize - Attempting to open device "hdmi:CARD=PCH,DEV=1"
2022-12-29 11:29:35.331 T:759      info <general>: CAESinkALSA::Initialize - Opened device "hdmi:CARD=PCH,DEV=1,AES0=0x04,AES1=0x82,AES2=0x00,AES3=0x00"
2022-12-29 11:29:35.331 T:759      info <general>: CAESinkALSA::InitializeHW - Your hardware does not support AE_FMT_FLOAT, trying other formats
2022-12-29 11:29:35.331 T:759      info <general>: CAESinkALSA::InitializeHW - Using data format AE_FMT_S32NE
2022-12-29 11:29:35.331 T:759     debug <general>: CAESinkALSA::InitializeHW - Request: periodSize 2205, bufferSize 8820
2022-12-29 11:29:35.342 T:759     debug <general>: CAESinkALSA::InitializeHW - Got: periodSize 2205, bufferSize 8820
2022-12-29 11:29:35.342 T:759     debug <general>: CAESinkALSA::InitializeHW - Setting timeout to 200 ms
2022-12-29 11:29:35.342 T:759     debug <general>: CAESinkALSA::GetChannelLayout - Input Channel Count: 2 Output Channel Count: 2
2022-12-29 11:29:35.342 T:759     debug <general>: CAESinkALSA::GetChannelLayout - Requested Layout: FL, FR
2022-12-29 11:29:35.342 T:759     debug <general>: CAESinkALSA::GetChannelLayout - Got Layout: UNKNOWN1, UNKNOWN1 (ALSA: UNKNOWN UNKNOWN)

^ 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.

It shows the drive being detected.. can you do "journalctl | paste" and share the URL as this will show more about systemd (which runs the service units that do sharing).

The config.txt file passes instructions to the boot firmware of a Raspberry Pi board. It doesn't exist on other hardware platforms.

Run "journalctl | paste" and share the URL please.

Quote from Skeeve

My assumption is: The wyse needs some special shutdown no one knows about 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.

If the credential file doesn't work, revert to the original approach but try using urlencoded values with no escaping. Any good?

Enable verbose logging in the GUI and then look at the debug log in /storage/.kodi/temp/kodi.log .. and the reason for the scrape failure is normally quite obvious from reading the log.

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

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.

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.

Options=credentials=/storage/.cache/smbcreds

and in the file:

username=firstname.lastname
password=PasswordWithNoEscapedCharacters!@#
domain=mydomain   <= optional

If that doesn't work, try urlencoding the special characters, see the table here https://www.w3schools.com/tags/ref_urlencode.ASP

It's best to ask for Android images on an Android oriented forum. I doubt you'll have any offers here.

Quote from james

What am I missing?

A description of what you are actually trying to achieve and why.. which might lead to someone sharing ideas on how to achieve it.

Quote from milo

So there will be tomorrow a libreelec with Kodi 19.5?

Staff spending time with their families over the Christmas period has a higher priority than shipping a Kodi release, so probably not.

As long as the AVR/TV advertises support for HDR over the HDMI connection we can "just use it" when HDR media is played. There is nothing to set (other than on/off - on by default) as it's simply a media property and the video pipeline adjusts accordingly.

SuggestionL: Turn it all off. Turn it all back on again.

RK3399 is simply using an current version of u-boot and current version of Linux; unlike most distros that will be using vendor u-boot and vendor kernel sources. All our config/sources are in GitHub https://github.com/LibreELEC/LibreELEC.tv/

Please share the system log from cold boot with the drive connected, i.e. "dmesg | paste" and share the URL