Jump to content

JMCC

Members
  • Posts

    941
  • Joined

  • Last visited

Posts posted by JMCC

  1. 3 hours ago, Дмитрий Батин said:

    Do you have any manual, that can help us to get it ?

    Hello! In the first post, you have links to all the sources, most of them from my GitHub repos. The procedure might be outdated, though, I haven't touched it since 2019.

     

    For Kodi, you can try the rockchip branch for legacy kernel, or the mainline branch for current. Compilation instructions are included in the repo. Good luck!

  2. 19 hours ago, MadEDoctor said:

    I am unable to boot any OS different from VMware (arm version) and RISC OS

    Well, I don't even own a RPi, but here are some suggestions:

    • You mention several OS'es, but not Armbian. Have you tried Armbian? If not, that would be the first thing to do, specially since you asked here :)
    • In your video, you show RISC OS, and apparently it is running a armv7 version. Could it be that 32-bit ARM OS's are working, but 64-bit are not? If this is the issue, then maybe you can try to build 32-bit Armbian image and see if it works.
    • It could also be a device tree issue. Maybe you can extract the DTB from some of the OS's that are working, and try to use it with an Armbian image.
  3. 6 hours ago, Handy Doctor said:

    None works. If lucky, some would boot into GUI

    Do you have emmc or only SD card? Renegade legacy images don't get along well with SD cards (it was a problem with regulator voltages, and didn't affect all units). For example, mine worked only with certain older legacy images on SD card, but it broke somewhere around early 2019.

     

    So do you have emmc? If so, the easiest is boot the board from a current image, and then flash legacy from it into emmc. I can teach you how to do that

     

    If you don't have emmc, please try this image: https://armbian.tnahosting.net/archive/renegade/archive/Armbian_5.75_Renegade_Ubuntu_bionic_default_4.4.174.7z , and use the old multimedia script instead (DO NOT upgrade the kernel, use "apt-mark hold"):

     

  4. On 1/26/2023 at 4:49 PM, Salvo Nice said:

    I have a RockPi 4c + which has this variant. But I also noticed that legacy Armbian is not available for this board, maybe I have to build it myself

    Sorry, I don't have that board and have not tested the framework on it. Maybe you can build an image and try.

  5. 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. 

  6. 19 hours ago, jock said:

    I may send you those things

    Sure, you can PM them to me, please.

     

    On a side note, I finally got to re-flash some image to my TV box, using a usb-c to usb-a cable on my laptop. This one seems to make the box run a bit hotter and maybe faster, I will try to investigate whether memory is clocked at 666MHz or not.

    [EDIT: No, all dmc opp's 400MHz and above are disabled. But the CPU opp at 1104MHz is runnig at a voltage of 1275/1275/1350, hence the heat. This is crazy...]

  7. On 7/12/2022 at 1:01 PM, jock said:

    Sorry for the bad experience 😥

    No prob, I was counting on the possibility of bricking it, but it was just a 20€ crappy device laying around. And it is not bricked after all, yet it works faster than factory with Armbian, and even have WiFi, which I didn't expect 😆

    I'm on vacation and I don't have any USB-OTG cable here, so I cannot use the RK flashing tool. There is an option to create an "upgrade SD card", but it only supports cards up to 16GB, not bigger (WTH?), and also requires a reset button which seems not to be present on the device.

     

    This also motivates me to spend some time finishing the media integration for Mainline, so I can at least use Kodi on this 😄

     

  8. @jock Thanks for the info. On a side note, I found a small bug: when making the emmc backup, if the resulting file is bigger than 4Gb it will just stop there (because of the FAT size limit) and you will get a broken backup.

     

    Probably could be solved by splitting the backup, for example along these lines:

    # Split backup in 2Gb parts, with two-character suffixes
    dd if=/dev/mmcblk1 | gzip -c | split -b 2000m - tvbox-backup.img.gz.
    
    # Restore the backup
    cat tvbox-backup.img.gz.* | gzip -dc | dd of=/dev/mmcblk1
    
    

     

  9. @jock I got some X88 pro 10 laying around, and tried your solution. It works great, I was able to boot from the multitool, and flash Armbian to the emmc. However, I am wondering if there is any possibility to keep the original Android on the emmc, and boot Armbian when plugged on a SD card/USB.

     

    After all, if it can boot the multitool with the original firmware on emmc, there must be some way to boot the full Armbian image, right? Maybe an issue with Mainline U-Boot, and you are using BSP u-boot for the multitool?

  10. 5 hours ago, Evan Langlois said:

    I see Focal and Bullseye, no Buster for download on official Armbian site.  Both are using kernel 5.15, so I assume mainline.  Has all this been incorporated into the mainline/bullseye build, or do I need to track down a buster image from someplace?

    You don't specify your board, but for example, if you scroll all the way down on this page, you will see the Buster Default Desktop image for download: https://www.armbian.com/nanopc-t4/

  11. 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/*

  12. 13 hours ago, Chris4arm said:

     

     

    Hi,

    am I alone to (try to) use a Station M1 under Armbian ?

     

    Chris

    I use the M1 with Armbian Buster and the Default (Legacy) kernel, and it works mostly fine except for Bluetooth. I know that some people find it more exciting to use the Mainline kernel, but for me Default/Legacy works better

  13. 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.

  14. 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"?

  15. Moved to P2P help, since it is not a RK3399-specific issue, nor a bug.

     

    2 hours ago, FredrikA said:

    export DISPLAY=localhost:10.0

    How are you connecting from your Windows machine? If you are using putty, it will work without setting this env variable, since putty will make its own proxy (in fact, this variable will break it). If you are using Window's built-in ssh client, then you need to do the config on the Windows side.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines