Posts by Da Flex

Thanks. Now I'm thinking LE uses an incomplete Bluetooth driver:

Aug 08 19:26:47.853413 kodi bluetoothd[628]: profiles/network/bnep.c:bnep_init() kernel lacks bnep-protocol support
Aug 08 19:26:47.854683 kodi systemd[1]: Starting kodi-waitonnetwork.service...
Aug 08 19:26:47.853437 kodi bluetoothd[628]: src/plugin.c:init_plugin() System does not support network plugin
Aug 08 19:26:47.854742 kodi systemd[1]: lircd.service was skipped because of an unmet condition check (ConditionPathExists=/storage/.config/lircd.conf).
Aug 08 19:26:47.855066 kodi systemd[1]: lircd-uinput.service was skipped because of an unmet condition check (ConditionPathExists=/storage/.config/lircd.conf).
Aug 08 19:26:47.865289 kodi systemd[1]: Starting sshd.service...
Aug 08 19:26:47.866274 kodi bluetoothd[628]: src/plugin.c:init_plugin() System does not support bap plugin
Aug 08 19:26:47.866314 kodi bluetoothd[628]: src/plugin.c:init_plugin() System does not support bass plugin
Aug 08 19:26:47.871909 kodi kernel: macb 1f00100000.ethernet eth0: PHY [1f00100000.ethernet-ffffffff:01] driver [Broadcom BCM54213PE] (irq=POLL)
Aug 08 19:26:47.872501 kodi kernel: macb 1f00100000.ethernet eth0: configuring for phy/rgmii-id link mode
Aug 08 19:26:47.866318 kodi bluetoothd[628]: src/plugin.c:init_plugin() System does not support mcp plugin
Aug 08 19:26:47.866323 kodi bluetoothd[628]: src/plugin.c:init_plugin() System does not support vcp plugin
Aug 08 19:26:47.866329 kodi bluetoothd[628]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Aug 08 19:26:47.866333 kodi bluetoothd[628]: src/plugin.c:init_plugin() System does not support micp plugin
Aug 08 19:26:47.866339 kodi bluetoothd[628]: src/plugin.c:init_plugin() System does not support ccp plugin
Aug 08 19:26:47.866345 kodi bluetoothd[628]: src/plugin.c:init_plugin() System does not support csip plugin
Aug 08 19:26:47.866479 kodi bluetoothd[628]: Bluetooth management interface 1.22 initialized

PS: Maybe it's that bug:

Post

RE: Radxa X4

Posts edited to remove all the advertorial content. The second post was completely unnecessary so deleted.

In terms of thoughts, it looks interesting: decent overall specs although most users will want emmc flash onboard which is promised but not shipping yet. There is one outstanding DRM bug affecting N100 devices that Intel devs are being rather slow at, but overall it should require nothing to be supported with LE.

chewitt

July 21, 2024 at 1:24 PM

That board was released last year, so still pretty new. Post a log from Generic please...

HDMI settings don't work anymore at config.txt. The new approach is something like that:

Thread

Raspi4 hdmi_pixel_encoding=2 does not work with Libreelec 11.0.6

Hello Guys,

since I did an update from Libreelec 9.2.6 to 11.0.6 von my Raspi 4 the colors looking very pale.

With Libreelec 9.2.6 I've fixed it in the config.txt with the command option: hdmi_pixel_encoding=2

It seems to be that the command option does not work anymore.

How can I fix this problem ?

Thanks in advance

Greeting from Lars

larslunte

March 18, 2024 at 6:59 PM

The driver seems to work. I guess you're on a low sampling rate. We need a full log for audio quality...

Quote from wyup

Is this considered hardware acceleration?

No, KMS isn't the actual hardware acceleration layer:

Kernel Mode Setting (KMS) — The Linux Kernel documentation

Quote from hiya

Sorry I didn't see the VP9 in the logs...

Line 8 of your log snippet. YouTube often plays ads before the actual content, so maybe the ad is VP9. VP9 was developed by Google, so it would make sense.

Update to LE 12.

• we only fix bugs on latest LE versions, and yours is outdated
• with sonarr/radarr it's a typical piracy setup, which I will not support

We don't work with log snippets. Provide a complete one.

Quote from leano

what is difference between 'video=HDMI-A-2:D' and 'video=HDMI-A-2:d', upper and lower case Dd?

modedb default video mode support — The Linux Kernel documentation

Maybe creating new EDID helps:

https://wiki.libreelec.tv/configuration/edid

Update to latest LE to get latest Bluetooth drivers. If the problem remains...

Quote from apw63

I’ve come to the conclusion that the tv in our RV has an issue outputting the media.

Or you're using a cheap cable over there. Make sure it's conform to HDMI 2.0 / 2.1 standard.

Quote from leano

when i install the (none legacy) generic will i get HDR?

Yes.

I guess your PC has an LSPCon chip to convert from DP to HDMI. Those chips have known driver issues, and such issues are very likely unsolvable by us (search for "LSPCon" on the forum).

Make sure your BIOS is up-to-date. If your hardware support page offers video driver updates, install the latest. They sometimes include firmware for the LSPCon driver. You probably need Windows to install those updates.

You probably get your videos from illegal sources, and they aren't encoded correctly:

2024-08-02 17:51:35.042 T:881     debug <general>: ActiveAE::SyncStream - average error of 102.118088, start adjusting
2024-08-02 17:51:35.092 T:881     debug <general>: ActiveAE::SyncStream - average error 2.118088 below threshold of 30.000000
...
Feb 27 17:26:21.857301 Lanser kernel: v3d fec00000.v3d: MMU error from client CLE (4) at 0x6dc1000, pte invalid
Feb 27 17:26:25.549369 Lanser iwd[410]: invalid HE capabilities
Feb 27 17:26:25.549889 Lanser iwd[410]: error parsing non-HT rates

Quote from wyup

Does Android use OpenGL or Vulkan for this?

Android supports OpenGLES and Vulkan. I don't think it's used pretty much, because they use a lot of hardware acceleration for video playback. RPi does the opposite: It uses a lot of software decoding, which needs more processing power.

So both platforms might deliver the same performance on different hardware.