Jump to content
  • 0

RK3399 Legacy Multimedia Framework


JMCC
 Share

Question

IT'S FINALLY HERE...

background-business-design-star-internet-concept-1626698-pxhere_com.jpg.719bd6b4d02c30003ba20713d391aede.jpg

THE OFFICIAL ROCKCHIP-LEGACY MULTIMEDIA INTEGRATION

 

After two years of using a separate script to enable the multimedia features in RK3399 Legacy Kernel, the whole framework has been incorporated to the official Armbian packaging system. The choice distro for this integration is Debian Buster (see FAQ at the end of this post about the reasons).

 

I. Installation

  1. Download a Armbian Buster Legacy Desktop image for your board, and install it with the standard Armbian method.
  2. Install the complete multimedia solution with
    sudo apt update && sudo apt upgrade
    
    sudo apt install media-buster-legacy-rk3399 --install-recommends

    The switch "--install-recommends" will add the whole Kodi binary addons collection (retro-gaming cores, music visualizations, screensavers, additional media decoders/encoders, vfs, etc.), plus the GLES-to-OpenGL wrapper "gl4es".

 

II. Features

  1. Accelerated GLES/EGL X desktop: No action needed.
  2. Accelerated Chromium, with WebGL and video display acceleration: No action needed
  3. Desktop video player capable of smooth 4K HEVC-HDRUse the "Rockchip Gst Player" from the Multimedia menu, or choose it with right-click on the media file. Command-line 4K playing is also possible with "gst-play-1.0 --videosink=kmssink".
  4. RKMPP-accelerated MPV: Use normally for standard operation (windowed with mouse-operated GUI). For fullscreen, keyboard-operated mode, use the command line switch "--gpu-context=drm" (this will allow you to play smooth 4K).
            - See instructions below, in the next post, for playing YouTube videos up to 4K with this MPV.

  5. ISP Camera with real-time h.264/1080p HW encoding: Using the Gstreamer Plugin. Check this wiki for instructions on how to use it. Most of it applies to Armbian, except for the selection of ov5647/imx219 camera, which must be done using DT overlays.
  6. OpenCL 1.2 support: It will be fully functional, no further action needed. You can download some tests and examples from this link.
  7. Kodi 18.9 Leia with full RKMPP+GBM acceleration, 4K-HDR capable: You can start it from LightDM menu as your user account: 
    kodi-gbm-info.jpg.271beb6d036378968e74faa1f841dcbd.jpg

    Alternatively, you can also run it as a system service with these command lines:
    sudo systemctl disable lightdm
    sudo systemctl enable kodi-gbm
    sudo reboot
  8. Full collection of Kodi binary add-ons: Includes retrogaming cores, media encoders and decoders, PVR, screensavers, vfs and audio visualizations. They are all installed with the package "kodi-addons-full", but are disabled by default. They need to be enabled individually within the Kodi GUI.
  9. OpenGL 2.1 support through the gl4es wrapper: It is installed with the package "gl4es", with no further action needed.

 

III. Sources

This is the list of the sources used for the packages:

 

IV. FAQ

  • ¿Why did you use Debian Buster as a base for this implementation?
    It was the most appropriate for several reasons. Upstream Rockchip-Linux developers use Debian buster, so the software could be ported with less modifications than if we chose a different distro. Besides, it is a completely stable distro, unlike Bullseye, which is a moving target as of today. It also has Chromium as a package, unlike Focal that uses snap instead. For last, it has a good backports repo, with several libs that would otherwise need to be compiled and maintained if we chose, for example, Focal.
     
  • ¿Why Legacy instead of Mainline?
    This is an implementation based on the vendor's BSP kernel. It has been tested and is reliable, which many people will prefer rather than having a bleeding-edge, less stable implementation. In addition to that, Mainline upstream multimedia support is still a WIP, and lacks many features that are only present on Legacy kernels.
     
  • ¿Will you add new features to this implementation?
    No, this implementation will only receive bug fixes if necessary. From now on, all multimedia work will be focused on Mainline and recent distros (like Focal or Bullseye). All new features will go there.
Link to comment
Share on other sites

Recommended Posts

  • 0
4 hours ago, ATK said:

UPDATE  : just checked inside armbian-config there "enable desktop environment" was disabled (don't know why this happened, before updating/upgrading this fresh installation desktop was all good and running)... So I just "enabled desktop environment" Again... Rebooted... And was back in DE... 

BUT one more observation/issue came up even before this update/upgrade....when I first installed this image I plugged in a "Dell" Wireless mouse/Keyboard pair (WIRELESS Kb/mouse receiver dongle inserted in USB2).. strange thing is happening now... It's all ok if I only use mouse BUT the moment I punch in few keys using the keyboard the system just suddenly halts.. I further investigated this by plugging in a USB/SERIAL cable.. I observed that the moment this keyboard activity/system halt happens the terminal throws up some messages which seems to be some "sleep" /PMIC  related and also some "exceptions" are reported.... Picture of those messages are attached. 

IMG_20210803_084612.jpg

I'm not sure how this issue can be related to the multimedia framework. Please post armbianmonitor -u

Link to comment
Share on other sites

When discussing a problem make sure to provide full logs!

  • 0

I finally moved the installation from SD card to eMMC (using NAND SATA Install script)and after that no problem experienced BUT F.Y.I below I am sharing Armbianmonitor output for both condition (when OS was on SD card and later when the OS was on eMMC) .

Armbianmonitor output  (OS on SD card)>>   http://ix.io/3uY1

Armbianmonitor output  (OS on eMMC)>>   http://ix.io/3uYa

 

Please also suggest which is the best scheme for CPU Governor  "On demand" or "Performance"  ?

Link to comment
Share on other sites

  • 0
6 minutes ago, ATK said:

which is the best scheme for CPU Governor  "On demand" or "Performance"  ?

Ondemand works very well in this kernel, more efficient and you won't notice any performance loss in most use cases

Link to comment
Share on other sites

  • 0

@JMCC continuing testing

 

 

 

I tested the new KODI on a Nanopc T4 + 4k TV with 4k resolution. Everything works fine. When playing test videos to the full screen, which works in 4k mode (desktop resolution 3840x2160), the load on the processor is minimal, here is a fragment of monitoring. For those who want to try a new version of KODI on Nanopc T4, there is a link to Bullseye test images with a new core.  :)

 

https://disk.yandex.ru/d/oUSTsAI_oRCGMA

 

 

Time       big.LITTLE   load %cpu %sys %usr %nice %io %irq   CPU  C.St.
15:09:09:  408/1416MHz  1.43   8%   2%   3%   1%   0%   0% 50.6�°C  0/5
15:09:15:  600/ 600MHz  1.47   4%   1%   1%   0%   0%   0% 50.0�°C  0/5
15:09:20:  408/ 600MHz  1.44   5%   1%   1%   0%   0%   0% 50.0�°C  0/5
15:09:25:  600/ 408MHz  1.48   4%   1%   1%   0%   0%   0% 50.0�°C  0/5
15:09:30:  408/ 600MHz  1.44   4%   1%   1%   0%   0%   0% 50.0�°C  0/5
15:09:35:  408/ 408MHz  1.41   5%   1%   1%   0%   0%   1% 50.0�°C  0/5
15:09:40:  408/ 408MHz  1.45   5%   2%   1%   0%   0%   0% 50.0�°C  0/5
15:09:45:  408/ 600MHz  1.50   4%   2%   1%   0%   0%   0% 50.0�°C  0/5
15:09:51:  408/ 408MHz  1.54   4%   1%   1%   0%   0%   0% 50.0�°C  0/5
15:09:56:  408/ 408MHz  1.60   4%   1%   1%   0%   0%   0% 50.0�°C  0/5
15:10:01: 1800/ 600MHz  1.64   4%   2%   1%   0%   0%   0% 50.6�°C  0/5
15:10:06:  408/ 408MHz  1.66   4%   2%   1%   0%   0%   0% 50.0�°C  0/5
15:10:11: 1800/ 408MHz  1.61   4%   1%   1%   0%   0%   0% 50.0�°C  0/5

 

Link to comment
Share on other sites

  • 0
9 minutes ago, balbes150 said:

@JMCCWe kindly ask you not to add dependencies on specific kernels to future packages. New kernels with HW can be for RK \ AW and different versions of edge \ current.

Yes, that makes sense. As a matter of fact, the legacy Kodi packages don't have any kernel dependency, it is only the meta-package for the whole multimedia framework that depended on the legacy kernel. The reason for that was that, if installed on a different kernel, it would break the system. But Kodi won't break anything by itself, so no kernel dependencies this time, I promise :)

Link to comment
Share on other sites

  • 0
On 9/27/2021 at 1:35 PM, JMCC said:

Kodi won't break anything by itself, so no kernel dependencies this time

 

I am looking for an easy way to install Kodi on a headless server (Helios64 - rk3399). I am not using a legacy kernel but 5.10.43 and Armbian Bullseye.

The intention is just to stream videos and display pictures with Kodi to a DLNA enabled smart TV.

 

Any help would be greatly appreciated !

Link to comment
Share on other sites

  • 0
On 10/3/2021 at 11:35 AM, ebin-dev said:

 

I am looking for an easy way to install Kodi on a headless server (Helios64 - rk3399). I am not using a legacy kernel but 5.10.43 and Armbian Bullseye.

The intention is just to stream videos and display pictures with Kodi to a DLNA enabled smart TV.

 

Any help would be greatly appreciated !

As stated above, you can install the packages from this link: https://users.armbian.com/jmcc/packages/kodi-mainline/arm64/

 

I am planning to build Kodi 19 packages and integrate them into the Armbian repos, but no ETA yet.

Link to comment
Share on other sites

  • 0
On 10/4/2021 at 1:17 PM, JMCC said:

As stated above, you can install the packages from this link: https://users.armbian.com/jmcc/packages/kodi-mainline/arm64/

 

I am planning to build Kodi 19 packages and integrate them into the Armbian repos, but no ETA yet.

 

Thank you very much for the hint. Installation of the packages went smoothly on the headless server. After messing around with the configuration files guisettings.xml and advancedsettings.xml I could access the web interface on port 8080 and change the settings, configure some addons etc.

 

However, it would not appear to be possible to add a media library or addons using the web interface - the required functionality is not displayed. Is this a known limitation of the web interface or is this due to a mistake on my side ?  As there is no access to any other Kodi GUI on the headless server I am stuck at that point. 

 

I am looking forward to test Kodi 19 packages once you found some time to build them.

Link to comment
Share on other sites

  • 0
4 hours ago, ebin-dev said:

it would not appear to be possible to add a media library or addons using the web interface

No idea, I never did that. I guess you may be luckier in the Kodi forums.

 

However, if you are using Kodi as a headless server, I see no point in using my packages. The only benefit they have is HW accelerated video play, but you are not using Kodi to watch the videos, are you? If that is the case, then you may be better off using the standard distro packages, which may have some functionalities enabled that are not present in my packages (maybe, I don't know, I never used them).

Link to comment
Share on other sites

  • 0
22 hours ago, JMCC said:

However, if you are using Kodi as a headless server, I see no point in using my packages.

 

Actually I am currently just exploring. Using Kodi as a headless server to stream to DLNA enabled devices turned out to be suboptimal :-)) .

 

Meanwhile I switched to Plex on the server. For all clients (SmartTV, Computers and iOS Devices) a native Plex app is available for free (except for iOS - a one time fee of 4.99 Euros is required for each device) and I am astonished about the performance and professional look of the system. The installation is configured as non-accessible from the outside - nonetheless the media can be streamed to remote devices coupled to the home network via VPN. Setting up a client-server system with Plex is a "no-brainer". You just have to make sure that the required ports are not used by other servers (port 9090 was used by another media server in my case).

 

I would strongly recommend Plex if you wish to stream content from a (headless) server to various client devices in your home network.

Link to comment
Share on other sites

  • 0

Hi!

I'm trying to install the legacy-multimedia-framework on my rockpro64 but I always end with a non working system.

Even ssh service is not available...

 

Here my steps:

  • install armbian buster (on eMMC using usbimager)
  • Complete the first boot configuration (password, user, ecc...)
  • apt update; apt upgrade
  • apt install media-buster-legacy-rk3399 --install-recommends
  • reboot
  • the board light are flashing but, after the boot prompt, the screen becomes total black and all the command I enter at the keyboard have no effect

Nothing more, nothing less.

I have also tried installing desktop using the armbian-config before the framework (which works well), but I ended in the same situation.

 

Can you suggest what I might have done wrong?

Thank you,

Riccardo

 

Edited by Rickyx
more info
Link to comment
Share on other sites

  • 0
52 minutes ago, Rickyx said:

Hi!

I'm trying to install the legacy-multimedia-framework on my rockpro64 but I always end with a non working system.

Even ssh service is not available...

 

Here my steps:

  • install armbian buster (on eMMC using usbimager)
  • Complete the first boot configuration (password, user, ecc...)
  • apt update; apt upgrade
  • apt install media-buster-legacy-rk3399 --install-recommends
  • reboot
  • the board light are flashing but, after the boot prompt, the screen becomes total black and all the command I enter at the keyboard have no effect

Nothing more, nothing less.

I have also tried installing desktop using the armbian-config before the framework (which works well), but I ended in the same situation.

 

Can you suggest what I might have done wrong?

Thank you,

Riccardo

 

First if all, if you want help you need to provide some basic information, like "armbianmonitor -u". Please read forum rules.

 

Second, are you sure you are using a buster legacy image, not "current"?

Link to comment
Share on other sites

  • 0

Thank you Jmcc,

I mistakenly thought that legacy was referring to the fact that buster is the old version: but instead it refers to a different the kernel version...

After downloading the last legacy version from:

https://armbian.hosthatch.com/archive/rockpro64/archive/

I correctly set all the framework.

 

Now chromium+threejs works very smooth.

Thank you again,

Riccardo

Link to comment
Share on other sites

  • 0

How is the state of this on the new release? Is VPU now possible on mainline?
I had tried images from balbes150 for the station P1 where I could install his Kodi packages for this. I was wondering if this now is possible on the latest release or not? And what packages need to be used for this?
Greetings.

Link to comment
Share on other sites

  • 0
23 hours ago, gounthar said:

What about hardware encoding with mainline?
Is it possible now?

Not AFAIK, and also ISP camera support was planned but I am not sure of the current status. I think those are the two main points why someone would like to stay using legacy.

 

On 3/3/2022 at 12:12 PM, NicoD said:

How is the state of this on the new release? Is VPU now possible on mainline?
I had tried images from balbes150 for the station P1 where I could install his Kodi packages for this. I was wondering if this now is possible on the latest release or not? And what packages need to be used for this?
Greetings.

I wanted to do some standard packages for all distros in mainline, but I have been overloaded since some time ago, and I am not sure when will I be able to have a look at it. I will announce if it becomes ready.

Link to comment
Share on other sites

  • 0
4 hours ago, JMCC said:

but I have been overloaded since some time ago

Take care of yourself and those around you. Best of luck. These things can wait. Cheers.

Link to comment
Share on other sites

  • 0

In NanopiM4v2 for sound on hdmi:

Edit the Alsa config:

 

nano /etc/asound.conf 

 

Delete old content and paste the following one:

 

pcm.snd_card { type hw card 1 device 0 } ctl.snd_card { type hw card 1 device 0 } pcm.dmixer { type dmix ipc_key 1024 ipc_perm 0666 slave.pcm "snd_card" slave { period_time 0 period_size 1024 buffer_size 4096 rate 48000 format S16_LE channels 2 } bindings { 0 0 1 1 } } 

Save the file and reboot.

Link to comment
Share on other sites

  • 0
17.12.2020 в 22:02, JMCC сказал:
 

IT'S FINALLY HERE...

 

THE OFFICIAL ROCKCHIP-LEGACY MULTIMEDIA INTEGRATION

 

After two years of using a separate script to enable the multimedia features in RK3399 Legacy Kernel, the whole framework has been incorporated to the official Armbian packaging system. The choice distro for this integration is Debian Buster (see FAQ at the end of this post about the reasons).

 

I. Installation

  1. Download a Armbian Buster Legacy Desktop image for your board, and install it with the standard Armbian method.
  2. Install the complete multimedia solution with
    sudo apt update && sudo apt upgrade
    
    sudo apt install media-buster-legacy-rk3399 --install-recommends

    The switch "--install-recommends" will add the whole Kodi binary addons collection (retro-gaming cores, music visualizations, screensavers, additional media decoders/encoders, vfs, etc.), plus the GLES-to-OpenGL wrapper "gl4es".


I am have RockPi 4C.
I am go to https://armbian.hosthatch.com/archive/rockpi-4c/ and download latest buster legacy:

https://armbian.hosthatch.com/archive/rockpi-4c/archive/Armbian_21.08.1_Rockpi-4c_buster_legacy_4.4.213_xfce_desktop.img.xz


Write image on sd card, boot from sd card and do commands:

sudo apt update && sudo apt upgrade
sudo apt install media-buster-legacy-rk3399 --install-recommends

And reboot

 

But I am see on my monitor (connected via hdmi) only blank screen.

Some info I am found in logs:

/var/log/Xorg.0.log

Скрытый текст

[    22.924] (II) modeset(0): glamor X acceleration enabled on Mali-T860
[    22.925] (II) modeset(0): glamor initialized
[    22.925] (II) modeset(0): FlipFB: Transformed
[    22.928] (II) modeset(0): Output HDMI-1 has no monitor section
[    22.929] (II) modeset(0): Bind output 91 to current crtc 64.
[    22.933] (II) modeset(0): EDID for output HDMI-1
[    22.933] (II) modeset(0): Printing probed modes for output HDMI-1
[    22.933] (II) modeset(0): Modeline "1280x720"x60.0   74.25  1280 1390 1430 1650  720 725 730 750 +hsync +vsync (45.0 kHz P)
[    22.933] (II) modeset(0): Modeline "1920x1080"x60.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[    22.933] (II) modeset(0): Modeline "1920x1080"x50.0  148.50  1920 2448 2492 2640  1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
[    22.933] (II) modeset(0): Modeline "1280x720"x50.0   74.25  1280 1720 1760 1980  720 725 730 750 +hsync +vsync (37.5 kHz e)
[    22.933] (II) modeset(0): Modeline "720x576"x50.0   27.00  720 732 796 864  576 581 586 625 -hsync -vsync (31.2 kHz e)
[    22.933] (II) modeset(0): Modeline "720x480"x59.9   27.00  720 736 798 858  480 489 495 525 -hsync -vsync (31.5 kHz e)
[    22.933] (II) modeset(0): Output HDMI-1 connected
[    22.933] (II) modeset(0): Using exact sizes for initial modes
[    22.933] (II) modeset(0): Output HDMI-1 using initial mode 1280x720 +0+0
[    22.934] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[    22.934] (==) modeset(0): DPI set to (96, 96)

 

[    23.696] (II) Initializing extension GLX
[    23.698] (EE) AIGLX error: dlopen of /usr/lib/aarch64-linux-gnu/dri/rockchip_dri.so failed (/usr/lib/aarch64-linux-gnu/dri/rockchip_dri.so: cannot open shared object file: No such file or directory)
[    23.699] (EE) AIGLX error: unable to load driver rockchip

 

/var/log/lightdm/seat0-greeter.log

Скрытый текст

==>[INIT] (slick-greeter-c) CDBG: In file: cdbg/src/mali_cdbg_env.c  line: 763 cdbgp_populate_from_system_environment
Initialization of a handle to the system environment failed (3)
ERROR: The DDK is not compatible with any of the Mali GPUs on the system.
The DDK was built for 0x860 r2p0 status range [0..15], but none of the GPUs matched:
LIBGL: Error while gathering supported extension (eglInitialize: EGL_NOT_INITIALIZED), default to none
/usr/bin/slick-greeter-check-hidpi:17: DeprecationWarning: Gdk.Screen.get_primary_monitor is deprecated
  primary = screen.get_primary_monitor()
/usr/bin/slick-greeter-check-hidpi:19: DeprecationWarning: Gdk.Screen.get_monitor_geometry is deprecated
  rect = screen.get_monitor_geometry(primary)
/usr/bin/slick-greeter-check-hidpi:20: DeprecationWarning: Gdk.Screen.get_monitor_width_mm is deprecated
  width_mm = screen.get_monitor_width_mm(primary)
/usr/bin/slick-greeter-check-hidpi:21: DeprecationWarning: Gdk.Screen.get_monitor_height_mm is deprecated
  height_mm = screen.get_monitor_height_mm(primary)
/usr/bin/slick-greeter-check-hidpi:22: DeprecationWarning: Gdk.Screen.get_monitor_scale_factor is deprecated
  monitor_scale = screen.get_monitor_scale_factor(primary)
[+0.95s] DEBUG: Connected api=1 version=1.26.0 default-session=xfce show-manual-login=false hide-users=false has-guest-account=false show-remote-login=true
[+1.16s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
[+1.16s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+1.16s] DEBUG: User roots added
[+1.22s] DEBUG: Loaded session /usr/share/xsessions/kodi-gbm.desktop (Kodi-GBM, This session will start Kodi media center)
[+1.22s] DEBUG: Ignoring session /usr/share/xsessions/kodi-x11.desktop
[+1.22s] DEBUG: Loaded session /usr/share/xsessions/lightdm-xsession.desktop (Default Xsession, )
[+1.22s] DEBUG: Loaded session /usr/share/xsessions/xfce.desktop (Xfce Session, Use this session to run Xfce as your desktop environment)
[+1.22s] DEBUG: Starting authentication for user roots...
[+1.22s] DEBUG: Wrote 21 bytes to daemon
[+1.23s] DEBUG: slick-greeter.vala:718: Starting main loop
[+1.25s] DEBUG: Read 8 bytes from daemon
[+1.25s] DEBUG: Read 35 bytes from daemon
[+1.25s] DEBUG: Prompt user with 1 message(s)
[+1.26s] DEBUG: background.vala:571: Regenerating backgrounds
[+1.26s] DEBUG: background.vala:68: Making background #000000 at 1024x768
[+1.26s] DEBUG: background.vala:79: Render of background #000000 complete
[+1.26s] DEBUG: background.vala:68: Making background /usr/share/backgrounds/armbian-lightdm/armbian03-Dre0x-Minum-dark-blurred-3840x2160.jpg at 1024x768
[+1.27s] DEBUG: background.vala:571: Regenerating backgrounds
[+1.27s] DEBUG: background.vala:68: Making background #000000 at 1024x768
[+1.27s] DEBUG: background.vala:79: Render of background #000000 complete
[+1.27s] DEBUG: background.vala:68: Making background /usr/share/backgrounds/armbian-lightdm/armbian03-Dre0x-Minum-dark-blurred-3840x2160.jpg at 1024x768
[+1.51s] DEBUG: slick-greeter.vala:282: starting system-ready sound
[+1.62s] DEBUG: background.vala:121: Render of background /usr/share/backgrounds/armbian-lightdm/armbian03-Dre0x-Minum-dark-blurred-3840x2160.jpg complete
[+1.72s] DEBUG: background.vala:121: Render of background /usr/share/backgrounds/armbian-lightdm/armbian03-Dre0x-Minum-dark-blurred-3840x2160.jpg complete
Gdk-Message: 09:16:52.933: slick-greeter: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
      after 21 requests (21 known processed) with 0 events remaining.
 

 

armbianmonitor -u: http://ix.io/3Z0A

 

Can you help me?
Thank you!

Link to comment
Share on other sites

  • 0
28 minutes ago, amurchick said:


I am have RockPi 4C.
I am go to https://armbian.hosthatch.com/archive/rockpi-4c/ and download latest buster legacy:

https://armbian.hosthatch.com/archive/rockpi-4c/archive/Armbian_21.08.1_Rockpi-4c_buster_legacy_4.4.213_xfce_desktop.img.xz


Write image on sd card, boot from sd card and do commands:

sudo apt update && sudo apt upgrade
sudo apt install media-buster-legacy-rk3399 --install-recommends

And reboot

 

But I am see on my monitor (connected via hdmi) only blank screen.

Some info I am found in logs:

/var/log/Xorg.0.log

  Reveal hidden contents

[    22.924] (II) modeset(0): glamor X acceleration enabled on Mali-T860
[    22.925] (II) modeset(0): glamor initialized
[    22.925] (II) modeset(0): FlipFB: Transformed
[    22.928] (II) modeset(0): Output HDMI-1 has no monitor section
[    22.929] (II) modeset(0): Bind output 91 to current crtc 64.
[    22.933] (II) modeset(0): EDID for output HDMI-1
[    22.933] (II) modeset(0): Printing probed modes for output HDMI-1
[    22.933] (II) modeset(0): Modeline "1280x720"x60.0   74.25  1280 1390 1430 1650  720 725 730 750 +hsync +vsync (45.0 kHz P)
[    22.933] (II) modeset(0): Modeline "1920x1080"x60.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[    22.933] (II) modeset(0): Modeline "1920x1080"x50.0  148.50  1920 2448 2492 2640  1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
[    22.933] (II) modeset(0): Modeline "1280x720"x50.0   74.25  1280 1720 1760 1980  720 725 730 750 +hsync +vsync (37.5 kHz e)
[    22.933] (II) modeset(0): Modeline "720x576"x50.0   27.00  720 732 796 864  576 581 586 625 -hsync -vsync (31.2 kHz e)
[    22.933] (II) modeset(0): Modeline "720x480"x59.9   27.00  720 736 798 858  480 489 495 525 -hsync -vsync (31.5 kHz e)
[    22.933] (II) modeset(0): Output HDMI-1 connected
[    22.933] (II) modeset(0): Using exact sizes for initial modes
[    22.933] (II) modeset(0): Output HDMI-1 using initial mode 1280x720 +0+0
[    22.934] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[    22.934] (==) modeset(0): DPI set to (96, 96)

 

[    23.696] (II) Initializing extension GLX
[    23.698] (EE) AIGLX error: dlopen of /usr/lib/aarch64-linux-gnu/dri/rockchip_dri.so failed (/usr/lib/aarch64-linux-gnu/dri/rockchip_dri.so: cannot open shared object file: No such file or directory)
[    23.699] (EE) AIGLX error: unable to load driver rockchip

 

/var/log/lightdm/seat0-greeter.log

  Reveal hidden contents

==>[INIT] (slick-greeter-c) CDBG: In file: cdbg/src/mali_cdbg_env.c  line: 763 cdbgp_populate_from_system_environment
Initialization of a handle to the system environment failed (3)
ERROR: The DDK is not compatible with any of the Mali GPUs on the system.
The DDK was built for 0x860 r2p0 status range [0..15], but none of the GPUs matched:
LIBGL: Error while gathering supported extension (eglInitialize: EGL_NOT_INITIALIZED), default to none
/usr/bin/slick-greeter-check-hidpi:17: DeprecationWarning: Gdk.Screen.get_primary_monitor is deprecated
  primary = screen.get_primary_monitor()
/usr/bin/slick-greeter-check-hidpi:19: DeprecationWarning: Gdk.Screen.get_monitor_geometry is deprecated
  rect = screen.get_monitor_geometry(primary)
/usr/bin/slick-greeter-check-hidpi:20: DeprecationWarning: Gdk.Screen.get_monitor_width_mm is deprecated
  width_mm = screen.get_monitor_width_mm(primary)
/usr/bin/slick-greeter-check-hidpi:21: DeprecationWarning: Gdk.Screen.get_monitor_height_mm is deprecated
  height_mm = screen.get_monitor_height_mm(primary)
/usr/bin/slick-greeter-check-hidpi:22: DeprecationWarning: Gdk.Screen.get_monitor_scale_factor is deprecated
  monitor_scale = screen.get_monitor_scale_factor(primary)
[+0.95s] DEBUG: Connected api=1 version=1.26.0 default-session=xfce show-manual-login=false hide-users=false has-guest-account=false show-remote-login=true
[+1.16s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
[+1.16s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+1.16s] DEBUG: User roots added
[+1.22s] DEBUG: Loaded session /usr/share/xsessions/kodi-gbm.desktop (Kodi-GBM, This session will start Kodi media center)
[+1.22s] DEBUG: Ignoring session /usr/share/xsessions/kodi-x11.desktop
[+1.22s] DEBUG: Loaded session /usr/share/xsessions/lightdm-xsession.desktop (Default Xsession, )
[+1.22s] DEBUG: Loaded session /usr/share/xsessions/xfce.desktop (Xfce Session, Use this session to run Xfce as your desktop environment)
[+1.22s] DEBUG: Starting authentication for user roots...
[+1.22s] DEBUG: Wrote 21 bytes to daemon
[+1.23s] DEBUG: slick-greeter.vala:718: Starting main loop
[+1.25s] DEBUG: Read 8 bytes from daemon
[+1.25s] DEBUG: Read 35 bytes from daemon
[+1.25s] DEBUG: Prompt user with 1 message(s)
[+1.26s] DEBUG: background.vala:571: Regenerating backgrounds
[+1.26s] DEBUG: background.vala:68: Making background #000000 at 1024x768
[+1.26s] DEBUG: background.vala:79: Render of background #000000 complete
[+1.26s] DEBUG: background.vala:68: Making background /usr/share/backgrounds/armbian-lightdm/armbian03-Dre0x-Minum-dark-blurred-3840x2160.jpg at 1024x768
[+1.27s] DEBUG: background.vala:571: Regenerating backgrounds
[+1.27s] DEBUG: background.vala:68: Making background #000000 at 1024x768
[+1.27s] DEBUG: background.vala:79: Render of background #000000 complete
[+1.27s] DEBUG: background.vala:68: Making background /usr/share/backgrounds/armbian-lightdm/armbian03-Dre0x-Minum-dark-blurred-3840x2160.jpg at 1024x768
[+1.51s] DEBUG: slick-greeter.vala:282: starting system-ready sound
[+1.62s] DEBUG: background.vala:121: Render of background /usr/share/backgrounds/armbian-lightdm/armbian03-Dre0x-Minum-dark-blurred-3840x2160.jpg complete
[+1.72s] DEBUG: background.vala:121: Render of background /usr/share/backgrounds/armbian-lightdm/armbian03-Dre0x-Minum-dark-blurred-3840x2160.jpg complete
Gdk-Message: 09:16:52.933: slick-greeter: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
      after 21 requests (21 known processed) with 0 events remaining.
 

 

armbianmonitor -u: http://ix.io/3Z0A

 

Can you help me?
Thank you!

 

Can you please do the whole process again from scratch? I mean, flashing again the SD card, and installing the multimedia framework. This time, please post all the output of the "apt-install" command.

Also, please post the contents of /etc/X11/xorg.conf.d/*

Link to comment
Share on other sites

  • 0
18 часов назад, Rickyx сказал:

@amurchick the monitor worked well without having installed the multimedia framework?

Can you connect the monitor after the startup of the RockPi ?

@Rickyx monitor say "No signal" when first booted from sd-card.

`dmesg` says "dwhdmi-rockchip ff940000.hdmi: failed to get edid"

All my trys to remove/insert HDMI cable - make same messages in dmesg.


So I am try previous versions from https://armbian.hosthatch.com/archive/rockpi-4c/
- Armbian_21.05.1_Rockpi-4c_buster_legacy_4.4.213_xfce_desktop.img.xz

- Armbian_21.02.3_Rockpi-4c_buster_legacy_4.4.213_xfce_desktop.img.xz

- Armbian_21.02.1_Rockpi-4c_buster_legacy_4.4.213_desktop.img.xz

- Armbian_20.11.10_Rockpi-4c_buster_legacy_4.4.213_desktop.img.xz

- Armbian_20.11.6_Rockpi-4c_buster_legacy_4.4.213_desktop.img.xz

 

Same result: no signal and `dmesg` says "dwhdmi-rockchip ff940000.hdmi: failed to get edid"

 

I am have Armbian 22.05.1 Bullseye with Linux 5.15.35-rockchip64 on eMMC - when boot from it - there are image on monitor and no `dmesg` messages like "ff940000.hdmi: failed to get edid" when remove/insert HDMI cable...
But image has defects (moire) and wrong colors - so I am guess my micro-HDMI to HDMI adapter has problems (before I am never connect monitor - its role before today was headless router).


I will order new micro-HDMI to HDMI cable and try again. I will let you know result.

@Rickyx, @JMCC Thank you for time spending.

Link to comment
Share on other sites

  • 0
31.05.2022 в 17:55, JMCC сказал:

 

Can you please do the whole process again from scratch? I mean, flashing again the SD card, and installing the multimedia framework. This time, please post all the output of the "apt-install" command.

Also, please post the contents of /etc/X11/xorg.conf.d/*

I am receive new cable micro-HDMI to DHMI and try again with https://armbian.hosthatch.com/archive/rockpi-4c/archive/Armbian_21.08.1_Rockpi-4c_buster_legacy_4.4.213_xfce_desktop.img.xz

After first start I am see in serial console:

 

Now starting desktop environment...

 

But monitor says "No HDMI signal".

 

In /var/log/Xorg.0.log I am see correct monitor detection:

Скрытый текст

[   186.195] (II) modeset(0): #0: hsize: 1920  vsize 1080  refresh: 60  vid: 49361
[   186.195] (II) modeset(0): #1: hsize: 1680  vsize 1050  refresh: 60  vid: 179
[   186.195] (II) modeset(0): #2: hsize: 1600  vsize 900  refresh: 60  vid: 49321
[   186.195] (II) modeset(0): #3: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
[   186.195] (II) modeset(0): #4: hsize: 1280  vsize 800  refresh: 60  vid: 129
[   186.195] (II) modeset(0): #5: hsize: 1280  vsize 720  refresh: 60  vid: 49281
[   186.195] (II) modeset(0): Supported detailed timing:
[   186.195] (II) modeset(0): clock: 533.2 MHz   Image Size:  698 x 393 mm
[   186.195] (II) modeset(0): h_active: 3840  h_sync: 3888  h_sync_end 3920 h_blank_end 4000 h_border: 0
[   186.195] (II) modeset(0): v_active: 2160  v_sync: 2163  v_sync_end 2168 v_blanking: 2222 v_border: 0
[   186.195] (II) modeset(0): Ranges: V min: 50 V max: 76 Hz, H min: 30 H max: 135 kHz, PixClock max 605 MHz
[   186.195] (II) modeset(0): Monitor name: BenQ PD3220U
[   186.195] (II) modeset(0): Supported detailed timing:
[   186.195] (II) modeset(0): clock: 241.5 MHz   Image Size:  698 x 393 mm
[   186.195] (II) modeset(0): h_active: 2560  h_sync: 2608  h_sync_end 2640 h_blank_end 2720 h_border: 0
[   186.195] (II) modeset(0): v_active: 1440  v_sync: 1443  v_sync_end 1448 v_blanking: 1481 v_border: 0
[   186.195] (II) modeset(0): Supported detailed timing:
[   186.195] (II) modeset(0): clock: 262.8 MHz   Image Size:  698 x 393 mm
[   186.195] (II) modeset(0): h_active: 3840  h_sync: 3888  h_sync_end 3920 h_blank_end 4000 h_border: 0
[   186.195] (II) modeset(0): v_active: 2160  v_sync: 2163  v_sync_end 2168 v_blanking: 2191 v_border: 0
[   186.195] (II) modeset(0): Supported detailed timing:
[   186.195] (II) modeset(0): clock: 277.2 MHz   Image Size:  698 x 393 mm
[   186.196] (II) modeset(0): h_active: 1920  h_sync: 1968  h_sync_end 2000 h_blank_end 2080 h_border: 0
[   186.196] (II) modeset(0): v_active: 2160  v_sync: 2163  v_sync_end 2173 v_blanking: 2222 v_border: 0
[   186.196] (II) modeset(0): Number of EDID sections to follow: 1
[   186.196] (II) modeset(0): EDID (in hex):
[   186.196] (II) modeset(0):   00ffffffffffff0009d12d8045540000
[   186.196] (II) modeset(0):   161d0103804627782ea2a5ac5047ad27
[   186.196] (II) modeset(0):   0d5054a56b80d1c0b300a9c081808100
[   186.196] (II) modeset(0):   81c0010101014dd000a0f0703e803020
[   186.196] (II) modeset(0):   3500ba892100001a000000ff0057354b
[   186.196] (II) modeset(0):   30303532323031390a20000000fd0032
[   186.196] (II) modeset(0):   4c1e873c000a202020202020000000fc
[   186.196] (II) modeset(0):   0042656e5120504433323230550a0135
[   186.196] (II) modeset(0):   020344f1515d5e5f6061101f22212005
[   186.196] (II) modeset(0):   14041312030123090707830100006d03
[   186.196] (II) modeset(0):   0c002000383c20006001020367d85dc4
[   186.196] (II) modeset(0):   01788003e305e301e40f180000e60605
[   186.196] (II) modeset(0):   015b5a3f565e00a0a0a0295030203500
[   186.196] (II) modeset(0):   ba892100001aa36600a0f0701f803020
[   186.196] (II) modeset(0):   3500ba892100001a4d6c80a070703e80
[   186.196] (II) modeset(0):   30203a00ba892100001a00000000001b
[   186.196] (--) modeset(0): HDMI max TMDS frequency 300000KHz
[   186.196] (II) modeset(0): Printing probed modes for output HDMI-1
[   186.196] (II) modeset(0): Modeline "3840x2160"x60.0  533.25  3840 3888 3920 4000  2160 2163 2168 2222 +hsync -vsync (133.3 kHz eP)
[   186.196] (II) modeset(0): Modeline "3840x2160"x60.0  594.00  3840 4016 4104 4400  2160 2168 2178 2250 +hsync +vsync (135.0 kHz e)
[   186.197] (II) modeset(0): Modeline "3840x2160"x50.0  594.00  3840 4896 4984 5280  2160 2168 2178 2250 +hsync +vsync (112.5 kHz e)
[   186.197] (II) modeset(0): Modeline "3840x2160"x59.9  593.41  3840 4016 4104 4400  2160 2168 2178 2250 +hsync +vsync (134.9 kHz e)
[   186.197] (II) modeset(0): Modeline "3840x2160"x30.0  297.00  3840 4016 4104 4400  2160 2168 2178 2250 +hsync +vsync (67.5 kHz e)
[   186.197] (II) modeset(0): Modeline "3840x2160"x25.0  297.00  3840 4896 4984 5280  2160 2168 2178 2250 +hsync +vsync (56.2 kHz e)
[   186.197] (II) modeset(0): Modeline "3840x2160"x24.0  297.00  3840 5116 5204 5500  2160 2168 2178 2250 +hsync +vsync (54.0 kHz e)
[   186.197] (II) modeset(0): Modeline "3840x2160"x30.0  296.70  3840 4016 4104 4400  2160 2168 2178 2250 +hsync +vsync (67.4 kHz e)
[   186.197] (II) modeset(0): Modeline "3840x2160"x24.0  296.70  3840 5116 5204 5500  2160 2168 2178 2250 +hsync +vsync (53.9 kHz e)
[   186.197] (II) modeset(0): Modeline "3840x2160"x30.0  262.75  3840 3888 3920 4000  2160 2163 2168 2191 +hsync -vsync (65.7 kHz e)
[   186.197] (II) modeset(0): Modeline "1920x2160"x60.0  277.25  1920 1968 2000 2080  2160 2163 2173 2222 +hsync -vsync (133.3 kHz e)
[   186.197] (II) modeset(0): Modeline "2560x1440"x60.0  241.50  2560 2608 2640 2720  1440 1443 1448 1481 +hsync -vsync (88.8 kHz e)
[   186.197] (II) modeset(0): Modeline "1920x1080"x60.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 -hsync -vsync (67.5 kHz e)
[   186.197] (II) modeset(0): Modeline "1920x1080"x60.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[   186.197] (II) modeset(0): Modeline "1920x1080"x50.0  148.50  1920 2448 2492 2640  1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
[   186.197] (II) modeset(0): Modeline "1920x1080"x59.9  148.35  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.4 kHz e)
[   186.197] (II) modeset(0): Modeline "1920x1080i"x60.0   74.25  1920 2008 2052 2200  1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
[   186.197] (II) modeset(0): Modeline "1920x1080i"x50.0   74.25  1920 2448 2492 2640  1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
[   186.197] (II) modeset(0): Modeline "1920x1080"x30.0   74.25  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (33.8 kHz e)
[   186.197] (II) modeset(0): Modeline "1920x1080"x25.0   74.25  1920 2448 2492 2640  1080 1084 1089 1125 +hsync +vsync (28.1 kHz e)
[   186.197] (II) modeset(0): Modeline "1920x1080"x24.0   74.25  1920 2558 2602 2750  1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
[   186.197] (II) modeset(0): Modeline "1920x1080i"x59.9   74.18  1920 2008 2052 2200  1080 1084 1094 1125 interlace +hsync +vsync (33.7 kHz e)
[   186.197] (II) modeset(0): Modeline "1920x1080"x30.0   74.18  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (33.7 kHz e)
[   186.197] (II) modeset(0): Modeline "1920x1080"x24.0   74.18  1920 2558 2602 2750  1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
[   186.197] (II) modeset(0): Modeline "1680x1050"x59.9  119.00  1680 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[   186.197] (II) modeset(0): Modeline "1600x900"x60.0  108.00  1600 1624 1704 1800  900 901 904 1000 +hsync +vsync (60.0 kHz e)
[   186.197] (II) modeset(0): Modeline "1280x1024"x75.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[   186.197] (II) modeset(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[   186.197] (II) modeset(0): Modeline "1280x800"x59.9   71.00  1280 1328 1360 1440  800 803 809 823 +hsync -vsync (49.3 kHz e)
[   186.197] (II) modeset(0): Modeline "1152x864"x75.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[   186.197] (II) modeset(0): Modeline "1280x720"x60.0   74.25  1280 1390 1430 1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
[   186.197] (II) modeset(0): Modeline "1280x720"x50.0   74.25  1280 1720 1760 1980  720 725 730 750 +hsync +vsync (37.5 kHz e)
[   186.197] (II) modeset(0): Modeline "1280x720"x59.9   74.18  1280 1390 1430 1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
[   186.197] (II) modeset(0): Modeline "1024x768"x75.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[   186.197] (II) modeset(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[   186.197] (II) modeset(0): Modeline "832x624"x74.6   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[   186.197] (II) modeset(0): Modeline "800x600"x75.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[   186.197] (II) modeset(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[   186.197] (II) modeset(0): Modeline "720x576"x50.0   27.00  720 732 796 864  576 581 586 625 -hsync -vsync (31.2 kHz e)
[   186.197] (II) modeset(0): Modeline "720x480"x60.0   27.03  720 736 798 858  480 489 495 525 -hsync -vsync (31.5 kHz e)
[   186.197] (II) modeset(0): Modeline "720x480"x59.9   27.00  720 736 798 858  480 489 495 525 -hsync -vsync (31.5 kHz e)
[   186.198] (II) modeset(0): Modeline "640x480"x75.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[   186.198] (II) modeset(0): Modeline "640x480"x60.0   25.20  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[   186.198] (II) modeset(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[   186.198] (II) modeset(0): Modeline "720x400"x70.1   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[   186.198] (II) modeset(0): Output HDMI-1 connected
[   186.198] (II) modeset(0): Using exact sizes for initial modes
[   186.198] (II) modeset(0): Output HDMI-1 using initial mode 3840x2160 +0+0

 

I am try FHD monitor (1080p) and HD TV (720p)- same result (in logs all OK, but no image on screen).

 

So I think the problem is in my rock pi 4 c hardware.

 

Sorry for the inconvenience.

Link to comment
Share on other sites

  • 0

Hello,

I'm posting here hoping to get a response :)

 

Context :

 

I currently have my Helios64 server running on Armbian 22.02.1. I have several services (in total 21 Docker Containers) including Jellyfin to watch movies (only 1080p - H264).

Currently, I'm sending the video stream to my chomecast connected to my Salon TV. It sometimes happens (for certain film releases) that reading is impossible (freeze), the CPU is then at 100% utilization. I use hardware acceleration (VAAPI) for transcoding but it doesn't seem enough sometimes

 

So I wonder can i use your solution "ROCKCHIP-LEGACY MULTIMEDIA INTEGRATION" to play my movies directly on my TV via HDMI ? Will I lose my already functional services?

 

If one evening, I decide to watch a movie, so I start on the desktop :

  1. Will my other services still be able to run in the background?
  2. Will the reading performance be better ?

 

Thank you for all your details :)

 

Flolm

Edited by Flolm
Link to comment
Share on other sites

  • 0
18 hours ago, Flolm said:

I currently have my Helios64 server running on Armbian 22.02.1.

 

I forgot to specify that I am using the CLI version of Armbian and not desktop.

Link to comment
Share on other sites

  • 0
On 8/4/2022 at 5:29 PM, Flolm said:

Hello,

I'm posting here hoping to get a response :)

 

Context :

 

I currently have my Helios64 server running on Armbian 22.02.1. I have several services (in total 21 Docker Containers) including Jellyfin to watch movies (only 1080p - H264).

Currently, I'm sending the video stream to my chomecast connected to my Salon TV. It sometimes happens (for certain film releases) that reading is impossible (freeze), the CPU is then at 100% utilization. I use hardware acceleration (VAAPI) for transcoding but it doesn't seem enough sometimes

 

So I wonder can i use your solution "ROCKCHIP-LEGACY MULTIMEDIA INTEGRATION" to play my movies directly on my TV via HDMI ? Will I lose my already functional services?

 

If one evening, I decide to watch a movie, so I start on the desktop :

  1. Will my other services still be able to run in the background?
  2. Will the reading performance be better ?

 

Thank you for all your details :)

 

Flolm

First of all, for this multimedia integration to work, you need to be running the legacy kernel (4.4.x). You don't specify which kernel you are running.

Second, AFAIK the only option to make HW encoding to work is gstreamer. This solution will install the required gstreamer plugin (see first post). But Jellyfin uses ffmpeg, so it is difficult that you can make it work with gstreamer, without editing the code and recompiling. Maybe another option is using a wrapper script that uses a ffmpeg pipe, and pointing the custom ffmpeg version from Jellyfin menu, but I have never tried something like that.

 

Third, and most important, if you want to post any question, please follow the forum guidelines and provide all the necessary information. 

Link to comment
Share on other sites

  • 0

hi, i have an orangepi 4 lts, but thereis no legacy image of armbian for this board. Orange pi does have their own debian legacy image but it tells me it was unable to locate the package. Is there any way to get the multimedia integration on this board? thanks!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...