Jump to content

jcaron

Members
  • Posts

    24
  • Joined

  • Last visited

Posts posted by jcaron

  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. On 3/29/2020 at 1:38 PM, balbes150 said:

    Strangely, when you build mesa-20, everything goes correctly, but after installing mesa, the old mesa-19 remains. Something changed in the rules, how do I install the new version ? Previously, the instruction worked correctly and mesa started using Panfrost. By the way, installation from repositories of the latest mesa-20 also does not use Panfrost.

     

    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. 6 hours ago, Salvador Liébana said:

    Hi, I am testing mesa panfrost on RK3399 and I am facing an odd problem. When joint the chroot as root I get mesa working but if I join as pi, the user, I cant get it working and I've receive just a soft render (llvmpipe)

    How this could be fixed?? any experience??

     

    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. 5 hours ago, szaro102 said:

    Files have not been deleted, first 1GB of disk was filed with "zero". So MBR are missing.


    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. 1 minute ago, martinayotte said:

    I've asked on chat, and @jernej answered me :

    H6 has interrupts on port F, G, H, L and M according to manual

    So, old trial on port C didn't worked, but on port F, example PF2, it is working and "edge" is present...

    Conclusion, reading manual is always a good thing to do :P

     

    Ah indeed, a few dozen pages further it becomes clear...

  6. 24 minutes ago, martinayotte said:

    Interesting ... On all my H6, "edge" is effectively not present, but is present on all my H3 or H5 ...

    I need to look deeper since it highlight my curiosity !

     

    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. 2 hours ago, Aleksandar said:

    Hello,

    I'm using orangepi3 with latest Armbian 20.02

    Why there is no egde file in /sys/class/gpio/gpioXXX/  like on the raspberrypi

     

    According to https://www.kernel.org/doc/Documentation/gpio/sysfs.txt

     

    Quote

    "edge" ... reads as either "none", "rising", "falling", or "both". Write these strings to select the signal edge(s) that will make poll(2) on the "value" file return. This file exists only if the pin can be configured as an interrupt generating input pin.

     

    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. 2 hours ago, Aleksandar said:

    I have OrangePi3 (Linux orangepi3 5.4.14-sunxi64 #rc1 SMP Sat Jan 25 15:46:08 CET 2020 aarch64 GNU/Linux ) running

    Armbian_20.02.0-rc1_Orangepi3_buster_current_5.4.14

    This is the board with 26-pin header.

     

    There is no /dev/spi0.0

     

    This is my /boot/armbianEnv.txt file

     

    [...]

    overlays=spi-spidev
    param_spidev_spi_bus=0
    param_spidev_spi_cs=0
    param_spidev_max_freq=1000000

     

    What else I can try to get /dev/spi

     

    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.

  10. 2 minutes ago, amirul said:

    Did not touch chromium settings. Where is chromium blacklisted in the mesa driver?

     

    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.

  11. 3 hours ago, amirul said:

    For anyone who is interested, here are glmark2 results

    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...

  12. 5 hours ago, amirul said:

    That may be true, I'm only reporting my experience with it. The clicks could be some hardware interference?

     

    You should probably start by checking what chrome://gpu says to see exactly what is used or not.

  13. 7 hours ago, amirul said:

    Seems usable, lets see what happens...

    ... online video in chromium slightly jerky with some weird clicking noise

     

    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).

  14. Note also that many build scripts will attempt to use several cores to speed things up, but the RAM-to-core ratio of SBCs is often not very favourable to this.

     

    You can usually add an option on the command line (often -j) to set the number of parallel jobs to run. 1 or 2 is probably more suitable than defaults like 4 or "number of cores" or "number of cores + 1".

     

  15. 24 minutes ago, AZ8 said:

    1. how far Armbian on Opi3 from stable point?

     

    This probably depends on your specific use case and the specific features you use. In my case I find it very stable, but I don't use any of the video acceleration features for instance, or sound, or cameras, and I haven't tested WiFi much. The only thing I'm waiting for is 3D GPU support.

  16. 2 hours ago, SchmuseTigger said:

    Wait, BT is working with 5.4 RC now?

     

    If by BT you mean Bluetooth like I do, it's working in 5.3 on the Orange Pi 3 using the Armbian nightly, it includes the firmware for the chip, there's just a bit of setup to do.

     

    IIRC all that is really needed is the init script available in the package included here:

    and a little change covered here:

     

  17. 20 minutes ago, leofuscaldi said:

    I don't know what else to try. My OPi3 Fails 100% of the attempts to use.... sometimes it doesn't even finish the boot, sometimes i can type login/pass before it freezes. Tried many many different nightly images.... It works stable with LibreElec beta image, but, I don't want to use mine (only) as kodi media center....

     

    Do you mean you can't get any version of Armbian to run on your Orange Pi 3 at all? I have one that's running very well using the Buster minimal version based on 5.3, including X, Chromium, HDMI output, Ethernet, USB, SPI... I have only tested Wi-Fi very quickly, but it worked out of the box. BT and SPI needed a little bit more configuration.

     

    I started from Armbian_5.98.191009_Orangepi3_Debian_buster_dev_5.3.5_minimal but have upgraded several times since. Currently on 5.3.7 5.98.191026.

     

    I'm booting directly from SD card, if that matters (no eMMC, 1 GB RAM).

     

    Really the only thing I'm missing for now is 3D GPU support (panfrost), other than that it's just perfect, though I don't use video at all so I have no idea of the support on that front.

     

    By the way, thanks to all for the really great job!

  18. 1 minute ago, megi said:

    T720 is blacklisted by panfrost driver in mesa.

     

    Ah indeed, I see that it's actually not whitelisted in the mesa panfrost driver. I also see the mesa panfrost driver blacklists Chromium which is my target use case, so it seems the panfrost+mesa route is not yet viable.

     

    So what options are there to be able to use the T720 GPU at the moment, if any?

     

    * Only using vendor system images such as those provided

    * Use armbian + binary driver + X11 driver (e.g. as described here: https://linux-sunxi.org/Xorg + https://linux-sunxi.org/Mali_binary_driver)? Is this actually applicable to the T720 or just the Mali 400 (probably with different drivers)?

     

    In the latter case (if that is even possible), is there any automated process to achieve that (e.g. download a specific Armbian image, install specific packages...) or is still a very manual process?

     

    Thanks in advance for any hints!

  19. 12 hours ago, PiotrO said:

    @jcaron

    Are You using mesa on t720 or mali blob?

     

     

     

    I'm not sure I understand the question, but I'm using Panfrost (or at least trying to), which as far as I understand, is the blob-less driver.

     

    Not quite sure whether mesa from packages is actually configured with panfrost support, though, is there a way to check that?

  20. On 10/18/2019 at 11:52 PM, LukeHack said:

    I'm using it since the 19/10/08 kernel release, no problem with glxgear nor compositing, glxinfo tell me direct rendering is enable, the driver support

    also good video decoding..

    i'm waiting for h264 encoding support.. then i will total happy :lol:

     

    Hi, could you provide a few more details about how you got this to work? I just can't get X to use panfrost on my Orange Pi 3, it's stuck on llvmpipe.

     

    Kernel:

    Linux orangepi3 5.3.7-sunxi64 #5.98.191020 SMP Sun Oct 20 02:43:11 CEST 2019 aarch64 GNU/Linux

     

    Logs about panfrost:

    sun4i-drm display-engine: bound 1100000.mixer (ops 0xffff000010becf50)
    sun4i-drm display-engine: bound 6510000.tcon-top (ops 0xffff000010bf1138)
    sun4i-drm display-engine: bound 6515000.lcd-controller (ops 0xffff000010be9450)
    sun4i-drm display-engine: bound 6000000.hdmi (ops 0xffff000010bec2f8)
    [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
    [drm] No driver support for vblank timestamp query.
    [drm] Initialized sun4i-drm 1.0.0 20150629 for display-engine on minor 0
    sun4i-drm display-engine: fb0: sun4i-drmdrmfb frame buffer device
    panfrost 1800000.gpu: clock rate = 432000000
    panfrost 1800000.gpu: bus_clock rate = 100000000
    panfrost 1800000.gpu: mali-t720 id 0x720 major 0x1 minor 0x1 status 0x0
    panfrost 1800000.gpu: features: 00000000,10309e40, issues: 00000000,21054400
    panfrost 1800000.gpu: Features: L2:0x07110206 Shader:0x00000000 Tiler:0x00000809 Mem:0x1 MMU:0x00002821 AS:0xf JS:0x7
    panfrost 1800000.gpu: shader_present=0x3 l2_present=0x1
    [drm] Initialized panfrost 1.0.0 20180908 for 1800000.gpu on minor 1
    

    Mesa is 19.3.0 from packages (it was bumped to this version a few days ago).

     

    I added a file /etc/X11/xorg.conf.d/02-panfrost.conf containing:

    Section "ServerFlags"
            Option  "AutoAddGPU" "off"
            Option "Debug" "dmabuf_capable"
    EndSection
    
    Section "OutputClass"
            Identifier "Panfrost"
            MatchDriver "sun4i-drm"
            Driver "modesetting"
            Option "PrimaryGPU" "true"
    EndSection

    But still nothing but llvmpipe.

     

    Did I miss something? Does the mesa from packages include panfrost support? Should I build from source? If you built from source, what options did you use?

     

    Thanks!

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines