Posts by HiassofT

Thanks a lot for testing, it's great this is working now - this was a tough puzzle to solve

We'll include the necessary config changes in LE so future LE versions will support the official 7inch display.

so long,

Hias

BTW: also make sure you are using HDMI0 (the one next to the power connector on RPi4) - HDMI1 only supports up to 4kp30.

so long,

Hias

Please post the outputs of "modetest | pastebinit" and "pastekodi"- this will show what modes are available (and a copy of the edid).

Most sinks won't list 4kp50/60 modes at 4:4:4 in the EDID unless you enable "HDMI Deep Color" at the sink - then 4k 4:4:4 is limited to 30fps and only 4:2:0 (which the RPi doesn't support) 50/60fps are listed.

YCbCr 4:4:4 isn't supported in the driver either, the proposed kernel patch would add that along 4:2:2 as well.

IIRC all matrices and BT709/2020 colorspace signalling should be fine now.

so long,

Hias

New day, new try - I noticed I missed one option: https://www.horus.com/~hias/tmp/libr…442-9bbb99c.tar

Please report back if it works. If it doesn't please post your config.txt (Note that IIRC you need to have ignore_lcd=1 in it, and the 7inch dtoverlay after the "include distroconfig.txt").

so long,

Hias

Thanks for testing!

The main problem with the DSI drivers is that the kernel ends up in an endless probe loop if something is wrong (eg a driver missing or not initializing) without telling you what failed - several drivers just silently pass on errors without logging anything so there's no chance of finding out which of the sub-sub-sub components are missing or failing to initialize.

I get the same lockup (endless probe/bind loop) here with the 7inch dtoverlay loaded. I don't have the display, so I'd expect things to fail, but not as badly as they do (unable to complete kernel boot) and tons of meaningless errors on the serial console.

At the moment I'm at a complete loss, I think I have all the required dependencies enabled and no idea what else might be missing.

so long,

Hias

Not easily, you'd need to build kernel and kodi with the current WIP patches (same for LE).

config.txt is in /flash/ - see our Wiki https://wiki.libreelec.tv/configuration/config_txt

so long,

Hias

YCbCr 4:2:2 is supported by the hardware but not implemented in the driver and/or kodi yet (a complicated story...). Eventually support should be added though.

To get 4kp50/60 output (at RGB 4:4:4) you need to add hdmi_enable_4kp60=1 to config.txt - the HDMI sink also needs to support that and signal it via EDID.

so long,

Hias

Next try, could you please test with this build: https://www.horus.com/~hias/tmp/libr…536-90f3d53.tar

I found a couple more modules need to be built into the kernel.

so long,

Hias

Please provide a short sample file (1 minute or so) that has this issue. Also please test that if the issue occurs too when playing from a local USB drive to rule out network/nfs issues.

so long,

Hias

Please give this build a try: https://www.horus.com/~hias/tmp/libr…232-e829476.tar (just copy it to the update share and reboot)

I noticed we were missing some kernel config options, they are included in this build.

so long,

Hias

Oh, this is weird, the "Playback Channel Map" should have 2 values (eg "0,0" or "3,4"), but there's only in both cases. Probably luck that it worked before.

Try creating a /storage/.config/asound.conf file with the following content:

pcm.myoutput {
  type hw
  card "Headset"
  chmap [ "FL,FR" ]
  channels 2
  hint.description "my output with fixed chmap"
}

This should give you an "ALSA: Headset ()" (or similar) device with a fixed channel map to make kodi happy.

so long,

Hias

You have to set video=... in /flash/cmdline.txt, not config.txt

so long,

Hias

Interesting. Can you post the output of amixer -c Headset contents both on LE 9.2 and LE10?

so long,

Hias

Getting composite video on RPi4 is currenntly a bit messy as composite has to be expicitly enabled in the kms driver, too (on RPi0-3 it's enabled by default in kms and there's an option to disable it).

This means you either have to modify distroconfig.txt (which isn't great as it will be replaced on every upgrade) or copy the contents of distroconfig.txt to config.txt and disable the distroconfig.txt include (which isn't great either as you may miss important changes to distroconfig.txt on upgrades).

That being said you need to make 3 changes to get composite out on LE 10.0.1:

add "composite=1" to the kms dtoverlay in distroconfig.txt

dtoverlay=vc4-kms-v3d,cma-512,composite=1

enable tvout in config.txt

enable_tvout=1

set your desired mode in cmdline.txt (on the same line after "quiet"). eg for PAL:

video=Composite-1:720x576@50ie

or for NTSC:

video=Composite-1:720x480@60ie

Note the "e" at the end, it's important, if you omit this kodi won't detect the output (as connector status is "unknown" because composite doesn't have hotplug detect, with "e" in the mode it's forced to "on").

so long,

Hias

This headset uses a very weird channel layout, 3 channels where the first one unknown/unused - I've never seen such an odd setup before:

INFO <general>: m_channels : UNKNOWN1, FL, FR

Kodi doesn't cope with that too well, it expects to get a normal 2-channel setup with left and right.

It might be possible to work around that by creating a /storage/.config/asound.conf file (that's the equivalent of ~/.asoundrc on other linux distros) and creating a custom pcm using the route plugin.

read more about it here: https://www.alsa-project.org/wiki/Asoundrc here https://www.alsa-project.org/alsa-doc/alsa-lib/pcm_plugins.html and some LE specific info in this forum thread RE: Volume Control for Chrome Add-On

so long,

Hias

If you have a linux PC (or VM) mount the ext4 partition on the SD card and put the tar (or img) file in the .update folder.

I've just PR'ed a fix for broken USB and network on RPi2/3 https://github.com/LibreELEC/LibreELEC.tv/pull/5863, if it gets merged in time tomorrow's nightly should be fine again.

so long,

Hias

Quote from Sakurai

(Translated by google) After loading KODI, the mouse pointer disappears. The mouse, keyboard and touch pad do not work. No further work possible

Sorry, I broke USB on RPi2 when moving to kernel 5.15. I've already PR'ed a fix https://github.com/LibreELEC/LibreELEC.tv/pull/5863, tomorrow's nightly should be fine again.

so long,

Hias

yullaw thanks for testing, it's great you could narrow it down!

Can you please open an issue here https://github.com/raspberrypi/firmware/issues with the details of your analysis? This seems to be a bug in the RPi firmware.

so long,

Hias