Jump to content


  • Posts

  • Joined

  • Last visited

  1. A couple of days have passed since my last post, and i must say, congrats @jock on your awesome work. The build is running smoothly without any hiccups or other noteworthy bugs. After optimizing my Kivy app a bit more, the whole interface runs at a steady 60-120 fps. I'm currently researching hardware accelerated video encoding to make the whole show complete (but, as you may have guessed, i know nothing about). I've read about the 'Rockchip-linux' github repositories, but it seems like it's waaay out of my league, but i will try to make the best of it as i continue to learn. HDMI audio didn't work right out of the box, you'll have to switch the default ALSA output (since the card gets recognized just fine) Edit (or create) /etc/asound.conf and insert the following: defaults.pcm.card 2 defaults.ctl.card 2 Reboot the box (or restart apps using audio output) and voilà. If that does not work, try searching for your 'HDMI' card using 'aplay --list-devices' and replace the number '2' with the one of your desired output.
  2. First things first; i haven't experienced any panics, crashes or other similar bugs. The new image runs smoothly as far as i can tell. Seondly; Kivy finally *bleep* works. After compiling 20+ builds with different configurations, throwing the tv off the wall, buying a new tv and starting all over again, i found out that the issue was to do with Mesa not playing nice with the anti-aliasing Kivy applied, which resulted in a black screen. It still runs at 10-15 fps, but i think that's due to this build of Kivy being built with OpenGL instead of OpenGL ES, so i'm currently in the process of building Kivy with GLES support. At least we're making progress and i can't thank you guys enough for thinking this trough with me (or actually 'for me'). So for anyone who happens to come across this post with the same problem, set the 'multisamples' in the 'graphics' config to '0' like this (which may or may not help for you): EDIT: After building Kivy with OpenGL ES support, the whole ui works smoothly at around 30 - 70fps. Have a good weekend!
  3. If you need someone for testing, let me know. I'm happy to test it out.
  4. Thanks for the correction. I've generated a new log, http://ix.io/3zQZ Edit; I also got my Xorg log here, but i didn't see anything interesting.
  5. I've got my armbianmonitor -u log here, if it helps; http://ix.io/3zGJ. Thanks for the quick reply as always.
  6. After doing a fresh install and only installing Kivy, it recognizes the OpenGL renderer as 'llvmpipe', so no hardware acceleration. But as soon as i install Xorg, it correctly sets 'Mali450' as renderer, but the screen goes black with only a cursor showing. I'm personally getting the feeling that Kivy does not play nice with this version of Mesa (20.3.5).
  7. I did some research on how to install the proprietary drivers, but it's quite hard to get in to for developers like me who are more used to the high-level stuff (python, lamp stack). There is info out there but it's too complicated for my simple brain. I've also tried running the kivy build script with and without OpenGL ES, Wayland and X11 without any improvement. I've even tried using OpenGL Kivy with GL4ES without any result (it doesn't get recognized by Kivy). I would like to help out wherever i can because i feel projects like Armbian are simply quite amazing. Thanks again for your help and your awesome builds, i'm really looking forward to using the updated images with the newer Mesa library and crossing my fingers somebody smarter than me comes up with a solution, or that the updated images will 'just work' with Kivy. On the Legacy kernel images with GL4ES, it runs at 60-80 fps without any (noticeable) dips. Kivy exclusively uses OpenGL/OpenGL ES to render the interface.
  8. I've got my board running at 1.3 Ghz with the legacy kernel. When pushing the hardware (by compiling or letting the CPU sit at 100%) the temperatures would regularly hit 80-90 degrees celsius, which i'm not very comfy with. With the new image, it's sitting at 1Ghz (via armbian-config) with max 70-75 degrees under heavy load. I could install a bigger heatsink, but as you said, the RK3318 is a sketchy chip.
  9. I've tested your build on the little HK1 Max, and it works like a charm. I've left it running for about 10 hours without any hiccups. There is however one problem, my Kivy app recognizes the Mali and Mesa libraries, but it will only show a black screen under X, Wayland and headless (sdl2) mode. Weston works like a charm and i can move windows smoothly, and they will fade smoothly upon opening and closing. I've noticed that while using weston, there was no (noticeable) screen tearing. When i try to open the Kivy-app in headless mode (running from the command line directly) it only shows a black screen with a cursor. The app will open without Open GL ES under X11, but i'll only get 2-10 fps because it uses llvm instead of Mali450 as renderer. As i suspect this is an issue with Kivy, i've already posted a topic via the Kivy Discord-channel, and i'm now waiting for a reply. Kivy log: I've also noticed that while running setup.py, kivy will search for the following files when it detects Mesa: mali_paths = ( '/usr/lib/arm-linux-gnueabihf/libMali.so', '/usr/lib/arm-linux-gnueabihf/mali-egl/libmali.so', '/usr/local/mali-egl/libmali.so') None of these files exist and i don't know if this could be the possible issue. Thanks again for taking your time with me.
  10. I've downloaded the mainline image you've built for Wester_Minsk. I will try it tonight. I've seen people getting rid of screen tearing using weston since some say it's more optimized than X11 ever was (i can't confirm this, but it's worth a try). For a little context on the screen tearing: I'm developing a Kivy app for advanced multimedia features (like Spotify Connect, IPTV playback, remote playback from the box via other devices) all built in a single app. It already is a very complex interface, but it's running great at 60-120 fps, but the tearing throws me off when quickly animating objects. It's using gl4es and it seems hardware accelerated because without gl4es it runs at about 5-20fps. Thanks again for your quick reply and help. I'll keep you posted!
  11. I've got a HK1 Max with a RK3318 (ordered a 3328, but got a 3318 delivered). X11 works, but it has screen tearing issues. The HDMI output stops completely (as in no signal) when adding a new cvt mode via xrandr. I'm using the build with the supplied drivers, and i was wondering if maybe things will run better under Wayland/Weston. It needs to run a Python Kivy-app with many animations, so screen tearing is not ideal. I have no clue how to install/compile wayland/weston, but i got something running which returns the following error: [15:00:37.291] weston 5.0.0 https://wayland.freedesktop.org Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/ Build: unknown (not built from git or tarball) [15:00:37.292] Command line: weston [15:00:37.296] OS: Linux, 4.4.213-rockchip64, #5 SMP Fri Apr 16 17:25:31 UTC 2021, aarch64 [15:00:37.301] Using config file '/home/user/.config/weston.ini' [15:00:37.304] Output repaint window is 7 ms maximum. [15:00:37.308] Loading module '/usr/lib/aarch64-linux-gnu/libweston-5/drm-backend.so' [15:00:37.333] Failed to load module: /usr/lib/aarch64-linux-gnu/libweston-5/drm-backend.so: undefined symbol: gbm_bo_get_offset [15:00:37.333] fatal: failed to create compositor backend I would really appreciate If somebody would like to point me in the right direction. dmesg output: All modules worked right out of the box; Wi-Fi, HDMI (video and sound), Ethernet and IR. Thank you so much, @jock for all the hard work you've put in to this.
  12. Hello, Software developer (web) from the Netherlands here. Just picked up a "X88 Pro 20" box from AliExpress: Link to AliExpress. I'm wondering if it is any good and if it will run armbian. I've looked at several other SoC's, but this one looked quite nice, especially at this price point (49 euros). I needed a bit more GPU power and RAM because i'm planning to do a electron (chromium+node.js) based home control app for the thing. If somebody got armbian working with some features (hardware acceleration is quite important), i would be thankful if you would like to share your thoughts and methods on how to install it since i'm (very) new to this whole SoC/SoB thing. I've just placed my order and it will arrive in about 4-10 days. I am always happy to test builds for it. Thanks so much, and have a nice week. - Alwin
  • Create New...