Posts by ozarks

Quote from chewitt

Yup! .. but AFAIK the codebase is still lacking HDMI audio and most of the video codecs

See: https://gitlab.collabora.com/hardware-enabl…?ref_type=heads

Thanks for the update and the link, which does indeed show that there is still some way to go for the right elements to be in place.

One stop forward though and with the RK3588 starting to look like another Lemon like the RK3399, any improvements from those outside of the inner Rockchip bubble are going to give some hope to avoid a successive Rockchip failure.

OpenGL ES 3.1 conformance is also another step forward.

With the new release of Linux 6.10 Release, notably the Panthor open-source driver now being an official constituent of the kernel, does this increase the possibility of official LibreELEC support?

Quote from Mister_Sparkle

Hello,

Searched this thread and I did not find specific mention of whether or not this can be used on the Orange Pi 5b? If so, are the steps the exact same as in the original post ?

They would be the same except for the image that you start with, which in your case will be for the 5b model.

The original link will be unavailable but you could use one of the latest builds from https://github.com/armbian/os/releases

You will find that newer releases will be for kernels 5.1 6.1 and 6.8, so begin with the 5.1 and then perhaps see wat happens with the other 2.

Just note that not everything is working in Kodi yet, such as HDR and, if I remember correctly, some 10bit videos.

You may also be interesting in another fork that has been developed where there is great interest in Kodi and things are at a more advanced stage.

Releases · Joshua-Riek/ubuntu-rockchip

Ubuntu 22.04 and 24.04 for Rockchip RK35XX Devices - Joshua-Riek/ubuntu-rockchip

github.com

orange pi 5 plus use kodi ，When playing 4k, the screen goes black, but the sound and subtitles are displayed normally · Issue #815 · Joshua-Riek/ubuntu-rockchip

orange pi 5 plus use kodi ，When playing 4k, the screen goes black, but the sound and subtitles are displayed normally ubuntu24

github.com

Sadly though, right now, because of the failures of both Rockchip and in this case, Orange Pi, all the necessary things to make Kodi fully functional on the RK3588 seem a fair way away and it, IMO, could be 3 years from release that things come together because of the great independent devs and communities.

Quote from chewitt

https://gitlab.collabora.com/hardware-enabl…nline-status.md

AFAIK the HDMI code has either been submitted or is close to being submitted, and panthor GPU support is now merged, but hardware video decode codecs are still missing. It'll be usable at 1080p with software decoding. I'm not sure about 4K media.

At this point someone who cares about RK3588 support should probably submit changes to create an LE13 image. I think we'd have no problem with including backports and patches that are iterating on mailing lists, but we wouldn't accept drivers from the vendor codebase uless backed with a commitment from a "known name" developer planning to rework them in the mid-term.

Thanks for the clarification.

There is one person working on Linux that does seem to show an interest in Kodi, who may perhaps be interested but whether they would be considered a known name I can't know.

But I will make them aware of this thread such that they can make a decision as to whether they wish to approach your team.

With new kernel 6.1 (and even 6.8) development picking up stream as well as many patches and fixes also seemingly being pushed upstream, I was wondering what the general current progress was in respect of the RK3588/s SOC in general.

Just trying to get a baseline, with no unrealistic or unreasonable expectations.

There are any number of chap RK3328 boxes on Aliexpress that would do the trick and checking on the specific Rockchip forum here may help focus more on specific models.

I would tend to avoid the 2Gb/16Gb varieties as they tend to come with only 100Mb Ethernet and 2.4Ghz WiFi.

The suggestion from emveepee regarding the S905W2 is also valid.

Which Rockchip SOC are you using?

I noticed that the Firefly Station M3 was supported but I could not identify a DTB for this model.

Quote from Adr3nal1n

Hi,

For all the those with an Orange Pi 5, I have posted a guide over on the Armbian forums to enable Kodi on Orange Pi 5 with GPU Hardware Acceleration and HDMI Audio.

[GUIDE] Kodi on Orange Pi 5 with GPU Hardware Acceleration and HDMI Audio

Hope this helps scratch that Kodi itch, until the superstars that maintain LibreELEC have a build available for the Orange Pi 5.

Awesome. The community development for this board in such a short space of time is amazing.

I tried the latest nightly and it now works correctly on both systems.

There might be a pointer here that could be of the same use in LibreELEC

Rtl8761b bluetooth driver fix - General - CoreELEC Forums

Quote from mglae

In the meantime kernel is updated to 5.9 with included IOMMU support.

There are reports that Braswell is working when using the intel_iommu=on kernel parameter.

Thanks for the update.

Can this parameter be added somewhere after a set-up or is it something that has to be done prior to a build?

Quote from mglae

Seems to be a kernel issue with Braswell CPUs. There is a comment in kernel 5.8.7 PR with linked bug report.

Thanks.

That does explain why and I will follow the progress to see if it gets resolved.

I've tried a number of builds, including the latest and there is no change in behaviour.

Originally had this problem with a Millhouse Kodi build but nobody on the Kodi forum was able to help, so tried with a fresh default generic Libreelec installation and then with the latest nightly with all 3 showing the same results. The following is the key elements of my post. I had thought that Braswell would no longer be supported but it seemed that the most likely scenario was a switch to i965 rather than iHD but I was unable to find a method that would work.

I carried out a new installation to a USB flash drive and booted using an Asock Beebox N3150.

After seeing the initial text splash screen that gave the options for running (live, run etc) the screen went blank and the only activity was for a few seconds on the flash drive.

I shut it down and booted from the same flash drive to an ancient second gen i7 laptop and it booted fine.

I set a manual IP address, booted again from the Beebox and then SSH into the box to look at the log.

There was a specific line that stood out that read ERROR <general>: libva error: /usr/lib/dri/iHD_drv_video.so init failed

I guessed that this might point to the problem but whilst I could find plenty of info about it, it was all geared towards Linux installations and I could not see anything that might help solve things.

Copied the contents of the Kodi log to hastebin and hope that this gives the required information for diagnosis.

hastebin

Thanks

Quote from robert_cz

Code

LibreELEC (official): 9.2.3 (Generic.x86_64)

LibreELEC:~ # lspci
(...)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 0c)
(...)

On this hardware I have this problem:

Code

LibreELEC:~ # vainfo
libva info: VA-API version 1.5.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_5
libva error: /usr/lib/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

Any idea?

Quote from robert_cz

Code

LibreELEC (official): 9.2.3 (Generic.x86_64)

LibreELEC:~ # lspci
(...)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 0c)
(...)

On this hardware I have this problem:

Code

LibreELEC:~ # vainfo
libva info: VA-API version 1.5.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_5
libva error: /usr/lib/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

Any idea?

Are you getting a blank screen after seeing the initial splash to confirm booting?

I have a couple of older Intel Boxes. One running a x5-Z8350 (HD Graphics (Cherrytrail)) and the other a Celeron N3150 (Intel(R) HD Graphics 400 (Braswell).

Both were previously running fine using some old builds based upon Linux kernel 4.19.

I created a new fresh USB boot using 9.2.2 and fired it up on each box.

On the x5-Z8350 I end up with a blank screen other than a few lines showing errors, all very similar such as:

[ 0.37032] ACPI Bios error (bug) failure creating named object [\SB.STR3], AE_ALREADY_EXISTS (20190215/dswload2-324)

On the N3150, there is just a black screen.

On both boxes however, I was able to SSH with WinSCP, which seemed to indicate a successful boot process.

I also ran the command kodi-send --host=127.0.0.1 -a "TakeScreenshot" and to my surprise, it captured the full Estuary opening screen.

The same USB build works fine on machines with an old Core i7-2630Q or newer N3350 or N4200.

Trying various older builds I find that anything based upon Linux kernel 5 or above will not work but anything prior to that works.

Searching for info regarding the ACPI bios error doesn't yield anything that specifically answers the question as to what it is any why it occurs.

I was asked to update a friends older Libreelec running on an SD card on their Beelink GT 1 clone 2Gb/16Gb/1GB Lan(which runs GT1 Android perfectly).

But I ran into some issues.

Firstly in the initial post of this thread there is mention of a new activation of the universal multi-boot but no mention of what, where and how this part is achieved.

So I soldiered on with the knowledge that I had from previous installation.

Flashed the latest S912 image (LibreELEC-AMLGX.arm-9.80-devel-20190821140333-07b919f-s912.img)

It was to clear which DTB should be used but as this was a q201 board (which the previous Libreelec version had a DTB for this setup) it seemed logical to start with the meson-gxm-q201.dtb, so I modified uEnv.ini and extlinux.conf as appropriate.

Popped in the SD card and started up the box, which initially booted to Android, so I installed the Reboot to Libreelec app, ran it and it proceeded to boot from the SD card and I saw the Libreelec logo.

But after waiting a little while, I noticed that a reboot had been automatically initiated, where it would go through the same process again and again, in some form of boot loop. It did this a number of times before just stopping with no activity and a blank screen.

So I switched the box off and put the SD card into my PC to see what it;s state was. It seemed to be at the same state that it was in before placing it onto the Android box.

I wondered whether the dtb was incompatible, so after a little searching it seemed that the extlinux.conf or meson-gxm-rbox-pro might potentially be compatible but after trying each, the same boot loop activity occurred.

So I am stuck as to what direction to go in next and wonder whether this mysterious universal multi-boot thing holds the answer?