Jump to content

JMCC

Members
  • Posts

    941
  • Joined

  • Last visited

Reputation Activity

  1. Like
    JMCC got a reaction from hartraft in RK3399 Legacy Multimedia Framework   
    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
    Download a Armbian Buster Legacy Desktop image for your board, and install it with the standard Armbian method. 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
    Accelerated GLES/EGL X desktop: No action needed. Accelerated Chromium, with WebGL and video display acceleration: No action needed Desktop video player capable of smooth 4K HEVC-HDR: Use 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". 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.
    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. OpenCL 1.2 support: It will be fully functional, no further action needed. You can download some tests and examples from this link. Kodi 18.9 Leia with full RKMPP+GBM acceleration, 4K-HDR capable: You can start it from LightDM menu as your user account: 


    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 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. 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.
  2. Like
    JMCC reacted to balbes150 in Architecture for adding additional desktop enviromnents, and application groups   
    I tried adding a new configuration to the build system that is (if possible) close to the current set of master branch packages when building a default image with DE XFCE. I checked the native build with this configuration option, the build passes without errors and the images work on P1\M1. If someone has time, please look and check the received configuration, maybe I missed some necessary packages (or added extra ones). Links to package lists for focal and buster.
     
    https://github.com/150balbes/build/tree/armbian-tv-next/config/desktop/buster/environments/xfce/config_default
     
    https://github.com/150balbes/build/tree/armbian-tv-next/config/desktop/focal/environments/xfce/config_default
     
    I plan to send the PR after the other interested developers confirm that the configuration is correct.
  3. Like
    JMCC got a reaction from alsc in HDMI-CEC won't work on Buster Legacy (4.4.213-rockchip64)   
    Arre you talking about the tweaked kernel I linked above? That was just for testing. Now, the relevant changes are merged into the build script. So, if you are still using the testing version, just install a recently built kernel: either build your own debs with the build script, download it from beta, or wait for the next stable release.
     
    The errors you show are not critical, it seems like probably EXT4 debug was enabled on that kernel. If after switching to the official kernel the problem persists, we'll look into it.
  4. Like
    JMCC reacted to balbes150 in RK3399 Legacy Multimedia Framework   
    LE uses its own settings management system (including audio), which consists of many different additional components (these are not components of KODI itself). For Armbian + mediascript, you must first set the necessary settings in the system (if the system supports them, not all settings are possible in Armbian) and then switch to KODI. In Armbian, the KODI application is limited in setting different hardware settings, it uses system settings.
  5. Like
    JMCC got a reaction from pro777 in Mainline VPU   
    I just posted the announcement for the official Armbian Rockchip Legacy Multimedia Framework. As you can see on the announcement, I say that from now on all multimedia work will be done in Mainline.
     
    That means integrating GPU and VPU acceleration into the official Armbian repos. The timeline is for next Armbian release, in February, if possible.
     
    As of today, I am planning to include Kodi and MPV. So if anybody wants to help, it will be much appreciated. 
  6. Like
    JMCC got a reaction from VyacheslavS in RK3399 Legacy Multimedia Framework   
    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
    Download a Armbian Buster Legacy Desktop image for your board, and install it with the standard Armbian method. 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
    Accelerated GLES/EGL X desktop: No action needed. Accelerated Chromium, with WebGL and video display acceleration: No action needed Desktop video player capable of smooth 4K HEVC-HDR: Use 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". 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.
    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. OpenCL 1.2 support: It will be fully functional, no further action needed. You can download some tests and examples from this link. Kodi 18.9 Leia with full RKMPP+GBM acceleration, 4K-HDR capable: You can start it from LightDM menu as your user account: 


    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 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. 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.
  7. Like
    JMCC got a reaction from VyacheslavS in RK3399 Legacy Multimedia Framework   
    New release in the repos:
    Fixed Chromium showing images in indexed color, and other limitations. Fixed OpenCL broken in last update Improved X performance under glamor (by 100%, in gtkperf tests) Fixed rkcamsrc plugin for using the ISP MIPI-CSI camera (ov5647 still needs some kernel work for rk3399). Added the Rockchip RGA library (also enabled in the kernel).
  8. Like
    JMCC got a reaction from NicoD in RK3399 Legacy Multimedia Framework   
    New release in the repos:
    Fixed Chromium showing images in indexed color, and other limitations. Fixed OpenCL broken in last update Improved X performance under glamor (by 100%, in gtkperf tests) Fixed rkcamsrc plugin for using the ISP MIPI-CSI camera (ov5647 still needs some kernel work for rk3399). Added the Rockchip RGA library (also enabled in the kernel).
  9. Like
    JMCC reacted to piter75 in Armbian v21.02   
    @JMCC This should do the trick to fix it for boards in rk3399 family:
    https://github.com/armbian/config/pull/134/files
  10. Like
    JMCC reacted to Werner in Armbian v21.02   
    Yeah. no fancy output this time
  11. Like
    JMCC got a reaction from Werner in RK3288/RK3328 Legacy Multimedia Framework   
    I recently configured the build script to create a Buster Desktop image for all Rockchip boards, so with next Armbian update it should appear in the download page. In the meantime, as @TonyMac32 said, you can download the server image and use "armbian-config" to install the Desktop easily (it's under System -> Default Desktop).
  12. Like
    JMCC got a reaction from TRS-80 in RK3288/RK3328 Legacy Multimedia Framework   
    LOL No, man, I'm not that old!
  13. Like
    JMCC reacted to NicoD in RK3399 Legacy Multimedia Framework   
    I finished the video about the media script. 
    I had a lot of troubles with youtube because I used a few seconds of southpark and I got age restriction 18 years. Youtube doesn't like Southpark clearly. 
    Tried 3 times with different clips. In the end I cut it all out.. Thanks @JMCC for the awsome work. Without your scripts I wouldn't think of using an SBC as main desktop. 
     
  14. Like
    JMCC got a reaction from TonyMac32 in RK3288/RK3328 Legacy Multimedia Framework   
    LOL No, man, I'm not that old!
  15. Like
    JMCC reacted to axzxc1236 in RK3288/RK3328 Legacy Multimedia Framework   
    I am very impressed by how much feature we are getting... WOWIE
    I don't know if anyone has said this to you but you are a legend!
  16. Like
    JMCC got a reaction from Azq2 in RK3288/RK3328 Legacy Multimedia Framework   
    IT'S FINALLY HERE...

    THE OFFICIAL ROCKCHIP-LEGACY MULTIMEDIA INTEGRATION
     
    After two years of using a separate script to enable the multimedia features in RK3288/3328 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
    Download a Armbian Buster Legacy Desktop image for your board, and install it with the standard Armbian method. Install the complete multimedia solution with sudo apt update && sudo apt upgrade sudo apt install media-buster-legacy-tinkerboard --install-recommends ## Or ## sudo apt install media-buster-legacy-rk3328 --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
    Accelerated GLES/EGL X desktop: No action needed. Accelerated Chromium, with WebGL and video display acceleration: No action needed Desktop video player capable of smooth 4K HEVC-HDR: Use 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". 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. ISP Camera with real-time h.264/1080p HW encoding (RK3288 only): 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. OpenCL 1.2 support (RK3288 only): It will be fully functional, no further action needed. You can download some tests and examples from this link. Kodi 18.9 Leia with full RKMPP+GBM acceleration, 4K-HDR capable: You can start it from Light DM menu as your user account: 
     
    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  
    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. 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.
  17. Like
    JMCC got a reaction from NicoD in RK3399 Legacy Multimedia Framework   
    Try adding the switch --ytdl-format="bestvideo[height<=?720]+bestaudio/best"
     
    More info: https://github.com/mpv-player/mpv/issues/4241
  18. Like
    JMCC got a reaction from NicoD in Buster image - unable to boot RockPi 4 B (1GB) board   
    Good. I am also working on some multimedia kernel-related stuff for legacy RK3399's, I am planning to push the changes very soon too. BTW, I understnad it is conveninet to make a Jira issue for it, because that way it is easier to incorporate it into the changelog, correct?
  19. Like
    JMCC got a reaction from Werner in Buster image - unable to boot RockPi 4 B (1GB) board   
    Good. I am also working on some multimedia kernel-related stuff for legacy RK3399's, I am planning to push the changes very soon too. BTW, I understnad it is conveninet to make a Jira issue for it, because that way it is easier to incorporate it into the changelog, correct?
  20. Like
    JMCC got a reaction from Werner in RK3399 Legacy Multimedia Framework   
    @Werner  @NicoD
    OK, I could not resist, and compiled a test version of the latest RK Xserver. I tested it, and gave me good impression in terms of performance, and also seemed to correct some old bugs that appeared when you enabled desktop compositing. However, I cannot tell too well about the performance, because I am using the board connected to a cheap HDMI-USB capture device, on my laptop's screen 
     
    If you want to give it a try, and give some feedback, you can download the packages from here (you need to install these two with "dpkg -i *.deb", and then do "apt -f install" just in case there is some missing dep).
    https://users.armbian.com/jmcc/packages/new-xserver/
  21. Like
    JMCC got a reaction from NicoD in RK3399 Legacy Multimedia Framework   
    @Werner  @NicoD
    OK, I could not resist, and compiled a test version of the latest RK Xserver. I tested it, and gave me good impression in terms of performance, and also seemed to correct some old bugs that appeared when you enabled desktop compositing. However, I cannot tell too well about the performance, because I am using the board connected to a cheap HDMI-USB capture device, on my laptop's screen 
     
    If you want to give it a try, and give some feedback, you can download the packages from here (you need to install these two with "dpkg -i *.deb", and then do "apt -f install" just in case there is some missing dep).
    https://users.armbian.com/jmcc/packages/new-xserver/
  22. Like
    JMCC got a reaction from NicoD in RK3399 Legacy Multimedia Framework   
    That means it is working 
     
    Let me explain: last update did not change any binaries. It was instead a deep change in how the package installed the libraries, since the "old simple method" that used to work in Stretch and Bionic,  was not working correctly with Buster's ldconfig. So I had to do things "the complicated way", as prescribed by recent Debian packaging rules.
     
    So, before, you were simply not having any acceleration. Hence the errors that some of you posted. Now, you are getting Glamor "acceleration", which gives you the possibility of having GPU accelerated layers (for video play, 3D apps, WebGL, etc.), in exchange for a loss in 2D performance.
     
    Rockchip is now working on a new version of their X server, supporting EXA acceleration, which *should* be better . But I am not sure even how well it works, it would require some investigation. 
  23. Like
    JMCC got a reaction from Werner in RK3399 Legacy Multimedia Framework   
    That means it is working 
     
    Let me explain: last update did not change any binaries. It was instead a deep change in how the package installed the libraries, since the "old simple method" that used to work in Stretch and Bionic,  was not working correctly with Buster's ldconfig. So I had to do things "the complicated way", as prescribed by recent Debian packaging rules.
     
    So, before, you were simply not having any acceleration. Hence the errors that some of you posted. Now, you are getting Glamor "acceleration", which gives you the possibility of having GPU accelerated layers (for video play, 3D apps, WebGL, etc.), in exchange for a loss in 2D performance.
     
    Rockchip is now working on a new version of their X server, supporting EXA acceleration, which *should* be better . But I am not sure even how well it works, it would require some investigation. 
  24. Like
    JMCC reacted to rna in Install Box86 on Arm64   
    Dear All,
    I just want to make a Tutorial on my successful attempt in Installing Box86 on Arm64 and Install Wine X86 apps. In this example it is Sketchup 7.1 and Sketchup 8
    But before starting I want to thanks to PtitSeb for his hard work to bring this dream into reality (running x86 apps on arm64 box).
    My system is X96 Max+ S905x3. I used @balbes150 older image to boot to Armbian, many thanks for him. So In general every box running Armbian 64bit should work.

    This tutorial will use debootstrap Debian Buster Armhf as base for chroot. The keyword is "Arm64" support "Armhf", therefore you do not need to use Qemu or Binfmt_misc as it is very slow. Here's my report on Manjaro Arm Forum: https://archived.forum.manjaro.org/t/x86-64-chroot-on-manjaro-arm-install-x86-64-deb-install-wine-windows-apps/150420/103

    Here's what you need:
    1. Open terminal, then type:
    sudo apt install schroot debootstrap sudo mkdir /srv/chroot sudo mkdir /srv/chroot/debian-armhf sudo debootstrap --arch armhf --foreign buster /srv/chroot/debian-armhf http://debian.xtdv.net/debian sudo chroot "/srv/chroot/debian-armhf" /debootstrap/debootstrap --second-stage 2. Then add a config file for debian-armhf:
    sudo nano /etc/schroot/chroot.d/debian-armhf.conf Copy paste this code, and change <username> into your computer username
    [debian-armhf] description=Debian Armhf chroot aliases=debian-armhf type=directory directory=/srv/chroot/debian-armhf profile=desktop personality=linux preserve-environment=true root-users=<username> users=<username> 3. Then edit the nssdatabases
    sudo nano /etc/schroot/desktop/nssdatabases copy paste this code
    # System databases to copy into the chroot from the host system. # # <database name> #passwd shadow #group gshadow services protocols #networks #hosts #user 4. Edit the stateoverride, and change the first contrab to root
    sudo nano /srv/chroot/debian-armhf/var/lib/dpkg/statoverride copy paste this code
    root root 2755 /usr/bin/crontab 5. Now you should be able to schroot by typing
    sudo schroot -c debian-armhf 6. edit the bashrc
    nano ~/.bashrc add this code to the bottom of the line
    export LANGUAGE="C" export LC_ALL="C" export DISPLAY=:0 7. let's restart chroot environment by exit and login again, then add a username that is similar to your main system username
    exit id sudo schroot -c debian-armhf adduser <username> su - <username> then again add bashrc
    nano ~/.bashrc again add this code to the bottom of the line
    export LANGUAGE="C" export LC_ALL="C" export DISPLAY=:0 8. Then restart chroot by double exit and login again, then install the following package
    exit exit sudo schroot -c debian-armhf apt update && apt upgrade apt install git wget cmake build-essential python3 apt install gcc-arm-linux-gnueabihf 9. Now let's compile the Box86 within Chroot environment
    git clone https://github.com/ptitSeb/box86 cd box86 mkdir build; cd build; cmake .. -DARM_DYNAREC=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo; make exit 10. Now login to chroot again then download wine from twisteros: https://twisteros.com/wine.tgz then extract it to your home folder. Your extracted wine location should be in: ~/wine/bin/wine
    sudo schroot -c debian-armhf wget https://twisteros.com/wine.tgz tar zxvf wine.tgz  11. Install Zenity in chroot environment, as wine will not have window without it:
    apt install zenity 12. Exit from chroot environment by typing
    exit 13. To install a windows app, in this case sketchup 7.1 and 8 you can download it from: http://www.oldversion.com/windows/google-sketchup/ then type:
    schroot -c debian-armhf ~/box86/build/box86 ~/wine/bin/wine 'your/installation/folder/It/is/better/to/drag/and/drop/the/installer' 14. To run the installed program you can type this or make it as a shortcut from desktop launcher:
    schroot -c debian-armhf ~/box86/build/box86 ~/wine/bin/wine your/installed/program/location  
    and here's my final sketchup running smoothly on LLVM Pipe Graphics. I also attached the Box86 running on Manjaro Arm with the good performance as well for addition.

    To be honest, I didn't expect the performance to be this good. It almost remind me of "Rosetta 2" of Apple Silicon, but it is open source.

    Big respect for PtitSeb for bringing this magic to the Arm64 World. I also want to thanks to Xabbu and Lolix from Manjaro Forum to help me figuring out the chroot environment in my older Manjaro Forum Post.
     
    Hope that helps,
     
    Many Thanks,
    rna
     



     

     

     

     
     
    UPDATE 1
    *IMPORTANT NOTE:
    To fix Sketchup 7/8 OpenGL Display Error:
    You have to edit the wine regedit and change the sketchup display setting from "0" to "1"
    - Open Sketchup then close
    - Open terminal then run regedit by typing:
    schroot -c debian-armhf ~/box86/build/box86 ~/wine/bin/wine regedit - Then find:
       HKEY_CURRENT_USER\Software\Google\SketchUp7\GLConfig\Display
    - Then change the “HW_OK” from “0” to “1”
    - Then close your regedit
    - Then open Sketchup 7/8. Now you should be ok.

    UPDATE 2
    you can also follow the Box86 compatibility list here:
    https://github.com/ptitSeb/box86-compatibility-list/issues
    You can also use winetricks to install some dependency, like .NET 4.0 as detailed by WheezyE here:
    https://github.com/ptitSeb/box86-compatibility-list/issues/46
    In fact, by using WheezyE method I was able to install all depencencies to install sketchup 2014 successfully from winetricks in Armbian Reforge (Just to let you know that Armbian Reforge is embedded with Box86 by default).
     
    However, at the moment winetricks does not works in our chroot method. Therefore, Help would be appreciated.

    BONUS:
    For those of you that desperately want to install blender 2.79 on Armbian Focal / Manjaro, you can use this method.
    Open terminal, then type:
    sudo schroot -c debian-armhf apt install blender exit Now to open blender, you can use this command (you can also make launcher):
    schroot -c debian-armhf blender Now Blender 2.79b should run perfectly on you system
     
  25. Like
    JMCC got a reaction from Werner in HDMI-CEC won't work on Buster Legacy (4.4.213-rockchip64)   
    It's OK, nanopct4 has rk3399 kernel. It is good to know that it only needs kernel configs to be enabled, unlike the rockpi and rockpro64 that needed DT patches in the rockchip64 kernel

    Enviado desde mi moto g(6) plus mediante Tapatalk

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines