AlwinLub

Members
  • Posts

    12
  • Joined

  • Last visited

Reputation Activity

  1. Like
    AlwinLub got a reaction from Willy Moto in CSC Armbian for RK3318/RK3328 TV box boards   
    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!
  2. Like
    AlwinLub got a reaction from jock in CSC Armbian for RK3318/RK3328 TV box boards   
    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.
  3. Like
    AlwinLub got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    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.
  4. Like
    AlwinLub got a reaction from Willy Moto in CSC Armbian for RK3318/RK3328 TV box boards   
    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.
  5. Like
    AlwinLub got a reaction from fabiobassa in CSC Armbian for RK3318/RK3328 TV box boards   
    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.
  6. Like
    AlwinLub got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    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. Like
    AlwinLub got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    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!
  8. Like
    AlwinLub got a reaction from jock in CSC Armbian for RK3318/RK3328 TV box boards   
    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!
  9. Like
    AlwinLub got a reaction from fabiobassa in CSC Armbian for RK3318/RK3328 TV box boards   
    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!
  10. Like
    AlwinLub got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    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.
     
  11. Like
    AlwinLub got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    If you need someone for testing, let me know. I'm happy to test it out.
  12. Like
    AlwinLub got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    I've got my armbianmonitor -u log here, if it helps; http://ix.io/3zGJ. Thanks for the quick reply as always.
     
  13. Like
    AlwinLub reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    Hmm, actually I built an newer image with kernel 5.14 and hirsute and the Lima driver is not playing nice at all.
    I tried both the stock mesa coming with Hirsute and latest development mesa and both of them cause the login screen to appear just as you describe: black screen and the cursor.
    Lima driver is somehow complaining with these lines in dmesg:
    [ 39.136659] [drm:lima_sched_timedout_job [lima]] *ERROR* lima job timeout [ 39.136801] lima ff300000.gpu: fail to save task state from Xorg pid 1654: error task list is full [ 39.136818] lima ff300000.gpu: gp task error int_state=0 status=a so I got to investigate this issue too...
     
    edit: uff... ok it seems that the issue is due to the missing operating points in the device tree. I always fall into every time there is a new kernel