Jump to content

fredrum

Members
  • Posts

    29
  • Joined

  • Last visited

Everything posted by fredrum

  1. Has anyone spotted a change in very recent kernel driver of pancfs turning into 'panthor'? It's mentioned here https://lwn.net/Articles/940957/ and is about Mali Mesa continous work. I guess I'll try to take a look at kernel repo's myself but I'm not used to doing that so thought I'd drop the info here as well. Cheers Update: Nope if I'm looking in the right place I can't see it in linux kernel 6.6-rc4 even. I think it should be living here 'drivers/gpu/drm/panthor' as per https://lore.kernel.org/linux-arm-kernel/20230809171017.64409d60@collabora.com/T/ for example. I guess its still way too early.
  2. Hello! Has anyone tried to play straight unconverted hevc video from a GoPro 11? Iv'e tried ffplay and gst-play but I'm just getting a static image and a bunch of these errors, [swscaler @ 0x7f49d399c0] [swscaler @ 0x7f49d47a50] deprecated pixel format used, make sure you did set range correctly I have successfully played example jellyfish videos of hevc and hevc 10bit formats, ffmpeg reports the following details from the GoPro footage, Stream #0:0[0x1](eng): Video: hevc (Main) (hvc1 / 0x31637668), yuvj420p(pc, bt709), 3840x2160 [SAR 1:1 DAR 16:9], 119725 kb/s, 119.88 fps, 119.88 tbr, 120k tbn (default) Any suggestions? Cheers!
  3. This Mekatronics box is using the rk3588 with the Mali-G610. (same gpu as Opi5) Presumably using the vendor blob drivers. glmark score: 3696 [ YouTube video showing test + result] I have been testing the Collabora new Mesa source and using Balbes test kernel builds with pancsf but I'm not getting anything near these numbers. IIRC I get around 1200-1300. I don't know what the Collabora plan is here as there doesn't seem to be much action as far as I can tell as an outside observer. Not sure how ready they think this Panfrost version ('v10') is? EDIT: Btw regarding video decoding the HW seems extremely capable. Here's a thread talking about 16 1080p streams simultaneously, https://forum.radxa.com/t/decoding-and-rendering-16-1080p-streams-with-gstreamer/16307
  4. I am currently using your 20230331-current image. Should I upgrade to one of your later ones? I had the smae issue before with getting the GPU recognized and not sure why. Could it be because I install to /usr/lib ? I do edit some ld config files and do 'sudo ldconfig' and it does make the system pick up my own built mesa but always with llvm. I did get GPU with a mesa build you linked to and I just copied straight to the default repo system folder. Could it just be the folder where I install it?
  5. Hello! Does anyone, and by anyone I probably really mean @balbes150 :D, know what I need to do when building official Mesa for it to be recognized in the experimental 6.x kernel environment? There's a panfrost focused dev/staging branch that the panfrost devs are using that I would love to try and be able to build for OPi5 but when I do it I always just get llvm. balbes, you are managing to get the GPU recognized would you be able to share how that's done in the building? I'm not asking for you to provide a build I would just love to know how you do it so I can as well and test the new versions as they happen. This is the branch and commits btw that I read on 'the internet' that its the bleeding edge for rk3588/Mali g610 mesa. https://gitlab.freedesktop.org/panfrost/mesa/-/commits/panfrost/v10-wip Iv'e successfully built that mesa branch and took the latest commits but the gpu is still not recognized so there must be a trick I'm missing. Does anyone have any suggestions? Cheers!
  6. Ohhhh with that one I now do get the GPU detected with glxinfo -B ! Nice one! [ I kept updating this maybe skip to the end for the success part? ] There are some very cool and strong graphical artifacts in some areas now and then and there's a error message from the glxinfo. Is there a device file I need to flip some permission on or something maybe? Using gnome+wayland. fred@orangepi5:~$ glxinfo -B name of display: :0 DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied Failed to create scanout resource display: :0 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Mesa (0xffffffff) Device: Mali-G610 (Panfrost) (0xffffffff) Version: 23.0.0 Accelerated: yes Video memory: 7695MB Unified memory: yes Preferred profile: compat (0x2) Max core profile version: 0.0 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1 OpenGL vendor string: Mesa OpenGL renderer string: Mali-G610 (Panfrost) OpenGL version string: 3.0 Mesa 23.0.0-devel (git-cbe80448cc) OpenGL shading language version string: 1.30 OpenGL context flags: (none) DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied Failed to create scanout resource OpenGL ES profile version string: OpenGL ES 3.1 Mesa 23.0.0-devel (git-cbe80448cc) OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10 Trying this but it doesn't help, sudo chmod a+rw /dev/dri/* I'll google around a bit! Don't worry if this is eating up your time and you'd rather spend that on other things. If that's the case I'll just leave this until its more mature. If not I'm happy to keep trying stuff. UPDATE: trying glmark2-es2-wayland but it doesn't find the GPU it is running with llvm. Both these ways of running: > glmark2-es2-wayland and > LD_LIBRARY_PATH="/usr/lib/aarch64-linux-gnu" glmark2-es2-wayland libEGL warning: egl: failed to create dri2 screen libEGL warning: failed to get driver name for fd 0 libEGL warning: MESA-LOADER: failed to retrieve device information libEGL warning: failed to get driver name for fd 0 glxgears also not happy: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied Failed to create scanout resource Segmentation fault Checking dmesg for drm: [just the tail of output] [ 2.449518] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable [rockchipdrm]] dclk_out0 div: 0 dclk_core0 div: 2 [ 2.449565] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable [rockchipdrm]] set dclk_vop0 to 148500000, get 148500000 [ 2.861015] rockchip-drm display-subsystem: [drm] fb0: rockchipdrmfb frame buffer device [ 2.878911] [drm] Initialized rockchip 3.0.0 20140818 for display-subsystem on minor 1 [ 3.117857] [drm:rockchip_drm_fault_handler [rockchipdrm]] *ERROR* iommu fault handler flags: 0x0 [ 3.243729] rockchip-vop2 fdd90000.vop: [drm:vop2_isr [rockchipdrm]] *ERROR* POST_BUF_EMPTY irq err at vp0 [ 3.244607] rockchip-vop2 fdd90000.vop: [drm:vop2_isr [rockchipdrm]] *ERROR* POST_BUF_EMPTY irq err at vp0 [ 3.245466] rockchip-vop2 fdd90000.vop: [drm:vop2_isr [rockchipdrm]] *ERROR* POST_BUF_EMPTY irq err at vp0 [ 3.246323] rockchip-vop2 fdd90000.vop: [drm:vop2_isr [rockchipdrm]] *ERROR* POST_BUF_EMPTY irq err at vp0 [ 3.247183] rockchip-vop2 fdd90000.vop: [drm:vop2_isr [rockchipdrm]] *ERROR* POST_BUF_EMPTY irq err at vp0 [ 3.248039] rockchip-vop2 fdd90000.vop: [drm:vop2_isr [rockchipdrm]] *ERROR* POST_BUF_EMPTY irq err at vp0 [ 3.248895] rockchip-vop2 fdd90000.vop: [drm:vop2_isr [rockchipdrm]] *ERROR* POST_BUF_EMPTY irq err at vp0 [ 3.249757] rockchip-vop2 fdd90000.vop: [drm:vop2_isr [rockchipdrm]] *ERROR* POST_BUF_EMPTY irq err at vp0 [ 4.753891] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm... [ 4.802028] systemd[1]: modprobe@drm.service: Deactivated successfully. [ 4.803050] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm. [ 24.800483] [drm:rockchip_drm_fault_handler [rockchipdrm]] *ERROR* iommu fault handler flags: 0x0 [ 24.801159] rockchip-vop2 fdd90000.vop: [drm:vop2_isr [rockchipdrm]] *ERROR* POST_BUF_EMPTY irq err at vp0 UPDATE 2: Waaiiit a minute. It seems my custom build Mesa was interfering even after I had reset the ld conf files + sudo ldconfig. Now I was able to run, > LD_LIBRARY_PATH="/usr/lib/aarch64-linux-gnu" glmark2-es2-wayland and without changing the default governor I got: glmark2 Score: 2189 Success!! There were still some strong glitching in the following, [jellyfish] [terrain] [refract] but maybe something in my own Mesa install still interefered. I still also get the DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied from glxinfo. UPDATE 3: After sticking the governor to performance glmark2-es2-wayland returns: glmark2 Score: 3455 A new record for me on this board! The other issues mentioned above are still there but maybe I'll have to re-run on a clean flashed SD card and see what goes away. That'll be for later because now I'm itching to try Dolphin again on this setup!
  7. Someone asked in a different thread how I got Dolphin to run so thought I'd start a thread so not to pollute the other one. Basically it wasn't that hard especially if youve done some git'hubbing before. I think I followed the 'Ubuntu' instructions here. Make sure you get the dependencies and do all the steps correctly. It should build without problems if you do. (remember you have a lot of cores on Opi5 so can use 'make -j6' or even higher) https://github.com/dolphin-emu/dolphin/wiki/Building-for-Linux You then want to set a config flag to make Dolphin use GLES instead of big brother OpenGL. (you probably want to run it at least once to generate the config files) nano ~/.config/dolphin-emu/GFX.ini add a line: PreferGLES = True But when running one of the more common games I got a shader compilation error. I hacked around that and also reported it on the Dolpin bug report site and it should be fixed soon when the 'PR' gets accepted. In the meantime you can read here what to do, https://bugs.dolphin-emu.org/issues/13198# Note that in my youtube video I get a good fps but later on in the game when you get to the first village the transparencies in the central square bonfire completely kills fps. The same happens in Metroid Prime when you have the large bluish holo walls in view. Mario Kart runs pretty well most of the time. Mario Sunshine as well at least in the plaza area I have't tried further. Cheers and Good Luck!
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines