Ben N Voutour Posted September 22, 2021 Posted September 22, 2021 (edited) 7 hours ago, jock said: I didn't see any overclocked dtb file here around... however I'm not really fond of overclocking for these chips: they already are scrap parts that somehow reach the nominal frequencies. Some of the rk3318 boxes are also downclocked by manufacturers to 1.1 Ghz to be stable, overclocking is not something I would really love about. It's already hard to get the things together and make the board working stable enough. Adding another big source of instability... hmm I don't think it is a wise idea. it was in the google drive from the dms mod rom mine seems stable at 1.3 GHz but i want to test if it can go to 1.5 GHz. the overclock is more than just the cpu, it is also the ram clock so the cpu in theory should be able to hit 1.5 GHz and the memory should also be able to hit 1066 MHz without any major issues up front. in android the power limit is 5v 1.1a at idle i am using a 5v 4a power brick and it seems rock solid. look for the v3a rom from 4pda and get the dtb file if you can. (H96 MAX ?RK3318 Android 9) made by DMSSRU and it is called DMS Mod Edited September 22, 2021 by RetroFan90 typo 0 Quote
AlwinLub Posted September 22, 2021 Posted September 22, 2021 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). 1 Quote
jock Posted September 22, 2021 Author Posted September 22, 2021 2 hours ago, AlwinLub said: 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). 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 2 Quote
AlwinLub Posted September 22, 2021 Posted September 22, 2021 2 hours ago, jock said: 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 I've got my armbianmonitor -u log here, if it helps; http://ix.io/3zGJ. Thanks for the quick reply as always. 1 Quote
Ben N Voutour Posted September 24, 2021 Posted September 24, 2021 On 9/22/2021 at 4:43 PM, AlwinLub said: I've got my armbianmonitor -u log here, if it helps; http://ix.io/3zGJ. Thanks for the quick reply as always. set your boot settings so that verbosity=1 is verbosity=7 and then run armbianmonitor -u and upload that. 0 Quote
Ben N Voutour Posted September 24, 2021 Posted September 24, 2021 Just now, RetroFan90 said: set your boot settings so that verbosity=1 is verbosity=7 and then run armbianmonitor -u and upload that. https://docs.armbian.com/User-Guide_Fine-Tuning/ 0 Quote
AlwinLub Posted September 24, 2021 Posted September 24, 2021 10 hours ago, RetroFan90 said: https://docs.armbian.com/User-Guide_Fine-Tuning/ 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. Spoiler [ 592.157] X.Org X Server 1.20.11 X Protocol Version 11, Revision 0 [ 592.158] Build Operating System: linux Debian [ 592.158] Current Operating System: Linux rk3318-box 5.10.64-rockchip64 #trunk SMP PREEMPT Tue Sep 14 13:49:15 UTC 2021 aarch64 [ 592.158] Kernel command line: root=UUID=2df618ba-f178-4f71-b960-6c3d3e7d27f2 rootwait rootfstype=ext4 bootsplash.bootfile=bootsplash.armbian console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=7 ubootpart=098367f1-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 [ 592.158] Build Date: 13 April 2021 04:07:31PM [ 592.158] xorg-server 2:1.20.11-1 (https://www.debian.org/support) [ 592.159] Current version of pixman: 0.40.0 [ 592.159] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 592.159] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 592.159] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Sep 24 16:53:47 2021 [ 592.161] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 592.162] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 592.163] (==) No Layout section. Using the first Screen section. [ 592.163] (==) No screen section available. Using defaults. [ 592.163] (**) |-->Screen "Default Screen Section" (0) [ 592.163] (**) | |-->Monitor "<default monitor>" [ 592.164] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 592.165] (**) Option "BlankTime" "0" [ 592.165] (**) Option "StandbyTime" "0" [ 592.165] (**) Option "SuspendTime" "0" [ 592.165] (**) Option "OffTime" "0" [ 592.165] (==) Automatically adding devices [ 592.165] (==) Automatically enabling devices [ 592.165] (==) Automatically adding GPU devices [ 592.165] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 592.166] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 592.166] Entry deleted from font path. [ 592.166] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 592.166] (==) ModulePath set to "/usr/lib/xorg/modules" [ 592.166] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 592.166] (II) Loader magic: 0xaaaac3260e28 [ 592.166] (II) Module ABI versions: [ 592.166] X.Org ANSI C Emulation: 0.4 [ 592.166] X.Org Video Driver: 24.1 [ 592.166] X.Org XInput driver : 24.1 [ 592.166] X.Org Server Extension : 10.0 [ 592.173] (--) using VT number 2 [ 592.173] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 592.178] (II) xfree86: Adding drm device (/dev/dri/card0) [ 592.192] (II) xfree86: Adding drm device (/dev/dri/card1) [ 592.194] (II) no primary bus or device found [ 592.194] falling back to /sys/devices/platform/display-subsystem/drm/card0 [ 592.194] (II) LoadModule: "glx" [ 592.195] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 592.201] (II) Module glx: vendor="X.Org Foundation" [ 592.202] compiled for 1.20.11, module version = 1.0.0 [ 592.202] ABI class: X.Org Server Extension, version 10.0 [ 592.202] (==) Matched modesetting as autoconfigured driver 0 [ 592.202] (==) Matched fbdev as autoconfigured driver 1 [ 592.202] (==) Assigned the driver to the xf86ConfigLayout [ 592.202] (II) LoadModule: "modesetting" [ 592.202] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 592.203] (II) Module modesetting: vendor="X.Org Foundation" [ 592.203] compiled for 1.20.11, module version = 1.20.11 [ 592.203] Module class: X.Org Video Driver [ 592.203] ABI class: X.Org Video Driver, version 24.1 [ 592.204] (II) LoadModule: "fbdev" [ 592.204] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [ 592.205] (II) Module fbdev: vendor="X.Org Foundation" [ 592.205] compiled for 1.20.0, module version = 0.5.0 [ 592.205] Module class: X.Org Video Driver [ 592.205] ABI class: X.Org Video Driver, version 24.0 [ 592.205] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 592.205] (II) FBDEV: driver for framebuffer: fbdev [ 592.257] (II) modeset(0): using drv /dev/dri/card0 [ 592.258] (WW) Falling back to old probe method for fbdev [ 592.258] (II) Loading sub module "fbdevhw" [ 592.258] (II) LoadModule: "fbdevhw" [ 592.258] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [ 592.259] (II) Module fbdevhw: vendor="X.Org Foundation" [ 592.259] compiled for 1.20.11, module version = 0.0.2 [ 592.259] ABI class: X.Org Video Driver, version 24.1 [ 592.261] (II) modeset(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 592.261] (==) modeset(0): Depth 24, (==) framebuffer bpp 32 [ 592.262] (==) modeset(0): RGB weight 888 [ 592.262] (==) modeset(0): Default visual is TrueColor [ 592.262] (II) Loading sub module "glamoregl" [ 592.262] (II) LoadModule: "glamoregl" [ 592.262] (II) Loading /usr/lib/xorg/modules/libglamoregl.so [ 592.287] (II) Module glamoregl: vendor="X.Org Foundation" [ 592.287] compiled for 1.20.11, module version = 1.0.1 [ 592.287] ABI class: X.Org ANSI C Emulation, version 0.4 [ 593.068] (II) modeset(0): glamor X acceleration enabled on Mali450 [ 593.069] (II) modeset(0): glamor initialized [ 593.185] (II) modeset(0): Output HDMI-1 has no monitor section [ 593.298] (II) modeset(0): EDID for output HDMI-1 [ 593.298] (II) modeset(0): Manufacturer: SAM Model: 7c5 Serial#: 1 [ 593.298] (II) modeset(0): Year: 2010 Week: 46 [ 593.298] (II) modeset(0): EDID Version: 1.3 [ 593.298] (II) modeset(0): Digital Display Input [ 593.298] (II) modeset(0): Max Image Size [cm]: horiz.: 121 vert.: 68 [ 593.298] (II) modeset(0): Gamma: 2.20 [ 593.298] (II) modeset(0): No DPMS capabilities specified [ 593.298] (II) modeset(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 [ 593.298] (II) modeset(0): First detailed timing is preferred mode [ 593.298] (II) modeset(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600 [ 593.298] (II) modeset(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329 [ 593.298] (II) modeset(0): Supported established timings: [ 593.298] (II) modeset(0): 720x400@70Hz [ 593.298] (II) modeset(0): 640x480@60Hz [ 593.298] (II) modeset(0): 640x480@67Hz [ 593.298] (II) modeset(0): 640x480@72Hz [ 593.298] (II) modeset(0): 640x480@75Hz [ 593.298] (II) modeset(0): 800x600@60Hz [ 593.299] (II) modeset(0): 800x600@72Hz [ 593.299] (II) modeset(0): 800x600@75Hz [ 593.299] (II) modeset(0): 832x624@75Hz [ 593.299] (II) modeset(0): 1024x768@60Hz [ 593.299] (II) modeset(0): 1024x768@70Hz [ 593.299] (II) modeset(0): 1024x768@75Hz [ 593.299] (II) modeset(0): 1280x1024@75Hz [ 593.299] (II) modeset(0): 1152x864@75Hz [ 593.299] (II) modeset(0): Manufacturer's mask: 0 [ 593.299] (II) modeset(0): Supported standard timings: [ 593.299] (II) modeset(0): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337 [ 593.299] (II) modeset(0): #1: hsize: 1280 vsize 800 refresh: 60 vid: 129 [ 593.299] (II) modeset(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513 [ 593.299] (II) modeset(0): #3: hsize: 1280 vsize 1024 refresh: 60 vid: 32897 [ 593.299] (II) modeset(0): #4: hsize: 1440 vsize 900 refresh: 60 vid: 149 [ 593.299] (II) modeset(0): #5: hsize: 1440 vsize 900 refresh: 75 vid: 3989 [ 593.299] (II) modeset(0): #6: hsize: 1680 vsize 1050 refresh: 60 vid: 179 [ 593.299] (II) modeset(0): #7: hsize: 1600 vsize 1200 refresh: 60 vid: 16553 [ 593.299] (II) modeset(0): Supported detailed timing: [ 593.299] (II) modeset(0): clock: 148.5 MHz Image Size: 160 x 90 mm [ 593.299] (II) modeset(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0 [ 593.299] (II) modeset(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0 [ 593.299] (II) modeset(0): Supported detailed timing: [ 593.299] (II) modeset(0): clock: 85.5 MHz Image Size: 160 x 90 mm [ 593.299] (II) modeset(0): h_active: 1360 h_sync: 1424 h_sync_end 1536 h_blank_end 1792 h_border: 0 [ 593.299] (II) modeset(0): v_active: 768 v_sync: 771 v_sync_end 777 v_blanking: 795 v_border: 0 [ 593.299] (II) modeset(0): Ranges: V min: 24 V max: 75 Hz, H min: 26 H max: 81 kHz, PixClock max 235 MHz [ 593.299] (II) modeset(0): Monitor name: SAMSUNG [ 593.300] (II) modeset(0): Supported detailed timing: [ 593.300] (II) modeset(0): clock: 148.5 MHz Image Size: 160 x 90 mm [ 593.300] (II) modeset(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0 [ 593.300] (II) modeset(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0 [ 593.300] (II) modeset(0): Supported detailed timing: [ 593.300] (II) modeset(0): clock: 74.2 MHz Image Size: 160 x 90 mm [ 593.300] (II) modeset(0): h_active: 1280 h_sync: 1720 h_sync_end 1760 h_blank_end 1980 h_border: 0 [ 593.300] (II) modeset(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0 [ 593.300] (II) modeset(0): Supported detailed timing: [ 593.300] (II) modeset(0): clock: 74.2 MHz Image Size: 160 x 90 mm [ 593.300] (II) modeset(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0 [ 593.300] (II) modeset(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0 [ 593.300] (II) modeset(0): Number of EDID sections to follow: 1 [ 593.300] (II) modeset(0): EDID (in hex): [ 593.300] (II) modeset(0): 00ffffffffffff004c2dc50701000000 [ 593.300] (II) modeset(0): 2e140103807944780aee91a3544c9926 [ 593.300] (II) modeset(0): 0f5054bdef80714f8100814081809500 [ 593.300] (II) modeset(0): 950fb300a940023a801871382d40582c [ 593.300] (II) modeset(0): 4500a05a0000001e662150b051001b30 [ 593.300] (II) modeset(0): 40703600a05a0000001e000000fd0018 [ 593.300] (II) modeset(0): 4b1a5117000a202020202020000000fc [ 593.300] (II) modeset(0): 0053414d53554e470a20202020200126 [ 593.300] (II) modeset(0): 020332f14b901f041305140312202122 [ 593.301] (II) modeset(0): 2309070783010000e2000fe305030172 [ 593.301] (II) modeset(0): 030c001000b82d20d0080140073f4050 [ 593.301] (II) modeset(0): 90a0023a80d072382d40102c4580a05a [ 593.301] (II) modeset(0): 0000001e011d00bc52d01e20b8285540 [ 593.301] (II) modeset(0): a05a0000001e011d80d0721c1620102c [ 593.301] (II) modeset(0): 2580a05a0000009e0000000000000000 [ 593.301] (II) modeset(0): 000000000000000000000000000000b8 [ 593.301] (--) modeset(0): HDMI max TMDS frequency 225000KHz [ 593.301] (II) modeset(0): Printing probed modes for output HDMI-1 [ 593.301] (II) modeset(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) [ 593.301] (II) modeset(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) [ 593.301] (II) modeset(0): Modeline "1920x1080i"x60.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e) [ 593.301] (II) modeset(0): Modeline "1920x1080i"x50.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e) [ 593.301] (II) modeset(0): Modeline "1920x1080"x30.0 74.25 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (33.8 kHz e) [ 593.301] (II) modeset(0): Modeline "1920x1080"x25.0 74.25 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (28.1 kHz e) [ 593.301] (II) modeset(0): Modeline "1920x1080"x24.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e) [ 593.301] (II) modeset(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) [ 593.301] (II) modeset(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e) [ 593.302] (II) modeset(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) [ 593.302] (II) modeset(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) [ 593.302] (II) modeset(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) [ 593.302] (II) modeset(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [ 593.302] (II) modeset(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) [ 593.302] (II) modeset(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) [ 593.302] (II) modeset(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) [ 593.302] (II) modeset(0): Output HDMI-1 connected [ 593.302] (II) modeset(0): Using exact sizes for initial modes [ 593.302] (II) modeset(0): Output HDMI-1 using initial mode 1920x1080 +0+0 [ 593.302] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0) [ 593.302] (==) modeset(0): DPI set to (96, 96) [ 593.302] (II) Loading sub module "fb" [ 593.302] (II) LoadModule: "fb" [ 593.303] (II) Loading /usr/lib/xorg/modules/libfb.so [ 593.304] (II) Module fb: vendor="X.Org Foundation" [ 593.304] compiled for 1.20.11, module version = 1.0.0 [ 593.304] ABI class: X.Org ANSI C Emulation, version 0.4 [ 593.304] (II) UnloadModule: "fbdev" [ 593.304] (II) Unloading fbdev [ 593.305] (II) UnloadSubModule: "fbdevhw" [ 593.305] (II) Unloading fbdevhw [ 593.497] (==) modeset(0): Backing store enabled [ 593.497] (==) modeset(0): Silken mouse enabled [ 593.508] (II) modeset(0): Initializing kms color map for depth 24, 8 bpc. [ 593.508] (==) modeset(0): DPMS enabled [ 593.509] (II) modeset(0): [DRI2] Setup complete [ 593.509] (II) modeset(0): [DRI2] DRI driver: rockchip [ 593.509] (II) modeset(0): [DRI2] VDPAU driver: rockchip [ 593.509] (II) Initializing extension Generic Event Extension [ 593.510] (II) Initializing extension SHAPE [ 593.511] (II) Initializing extension MIT-SHM [ 593.512] (II) Initializing extension XInputExtension [ 593.513] (II) Initializing extension XTEST [ 593.514] (II) Initializing extension BIG-REQUESTS [ 593.515] (II) Initializing extension SYNC [ 593.516] (II) Initializing extension XKEYBOARD [ 593.517] (II) Initializing extension XC-MISC [ 593.518] (II) Initializing extension SECURITY [ 593.518] (II) Initializing extension XFIXES [ 593.519] (II) Initializing extension RENDER [ 593.520] (II) Initializing extension RANDR [ 593.521] (II) Initializing extension COMPOSITE [ 593.522] (II) Initializing extension DAMAGE [ 593.523] (II) Initializing extension MIT-SCREEN-SAVER [ 593.524] (II) Initializing extension DOUBLE-BUFFER [ 593.524] (II) Initializing extension RECORD [ 593.525] (II) Initializing extension DPMS [ 593.526] (II) Initializing extension Present [ 593.527] (II) Initializing extension DRI3 [ 593.527] (II) Initializing extension X-Resource [ 593.528] (II) Initializing extension XVideo [ 593.529] (II) Initializing extension XVideo-MotionCompensation [ 593.529] (II) Initializing extension SELinux [ 593.529] (II) SELinux: Disabled on system [ 593.529] (II) Initializing extension GLX [ 593.891] (II) AIGLX: Loaded and initialized rockchip [ 593.891] (II) GLX: Initialized DRI2 GL provider for screen 0 [ 593.891] (II) Initializing extension XFree86-VidModeExtension [ 593.892] (II) Initializing extension XFree86-DGA [ 593.893] (II) Initializing extension XFree86-DRI [ 593.893] (II) Initializing extension DRI2 [ 593.899] (II) modeset(0): Damage tracking initialized [ 593.899] (II) modeset(0): Setting screen physical size to 508 x 285 [ 594.206] (II) config/udev: Adding input device adc-keys (/dev/input/event6) [ 594.206] (**) adc-keys: Applying InputClass "libinput keyboard catchall" [ 594.207] (II) LoadModule: "libinput" [ 594.208] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so [ 594.224] (II) Module libinput: vendor="X.Org Foundation" [ 594.224] compiled for 1.20.8, module version = 0.30.0 [ 594.224] Module class: X.Org XInput Driver [ 594.224] ABI class: X.Org XInput driver, version 24.1 [ 594.224] (II) Using input driver 'libinput' for 'adc-keys' [ 594.224] (**) adc-keys: always reports core events [ 594.224] (**) Option "Device" "/dev/input/event6" [ 594.225] (**) Option "_source" "server/udev" [ 594.241] (II) event6 - adc-keys: is tagged by udev as: Keyboard [ 594.241] (II) event6 - adc-keys: device is a keyboard [ 594.242] (II) event6 - adc-keys: device removed [ 594.304] (**) Option "config_info" "udev:/sys/devices/platform/adc-keys/input/input6/event6" [ 594.304] (II) XINPUT: Adding extended input device "adc-keys" (type: KEYBOARD, id 6) [ 594.304] (**) Option "xkb_model" "pc105" [ 594.304] (**) Option "xkb_layout" "us" [ 594.310] (II) event6 - adc-keys: is tagged by udev as: Keyboard [ 594.311] (II) event6 - adc-keys: device is a keyboard [ 594.318] (II) config/udev: Adding input device dw_hdmi (/dev/input/event7) [ 594.318] (**) dw_hdmi: Applying InputClass "libinput keyboard catchall" [ 594.318] (II) Using input driver 'libinput' for 'dw_hdmi' [ 594.318] (**) dw_hdmi: always reports core events [ 594.318] (**) Option "Device" "/dev/input/event7" [ 594.319] (**) Option "_source" "server/udev" [ 594.326] (II) event7 - dw_hdmi: is tagged by udev as: Keyboard Pointingstick [ 594.327] (II) event7 - dw_hdmi: device is a pointer [ 594.327] (II) event7 - dw_hdmi: device is a keyboard [ 594.328] (II) event7 - dw_hdmi: device removed [ 594.360] (II) libinput: dw_hdmi: needs a virtual subdevice [ 594.361] (**) Option "config_info" "udev:/sys/devices/platform/ff3c0000.hdmi/rc/rc0/input7/event7" [ 594.361] (II) XINPUT: Adding extended input device "dw_hdmi" (type: MOUSE, id 7) [ 594.362] (**) Option "AccelerationScheme" "none" [ 594.362] (**) dw_hdmi: (accel) selected scheme none/0 [ 594.362] (**) dw_hdmi: (accel) acceleration factor: 2.000 [ 594.362] (**) dw_hdmi: (accel) acceleration threshold: 4 [ 594.369] (II) event7 - dw_hdmi: is tagged by udev as: Keyboard Pointingstick [ 594.370] (II) event7 - dw_hdmi: device is a pointer [ 594.370] (II) event7 - dw_hdmi: device is a keyboard [ 594.376] (II) config/udev: Adding input device Razer Razer BlackWidow Chroma V2 (/dev/input/event0) [ 594.377] (**) Razer Razer BlackWidow Chroma V2: Applying InputClass "libinput keyboard catchall" [ 594.377] (II) Using input driver 'libinput' for 'Razer Razer BlackWidow Chroma V2' [ 594.377] (**) Razer Razer BlackWidow Chroma V2: always reports core events [ 594.377] (**) Option "Device" "/dev/input/event0" [ 594.377] (**) Option "_source" "server/udev" [ 594.387] (II) event0 - Razer Razer BlackWidow Chroma V2: is tagged by udev as: Keyboard [ 594.387] (II) event0 - Razer Razer BlackWidow Chroma V2: device is a keyboard [ 594.389] (II) event0 - Razer Razer BlackWidow Chroma V2: device removed [ 594.412] (**) Option "config_info" "udev:/sys/devices/platform/ff580000.usb/usb1/1-1/1-1:1.0/0003:1532:0221.0001/input/input0/event0" [ 594.412] (II) XINPUT: Adding extended input device "Razer Razer BlackWidow Chroma V2" (type: KEYBOARD, id 8) [ 594.412] (**) Option "xkb_model" "pc105" [ 594.412] (**) Option "xkb_layout" "us" [ 594.423] (II) event0 - Razer Razer BlackWidow Chroma V2: is tagged by udev as: Keyboard [ 594.423] (II) event0 - Razer Razer BlackWidow Chroma V2: device is a keyboard [ 594.430] (II) config/udev: Adding input device Razer Razer BlackWidow Chroma V2 Keyboard (/dev/input/event1) [ 594.430] (**) Razer Razer BlackWidow Chroma V2 Keyboard: Applying InputClass "libinput keyboard catchall" [ 594.430] (II) Using input driver 'libinput' for 'Razer Razer BlackWidow Chroma V2 Keyboard' [ 594.430] (**) Razer Razer BlackWidow Chroma V2 Keyboard: always reports core events [ 594.431] (**) Option "Device" "/dev/input/event1" [ 594.431] (**) Option "_source" "server/udev" [ 594.441] (II) event1 - Razer Razer BlackWidow Chroma V2 Keyboard: is tagged by udev as: Keyboard [ 594.441] (II) event1 - Razer Razer BlackWidow Chroma V2 Keyboard: device is a keyboard [ 594.443] (II) event1 - Razer Razer BlackWidow Chroma V2 Keyboard: device removed [ 594.468] (**) Option "config_info" "udev:/sys/devices/platform/ff580000.usb/usb1/1-1/1-1:1.1/0003:1532:0221.0002/input/input1/event1" [ 594.468] (II) XINPUT: Adding extended input device "Razer Razer BlackWidow Chroma V2 Keyboard" (type: KEYBOARD, id 9) [ 594.468] (**) Option "xkb_model" "pc105" [ 594.468] (**) Option "xkb_layout" "us" [ 594.479] (II) event1 - Razer Razer BlackWidow Chroma V2 Keyboard: is tagged by udev as: Keyboard [ 594.479] (II) event1 - Razer Razer BlackWidow Chroma V2 Keyboard: device is a keyboard [ 594.486] (II) config/udev: Adding input device Razer Razer BlackWidow Chroma V2 Consumer Control (/dev/input/event2) [ 594.487] (**) Razer Razer BlackWidow Chroma V2 Consumer Control: Applying InputClass "libinput keyboard catchall" [ 594.487] (II) Using input driver 'libinput' for 'Razer Razer BlackWidow Chroma V2 Consumer Control' [ 594.487] (**) Razer Razer BlackWidow Chroma V2 Consumer Control: always reports core events [ 594.487] (**) Option "Device" "/dev/input/event2" [ 594.487] (**) Option "_source" "server/udev" [ 594.498] (II) event2 - Razer Razer BlackWidow Chroma V2 Consumer Control: is tagged by udev as: Keyboard [ 594.498] (II) event2 - Razer Razer BlackWidow Chroma V2 Consumer Control: device is a keyboard [ 594.500] (II) event2 - Razer Razer BlackWidow Chroma V2 Consumer Control: device removed [ 594.520] (II) libinput: Razer Razer BlackWidow Chroma V2 Consumer Control: needs a virtual subdevice [ 594.520] (**) Option "config_info" "udev:/sys/devices/platform/ff580000.usb/usb1/1-1/1-1:1.1/0003:1532:0221.0002/input/input2/event2" [ 594.520] (II) XINPUT: Adding extended input device "Razer Razer BlackWidow Chroma V2 Consumer Control" (type: MOUSE, id 10) [ 594.521] (**) Option "AccelerationScheme" "none" [ 594.521] (**) Razer Razer BlackWidow Chroma V2 Consumer Control: (accel) selected scheme none/0 [ 594.521] (**) Razer Razer BlackWidow Chroma V2 Consumer Control: (accel) acceleration factor: 2.000 [ 594.521] (**) Razer Razer BlackWidow Chroma V2 Consumer Control: (accel) acceleration threshold: 4 [ 594.531] (II) event2 - Razer Razer BlackWidow Chroma V2 Consumer Control: is tagged by udev as: Keyboard [ 594.532] (II) event2 - Razer Razer BlackWidow Chroma V2 Consumer Control: device is a keyboard [ 594.538] (II) config/udev: Adding input device Razer Razer BlackWidow Chroma V2 System Control (/dev/input/event3) [ 594.539] (**) Razer Razer BlackWidow Chroma V2 System Control: Applying InputClass "libinput keyboard catchall" [ 594.539] (II) Using input driver 'libinput' for 'Razer Razer BlackWidow Chroma V2 System Control' [ 594.539] (**) Razer Razer BlackWidow Chroma V2 System Control: always reports core events [ 594.539] (**) Option "Device" "/dev/input/event3" [ 594.539] (**) Option "_source" "server/udev" [ 594.549] (II) event3 - Razer Razer BlackWidow Chroma V2 System Control: is tagged by udev as: Keyboard [ 594.550] (II) event3 - Razer Razer BlackWidow Chroma V2 System Control: device is a keyboard [ 594.551] (II) event3 - Razer Razer BlackWidow Chroma V2 System Control: device removed [ 594.572] (**) Option "config_info" "udev:/sys/devices/platform/ff580000.usb/usb1/1-1/1-1:1.1/0003:1532:0221.0002/input/input3/event3" [ 594.572] (II) XINPUT: Adding extended input device "Razer Razer BlackWidow Chroma V2 System Control" (type: KEYBOARD, id 11) [ 594.572] (**) Option "xkb_model" "pc105" [ 594.572] (**) Option "xkb_layout" "us" [ 594.583] (II) event3 - Razer Razer BlackWidow Chroma V2 System Control: is tagged by udev as: Keyboard [ 594.584] (II) event3 - Razer Razer BlackWidow Chroma V2 System Control: device is a keyboard [ 594.590] (II) config/udev: Adding input device Razer Razer BlackWidow Chroma V2 (/dev/input/event4) [ 594.591] (II) No input driver specified, ignoring this device. [ 594.591] (II) This device may have been added with another device file. [ 594.596] (II) config/udev: Adding input device Razer Razer BlackWidow Chroma V2 (/dev/input/event5) [ 594.596] (**) Razer Razer BlackWidow Chroma V2: Applying InputClass "libinput pointer catchall" [ 594.596] (II) Using input driver 'libinput' for 'Razer Razer BlackWidow Chroma V2' [ 594.596] (**) Razer Razer BlackWidow Chroma V2: always reports core events [ 594.596] (**) Option "Device" "/dev/input/event5" [ 594.596] (**) Option "_source" "server/udev" [ 594.664] (II) event5 - Razer Razer BlackWidow Chroma V2: is tagged by udev as: Mouse [ 594.665] (II) event5 - Razer Razer BlackWidow Chroma V2: device is a pointer [ 594.667] (II) event5 - Razer Razer BlackWidow Chroma V2: device removed [ 594.708] (**) Option "config_info" "udev:/sys/devices/platform/ff580000.usb/usb1/1-1/1-1:1.2/0003:1532:0221.0003/input/input5/event5" [ 594.708] (II) XINPUT: Adding extended input device "Razer Razer BlackWidow Chroma V2" (type: MOUSE, id 12) [ 594.709] (**) Option "AccelerationScheme" "none" [ 594.709] (**) Razer Razer BlackWidow Chroma V2: (accel) selected scheme none/0 [ 594.709] (**) Razer Razer BlackWidow Chroma V2: (accel) acceleration factor: 2.000 [ 594.709] (**) Razer Razer BlackWidow Chroma V2: (accel) acceleration threshold: 4 [ 594.776] (II) event5 - Razer Razer BlackWidow Chroma V2: is tagged by udev as: Mouse [ 594.777] (II) event5 - Razer Razer BlackWidow Chroma V2: device is a pointer [ 594.783] (II) config/udev: Adding input device Razer Razer BlackWidow Chroma V2 (/dev/input/mouse0) [ 594.784] (II) No input driver specified, ignoring this device. [ 594.784] (II) This device may have been added with another device file. [ 594.787] (II) config/udev: Adding input device gpio_ir_recv (/dev/input/event8) [ 594.788] (**) gpio_ir_recv: Applying InputClass "libinput keyboard catchall" [ 594.788] (II) Using input driver 'libinput' for 'gpio_ir_recv' [ 594.788] (**) gpio_ir_recv: always reports core events [ 594.788] (**) Option "Device" "/dev/input/event8" [ 594.788] (**) Option "_source" "server/udev" [ 594.795] (II) event8 - gpio_ir_recv: is tagged by udev as: Keyboard Pointingstick [ 594.796] (II) event8 - gpio_ir_recv: device is a pointer [ 594.797] (II) event8 - gpio_ir_recv: device is a keyboard [ 594.800] (II) event8 - gpio_ir_recv: device removed [ 594.852] (II) libinput: gpio_ir_recv: needs a virtual subdevice [ 594.852] (**) Option "config_info" "udev:/sys/devices/platform/ir-receiver/rc/rc1/input8/event8" [ 594.852] (II) XINPUT: Adding extended input device "gpio_ir_recv" (type: MOUSE, id 13) [ 594.853] (**) Option "AccelerationScheme" "none" [ 594.853] (**) gpio_ir_recv: (accel) selected scheme none/0 [ 594.853] (**) gpio_ir_recv: (accel) acceleration factor: 2.000 [ 594.853] (**) gpio_ir_recv: (accel) acceleration threshold: 4 [ 594.860] (II) event8 - gpio_ir_recv: is tagged by udev as: Keyboard Pointingstick [ 594.861] (II) event8 - gpio_ir_recv: device is a pointer [ 594.861] (II) event8 - gpio_ir_recv: device is a keyboard [ 594.909] (**) dw_hdmi: Applying InputClass "libinput keyboard catchall" [ 594.910] (II) Using input driver 'libinput' for 'dw_hdmi' [ 594.910] (**) dw_hdmi: always reports core events [ 594.910] (**) Option "Device" "/dev/input/event7" [ 594.910] (**) Option "_source" "_driver/libinput" [ 594.910] (II) libinput: dw_hdmi: is a virtual subdevice [ 594.910] (**) Option "config_info" "udev:/sys/devices/platform/ff3c0000.hdmi/rc/rc0/input7/event7" [ 594.911] (II) XINPUT: Adding extended input device "dw_hdmi" (type: KEYBOARD, id 14) [ 594.911] (**) Option "xkb_model" "pc105" [ 594.911] (**) Option "xkb_layout" "us" [ 594.912] (**) Razer Razer BlackWidow Chroma V2 Consumer Control: Applying InputClass "libinput keyboard catchall" [ 594.913] (II) Using input driver 'libinput' for 'Razer Razer BlackWidow Chroma V2 Consumer Control' [ 594.913] (**) Razer Razer BlackWidow Chroma V2 Consumer Control: always reports core events [ 594.913] (**) Option "Device" "/dev/input/event2" [ 594.913] (**) Option "_source" "_driver/libinput" [ 594.913] (II) libinput: Razer Razer BlackWidow Chroma V2 Consumer Control: is a virtual subdevice [ 594.913] (**) Option "config_info" "udev:/sys/devices/platform/ff580000.usb/usb1/1-1/1-1:1.1/0003:1532:0221.0002/input/input2/event2" [ 594.913] (II) XINPUT: Adding extended input device "Razer Razer BlackWidow Chroma V2 Consumer Control" (type: KEYBOARD, id 15) [ 594.913] (**) Option "xkb_model" "pc105" [ 594.913] (**) Option "xkb_layout" "us" [ 594.915] (**) gpio_ir_recv: Applying InputClass "libinput keyboard catchall" [ 594.915] (II) Using input driver 'libinput' for 'gpio_ir_recv' [ 594.915] (**) gpio_ir_recv: always reports core events [ 594.915] (**) Option "Device" "/dev/input/event8" [ 594.915] (**) Option "_source" "_driver/libinput" [ 594.915] (II) libinput: gpio_ir_recv: is a virtual subdevice [ 594.915] (**) Option "config_info" "udev:/sys/devices/platform/ir-receiver/rc/rc1/input8/event8" [ 594.915] (II) XINPUT: Adding extended input device "gpio_ir_recv" (type: KEYBOARD, id 16) [ 594.916] (**) Option "xkb_model" "pc105" [ 594.916] (**) Option "xkb_layout" "us" [ 610.980] (II) event6 - adc-keys: device removed [ 611.037] (II) event0 - Razer Razer BlackWidow Chroma V2: device removed [ 611.052] (II) event1 - Razer Razer BlackWidow Chroma V2 Keyboard: device removed [ 611.069] (II) event3 - Razer Razer BlackWidow Chroma V2 System Control: device removed [ 611.084] (II) event5 - Razer Razer BlackWidow Chroma V2: device removed [ 611.116] (II) event7 - dw_hdmi: device removed [ 611.132] (II) event2 - Razer Razer BlackWidow Chroma V2 Consumer Control: device removed [ 611.148] (II) event8 - gpio_ir_recv: device removed [ 611.193] (II) UnloadModule: "libinput" [ 611.193] (II) UnloadModule: "libinput" [ 611.193] (II) UnloadModule: "libinput" [ 611.193] (II) UnloadModule: "libinput" [ 611.193] (II) UnloadModule: "libinput" [ 611.194] (II) UnloadModule: "libinput" [ 611.194] (II) UnloadModule: "libinput" [ 611.194] (II) UnloadModule: "libinput" [ 611.194] (II) UnloadModule: "libinput" [ 611.194] (II) UnloadModule: "libinput" [ 611.199] (II) UnloadModule: "libinput" [ 611.370] (II) Server terminated successfully (0). Closing log file. 1 Quote
jock Posted September 24, 2021 Author Posted September 24, 2021 Nope, it looks like there is nothing really interesting. Maybe it's just the mesa Lima driver which is just too old. I sorted out the display problems, but then other issues regarding the i2s bus with kernel 5.14 came up. I think I can build a couple of fresh images with the 5.10 kernel which is good enough for now. 1 Quote
AlwinLub Posted September 24, 2021 Posted September 24, 2021 1 hour ago, jock said: Nope, it looks like there is nothing really interesting. Maybe it's just the mesa Lima driver which is just too old. I sorted out the display problems, but then other issues regarding the i2s bus with kernel 5.14 came up. I think I can build a couple of fresh images with the 5.10 kernel which is good enough for now. If you need someone for testing, let me know. I'm happy to test it out. 1 Quote
jock Posted September 24, 2021 Author Posted September 24, 2021 Update! Images with mainline kernel have been updated to Debian Bullseye (minimal) and Ubuntu Hirsute (xfce desktop) with kernel 5.10.68. Kernel is the same major version as previous mainline images, but Bullseye and Hirsute should provide significant newer software packages (including new Mesa libraries for those interested in graphics). 3 Quote
pakos96 Posted September 24, 2021 Posted September 24, 2021 Hi, thank you for your work! I've tried the latest image with mainline kernel Ubuntu Hirsute on my android box bought on Amazon Italy called "Bqeel TV Box R2 PLUS 4GB +64GB CPU RK3318" (https://www.amazon.it/gp/product/B07VXMTD78). I installed the image on the eMMC and tried a bit to see how the performance was. It starts up correctly but it lags enough. I have created with "armbianmonitor -u" a log that maybe can help you. This is the specification: RK3318, 4GB RAM, 64GB ROM, WIFI AP6330. This is the link of the log: ix.io/3zSk (verbosity 7) This is the link for download the original Android ROM: https://mega.nz/file/AYlDhA7L#y7vW7S3arW995X_m5c8URa3UGVTzxm0KDrC1-aNplGw. Unfortunately I don't know how to use the soldering iron and I don't have the skills to connect a serial cable. Hope it can help you somehow. Cheers 1 Quote
Ben N Voutour Posted September 25, 2021 Posted September 25, 2021 5 hours ago, pakos96 said: Hi, thank you for your work! I've tried the latest image with mainline kernel Ubuntu Hirsute on my android box bought on Amazon Italy called "Bqeel TV Box R2 PLUS 4GB +64GB CPU RK3318" (https://www.amazon.it/gp/product/B07VXMTD78). I installed the image on the eMMC and tried a bit to see how the performance was. It starts up correctly but it lags enough. I have created with "armbianmonitor -u" a log that maybe can help you. This is the specification: RK3318, 4GB RAM, 64GB ROM, WIFI AP6330. This is the link of the log: ix.io/3zSk (verbosity 7) This is the link for download the original Android ROM: https://mega.nz/file/AYlDhA7L#y7vW7S3arW995X_m5c8URa3UGVTzxm0KDrC1-aNplGw. Unfortunately I don't know how to use the soldering iron and I don't have the skills to connect a serial cable. Hope it can help you somehow. Cheers could you do a log with the cpu clocked at 1.3 GHz? 0 Quote
usual user Posted September 25, 2021 Posted September 25, 2021 On 9/22/2021 at 4:59 PM, AlwinLub said: Kivy does not play nice with this version of Mesa (20.3.5). I don't know what requirements Kivy places on the graphics stack, but since Panfrost achieves OpenGL ES 3.1 conformance on Mali-G52, it certainly makes sense to read this to understand what to expect from a lima-driven GPU. I still remember very well times when my GPU only reached almost 2.0 and the performance was quite moderate. With now 3.1 it's a big difference for daily desktop use, although my GPU isn't yet declared fully compliant. But since this is bleeding edge development, at least the current mesa mainline release is required in any case. If not even the main branch to use just implemented extentions. Kernel driver wise everything necessary should already be available and therefor mesa is where you are looking for GPU support improvements. 2 Quote
Ben N Voutour Posted September 25, 2021 Posted September 25, 2021 2 hours ago, usual user said: I don't know what requirements Kivy places on the graphics stack, but since Panfrost achieves OpenGL ES 3.1 conformance on Mali-G52, it certainly makes sense to read this to understand what to expect from a lima-driven GPU. I still remember very well times when my GPU only reached almost 2.0 and the performance was quite moderate. With now 3.1 it's a big difference for daily desktop use, although my GPU isn't yet declared fully compliant. But since this is bleeding edge development, at least the current mesa mainline release is required in any case. If not even the main branch to use just implemented extentions. Kernel driver wise everything necessary should already be available and therefor mesa is where you are looking for GPU support improvements. i'd like to test the new version and see if it is any better the last build 0 Quote
usual user Posted September 25, 2021 Posted September 25, 2021 25 minutes ago, RetroFan90 said: i'd like to test the new version and see if it is any better the last build Then why not start, @jock has announced new versions and the links on the first page are already up? 2 Quote
jock Posted September 25, 2021 Author Posted September 25, 2021 @pakos96 Hello! I guess you are saying that is lagging because desktop is not very reactive. For start, it is wisely suggested in armbian to disable the xfce desktop compositor (Menu -> System -> Window Manager Tweaks). Don't expect very fast graphical performance, mali-450 is still a limited GPU. Also, until I don't enable the RAM frequency scaling, the RAM is fixed at 330 MHz (instead of usual 667 or 800 MHz) and this is a huge hit for general graphical performance. @usual user As far as I see, armbian hirsute should have oibaf repository enabled and so Mesa comes as the latest development release 2 Quote
fabiobassa Posted September 25, 2021 Posted September 25, 2021 @RetroFan90 you are welcome to test every single image jock is assemblying bit I don't think this is the right approach to this CCS case community study on rk3318 and generally on every tvbox and every soc born to do other things in their life ( TVBOX !!!!) Just reporting " this doesn't work" or " this is lagged" or can you test cpu at 1.3 or 1,8 Ghz is overhealming problem of those @jock ( and me, but I am more the hardware man..) is already informed Until the whole X system isn't mature , every single piece is on place, every right library is in the right directory I think that we can enjoy the steps every day we are doing together, and what Jock did is so big step that mostly of ourselves can't believe ! At the actual state of the art there is none or few chanches that every thing will work out of the box. Study first the whole picture and then go deep in particular features But the road is signed !!! 2 Quote
AlwinLub Posted September 25, 2021 Posted September 25, 2021 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): Spoiler from kivy.config import Config Config.set('graphics', "multisamples", '0') EDIT: After building Kivy with OpenGL ES support, the whole ui works smoothly at around 30 - 70fps. Have a good weekend! 4 Quote
pakos96 Posted September 25, 2021 Posted September 25, 2021 10 hours ago, jock said: @pakos96 Hello! I guess you are saying that is lagging because desktop is not very reactive. For start, it is wisely suggested in armbian to disable the xfce desktop compositor (Menu -> System -> Window Manager Tweaks). Don't expect very fast graphical performance, mali-450 is still a limited GPU. Also, until I don't enable the RAM frequency scaling, the RAM is fixed at 330 MHz (instead of usual 667 or 800 MHz) and this is a huge hit for general graphical performance. @usual user As far as I see, armbian hirsute should have oibaf repository enabled and so Mesa comes as the latest development release Hi, thanks for your reply. Sorry but I can only reply to the topic once a day. I've installed the minimal version and it's ok. No problem so far. I sent the links in the previous message in the hope that you can find something useful. I hope so I don't want to get the idea that I complained that it was "lagging" but it was just to be able to provide more information about my tv box and help in some way with the development. These are the double-sided photos of the card (if it can help): I am currently using the limited 1.1GHz version (although in reality the max speed is 1.01GHz), I have installed pi-hole and unbound and have not noticed any problems at the moment. Thanks again! 2 Quote
jock Posted September 26, 2021 Author Posted September 26, 2021 @pakos96 Ookay, got it! Glad to hear everything is fine Thanks for the photos, they are always useful to inspect the board! 2 Quote
pakos96 Posted September 27, 2021 Posted September 27, 2021 Sorry, I've a question. It's possible to install "docker" in your latest armbian minimal build? I've followed the official guide on Docker website but I've an error when I try to install "docker-ce" (sorry but the follow screenshot it's in Italian language). In English: Package docker-ce is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source. However these packages replace it: docker-ce-cli:amd64 E: Package 'docker-ce' has no installation candidate E: Unable to locate package docker-ce-cli E: Unable to locate package containerd.io E: Couldn't find any package by glob 'containerd.io' E: Couldn't find any package by regex 'containerd.io' What can I do? Can you suggest me something? Thank you! 0 Quote
jock Posted September 27, 2021 Author Posted September 27, 2021 @pakos96 don't know anything about docker, maybe armbian-config has an automated script to install docker, you may check it out. Also you can post in the general chit chat community forum about, I'm sure there you may get a more detailed answer. 1 Quote
curse Posted September 27, 2021 Posted September 27, 2021 Note: If you get an E: Package 'docker-ce' has no installation candidateerror when using only stable APT source this is because the stable version of docker for Ubuntu 20.04 doesn’t exist yet. Meanwhile you have to use the edge / test version. https://grigorkh.medium.com/how-to-install-docker-on-ubuntu-20-04-f1b99845959e#:~:text=Note%3A If you get an E%3A Package 'docker-ce',have to use the edge %2F test version. My first hit on a Google search. 1 Quote
pakos96 Posted September 27, 2021 Posted September 27, 2021 3 hours ago, jock said: @pakos96 don't know anything about docker, maybe armbian-config has an automated script to install docker, you may check it out. Also you can post in the general chit chat community forum about, I'm sure there you may get a more detailed answer. Yes, armbian-config should have an automated script for docker installation but I didn't find it. For this reason I was looking for a manual installation. I've read comments in the past that docker worked without problems and I wanted to try it too. Thank you for your suggestion. 1 hour ago, curse said: Note: If you get an E: Package 'docker-ce' has no installation candidateerror when using only stable APT source this is because the stable version of docker for Ubuntu 20.04 doesn’t exist yet. Meanwhile you have to use the edge / test version. https://grigorkh.medium.com/how-to-install-docker-on-ubuntu-20-04-f1b99845959e#:~:text=Note%3A If you get an E%3A Package 'docker-ce',have to use the edge %2F test version. My first hit on a Google search. I've the latest build with Debian 11 and should be compatible with docker. But I will check out also this link. Thanks 0 Quote
AlwinLub Posted September 28, 2021 Posted September 28, 2021 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 Quote
Ben N Voutour Posted September 30, 2021 Posted September 30, 2021 how would i go about putting retroarch and emulationstation as the ui instead of the desktop? and how do i get a complete dtb dump from android 9 as root? and can the dtb file frrom android 9 be used for armbian? 0 Quote
curse Posted October 1, 2021 Posted October 1, 2021 @jockSorry for an extremely late reply. I was on vacation in distant lands(visiting my mom in Sweden), and the only monitor I had available to use there was an old 1024x768 monitor which I couldn't get to work with Armbian. The only thing that worked was the Multitool. Well, I'm back home in the Canary Islands with the volcanoes now. So finally. I can report that the WiFi on my H96Max+ (RK3328) works with the last idea you had https://forum.armbian.com/topic/17597-csc-armbian-for-rk3318rk3328-tv-box-boards/?do=findComment&comment=127240 Thank you for all the help. 3 Quote
curse Posted October 4, 2021 Posted October 4, 2021 (edited) BTW, today I downloaded and installed the latest "minimal" "Armbian 21.11 - Debian Bullseye minimal - mainline kernel 5.10.68 - Download from here - Build date: 2021-09-24" I don't seem to find "armbian-config". In /usr/local/bin/ there is only rk3318-config. Has it been forgotten or is it just me who are looking at the wrong place? Edit/ I just remembered reading somewhere that armbian-config isn't in the minimal images because it needs a lot of dependencies... Edited October 4, 2021 by curse 1 Quote
Gausus Posted October 5, 2021 Posted October 5, 2021 On 10/1/2021 at 3:10 PM, curse said: @jockSorry for an extremely late reply. I was on vacation in distant lands(visiting my mom in Sweden), and the only monitor I had available to use there was an old 1024x768 monitor which I couldn't get to work with Armbian. The only thing that worked was the Multitool. Well, I'm back home in the Canary Islands with the volcanoes now. So finally. I can report that the WiFi on my H96Max+ (RK3328) works with the last idea you had https://forum.armbian.com/topic/17597-csc-armbian-for-rk3318rk3328-tv-box-boards/?do=findComment&comment=127240 Thank you for all the help. How did you make the WiFi work ? Did you write over the existing /lib/firmware/brcm/brcmfmac4334-sdio.rockchip,rk3318-box.txt ? Have tried the method without success. Have tested both nvram files past to brcmfmac4334-sdio.rockchip,rk3318-box.txt (reboot) WiFi in network-manager, enter password. After some time password prompt comes back asking for password. Opened the box, SP2743C on wifi chip. Google: wifi chip SP2743C , no result. Tested on mainline kernel 5.10.68 Run rk3318-config to configured , Wifi Broadcom BCM4334/Ampak6334 - Dev ID: 02d0:4334 armbianEnv.ini: overlays=rk3318-box-cpu-hs rk3318-box-led-conf1 rk3318-box-wlan-ap6334 Have also tested with: overlays=3318-box-wlan-ap6330 H96 Max+ RK3328 (4G/64G) dmesg from clean install , only run .rk3318-config and reboot. 0 Quote
Recommended Posts
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.