Posts by HiassofT

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

See here: RE: Cannot Install/Update Addons

so long,

Hias

see here: RE: raspberry pi zero 2 w

so long,

Hias

Cris_ according to your logs the drm.debug/video kernel command line parameters weren't active. Did you add them to cmdline.txt in a separate line?

Note that everything in cmdline.txt has to be on a single line, please add these after "quiet", separated by a blank, and redo the tests.

While you're at it it would also be interesting to see logs from LE 10.0.0 with drm.debug=0x04

so long,

Hias

Cris_ from your logs it looks like the RPi isn't detecting the AVR - HDMI shows up disconnected in modetest.

Can you try adding drm.debug=0x04 to the end of cmdline.txt?

pastekodi plus modetest outputs from a cold boot (RPi disconnected from power) would be great.

If you don't see the LE splash then ssh in and reboot. Do you see the LE splash now? If yes, please post pastekodi/modetest outputs of that, too.

Also try adding video=HDMI-A-1:1920x1080M@60D (note the "D" at the end) to cmdline.txt. Does this work? Again, pastekodi/modetest outputs would be great.

so long,

Hias

Please ssh in and post the output of "pastekodi" and "modetest | pastebinit" while running LE 10.0.1

so long,

Hias

Latest LE11 nightly RPi2 build from https://test.libreelec.tv/ should start fine on RPi zero 2 (LE10 would also work but we have no RPi2 builds yet).

Note though that 512MB RAM will be quite tight and you may run into out-of-memory issues.

so long,

Hias

Quote from nicoco

Could you please elaborate on both the tinkering process and the drawbacks?

Simulateneous output was great for me with previous version, I'd like to do it again! My pulseaudio skills are limited but I guess that is the way, right?

I've never tried it myself but IIRC there were forum posts from others who did that and reported that audio was significantly delayed. The search function should help you find the posts.

so long,

Hias