Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Last time I tested (back on 5.5), supertuxkart worked for a little while but always ended up crashing after a few minutes. Also some benchmarks went through perfectly fine while others (especially those involving textures) either crashed or resulted in weird display. There were a few patches for the kernel from the panfrost team which I'm not sure were merged into 5.6. It might be good to ask the panfrost team if any need to be added on top of the 5.6 mainline.
  2. IIRC the default build settings for mesa install it in /usr/local when the version from packages goes into /usr. This can leave you in a pretty weird state in my experience. Setting the install path to /usr helps.
  3. You probably need to add permissions to (at least) `/dev/fb0 /dev/dri/card* /dev/dri/render*` if you start X while not root. This works on the Orange Pi 3 (Allwinner H6), it may be slightly different on other hardware.
  4. There’s probably a lot more than just the MBR missing. What kind of file system was it? How much data was in there? How long had you been using it?
  5. Ah indeed, a few dozen pages further it becomes clear...
  6. Can't find anything saying that some GPIOs would not allow interrupts in the doc, but I only looked relatively quickly. It's probably something in the DTB which tells the kernel whether the GPIO has interrupts or not, but I'm not quite familiar with their structure or contents... Another possibility could that the pin is believed by the kernel to be used for another function and thus interrupts are disabled, maybe? If I'm not mistaken GPIO117 is PD21, and PD21 is used by UART2?
  7. According to https://www.kernel.org/doc/Documentation/gpio/sysfs.txt gpio117 either cannot generate an interrupt, or this is not known to the kernel/driver. Trying to find the info in the H6 manual. Are you tied to this specific pin? Note that edge correctly appears for gpio40 for instance.
  8. Just upgraded to the latest Armbian 20.05 with kernel 5.5.0 final. It seems to be working well, however I'm still having issues with Panfrost/T720, just wondering if it's just me (messed up compilation or configuration somewhere) or if others have the same issue. jc@orangepi3:~$ glmark2 --validate ======================================================= glmark2 2017.07 ======================================================= OpenGL Information GL_VENDOR: Panfrost GL_RENDERER: Mali T720 (Panfrost) GL_VERSION: 2.1 Mesa 20.0.0-devel (git-f09c466732) ======================================================= [build] use-vbo=false:[ 570.822429] Purging 8519680 bytes Validation: Failure [build] use-vbo=true: Validation: Success [texture] texture-filter=nearest: Validation: Failure [texture] texture-filter=linear: Validation: Success Segmentation fault jc@orangepi3:~$ glmark2-es2 --validate ======================================================= glmark2 2017.07 ======================================================= OpenGL Information GL_VENDOR: Panfrost GL_RENDERER: Mali T720 (Panfrost) GL_VERSION: OpenGL ES 2.0 Mesa 20.0.0-devel (git-f09c466732) ======================================================= [build] use-vbo=false: Validation: Failure [build] use-vbo=true: Validation: Success [texture] texture-filter=nearest: Validation: Failure [texture] texture-filter=linear: Validation: Success [texture] texture-filter=mipmap: Validation: Failure [shading] shading=gouraud: Validation: Failure [shading] shading=blinn-phong-inf: Validation: Failure [shading] shading=phong: Validation: Failure [shading] shading=cel: Validation: Unknown [bump] bump-render=high-poly: Validation: Failure [bump] bump-render=normals: Validation: Failure [bump] bump-render=height: Validation: Failure [effect2d] kernel=0,1,0;1,-4,1;0,1,0;: Validation: Failure [effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: Validation: Failure [pulsar] light=false:quads=5:texture=false: Validation: Failure [desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: Validation: Failure [desktop] effect=shadow:windows=4: Validation: Failure [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: Validation: Failure [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: Validation: Success [buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: Validation: Success [ideas] speed=duration: Validation: Unknown [jellyfish] <default>: Validation: Unknown [terrain] <default>: Validation: Unknown [shadow] <default>: Validation: Unknown [refract] <default>: Validation: Unknown [conditionals] fragment-steps=0:vertex-steps=0: Validation: Failure [conditionals] fragment-steps=5:vertex-steps=0: Validation: Failure [conditionals] fragment-steps=0:vertex-steps=5: Validation: Failure [function] fragment-complexity=low:fragment-steps=5: Validation: Failure [function] fragment-complexity=medium:fragment-steps=5: Validation: Success [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: Validation: Success [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: Validation: Success [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: Validation: Success
  9. ___ ____ _ _____ / _ \| _ \(_) |___ / | | | | |_) | | |_ \ | |_| | __/| | ___) | \___/|_| |_| |____/ Welcome to Armbian buster with Linux 5.5.0-sunxi64 Thanks all for the great job! Still having issues with Panfrost/T720 though, I'll post in the Orange Pi 3 thread about that.
  10. The SPI on the header is actually SPI1, so you need: overlays=spi-spidev1 param_spidev_spi_bus=1 That should get you /dev/spidev1.0.
  11. In src/gallium/drivers/panfrost/pan_screen.c, function panfrost_create_screen, blacklist array (line 719 in the version I have). Also note that your chrome://gpu output says "Video Decode: Unavailable". This is (as far as I understand it) completely separate from panfrost/mesa etc. The video decode engine is a separate component in the SoC. There was a long discussion somewhere else in the forum about how to configure/install/compile things for that, though it is probably very SoC-dependent, I have no idea if there's support for the relevant component of the RK3399.
  12. That's weird, because I did the same test yesterday evening, and I have lots of crashes and validation failures. Same 5.5.0-rc6, mesa out of git master. What hardware are you running on? I'm on an Orange Pi 3 (H6, T720MP2). Also, did you remove the blacklisting of chrome/chromium in the panfrost mesa driver? Chrome shouldn't see panfrost. Can you share your X11 config related to panfrost, if any? I may be missing something...
  13. You should probably start by checking what chrome://gpu says to see exactly what is used or not.
  14. Video decoding uses a different part of the chip which is not related to panfrost (and much less to Mesa), does it? Also Chromium is blacklisted by Mesa for 3D (or at least it was a few ago when I checked).
  15. I believe you need to use a 5.5 kernel to get the latest panfrost-related patches (I might be wrong).
  • Create New...