Posts by HiassofT

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

yullaw thanks for testing, this is great you can reproduce it on RPiOS, too!

Can you bisect through the rpi-update kernel/frmware changes and try to find out when it started?

LE10.0.0 is (roughly) using the Aug 5 rpi-update firmware https://github.com/raspberrypi/rp…d9f6998fe484c97

First run "sudo rpi-update

2073a27299fc17cf93152e9c8d9f6998fe484c97", reboot and check if this is fine (it should be, but better double check).

If that is OK check with a firmware from about mid September. If that was OK try one between mid September and today, if it was bad try one beween Aug 5 and mid September etc. Just run rpi-update with the githash of the firmware commits from here: https://github.com/raspberrypi/rpi-firmware/commits/master

so long,

Hias

yullaw thanks a lot for the logs, still not sure why you don't get a picture, everything looks fine to me..

Can you test if you can reproduce it on RPiOS lite (without GUI) and the latest rpi-update kernel and vc4-kms-v3d dtoverlay enabled in config.txt? That combination should be rather close to LE10.0.1 and if it has that issue too it'll be easier to test with older kernels than on LE.

so long,

Hias

yullaw the info from your logs doesn't quite add up, modetest reports 1360x768 mode, according to kodi log it should be 1920x1080. Did you change mode (manually or on playback via whitelist)?

Kodi debug-log would have shown that info, other that everything looks fine to me so not sure why you don't get a picture without manually changing inputs.

Could you give this build a try: https://www.horus.com/~hias/tmp/libr…829-035c5c6.tar - just copy it to the update share and reboot. It contains the latest video driver fixes that haven't made it into 10.0.1.

so long,

Hias

Cris_ my guess would be either the hotplug fixes in the driver or just luck or a combination of both. Kodi doesn't really support display hotplug, the driver now properly detects and handles it though, and if your TV/AVR constantly dis- and re-appears you won't get display from kodi if it started up when the TV was "gone".

BTW: It might be worth checking if a direct connection from RPi4 to the TV works, it could also be that the AVR is doing something odd.

so long,

Hias

Quote from SpeedySteve

MatteN

I had the same problem. Solution for me was to use HDMI Port 0!

I can confirm that. As soon as HDMI1 is used brightness/gamma is off.

so long,

Hias

Cris_ your kernel logs, also the one from LE10.0.0, are spammed with HDMI disconnect/connect events.

I highly recommend checking the cabling, reseating the HDMI cable and/or using a different one could do wonders.

so long,

Hias

Quote from ambetanterix

On a RPi4, using 1080p hdmi out, the brightness is double what it was under 10.0.0, for both the UI and videos. This causes everything to look washed out.

Note: hdmi0 for video, hdmi1 for audio.

Thanks for the report, I could reproduce this here. It only happens when both HDMI ports are connected, with only one HDMI port connected the picture is fine. It's a bug in the RPi linux kernel, I've created an issue here: https://github.com/raspberrypi/linux/issues/4676

so long,

Hias