![]() ![]()
In nf, leave also the "default" armbian configuration file (which should be already in directory) and remove everything else. OPENGL 2.1 SUPERTUXKART DRIVERNormally, for example, modelines and resolutions are autodetected by the driver and you should not specify them manually (you can also take a look to the detected modelines in /var/log/Xorg.0.log file if you want). Nowadays X.org is doing good job at autoconfiguring itself, and the configuration files are there for "little" adjustments. I have my own rule for nf files: the less configuration you write the best it performs. Modes "1920x1080" "1280x1024" "1024x768" "800圆00"Īhhh, mixing modesetting and armsoc is not a wise idea, actually I don't know what is going to be chosen by X11 server. OPENGL 2.1 SUPERTUXKART UPDATEI will attach a screenshot to this, if anyone knows, please update the thread. Maybe gl4es does not support some of the GL code used ? I am not sure why Supertuxkart does not work. Pretty soon I will be able to experiment with GnuRadio and get the more complex configurations that require a GPU running. Armegetron plays well 1080p, all options turned up. OPENGL 2.1 SUPERTUXKART FULLIf you look the config over and notice someting that will slow down glmark2-es2, please let me know.īzflag is playable at full 1080p, High Quality setting. I compiled and installed the GL4ES wrapper, and updated my configurations. At first I though not successfull because glmark2-es2 has poor benchmarks. OPENGL 2.1 SUPERTUXKART INSTALLInstall Jocks's X11 Armsoc Driver, Install Midgard Mali T86 Blobs. It's beginning to WORK! What I did was search for the Mesa Libraries, remove them. I'm pretty sure I'm getting close to getting hardware acceleration working on my nanopc-t4 If you have armsoc_dri.so can you attach it to this thread ? Without armsoc_dri I'm stuck software rendering. Ri.so failed (/usr/lib/aarch64-linux-gnu/dri/armsoc_dri.so: cannot open shared o (EE) AIGLX error: dlopen of /usr/lib/aarch64-linux-gnu/dri/armsoc_d Isn't that part of the armsoc driver build ? use-vbo=true: FPS: 13 FrameTime: 76.923 ms use-vbo=false: FPS: 11 FrameTime: 90.909 ms I ran glmark2-es2 glmark2-es2 -fullscreen I built Jock's forked X11 armsoc driver, Installed and configured the Malie BLOB rpm and configured for X11. (II) modeset(0): Manufacturer: GSM Model: 1 Serial#: 16843009 (II) modeset(0): Output DP-1 has no monitor section (II) modeset(0): Output HDMI-1 has no monitor section (WW) modeset(0): Glamor is using GLES2 but GLX needs GL. OPENGL 2.1 SUPERTUXKART PATCHMaybe you could ask for the patch on the RK32xx section, they have it working (armhf). I tried to build the xserver based on Rockchip xserver (debian) on Ubuntu, not much success. (EE) modeset(0): glamor initialization failed (II) glamor: OpenGL accelerated X.org driver based. ABI class: X.Org ANSI C Emulation, version 0.4 compiled for 1.19.6, module version = 1.0.0 (II) Module glamoregl: vendor="X.Org Foundation" (II) Loading /usr/lib/xorg/modules/libglamoregl.so (=) modeset(0): Default visual is TrueColor (=) modeset(0): Depth 24, (=) framebuffer bpp 32 "Default Screen Section" for depth/fbbpp 24/32 (II) modeset(0): Creating default Display subsection in Screen sect (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support compiled for 1.19.6, module version = 0.0.2 (II) Module fbdevhw: vendor="X.Org Foundation" ![]() (II) Loading /usr/lib/xorg/modules/libfbdevhw.so (WW) Falling back to old probe method for fbdev (II) modeset(0): using drv /dev/dri/card0 (II) FBDEV: driver for framebuffer: fbdev (II) modesetting: Driver for Modesetting Kernel Drivers: kms ABI class: X.Org Video Driver, version 23.0 compiled for 1.19.3, module version = 0.4.4 (II) Module fbdev: vendor="X.Org Foundation" (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so Is this error really due ot the xorg fbdev driver being loaded ? I followed the instructions, installed the dependencies and default OpenGLES/GL/CL first. I can run Kodi 18b5, which renders menu and video on mali.īlobs trying to use the mali userspace blobs. ![]() ![]() This blob setup below can save you a lot of sweat unless you really want to go with Panfrost. I have been playing with T86x on my NanoPi M4 and i can say 3D and OpenCL are working fine with the mali userspace blobs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |